MICROSOFT TEAMS FOR DIGITAL PHONE

MICROSOFT TEAMS FOR DIGITAL PHONE TECHNICAL DOCUMENTATION

Version 1.1

Microsoft Teams for Digital Phone Technical Documentation

2

1 TABLE OF CONTENTS 2 2 INTRODUCTION 3 3 ADDING THE SBC FQDN INTO MICROSOFT 365 3

3.1 General Information 3 3.2 Add the SBC FQDN as a new domain on Microsoft 365 and obtain the verification code 4 3.3 Contact O2 Support 6 3.4 Verify the new Domain for the SBC 6 3.5 Activate the new Domain 8

4 USING POWERSHELL TO CONFIGURE THE MICROSOFT PHONE SYSTEM 11 4.1 Powershell Prerequisites 11 4.2 Check Execution Policy 11 4.3 Signing in, Starting and Importing a New Session in PowerShell 12

5 CONFIGURING THE VOICE ROUTING COMPONENTS IN MICROSOFT 365 14 5.1 PSTN Usage Identity 14 5.2 Voice Route 14 5.3 Voice Routing Policy 14 5.4 Tenant Dial Plan 15 6 CONFIGURING USERS IN MICROSOFT 365 16

6.1 Assign Licenses 16 6.2 Check that the User is hosted on Skype For Business Online 16 6.3 Assigning PSTN Phone Number 16 6.4 Assigning Voice Routing Policy 17 6.5 User Configuration Check 17

7 CONFIGURING DIGITAL PHONE PHONE EXTENSION 18 7.1 Adding MS Teams to Digital Phone Extension 18 7.2 Removing MS Teams from Digital Phone Extension 18

.

1 Table of contents


"Microsoft Teams for Digital Phone" is a bolt-on that supplements the "Telephone System" service with a Voice over IP (VoIP) interface into Microsoft Phone System. Microsoft Teams for Digital Phone uses Microsoft’s Direct Routing solution to enable PSTN services from within Microsoft Teams

This document provides the technical implementation of “ Microsoft Teams for Digital Phone”

3.1 General Information

3.2 Add the SBC FQDN as a new domain on Microsoft 365 and obtain the verification code

In the Microsoft 365 Admin Center, go to Settings > Domains > Add domain. In the Enter a domain you own box, type the FQDN of the SBC for this tenant. In the example image below the FQDN is Kxxxx- 01.customers.teams-pbx.cloud. Click:Next

4

NFON AG · Machtlfinger Str. 7 · 81379 München · Tel.: + 49 89 45 3000 · nfon.com

In this documentation: In the commands examples below, we will add the PSTN Gateway Domain Kxxxx- nn.customers.teams-pbx.cloud in the end-customer Microsoft 365 tenant, e.g. Kxxxx-01.customers.teams- pbx.cloud. This will allow customers with multiple Microsoft 365 tenants use one K account for Direct Routing.

Ensure that you have appropriate rights in the customer tenant. You can only add new domains if you signed into the Microsoft 365 admin center as a Global Administrator!

• O2 will provide you with a Session Border Controller (SBC) Fully Qualified Domain Name (FQDN) for each K account;

• If you have multiple Digital Phone K accounts, you will need to repeat the steps listed below for each K account.

2 Introduction

3 ADDING THE SBC FQDN INTO MICROSOFT 365

https://admin.microsoft.com/

https://admin.microsoft.com/

5


As the SBC FQDN has never been registered as a domain in the Microsoft 365 tenant, in the next step, you will need to verify the domain. Select Add a TXT record instead;

O2 Support need this Information!

• Subject: Kxxxx - MS Teams Direct Routing Activation; • Teams SBC FQDN: Kxxx-01.customers.teams-pbx.cloud; • TXT Verification: MS=ms44027887

Click Save and Close;

6


3.3 Contact O2 Support

You will require the following information: Information Shown in documentation as Example Digital Phone PBX K account Kxxxx KABCD PSTN Gateway SBC FQDN This will be provided by NFON

Kxxxx-nn.customers.teams-pbx.cloud KABCD-01.customers.teams- pbx.cloud

Customer Default Domain for the Office 365 Tenant

Domain nfon.com

MS 365 - Domain validation TXT Record

MS=ms44027887

3.4 Verify the new Domain for the SBC

O2 support will confirm by email when the TXT record required for verification has been created.

Once confirmed, go back to Setup – Domain, click on the domain name and start the Setup:

Click Verify, for domain verification.

7


On the Choose your online services page, clear all options and click Next:

Click Finish

8


Ensure that the status is setup complete

3.5 Activate the new Domain

