Quote Originally Posted by VOIPoTim View Post
The devices re-register every few minutes, but sometimes if an ISP renews the IP or something along those lines the router will "close" the NAT pinhole basically preventing two way communication where our packets don't get to it.

That's why sometimes a reboot is needed.

Not ideal, but it's just the nature of NAT since if we can't get through to the device, we can't make it do anything.
Thanks, but that's irrelevant. my router's public IP is unchanged for months. Still is.
Quote Originally Posted by VOIPoTim View Post
With most routers port forwarding fixes this since all traffic on those ports get right through, but it depends a lot on the router.
Thanks, but that's irrelevant to this case too. Port forwarding off/on makes no difference. It has been on for a long time.

The fundamental problem here is that VoIPo pays no attention to ATAs that have inexplicably stopped re-registering. Takes no staff time to have server email customer a warning for the first n days. Or a robo-dial to the customer's number since it rolls to the failover.

Because the outgoing calls are OK, the customer (e.g., me) assumes all is OK.