On Wed, Dec 20, 2017 at 12:25:24PM +0000, Phil Reynolds wrote: > On Tue, 19 Dec 2017 18:22:47 +0000 > Phil Reynolds <phil-debian@tinsleyviaduct.com> wrote: > > If I set up Zoiper to use the FQDN of the Asterisk box, it connects > > just fine when I am not at home. However, when I am at home, it still > > uses the public IP address (192.0.2.51) of the Asterisk box, which, > > because it can see the phone directly, then responds using its own > > private address (192.168.0.4) - this causes Zoiper to fail to > > register. (it is clear from a tcpdump that this is happening) > > > > At no point does the router get involved in the communication between > > the phone and the Asterisk box. To do so might make things easier, or > > could just add an unnecessary layer of complexity. > > > > The answer to the problem could lie in several places: > > > > - If I could persuade the Asterisk box to respond on its public > > address rather than its private one, that would probably work. > > ... and, by adding two bindaddrs to the iax.conf, I have made this > happen. It no longer listens on 192.168.0.4, and my Android phone now > registers with it even when I'm at home, with no fiddling with anything > else. > > Obviously, if I ever did need IAX on the local IPv4, I would have to > reopen this, so by no means do I consider this a permanent solution. > However, at present I can work with it. If some other solution (other > than the pinnacle, IPv6-enabled Zoiper) can be found, that would be > even better. One potential solution would be to split your DNS so that hostnames resolve to public addresses for external queries, but private addresses for internal queries. I doubt dnsmasq can do this though, so you might have to look into setting up a "real" DNS server. Cheers, Tom -- knghtbrd: there may be no spoon, but can you spot the vulnerability in eye_render_shiny_object.c? -- rcw
Attachment:
signature.asc
Description: Digital signature