search

oussdag / imsdroid

Automatically exported from code.google.com/p/imsdroid
0 stars 0 forks source link

Client does not copy Record-Route header params while creating route set in ACK request. #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Basic INVITE call.

2.
3.

What is the expected output? What do you see instead?
Record-Route header params sent by server in 180 ringing are not copied into 
the route headers, this leads to server rejecting the ack.

What version of the product are you using? On what operating system?
IM-client/OMA1.0 IMSDroid/v1.0.271 (doubango r479)
Xperia X10 mini android 1.6
Please provide any additional information below.
I am pasting the packets in question hope this will be helpful..
SIP/2.0 200 OK
Content-Length: 277
P-Asserted-Identity: <sip:7001@other.scmdomain1.com>
Call-ID: b9cb4173-5001-e31e-6604-aae8dc08fef3
CSeq: 957575042 INVITE
From: <sip:7002@other.scmdomain1.com>;tag=1283668298081
To: <sip:7001@other.scmdomain1.com>;tag=s+1+41430000+6f074b91
Via: SIP/2.0/UDP 
192.168.1.12:56883;received=192.168.30.1;rport=56883;branch=z9hG4bK1283684730816
Record-Route: <sip:169928103@192.168.200.2:50607;lr>;X-DC-TM-IDX=1
Record-Route: 
<sip:169928103@192.168.200.2:5060;lr;comp=sigcomp>;X-DC-TM-IDX=1;X-ST-DLG-ID=536
870916;X-ST-CID-1=25020023;X-ST-CID-2=25020028
Server: Starent
Content-Type: application/sdp
Contact: <sip:192.168.210.2:50605;X-ST-CID-1=15020074;X-ST-CID-2=15020075>
History-Info: <sip:7001@other.scmdomain1.com>;index=1
History-Info: <sip:7001@other.scmdomain1.com>;index=1.1
History-Info: <sip:7001@192.168.30.1:1206>;index=1.1.1

v=0
o=MUSIX 1283754645599 1283754645599 IN IP4 mavenir.com
s=voipcall
c=IN IP4 192.168.1.13
t=0 0
m=audio 6000 RTP/AVP 0 8 3 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:3 gsm/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv
[Above is the 200 Ok to the client, notice the header params in record-route 
X-DC-TM-IDX=1;X-ST-DLG-ID=536870916;X-ST-CID-1=25020023;X-ST-CID-2=25020028]

Ack generated by the client[Notice route does not contain the abover params]

ACK sip:192.168.210.2:50605;X-ST-CID-1=15020074;X-ST-CID-2=15020075 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.12:56883;branch=z9hG4bK1283092282307;rport
From: <sip:7002@other.scmdomain1.com>;tag=1283668298081
To: <sip:7001@other.scmdomain1.com>;tag=s+1+41430000+6f074b91
Contact: 
<sip:7002@192.168.1.12:56883;transport=udp>;+g.oma.sip-im;language="en,fr"
Call-ID: b9cb4173-5001-e31e-6604-aae8dc08fef3
CSeq: 957575042 ACK
Content-Length: 0
Max-Forwards: 70
Route: <sip:169928103@192.168.200.2:5060;lr;comp=sigcomp>
Route: <sip:169928103@192.168.200.2:50607;lr>
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 IMSDroid/v1.0.271 (doubango r479)

RFC 3261 reference.
12.1.1 UAS behavior

   When a UAS responds to a request with a response that establishes a
   dialog (such as a 2xx to INVITE), the UAS MUST copy all Record-Route
   header field values from the request into the response (including the
   URIs, URI parameters, and any Record-Route header field parameters,
   whether they are known or unknown to the UAS) and MUST maintain the
   order of those values

Original issue reported on code.google.com by sourab.d...@gmail.com on 6 Sep 2010 at 7:16

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 6 Sep 2010 at 3:19

GoogleCodeExporter commented 9 years ago 
Fixed in version 1.0.279.

Original comment by boss...@yahoo.fr on 7 Sep 2010 at 8:11