The Enabling Technologies Blog

Our team of Cloud Strategy Advisors, Solution Architects, Engineers and former C-Suite Executives work diligently to provide our vistors with the most pressing information.

John Miller /

Migrating Intelepeer SIP Trunks to the new Platform

Introduction 

If you’ve added an IntelePeer SIP Trunk to your environment in the last two (2) years, it has probably been setup on IntelePeer’s “Ribbon SBC 7k” platform. According to IntelePeer, this new platform allows  

“Unlimited scalability, the latest security compliance, and advanced services such as our Atmosphere Communication Platform as a Service (CPaaS) and future services.” 

 The new platform is required if you want to use IntelePeer as your Emergency Routing Service Provider (ERSP) as part of your Teams Dynamic 911 implementation. “Traditional” ERSPs like Intrado take a 911 call from a Teams Direct Routing user and route it to the appropriate Public Safety Answering Point (PSAP). The ERSP can determine the correct PSAP for the call based on the user’s current address provided by Microsoft Teams. Connections to ERSPs are typically setup using a dedicated SIP Trunk between the Session Border Controller (SBC) and the ERSP. IntelePeer offers the option to add this ERSP capability to their Atmosphere CPaas SIP Trunks. For further information about Teams Dynamic 911, please look at our other blog articles on the subject. 

IntelePeer has made the process of migrating a SIP Trunk very easy. The migration will require changes to your Teams Direct Routing SBCs interfaced to the older IntelePeer SIP Trunks. The lead time for IntelePeer to setup these new SIP Trunks is currently very short. As we get closer to the end of the year, it is expected that these lead times will increase. Enabling recommends that SIP Trunks that if you need migrate to Atmosphere CPaas SIP Trunks you do so as soon as you can. 

Do you have any older IntelePeer SIP Trunks? 

  • You can check your existing SIP Trunks 
  • Calling the IntelePeer NOC at +1 (866) 780-8639 

Using your Customer Portal to check your SIP Trunks 

  1. Open a browser and navigate to https://customer.intelepeer.com. If you do not have credentials, forgot them or are having any other problems signing in, please use the contact information listed above. 
  2. Enter your credentials 
  3. Click on the “Log In” button which should take you to your Dashboard 

Graphical user interface, text, application, email

Description automatically generated

     4. Click on “Usage-based” from the vertical menu. 

     5. Click on each package listed under “User-based” (you may not have any) 

Graphical user interface, application

Description automatically generated

       6. Look at the “IntelePeer Trunk Name” for each trunk listed under the “Round Robin Routing Profile” or “Trunks” header. If the fourth                         character in the name is: 
       a) A zero (0) or a four (4): The SIP Trunk is NOT running on the “Ribbon SBC 7k” platform and will have to be migrated. In the example, both             SIP Trunks will need to be migrated. 
        b) A seven (7): The SIP Trunk is on the “Ribbon SBC 7k” platform and is good to go! 

Graphical user interface, application, Teams

Description automatically generated

       7. Click on “UC Basic/P Bundle” in the left vertical menu 
       8. Click on each listed SIP Trunk (you may not have any!)  
       9. Review the fourth digit of their “IntelePeer Trunk Name” values 

Number formatting requirements for Ribbon SBC 7k SIP Trunks 

  • The number formatting requirements of the Ribbon SBC 7k SIP Trunks are different than those of the old SIP Trunks 
  • These changes will have to be planned for and applied to your SBCs 

Inbound Calls: IntelePeer SIP Trunk to SBCs 

  • Source\Calling Number 
  • Domestic Callers 
  • 10 Digits or e.164: 
  • 4436255100 
  • +14436255100 
  • International Callers 
  • e.164 
  • +440207123456 
  • Destination\Called Number 
  • Domestic PBX or Teams users 
  • 10 Digits or e.164: 
  • 4436255100 
  • +14436255100 
  • PBX or Teams users with non-US phone numbers 
  • e.164 
  • +440207123456 

Outbound Calls: PBX or Teams through the SBCs over IntelePeer SIP Trunks 

  • Source\Calling Number of the PBX or Teams caller 
  • Domestic Callers 
  • 10 Digits, 1 + 10 digits, or e.164: 
  • 4436255100 
  • 14436255100 
  • +14436255100 
  • International Callers 
  • e.164 
  • +440207123456 
  • Destination\Called Number 
  • PBX or Teams callers with a domestic phone number 
  • 10 Digits, 1 + 10 digits, or e.164: 
  • 4436255100 
  • +14436255100 
  • +14436255100 
  • PBX or Teams users with non-US phone numbers 
  • e.164 or 011 + Country Code + Number 
  • +440207123456 
  • 011440207123456 

