MS Teams Direct Routing - Migration Automated Steps

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Direct Routing Migration - Frequently Asked Questions

Will there be downtime?
There is no expected downtime during the migration, and the Legacy Direct Routing trunk continues to function throughout the migration for Inbound and Outbound calling until the numbers are re-routed over the new Direct Routing Trunks.

Will my users notice anything different?
No, the migration will be seamless for your users, and they will not notice any changes to the service.

What do we get out of upgrading?
One Click Failover, Manage forwarding through Commportal or CallTower Connect.
    Geo-Redundant Direct Network Connectivity to Microsoft
    Same Backend Platform as Operator Connect
    Streamlined Voice Path
    Dynamic E911

Is there any additional cost associated with the upgrade?
No, there is no additional cost, and your monthly bill will remain the same.

How do I configure Dynamic E911?
MS Teams Dynamic e911 Dialing - Operator Connect and Direct Routing

How do I configure One Click Failover?
MS Teams - One-Click Failover

How much time is required for the upgrade?
We schedule an hour for the actual migration, Typically, the automated migration takes anywhere from 25 mins to 45 mins, and we allow for plenty of time to validate.

Why do you need Domain Name Administrator and User Administrator?
See the Below section "Direct Routing - Automated Migration Steps", The steps which require elevated roles are highlighted with either "Domain Name Administrator" or "User Administrator."

Direct Routing - Migration Automated Steps

The following steps are performed by CallTower in order to migrate Direct Routing to CallTower’s new platform.

After the customer configures a "Service Account" with "Domain Name Administator" and "User Administrator" roles, the following will take place:

1. CallTower validates available licenses for activation users

2. CallTower starts an automated migration process in CallTower Connect

Automation adds two custom domain names for SBC gateways - Domain Name Administrator
- {customer domain}.pstn1.ct-us-chi.services
- {customer domain}.pstn1.ct-us.dal.services
Automation creates two activation users, one on each SBC domain - User Administrator
Automation applies a license to each activation user - User Administrator
Automation creates Voice Routes using new SBC Gateway Domains (*Teams Admin)
Automation Removes Activation users - User Administrator
Automation starts re-routing inbound numbers to use the new SBC Gateway Trunks

3. CallTower/Customer validates inbound numbers are completed

4. CallTower manually removes Audio Codes PSTN Gateways (*Teams Admin)

5. CallTower manually removes legacy custom domain - Domain Name Administrator

6. The customer validates outbound calls are completed

7. The customer removes Domain Name Administrator and User Administrator Roles from Service Account

8. Completed

GCCHigh Direct Routing - Migration Steps

Automated Migration Process (Connect service account in place):

Customer Grants Service Account with Domain Name Administrator and User Administrator Role.
CallTower Validate Available Licenses for Activation Users.
CallTower Start Automated Migration Process in in connect
1. Automation adds two custom domain names for SBC gateways - Domain Name Admin
  1. {customer domain}.pstn3.ctgov.services
  2. {customer domain}.pstn4.ctgov.services
2. Automation creates two activation users one on each SBC domain - User Admin
3. Automation applies a license to each activation user - User Admin
4. Automation create Voice Routes using new SBC Gateway Domains - Teams Admin
5. Automation Removes Activation users - User Admin
6. Automation starting re-routing of inbound numbers to use the new SBC Gateway Trunks.
CallTower/Customer validate Inbound numbers are completing.
CallTower manually removes Audio Codes PSTN Gateways - Teams Admin
CallTower manually removes legacy custom domain - Domain Name Admin
Customer validates outbound calls are completing.
Customer removes Domain Name Administrator and User Administrator Role from Service Account
Completed.

Self Directed PowerShell Process (Connect does not have a service account):

If you do not have a service account in place for CallTower Connect, and you would like to execute the PowerShell steps on your own tenant this will be the process used:

Customer Schedules an Migration call with both an Administrator on the Tenant and CallTower Engineer.
Customer/CallTower Validates Available Licenses for Activation Users.
Customer will Share screen and starts the Self Directed Migration Script.
1. Script adds two custom domain names for SBC gateways - Domain Name Admin Required
  1. {customer domain}.pstn3.ctgov.services
  2. {customer domain}.pstn4.ctgov.services
2. CallTower updates DNS Records while script is paused.
3. Script creates two activation users one on each SBC domain - User Admin Required
4. Script applies a license to each activation user - User Admin Required
5. Script create Voice Routes using new SBC Gateway Domains - Teams Admin Required
6. Script Removes Activation users - - User Admin Required
7. CallTower begins re-routing of inbound numbers to use the new SBC Gateway Trunks.
  1. (15 minute pause recommended)
CallTower/Customer validate Inbound numbers are completing.
CallTower instructs to run the last section of the script.
Script removes Audio Codes PSTN Gateways - Teams Admin Required
Script manually removes legacy custom domain - Domain Name Admin Required
Customer validates outbound calls are completing.
Completed.