Microsoft Teams Implementation Guide

...

...

• For more prerequisite details, see Microsoft's document for Plan Direct Routing.

...

Direct Routing requires a custom domain for each Office 365 tenant. For more information, click here.

...

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.

...

• Table note The IPs and domain names in this document are used as examples.

...

• To learn more about SBC certificates, refer to this Microsoft documentation.

...

1. Connect the SBC with Phone System and validate connection

Using the Microsoft Teams admin center

To add the Peeredge SBC to Direct Routing:

...

• make sure the user exists in your Microsoft 365 Tenant, and

• assign the Skype for Business Online (Plan 2) and Microsoft Phone System Licenseslicenses.

There are two options for adding a new user to Microsoft 365:

• Create the user in your on-premise Active Directory and sync the user to the cloud.

• Create the user directly in the Tenant using the Microsoft 365 admin center, Microsoft 365 Azure Active Directory Portal, or via PowerShell.

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:

1. Go to Users -> Manage users.

2. Select a user.

3. Under Account General information, select Edit.

4. Under Assign phone number, click the Phone number type drop-down menu and select Direct Routing.

5. Enter an assigned phone number and a phone number extension, if applicable.

6. Click Apply.

...

• Set-CsPhoneNumberAssignment -Identity "<User name>" -PhoneNumber <phone number> -PhoneNumberType DirectRouting

Before

...

phone number assignment

...

After

...

phone number assignment

...

3. Configure call routing

Call routing is made up of 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.

...

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:

1. Go to Voice -> Direct Routing.

2. Select Manage PSTN usage records in the top right corner of the page.

3. Click + Add and enter the name of the PSTN usage record.

4. Repeat step 3 to add more records.

5. 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:

1. Go to Voice -> Direct Routing.

2. Click the Voice routes button.

3. Click the Add button.

4. Add the name Non-Emergency Test in the voice route in the Add a name for your voice route field.

5. Make sure the Priority is 1.

6. Make sure the Dialed number pattern is ^933$.

7. Click the Add SBCs button and select your Peeredge SBCs and then click Apply.

8. Click the ADD PSTN usage button and select the US-Emergency PSTN Usage and then click Apply.

9. Click Save.

10. 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:

1. Go to Voice -> Voice routing policies.

2. Click the + Add button.

3. Add the policy name in the Add a name for your voice routing policy field.

4. Add an appropriate description.

5. Add one or more PSTN usages.

6. Click Save.

7. Repeat steps 2 – 6 for each voice routing policy.

...

• New-CsOnlineVoiceRoutingPolicy "policy name" -OnlinePstnUsages "PSTN Usage"

Image Modified

To edit an existing voice routing policy, use the Set-CsOnlineVoiceRoutingPolicy command:

...

Assign the voice routing policy to a user

Using the Microsoft Teams admin center:

1. Go to Voice -> Voice routing policies.

2. Highlight the voice policy you want to assign.

3. Click the Assign button.

4. In the Manage user search box, search for the user and click add when found.

5. Click Apply.

...

The example below shows how to add a typical US dial plan.

Using the Microsoft Teams admin center:

1. Go to Voice -> Dial plans.

2. Click the +Add button to add a Tenant dial plan.

3. Add the dial plan name (US DP) in the Add a name for your dial plan field.

4. Add an appropriate description (Tenant User Dial plan for US-based users).

5. 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.

6. Set Optimized device dialing to ON if you configured an External dialing prefix.

7. Click the Add button under Normalization rules to open the Add new rule pane.

8. Enter a rule name (Non-Emergency Test Call) in the Name field.

9. Add an appropriate description.

10. Select an appropriate Rule creation mode (Advanced).

11. Enter a dial pattern to match (^(911)$) in the If condition.

12. Enter the translation/number manipulation ($1) in the Then do this field.

13. 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."

14. Click Save.

15. Repeat steps 7 – 14 to add Normalization rules.

