On Mon, Sep 26, 2016 at 05:18:32PM +0530, Infinicalls Infinicalls wrote: The problem you have is that a lookup() will succeed on host1 when a UAC is registered to host2 (but stateful firewalls/NAT prohibit traffic from ipadresses other than host2). You can either figure out which host was used to register by looking at the socket value in the location table (using sqlops/avp_db_query) and send the INVITE to the other host if socket doesn't contain a local ipadress (by simply setting $rd to the other host and setting $du to null) or just wait for a failure route (which adds a delay) to trigger and send the invite to the other host (again setting $du to null and $rd to the other host).

On Thu, Sep 29, 2016 at 01:53:14PM +0530, Infinicalls Infinicalls wrote: In that case there is no direct way to get the external ip as far as I know. As far as location is concerned that information is lost. You might want to look into the Path module to store information about the REGISTER (you might have to fake a Path header before save from available info during the REGISTER). It is the correct idea, but it might be a little bit fragile. There might be no response (in which case you get a local generated 408), but if a device is listening it might decide to send any 4/5/6xx code. You might want to take a look at you solution though. For example you might want to introduce edge proxies, clients connect with those directly, but they forward the requests to a (specific or loadbalanced) registrar (essentially the machines you have up and running now). These proxies insert Path information about themselves in any messages coming from the outside world (add_path_received()) , the registrar saves the Path info: modparam("registrar", "use_path", 1) modparam("registrar", "path_use_received", 1) Now any registrar looking at the shared location data knows which edge proxy to sent the request for the enduser to directly.

On Fri, Sep 30, 2016 at 09:08:50AM +0530, Infinicalls Infinicalls wrote: Looks similar to my own setup, which I posted here http://lists.sip-router.org/pipermail/sr-users/2016-August/094280.html Than a edge proxy setup will help, the config in them is static (and can be stateless). Dispatcher can distribute anyway you want, if you need to do maintenance/add more registrars you just edit dispatcher.list and reload them on the edge.