Advice for 1 PBX & 4 SBCs separate in 2

[AWS2P]

Hi,
I need confirmation on what is the best and simple to do in my case, I need to separate a PBX in 2
My starting point is: Cloud PBX A with 4 SBCs attached
Goal point is: Cloud PBX A keep SBC 1&2 attached , Cloud PBX B (part of actual config coming from PBX A) keep SBC 3&4 attached

What I have in mind is: (am I right thinking like this?)

• Doing a backup From PBX A without KEY and FQDN and keep it ready to use on PBX B
• Buy a new 3CX licence for PBX B
• Create a new VM for PBX B
• Install 3CX on VM with new FQDN
• On PBX A deletion of all settings used now on PBX B
• Restore backup on PBX B (this to retrieve mostly everything set like it was on PBX A, and delete all settings useless for PBX B)
• I expect SBCs 3&4 to reconnect to PBX B after only FQDN change on 3CX PBX B side , is this ok ?
• For phones behind SBCs 3&4, will I need to factory reset them or phones could be able to provision alone? (mix of Desk phones Fanvil , Apps and DECT W60B)

Thanks for your validation or not

 

[VasilisV_3CX]

Hi @aws2p,

The only advice I have for you, is to change any register based SIP Trunks registrars (add a "1" to that and the proxy if it exists) so that the SIP Trunks do not register.

Also maybe change the email addresses (add a "1" there too) on the users so that they do not receive welcome emails when created, then remove them after the installation.

 

[AWS2P]

all others things from my list are good ? nothing missing ? process order seems good ?

SBC 3and4 are Pi 4 based, is there something to change on their side or nothing ?

 

[VasilisV_3CX]

Hi @aws2p,

Yes, the general logic seems okay, shouldn't be a problem. Let me know if you run into any problems along the way.