search

kameldjabri / webrtc2sip

Automatically exported from code.google.com/p/webrtc2sip
1 stars 0 forks source link

Content-Lenght is NOT required in SIP over WebSocket #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
http://tools.ietf.org/html/draft-ietf-sipcore-sip-websocket-04#section-5.1

------------------
5.1.  General

Each SIP message MUST be carried within a single WebSocket message,
and a WebSocket message MUST NOT contain more than one SIP message.
Because the WebSocket transport preserves message boundaries, the use
of the Content-Length header in SIP messages is optional when they
are transported using the WebSocket sub-protocol.
------------------

However webrtc2sip complains if a SIP request over WebSocket has no 
Content-Lenght:

-------------
WARNING | 20121017-110236.991 | repro | RESIP:TRANSPORT | 140109811562240 | 
ConnectionBase.cxx:320 | Malformed Content-Length in connection-based 
transport. Not much we can do to fix this. SipMessage::Exception Missing header 
Content-Length @ SipMessage.cxx:1371
-------------

Original issue reported on code.google.com by i...@aliax.net on 17 Oct 2012 at 4:11

GoogleCodeExporter commented 9 years ago 
Fix by SVN r21.

Original comment by boss...@yahoo.fr on 3 Dec 2012 at 7:24