just50415 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 0 forks source link

REFER then BYE incorrect CSeq from non-initiator of group chat #48

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Start a group chat
2. Have one of the invitees invite another participant (sends REFER)
3. Have that same invitee leave the chat (sends BYE)

What is the expected output? What do you see instead?
I expect the CSeq of the BYE to be one more than the CSeq of the previous 
REFER. Instead the BYE has the same CSeq.

What version of the product are you using? On what operating system?
2.3.5 on a variety of handsets and OS versions (an example is Android 2.3.3)

Please provide any additional information below.

Here are two sample messages received in sequence from the same handset:
REFER sip:chat1@192.168.30.241:5062 SIP/2.0
via: SIP/2.0/UDP 192.168.30.241:7050;branch=z9hG4bK8c44.c3136b55.0,SIP/2.0/UDP 
192.168.0.101:5060;branch=z9hG4bK60de132556aa30dd3e090fdaaae6d478323633;received
=24.89.236.25;
rport=63569
max-forwards: 69
call-id: np00-2-fGvT94kQdYko0NZW
from: <tel:+19024412865>;tag=eNcR4TT2BA
to: <tel:+19024528375>;tag=MfWMBnnFrYBipo7Y
cseq: 2 REFER
contact: <sip:24.89.236.25:63569>;+g.oma.sip-im
accept-contact: *;+g.oma.sip-im
refer-to: <tel:+19024528375>
user-agent: IM-client/OMA1.0 OrangeLabs-RCS-client/2.3.5
content-length: 0
p-preferred-identity: <tel:+19024412865>
refer-sub: false

BYE sip:chat1@192.168.30.241:5062 SIP/2.0
via: SIP/2.0/UDP 192.168.30.241:7050;branch=z9hG4bK8c44.d3136b55.0,SIP/2.0/UDP 
192.168.0.101:5060;branch=z9hG4bKd91382f510a95c7b7d2cbb0263b48d19323633;received
=24.89.236.25;
rport=63569
max-forwards: 69
call-id: np00-2-fGvT94kQdYko0NZW
from: <tel:+19024412865>;tag=eNcR4TT2BA
to: <tel:+19024528375>;tag=MfWMBnnFrYBipo7Y
cseq: 2 BYE
accept-contact: *;+g.oma.sip-im
refer-to: <tel:+19024528375>
content-length: 0
p-preferred-identity: <tel:+19024412865>
refer-sub: false

Original issue reported on code.google.com by iiaGa...@gmail.com on 20 Jan 2012 at 12:00

GoogleCodeExporter commented 8 years ago
Fixed in v2.4.1

Original comment by jmauffret@gmail.com on 30 Mar 2012 at 6:39