Show Posts
1
MiVoice Office 250/Mitel 5000 / Phone Hangs on "Contacting Server" - COMCAST?
« on: April 06, 2016, 09:48:24 AM »
Good morning!
We have the Mitel 5000 brain, with multiple 5340 IP phones off-site.
Most are in home offices around the city here – i.e. same ISP (TimeWarner).
One is in a home office hundreds of miles away in Atlanta, Georgia (Comcast). In late February the Comcast user returned to Georgia from a business trip up here (Rochester, NY) and called because neither her phone nor her VPN software were working anymore. Both had worked previously, and the VPN software continued to work everywhere except through her home connection.
We were on the cusp of installing a new firewall in her home office, so we ignored the issues for a week and installed the firewall. Firewall now works perfectly, however phone continues to hang on "contacting server".
Had the phone, cords and power brick all shipped back up here. Configured a new phone, power brick, lan cords, and took them off site and tested – phone works perfectly. Packed it up, shipped it to Atlanta, she connected to her network - no joy, same hang on "Contacting Server".
The Comcast modem is in virtual bridge mode, so they say it is doing absolutely nothing with the traffic. The firewall has a trusted port configured for phone traffic – problem occurs on that port. Also has a port configured wide open (DMZ) in case we need to test anything outside of firewall rules – problem occurs on that port as well.
I suspect the issue is the Comcast connection, particularly since the problem started prior to installing the new firewall, but I'm not sure how to check or test or even what language to use when calling their techs to troubleshoot...
Logs from the firewall:
networkd [eth2 (Trusted Phone)] Interface link status changed to down id="3100-002C"
networkd [eth2 (Trusted Phone)] Interface link status changed to up id="3100-002C"
networkd [eth2 (Trusted Phone)] Interface link status changed to down id="3100-002C"
networkd [eth2 (Trusted Phone)] Interface link status changed to up id="3100-002C"
dhcpd DHCPDISCOVER from 08:00:0f:5c:bd:96 via eth2 id="1600-0066"
dhcpd DHCPOFFER on 192.168.4.2 to 08:00:0f:5c:bd:96 via eth2 id="1600-0065"
dhcpd DHCPREQUEST for 192.168.4.2 (192.168.4.1) from 08:00:0f:5c:bd:96 via eth2 id="1600-0066"
10 minutes or so later, this sequence will repeat.
2016-04-06 09:46:17 dhcpd DHCPACK on 192.168.4.2 to 08:00:0f:5c:bd:96 via eth2 id="1600-0065"
We have the Mitel 5000 brain, with multiple 5340 IP phones off-site.
Most are in home offices around the city here – i.e. same ISP (TimeWarner).
One is in a home office hundreds of miles away in Atlanta, Georgia (Comcast). In late February the Comcast user returned to Georgia from a business trip up here (Rochester, NY) and called because neither her phone nor her VPN software were working anymore. Both had worked previously, and the VPN software continued to work everywhere except through her home connection.
We were on the cusp of installing a new firewall in her home office, so we ignored the issues for a week and installed the firewall. Firewall now works perfectly, however phone continues to hang on "contacting server".
Had the phone, cords and power brick all shipped back up here. Configured a new phone, power brick, lan cords, and took them off site and tested – phone works perfectly. Packed it up, shipped it to Atlanta, she connected to her network - no joy, same hang on "Contacting Server".
The Comcast modem is in virtual bridge mode, so they say it is doing absolutely nothing with the traffic. The firewall has a trusted port configured for phone traffic – problem occurs on that port. Also has a port configured wide open (DMZ) in case we need to test anything outside of firewall rules – problem occurs on that port as well.
I suspect the issue is the Comcast connection, particularly since the problem started prior to installing the new firewall, but I'm not sure how to check or test or even what language to use when calling their techs to troubleshoot...
Logs from the firewall:
networkd [eth2 (Trusted Phone)] Interface link status changed to down id="3100-002C"
networkd [eth2 (Trusted Phone)] Interface link status changed to up id="3100-002C"
networkd [eth2 (Trusted Phone)] Interface link status changed to down id="3100-002C"
networkd [eth2 (Trusted Phone)] Interface link status changed to up id="3100-002C"
dhcpd DHCPDISCOVER from 08:00:0f:5c:bd:96 via eth2 id="1600-0066"
dhcpd DHCPOFFER on 192.168.4.2 to 08:00:0f:5c:bd:96 via eth2 id="1600-0065"
dhcpd DHCPREQUEST for 192.168.4.2 (192.168.4.1) from 08:00:0f:5c:bd:96 via eth2 id="1600-0066"
10 minutes or so later, this sequence will repeat.
2016-04-06 09:46:17 dhcpd DHCPACK on 192.168.4.2 to 08:00:0f:5c:bd:96 via eth2 id="1600-0065"
