HI Fred, What you said is correct, but from my observations(from the capture below), we can see that when the SIP call succeeded, even in that case, there was no user part Request-URI in the ACK. Even the UA(AOL in my case) is observed to be sending ACK with no user part in the Request-URI. Could this mean that the UA is not 3261 compliant?? In that case the SIP call should not fail.
Please provide your comments. regards Mahesh On Mon, 2004-12-06 at 22:12, Sciscione, Frederic wrote: > Hi Manesh, > > As michael koehler indicated in a previous mail, your problem might be due to > the fact that userpart is missing in the Request-URI in the ACK; Check this > extract from RFC 3261 : > > "17.2.3 Matching Requests to Server Transactions > ... > If the branch parameter in the top Via header field is not present, > or does not contain the magic cookie, the following procedures are > used. These exist to handle backwards compatibility with RFC 2543 > compliant implementations. > > .... > > The ACK request matches a transaction if the Request- > URI, From tag, Call-ID, CSeq number (not the method), and top Via > header field match those of the INVITE request which created the > transaction, and the To tag of the ACK matches the To tag of the > response sent by the server transaction. Matching is done based on > the matching rules defined for each of those header fields. > " > > Cheers, > Fred. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of mahesh > akarapu > Sent: 04 December 2004 12:03 > To: mahesh akarapu > Cc: [EMAIL PROTECTED] > Subject: Re: [Sip-implementors] 200 OK after recieving ACK > > > Could some one please provide your comments on the following > observations. > > thanks > Mahesh > > On Fri, 2004-12-03 at 14:09, mahesh akarapu wrote: > > Hi all, > > > > I am sending the capture again as my previous attachments are filtered > > out. The initial part of the capture gives the summary of the packets > > and the later part gives the packet details. Please go through the > > capture and let me know your comments on this. > > > > NOTE: Packets (1-11) in the capture show the case where the SIP call was > > established and terminated normally. Packets (12-27) show the case where > > i observed the problem behavior. > > > > Thanks > > Mahesh > > > > Summary of the capture > > ---------------------- > > No. Time Source Destination Protocol > > Info > > 1 0.000000 202.125.84.170 202.125.84.171 SIP/SDP > > Request: INVITE sip:[EMAIL PROTECTED]:2323, with session description > > 2 0.001895 202.125.84.171 202.125.84.170 SIP > > Status: 100 Trying > > 3 0.002298 202.125.84.171 202.125.84.170 SIP > > Status: 180 Ringing > > 4 0.457915 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 5 0.957847 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 6 1.956892 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 7 3.132889 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2323 > > 8 3.406479 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2323 > > 9 3.504555 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2323 > > 10 9.637902 202.125.84.171 202.125.84.170 SIP > > Request: BYE sip:202.125.84.170:1464 > > 11 10.707566 202.125.84.170 202.125.84.171 SIP > > Status: 200 OK > > 12 177.486924 202.125.84.170 202.125.84.171 SIP/SDP > > Request: INVITE sip:[EMAIL PROTECTED]:2348, with session description > > 13 177.489169 202.125.84.171 202.125.84.170 SIP > > Status: 100 Trying > > 14 177.489344 202.125.84.171 202.125.84.170 SIP > > Status: 180 Ringing > > 15 177.918060 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 16 178.419757 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 17 179.418770 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 18 180.682108 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2348 > > 19 180.931235 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2348 > > 20 181.028713 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2348 > > 21 181.415804 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 22 181.611861 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2348 > > 23 185.419576 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 24 185.613523 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2348 > > 25 193.418232 202.125.84.171 202.125.84.170 SIP/SDP > > Status: 200 OK, with session description > > 26 193.624329 202.125.84.170 202.125.84.171 SIP > > Request: ACK sip:202.125.84.171:2348 > > 27 203.695962 202.125.84.171 202.125.84.170 SIP > > Request: BYE sip:202.125.84.170:1501 > > > > > > Packet Details > > -------------- > > Frame 1 (1108 on wire, 1108 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1463 (1463), Dst Port: 2323 (2323) > > Session Initiation Protocol > > Request line: INVITE sip:[EMAIL PROTECTED]:2323 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: <sip:[EMAIL PROTECTED]> > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.170:1464> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 2 (354 on wire, 354 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2323 (2323), Dst Port: 1464 (1464) > > Session Initiation Protocol > > Status line: SIP/2.0 100 Trying > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 3 (355 on wire, 355 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2323 (2323), Dst Port: 1464 (1464) > > Session Initiation Protocol > > Status line: SIP/2.0 180 Ringing > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 4 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2323 (2323), Dst Port: 1464 (1464) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2323> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 5 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2323 (2323), Dst Port: 1464 (1464) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2323> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 6 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2323 (2323), Dst Port: 1464 (1464) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2323> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 7 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1463 (1463), Dst Port: 2323 (2323) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2323 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 8 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1463 (1463), Dst Port: 2323 (2323) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2323 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 9 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1463 (1463), Dst Port: 2323 (2323) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2323 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1464 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > To: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 10 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2323 (2323), Dst Port: 1464 (1464) > > Session Initiation Protocol > > Request line: BYE sip:202.125.84.170:1464 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.171:2323 > > Max-Forwards: 70 > > From: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > To: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 BYE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 11 (347 on wire, 347 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1464 (1464), Dst Port: 2323 (2323) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.171:2323 > > From: > > <sip:[EMAIL PROTECTED]>;tag=0f5e01e201cf4d8cb1a3eddf366cc7c3 > > To: "intoalg3" > > <sip:intoalg3>;tag=b50173a54a7b452fa28be149c4756556 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 BYE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 12 (1108 on wire, 1108 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: INVITE sip:[EMAIL PROTECTED]:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: <sip:[EMAIL PROTECTED]> > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.170:1501> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 13 (354 on wire, 354 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 100 Trying > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 14 (355 on wire, 355 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 180 Ringing > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 15 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2348> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 16 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2348> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 17 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2348> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 18 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 19 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 20 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 21 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2348> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 22 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 23 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2348> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 24 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 25 (1098 on wire, 1098 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Status line: SIP/2.0 200 OK > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 INVITE > > Contact: <sip:202.125.84.171:2348> > > User-Agent: RTC/1.2 > > Content-Type: application/sdp > > Content-Length: 679 > > Session Description Protocol > > > > Frame 26 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.170 (202.125.84.170), Dst Addr: > > 202.125.84.171 (202.125.84.171) > > User Datagram Protocol, Src Port: 1500 (1500), Dst Port: 2348 (2348) > > Session Initiation Protocol > > Request line: ACK sip:202.125.84.171:2348 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.170:1501 > > Max-Forwards: 70 > > From: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > To: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 ACK > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > Frame 27 (386 on wire, 386 captured) > > Ethernet II > > Internet Protocol, Src Addr: 202.125.84.171 (202.125.84.171), Dst Addr: > > 202.125.84.170 (202.125.84.170) > > User Datagram Protocol, Src Port: 2348 (2348), Dst Port: 1501 (1501) > > Session Initiation Protocol > > Request line: BYE sip:202.125.84.170:1501 SIP/2.0 > > Message Header > > Via: SIP/2.0/UDP 202.125.84.171:2348 > > Max-Forwards: 70 > > From: > > <sip:[EMAIL PROTECTED]>;tag=a07546d948cf47cb9237fb91a479c9cc > > To: "intoalg3" > > <sip:intoalg3>;tag=aa45b7c47b6c4fab90a6b02005d61c27 > > Call-ID: [EMAIL PROTECTED] > > CSeq: 1 BYE > > User-Agent: RTC/1.2 > > Content-Length: 0 > > > > > > > > > > > > On Wed, 2004-12-01 at 19:00, michael koehler wrote: > > > From this point 1-11 looks fine, but 12-27 not and after several > > > retransmissions the callee > > > hung up the call. Maybe someone more familar with the "RTC" stack drop > > > a comment here. > > > > > > From my point of view even the first call could not work. Maybe have a > > > closer look at: rfc3261 / 17.1.1.3 Construction of the ACK Request. > > > > > > Ok, rfc2543 does not point the use of request-uri values out like > > > rfc3261 does in this case, but even in rfc2543 i can only find examples > > > like > > > these: > > > > > > ACK sip:[EMAIL PROTECTED] SIP/2.0 > > > Via: SIP/2.0/UDP north.east.isi.edu > > > From: Mark Handley <sip:[EMAIL PROTECTED]> > > > To: Eve Schooler <sip:[EMAIL PROTECTED]> ;tag=9883472 > > > Call-ID: [EMAIL PROTECTED] > > > CSeq: 1 ACK > > > > > > > > > Regards, > > > > > > Michael > > > > > > On Dec 1, 2004, at 2:00 PM, mahesh akarapu wrote: > > > > > > > Hi Michael, > > > > > > > > If you look at packets 1-11(this is the case where no 200 OK was sent > > > > after ACK is recieved), there also the request line does not contain > > > > the > > > > user part. I guess if it is because of the user part missing, then in > > > > the first case also we should see 200 Ok after ACK. > > > > > > > > What are your comments on this. > > > > > > > > regards > > > > Mahesh > > > > > > > > On Wed, 2004-12-01 at 17:02, michael koehler wrote: > > > >> Seems that ACK is missing the userpart of the request line. > > > >> > > > >> should be: > > > >> > > > >> ACK sip:[EMAIL PROTECTED] > > > >> > > > >> instead of > > > >> > > > >> ACK sip:202.125.84.170... > > > >> > > > >> > > > >> my 5c > > > >> > > > >> Michael > > > >> > > > >> On Dec 1, 2004, at 8:00 AM, mahesh akarapu wrote: > > > >> > > > >>> Hi, > > > >>> I am attaching the ethereal captures, so as to be clear on the > > > >>> problem. > > > >>> I am using the following network setup. > > > >>> > > > >>> HOST1---HOST2 > > > >>> > > > >>> HOST1(202.125.84.170) and HOST2(202.125.84.171) are windows-XP > > > >>> machines > > > >>> with AOL instant messengers as the UAs. Now a sip call is initiated > > > >>> from > > > >>> HOST1. I am attaching the ethereal capture on HOST2 where the problem > > > >>> behaviour is seen. > > > >>> Packets (1-11) in the capture show the case where the SIP call was > > > >>> established and terminated normally. Packets (12-27) show the case > > > >>> where > > > >>> i observed the problem behavior. > > > >>> Please go through the capture and let me know your comments on this. > > > >>> > > > >>> Regards > > > >>> Mahesh > > > >>> > > > >>> > > > >>> On Tue, 2004-11-30 at 20:49, Nataraju A B wrote: > > > >>>> If you can send the message details it would be easy to find out the > > > >>>> actual problem... > > > >>>> > > > >>>> Otherwise we could only find vague answer which may not be useful to > > > >>>> your actual problem... > > > >>>> > > > >>>> Best Regards, > > > >>>> Nataraju A.B. > > > >>>> > > > >>>> -----Original Message----- > > > >>>> From: [EMAIL PROTECTED] > > > >>>> [mailto:[EMAIL PROTECTED] On Behalf Of > > > >>>> michael > > > >>>> koehler > > > >>>> Sent: Tuesday, November 30, 2004 4:51 PM > > > >>>> To: mahesh akarapu > > > >>>> Cc: [EMAIL PROTECTED] > > > >>>> Subject: Re: [Sip-implementors] 200 OK after recieving ACK > > > >>>> > > > >>>> Mahesh, > > > >>>> > > > >>>> > > > >>>> when UAS is sending 200 after ACK then it could be that UAS is not > > > >>>> understaending your ACK request. > > > >>>> > > > >>>> ensure that your ACK request is matching: > > > >>>> > > > >>>> - request uri from INVITE (or record route) > > > >>>> - to/from headers incl. TAGS (to-tag from 200) > > > >>>> - call-id from INVITE > > > >>>> - cseq from INVITE > > > >>>> > > > >>>> > > > >>>> > > > >>>> > > > >>>> Have in mind this could also be a proxy bug and without further > > > >>>> details > > > >>>> it is only possible to give hints. At least, maybe your ACK is never > > > >>>> reaching the right destination. > > > >>>> > > > >>>> > > > >>>> > > > >>>> Regards, > > > >>>> > > > >>>> Michael > > > >>>> > > > >>>> > > > >>>> On Nov 30, 2004, at 6:17 AM, mahesh akarapu wrote: > > > >>>> > > > >>>>> Hi all, > > > >>>>> I have a doubt regarding how ACK requests are handled. > > > >>>>> I am trying to establish a SIP session. The following is the > > > >>>>> scenario. > > > >>>>> A------------B > > > >>>>> INV---------> > > > >>>>> <----------100 > > > >>>>> <----------180 > > > >>>>> <----------200 > > > >>>>> ACK---------> > > > >>>>> Till this point, it is OK.But after this there are repeated 200Ok > > > >>>>> from > > > >>>> > > > >>>>> B > > > >>>>> as below. > > > >>>>> <----------200 > > > >>>>> ACK---------> > > > >>>>> <----------200 > > > >>>>> ACK---------> > > > >>>>> > > > >>>>> I guess according to the RFC 3261, once ACK is received, the UA > > > >>>>> should > > > >>>>> stop sending the 200 OK.Could someone please tell me if this a > > > >>>> possible > > > >>>>> scenario, that is under what circumstances 200 OK is sent after > > > >>>>> recieving ACK. I could not get the answer for this from the RFC. > > > >>>>> > > > >>>>> Could someone answer this. > > > >>>>> > > > >>>>> thanks > > > >>>>> Mahesh > > > >>>>> > > > >>>>> > > > >>>>> > > > >>>>> _______________________________________________ > > > >>>>> Sip-implementors mailing list > > > >>>>> [EMAIL PROTECTED] > > > >>>>> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > >>>>> > > > >>>> > > > >>>> _______________________________________________ > > > >>>> Sip-implementors mailing list > > > >>>> [EMAIL PROTECTED] > > > >>>> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > >>> > > > >>> <host2-capture> > > > > > > > > > > > > > > _______________________________________________ > > Sip-implementors mailing list > > [EMAIL PROTECTED] > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
