This one has me stumped and I already have Mitel support involved and so far we have not isolated the issue.
This is more of a hail mary as some of you guys have seen some strange s**t and this definitely qualifies
Hardware specs
- Multi-instance MCD server running 7.1
- MBG for SIP trunking and Teleworker gateway 8.1.26
- Dedicated 100Mb fiber internet at main site
Remote site
- Basic internet, specs unknown
- 10 X 5320e phones in teleworker mode
Symptoms
- Every phone resets after 4 hours
- Phones are not on the same schedule, any random phone might reboot within a 30 minute window but individually, every 4 hours like clockwork
- manually resetting a phone starts the timer again for that phone
- When the phone fails, the display indicates "Contacting Server" for anywhere from 1 to 15 minutes. Varies by instance
- Holding down the * (Star) key while in the Contacting Server state reveals the correct TW server address
- Phones will recover on their own but only after some time. Phones will recover immediately if rebooted manually
- It does not matter if the phone is in use or not, the phone will reset at 4 hours.
Troubleshooting steps
- Phones have been statically assigned to avoid DHCP issues
- A TW set was set up at a different location without issues
- The functional TW set was brought to site and it started rebooting the same as the others
- IT support has removed the firewall
- IT support indicates that there are no ICMP redirects configured on the site
- IT support has the network configured as a flat lan with only NAT in place before the internet
- The IP Phone Analyser has been deployed at the site and logs provided to Mitel
- Tug logs and MCD maintenance logs have been provided to Mitel
Steps planned to be taken
- Take a LTE wireless modem to site to connect a phone to the internet via a completely different service
- Pray, offer sacrifices, hop on one foot while spinning in place, etc
If you've read this far, thank you. Any suggestions?
**********************************************
What's most important is that you realise ... There is no spoon.
This is more of a hail mary as some of you guys have seen some strange s**t and this definitely qualifies
Hardware specs
- Multi-instance MCD server running 7.1
- MBG for SIP trunking and Teleworker gateway 8.1.26
- Dedicated 100Mb fiber internet at main site
Remote site
- Basic internet, specs unknown
- 10 X 5320e phones in teleworker mode
Symptoms
- Every phone resets after 4 hours
- Phones are not on the same schedule, any random phone might reboot within a 30 minute window but individually, every 4 hours like clockwork
- manually resetting a phone starts the timer again for that phone
- When the phone fails, the display indicates "Contacting Server" for anywhere from 1 to 15 minutes. Varies by instance
- Holding down the * (Star) key while in the Contacting Server state reveals the correct TW server address
- Phones will recover on their own but only after some time. Phones will recover immediately if rebooted manually
- It does not matter if the phone is in use or not, the phone will reset at 4 hours.
Troubleshooting steps
- Phones have been statically assigned to avoid DHCP issues
- A TW set was set up at a different location without issues
- The functional TW set was brought to site and it started rebooting the same as the others
- IT support has removed the firewall
- IT support indicates that there are no ICMP redirects configured on the site
- IT support has the network configured as a flat lan with only NAT in place before the internet
- The IP Phone Analyser has been deployed at the site and logs provided to Mitel
- Tug logs and MCD maintenance logs have been provided to Mitel
Steps planned to be taken
- Take a LTE wireless modem to site to connect a phone to the internet via a completely different service
- Pray, offer sacrifices, hop on one foot while spinning in place, etc
If you've read this far, thank you. Any suggestions?
**********************************************
What's most important is that you realise ... There is no spoon.