Azure 3CX v16 to V18 SBC

[eds.pare]

We are planning to upgrade from v16 to v18 in azure by creating a new instance by using the backup.
We have an SBC and some trunks to another 3cx instance that we have. do we need to change anything on the sbc config?

Thank you

 

[Saqqara]

No changes are required on sbc

Sbc connects via fqdn

Just remember ttl on 3cx std or pro on 3cx fqdn is 6 hrs, ent is 5 mins - so it make take while for the fqdn to be pointing to the wan IP address

 

[ChrisC_3CX]

We are planning to upgrade from v16 to v18 in azure by creating a new instance by using the backup

Do bear in mind that, if the existing 3CX v16 Instance is already in azure and has been deployed as per our guidelines, you could upgrade it directly to v18 via the Management Console. This will also upgrade the OS from Debian 9 to Debian 10.

Regarding the SBC, as @Saqqara correctly said it should connect automatically once the DNS gets updated and propagates so there should be nothing to worry about. Just make sure you shutdown the old VM before deploying the new one so that it does not interfere with the DNS records in any way.