nvoice for microsoft teams service description · 2020. 3. 23. · 5 adding the sbc fqdn into...

Nvoice for Microsoft Teams Technical Documentation


© 2019 NFON AG - All rights reserved. The right of amendment is reserved. Version 1.1 / 12/2019 (EN)

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

Version 1.1

NFON AG Machtlfinger Str. 7

81379 München Tel.: + 49 89 45 3000

www.nfon.com

© 2019 NFON AG - All rights reserved

Subject to change without notice

Version 1.1 / 12/2019 (EN)




1 Table of contents

1 TABLE OF CONTENTS 3

2 INTRODUCTION 4

3 INFORMATION REQUIRED BEFORE YOU GET STARTED 4

4 USING POWERSHELL TO CONFIGURE THE MICROSOFT PHONE SYSTEM 4

4.1 Powershell Prerequisites 4

4.2 Log Into Microsoft Powershell 5

4.3 Pre-Check Before Configuring the SBC FQDN 6

5 ADDING THE SBC FQDN INTO MICROSOFT 365 7

5.1 General Information 7

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

5.3 Verify the new Domain for the SBC 9

5.4 Activate the new Domain 11

6 CONFIGURING THE VOICE ROUTING COMPONENTS IN MICROSOFT 365 14

6.1 PSTN Usage Identity 14

6.2 Voice Route 14

6.3 Voice Routing Policy 14

6.4 Tenant Dial Plan 15

7 CONFIGURING USERS IN MICROSOFT 365 16

7.1 Assign Licenses 16

7.2 Check that the User is hosted on Skype For Business Online 16

7.3 Assigning PSTN Phone Number 16

7.4 Assigning Voice Routing Policy 17

7.5 User Configuration Check 17

8 CONFIGURING NFON PHONE EXTENSION 18

8.1 Adding MS Teams to NFON Extension 18

8.2 Removing MS Teams from NFON Extension 18

.




2 Introduction

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

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

3 Information required before you get started

You will require the following information:

Information Shown in documentation as Example

NFON 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=ms12345678

NFON Support need this Information! (Details Page 8)

• Subject: Kxxxx - MS Teams Direct Routing Activation;

• Teams SBC FQDN: Kxxx-01.customers.teams-pbx.cloud;

• TXT Verification: MS=ms44027887

4 Using Powershell to Configure The Microsoft Phone System

4.1 Powershell Prerequisites

Before downloading and installing the Skype for Business Online PowerShell Module, you need to ensure that Microsoft Visual C++ 2017 is installed - minimum version 14.10.25008. You can install from here: https://visualstudio.microsoft.com/downloads/ - navigate to Other Tools and Frameworks, Microsoft select Visual C++ Redistributable for Visual Studio 2019 then choose the relevant version.

• Download and install the Skype for Business Online PowerShell Module here: https://www.microsoft.com/en-US/download/confirmation.aspx?id=39366

• Installation instructions are available in this Microsoft knowledge base article: Download and install the Skype for Business Online Module module.

https://visualstudio.microsoft.com/downloads/




4.2 Log Into Microsoft Powershell

Don't forget to run PowerShell as an administrator

Import the module Skype for Business Online Connector in your PowerShell environment:

Import-Module "C:\\Program Files\\Common Files\\Skype for Business Online\\Modules\\SkypeOnlineConnector\\SkypeOnlineConnector.psd1"

To configure Microsoft Teams Direct Routing an online session must be created:

Import Modules SkypeOnlineConnector-sfbSession = New-CsOnlineSession




Import the session created earlier:

Import-PSSession $sfbSession

Check that you're properly connected to the correct Office 365 tenant:

Get-CsTenant | select DisplayName, Domains

Check that you have access to the required commands by running the following command:

gcm *CsOnlineVoiceRoute*

4.3 Pre-Check Before Configuring the SBC FQDN

Previously, Microsoft required the PSTN Gateway to be configured on the Customer's Microsoft 365

Get-CsOnlinePSTNGateway

As you can see there is a PSTN Gateway configured. Please remove the configured PSTN Gateway by using the following command:

Remove-CsOnlinePSTNGateway -Identity <SBC FQDN>




5 Adding the SBC FQDN Into Microsoft 365

5.1 General Information

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!

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.

Notes:

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

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

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

https://admin.microsoft.com/

https://admin.microsoft.com/




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;

NFON Support need this Information provided by the verification screen:

• Subject: Kxxxx - MS Teams Direct Routing Activation;

• Teams SBC FQDN: Kxxx-01.customers.teams-pbx.cloud;

• TXT Verification: MS=ms44027887

Click Save and Close;




5.3 Verify the new Domain for the SBC

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




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

Click Finish




Ensure that the status is setup complete

The required domain for your SBC has now been added!

Please contact NFON Support and confirm that the SBC Domain has been successfully verified. Until this has been done, the SBC won’t be activated on NFON Cloud Side!

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

Note: this is a Microsoft requirement over which NFON 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!

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




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




Click Next, and keep Optional Settings as default:

Click Next and finish the User Setup.

Your SBC Domain should be activated now!




6 Configuring the Voice Routing Components in Microsoft 365

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

6.1 PSTN Usage Identity

A PSTN usage links a voice policy to a route. Since all calls will go through the NFON PBX, a simple, global one, will suffice: Set-CsOnlinePstnUsage -Identity Global -Usage @{Add="NFON-PBX- Kxxxx"}

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

6.2 Voice Route

Again, as all calls will go through the NFON PBX, a simple voice route will suffice:

New-CsOnlineVoiceRoute -Identity "Catchall-to-NFON-Kxxxx"-NumberPattern ".*" -OnlinePstnGatewayList Kxxxx-nn.customers.teams-pbx.cloud -Priority 1 -OnlinePstnUsages "NFON-PBX-Kxxxx"

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!

6.3 Voice Routing Policy

The same goes for the Voice Routing Policy:

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




6.4 Tenant Dial Plan

For a full integration in the NFON Cloudya 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

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!

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




7 Configuring Users in Microsoft 365

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

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

NFON is not responsible for the Microsoft licensing!

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

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

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

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

7.3 Assigning PSTN Phone Number

Now assign a phone number to the user:

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

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 NFON Admin portal.

mailto:[email protected]




7.4 Assigning Voice Routing Policy

Grant-CsOnlineVoiceRoutingPolicy -Identity [email protected] -PolicyName "Via-NFON-Kxxxx"

Note: Again, it may be possible that the Voice Routing Policy cannot be assigned (because it can't be found). You may have to wait a few hours for the configuration to be propagated through the Microsoft back-end.

7.5 User Configuration Check

Run the following commands to check that the configuration has been accepted:

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

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

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




8 Configuring NFON Phone Extension

8.1 Adding MS Teams to NFON 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 NFON 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.

8.2 Removing MS Teams from NFON 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.

nvoice for microsoft teams service description · 2020. 3. 23. · 5 adding the sbc fqdn into...

Documents