After you register the SBC FQDN as a domain on Microsoft 365, you will need to activate it by adding at least one user and assigning a SIP address with the FQDN portion of the SIP address matching the created SBC FQDN Domain on your Microsoft 365 tenant.

Create Activation User

Go to Users > Active users, click on Add a user

First name Kxxxx SBC

Last name Activation

Display name Kxxxx SBC Activation

Username / Domain sbcactivation / kxxxx--01.customers.teams-pbx.cloud

Password settings Auto Generate

License required Assign at least E1 License

The required domain for your SBC has now been added! Please contact O2 Support and confirm that the SBC Domain has been successfully verified. Until this has been done, the SBC won’t be activated on O2 Cloud Side!

Note: this is a Microsoft requirement over which O2 has no control! At the time of writing this documentation this “Activation User” needs to be kept. It cannot be deleted, not deactivated and must be licensed!

9


Click Next, Assign the required licenses as shown in the table above:

10


Click Next, and keep Optional Settings as default:

Click Next and finish the User Setup.

Your SBC Domain should be activated now!

11


4.1 Powershell Prerequisites

Uninstalling the Skype for Business Online Connector Module: If you have previously used the Skype for Business Online Connector module, you must uninstall it. To do this, in Control Panel, go to Programs and Features, select Skype for Business Online, Windows PowerShell Module, and then select Uninstall.

4.2 Check Execution Policy

Teams PowerShell Module requires PowerShell 5.1 or higher. Install the latest version of PowerShell available for your operating system. Installation instructions are available in this Microsoft knowledge base article: https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install#install-the-teams-powershell-module

Get-ExecutionPolicy -List Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process

4 Using Powershell to Configure The Microsoft Phone System

https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install#install-the-teams-powershell-module

https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install#install-the-teams-powershell-module

12


4.3 Signing in, Starting and Importing a New Session in PowerShell

Don't forget to run PowerShell as an administrator

The following command can be copied and pasted into the PowerShell window and run: $credential = Get-Credential Connect-MicrosoftTeams -Credential $credential $session = New-CsOnlineSession -Credential $credential Import-PsSession $session Entering the code above it will ask for the admin login credentials as shown in the image below:

• Enter your password • Select Sign in

After signing in, a loading bar will load along the top of the PowerShell window and then output something similar to the result below: Import-PSSession $sfbSession cmdlet Get-Credential at command pipeline position 1 Supply values for the following parameters: Credential Account : [email protected] ... ... Check that you're properly connected to the correct Office 365 tenant G et-CsTenant | select DisplayName, Domains

This will display the name of the O365 tenant and the domains configured on the account.

13


Check that you have access to the required commands by running the following command: gcm *CsOnlineVoiceRoute* This will output the following:

gcm *CsOnlineVoiceRoute* CommandType Name Version Source ----------- ---- ------- ------ Function Get-CsOnlineVoiceRoute 1.0 tmp_r5ktxabt.pr4 Function New-CsOnlineVoiceRoute 1.0 tmp_r5ktxabt.pr4 Function Remove-CsOnlineVoiceRoute 1.0 tmp_r5ktxabt.pr4 Function Set-CsOnlineVoiceRoute 1.0 tmp_r5ktxabt.pr4

This will show functions you have access to. If it matches with the above then you can begin configuring the tenant.

See also: https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install

https://docs.microsoft.com/en-us/microsoftteams/teams-powershell-install

14


5.1 PSTN Usage Identity A PSTN usage links a voice policy to a route. Since all calls will go through the Digital Phone PBX, a simple, global one, will suffice:

5.2 Voice Route Again, as all calls will go through the Digital Phone PBX, a simple voice route will suffice:

5.3 Voice Routing Policy The same goes for the Voice Routing Policy:

New-CsOnlineVoiceRoutingPolicy -Identity "Via-NFON-Kxxxx"-OnlinePstnUsages "NFON-PBX-Kxxxx"

In the commands examples below, replace Kxxxx with the correct Digital Phone K account value. You will need to use Microsoft PowerShell in order to complete the configuration below.

5 Configuring the Voice Routing Components in Microsoft 365

Note: It might take up to 2 hours or so for the new PSTN Usage to sync in Microsoft back-end

Sometimes this command will not work immediately because the Microsoft Office 365 back-end hasn't propagated the PSTN Usage yet. Just leave it at this stage for at least two hours (maximum 24 hrs), then try again. If it still doesn't work then, double check everything or delete the configuration and reconfigure it from scratch!

Kxxxx-nn.customers.teams-pbx.cloud -Priority 1 -OnlinePstnUsages "NFON-PBX-Kxxxx"

15


