[OpenSIPS-Users] Path support workaround

Thu Jun 15 13:38:13 UTC 2023

i added it and i am still getting

Jun 15 14:36:31 so-sbc-02 opensips: Jun 15 14:36:31 [26314] ERROR:proto_wss:ws_connect: cannot complete WebSocket handshake
Jun 15 14:36:31 so-sbc-02 opensips: Jun 15 14:36:31 [26314] ERROR:proto_wss:proto_wss_send: connect failed
Jun 15 14:36:31 so-sbc-02 opensips: Jun 15 14:36:31 [26314] ERROR:tm:msg_send: send() to xxxxxx:443 for proto wss/6 failedJun 15 14:36:31 so-sbc-02 opensips: Jun 15 14:36:31 [26314] ERROR:tm:t_forward_nonack: sending request failed

Sent with [Proton Mail](https://proton.me/) secure email.

------- Original Message -------
On Thursday, June 15th, 2023 at 2:34 PM, nutxase <nutxase at proton.me> wrote:

> I dont have it added
> my setup is
>
> WSS client on mobile phone --- opensips --mid_registrar -- asterisk
>
> loadmodule "mid_registrar.so"
> modparam("mid_registrar", "mode", 2) /* 1 = mirror / 1 = ct / 2 = AoR */
> modparam("mid_registrar", "outgoing_expires", 180)
> modparam("mid_registrar", "min_expires", 60)
> modparam("mid_registrar", "max_expires", 180)
> modparam("mid_registrar", "max_contacts", 16)
> modparam("mid_registrar", "received_avp", "$avp(received)")modparam("mid_registrar", "pn_pnsreg_interval", 140)
>
> all works fine except the hangup does not work and call drops after 33 seconds
> do you think that setting is the fix?
>
> Sent with [Proton Mail](https://proton.me/) secure email.
>
> ------- Original Message -------
> On Thursday, June 15th, 2023 at 2:31 PM, Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:
>
>> It looks like your opensips is trying to perform a remote connect via WSS, which cannot work
>>
>> Are you using this
>> https://opensips.org/html/docs/modules/3.3.x/mid_registrar.html#param_tcp_persistent_flag
>> to prevent the TCP/WSS conn to be closed before the expiration of the registration ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>> https://www.opensips-solutions.com
>>
>> https://www.siphub.com
>>
>> On 6/13/23 3:35 PM, nutxase wrote:
>>
>>> So in netstat i dont see any connections to my public ip(uac client)
>>> but in the log i see
>>>
>>> RROR:tls_wolfssl:_wolfssl_tls_connect: New TLS connection to xxxx:443 failed
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8048]: ERROR:tls_wolfssl:_wolfssl_tls_connect: TLS connect error: -313, received alert fatal error
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8048]: ERROR:proto_wss:ws_client_handshake: cannot start handshake
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8048]: ERROR:proto_wss:ws_connect: cannot complete WebSocket handshake
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8048]: ERROR:proto_wss:proto_wss_send: connect failed
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8048]: ERROR:core:msg_send: send() to xxxx:443 for proto wss/6 failed
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8050]: ERROR:tls_wolfssl:_wolfssl_tls_connect: New TLS connection to xxx:443 failed
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8050]: ERROR:tls_wolfssl:_wolfssl_tls_connect: TLS connect error: -313, received alert fatal error
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8050]: ERROR:proto_wss:ws_client_handshake: cannot start handshake
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8050]: ERROR:proto_wss:ws_connect: cannot complete WebSocket handshake
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8050]: ERROR:proto_wss:proto_wss_send: connect failed
>>> Jun 13 13:33:08 so-sbc-02 /usr/local/sbin/opensips[8050]: ERROR:core:msg_send: send() to xxxx:443 for proto wss/6 failed
>>> Jun 13 13:33:09 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:tls_wolfssl:_wolfssl_tls_connect: New TLS connection to xxx:443 failed
>>> Jun 13 13:33:09 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:tls_wolfssl:_wolfssl_tls_connect: TLS connect error: -313, received alert fatal error
>>> Jun 13 13:33:09 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:proto_wss:ws_client_handshake: cannot start handshake
>>> Jun 13 13:33:09 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:proto_wss:ws_connect: cannot complete WebSocket handshake
>>> Jun 13 13:33:09 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:proto_wss:proto_wss_send: connect failed
>>> Jun 13 13:33:09 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:core:msg_send: send() to xxxx:443 for proto wss/6 failed
>>> Jun 13 13:33:11 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:tls_wolfssl:_wolfssl_tls_connect: New TLS connection to xxxx:443 failed
>>> Jun 13 13:33:11 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:tls_wolfssl:_wolfssl_tls_connect: TLS connect error: -313, received alert fatal error
>>> Jun 13 13:33:11 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:proto_wss:ws_client_handshake: cannot start handshake
>>> Jun 13 13:33:11 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:proto_wss:ws_connect: cannot complete WebSocket handshake
>>> Jun 13 13:33:11 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:proto_wss:proto_wss_send: connect failed Jun 13 13:33:11 so-sbc-02 /usr/local/sbin/opensips[8047]: ERROR:core:msg_send: send() to xxxx:443 for proto wss/6 failed
>>>
>>> Sent with [Proton Mail](https://proton.me/) secure email.
>>>
>>> ------- Original Message -------
>>> On Tuesday, June 13th, 2023 at 12:41 PM, Bogdan-Andrei Iancu [<bogdan at opensips.org>](mailto:bogdan at opensips.org) wrote:
>>>
>>>> OK, so it looks like the target IP is a public valid one. Check with netstat if you have any ongoing TCP conns to that IP
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>> https://www.opensips-solutions.com
>>>>
>>>> https://www.siphub.com
>>>>
>>>> On 6/13/23 10:38 AM, nutxase wrote:
>>>>
>>>>> Hi Bogdan
>>>>>
>>>>> So the ip is the ip of the uac client (internet ip)and not sure how to check for any nat issues there? please help :)
>>>>> not sure exactly sure how it would be down as it is mid registrar looking up the location then establishing the call
>>>>>
>>>>> Sent with [Proton Mail](https://proton.me/) secure email.
>>>>>
>>>>> ------- Original Message -------
>>>>> On Tuesday, June 13th, 2023 at 7:02 AM, Bogdan-Andrei Iancu [<bogdan at opensips.org>](mailto:bogdan at opensips.org) wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The error you get from OpenSIPS is about its inability to send a message to a certain WSS destination. This may be because:
>>>>>> 1) the actual destination is wrong - you know the IP, check if it make sense, maybe there are some end-user nat issues
>>>>>> 2) as WSS is TCP based, the original connection is down and opensips is not able to create a new one from server side.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Bogdan-Andrei Iancu
>>>>>>
>>>>>> OpenSIPS Founder and Developer
>>>>>> https://www.opensips-solutions.com
>>>>>>
>>>>>> https://www.siphub.com
>>>>>>
>>>>>> On 6/12/23 7:17 PM, nutxase via Users wrote:
>>>>>>
>>>>>>> Hi Guys
>>>>>>>
>>>>>>> So i am using a wss client and sending registration via mid_registrar to asterisk(pjsip) and all works fine except on inbound calls we get a lot of errors and googling has pointed me to this link https://issues.asterisk.org/jira/browse/ASTERISK-28211
>>>>>>> here are the errors i get
>>>>>>>
>>>>>>> Jun 12 17:02:01 so-sbc-02 /usr/local/sbin/opensips[23379]: ERROR:nathelper:msg_send: send() to xxxxxx:32900 for proto wss/6 failed
>>>>>>> Jun 12 17:02:01 so-sbc-02 /usr/local/sbin/opensips[23379]: ERROR:nathelper:nh_timer: sip msg_send failed!
>>>>>>>
>>>>>>> my question is, does anyone have a work around for this? as currently inbound calls do not work properly :(
>>>>>>>
>>>>>>> Sent with [Proton Mail](https://proton.me/) secure email.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at lists.opensips.org
>>>>>>>
>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20230615/f1fb711d/attachment-0001.html>