You’ll need a Telnyx account to get Teams Direct Routing set up. Sign up today.
Looking for more info? Find out why Direct Routing is the next big thing in business communications.
Direct Routing with Microsoft Teams allows businesses to connect external phone lines to Microsoft Teams and use Teams as an office phone system instead of a legacy PBX system. This means you can maintain your existing SIP trunks and PSTN connectivity -- retaining control over your numbers and realizing cost savings over the MS Teams Calling Plans.
In this user guide, we’ll show Telnyx customers how to use Telnyx as a PSTN provider for Microsoft Teams Direct Routing.
Once set up, Telnyx customers will be able to buy Numbers on the Telnyx Mission Control Portal, receive calls from the PSTN to their Teams account, and send calls to the PSTN from the same Teams account.
This integration is carried out via the Telnyx MS Teams SBC, which interconnects Microsoft Teams with the Telnyx telephony platform. Telnyx SBC uses the base domain mstsbc.telnyx.tech, and Telnyx customers will be able to interconnect using a subdomain of mstsbc.telnyx.tech and a token for authentication.
This product is currently in Beta. Reach out to a member of our team for a list of currently supported features.
This guide is broken down into 4 sections:
- Telnyx Portal Setup
- Microsoft 365 Admin Center: Telnyx Subdomain Setup
- Microsoft Teams: Direct Routing Setup
- Making Test Calls
In order to use Telnyx as a PSTN provider for Microsoft Teams Direct Routing you’ll need a Telnyx account, which you can create in our Mission Control Portal
To explore and buy numbers on the Mission Control Portal you can follow these four quick steps:
- Navigate to the ‘Numbers’ tab on the menu and click ‘Search and Buy Numbers’.
- Perform a Number Search based on region and features.
- Enter your chosen criteria and click the ‘Search Numbers’ button. A list of all available numbers with your chosen features will appear.
- Click the ‘Add to Cart’ button to purchase a number and navigate to the ‘Cart’ at the top right-hand corner of the screen to check out.
Next, you’ll need to set up an Outbound Voice Profile to make outbound calls to the PSTN. This can be created from the ‘Outbound Voice Profiles’ tab in the Mission Control Portal. Follow along with our ‘ Getting Started with SIP Trunking ’ video on how to set your profile, billing, and anti-fraud preferences.
Once you have your Portal Account up and running you’ll need to set up a new MS Teams SIP Connection- let's get started!
When you have set up an account in the Mission Control Portal, the first thing you need to do is to set up a new Connection for the Telnyx SBC on the SIP Connections Page .
Click Add SIP Connection and name your connection. A pop-up window will appear. Give your new connections a name, in this case we'll call it 'MS Teams Trial Connection'. Click Create SIP Connection.
Creating a new SIP Connection in Mission Control
An 'Edit SIP Connection' window will appear. Under SIP Connection Type choose MS Teams SBC. Click Save & Finish Editing.
Creating an MS Teams SBC SIP Connection in Mission Control.
At this point you'll want to take note of the auto-generated subdomain as it will be needed at different stages during the set up.
Next you’ll need to assign a Number to the MS Teams SBC Connection.
In order to do this, you’ll first have to buy a number in the Mission Control Portal, as explained in the Introduction of this guide.
If you have an existing number, navigate to the ‘Numbers’ page and assign your Microsoft Teams connection to the desired DID as shown below.
*Assigning a Telnyx Number to a Microsoft Teams DID connection. *
Lastly, you’ll also want to assign the SIP Connection to the Outbound Voice Profile created in the Introduction of this guide. If you don’t have an outbound profile yet you can create it in the tab “Outbound Voice Profiles. Choose the Traffic Types and Allowed Destinations according to your preferences and click Save.
You can assign an outbound profile to the MS Teams connection in SIP Connections -> Connection -> Outbound and selecting the “Outbound Voice Profile”. Once completed click on “Save All Changes”.
Now that your Mission Control Portal is set up and ready to go, you’ll need to activate the subdomain in the Microsoft admin portal before setting up Direct Routing in Microsoft Teams.
In order to set this up, you’ll need a Microsoft license. We’ve listed different license options in the table below. You’ll need one of the base plans and an add-on if necessary:
|Base Plan||Add on required for Direct Routing|
|Microsoft Office 365 Enterprise E5||No add on required|
License Options and Add Ons required to activate subdomain in Microsoft admin portal
Before you start, ensure you have the appropriate rights in the customer tenant. You can only add new domains if you signed in to the Microsoft 365 admin center as a Global Administrator. To validate the role you have, please sign in to the Microsoft 365 admin center ( https://portal.office.com ) and go to Users → Active Users and then verify that you have a Global Administrator role.
Navigate to Setup → Domains → Add Domain in the Microsoft 365 admin center. Add the subdomain that was automatically generated wwhen the Telnyx Portal Connection was created in Section 1.
Adding a subdomain in Microsoft 365 admin center
Click on Next and verify the domain on the following page. Then select Add a TXT record instead.
Verifying the domain on Microsoft Teams
Click Next and take note of the TXT value.
Information required to verify the domain.
Go back to your Telnyx MS Teams SBC SIP Connection in the Mission Control Portal and click the Edit button on your new connection. Navigate to the ‘Domain Validation’ tab in this window and paste the TXT Value from the MS Teams portal into the ‘TXT Value’ field on your Telnyx SIP Connection. Click Save All Changes.
The TXT Name and TTL fields should match the fields shown in Microsoft 365 admin center, so they can’t be edited.
Adding the TXT Value to the Telnyx SIP Connection in Mission Control
Once changes are saved go back to Microsoft 365 admin center and click on the Verify button.
Verifying the subdomain in MS Teams
Note: It’s OK if the domain status shows “No services selected”. You don’t need to add SPF records. SPF records are a requirement for email but not for Direct Routing.
On the next page, select More Options and the select Skip and do this later and click Next.
Check the ‘Skip and do this later’.
After this you'll see a screen menu indicating that the setup is complete.
Domain setup is complete
After you have registered a domain name, you’ll need to activate it. You can do this by adding at least one user and assigning a domain that matches the subdomain that was automatically generated when the Telnyx Portal Connection was created in Section 1.
To do this, navigate to Users → Active users → Add a user in the Microsoft admin center.
Adding users to activate the subdomain
Next, fill in the User details, select the Telnyx subdomain (i.e yyyy.msteams.telnyx.com), assign E5 license and click Add. You can remove the E5 license from this user once you're able to add this domain to Direct routing.
Activating the subdomain
Here, we’ll take a look at how to set up the Telnyx SBC subdomain in the Microsoft Teams admin center. To do this, you’ll have to have a Microsoft Teams E5 license assigned to each user who will be making and receiving calls to the PSTN. Keep in mind that the changes on the MS Teams admin portal may take up to 24 hours to take effect.
In the left tab of the Microsoft Teams admin center, navigate to ‘Voice → Direct Routing’. Click the SBCs tab.
Direct Routing in the Microsoft Teams admin center.
Click Add and enter the subdomain that was automatically generated when the Telnyx Portal Connection was created in Section 1. Set the SBC to use SIP signaling port 5061, check that SIP options and the connection are enabled. When you’re done click Save.
Enter SBC settings in Microsoft Teams
Once you save the changes, the connection should look like this:
Example Connection in Microsoft Teams
This step enables PSTN usage for Direct Routing. In the left tab, navigate to Voice → Direct Routing. In the upper right-hand corner, select Manage PSTN usage records.
Manage PSTN Usage Records
Click Add, type TELNYX, and then click Apply.
Creating PSTN Usage Records
Now you’ll need to create a pass-through voice route. In the left-hand tab of the admin center, navigate to Voice → Direct Routing. When on the Directing Routing page, select the Voice routes tab.
Click Add, and then enter a name and description for the voice route.
Set the priority and specify the dialed number pattern as per your service provider’s numbering plan.
Creating Voice Routes in Microsoft Teams
To enroll SBC with the voice route, navigate to SBCs enrolled on the Direct Routing page. Click ‘Add SBCs’, select the SBCs you want to enroll, and then click Apply.
To add PSTN usage records, navigate to the PSTN usage records section. Click Add PSTN usage, select the PSTN records you want to add, and then click Apply.
Note that for this example we included “^(.*)$”, which allows you to dial any destination. We recommend using a different pattern if you want to include restrictions.
*Enrolling SBC’s and adding PSTN usage records in Microsoft Teams. *
In the left tab of the Microsoft Teams admin center, navigate to Voice → Voice routing policies, and then click Add. Type TELNYX as the name and add a description.
Adding Voice Routing Policies in Microsoft Teams
Under PSTN usage records, click Add PSTN usage, select the "TELNYX" PSTN usage record, and then click Apply.
Adding PSTN Usage Records
Under ‘Users’ in the tab on the left-hand side, click Policies. Select Edit and assign "TELNYX" Dial plan and Voice routing policy, and then click Apply.
*Assigning the Telnyx dial plan and voice routing policy in Microsoft Teams. *
To provision a user with an on-premises phone number using powershell run the following cmdlet:
Ps> Set-CsUser -Identity "<User name>" -OnPremLineURI tel:<+E164 phone number>
To activate a user with enterprise voice using powershell, run the following cmdlet:
Ps> Set-CsUser -Identity "<User name>" -EnterpriseVoiceEnabled $true
Don’t worry, you’re nearly there!
The last step is to test inbound and outbound calls from Microsoft Teams to verify the service is working. To do this, follow these short steps:
- Call a PSTN number from the Microsoft Teams client. You’ll want to confirm the call connects through Telnyx and that there is two-way audio.
- Call a Telnyx DID assigned to both your new Microsoft Teams Portal Connection and one of your Microsoft Teams users in the Microsoft Admin Center from the PSTN (i.e. a cell phone). Confirm that the call is received in Microsoft Teams and there is two-way audio.
- Check that both calls went through your Telnyx portal account by checking your CDRs present in the Reporting section of the Telnyx Mission Control Portal . If there's any difficulty with making/receiving calls, then please send us an email to [email protected] (including a note of the number dialed and the date/time) and we'll do our best to help you out.
And that’s it. You’ve successfully set up Microsoft Teams Direct Routing using Telnyx.
Dynamic location routing (DLR) is now available for Telnyx Direct Routing customers. Users who wish to set up DLR for Direct Routing need to have:
- Microsoft Teams Emergency Calling configured according to Microsoft specifications
- Associated any number they wish to activate DLR on with a Microsoft Teams Direct Routing SIP Connection.
Based on the user's location at the moment of the 911 call, Telnyx Microsoft Teams Direct Routing Dynamic Location Routing (DLR) offers routing and locating capabilities for emergency calls.
Even though Microsoft Teams handles most configurations and location management, user by user, Telnyx offers the essential enriched connection to the proper Public Safety Answering Point (PSAP) and the caller's location information is made accessible to the emergency operator.
The PIDF-LO (Presence Information Data Format – Location Object) provides a flexible and versatile means to represent location information in a SIP header using an XML schema.
This XML schema has all the relevant information associated with the Microsoft Teams user location, according to the information configured on the Microsoft Teams account.
This information will be added to all 911 calls made through Microsoft Teams Director Routing, on the SIP INVITE, which will be made available to the 911 PSAP.
To get started reach out to a member of our support team for assistance.
Note that Telnyx only supports PIDF-LO LIS and ASSIST methods.
If you’re looking for more information about Telnyx SIP Trunking, take a look at our product page where you’ll find details about our features and pricing.
If you need some extra help, our support team is always on hand to answer any questions.- don’t hesitate to get in touch .