Hi, Bertrand!

I believe the problem is the order of the Route headers generated by the Application SRV. Can you also post the INVITE sent by OpenSIPS to the Application SRV?

Best regards,
Răzvan

On 2/20/20 7:11 PM, Bertrand Gaudin wrote:
Hi,

I'm quite new to opensips and for a poc , I've built an Opensips gateway with 
RTP-Engine module as webRTC gateway.
Client -(wss - public)->  R-proxy -(priv-wss)->  Opensips GW - (priv SIP/RTP)-> 
 Application srv
It works fine with a basic dialin from the webrtc client and this even if the 
client is behind a NAT...  but now I've some difficulties when the called part 
(an application server) is sending a ReInvite to the Calling Part

When the application server is sending back a ReInvite to the Opensips GW, The 
Invite is sent to the proxy through SIP while wss transport is expected.
ReInvite received by  Opensips:
     Message Header
         Via: SIP/2.0/UDP 
10.102.33.101;branch=z9hG4bK-20aa47ca8d2e4c7680cc967998c2f62f
         Supported: timer
         To: <sip:[email protected]>;tag=roj765mrvt
         From: 
<sip:[email protected]>;tag=10.102.33.155060+1+5750674+191dbe66
         Call-ID: cif3q52e3pfr1achul6q
         [Generated Call-ID: cif3q52e3pfr1achul6q]
         CSeq: 1 INVITE
         Contact: <sip:10.102.33.101>
         Route: <sip:10.108.1.11:443;transport=wss;r2=on;lr>
         Route: <sip:10.108.1.11;r2=on;lr>
         Allow: INVITE,ACK,BYE,OPTIONS,CANCEL,INFO,PRACK,UPDATE
         Session-Expires: 36000;refresher=uac
         Content-Type: application/sdp
         Content-Length: 231
     Message Body

ReInvite sent by OpenSIPS to the R-proxy through UDP/SIP while wss transport is 
expected.
User Datagram Protocol, Src Port: 5060, Dst Port: 60534
Session Initiation Protocol (INVITE)
     Request-Line: INVITE sip:[email protected]:60534;transport=ws;ob SIP/2.0
     Message Header
         Max-Forwards: 10
         Record-Route: <sip:10.108.1.11;lr>
         Via: SIP/2.0/UDP 10.108.1.11:5060;branch=z9hG4bK456c.2e6bb331.0
         Via: SIP/2.0/UDP 
10.102.33.101;branch=z9hG4bK-20aa47ca8d2e4c7680cc967998c2f62f
         Supported: timer
         To: <sip:[email protected]>;tag=roj765mrvt
         From: 
<sip:[email protected]>;tag=10.102.33.155060+1+5750674+191dbe66
         Call-ID: cif3q52e3pfr1achul6q
         [Generated Call-ID: cif3q52e3pfr1achul6q]
         CSeq: 1 INVITE
         Contact: <sip:10.102.33.101:5060>
         Allow: INVITE,ACK,BYE,OPTIONS,CANCEL,INFO,PRACK,UPDATE
         Session-Expires: 36000;refresher=uac
         Content-Type: application/sdp
         Content-Length: 581
     Message Body

Again from dialin Opensips is correctly receiving WSS messages on the WSS 
listener (here, 10.108.1.11:443) and the OK is correctly sent to the calling 
part with wss.
Any idea? Something wrong with this route (Route: 
<sip:10.108.1.11:443;transport=wss;r2=on;lr>)? Any help is welcome.

Thx in advance,
Bertrand Gaudin


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Răzvan Crainea
OpenSIPS Core Developer
  http://www.opensips-solutions.com

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to