Status: Accepted
Owner: jean.deruelle
Labels: Type-Defect Priority-Medium Component-JAIN-SIP-Javascript
Roadmap-Fix
New issue 35 by jean.deruelle: Interoperability Issues with reSIProcate
http://code.google.com/p/jain-sip/issues/detail?id=35
1. a user can't register with reSIProcate with patch for SIP Over
WebSockets from SIPML5 because reSIProcate sends back the response to the
REGISTER via TCP port 5060. I believe it does that because it does not know
the port it should use.
using rport= in the Via fixes it (even though reSIProcate shouldn't care
because it is ovr TCP and should reuse the Connection)
2. After the rport fix, the client crashes with the errors below.
SIP message sent: REGISTER sip:robotics.net SIP/2.0
Call-ID: 1352416918007
CSeq: 1 REGISTER
From: <sip:[email protected]>;tag=1352416918018
To: <sip:[email protected]>
Via: SIP/2.0/WS Pof71HhIxUut.invalid;branch=z9hG4bK1352416917943;rport
Max-Forwards: 70
Expires: 3600
User-Agent: MobicentsWebRTCPhone
Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER
Contact: <sip:[email protected];transport=ws>
Content-Length: 0
jain-sip.js:20682
StringMsgParser:parseSIPMessagebyte(): catched exception:TypeError: Cannot
call method 'charCodeAt' of undefined jain-sip.js:11994
Uncaught TypeError: Cannot call method 'getContentLength' of null
jain-sip.js:15406
