| Anchor | ||||
|---|---|---|---|---|
|
Microsoft Teams Implementation Guide
| Anchor | ||||
|---|---|---|---|---|
|
...
For more prerequisite details, see Microsoft's document for Plan Direct Routing.
| Anchor | ||||
|---|---|---|---|---|
|
...
Direct Routing requires a custom domain for each Office 365 tenant. For more information, click here.
| Anchor | ||||
|---|---|---|---|---|
|
...
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 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
To add the Peeredge SBC to Direct Routing:
...
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, click the Phone number type drop-down menu and select Direct Routing.
Enter an assigned phone number and a phone number extension, if applicable.
Click Apply.
...
| Anchor | ||||
|---|---|---|---|---|
|
3. Configure call routing
Call routing has 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. Sample Call routing policy names include:
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. Sample PSTN usage names include:
US-Emergency
US-LD
US-INTL
Company-Internal
Voice routes
A number pattern and set of online PSTN gateways 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. Sample Voice route names and their associated dialed number patterninclude:
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
This is a pointer to the Peeredge SBC that also stores the configuration which is applied when a call is placed through the SBC, such as forward P-Asserted-Identity (PAI) or Preferred Codecs. The pointer can be added to voice routes.
Two examples (from Microsoft) of voice routing policies in a call flow.
...
Create the PTSN usages
In the following example, we create four PSTN usage records. We suggest admins use easy-to-understand names representing the 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 of the page.
Click + Add and enter the name of the PSTN usage record.
Repeat step 3 to add more records.
Click Apply to finish.
...
In the following example, we create four 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.
Make sure the Priority is 1.
Make sure the Dialed number pattern is ^933$.
Click the Add SBCs button and select your Peeredge SBCs and then click Apply.
Click the ADD PSTN usage button and select the US-Emergency PSTN Usage and then click Apply.
Click Save.
Repeat steps 3 – 9 for any other voice routes using an appropriate priority and PSTN Usage. When overlapping dialed number patterns exist, give the more specific pattern higher priority.
...
Create the voice routing policy
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 field.
Add an appropriate description.
Add one or more PSTN usages.
Click Save.
Repeat steps 2 – 6 for each voice routing policy.
...
Assign the voice routing policy to a user
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.
...
The example below shows 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 your dial plan field.
Add an appropriate description (Tenant User Dial plan for US-based users).
Add an External dialing prefix (8). Legacy PBX was often configured with 8 or 9 as an external dialing prefix to route the call to an 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 Save.
Repeat steps 7 – 14 to add Normalization rules.
Click Save.
...
Login to your Peeredge SBC Portal.
Go to the Tree View in the left panel and click Relationships if the menu is collapsed. If the Tree View is expanded, click on All.
Click the + Add Relationship button in the top right.
Add the Customer (or meaningful) name in the Relationship Name field.
Leave the Send trunk group notification checked.
Fill in the optional fields.
Add a company logo (optional).
When complete, click the Add Relationship button.
...
Insert Video Demo Link? 9. Scroll through the Relationships list and click the new Relationship name.
...
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.
Go to the Tree View in the left panel and click Relationships if the menu is collapsed. If the Tree View is expanded, click All.
Select the Customer Relationship you created in Step 1.
Select the Trunk Groups menu tab (next to the Relationship Info menu).
Click the + Add Group button in the top right window.
Enter an appropriate name for the Trunk Group in the Name field. For example, From Teams.
Select Termination on the drop-down menu in the Direction field.
Select Customer on the drop-down menu 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 Create.
...
The Dialpad should be visible in the Calls --> Phone window in the Teams Client.
Check to see if the Teams User is assigned Skype for Business Online (Plan 2) license and the Microsoft Phone System.
Check to see if the Teams User has been assigned a Telephone number.
Check to see if the Teams User has been assigned a Voice Routing Policy.
...
Termination filters All CDRs from Termination Customer Trunk Group (ingress call leg) to a Termination Vendor (egress call leg) (e.g. PSTN Outbound Calls).
CDR Export Download exported CDRs.
Origination filters All CDRs from an Origination Vendor Trunk Group (ingress call leg) to an Origination Customer (egress call leg) (e.g. PSTN Inbound Calls).
Live Calls Display all calls in progress. Optionally, select and kill individual calls.
The Time Filter This drop-down offers several command time frames to filter on.
The Date/Time selector Defines Defines a specific start date and time and end date and time.
All will display CDRs Based on the selected direction (Termination/Origination) and selected dime filters.
Completed Further filter the CDRs to just those with the 2xx Release Code.
Failed Further filter the CDRs to those with a 4xx/5xx/6xx Release Code.
The Table Columns button Select columns to display and arrange display order.
Filter button Refine your filter to specific Customer Trunk Groups, Vendor Trunk Groups, Minimum and Maximum call durations, a specific ANI, Dialed Number, SIP Call ID, or Cause Code.
Displays the CDRs that match the filter criteria. The Search box allows you to further filter on any text string within this set of CDRs.
Export Initiate an export task and create a CSV file containing all CDRs that match your filter criteria. Use the CDR Export to download the CDRs once they are generated.
Lookup LRN/Spam – XXXThis button can be used to lookup an LRN associated to a specific DNIS or to check is a specific DNIS is in the Spam database.
If you click the vertical ellipsis to the right of an individual CDR, the portal presents three options.
...