Welcome
Guest
FAQ Forum Developers Sign In

How do I ensure my users and devices can connect to OpenScape Cloud after the migration to Google Cloud Platform?

Last updated:

OpenScape Cloud will be migrated to the Google Cloud Platform in Q3 and Q4 of 2019, respectively. This article is intended to inform you in advance and in particular to make any potentially necessary changes or preparations in your ITC infrastructure.

At the present time, we are publishing the migration schedule and planned processing for our customers on the cloud system in North America.

The migration schedule for the remaining customers and regions will be published some weeks upfront of the transition.

Our engineers have worked hard to limit the impact to you. Unfortunately, despite this work, some impacts are unavoidable. We are sorry in advance for any inconvenience caused.

Any SIP trunk provider that supports static routing will be contacted by us to update their routing tables accordingly. The remaining SIP provider connections (with user / password or digest authentication) do not require any changes – the link will be re-established by OpenScape Cloud from the new data center. Your telephones will be redirected to the new datacenter automatically by adjusting DNS.

 

We expect the following impacts for North America:
  • For Thursday – September 26, 2019 between 1:00 am to 7:00 am EST we plan for a maintenance window for execution of the migration which comes with service interruption for all telephony calls: Telephony calls that are in progress involving an OpenScape Cloud client or a phone (Unify desk phone, 3rd party SIP phone or cordless IP DECT) will be dropped and not re-established until the maintenance work has been concluded. Circuit functionality including Circuit to Circuit calls or meetings (conferences) will be unaffected.

  • Upfront, starting Monday - September 23, 2019 the administration of OpenScape Cloud will be restricted for our preparation and we kindly ask you to avoid any administrative tasks related to telephony deployment and functionality.

 

We kindly ask you for the following preparative work:
  • The DNS names of our server will be updated from the old datacenter to the new one. If your Firewall is currently restricting outbound traffic based on destination IPs, the rules will have to be updated as shown below. Please select the US System for North America or the EU System (Rest of World) depending on which you are served from.

  • If you use 3rd party SIP devices or Cordless IP DECT phones and entered IP addresses as the device’s registration parameters then the configuration needs to be either changed upfront to using the DNS addresses or needs to be changed with our data center migration to our new IP addresses.

 

US System

Usage FQDN Old IP Address New IP Address Port
OpenScape Cloud User SBC NA sbc-03-na.yourcircuit.com 208.43.225.170 35.226.123.45

65061

10000..49999

Deployment Server NA dls-01-na.yourcircuit.com 208.43.225.173 35.192.34.157 18443, 18444
File Server NA fs-01-na.yourcircuit.com 208.43.225.173 35.192.34.157 444

 

EU System

Usage FQDN Old IP Address New IP Address Port
OpenScape Cloud User SBC EU sbc-03-eu.yourcircuit.com 5.10.66.101 35.234.104.141

65061

10000..49999

Deployment Server EU dls-01-eu.yourcircuit.com 5.10.66.123 34.89.193.224 18443, 18444
File Server EU fs-01-eu.yourcircuit.com 5.10.66.123 34.89.193.224 444

 

We thank you for your understanding and your cooperation.

Please do not hesitate to contact us in case of any questions.

1 person found this useful.
Me too / Not at all