Hi Alexey - thanks for responding. I've seen past reports where NAT was causing this type of problem. I tried your suggestion but, along with other tests such as forcing fix_nated_register() or fix_nated_contact() on all messages, and after trying Stas' suggestion, it still doesn't work for me. I believe that I've followed the tutorials correctly but, as per another post of mine, there are issues with the 3.0 tutorial scripts being out of date - so maybe the problem lies somewhere in how I've tried to fix the script errors for 3.0.2?
It's very frustrating because I can look at the "location" table in MySQL and see the information being correctly stored, it just appears that for some reason when it looks up and retrieves the information it doesn't recognise that the destination retrieved is a WebSocket and so tries to treat it as a FQDN - or at least that's what it seems to be saying to me. cheers, Mark On Fri, 17 Jul 2020 at 07:07, Alexey Vasilyev <alexei.vasil...@gmail.com> wrote: > Hi Mark, > > try this: > > if (nat_uac_test("123")) { > if (is_method("REGISTER")) { > fix_nated_register(); > } else { > fix_nated_contact(); > } > } > > > > ----- > --- > Alexey Vasilyev > -- > Sent from: > http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users