PBX Migration to a new colo...

[narrington]

I know this question has been asked in various threads. I have read most of them and I feel like I have a good understanding what will happen. but I wanted to make a thread to be sure.

I'm relocating our PBX from a corperate office into a colo. I've already built the server and installed the 3cx/debian (stretch) image and I'm about to kick off the configuration tool.

We have an enterprise license with an up-to-date maintenance contract and FQDN (through 3cx). I know the licenses are bound to the FQDN and cant be seperated. that's expected. we also have a dozen or so SBCs in the wild handling remote workers.

My checklist is as follows:
1> deploy a new SBC to take the old server's place at the office where the PBX lived (presently handles a dozen or so phones, all of them are offline because of quarentine... gotta love this massively long "unscheduled service window"!)
2> run a late stage backup of the old server and scp the backup file to the new server.
3> run the 3cx config tool and select "Restore an existing backup configuration"

I've never actually done this before so this part is a little fuzzy, but I assume the tool will restore the config of the original server including sip trunks, SBCs, FQDN, and licenses... right?

any other gotcha's I should be looking for?

 

[Alphabetic]

https://www.3cx.com/docs/manual/pbx-backup-restore-failover/

Check everything in your backup when you run it - Yes, that will be restored.

You will need to re-enabled your scheduled backup on your new server and also reset/reprovision all phones.

Your existing SBCs should be pointing at the FQDN so once that gets updating they should automatically reconnect - Though i've not tested this so you may end up setting these up again.

If you can SSH to the Pi's (if thats what you have)

sudo apt remove 3cxsbc --purge

then set up again https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

and just make sure you've got the NTP installed on Debian

apt-get update

apt-get install ntp

 

[narrington]

Thanks @kieferschild... This all seems pretty straight forward. even the gotchas are somewhat expected. of course I hope the SBCs just connect to the new server (following the FQDN), but I can handle it if they dont. as for connecting to the SBCs via ssh... not really possible for most of them. I DID set up ssh, but they're all living at people's private residences. we cobbled together a bunch of raspberry Pis for project "go-home". Didn't really bother with more than that so direct access from here to each one is not really an option. I have to regularly re-provision phones when the SBCs take new IPs from their respective routers, so that's old news too.

I guess I'm going to have to set expectations for people the weekend I do this. probably going to have to teamviewer in to everyone's PCs and ssh to the pi's from there. meh. it's not the end of the world ether way.