[OpenSIPS-Users] Problem: Registration Proxy with WebRTC

[Dragomir Haralambiev]

Here is answer from JsSIP but I do not know how to setup Opensips:


=================== answer ===============
The error log does tell you what is happening:

```
JsSIP | SANITY CHECK | Via host in the response does not match UA Via host
value. Dropping the respons
```

Have a look at the chapter 18.1.2 from RFC 3261:

```

18.1.2 Receiving Responses

   When a response is received, the client transport examines the top
   Via header field value.  If the value of the "sent-by" parameter in
   that header field value does not correspond to a value that the
   client transport is configured to insert into requests, the response
   MUST be silently discarded.

```

The "sent-by" parameter in the response has been altered from the one sent
out from JsSIP. Your server is manipulating such a value and that makes the
response to be discardes as per RFC 3261.

2017-07-02 22:20 GMT+03:00 Dragomir Haralambiev <goup2010 at gmail.com>:

> Hello,
>
> I try to setup Registration proxy (opensips 2.3) like this article:
> https://blog.opensips.org/2016/12/13/how-to-proxy-sip-registrations/
>
> 1. When use Zoiper all is OK
> Zoiper <----> Opensips REGISTRATION Proxy <-----> SBC
>
> 2. I have problem when use WebRTC.
> (*Via sent-by in the response does not match UA Via host value. Dropping
> the response*):
>
> SIP.JS <----->Opensips REGISTRATION Proxy <-----> SBC
>
> Here is WebSocket text messages:
>
> REGISTER sip:<IP:Opensips> SIP/2.0
> Via: SIP/2.0/WSS 192.0.2.148;branch=z9hG4bK8881457
> Max-Forwards: 70
> To: "Tester" <sip:555999@<IP:Opensips>>
> From: "Tester" <sip:555999@<IP:Opensips>>;tag=u6aro6a8mj
> Call-ID: k5uhq12e1bb93rg9igvpvv
> CSeq: 83 REGISTER
> Contact: <sip:r0f6p7so at 192.0.2.148;transport=wss>;reg-id=1;+sip.
> instance="<urn:uuid:ed6914c3-65ee-4e9a-b6e8-3fcd74cb66ac>";expires=60
> Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
> Supported: path, gruu, outbound
> User-Agent: SIP.js/0.7.8
> Content-Length: 0
>
>
>
> sip-0.7.8.js:2900 Sun Jul 02 2017 18:41:19 GMT+0300 (FLE Daylight Time) |
> sip.transport | received WebSocket text message:
>
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/WSS 192.0.2.148:5060;rport=53162;received=<Sip.js_IP>;branch=
> z9hG4bK8881457
> From: "Tester" <sip:555999@<IP:Opensips>>;tag=u6aro6a8mj
> To: "Tester" <sip:555999@<IP:Opensips>>
> Call-ID: k5uhq12e1bb93rg9igvpvv
> CSeq: 83 REGISTER
> Contact: <sip:r0f6p7so@<Sip.js_IP>:53162;transport=wss>;reg-id=1;
> +sip.instance="<urn:uuid:ed6914c3-65ee-4e9a-b6e8-3fcd74cb66ac>";expires=60
> WWW-Authenticate: Digest realm="sbc.com", nonce="ee228f001f1459108000000
> c2916c1ef at sbc.com"
> Content-Length: 0
>
>
>
> sip-0.7.8.js:2900 Sun Jul 02 2017 18:41:19 GMT+0300 (FLE Daylight Time) |
> sip.sanitycheck | *Via sent-by in the response does not match UA Via host
> value. Dropping the response*
>
>
> Best regards,
> Drgagomir
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170705/353b005f/attachment.html>