I see the equipment at 122.169.243.35 is not forwarding the response. One problem I can see is that the Via's in the 200 ok response (frame 114) don't match with those in the INVITEs in frames 18 and 21.
Actually. this is a problem with all the responses generated by 59.93.52.43. The UA has stripped all the ibmsid parameters of the Via. Via's can be appended (e.g. rport and received) but they should never be truncated or altered in any other way. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 11 June 2008 09:58 To: Attila Sipos; [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request Hi Attila, Could you please tell me what's going wrong in the above attached ethereal trace .The case is simple invite establishment. But the call did not establish . Thanks & Regards Rajeswari.R -----Original Message----- From: Attila Sipos [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 1:56 PM To: Routhu, Rajeswari (Cognizant); [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request I looked in ethereal/wireshark. I "counted" the number of bytes in the body (I selected "View" then "Packet Bytes", then noted the start and finish of the body. start at 0258 and finish at 0394 0394 - 0258 = 13C - which is 316 in decimal) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 11 June 2008 09:19 To: Attila Sipos; [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request Hi Attila, Thanks for the response. I have doubt that how did u calculate the length. Thanks & Regards Rajeswari.R -----Original Message----- From: Attila Sipos [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 12:54 PM To: Routhu, Rajeswari (Cognizant); [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request 1. the content length doesn't match the length in the body. 2. the "Incomplete body" text means that it's expecting more bytes than are in the body so, yes, we have found the problem. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 11 June 2008 08:10 To: Attila Sipos; [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request I also feel the same thing . Is that the confirmed reason. -----Original Message----- From: Attila Sipos [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 12:27 PM To: Routhu, Rajeswari (Cognizant); [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request Isn't the Content-Length of the request wrong? The SIP message says "Content-Length: 317", but the message body is 316 Regards, Attila -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 11 June 2008 07:48 To: Attila Sipos; [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request Sorry for that .Please find the attachment. It's actually an ethereal trace file. I renamed it to txt file. Thanks & Regards Rajeswari.R -----Original Message----- From: Attila Sipos [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 11:57 AM To: Routhu, Rajeswari (Cognizant); [email protected] Subject: RE: [Sip-implementors] REG: 400 bad request there was no trace. Maybe you can't add attach it. Can you put the SIP messages into e-mail body text? Regards, Attila -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 11 June 2008 05:24 To: [email protected] Subject: [Sip-implementors] REG: 400 bad request Hi all, I have sent a request over wi-Fi from one sip client to another . For this iam getting 400 Bad request.Incomplete body. Iam attaching the ethereal trace. Please suggest me what's going wrong with the request.s Thanks & Regards Rajeswari.R This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
