Le 21/12/2017 à 01:48, Phil Reynolds a écrit :
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.How does the private client know that the public server address is reachable directly on the LAN an not through the router ?That I couldn't say, but it's plainly the case.
How are TCP/IP parameters configured on the client ? Could you show its routing table ?
Aren't you in control of the router configuration and which IPv6 DNS servers are advertised in the RAs it sends (radvd ?), and of these servers behaviour ?- If I could get the phone to pick up the private address of the Asterisk box rather than the public one, that would probably work. I have tried setting up to do this with dnsmasq, but the IPv6 settings for DNS cause this to be overridden. If I could somehow change the priority of this on the phone, it would help.All the IPv4 and IPv6 nameservers used by the client must resolve the name into the private address. If they also serve the public zone, you must set up "split DNS" to server different versions for private and public clients.Unfortunately I have found no way to override the radvd-provided DNS server addresses - otherwise I would have done this.
Just another thought : isn't it possible to set up Asterisk to listen explicitly on both the private and public IPv4 addresses instead of any local address, so that it opens two separate sockets ? This way I think it would reply with the proper source address.