problem when using webrtc2sip as a proxy about jssip HOT 12 CLOSED

@iwanbk, you can specifiy the full ws uri in the demo web. No need to modify the code for that.

Please, specify the full string of the ws uri within the demo web: ws://my.domain.com:4062

from jssip.

@jmillan
Hi, i modify the code because i thought it failed because jssip automatically convert ws://my.domain.com:4062 to ws://my.domain.com:4062/ (add a trailing slash).
And just realized that it still works with kamailio even with trailing slash.

Btw, have you tested jssip with webrtc2sip?

from jssip.

@iwanbk The URI ws://my.domain.com:4062/ is 100% valid, so if webrtc2sip fails to parse it there is a bug in webrtc2sip, not in JsSIP ;)

from jssip.

Closing the issue since it's not a bug in JsSIP but in a 3rd party server.

from jssip.

@ibc
Sorry if i was not clear.
Even with ws://my.domain.com:4062 (without trailing slash), it is not work.
You can see again my javascript console message, there is no trailing slash.

from jssip.

This is error message from webrtc2sip
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
WARNING | 20121017-110238.024 | 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

from jssip.

JsSIP does not add a Content-Length header since it's not mandatory (WebSocket it's a message boundary transport). See 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.

So it's a bug in webrtc2sip server.

from jssip.

Yeah,

As per section 5.1 in http://tools.ietf.org/html/draft-ietf-sipcore-sip-websocket-04, the Content-Length header in a SIP message is optional when using WebSocket as transport. It is hence a bug in webrtc2sip, which should respect a SIP message without such a header.

from jssip.

I've reported the bug in webrtc2sip server: http://code.google.com/p/webrtc2sip/issues/detail?id=5

Please follow it ;)

from jssip.

@jmillan Even if it's optional, does it hurt to send it? If it helps I'd be all for it.

from jssip.

JsSIP master now adds always a Content-Lenght header (regardless it's not mandatory). Let's make happy buggy servers from 3rd parties.

from jssip.

🍰

from jssip.