Source server: FreePBX 16.0.40.8
Target server: FreePBX 17.0.17
Both servers are fully updated for both OS and FreePBX modules.
The source server was running properly with a mix of Polycom 550 and 650 phones as extensions. All extensions could make and receive calls. Extension to Extension worked fine. All incoming truck calls worked as intended.
The target server was built using a base Debian OS and running the new FreePBX install script. From its ‘base’ install, I can add extensions accessing the same Polycom phones used by the source server, change the passwords, etc, and all the extensions work as intended.
I want to ‘move’ the source 16 system to the new 17 system.
I created a system backup from the source 16 and then restored it to the new 17 system. I activated the new server. Everything looks good. Extensions came over. Trunks and routes came over. Call traffic from Flowroute correctly came to the new server, etc.
BUT…All of the phone act as if they are offline or DND.
I manually reset the passwords on all phones. No help.
I performed a system reset on the phones and manually set all SIP and line settings on all phones. No help.
I manually recreated the extensions on the new system, resetting the passwords on the phones. No help.
In a nutshell… from a ‘fresh’ debian/Freebpx 17 install, I can configure an extension using known working Polycom 650 phones, and all is good. When I do a restore from a Freepbx 16 system using the same known working Polycom phones, the extensions all appear as offline. When you pickup an extension, it can retrieve voice mail. When you dial another extension, you get the message that the receiving extension is unavailable. When a call comes in the inbound truck, it gets routed to the recipient extension unavailable voicemail option.
Where should I look to solve this? Any and all ideas are greatly appreciated.
Thank you,
John