Re: [OpenSIPS-Users] invalid contact wss

2023-02-04 Thread Robert Dyck
I forgot to mention that nat_uac_test should use at least flag 2. This insures that usrloc contains "Received". On Thursday, January 19, 2023 10:27:47 A.M. PST nutxase via Users wrote: > Hi guys > > So i notice when i register a WSS client to opensips the contact shows > something like

Re: [OpenSIPS-Users] invalid contact wss

2023-02-04 Thread Robert Dyck
Do you have opensips-cli setup? If so, do "mi ul_dump". Look for your "invalid" contact. Your should have a line like "Received": "sip:1.2.3.4:60310;transport=wss", The IP address should be routable. On Thursday, January 19, 2023 10:27:47 A.M. PST nutxase via Users wrote: > Hi guys > > So i

Re: [OpenSIPS-Users] invalid contact wss

2023-02-04 Thread HS
Nutxcase, With ref to invalid wss contact - can you confirm Opensips version please? Thanks. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] invalid contact wss

2023-02-02 Thread Răzvan Crainea
Make sure you fix the WSS client's contact using fix_nated_contact(); Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 1/19/23 20:27, nutxase via Users wrote: Hi guys So i notice when i register a WSS client to opensips the contact shows something

[OpenSIPS-Users] invalid contact wss

2023-01-19 Thread nutxase via Users
Hi guys So i notice when i register a WSS client to opensips the contact shows something like Contact": "sip:62dntqm1@rwtjcrhyne3j.invalid;transport=wss", which causes inbound calls to not route and show 476 unresolvable destination. any tips of where to look here? Sent with [Proton