Re: [OpenSIPS-Users] Path support workaround

2023-06-15 Thread nutxase via Users
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

Re: [OpenSIPS-Users] Path support workaround

2023-06-15 Thread nutxase via Users
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",

Re: [OpenSIPS-Users] Path support workaround

2023-06-15 Thread Bogdan-Andrei Iancu
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 ?

Re: [OpenSIPS-Users] Path support workaround

2023-06-13 Thread nutxase via Users
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 :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,

Re: [OpenSIPS-Users] Path support workaround

2023-06-13 Thread Bogdan-Andrei Iancu
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

Re: [OpenSIPS-Users] Path support workaround

2023-06-13 Thread nutxase via Users
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/)

Re: [OpenSIPS-Users] Path support workaround

2023-06-13 Thread Bogdan-Andrei Iancu
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

[OpenSIPS-Users] Path support workaround

2023-06-12 Thread nutxase via Users
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