PBX Platforms
Page tree
Skip to end of metadata
Go to start of metadata

About

Sangoma has been working hard to launch our PBXact Cloud 2.0 communications platform, which has been deployed successfully for several months now. PBXact Cloud 2.0 is based on PBXact 16 which provides security and performance enhancements over the versions used for version 1.0. If you are a PBXact Cloud customer running PBXact Cloud 1.0, we will be moving your instance to the PBXact Cloud 2.0 platform. Sangoma endeavors to make this process as easy as possible, however, there is some coordination that may have to happen to ensure the migration goes smoothly.

Over the next few weeks we will select a migration date and time for your instance. If you prefer to schedule a time, please select the time that works best for you here: https://calendly.com/pbxact-cloud-support/migration

What Sangoma will be responsible for:

Sangoma will set up the new system in our new data center, and migrate all of your existing settings, phone numbers, records, domains, etc. This will be a new virtual machine with a new IP address, we’re unable to keep the same IP Address. We are also updating all systems to our current security model for Zero-Touch phone provisioning and Phone Apps in PBXact Cloud, so it’s possible that service IP, username, password, port, and protocol(s) will change.

What You will be responsible for:

Once the new changes are in place, it may be necessary for you to reconfigure all of your phones to ensure they are provisioning and registering to the new system and new IP Address. You will be responsible for the configuration of all phones that are not managed by Endpoint Manager to use the new connection information.

You will also be responsible for any networking related changes that need to be made, such as updating DHCP Option-66 to point to the new IP, and any firewall configuration that needs to be made on-premise.

Some devices such as older S Phones will require a factory reset to accept the updated Redirect Settings. If Redirect Settings for a phone are setup to be individually configured by MAC address instead of the deployment, this will need to be updated in portal.sangoma.com manually.

Zulu desktop is being phased out in favor of Sangoma Phone desktop. As part of the migration process, any end users on Zulu will need to move to Sangoma Phone, which will require new client download and new configuration. 

Before the migration

A few things can be done in advance to ensure a smooth migration:

  • Ensure all phones are being provisioned with endpoint manager. This allows us to redirect the phones to the new server once it's available. If the phones are NOT provisioned with endpoint manager, then they will need to be reconfigured manually after migration.
  • Ensure all S Phones have redirect settings properly set to the deployment in portal.sangoma.com. This will help ensure that the phone will get the proper configuration information in the case a factory reset needs to be preformed.
  • Determine if your network is running DHCP Option-66. If it is, then the settings will need to be adjusted once the migration has been completed.

After the migration

After the migration has been completed, we may ask you to reconfigure your phones. 

  • Sangoma/Digium D Phones should not need any additional configuration and should port over without requiring any intervention.
     
  • Sangoma S Phones may need a factory reset to ensure continued operation, otherwise they may stop working if restarted. To test this, restart the phones and if there are issues contacting the server, you can follow these instructions to factory reset your phones: https://wiki.freepbx.org/display/PHON/Factory+Reset

    Please note: Before factory resetting a Sangoma S phone, check that the Redirect configuration information is up to date in     portal.sangoma.com by looking at the assigned phones to your cloud deployment. The phones should be assigned to the cloud deployment, however, if a Sangoma Phone's Redirect settings are configured by MAC address and not to the deployment, the provisioning information will need to be updated in portal.sangoma.com for each phone to match the configuration found in the Endpoint Manager module under Global Settings. We only reset Redirect configuration information related to the deployment and leave phones configured by MAC address up to the user to manage. If you wish for us to manage your phone's configuration, simply assign the Redirect configuration of the phone to the deployment.

  • Zulu users will need to move to Sangoma Phone, which will require new client download and new configuration. You can follow these instructions to setup and configure Sangoma Phone: https://wiki.freepbx.org/display/CONNECT/Sangoma+Phone+Desktop+Client
     
  • Grandstream phones may need to be reconfigured to use the new server host and credentials on each phone, otherwise they may stop working if restarted. To test this, restart the phones and if there are issues contacting the server, you can follow these instructions to update your phones: https://wiki.freepbx.org/display/FPG/Supported+Devices-Grandstream
     
  • Yealink phones may need to be reconfigured to use the new server host and credentials on each phone, otherwise they may stop working if restarted. To test this, restart the phones and if there are issues contacting the server, you can follow these instructions to update your phones: https://wiki.freepbx.org/display/FPG/Supported+Devices-Yealink


FAQ

Will my PBXact Cloud instance get a new IP Address?

  • Yes, your PBXact Cloud 1.0 instance will be migrated to a new VM with a new IP Address. Unfortunately, we're unable to keep the same IP Address.


Will you know ahead of time what the new IP address will be set to?

  • No, we will not know until the time of migration what the new IP address will be set to. However, the hostname of the PBXact cloud instance will not change. I.E. <uuid>.clients.pbxactucc.com


Will my SIP Port change?

  • SIP Ports should stay configured to use 5060, however, we are converting all extensions from the chan_sip to PJSIP driver.
  • If using a mixture of the chan_sip and PJSIP driver, phones configured to use chan_sip may need to be manually reconfigured to work properly. 


Which ports will be updated? 

  • Admin Secure Port will change from 443 to 4443
  • UCP Secure Port will change from 4443 to 443
  • Phone Provisioning Port will change from 83 to 84
  • Restapps port will change from 84 to 83 


Is Sangoma Connect available on the latest version of cloud?

  • Yes, Sangoma Connect is enabled


Is Zulu supported on the latest version of cloud?

  • Zulu is being phased out in favor of Sangoma Connect and Sangoma Phone desktop. As part of the migration process, any end users on Zulu will need to move to Sangoma Phone, which will require new client download and new configuration.
  • Although it's being phased out, Zulu can be enabled on a per request basis to support.


  • No labels