Hello, This box in the middle is a funny thing.
Is it a proxy? -> No. Is it a B2BUA? -> No. Is it an old fashioned strict router? ->Yes.Better to use the lr default nowadays Does it remove mandatory headers? ->Yes. RR header from 200 is removed It is not removing the Route header from the ACK.Try that? Best regards, Ben. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Wood Sent: dinsdag 3 februari 2009 15:06 To: [email protected] Subject: Re: [Sip-implementors] Misformed ACK causing media session to fail Thanks for the help. I think there have been several problems here. As far as I can see everything now looks right but theres still no media. When you say the CSeq of ACK received is still incorrect - I dont see how because this is set by the phone and the phone (Cisco) should be correct. Its set to the CSeq of the INVITE it sent which was 2. The CSeq of the INVITE forwarded by the proxy had a Cseq of 1. Therefore surely the ACK recieved (which has come from the caller) should have its Cseq set to 2 and when I forward it I should set it to 1: The current message sequence is as follows: If someone can help me sort this I'll buy you a drink of your chocie via PayPal :) Thanks Andrew Original INVITE: INVITE sip:[email protected];user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK924d84358e6d1376 Contact: <sip:[email protected]:5060;user=phone;transport=udp> To: <sip:[email protected];user=phone> From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 2 INVITE Expires: 300 Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Content-Type: application/sdp Proxy-Authorization: Digest username="userB",realm="",nonce="1233669092:4fe679fd01f6c6fc6426d3ed4e1e 0a8e",uri="sip:[email protected]",response="33a4f7084f92cd584236998a45 3e6217",qop=auth-int,nc=00000001,cnonce="54fcbd06" Supported: replaces, 100rel User-Agent: Cisco-CP7912/8.0.0-060111A Content-Length: 288 v=0 o=201 822997805 822997805 IN IP4 192.168.254.2 s=Cisco 7912 SIP Call c=IN IP4 192.168.254.2 t=0 0 m=audio 16384 RTP/AVP 0 18 8 101 a=rtpmap:0 PCMU/8000/1 a=rtpmap:18 G729/8000/1 a=fmtp:18 annexb=yes a=rtpmap:8 PCMA/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 Forwarded INVITE INVITE sip:[email protected]:5060;user=phone;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK924d84358e6d1376 Max-Forwards: 70 Record-Route: <sip:[email protected];user=phone> Contact: <sip:[email protected]:5060> To: <sip:[email protected]:5060;user=phone;transport=UDP> From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 288 v=0 o=201 822997805 822997805 IN IP4 192.168.254.2 s=Cisco 7912 SIP Call c=IN IP4 192.168.254.2 t=0 0 m=audio 16384 RTP/AVP 0 18 8 101 a=rtpmap:0 PCMU/8000/1 a=rtpmap:18 G729/8000/1 a=fmtp:18 annexb=yes a=rtpmap:8 PCMA/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 Recieved 180: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK924d84358e6d1376 Record-Route: <sip:[email protected];user=phone> Contact: <sip:[email protected]:5060;user=phone;transport=udp> To: <sip:[email protected]:5060;user=phone;transport=UDP>;tag=2081843699 From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 1 INVITE Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Server: Cisco-CP7912/8.0.0-060111A Content-Length: 0 Modified 180: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK924d84358e6d1376 Record-Route: <sip:[email protected];user=phone> Contact: <sip:[email protected]:5060;user=phone;transport=udp> To: <sip:[email protected];user=phone>;tag=2081843699 From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 2 INVITE Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Server: Cisco-CP7912/8.0.0-060111A Content-Length: 0 Recieved 200: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK924d84358e6d1376 Record-Route: <sip:[email protected];user=phone> Contact: <sip:[email protected]:5060;user=phone;transport=udp> To: <sip:[email protected]:5060;user=phone;transport=UDP>;tag=2081843699 From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 1 INVITE Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, PRACK, UPDATE Content-Type: application/sdp Server: Cisco-CP7912/8.0.0-060111A Supported: replaces Content-Length: 210 v=0 o=200 59717500 59717500 IN IP4 192.168.254.1 s=Cisco 7912 SIP Call c=IN IP4 192.168.254.1 t=0 0 m=audio 16384 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 Forwarded 200: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK924d84358e6d1376 Contact: <sip:[email protected]:5060;user=phone;transport=udp> To: <sip:[email protected];user=phone>;tag=2081843699 From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 2 INVITE Content-Type: application/sdp Content-Length: 210 v=0 o=200 59717500 59717500 IN IP4 192.168.254.1 s=Cisco 7912 SIP Call c=IN IP4 192.168.254.1 t=0 0 m=audio 16384 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 ACK received: ACK sip:[email protected];user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bKd5d9d6be8d1f1e82 Route: <sip:[email protected];user=phone;transport=udp> To: <sip:[email protected];user=phone>;tag=2081843699 From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 1 ACK //whether this is 1 or 2 doesnt make any difference Proxy-Authorization: Digest username="userB",realm="",nonce="1233669092:4fe679fd01f6c6fc6426d3ed4e1e 0a8e",uri="sip:[email protected]",response="33a4f7084f92cd584236998a45 3e6217",qop=auth-int,nc=00000001,cnonce="54fcbd06" User-Agent: Cisco-CP7912/8.0.0-060111A Content-Length: 0 Outgoing ACK is: ACK sip:[email protected]:5060;user=phone;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bKd5d9d6be8d1f1e82 Route: <sip:[email protected];user=phone;transport=udp> To: <sip:[email protected];user=phone>;tag=2081843699 From: <sip:[email protected];user=phone>;tag=3440312132 Call-ID: [email protected] CSeq: 2 ACK Proxy-Authorization: Digest username="userB",realm="",nonce="1233669092:4fe679fd01f6c6fc6426d3ed4e1e 0a8e",uri="sip:[email protected]",response="33a4f7084f92cd584236998a45 3e6217",qop=auth-int,nc=00000001,cnonce="54fcbd06" User-Agent: Cisco-CP7912/8.0.0-060111A Content-Length: 0 Kanumuri, Sreeram wrote: > 1) Cseq of "ACK received" is still incorrect. > 2) R-uri of ACK is incorrect. > > HTH, > Sreeram. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Wood > Sent: Monday, February 02, 2009 12:10 PM > To: [email protected] > Subject: Re: [Sip-implementors] Misformed ACK causing media session to fail > > OK Ive modified it but there still something not right. The message > sequence now is as follows, but again no media occurs: Caller is on > 192.168.254.2 Called on 192.168.254.1 Proxy on 192.168.254.254 > > Im sure its the ACK which doesnt match up somehow? > > Thanks > Andrew > > INVITE sip:[email protected];user=phone SIP/2.0 > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK9523fd3665380954 > Contact: <sip:[email protected]:5060;user=phone;transport=udp> > To: <sip:[email protected];user=phone> > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 2 INVITE > Expires: 300 > Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, > PRACK, UPDATE > Content-Type: application/sdp > Proxy-Authorization: Digest > username="userB",realm="",nonce="1233605027:bad5982674da293fa82c60338b75 3cee",uri="sip:[email protected]",response="d24526e9e871487934057e3dd3 b9f467",qop=auth-int,nc=00000001,cnonce="b06fb8c6" > > Supported: replaces, 100rel > User-Agent: Cisco-CP7912/8.0.0-060111A > Content-Length: 288 > > v=0 > o=201 816592305 816592305 IN IP4 192.168.254.2 > s=Cisco 7912 SIP Call > c=IN IP4 192.168.254.2 > t=0 0 > m=audio 16384 RTP/AVP 0 18 8 101 > a=rtpmap:0 PCMU/8000/1 > a=rtpmap:18 G729/8000/1 > a=fmtp:18 annexb=yes > a=rtpmap:8 PCMA/8000/1 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-15 > > > > Forwarded INVITE: > INVITE sip:[email protected]:5060;user=phone;transport=UDP SIP/2.0 > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK9523fd3665380954 > Max-Forwards: 70 > Record-Route: <sip:[email protected];user=phone> > Contact: <sip:[email protected]:5060> > To: <sip:[email protected]:5060;user=phone;transport=UDP> > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 1 INVITE > Content-Type: application/sdp > Content-Length: 288 > > v=0 > o=201 816592305 816592305 IN IP4 192.168.254.2 > s=Cisco 7912 SIP Call > c=IN IP4 192.168.254.2 > t=0 0 > m=audio 16384 RTP/AVP 0 18 8 101 > a=rtpmap:0 PCMU/8000/1 > a=rtpmap:18 G729/8000/1 > a=fmtp:18 annexb=yes > a=rtpmap:8 PCMA/8000/1 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-15 > > > Recieved 180: > SIP/2.0 180 Ringing > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK9523fd3665380954 > Record-Route: <sip:[email protected];user=phone> > Contact: <sip:[email protected]:5060;user=phone;transport=udp> > To: <sip:[email protected]:5060;user=phone;transport=UDP>;tag=2081843699 > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 1 INVITE > Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, > PRACK, UPDATE > Server: Cisco-CP7912/8.0.0-060111A > Content-Length: 0 > > > > Modified 180: > SIP/2.0 180 Ringing > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK9523fd3665380954 > Record-Route: <sip:[email protected];user=phone> > Contact: <sip:[email protected]:5060;user=phone;transport=udp> > To: <sip:[email protected];user=phone>;tag=2081843699 > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 2 INVITE > Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, > PRACK, UPDATE > Server: Cisco-CP7912/8.0.0-060111A > Content-Length: 0 > > > Recieved 200: > SIP/2.0 200 OK > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK9523fd3665380954 > Record-Route: <sip:[email protected];user=phone> > Contact: <sip:[email protected]:5060;user=phone;transport=udp> > To: <sip:[email protected]:5060;user=phone;transport=UDP>;tag=2081843699 > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 1 INVITE > Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, > PRACK, UPDATE > Content-Type: application/sdp > Server: Cisco-CP7912/8.0.0-060111A > Supported: replaces > Content-Length: 210 > > v=0 > o=200 53311362 53311362 IN IP4 192.168.254.1 > s=Cisco 7912 SIP Call > c=IN IP4 192.168.254.1 > t=0 0 > m=audio 16384 RTP/AVP 0 101 > a=rtpmap:0 PCMU/8000/1 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-15 > > > Forwarded 200: > SIP/2.0 200 OK > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK9523fd3665380954 > Contact: <sip:[email protected]:5060;user=phone;transport=udp> > To: <sip:[email protected];user=phone>;tag=2081843699 > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 2 INVITE > Content-Type: application/sdp > Content-Length: 210 > > v=0 > o=200 53311362 53311362 IN IP4 192.168.254.1 > s=Cisco 7912 SIP Call > c=IN IP4 192.168.254.1 > t=0 0 > m=audio 16384 RTP/AVP 0 101 > a=rtpmap:0 PCMU/8000/1 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-15 > setting tcsid = 406 > > > > ACK received: > ACK sip:[email protected];user=phone SIP/2.0 > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bKf1ec9d5e2277fec7 > Route: <sip:[email protected];user=phone;transport=udp> > To: <sip:[email protected];user=phone>;tag=2081843699 > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 2 ACK > Proxy-Authorization: Digest > username="userB",realm="",nonce="1233605027:bad5982674da293fa82c60338b75 3cee",uri="sip:[email protected]",response="d24526e9e871487934057e3dd3 b9f467",qop=auth-int,nc=00000001,cnonce="b06fb8c6" > User-Agent: Cisco-CP7912/8.0.0-060111A > Content-Length: 0 > > > > Outgoing ACK is: > ACK sip:[email protected];user=phone SIP/2.0 > Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bKf1ec9d5e2277fec7 > Route: <sip:[email protected];user=phone;transport=udp> > To: <sip:[email protected];user=phone>;tag=2081843699 > From: <sip:[email protected];user=phone>;tag=3440312132 > Call-ID: [email protected] > CSeq: 1 ACK > Proxy-Authorization: Digest > username="userB",realm="",nonce="1233605027:bad5982674da293fa82c60338b75 3cee",uri="sip:[email protected]",response="d24526e9e871487934057e3dd3 b9f467",qop=auth-int,nc=00000001,cnonce="b06fb8c6" > User-Agent: Cisco-CP7912/8.0.0-060111A > Content-Length: 0 > > > > Brett Tate wrote: > >> The following are three of the problems: >> >> 1) The "proxied" 200 has a malformed Contact. >> >> 2) The "proxied" ACK has an incorrect CSeq since it doesn't match the "proxied" INVITE's CSeq. >> >> 3) The request-uri of the ACKs appear incorrect; however it might be related to problems 1 and 2. >> >> >> > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
