I have opened the tcp/udp ports from the engineering guides, what I have found on here, etc. Gave the MiVoice 250 a NAT IP that is externally reachable, and that's about it.
The one has been in use long before it became my problem has the NAT IP set in:
System > Devices and feature codes > IP connections > Local > Processor Module > NAT IP Address
and in System > IP Settings > System NAT IP Address.
I don't think that there is any port forwarding configured. No MBG, don't know if I need one or not. I have 13 MiVoice 250 systems across 12 offices.
OK, I am assuming you have a 1:1 NAT through a firewall with the ports listed allowed... the MiVO 250 has a public IP address that is dedicated for it's use exclusively. Good way to go if you have the right gear.
Port forwarding and settings won't cause phones to momentarily lose connection to the phone system, they either work or they don't... But that is what is happening, the phones are losing their connection to the phone system long enough to cause a soft reboot of the device so it can reconnect (a second or two).
It sounds like this is multiple phones exhibiting the behavior from different locations? Are they all connecting back to the same MiVO, or different ones? Look for the commonality... I am going to assume that they all report back to the same MiVO 250, but from different locations such as home offices and have different local networking hardware at the remote sites, eliminating the far end as the issue.
If they are all reporting back to the same MiVO, the commonality here is the Internet connection and router/firewall (and possibly any other local equipment you have).
The most likely causes here are insufficient bandwidth on the internet connection, a firewall/router that doesn't have enough power to deal with the workload, SPI (Stateful Packet Inspection) or other firewall feature is enabled and causing the problem, or much less likely are the MiVO 250 doesn't have enough resources (check RAM and CPU usage graphs) or there is an internal network issue.