16. Click Save.

...

The examples in this document show how to implement rate decks at the Relationship Level.

Configuring the Peeredge SBC

...

Step 1. Create a Customer Relationship
Step 2. Create a Vendor (PSTN Provider) Relationship
Step 3. Create an Origination Customer Trunk Group
Step 4. Create a Termination Customer Trunk Group
Step 5. Create an Origination Vendor Trunk Group
Step 6. Create a Termination Vendor Trunk Group
Step 7. Create and assign Origination Customer Rate Decks
Step 8. Create and assign Termination Customer Rate Decks
Step 9. Create and assign Origination Vendor Rate Decks
Step 10. Create and assign Termination Vendor Rate Decks
Step 11. Create and assign an Origination Customer Routeplan
Step 12. Create and assign a Termination Customer Routeplan

...

1. 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.

2. Select the Customer Relationship you created in Step 1.

3. Click the Trunk Groups menu tab (next to the Relationship Info menu).

4. Click the + Add Group button in the top right corner.

5. Enter an appropriate name for the Trunk Group in the Name field. For example, To Teams.

6. Select Origination on the drop-down menu in the Direction field,

7. Select Customer on the drop-down menu in the Relationship field.

8. Set the Max PDD to 10 seconds (or another appropriate value).

9. Set the B-Timer to 4 seconds (or another appropriate value).

10. Enable these options: Send E.164, Send PAI, Trunk Monitoring, Preserve Caller ID, Ignore Privacy Header, and Early Media.

11. Click Create.

...

Adding a trunk

Now that you have created the Trunk Group and filled in the fields on the Trunk Group Info page:

...

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.

1. 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.

2. Select the Customer Relationship you created in Step 1.

3. Select the Trunk Groups menu tab (next to the Relationship Info menu).

4. Click the + Add Group button in the top right window.

5. Enter an appropriate name for the Trunk Group in the Name field. For example, From Teams.

6. Select Termination on the drop-down menu in the Direction field.

7. Select Customer on the drop-down menu in the Relationship field.

8. Set the Max PDD to 10 seconds or another appropriate value.

9. Set the STIR/SHAKEN Treatment to No Treatment.

10. Verify the ANI Normalization and Normalize sipcodes attributes are enabled.

11. Click Create.

...

1. Click Trunks in the top center of the window.

2. Verify the Trunk type is set to IP.

3. In the IP Address field, enter 52.112.0.0.

4. In the Port field, enter 1.

...

1. This field identifies the source port that the Microsoft SIP Proxy will be using. Since TCP/TLS connections use random ephemeral ports as the source port, the value of 1 represents any source port.

2. In the Protocol field, select TLS 1.2 on the drop-down menu.

3. From the Location field drop-down, select the first available location (e.g. dal1).

4. From the Zones field drop-down, select the appropriate zone (e.g. default).

5. From the Switch IP field drop-down, select the Switch IP.

6. Click the Add Trunk button.

7. Repeat steps 13 - 20 using 52.120.0.0 in the IP Address field.

8. Verify the Status of the trunks is set to enabled.

9. Repeat steps 13 - 22 for every other SBC location (e.g. ash1) in the Location field.

Image Modified

Now that you have completed the Trunk page:

...

1. Click Trunks in the top center of the window.

2. Verify the Trunk type is set to IP.

3. In the IP Address field, enter the vendor's SBC IP address.

4. In the Port field, enter the vendor's SBC IP Port.

5. In the Protocol field, select the appropriate protocol from the drop-down menu.

6. From the Location field drop-down, select the first available location (e.g. dal1).

7. From the Zones field drop-down, select the appropriate zone (e.g. default).

8. From the Switch IP field drop-down, select the Switch IP.

9. Click the Add Trunk button.

10. Repeat steps 14 -21 to add a trunk for each of the vendor's SBCs

11. Repeat steps 14 -22 for every other SBC deployed location (e.g. ash1) shown in the Location drop-down menu.