5.4 Tenant Dial Plan For a full integration in the Digital Phone PBX, we also need to create a Tenant Dial Plan, so the numbers will be normalized, and some special characters don't get interpreted by the Microsoft Teams Cloud system.

$Rule1 = New-CsVoiceNormalizationRule ` -Identity “Global/NFON Prefix-1-9” ` -Description "Prefix-1-9" ` -Pattern '^([1-9]\d+)$' -Translation '$1' ` -InMemory $Rule2 = New-CsVoiceNormalizationRule ` -Identity “Global/NFON Prefix-Star” ` -Description "Prefix-Star" ` -Pattern '^(\*\d+(\d|\*|\#)*)$' -Translation '$1' ` -InMemory $Rule3 = New-CsVoiceNormalizationRule ` -Identity “Global/NFON Prefix-DoubleStar” ` -Description "Prefix-DoubleStar" ` -Pattern '^(\*\*\d+)$' -Translation '$1' ` -InMemory $Rule4 = New-CsVoiceNormalizationRule ` -Identity “Global/NFON Prefix-Hash” ` -Description "Prefix-Hash" ` -Pattern '^(\#\d+)$' -Translation '$1' ` -InMemory Set-CsTenantDialPlan ` -Identity "Global" ` -NormalizationRules $rule1,$rule2,$rule3,$rule4

The Office 365 tenant Phone System is now ready for making and receiving calls.

Note that we're adding these normalization rules to the tenant Global/Default dial-plan. If you don't wish to do so, you can create a new dial-plan, but additional normalization rules will be required if you decide to do so!

16


6.1 Assign Licenses When creating additional teams users or editing existing teams users via the Microsoft Admin Center, the global administrator needs to ensure the necessary licenses for the Microsoft Phone System is assigned. This is usually an E5 plan license or an E1/E3 plan license with an additional Phone System license.

O2 is not responsible for the Microsoft licensing!

6.2 Check that the User is hosted on Skype For Business Online First, you must check that the user is hosted on SfB Online (part of the MS Teams Phone System still uses Skype for Business):

The command above should return a value for the registrar pool such as: sippoolLONGB112.infra.lync.com

6.3 Assigning PSTN Phone Number Now assign a phone number to the user:

Note: The phone number (shown above as +441632960789) must be in E.164 format, without any spaces or punctuation. This number must match the DID that has been configured for the user's extension in the O2 Admin portal.

Microsoft PowerShell in order to complete the configuration below.

6 Configuring Users in Microsoft 365

Note: The username can be entered as "Joe Blog" or [email protected]

Set-CsUser -Identity [email protected] -EnterpriseVoiceEnabled $true -HostedVoiceMail $false - OnPremLineURI tel:+441632960789

mailto:[email protected]



17


6.4 Assigning Voice Routing Policy

6.5 User Configuration Check Run the following commands to check that the configuration has been accepted:

• LineURI and OnPremLineURI should both return the user DDI / Phone Number in E.164 format and be identical;

• OnlineVoiceRoutingPolicy should return the voice policy assigned to this Office 365 user (e.g. Via- NFON-PBX-Kxxxx)

The user DDI mentioned above should match the assigned DDI for that user's extension in the O2 Admin Portal.

may have to wait a few hours for the configuration to be propagated through the Microsoft back-end.

Get-CsOnlineUser -Identity [email protected] |select UserPrincipalName, DisplayName, RegistrarPool, OnlineVoiceRoutingPolicy, LineURI, OnPremLineURI, EnterpriseVoiceEnabled, HostedVoicemail

The dial pad in Microsoft Teams should appear. However, this might take up to 24 hours (time for Microsoft back-end to synchronise). The user might need to log off and on, but not always.



Nvoice for Microsoft Teams Technical Documentation

18

7.1 Adding MS Teams to Digital Phone Extension To ensure the calls to and from the Teams client are routed correctly, the following sections on the phone extension will also need to be configured in the O2 Admin Portal. Please check that the assigned number is the same number that was configured via PowerShell.

Add the corresponding Inbound Trunk Number to the MS Teams section. Unlike deskphones, you do not need to add or remove the MS Teams device manually. Once the Skype for Business / Microsoft Teams section is configured and then saved, the MS Teams device will be added to the phone extension automatically.

7.2 Removing MS Teams from Digital Phone Extension This works in the same principle as adding the device. If you press the delete (trash bin) icon next to the entry in the Skype for Business / Microsoft Teams section, then save the change, it will remove the MS Teams device automatically.

7 Configuring Digital Phone Phone Extension

Nvoice for Microsoft Teams Technical Documentation

19

Documents

MICROSOFT TEAMS FOR DIGITAL PHONE