The Migration Process 

  • The migration process requires coordination with IntelePeer, network and firewall administrators and your users.  
  • It will also require changes to your Session Border Controllers (SBC) and firewalls. 
  • Teams Dynamic 911 will require configuration and testing of: 
  • Microsoft Teams using the Teams Admin Center and Teams PowerShell Module. 
  • The Direct Routing SBC(s). 
  • Enabling Dynamic 911 on the migrated SIP Trunks in your IntelePeer Customer Portal. 
  • A cookie cutter approach to these migrations cannot be used. Each tends to be unique. 
  • The user experience should not change as they are moved to the new SIP Trunks. Training should not be needed. 
  • IntelePeer will remove the old packages and trunks from your account and their equipment after a “soak in” period. Customers will not be double billed for time that both SIP Trunks are in their account. 

High Level 

  1. Contact the IntelePeer Migrations team at +1 (720) 449-8964 to get the process started. 
  2. IntelePeer anticipates that it will take them about two (2) days to setup the new “Ribbon SBC 7k” SIP Trunks for a customer. Once setup, they will be able to provide you with the SIP signaling addresses for the new trunks. As we get closer to the end of the year, the lead time for this will likely increase. 
  3. At your request, IntelePeer can provision one (1) test number on the new trunk(s). They recommend that customers move some test numbers from their existing SIP trunks to the new trunks for testing. 
  4. The customer should perform an internal Change Control to add or create new rules on any applicable firewalls. Network architecture, routing changes, etc. will also have to be planned for. 
  5. “Hot cutting” the SBC to the new SIP signaling addresses is NOT recommended. 

       6. Gather the phone numbers of active users to be used for testing      

       7. Test “plumbing” to accommodate the new SIP Trunks should be added to the affected SBCs. For AudioCodes SBCs you will probably need              to add these objects to test the new SIP Trunks: 
       a) A Proxy Set 
       b) The signaling addresses to the Proxy Set 
       c) A new IP Group 
       d) New Classification rule 
       e) Two (2) routing rules 
       f) New inbound manipulation rules 
       g) New outbound manipulation rules 

       8. There should be no changes required in Microsoft Teams. 
       9. When ready, move some test numbers to the new SIP Trunk in the IntelePeer customer portal. 
     10. Make inbound and outbound test calls to the test users. These calls should flow through the test objects on the SBC. Use your existing                   telephony test plan. Testing should include: 
  • Inbound calls to: 
  • PBX users (if applicable) 
  • Microsoft Teams users 
  • Teams Auto Attendants and Call Queues 
  • 3rd Party integrated Contact Center Solutions 
  • Outbound calls to: 
  • Emergency numbers (even if you do not have Teams Dynamic 911 setup) 
  • Local numbers 
  • Service numbers 
  • Domestic numbers 
  • Toll Free numbers 
  • International numbers (if the SIP Trunks support these) 
  • Call holds – both directions 
  • Transfers – transfers both directions 
  • Dual-Tone Multi-Frequency (DTMF) Dialing 

      11. Determine if you will migrate all your users and their phone numbers at one time to the new SIP Trunks or in groups. Additional                            configuration of the SBC will be needed If you choose to move your users in groups. Moving your users in groups increases the degree of              difficulty of the process but tend to be a “safer” option. 

      12. You can move your phone numbers through your IntelePeer customer portal. Moves can be setup for one (1) to 250 users at a time. You             cannot use the portal to move Toll Free numbers. 
      13. You can also schedule moves with an IntelePeer Number Administrator. They should be able to move non-Toll-Free numbers within five                (5)  minutes and Toll-Free numbers within half an hour. They can move any number of phone numbers including and beyond 250. 
      14. Change the relevant rules and objects on the SBCs to point to the new SIP signaling addresses of the SIP Trunks. 
      15. Perform post cutover testing. 
      16. Remove the test objects and rules from the SBCs. 
      17. Remove the SIP signaling addresses from any firewall rules. 
      18. Complete the setup of Teams Dynamic 911 on the SBC and in the IntelePeer client portal. 
      19. Test Teams Dynamic 911 calling. 

Summary 

  • IntelePeer is retiring their old SIP Trunk infrastructure by the end of 2022. Old SIP Trunks will need to be migrated to the new “Ribbon SBC 7k” platform. 
  • Customers should check to see if they are using any old SIP Trunks and plan to migrate them. The information can be found in their customer portals or by contacting IntelePeer. 
  • The old SIP Trunks do not support dynamic routing of calls to PSAPs based on information provided by Teams Dynamic 911. If customers want to use the SIP Trunks to route calls correctly to the PSAPs, they will have to be migrated. 
  • Customers should plan on migrating their SIP Trunks as soon as possible to avoid any “mad rush” at then end of the year. 
  • Each migration tends to be unique. A general approach to these won’t work. 
  • Enabling does not recommend performing a “hot cut” migration. The new SIP Trunks should be setup in a test configuration and put through a typical Teams telephony test plan. 
  • Moving users phone numbers in groups rather than all at once can complicate the migration significantly. 

Work with our team of Cloud Computing Consultants who have done this so many times they know all of the “minefields” to prevent missteps.

ref:_00D80KtFf._5000y1WwWQD:ref