Cisco 7940 & 7960 Models No Longer Registering

[philodendrin]

We have a customer that was running 3CX v15 on a Server 2008 box. Since 2008 is no longer supported by 3CX and Microsoft, we swapped them over to a Win 10 PC, shut down the server 2008 server, matched the IP address of the Server 2008 box on the Win 10 PC, installed 3CX v16 on the Win 10 Pro box and restored from v15 backup.

After that, everything came back except for the Cisco 7940 and 7960 phones. Yealink, Fanvil, and Cisco SPA514g models registered just fine.

After waiting a day for the 7940s to register, we assigned the old Server 2008 box a new IP (offline) and then copied over the CNF files of the corresponding phones that were not registering to the provisioning directory on the Win 10 PC... we verified that we still had Option 66 set on the DHCP server, pointing to the IP address of the 3CX PC. We've tried factory resetting one and provisioning via TFTP. Nothing seems to work. And yes, we've followed the 3cx article https://www.3cx.com/sip-phones/cisco-7940g-7960g/

What the heck is the trick to getting these working again?

 

[cobaltit]

Have you tried looking at the logs to see if they are attempting to register? Wireshark perhaps?

 

[thegrs]

I just had the same issue as well and don't have a fix yet. We are running 3CX Version 16 Update 4 on a Windows Server 2012 R2 installed as a Hyper-V machine. Since the newer versions of IOS clients are going to require HTTP/2 we decided to switch our server over to a Windows 10 Pro build 1909 Hyper-V Machine. I backed up the old configuration from 3CX and turned the server off. Installed the new Windows 10 Machine and installed 3CX using the backup file and everything seemed to install ok. The Windows 10 Box has 3CX Version 16 Update 4A installed. I was able to do test calls from the 3CX Android client and also the Web Client.

I made sure that the new Windows 10 machine had the proper ip address and I also disabled Windows 10 firewall then I turned on the phones. The TFTP server hosted on the Windows 10 machine got the requests for the phones and sent back the configuration files. The phones finished booting and show up under the Phones tab in the Management Console of 3CX. The display on the phones showed they booted properly and connected as well. The issue is when you try to dial a call, it gives a fast busy signal on the phone and says Reorder on the screen.

Turning off the Windows 10 Hyper-V Machine and booting up the Windows Server 2012 R2 Hyper-V Machine and rebooting the phones gets they up and running properly. Is there something on Windows 10 that blocks the communication?

 

[thegrs]

bump

 

[thegrs]

bump

 

[cobaltit]

Would still need verbose activity logs and probably wireshark logs to further troubleshoot. I think I tossed all of my CP79xx phones so I don't know that I could test here.

 

[philodendrin]

We got the Cisco 7940/7960 models working somewhat by copying the MAC specific CNF files from the provisioning directory of the old 3CX server to new.

We've also had some success just firing up a TFTP server and pushing the CNF files. Option 66 is a crap shoot with these phones.

My current dilemma is trying to figure out a way to upgrade firmware from version 8 to 8.5.4s without an intermediary firmware. It looks like you need 8.3.3s before you can go higher...and Cisco now requires a support contract to get the firmware. So, a great way to force people to toss the phones.... make them pay more for a support contract than the phones are worth.