Skip to main content
CallTower Solutions Center

MS Teams Direct Routing - Migration Automated Steps

  1. Last updated
  2. Save as PDF

GCCHigh Direct Routing Migration - Frequently Asked Questions

How To Schedule Migration?
Click the link below to schedule the Migration. There is also an option to schedule a Consultation to discuss the Migration with an Engineer.

GCCHigh Migration Booking

clipboard_e5da2379f360f3175a00453012249d632.png

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?

  •     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 Quick Setup Guide

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.

clipboard_e5f159151109047fd4de9c00feeae4556.png

GCCHigh Direct Routing - Migration Steps

Automated Migration Process:
  1. Customer follows the steps outlined in the article here to add the application to their tenant.
  2. CallTower validates available licenses for activation users.
  3. CallTower starts automated migration process
    1. Automation adds two custom domain names for SBC gateways
      1. {customer domain}.pstn3.ctgov.services
      2. {customer domain}.pstn4.ctgov.services
    2. Automation creates two activation users one on each SBC domain
    3. Automation applies a license to each activation user
    4. Automation creates voice routes using new SBC gateway domains
    5. Automation removes activation users
    6. Automation begins re-routing of inbound numbers to use the new SBC gateway trunks.
  4. CallTower/Customer validates inbound calls are completing.
  5. CallTower manually removes Audio Codes PSTN gateways
  6. CallTower manually removes legacy custom domain(s)
  7. Customer validates outbound calls are completing.
  8. Customer may remove the application from their tenant if they desire.
  9. Completed.
  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
  2. Tags
    This page has no tags.