Hi Antonio, 200 OK of INVITE contains the multiple Record-Route headers. All subsequent requests from UAC should follow the path as mentioned in Record-Route header and Address in contact header should be the final destination.
In the mentioned scenario, 200 OK have the following Record-Route header. Record-Route: <sip:172.16.55.100;lr;did=021.929cd6c2>. Record-Route: <sip:10.9.6.40>. Therefore, ACK is forwarded at address 172.16.55.100. However, there is one issue I observed that address 172.16.55.100 should be sent into Route header of ACK since it a loose router. Regards, Alok Tiwari Aricent ________________________________________ From: [email protected] [[email protected]] On Behalf Of Antonio Spirandelli [[email protected]] Sent: Saturday, November 03, 2012 6:33 PM To: [email protected] Subject: [Sip-implementors] Help understanding trace Hi All, this is my first post and hope it will be accepted. I am currently stuck to understand the following trace: U 2012/10/31 15:02:02.908748 10.9.6.3:5060 -> 172.16.55.100:5060 SIP/2.0 200 OK. Record-Route: <sip:172.16.55.100;lr;did=021.929cd6c2>. Record-Route: <sip:10.9.6.40>. Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE. Contact: sip:10.9.6.3. Supported: replaces,timer,path,100rel. User-Agent: OmniPCX Enterprise R10.0 j1.410.45.a. Session-Expires: 1800;refresher=uas. P-Asserted-Identity: "User A" <sip:[email protected];user=phone>. Content-Type: application/sdp. To: <sip:[email protected]>;tag=be6dedc56089bca6b558af187479406f. From: <sip:[email protected]>;tag=q-7313-723a. Call-ID: [email protected]. CSeq: 19584 INVITE. Via: SIP/2.0/UDP 172.16.55.100;branch=z9hG4bK1125.b8ca83d.0. Via: SIP/2.0/UDP 10.9.6.40:5060;branch=z9hG4bKiekjcfzC14701805113857. Content-Length: 197. . v=0. o=OXE 1351691970 1351691970 IN IP4 10.9.6.3. s=abs. c=IN IP4 172.16.52.215. t=0 0. m=audio 32514 RTP/AVP 18. a=sendrecv. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=ptime:30. a=maxptime:40. U 2012/10/31 15:02:02.913036 172.16.55.100:5060 -> 10.9.6.40:5060 SIP/2.0 200 OK. Record-Route: <sip:172.16.55.100;lr;did=021.929cd6c2>. Record-Route: <sip:10.9.6.40>. Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE. Contact: sip:10.9.6.3. Supported: replaces,timer,path,100rel. User-Agent: OmniPCX Enterprise R10.0 j1.410.45.a. Session-Expires: 1800;refresher=uas. P-Asserted-Identity: "User A" <sip:[email protected];user=phone>. Content-Type: application/sdp. To: <sip:[email protected]>;tag=be6dedc56089bca6b558af187479406f. From: <sip:[email protected]>;tag=q-7313-723a. Call-ID: [email protected]. CSeq: 19584 INVITE. Via: SIP/2.0/UDP 10.9.6.40:5060;branch=z9hG4bKiekjcfzC14701805113857. Content-Length: 197. . v=0. o=OXE 1351691970 1351691970 IN IP4 10.9.6.3. s=abs. c=IN IP4 172.16.52.215. t=0 0. m=audio 32514 RTP/AVP 18. a=sendrecv. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=ptime:30. a=maxptime:40. U 2012/10/31 15:02:02.918144 10.9.6.40:5060 -> 172.16.55.100:5060 ACK sip:172.16.55.100;lr;did=021.929cd6c2 SIP/2.0. From: <sip:[email protected]>;tag=q-7313-723a. To: <sip:[email protected]>;tag=be6dedc56089bca6b558af187479406f. Call-ID: [email protected]. CSeq: 19584 ACK. Max-Forwards: 70. Content-Length: 0. Contact: <sip:[email protected]>. Route: sip:10.9.6.3. Via: SIP/2.0/UDP 10.9.6.40:5060;branch=z9hG4bKyugtlplC14701805118363. . U 2012/10/31 15:02:02.919412 172.16.55.100:5060 -> 172.16.55.100:5060 ACK sip:172.16.55.100;lr;did=021.929cd6c2 SIP/2.0. From: <sip:[email protected]>;tag=q-7313-723a. To: <sip:[email protected]>;tag=be6dedc56089bca6b558af187479406f. Call-ID: [email protected]. CSeq: 19584 ACK. Max-Forwards: 69. Content-Length: 0. Contact: <sip:[email protected]>. Route: sip:10.9.6.3. Via: SIP/2.0/UDP 172.16.55.100;branch=z9hG4bK1125.b8ca83d.2. Via: SIP/2.0/UDP 10.9.6.40:5060;branch=z9hG4bKyugtlplC14701805118363. . U 2012/10/31 15:02:02.920799 172.16.55.100:5060 -> 172.16.55.100:5060 ACK sip:172.16.55.100;lr;did=021.929cd6c2 SIP/2.0. From: <sip:[email protected]>;tag=q-7313-723a. To: <sip:[email protected]>;tag=be6dedc56089bca6b558af187479406f. Call-ID: [email protected]. CSeq: 19584 ACK. Max-Forwards: 68. Content-Length: 0. Contact: <sip:[email protected]>. Route: sip:10.9.6.3. Via: SIP/2.0/UDP 172.16.55.100;branch=z9hG4bK1125.b8ca83d.2. Via: SIP/2.0/UDP 172.16.55.100;branch=z9hG4bK1125.b8ca83d.2. Via: SIP/2.0/UDP 10.9.6.40:5060;branch=z9hG4bKyugtlplC14701805118363. As you can see the last ACK goes always at IP 172.16.55.100 instead it should be go to IP 10.9.6.3!!! Does someone can help me understand it?? THanks _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors =============================================================================== Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =============================================================================== _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
