| Anchor | ||||
|---|---|---|---|---|
|
Microsoft Teams Implementation Guide
| Anchor | ||||
|---|---|---|---|---|
|
...
For more prerequisite details, see Microsoft's document for Plan Direct Routing.
| Anchor | ||||
|---|---|---|---|---|
|
Microsoft 365 Tenant Requirements
Direct Routing requires a custom domain for each Office 365 tenant. For more information, click here.
| Anchor | ||||
|---|---|---|---|---|
|
Licensing Requirements
Direct Routing users must be assigned the following licenses in their Office 365 tenant:
...
The domain names for SBCs must be in the list of domain names registered in the "Domains" section under Settings of the Microsoft 365 admin center menu. The domain of a tenant must be activated and have a Healthy status. Go to the admin dashboard to add domains that are not already created and verified.
...
To learn more about SBC certificates, refer to this Microsoft documentation.
| Anchor | ||||
|---|---|---|---|---|
|
...
1. Connect the SBC with Phone System and validate connection
Using the Microsoft Teams admin center
Add a Peeredge SBC to Direct Routing by clicking Add under the SBC tab in the Direct Routing page under Voice in the Microsoft Teams Admin Center: 
The SBC FQDN entered in the Add an FQDN for the SBC field must exactly match the SBC Certificate's Common Name (CN) or be included in the Subject Alternative Name (SAN).
We recommend using 5061 as the SIP signaling port and enabling the Send SIP options, Forward call history, and Ring phone while trying to find the user. Other settings may need to be enabled based on your specific business requirements. If you plan to enable location based routing or Bypass mode, we recommend that you fully test the SBC integration with these features disabled first.
Note: the TLS connectivity status will be Inactive and the SIP Options status will be Warning until the Peeredge SBC Origination Customer SIP Trunk Group is configured. If you are anxious to see the status of these columns change to Active, you can jump ahead and complete Steps 1 and Step 3 in the Peeredge SBC configuration section.
Using Windows PowerShell
To add a new Direct Routing SBC, use the New-CsOnlinePSTNGateway command. If you forget a mandatory parameter, the cmdlet will prompt you to provide it as in this example. 
To view the configuration of the existing SBCs, use the Get-CsOnlinePSTNGateway command. 
To change the configuration of an existing SBC, use the Set-CsOnlinePSTNGateway command. 
To delete an existing SBC, use the Remove-CsOnlinePSTNGateway command. 
...
Must be configured for Teams Only mode
...
Must be homed online, enabled for enterprise voice and assigned a phone number
Using the Microsoft Teams admin center
Go to Users -> Manage users.
Select a user.
Under Account General information, select Edit.
Under Assign phone number, from the Phone number type drop-down menu, select Direct Routing.
Enter an assigned phone number and a phone number extension if applicable.
Select Apply.
...
| Anchor | ||||
|---|---|---|---|---|
|
Call routing is made up of the following elements:
Call routing policy – Also called a voice routing policy. A container for PSTN usages, which can be assigned to a user or to multiple users.
Example Call routing policy names:
US Only
US Global
Germany Only
Germany Global
Internal
PSTN usages – A container for voice routes and PSTN usages, which can be shared in different voice routing policies.
Example PSTN usage names:
US-Emergency
US-LD
US-INTL
Company-Internal
Voice routes – A number pattern and set of online PSTN gateways to use for calls where the calling number matches the pattern.
In the examples below the Internal voice routes represent routes to company managed third party PBXs used by employees that have not yet migrated to MS Teams.
Example Voice route names and their associated dialed number pattern:
US Emergency ^933$
US LD e164 ^+1[2-9]\d{2}[2-9]\d{6}$
US INTL e164 ^+[2-9]\d+$
Reston Internal ^+170355512\d{2}$
Chicago Internal ^+13125556[43]\d{2}$
Online PSTN gateway - A pointer to the Peeredge SBC that also stores the configuration that is applied when a call is placed through the SBC, such as forward P-Asserted-Identity (PAI) or Preferred Codecs; can be added to voice routes.
Two examples (from Microsoft) of voice routing policies in a call flow.
| Anchor | ||||
|---|---|---|---|---|
|
In the following example we will create 4 PSTN usage records. Use easy to understand names representing types of calls a user is allowed to dial.
Using the Microsoft Teams admin center
Go to Voice -> Direct Routing
Select Manage PSTN usage records in the top right corner
Click + Add and type in the name for the PSTN usage record
Repeat step 3 for any other records
Click the Apply button when finished
...
In the following example we will create 4 voice routes. The dial number patterns are in the form of a regular expression (regex). You can validate your regex patterns.
Using the Microsoft Teams admin center
Go to Voice -> Direct Routing
Click the Voice routes button
Click the Add button
Add the name Non Emergency Test in the voice route in the Add a name for your voice route field
The Priority should be 1
The Dialed number pattern should be ^933$
Click the Add SBCs button and select your Peeredge SBCs and click Apply
Click the ADD PSTN usage… button and select the US-Emergency PSTN Usage and click Apply
Click the Save button.
Repeat steps 3 – 9 for any other voice routes using an appropriate priority and PSTN Usage. When overlapping dialed number patterns exist the more specific pattern must have a higher priority
...
| Anchor | ||||
|---|---|---|---|---|
|
Using the Microsoft Teams admin center
Go to Voice -> Voice routing policies
Click the + Add button
Add the policy name in the Add a name for your voice routing policy
Add an appropriate description
Add one or more PSTN usages
Click the Save button.
Repeat step 2 – 6 for each voice routing policy
...
| Anchor | ||||
|---|---|---|---|---|
|
Using the Microsoft Teams admin center
Go to Voice -> Voice routing policies
Highlight the voice policy you want to assign
Click the Assign button
In the Manage user search box search for the user and click add when found
Click Apply
...
A dial plan is a named set of normalization rules that translate dialed phone numbers by an individual user into an alternate format (typically E.164) for purposes of call authorization and voice routing.
A dial plan consists of one or more normalization rules that define how phone numbers expressed in various formats are translated to an alternate format. The same dial string may be interpreted and translated differently in different dial plans, so depending on which dial plan is assigned to a given user, the same dialed number may be translated and routed differently.
The example below will show how to add a typical US dial plan.
Using the Microsoft Teams admin center
Go to Voice -> Dial plans
Click the +Add button to add a Tenant dial plan
Add the dial plan name (US DP) in the Add a name for you dial plan field
Add an appropriate description (Tenant User Dial plan for US based users)
Add an External dialing prefix (8). Legacy PBX were often configured with 8 or 9 as an external dialing prefix to route the call to in external line.
Set Optimized device dialing to on if you configured an External dialing prefix
Click the Add button under Normalization rules to open the Add new rule pane.
Enter a rule name (Non-Emergency Test Call) in the Name field
Add an appropriate description
Select an appropriate Rule creation mode (Advanced).
Enter a dial pattern to match (^(911)$) in the If condition.
Enter the translation/number manipulation ($1) in the Then do this field.
Optionally, enter a number in the test this rule field to validate the rule. A validated test results in "The translated number is an E.164 phone number".
Click the Save button.
Repeat steps 7 – 14 for any additional Normalization rules.
Click the Save button.
...
The Microsoft SIP Proxy FQDNs and IP Addresses used SIP signaling (and related firewall information) with Microsoft Teams Direct Routing are defined in this section of the Microsoft documentation.
If the Relationships menu is collapsed, click on Relationships from the Tree View in the left panel to view All existing Relationships. If it is expanded, click on All immediately under Relationships
Select the Customer Relationship you created in Step 1
Select the Trunk Groups menu (next to the Relationship Info menu)
Select the + Add Group button in the upper right window
Enter an appropriate name for the Trunk Group in the Name field. For example, From Teams
Select Termination from the drop-down selector in the Direction field
Select Customer from the drop-down selector in the Relationship field
Set the Max PDD to 10 seconds or another appropriate value.
Set the STIR/SHAKEN Treatment to No Treatment
Verify the ANI Normalization and Normalize sipcodes attributes are enabled
Click the Create button.
...