[OpenSIPS-Users] mid-registrar and WSS

Esty, Ryan ryan.esty at necect.com
Wed Mar 14 09:27:30 EDT 2018


Hi opensips users,

I have a couple of questions and I'm hoping someone can point me in the right direction.

We have a SIP PBX that doesn't do WSS for example using sipml5. I'm trying to put opensips in the middle of the SIP PBX and the WSS client with limited success using mid-registrar in opensips 2.3. If I don't try to pass the registration through and just use opensips as my SIP server the WSS client will register and calls can be made. If I do put in the mid-registrar and pass through the registration to the SIP PBX the SIP PBX will register the phone and pass back the 200 OK the client gets a message back but doesn't think it is for him because I'm assuming it is missing the VIA. On a successful registration the client will see the VIA on the unsuccessful registration the client doesn't see the VIA.


My first question is am I using the mid-registrar as designed I'm trying to set it up as contact mirroring (mode 0)? If I did pick the correct method why is my VIA disappearing and can I get it back? Someone on the list mentioned this https://blog.opensips.org/2016/12/13/how-to-proxy-sip-registrations and I will try it soon but it seemed the mid-registrar which I don't think was released yet was supposed to automatically do this.

This is the debug output when the registration is failed:
SEND: REGISTER sip:192.168.40.175 SIP/2.0
Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bKd7RGgr1eBtcOk2yUuIUuyvIqWk3G3Or0;rport
From: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>;tag=T9XcAa1Am5fIDrtIo68Z
To: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>
Contact: "Skwisgaar Skwigelf"<sips:312 at df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=wss>;expires=200;click2call=no;+g.oma.sip-im;+audio;language="en,fr"
Call-ID: 766574bd-8060-562d-1f67-24975848739c
CSeq: 5334 REGISTER
Content-Length: 0
Route: <sip:192.168.40.175:5061;lr;sipml5-outbound;transport=tls>
Max-Forwards: 70
User-Agent: IM-client/OMA1.0 sipML5-v1.2016.03.04
Organization: Doubango Telecom
Supported: path


SIPml-api.js?svn=252:1 ==session event = connecting
SIPml-api.js?svn=252:1 ==session event = sent_request
SIPml-api.js?svn=252:1 __tsip_transport_ws_onmessage
SIPml-api.js?svn=252:1 recv=SIP/2.0 200 OK
From: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>;tag=T9XcAa1Am5fIDrtIo68Z
To: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>;tag=83a00482-48f7-4f78-ab314b6aacadc545
Contact: <sips:312 at df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=wss>;expires=200
Call-ID: 766574bd-8060-562d-1f67-24975848739c
CSeq: 5334 REGISTER
Content-Length: 0
Server: Sphericall/9.1.0 Build/669
Allow: INVITE,ACK,CANCEL,OPTIONS,REFER,BYE,REGISTER,SUBSCRIBE,NOTIFY,UPDATE,PRACK,MESSAGE,INFO
Allow-Events: message-summary,presence

This is the debug output when the registration is successful:
SEND: REGISTER sip:192.168.40.175 SIP/2.0
Via: SIP/2.0/WSS df7jal23ls0d.invalid;branch=z9hG4bKLpgkzXTPZl5D5ghXuZ1vmNZXUn9nHkMr;rport
From: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>;tag=RyaJ7SLKEeeTS8r9v0BX
To: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>
Contact: "Skwisgaar Skwigelf"<sips:312 at df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=wss>;expires=200;click2call=no;+g.oma.sip-im;+audio;language="en,fr"
Call-ID: 6e7fe61e-a51f-96cf-a9a0-e3c3785259b9
CSeq: 7252 REGISTER
Content-Length: 0
Route: <sip:192.168.40.175:5061;lr;sipml5-outbound;transport=tls>
Max-Forwards: 70
User-Agent: IM-client/OMA1.0 sipML5-v1.2016.03.04
Organization: Doubango Telecom
Supported: path


SIPml-api.js?svn=252:1 ==session event = connecting
SIPml-api.js?svn=252:1 __tsip_transport_ws_onmessage
SIPml-api.js?svn=252:1 recv=SIP/2.0 200 OK
Via: SIP/2.0/WSS df7jal23ls0d.invalid;rport=60161;received=172.25.111.53;branch=z9hG4bKLpgkzXTPZl5D5ghXuZ1vmNZXUn9nHkMr
From: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>;tag=RyaJ7SLKEeeTS8r9v0BX
To: "Skwisgaar Skwigelf"<sip:312 at 192.168.40.175>;tag=54638b9941aeeb05912f3f3563e30b77.7a8c
Contact: <sips:312 at df7jal23ls0d.invalid;rtcweb-breaker=yes;transport=wss>;expires=200;received="sip:172.25.111.53:60161;transport=WSS"
Call-ID: 6e7fe61e-a51f-96cf-a9a0-e3c3785259b9
CSeq: 7252 REGISTER
Content-Length: 0
Server: OpenSIPS (2.3.3 (x86_64/linux))

Ryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180314/f221286d/attachment.html>


More information about the Users mailing list