drdavedmin wrote:You have been very helpful and I really appreciate it. The subnet thing you mention is very likely the problem. My router was already using the 172. series of IP addresses, which the Ooma also uses. I can reset my router to use a 10. series or a 192. series. Would that be likely to cure the issue?
It's probably create more (routing) problem than it cures.
Ooma already use the subnet 172.27.35.n, Where n will be different on each device connect directly to it.
Then you can use 172.27.36.m for your router DHCP, or turn off DHCP and change the rourter to bridge mode, i.e. it's behave like a dump switch.
However, I'm agree that double NAT is better, and against using the router in 'bridge' mode since telo primary is a voip device and it is not a fully functional router. A chaining double NAT is not a problem, imho. a branching triple NAT will be if there is no server acting as bridge.
The wording 'bridge' mode on most router is very misleading. it should be 'switch' mode because a network bridge is a hub where different subnets interconnect, and traffics between different subnets will be alowed/denied depending of the policies setup by admins.