Solved V18 move from on premise to cloud

[AWS2P]

Hi
actually I have a WIN10 ,V18, on premise PBX using non standard SIP port number.(it was impossible to use 5060 due to ISP)
When I will backup it, do I'll keep in the backup file the SIP port number previously used ?

If so, when I will reinstall on cloud, I'd like to re-use 5060, so how to proceed if backup restore previous number port ?

After that an SBC will be setup on customer location and phones will need to be reprovisionned, is there an more easy way to do than factory reset the phones and provision with new SBC and PBX settings?

 

[ChrisC_3CX]

actually I have a WIN10 ,V18, on premise PBX using non standard SIP port number.(it was impossible to use 5060 due to ISP)
When I will backup it, do I'll keep in the backup file the SIP port number previously used ?

If so, when I will reinstall on cloud, I'd like to re-use 5060, so how to proceed if backup restore previous number port ?

If you will be deploying via the Portal's deployment wizard you will not be able to change the SIP port. IF however you use the market place or the 3CX ISO to deploy then you should be able to change it.

After that an SBC will be setup on customer location and phones will need to be reprovisionned, is there an more easy way to do than factory reset the phones and provision with new SBC and PBX settings?

If the IP Phones were already using an SBC then you won't actually need to do anything, not even re-install the SBC as it will manage to connect once it resolves the FQDN to the new IP. This of course provided that you do not change the FQDN.

If however the IP Phones are currently provision as local or STUN devices, then you will need to install the SBC and also factory reset the IP Phones.

 

[AWS2P]

Thanks Chris, I will use AWS lightsail as cloud hoster, so I will install with portal's deployment, so it's impossible to change the SIP port ?

my understanding and also my question is about what's in backup? is the SIP port inside the file backup or not saved at all , and you are free to set it during reinstall and even after restoration port stay the one you choose during reinstall?

 

[ChrisC_3CX]

My apologies as I may have not been clear in my previous reply.

Using the 3CX Portal deployment wizard will revert the ports back to the default ones:

HTTPS: 443 or 5001 (this you can choose one of the two)
SIP Port: 5060
Tunnel port: 5090

If these are the ports you wish to switch to, using the deployment wizard would be the way to go. If you want to change the ports to anything else then you should either use the marketplace or 3CX ISO.

 

[AWS2P]

Ok so first part of the question is solved, as to say ports during reinstall revert to default, but once I will push the backuped file to restore the settings, is there something altering once again SIP port ? or it will stay as 5060?

 

[ChrisC_3CX]

..but once I will push the backuped file to restore the settings, is there something altering once again SIP port ?

No, if you restore via the 3CX Portal deployment wizard then, even if you use a backup taken from a system with custom ports, the ports will still revert back to the default ones I mentioned in my previous reply.

 

[AWS2P]

Thanks one potential shitty problem fixed

 

[ChrisC_3CX]

You're very welcome!