If I understand correctly Content-Length is the size of the SDP message, I have them here almost unaltered, unless the problem is with line feed/carriage return. I did wc and they match, humm not sure where to look. ------------------------------------------------------------------------ This one return "SIP/2.0 400 Content Length is Incorrect (359 vs 356)." ------------------------------------------------------------------------ Content-Length: 360. P-hint: Route[6]: mediaproxy . . v=0. o=- 7 2 IN IP4 192.168.101.239. s=CounterPath eyeBeam 1.5. c=IN IP4 10.0.4.210. t=0 0. m=audio 51090 RTP/AVP 0 8 18 101. a=alt:1 1 : 9xT8sdp8 dJNn6AL5 192.168.101.239 5992. a=fmtp:18 annexb=yes. a=fmtp:101 0-15. a=rtpmap:18 G729/8000. a=rtpmap:101 telephone-event/8000. a=sendrecv. a=x-rtp-session-id:6746FE4B967845A3BC3CE0528E9F9A0D. a=direction:active. ------------------------------------------------------------------------
------------------------------------------------------------------------ This one return "200 OK" ------------------------------------------------------------------------ Content-Length: 429. P-hint: Route[6]: mediaproxy . . v=0. o=- 6 2 IN IP4 10.0.1.71. s=CounterPath X-Lite 3.0. c=IN IP4 10.0.4.210. t=0 0. m=audio 51098 RTP/AVP 107 0 8 101. a=alt:1 4 : P2r8H0s1 PjFnvrZF 192.168.1.102 50514. a=alt:2 3 : Zg++GVqM zvF8qNdi 192.168.114.1 50514. a=alt:3 2 : aDT0P1g7 P6eCvs8N 192.168.146.1 50514. a=alt:4 1 : E0q9LRE/ m4a2BEWO 10.0.1.71 50514. a=fmtp:101 0-15. a=rtpmap:107 BV32/16000. a=rtpmap:101 telephone-event/8000. a=sendrecv. a=direction:active. ------------------------------------------------------------------------ ________________________________ From: [email protected] on behalf of Julien Chavanton Sent: Wed 29/07/2009 10:40 PM To: [email protected] Subject: [OpenSIPS-Users] SIP/2.0 400 Content Length is Incorrect Hi, I have this curious case where when sending call from Eyebeam we receive "SIP/2.0 400 Content Length is Incorrect" But this is only from one PC, another computer with Eyebeam does not face the same problem. I will investigate further on my side, but maybe someone as faced this before. Unfortunatly I have altered the data so it is not correct anyway : # U 1.1.1.1:40842 -> 3.3.3.3:5060 INVITE sip:[email protected] SIP/2.0. Via: SIP/2.0/UDP 1.1.1.1:40842;branch=z9hG4bK-d8754z-0978ed74e64c0d43-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:[email protected]:40842>. To: "1002123456789"<sip:[email protected]>. From: "test"<sip:[email protected]>;tag=524b8a00. Call-ID: Yzc0MmQxMzAyMjI5MDA0OGM5Y2VhYTZjZjQ2NjY5OTM.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1101w stamp 50331. Content-Length: 344. . v=0. o=- 7 2 IN IP4 1.1.1.1. s=CounterPath eyeBeam 1.5. c=IN IP4 1.1.1.1. t=0 0. m=audio 5992 RTP/AVP 0 8 18 101. a=alt:1 1 : 9xT8sdp8 dJNn6AL5 1.1.1.1 5992. a=fmtp:18 annexb=yes. a=fmtp:101 0-15. a=rtpmap:18 G729/8000. a=rtpmap:101 telephone-event/8000. a=sendrecv. a=x-rtp-session-id:6746FE4B967845A3BC3CE0528E9F9A0D. # U 2.2.2.2:5060 -> 3.3.3.3:5060 SIP/2.0 400 Content Length is Incorrect (359 vs 356).
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
