Show Posts
1
SIP On Mitel / All VOIP Devices Lose Network Connection
« on: October 10, 2019, 05:28:59 PM »
What variable -- active or passive -- on a DHCP based network will cause all Mitel VOIP handsets to:
Background: About two months ago and over five months of flawless production service, we had all Mitel 53xx phones on a client network go offline and start cycling through the power off, Waiting for LLDP, software version, Waiting for DHCP, DHCP: Discovery screens repeatedly. This issue occurs intermittently throughout the week and normally between 16:00 - 17:00 during the business day. There could be no DT for 4 / 5 days in a week. Or, the issue will manifest 4/5 days of the week.
DHCP is handled via the environment's router and we've successfully tested separate networks managed by the same router with no issues while the outage is occurring on the site's primary network.
While these Mitel 53xx (5320 for instance) handsets are provided with a local IP address, they connect up with the client's remote, cloud-based VOIP service provider.
We have worked with both the VOIP service provider as well as the router support group to verify settings, observe inbound DHCP packet traffic during outages, etc. Nothing specific sticks out. We have assigned static IP addresses to test phones as with no change in behavior during a given outage. Unfortunately, the phones simply will not connect up with the network. W/o fail, the VOIP phones will regain connectivity at some point during the evening hours.
We have been working to identify the issue -- likely something on the network or w/in the supporting switches which is actively or passively interfering with the Mitel phones.
There is no VLAN configured to be used with the VOIP phones. There are a total of 157 devices on the network.
The supporting switches are old with firmware that's ~10 years in age (inherited this environment); the switches do not retain settings when reset or power cycled. These are known issues. This client's IT hardware budget is challenged and challenging.
Any / all assistance or ideas are welcome.
Thank you!
- Lose network connectivity and drop active calls.
- Repeatedly cycle through the typical screens as if the phone was just connected to a live POE and network port.
- Not respond to actual power cycling, DHCP lease revocation and renewals or POE switch resets / restarts.
- Recover connectivity w/in a time band ranging from minutes to several hours.
Background: About two months ago and over five months of flawless production service, we had all Mitel 53xx phones on a client network go offline and start cycling through the power off, Waiting for LLDP, software version, Waiting for DHCP, DHCP: Discovery screens repeatedly. This issue occurs intermittently throughout the week and normally between 16:00 - 17:00 during the business day. There could be no DT for 4 / 5 days in a week. Or, the issue will manifest 4/5 days of the week.
DHCP is handled via the environment's router and we've successfully tested separate networks managed by the same router with no issues while the outage is occurring on the site's primary network.
While these Mitel 53xx (5320 for instance) handsets are provided with a local IP address, they connect up with the client's remote, cloud-based VOIP service provider.
We have worked with both the VOIP service provider as well as the router support group to verify settings, observe inbound DHCP packet traffic during outages, etc. Nothing specific sticks out. We have assigned static IP addresses to test phones as with no change in behavior during a given outage. Unfortunately, the phones simply will not connect up with the network. W/o fail, the VOIP phones will regain connectivity at some point during the evening hours.
We have been working to identify the issue -- likely something on the network or w/in the supporting switches which is actively or passively interfering with the Mitel phones.
There is no VLAN configured to be used with the VOIP phones. There are a total of 157 devices on the network.
The supporting switches are old with firmware that's ~10 years in age (inherited this environment); the switches do not retain settings when reset or power cycled. These are known issues. This client's IT hardware budget is challenged and challenging.
Any / all assistance or ideas are welcome.
Thank you!