You’ll need a dSIPRouter Cloud account to get Teams Direct Routing set up. Sign up today.
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.
This integration is implemented using dSIPRouter with the Microsoft Teams Module, which interconnects Microsoft Teams with your existing SIP provider. dSIPRouter uses a base domain of customers.dsiprouter.net. You can self-host your own dSIPRouter instance with the Microsoft Teams Module
This guide is broken down into 4 sections:
- dSIPRouter Cloud Info
- Microsoft 365 Admin Center: dSIPRouter Subdomain Setup
- Microsoft Teams: Direct Routing Setup
- Making Test Calls
In order to use dSIPRouter Cloud as a PSTN provider for Microsoft Teams Direct Routing you’ll will receive the following information from your customer sales representive:
- Unique hostname in the customers.dsiprouter.net domain
We support Bring Your Own Carrier (BYOC) so you can provide us:
- Your SIP Provider information
- A phone number attached to the SIP PRovider and we will configure it so that calls are terminated to your Microsoft Teams Tenant.
In the future you will be able to login to the dSIPRouter Portal and configure this information.
Now that you have the dSIPRouter Cloud configured, you’ll need to activate the *customers.dsiprouter.net 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 when the dSIPRouter 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.
Send a screenshot of the Verify Domain screen to the dSIPRouter Cloud account team using [email protected]
Once the account team responds, 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 provided by the dSIPRouter Cloud account team
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 dSIPRouter Cloud subdomain (i.e yyyy.customers.dsiprouter.net), 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 dSIPRouter 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 provided by the dSIPRouter Cloud team. 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 dSIPRouter, 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 SIP Carriers requirements.
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 dSIPRouter as the name and add a description.
Adding Voice Routing Policies in Microsoft Teams
Under PSTN usage records, click Add PSTN usage, select the "dSIPRouter" PSTN usage record, and then click Apply.
Adding PSTN Usage Records
Under ‘Users’ in the tab on the left-hand side, click Manage Users. Select a user, click on Policies Tab, select Voice routing policy, click Edit, select dSIPRouter and click Apply.
Assigning the dSIPRouter dial plan and voice routing policy in Microsoft Teams
You can assign a DID/phone number either using the Microsoft Teams Portal or via Powershell. The steps for both are below:
Under ‘Users’ in the tab on the left-hand side, click Manage Users. Select a user, click on Edit within the Assigned phone number section, add/or change phone number based on the number provided by the dSIPRouter Cloud account team, click Apply
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
- Login to your Microsoft Teams client and place an outbound call
- Use the DID/Phone Number assigned to the user in the above step to place an inbound call