[Serdev] [Tracker] Updated: (SER-372) Processing error when sending an ACK request back to SER to switch from TCP to UDP

[Jan Janak (JIRA)]

     [ http://tracker.iptel.org/browse/SER-372?page=all ]

Jan Janak updated SER-372:
--------------------------

    Fix Version/s: 2.0
                   Ipteldorf
         Assignee: Jan Janak

> Processing error when sending an ACK request back to SER to switch from TCP to UDP
> ----------------------------------------------------------------------------------
>
>                 Key: SER-372
>                 URL: http://tracker.iptel.org/browse/SER-372
>             Project: SER
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0
>         Environment: Linux x86, Clients are SIP-Communicator and Twinkle
>         Assigned To: Jan Janak
>            Priority: Minor
>             Fix For: 2.0, Ipteldorf
>
>
> Upon receiving the following ACK:
> ACK sip:bob at 10.100.1.33:5064 SIP/2.0
> Route: <sip:10.100.1.240;lr=on;transport=tcp;r2=on;ftag=bf79fb71>, <sip:10.100.1.240;lr=on;r2=on;ftag=bf79fb71>
> From: "jane" <sip:jane at cyprus.cam.zeus.com>;tag=bf79fb71
> CSeq: 1 ACK
> Content-Length: 0
> To: <sip:bob at example.com>;tag=sarxl
> Record-Route: <sip:10.100.1.33:5080;transport=tcp;lr=on>
> Call-ID: 5868257813c18dd3abd7f1e0ea1f875e at 0.0.0.0
> Max-Forwards: 69
> Via: SIP/2.0/TCP 10.100.1.33:39134;rport;branch=z9hG4bK35682726022s4gBh5L
> Via: SIP/2.0/TCP 0.0.0.0;branch=z9hG4bKe7ebad44d6214de2227bb2bcea7a6bd4;received=10.100.1.33
> SER seems to rewrite the request and put the bottom Route header in the target but then neglects to put the actual target anywhere and does some strange things with the Route and Record-Route header fields.
> The debug output from SER after it has finished processing the above request is:
> Sending: 
> ACK sip:10.100.1.240;lr=on;r2=on;ftag=bf79fb71 SIP/2.0
> Record-Route: <sip:10.100.1.240;r2=on;ftag=bf79fb71;lr=on>
> Record-Route: <sip:10.100.1.240;transport=tcp;r2=on;ftag=bf79fb71;lr=on>
> Route: 
> From: "jane" <sip:jane at cyprus.cam.zeus.com>;tag=bf79fb71
> CSeq: 1 ACK
> Content-Length: 0
> To: <sip:bob at cyprus.cam.zeus.com>;tag=sarxl
> Record-Route: <sip:10.100.1.33:5080;transport=tcp;lr=on>
> Call-ID: 5868257813c18dd3abd7f1e0ea1f875e at 0.0.0.0
> Max-Forwards: 16
> Via: SIP/2.0/UDP 10.100.1.240;branch=0;i=3
> Via: SIP/2.0/TCP 10.100.1.33:39134;rport=39134;branch=z9hG4bK35682726022s4gBh5L
> Via: SIP/2.0/TCP 0.0.0.0;branch=z9hG4bKe7ebad44d6214de2227bb2bcea7a6bd4;received=10.100.1.33
> P-hint: rr-enforced
> Then, when it receives the above request, it complains that there is a blank Route header and that the target of the request doesn't exist in the database and so discards the request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira