Fail to restore to v16 or v15.5 if using extension 700

[iNSIGHTS]

A customer is using extension 7xx as they have DIDs ending in 680 - 699 and in 780-790. The receptionist uses extension 700 and is the Operator extension.
This PBX was setup on V15 then upgraded to v15.5. I was forced to upgrade to V16 because the Android app is unable to connect to V15.5.
So I took a backup but was unable to restore to v16 - page that shows Operator extension shows the user's details but has 2 errors and the extension is blank but I'm unable to enter any info. But I'm also unable to restore back to v15.5 as it shows the same error.
Is the solution to do a new setup then restore from backup later?

 

[Evolute IT]

A customer is using extension 7xx as they have DIDs ending in 680 - 699 and in 780-790. The receptionist uses extension 700 and is the Operator extension.
This PBX was setup on V15 then upgraded to v15.5. I was forced to upgrade to V16 because the Android app is unable to connect to V15.5.
So I took a backup but was unable to restore to v16 - page that shows Operator extension shows the user's details but has 2 errors and the extension is blank but I'm unable to enter any info. But I'm also unable to restore back to v15.5 as it shows the same error.
Is the solution to do a new setup then restore from backup later?

Change the extension 700 before upgrade.

The 700 is now the conference bridge by default when upgrading so if an extension exists or if it was set as Operator, it will output errors.

@JohnS_3CX can help with the exact process.

 

[iNSIGHTS]

It's a big problem as this wasn't highlighted as a critical block so now I'm unable to move to v16 and also unable to revert back to v15.5.
If I'm able to recover I'll shift the receptionist to another extension but obviously could have avoided if I had known 700 was intended to be a hard coded block.

 

[iNSIGHTS]

Yikes now I have another error: too many cert generation requests for the same FQDN. I'm trying to restore the PBX, 5 requests in 7 days will trip this? The cert request should be done at a later stage of a restore if other processes can trip this up.
But a related problem triggered the rush to migrate to v16. Why does the Android app require v16 when the iOS can still work with v15.5sp6?

 

[Evolute IT]

Yikes now I have another error: too many cert generation requests for the same FQDN. I'm trying to restore the PBX, 5 requests in 7 days will trip this? The cert request should be done at a later stage of a restore if other processes can trip this up.
But a related problem triggered the rush to migrate to v16. Why does the Android app require v16 when the iOS can still work with v15.5sp6?

Because the Android one is newer. The new iOS app that will also only work with V16 is still under heavy development. Expected in 1-2 months.

To learn what's new of the Android app, see the blog.

As for your certificate issue, 3CX should work anyway and you should be able to access the MC even with an invalid certificate. To restore, I recommend going to a V15.5 SP6, restore the V15 backup you had made in the first place, then change the extension before upgrading to V16 again.

 

[iNSIGHTS]

Thanks for your suggestion but I already tried and I'm unable to go back to v15.5 either as I encounter the same error. With the cert error think I'll also unable to complete the setup even with a (temporary) new PBX config using the same initial settings.
So I'm stuck and the customer will have no PBX unless I restore it in about 3 hours.

 

[Evolute IT]

Thanks for your suggestion but I already tried and I'm unable to go back to v15.5 either as I encounter the same error. With the cert error think I'll also unable to complete the setup even with a (temporary) new PBX config using the same initial settings.
So I'm stuck and the customer will have no PBX unless I restore it in about 3 hours.

No, you should be able to retry the cert request and after 1-2 retry failed it will simply bypass that step. That happened to me once.

 

[iNSIGHTS]

Thanks, so I'll just retry. I tried installing with a new cert and key but unable to restore from backup; need to use same FQDN and license key. So I'll try to setup a new PBX then restore. I hope this workaround succeeds otherwise it's going to be a tense few hours soon.

 

[iNSIGHTS]

I tried installing as a new PBX config, setup operator extension as 789, then changed conference code to 400., Then attempt to restore. No go.
During setup I retried the cert requests many times and eventually had to release the cert, but after release I was informed my domain was already full so had to use another domain.
This is bad as the backup requires the same FQDN! Really stuck.

 

[ArtR]

Yikes now I have another error: too many cert generation requests for the same FQDN. I'm trying to restore the PBX, 5 requests in 7 days will trip this? The cert request should be done at a later stage of a restore if other processes can trip this up.
But a related problem triggered the rush to migrate to v16. Why does the Android app require v16 when the iOS can still work with v15.5sp6?

They now have a Legacy 155 3CX client for Android to use for systems staying on v15.5
We don't want to move to v16 yet, and this stopped working on my Android, but luckily they created the v15.5 compatible app.