Media Handling

Now that you have completed the Trunk page, move to the Media Handling page:

...

1. Click Trunks in the upper center of the window.

2. Verify the Trunk type is set to IP.

3. In the IP Address field, enter the vendor's SBC IP address.

4. In the Port field, enter the vendor's SBC IP Port.

5. In the Protocol field, select the appropriate protocol from the drop-down menu.

6. From the Location field, drop-down select the first available location (e.g. dal1).

7. From the Zones field drop-down, select the appropriate zone (e.g. default).

8. From the Switch IP field drop-down, select the Switch IP.

9. Click the Add Trunk button.

10. Repeat steps 2-9 to add a trunk for each of the vendor's SBCs.

11. Repeat steps 2-10 for every other SBC deployed location (e.g. ash1) shown in the Location drop-down menu.

Media Handling

Now that you have completed the Trunk page, move to the Media Handling page:

...

Step 7. Create and assign Origination Customer Rate Decks

...

Step 8. Create and assign Termination Customer Rate Decks

...

Step 9. Create and assign Origination Vendor Rate Decks

...

1. If the Relationships menu is collapsed, click Relationships from the Tree View in the left panel to view All existing Relationships. If it is expanded, click on All immediately under Relationships

2. Select the Vendor Relationship you created in Step 2.

3. Click the Rating menu tab.

4. Select the + Add Rate Deck button in the upper right window.

5. Enter an appropriate name for the Rate Deck in the Name field. See table.

6. Select the appropriate Location, Direction, Relationship, and Deck Type. See table.

7. Click the Add Rating button. Once you add a Rate Deck, the window changes to allow you to upload a CSV file. You can also download a sample CSV file by selecting Download Sample.

8. Click Upload document or drag the CSV file onto the window.

9. Match the column headers in the CSV file to the appropriate fields.

10. Optionally change the Effective Date or add an Expiration Date for the Rate Deck.

11. Click Save & Upload.

12. Repeat Steps 4 – 12 for the US & Canada Origination Vendor Toll-Free Rate Deck.

13. Use one of the two ways to assign Rate Decks to the Origination Vendor Trunk Group.
    

Step 10. Create and assign Termination Vendor Rate Decks

...

1. If the Relationships menu is collapsed, click Relationships in the Tree View in the left panel to view All existing Relationships. If it is expanded, click on All immediately under Relationships

2. Select the Customer Relationship you created in Step 1.

3. Click the Routing menu atbtab.

4. Click the + Add Routeplan button in the Origination section.

5. Add an appropriate name in the Routeplan Name field (e.g. To Teams RP).

6. Click the Create Button.

7. Select the Numbering Page.

8. To add one Telephone number at a time, click the + Add Number button.

9. Enter the e.164 number (less the + symbol) in the Number field.

10. Select the appropriate Number Type (e.g. DID).

11. For DID Number, select the Customer Tier (e.g. 1) and the Vendor Tier (e.g. 1).

12. Click the Add Number button.

...

• Run the Teams Dial Pad is Missing Tests from the Microsoft 365 admin center.

TLS Handshake and Certificate Issues

...

• If the TLS connectivity status shows Active, then the Microsoft SIP Proxy has successfully established a TLS connection to the Peeredge SBC.

• If the TLS connectivity status shows Inactive, then the Microsoft SIP Proxy cannot establish a TLS connection to the Peeredge SBC.

• Verify the FQDN spelling is spelled correctlycorrect.

• Verity the FQDN is resolvable by a Public DNS server, and the IP address is correct.

...

The Peeredge SBC uses the Termination Customer and Origination Vendor Trunk Groups to verify the source of all inbound SIP messages. Specific to a Microsoft Teams deployment, the Termination Customer Trunk Group must have the 52.112.0.0 and the 52.120.0.0 entries configured for Port 1 and the TLS 1.2 Protocol for each SBC.

...