Solved On-Prem to Digitalocean

Status
Not open for further replies.

DaveCo

Free User
Joined
Sep 12, 2020
Messages
15
Reaction score
1
Moved my local server to DigitalOcean using the re-install option from 3CX portal and the below occurred requiring me to roll back. Suggestions please.

Apple iPad would no longer ring, iPad to android worked - after roll back to local server iPad works.

Trunk from call centric not ringing extensions but showed registered - after roll back works.

Does softphones require re-scan of QR code, could not get green ready for calls, but able to get extension to extension calls to work. After rescan able to get green.

Windows client would not connect to new server, does it require a reconfiguration.

Thanks
Dave
 
Moved my local server to DigitalOcean using the re-install option from 3CX portal and the below occurred requiring me to roll back. Suggestions please.

Apple iPad would no longer ring, iPad to android worked - after roll back to local server iPad works.

Trunk from call centric not ringing extensions but showed registered - after roll back works.

Does softphones require re-scan of QR code, could not get green ready for calls, but able to get extension to extension calls to work. After rescan able to get green.

Windows client would not connect to new server, does it require a reconfiguration.

Thanks
Dave
You probably just didn't wait long enough for all DNS to update to the new IP.

Std and Pro licenses have a 6 hours TTL. Ent is 5min for failover.
 
  • Like
Reactions: RCT-CP
I did this as well the other week. The only hiccups I had were having to factory reset a couple hard phones that for whatever reason didn't want to accept being behind the SBC. They're legacy phones, so that's likely why.
 
  • Like
Reactions: Evolute IT
What @ConceptsWeb mentioned regarding the DNS may indeed be the case meaning you might have to give it some time but also make sure that you've shutdown the old server before deploying the new one otherwise it might override the new DNS record and cause remote endpoints to connect to the old IP again. Not shutting it down might also cause issues with SIP Trunk calls as the SIP Account will be registered on two different PBXs, this might explain why you had issues with Call Centric calls.

Does softphones require re-scan of QR code, could not get green ready for calls, but able to get extension to extension calls to work. After rescan able to get green.

Windows client would not connect to new server, does it require a reconfiguration.
If you're keeping the same FQDN then it should not require a rescan/reprovisioning, all it would need to be able to do is resolve to the new IP.
 
  • Like
Reactions: Evolute IT
Attempted again this weekend and my only complaint is that all phones had to rescan the QR code for apps to register which doesn't make sense since as ChrisC stated my FQDN didn't change.

Thanks for the feed back provided.
 
  • Like
Reactions: ChrisC_3CX
Attempted again this weekend and my only complaint is that all phones had to rescan the QR code for apps to register which doesn't make sense since as ChrisC stated my FQDN didn't change.
Glad to hear you got this sorted!

Indeed, if you did not change the FQDN the 3CX Apps should've been able to download the new provisioning without having to rescan. One thing I forgot to mention is that for this to happen you would have to actually also keep the same HTTPS port. If you changed from 443 to 5001 or vice versa then that would explain why you had to rescan.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet