For the benefit of anyone else looking at this thread later and needing to fight with a double nat'd environment, an epilogue: the configuration change needed to make Anveo work for me, also led to a double nat which broke my Tomato Router's ability to handle NAT Loopback on its own--it could no longer see the public IP address. As a result, the extensions became unable to dial each other, and all soft phones configured using my home network's FQDN, stopped working (natively) in my home network. I managed to fix these problems by manually adding two PREROUTING rules to my Tomato Router (using Tools-->System Commands). The rules that needed to be added looked like this:
iptables -t nat -A PREROUTING -i MyLANInterface -s LocalNetworkCDR -d MyPubIPCDR -p udp -m udp --dport 5060 -j DNAT --to-destination MyPrivIPofPBX
iptables -t nat -A PREROUTING -i MyLANInterface -s LocalNetworkCDR -d MyPubIPCDR -p udp -m udp --dport 5060 -j DNAT --to-destination MyPrivIPofPBX
Note: For FreshTomato, MyLANInterface is br0 (& no rule needed for wireless LAN interface called eth1).
@kenn10: As a non Tomato user who seems to know a lot about it, do you have any idea why these commands won't survive a reboot when I add them to the Firewall, Initialization, or WanUP sections of the Administration-->Scripts page?
iptables -t nat -A PREROUTING -i MyLANInterface -s LocalNetworkCDR -d MyPubIPCDR -p udp -m udp --dport 5060 -j DNAT --to-destination MyPrivIPofPBX
iptables -t nat -A PREROUTING -i MyLANInterface -s LocalNetworkCDR -d MyPubIPCDR -p udp -m udp --dport 5060 -j DNAT --to-destination MyPrivIPofPBX
Note: For FreshTomato, MyLANInterface is br0 (& no rule needed for wireless LAN interface called eth1).
@kenn10: As a non Tomato user who seems to know a lot about it, do you have any idea why these commands won't survive a reboot when I add them to the Firewall, Initialization, or WanUP sections of the Administration-->Scripts page?