[OpenSIPS-Users] Registrar+TLS+NAT question (OpenSIPS 3.0.1)
bogdan at opensips.org
Mon Jun 22 17:27:00 EST 2020
If you do an xlog on $fs after the lookup, what do you see there ?
OpenSIPS Founder and Developer
On 6/16/20 4:37 PM, Pete Kelly wrote:
> I am running a Registrar in a natted location (AWS) which is currently
> accessed via a tls socket.
> The listen parameter for the tls socket uses an alias to set the
> publicly advertised address, along the lines of:
> listen=tls:188.8.131.52:5061 <http://184.108.40.206:5061> AS
> tls:220.127.116.11:5061 <http://18.104.22.168:5061>
> however this public alias is also being set as the Socket when the
> AOR is stored in the usrloc module.
> "Socket": "tls:22.214.171.124:5061 <http://126.96.36.199:5061>"
> When I then do a lookup() on a registered user, it is failing to route
> as I believe the socket is being set to the public alias. It was
> working fine when there was no TLS involved.
> Is there an obvious way I can try to fix this? (I've tried
> using force_send_socket(tls:188.8.131.52:5061 <http://184.108.40.206:5061>)
> after the lookup, but that isn't helping either)
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users