IP Office

Deploying MS Teams Direct Routing with

IP Office

Issue 01b - (Tuesday, November 23, 2021)

 6.7.2 Assigning
............................................................................
an Emergency Policy to Users 53
Contents 7. Azure Active Directory Synchronization
1. IP Office and MS Teams 7.1 Preventing Manual
.....................................................................
URI Editing 57
1.1 MS Teams Call Routing.....................................................................
Options 7 7.2 Enabling Directory
.....................................................................
Synchronization 57
1.2 User Types ..................................................................... 8 7.3 Configuring Azure
.....................................................................
Active Directory App Registration 58
1.3 Scenarios ..................................................................... 9 7.4 Configuring a Teams
.....................................................................
Administrator 59
1.3.1 Integration
............................................................................
with Direct Routing 9 7.5 Creating User and
.....................................................................
Extension Templates 60
1.3.2 Integration with Direct Routing and Azure 7.6 Creating User Provisioning
.....................................................................
Rules 61
............................................................................ 10
Active Directory 7.7 Setting Up a Direct Routing Synchronization
1.4 Telephone and .....................................................................
Extension Numbers 11 Process ..................................................................... 62
1.5 Requirements ..................................................................... 13
1.6 Known Call Limitations
..................................................................... 13 8. Configuring the ASBCE
8.1 Example Schematic ..................................................................... 67
2. MS Teams Direct Routing 8.2 Information Required..................................................................... 67
2.1 Direct Routing Components
..................................................................... 17 8.3 Get the ASBCE .....................................................................
Version 68
2.1.1 Dial Plans
............................................................................ 17 8.4 Obtain the ASBCE .....................................................................
Certificates 69
2.1.2 Regular
............................................................................
Expressions 18 8.4.1 Downloading
............................................................................
the IP Office Root Certificate 70
2.1.3 Voice............................................................................
Routing Policies 18 8.4.2 Generating an Identity Certificate in IP Office
2.1.4 Voice............................................................................
Routes 18 Web Control ............................................................................ 71
2.1.5 Emergency
............................................................................
Routing Policies 19 8.4.3 Generating an Identity Certificate in IP Office
Web Manager ............................................................................ 72
2.1.6 PSTN............................................................................
Usages 19
8.4.4 Extracting the ASBCE Private Key and Identity
2.1.7 SBC ............................................................................ 19 Certificate ............................................................................ 73
2.1.8 MS Teams
............................................................................
Line 19 8.5 Adding a Root Certificate
.....................................................................
to the ASBCE 74
2.2 Direct Routing Call.....................................................................
Flow 20 8.6 Adding an Identity .....................................................................
Certificate to the ASBCE 75
2.3 Direct Routing Flowchart
..................................................................... 21 8.7 Define the IP Office.....................................................................
Server Interworking Profile 76
2.4 SBC Verification..................................................................... 22 8.8 Define the MS Teams .....................................................................
Server Interworking Profile 78
8.9 Create a TLS Client .....................................................................
Profile for the IP Office 80
3. Example Direct Routing Scenario
8.10 Create a TLS Client.....................................................................
Profile for MS Teams 81
3.1 Proposed Direct.....................................................................
Routing Configuration 25
8.11 Create the TLS.....................................................................
Server Profiles 82
3.2 Callflow ..................................................................... 27
8.12 Create the SIGMA .....................................................................
Script Files 83
3.3 Simplified Callflow
..................................................................... 28
8.13 Upload the SIGMA .....................................................................
Scripts 85
3.4 Multiple SBC Callflow
..................................................................... 29
8.14 Create a SIP Server.....................................................................
for the IP Office 86
4. Configuring the Users in MS Teams 8.15 Create a SIP Server.....................................................................
for MS Teams 88
4.1 User Configuration
.....................................................................
in MS Teams 32 8.16 Define a SIP Call .....................................................................
Routing Profile for the IP Office 90
4.2 Checking MS Teams
.....................................................................
User Numbers 33 8.17 Create a URI Group .....................................................................
for IP Office Extensions 91
8.18 Define a SIP Call .....................................................................
Routing Profile for MS Teams 92
5. Configuring the IP Office for MS Teams 8.19 Configure Topology .....................................................................
Hiding for the IP Office 94
5.1 Manually Adding.....................................................................
MS Teams+IP Office Users 36 8.20 Configure Topology .....................................................................
Hiding for MS Teams 95
5.2 Manually Adding Directory Entries for MS Teams 8.21 Define the Media .....................................................................
Rules for the IP Office 96
Only Users ..................................................................... 37 8.22 Define the Media .....................................................................
Rules for MS Teams 97
5.3 Adding an MS Teams
.....................................................................
Line 38 8.23 Create the Endpoint.....................................................................
Policy Groups 99
5.4 Check Collaboration
.....................................................................
Service 38 8.24 Create the SIP .....................................................................
Signaling Interfaces 100
8.25 Create the SIP .....................................................................
Media Interfaces 101
6. Configuring MS Teams Direct Routing
8.26 Configure the.....................................................................
Server Flow for IP Office 102
6.1 Adding an MS Teams .....................................................................
Line 43
8.27 Configure the.....................................................................
Server Flow for MS Teams 104
6.2 Verify the SBC Domain
..................................................................... 44
8.28 ASBCE Flowchart ..................................................................... 105
6.3 Adding the ASBCE .....................................................................
to MS Teams 45
6.4 Creating Dial Plans..................................................................... 46 9. Using Regular Expressions (regex)
6.4.1 Creating
............................................................................
a Dial Plan 46 9.1 Interpreting Regex
.....................................................................
Strings 109
6.4.2 Assigning
............................................................................
a Dial Plan to Users 47 9.2 Regex Syntax ..................................................................... 110
6.5 Creating Voice Routing
.....................................................................
Policies 48 9.3 Telephone Number
.....................................................................
Examples 111
6.5.1 Creating
............................................................................
a Voice Routing Policy 48 9.4 Digit Translations
..................................................................... 111
6.5.2 Assigning
............................................................................
a Voice Routing Policy to a User 49
6.6 Creating Voice Routes
..................................................................... 50 10. Troubleshooting
6.6.1 Creating
............................................................................
a Voice Route 51 10.1 IP Office System
.....................................................................
Status 114
6.7 Configure Emergency.....................................................................
Calling 52 10.2 IP Office System
.....................................................................
Monitor 115
6.7.1 Configuring
............................................................................
an Emergency Policy 52 10.3 ASBCE SIP Tracing
..................................................................... 116

Deploying MS Teams Direct Routing with IP Office Page 2

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Contents
10.3.1 Tracing
............................................................................
Address 116
10.3.2 Tracing
............................................................................
SIP Calls on the ASBCE 117
10.3.3 Downloading
............................................................................
Traces from the ASBCE 117
10.4 Monitoring Direct
.....................................................................
Routing 118

11. Document History

Index ...............................................................................125

Deploying MS Teams Direct Routing with IP Office Page 3

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 4
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 1.
IP Office and MS Teams

Deploying MS Teams Direct Routing with IP Office Page 5

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
1. IP Office and MS Teams
These notes cover the integration of MS Teams direct routing with IP Office systems. This is supported with IP
Office R11.1 FP2 and higher.

Support covers:
· MS Teams
MS Teams licensed through Microsoft with licenses assigned to users for features required. The free version of
MS Teams is not supported.
· Direct Routing
MS Teams Direct routing using an ASBC E R8.1.3.
o Scenarios covered include calls by MS Teams only users, IP Office only users, and users who are
simultaneous MS Teams+IP Office users.
o These notes should be used in conjunction with the Microsoft documentation. Refer to
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-landing-page

· Azure Active Directory Synchronization

MS Teams uses Azure Active Directory to store MS Teams user information. IP Office R11.1 FP2 supports
integration with Azure Active Directory to perform a range of actions:
o Automatically add Azure Active Directory user names and numbers to the IP Office system directory.

o Automatically create, update and delete IP Office users matching users in the Azure Active Directory.

o Automatically assign a voice routing policy to MS Teams users.

· Avaya Calling
Avaya calling is an alternation method of integrating MS Teams and IP Office. For details, refer to the separate
"Deploying Avaya Calling for MS Teams with IP Office" manual.

Overview
7
o MS Teams C all Routing Options
8
o User Types
9
o Scenarios
11
o Telephone and Extension Numbers
13
o Requirements
13
o Known C all Limitations

Deploying MS Teams Direct Routing with IP Office Page 6

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 IP Office and MS Teams:

1.1 MS Teams Call Routing Options

MS Teams users can make calls to normal PSTN telephone numbers using the following options. For more details,
refer to https://docs.microsoft.com/en-us/microsoftteams/pstn-connectivity
· Microsoft Calling Plans
PSTN calls are routed over Microsoft's own PSTN network, using Microsoft’s price plans for national and
international calls.

· Avaya Call
This method uses a MS Teams plug-in called Avaya C all. It links the user's MS Teams client with their Avaya
Workplace client. For details, refer to the separate "Deploying Avaya Calling for MS Teams with IP Office"
manual.
· Direct Routing
PSTN calls are routed via a third-parties SBC , in this case an ASBC E connected to the IP Office. This allows
calls to use PSTN trunks connected to the IP Office.
· Operator Connect
This option is similar to Direct Routing. However, all administration and services are run through the
infrastructure of a PSTN provide who is part of the Microsoft Operator C onnect program, using their SBC s and
SIP trunks.

Deploying MS Teams Direct Routing with IP Office Page 7

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
1.2 User Types
Within this documentation, we will refer to the following different types of users:

User Type Description

IP Office only user This type of user:

· Is configured only on the IP Office system with an IP Office extension number

· Does not require any specific IP Office user profile to interact with MS Teams
users.
· C an see and call MS Teams users from the IP Office system directory.

MS Teams only user This type of user:

· Is only configured in MS Teams with a MS Teams telephone number and/or
extension number.
· Requires a MS Teams license (Microsoft 365 Business Voice without C alling
Plan).

· Does not need any IP Office license or subscription.

· C an make and receive calls to and from IP Office extensions.

· C annot be part of IP Office features such as hunt groups, since they do not exist
as a user/extension record in the IP Office configuration

MS Teams+IP Office This type of user:

user
· Is configured as a user in both MS Teams and the IP Office.

· Has the same extension number on MS Teams and IP Office.

· C an also have a MS Teams telephone number.

· Requires a MS Teams license (Microsoft 365 Business Voice without C alling Plan).

· Requires an IP Office license or subscription for the following:

· On systems using PLDS licensing: MS Teams+IP Office users are

supported by the Office Worker, Teleworker and Power User profiles.
· On subscription mode systems: MS Teams+IP Office users are supported
by the UC User profile.
· Incoming calls alert both their MS Teams client and IP Office extension. The user
can use either for calls with other MS Teams and IP Office users.

· The user can be included in the configuration of other IP Office features such as
hunt groups, park/page, etc.

How are theses user types created?

In addition to manually creating the users, the creation of the different types of users can be partial automated
using Azure Active Directory synchronization. This allows the IP Office to create and update users in its own
configuration based on the Azure Active Directory user settings.
· Within Azure Active Directory, different groups can be defined for different types of user. Separate
synchronization rules can then be configured on the IP Office system for the different groups.

Deploying MS Teams Direct Routing with IP Office Page 8

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 IP Office and MS Teams: User Types

1.3 Scenarios
The integration with MS Teams covered in this documentation make use of the following new components:
·
9
· Direct Routing support
MS Teams users can be licensed to make and receive PSTN calls by a number of routes. Direct routing allows
that operation to be via any of a number of Microsoft accredited SBC s. For IP Office support, ASBC E R8.1.3
can be used.
10
· Direct Routing support and Azure Active Directory synchronization
IP Office R11.1 FP2 and higher can connect to Azure Active Directory in order to obtain MS Teams user
information. This can be used to update directory information and/or create IP Office users.

1.3.1 Integration with Direct Routing

MS Teams direct routing uses a third-party SBC to route calls to and from MS Teams users. This replaces the need
to use Microsoft calling plans.
For IP Office systems, direct routing can be done using an ASBC E R8.1.3.

Deploying MS Teams Direct Routing with IP Office Page 9

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
1.3.2 Integration with Direct Routing and Azure Active Directory
9
This scenario builds on the previous direct routing integration by adding Azure Active Directory synchronization.

This allows the following:

· Automatically add MS Teams user contact details to the IP Office system directory.

· C reate and maintain IP Office users from user records in Azure Active Directory. Those users can be ordinary
IP Office users and/or MS Teams+IP Office users.
· Select and assign the voice routing policy to use to MS Teams users.

Deploying MS Teams Direct Routing with IP Office Page 10

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 IP Office and MS Teams: Scenarios

1.4 Telephone and Extension Numbers

Within MS Teams, a user can have a telephone number and/or extension number. Either can be used by MS Teams
to route calls to that user. For more information, refer to https://docs.microsoft.com/en-
us/microsoftteams/manage-phone-numbers-landing-page

Number Formats
Before looking at how the numbers are used, it is important to look at the formats used to enter and display the
numbers. MS Teams-IP Office integration involves a number of different interfaces, each with slight variances on
how it displays the same number.

Interface Telephone Number and Telephone Number Extension

Extension Only Only

Azure AD Admin Portal +441632768402 x402 +441632768402 x402

441632768402 x402 441632768402

Teams Admin Portal tel:441632768402;ext=402 tel:441632768402 402

IP Office Admin MS Teams URI 441632768000;ext=402 441632768402 +402

Menu
System Directory 441632768402-402 441632768402 +402
Number

MS Teams Client (1632) 768 8402 extn 402 (1632) 768 8402 +402

IP Office SIP URI[1] +441632768402;ext=402 +441632768402 –

1. The IP Office also adds the required protocol prefix and domain/port suffix elements (for example sip:
+441632768402;ext=402@sip.pstnhub.microsoft.com:5061).

Telephone Numbers
This documentation assumes that incoming calls for all telephone numbers are routed from the PSTN to the IP
Office. It does not cover scenarios where the customer also has telephone numbers routed directly to MS Teams
through Microsoft calling plans.
· Note that the expected telephone number is a full number including international country code but no country
specific international dialing prefix (except+ where indicated).
· If the customer has telephone numbers registered to Microsoft calling plans, those numbers need to migrated
to one of the IP Office system's line providers.
· Microsoft recommend that phone numbers are configured as full E.164 phone numbers with country code. MS
Teams also support phone numbers with extensions, which are used to lookup users when the lookup against
the telephone number returns more than one result.

Extension Numbers
For scenarios that include MS Teams only users:
· The MS Teams only users' extension numbers must be unique from the IP Office extension numbers used by IP
Office only and MS Teams+IP Office users.
· For ease of configuration and maintenance, use extension ranges for each that do not overlap.

· Due to the operation of MS Teams, the + indicator used for E.164 international numbers also appears on
extension numbers in some interfaces.

Deploying MS Teams Direct Routing with IP Office Page 11

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
How the Numbers are Used
Where possible, we recommend using the telephone number and extension number format. However, the values
used depend on the scenario being configured:
· Common MS Teams Telephone Number
For scenarios where the same external PSTN number is used for all or several MS Teams users, the common
telephone number and the individual extension number of each user can be combined. For example:
· User A: 441632768000 x401

· User B: 441632768000 x402

· Individual MS Teams Telephone Numbers

For scenarios where individual PSTN numbers are available for each user, the user can be configured using just
that telephone number if required or with both their individual telephone number and an extension number. For
example:
· User A: 441632768401 or 441632768000 x401

· User B: 441632768402 or 441632768000 x402

· MS Teams Extension Number Only

For scenarios where just extension numbers are required, the telephone number can be omitted. For example:

· User A: x401

· User B: x402

Routing IP Office Calls to the MS Teams Numbers

Once the contact numbers for MS Teams users have been added to the IP Office system directory, the MS Teams
users can be called using the directory. For incoming PSTN calls to the IP Office, normal routing through incoming
call routes is required.
Adding the MS Teams numbers to the IP Office system directory can be done either manually or using automatic
directory synchronization.

Deploying MS Teams Direct Routing with IP Office Page 12

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 IP Office and MS Teams: Telephone and Extension Numbers

1.5 Requirements
The following is a summary of the requirements for installation:

Area Requirements

IP Office · IP Office R11.1 FP2 running either subscription mode or IP Office Preferred edition.

ASBCE · ASBC E R8.1.3 plus:

· ipcs and root passwords for administrator access.

· Software for SSH and SFTP access.

Certificates · Administrator rights to obtain the IP Office root certificate and to generate identity
certificates for the same certificate authority (C A).

IP Office only users · No special configuration requirements.

MS Teams only users · MS Teams: MS Teams license including direct routing (Microsoft 365 Business
Voice without C alling Plan).

MS Teams+IP Office · MS Teams: MS Teams license including direct routing (Microsoft 365 Business
users Voice without C alling Plan).
· IP Office: IP Office User Profile/License:

· Subscription mode systems: Supported by the UC User profile.

· PLDS licensed systems: Supported by the Office Worker, Teleworker and

Power User profiles.

MS Teams · Single tenancy.

Domain · Administrator rights to configure the customer's domain DNS or add files to the
domains default website root.

Other requirements · Administrator rights to the customer's tenancy through the Azure Active Directory
and MS Teams admin portals.

1.6 Known Call Limitations

The following are current known limitations for MS Teams integration with IP Office:
· Name updates are not propagated
In scenarios such as call transfers and forwards, the MS Teams user still sees the original call name. For
example, if MS Teams user Alice calls IP Office user Bob, and Bob then transfers the call to user C arol,
Alice's display still shows the call as being with Bob.
· Hold indication status is not propagated
With MS Teams, if MS Teams puts an IP Office user on hold, or vice versa, there is no indication that the call
is on hold. However, the held user still hears hold music.

Deploying MS Teams Direct Routing with IP Office Page 13

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 14
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 2.
MS Teams Direct Routing

Deploying MS Teams Direct Routing with IP Office Page 15

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
2. MS Teams Direct Routing
This section section provides an overview of the components and routing involved. For full details of MS Teams
direct routing, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-landing-page

Summary
17
o Direct Routing C omponents
17
§ Dial Plans
18
§ Regular Expressions
18
§ Voice Routing Policies
18
§ Voice Routes
19
§ Emergency Routing Policies
19
§ PSTN Usages
19
§ SBC
19
§ MS Teams Line
20
o Direct Routing C all Flow
21
o Direct Routing Flowchart
22
o SBC Verification

Deploying MS Teams Direct Routing with IP Office Page 16

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 MS Teams Direct Routing:

2.1 Direct Routing Components

The configuration of direct routing in MS Teams uses a range of components:
17
o Dial Plans
18
o Regular Expressions
18
o Voice Routing Policies
18
o Voice Routes
19
o Emergency Routing Policies
19
o PSTN Usages
19
o SBC
19
o MS Teams Line

2.1.1 Dial Plans

Dial plans are sets of rules for how to translate any numbers dialed by MS Teams users. For more information, go
to https://docs.microsoft.com/en-us/microsoftteams/what-are-dial-plans
Each dial plan contains up to 50 dialing rules. These rules are checked for a match to the number dialed by the
user.
When a match occurs, that rule's settings determine what changes should be applied to the dialed number. The
translated number is then used for routing through the user's associated voice routing policy.
There are several types of dial plan:
· Country dial plans - Microsoft maintain dial plans for different countries. When the MS Teams user's location
is set to a particular country, the appropriate country dial plan is automatically associated with the user's
dialing.
· Global dial plan - Each tenancy in MS Teams has a default global dial plan. This is applied to all users who
are not associated with a user plan (below). The dialing rules in the global plan are checked for a dialing match
before then being checked against the country dial plan.
o The global dial plan can also be used as a template for any user dial plans. When adding a new user dial
plan, the new plan is created with a copy of the dialing rules currently in the global plan.
· User dial plans - For each tenancy you can create up to a 1000 additional dial plans. Some or all MS Teams
users can be associated with one of those user plans. The dialing rules in that user plan are then checked for a
dialing match before then being checked against the country dialing plan.

Planning a dial plan

1. Decide whether to use the Global dial plan or create a customer specific plan or plan. Using a dial plan is
recommended as it provides a method to to override the default translations that would otherwise be applied
by the country plans.
2. List all types of numbers for which custom dial rules are needed.
· This list should be as comprehensive as possible. Any number formats likely to be used that do not have a
match in the global or user plan may instead be matched by the country dial plan. This frequently leads to
the number being prefixed with + or + and the country code for the user's location.
3. List which users or groups of users need to dial which numbers. Use this to assess whether the dialing rules
can be added to the tenancies global dial plan or need to be grouped in a number of separate user dial plans.
In some cases, the global plan may be suitable for most users but with user plans required for some specific
groups.

Deploying MS Teams Direct Routing with IP Office Page 17

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
2.1.2 Regular Expressions
Several MS Teams menus use 'dial patterns' to match the number dialed or to be dialed. These patterns use regex
(regular expression) strings to check for matches to the dialed digits. For example, the regex pattern ^2\d{2}$
matches any three-digit number beginning with a 2.
· In Dial plans, they are used to match numbers dialed by a user and then apply a number translation.

· In Voice routes, they are used to match the number on outgoing calls to the routes for the call.
108
For more details, see Using Regular Expressions (regex) .

2.1.3 Voice Routing Policies

For direct routing, each MS Teams user is associated with a Voice Routing Policy. For dialing that has been matched
to an entry in the user's assigned dial plan, the resulting translation is then checked for matches against the
available voice routes.
Each voice routing policy can list a number of PSTN usages. When matching out going calls to voice routes, only
routes that have a usage matching one of those in the voice routing policy are considered.

· The different usages are checked for a matching voice route in the order that the usages are listed in the voice
routing policy. That is, all the voice routes with the same usage are checked for a match as a set, using their
dial pattern and priority settings.

The Global Policy

Each tenancy in MS Teams has a default global voice routing policy. This policy is applied to the dialing of all direct
routing users who are not associated with a specific voice routing policy that you create.
o The global policy is also be used as a template for any new policies. When adding a new policy, the new
policy is created with a copy of the settings of currently in the global policy.

Planning Voice Routing Policies

1. Decide whether separate policies are required. For example, through the use of policies with different sets of
PSTN usage records, configure policies for control of local/national/ international calling.
2. List those numbers of types of number for which different policies may be required.
3. List which users or groups of users need to dial which numbers. Use this to assess whether the PSTN usages
can be added to the tenancies global dial plan or need to be grouped in a number of separate user dial plans.
In some cases, the global plan may be suitable for most users but with user plans required for some specific
groups.
For more details, refer to https://docs.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies

2.1.4 Voice Routes

Once a user's dialing has been matched processed through their associated dial plan and voice routing policy, the
resulting number is checked for matches in the MS Teams Voice Route entries. The match then used defines the
SBC connection that should be used for the call.
Each voice route has three settings that are used for this matching; a usage label, a dial pattern and a priority.
These are used as follows:
· The routes are grouped by usage and then checked in the order of the usages as listed in the user's assigned
voice routing policy.
o The first set of usage voice routes are checked for a dial pattern match.

o If no dial pattern match is found, then the next set of usage voice routes are checked, based on the order of
usages in the voice routing policy.
o If a dial pattern match is found, a connection to the SBC (or SBC s) listed in the matched usage route with
the highest priority is attempted.
§ The SBC s which have recently had a successful handshake are checked first, in random order. In MS
Teams, these are referred to as the 'healthy' SBC s.
§ If not successful, any other SBC s specified are checked, again in random order. In MS Teams, these are
referred to as the 'demoted' SBC s.
§ If successful SBC connection occurs, the call now follows the SBC s routing settings.

· If no successfully routed match occurs, the call is re-routed to Microsoft calling plans if enabled for the user,
otherwise the call is dropped.

Deploying MS Teams Direct Routing with IP Office Page 18

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 MS Teams Direct Routing: Direct Routing Components
2.1.5 Emergency Routing Policies
You can use emergency policies in MS Teams to set up emergency numbers and specify how emergency calls are
routed. An emergency policy determines the numbers used to call emergency services, and how calls to emergency
services are routed.
You can use the global policy or create and assign custom policies. Users automatically use the global policy unless
you create and assign them a custom policy.

For more information, go to https://docs.microsoft.com/en-us/microsoftteams/manage-emergency-call-routing-

policies

2.1.6 PSTN Usages

PSTN usage records are simply a set of labels or tags. They are used to link different elements in the call routing
process:
· Each voice route is configured with just one PSTN usage.

· Each voice routing policy is configured with a list of PSTN usage records. C alls routed by the policy can only
use voice routes which are set with one of those PSTN usages.

· Each emergency routing policy is configured with a single PSTN usage from the set available. C alls routed by
the policy can only use voice routes which also have the same PSTN usage.

2.1.7 SBC
When using direct routing, the final stage of outgoing call routing in MS Teams is to route the call to a Microsoft
accredited SBC .
For IP Office support, ASBC E R8.1.3 should be used. Direct routing is supported from R8.1.2, however R8.1.3
contains updates required for IP Office.

2.1.8 MS Teams Line

For direct routing, the connection between the ASBC E and IP Office uses a MS Teams line added to the IP Office
configuration.
· On Server Edition deployments, separate MS Teams lines can be defined on up to 2 IP Office systems. It is
recommend to do this on the primary server and secondary servers to provide resiliency.

Deploying MS Teams Direct Routing with IP Office Page 19

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
2.2 Direct Routing Call Flow
The following is a simplified summary of how the MS Teams components are used for direct routing.

Normal Calls
[Teams User] > [Dial plan] > [Voice routing policy] > [PSTN usage] > [Voice routes] > [SBCs]
The MS Teams user dials a number:

1. Dial plan
The number is checked for a match against either the user's associated dial plan. The dial plan applies the
number translation if a match occurs, otherwise the call is dropped. A translation can include allowing the
number dialed to remain as is.
2. Voice routing policy
The user's associated voice routing policy indicates the PSTN usage records they can use.
3. PSTN usage
PSTN usage records have no configuration settings other than their name. However, they are used used to
create links between a user's voice routing policy and the voice routes their calls can use. The same PSTN
usage must appear in each.
4. Voice routes
The translated number is checked for matches against the available voice routes. Only voice routes that
match usages in the user's voice routing policy are checked for a dial pattern match.
5. SBC
The matched voice route specifies the SBC or SBC s to use for the call. If the SBC is available, the call is
connected. If not available, further attempts at matching to another route in the same usage is attempted.

Emergency Calls
[Teams User] > [Emergency routing policy] > [PSTN usage] > [Voice routes] > [SBCs]
The routing of emergency calls via direct routing should be done through emergency routing policies rather than the
voice routing policies used for normal calls.
The MS Teams user dials a number:
1. Emergency routing policy
If the number matches one in the user's associated emergency routing policy, that policy is used to route the
call. If the number matches one of those in the policy's Emergency dial mask, it is translated to the
Emergency dial string number. For example, if a user dials 911 or 999, the number is translated to 112 for
onward routing.
2. PSTN usage
PSTN usage records have no configuration settings other than their name. However, they are used used to
create links between a user's emergency routing policy and the voice routes it can use. The same PSTN usage
must appear in each.
3. Voice routes
The emergency number is checked for a match against the available voice routes. The matching looks for a
voice route with a dial pattern that matches the emergency number and the PSTN usage set in the emergency
routing policy.
4. SBC
The matched voice route specifies the SBC or SBC s to use for the call.

Routing Failure
In all the above, if direct routing fails at any point, the call is redirected to using Microsoft C alling Plans if the MS
Teams user is configured for calling plans. If otherwise, the call is dropped.

Deploying MS Teams Direct Routing with IP Office Page 20

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 MS Teams Direct Routing: Direct Routing Call Flow

2.3 Direct Routing Flowchart

The following flowchart is a simplified summary of the call routing applied in MS Teams.

· Vertical results are positive, horizontal negative.

Deploying MS Teams Direct Routing with IP Office Page 21

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
2.4 SBC Verification
During the process of adding a connection to the ASBC E to MS Teams, you will be prompted to verify the domain
part of the ASBC Es FQDN. For example, for the FQDN sbc.example.com, you will need to verify that you have
administrator rights for the example.com domain.
Verification will require you to be able to do one of the following:
· Add a TXT record to the domain's DNS records.

· Add an MX record to the domain's DNS records.

· Add a text file to the root of the domain's default web site.

Deploying MS Teams Direct Routing with IP Office Page 22

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 3.
Example Direct Routing
Scenario

Deploying MS Teams Direct Routing with IP Office Page 23

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
3. Example Direct Routing Scenario
In this scenario, the customer has a single ASBC E and IP Office.

· IP Office extension numbers in the range 2XX. MS Teams only user extension numbers in the range 4XX.

· For ease of implementation and maintenance, the extension number range used for MS Teams only users
should not overlap with the range used for other users.
· Local area code 01632.

· Main telephone number 01632 768000

· The customer is based in the UK, international dialing prefix 44.

· The customer wants to be able to restrict which MS Teams users can make outgoing national and international
PSTN through the IP Office.

Numbers to Consider
Begin planning by considering the different numbers used on or routed through the IP Office:

Dialed Numbers Details

Extension IP Office These are 3 digit numbers in the range 200 to 299. These can be used for our IP
Numbers Office only and MS Teams+IP Office users.
MS Teams Only These are 3 digit numbers in the range 400 to 499. These can be used for any
MS Teams only users.
IP Office Shortcodes These are numbers of variable length but always beginning with *.
Incoming PSTN Calls The customer's main number for calls to the IP Office is 01632 768000.
Emergency Calls 999 and 112.
PSTN Local Potentially any 6 digit number.
National 7 to 10 digit numbers with a leading 0.
International Numbers beginning 00.

There are also some special scenarios we want to consider for calls made by MS Teams users:
· Any calls from MS Teams with a + prefix need to be converted:

o + changed to the international dialing prefix for the customer's locale, if the country code is not 44.

o + or 00 and the country code removed for international calls that should be handled as national calls.

o + removed from any other numbers. MS Teams sometimes prefixes + to non-international numbers.

· We want calls prefixed with the country code 44 changed back to being national numbers with just the national
dialing prefix.

Deploying MS Teams Direct Routing with IP Office Page 24

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Example Direct Routing Scenario:

3.1 Proposed Direct Routing Configuration

For our example scenario, we have concluded that we need the following direct routing configuration.

Proposed Dial Plan

We will use a single dial plan for all users.
· The aim is to convert all numbers to a format useable by the IP Office systems. The translations also need to
match the dial patterns used for the voice routes.
· The single plan can contain the full range of required digit translations for all user. C ontrol of which numbers a
particular user can connect to it still limited by the PSTN usages set in their assigned voice routing policy.
· We need to cover both the format for numbers stored within Azure Active Directory (typically full E.164 format)
and numbers that may be manually dialed from the MS Teams client.
· Note that the order of the dial patterns is important. The entries in the dial plan are checked for the first match
from the top-down.
In this case, the plan matches expected dialing in the customer's UK location.

Pattern | Translation Description

^\+?(2\d{2})$ $1 Match any 3-digit numbers beginning with a 2. That is, IP

Office extension numbers. Translate the full number as is.
The \+? part matches whether the number is prefixed with a
+ or not.
^(\*.+)$ $1 Match any numbers prefixed with a *. That is, IP Office
shortcodes. Translate the full number as is.
^(\+44|0044|0)?(1632)?768([24]\d{2})$ $3 Match any DID/DDI number dialed as a local, nation or
international number. Translate to the extension number.
^(\d{6})$ $1 Match any 6-digit numbers. That is local phone numbers
without the local area code. Translate the full number as is.
^(0\d{6,10})$ $1 Match any 7 to 10-digit numbers prefixed with a 0. That is
national numbers. Translate the full number as is.
^(\+|00)44(.+)$ 0$2 Match any number prefixed with 0044 or +44. That is, UK
numbers dialed as full international numbers. Translate back
to national numbers prefixed with just 0.
^(\+|00)(.+)$ 00$2 Match any number prefixed with 00 or +. Translate the
number to the international dialing prefix for the customer's
location, for this scenario 00.

· The matching of calls already dialed in the format expected by the IP Office may appear superfluous. However,
doing this in the customer's dial plan prevent those numbers being altered by the fixed country dial plan, which
typically will add + or + and the country code for the users's location to any number.

Proposed Voice Routing Policies/PSTN Usages

The customers wants to be able to configure MS Teams users with internal only, national only and all dialing rights.
We can configure that using the following set of three PSTN usages and three voice routing policies:

PSTN usage Voice routing policy

IPO PSTN All

IPOffice Yes Yes Yes

National – Yes Yes
International – – Yes

Deploying MS Teams Direct Routing with IP Office Page 25

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Proposed Voice Routes
For the voice routes, we need digit pattern matches for numbers resulting from the translations applied by the dial
plan.

Voice Route Priority Dial Pattern PSTN Usage SBC

Extn2xx 1 ^2\d{2}$ IPOffice sbc1.example.com

Shortcodes 1 ^*.+$ IPOffice sbc1.example.com
PSTN_Local 1 ^\d{6}$ National sbc1.example.com
PSTN_National 1 ^0\d{10}$ National sbc1.example.com
PSTN_Global 1 ^00.+$ International sbc1.example.com
Emergency 1 ^\+?999 National sbc1.example.com

· The dial patterns do not need the ( ) brackets as in the dial plan since we are do not need to refer to them in
any translation.

Proposed Emergency Routing Policy

Setting Value

Emergency Dial Number 999

Emergency Dial Mask 112;911
PSTN Usage National

Deploying MS Teams Direct Routing with IP Office Page 26

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Example Direct Routing Scenario: Callflow

3.2 Callflow
The following is a view of the call routing within MS Teams for our example:

· In theory, the emergency calls could have used the same voice route and PSTN usage. However, using separate entries just for emergency calls means future changes
to normal call routing can be made and testing without affecting emergency call routing.

Deploying MS Teams Direct Routing with IP Office Page 27

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
3.3 Simplified Callflow
In this simplified version of the previous callflow, all users are being allowed to dial any numbers. The dial plan used matches any dialing as does the voice route.

In this case:
· The dial plan is still needed to perform any necessary number translation between numbers used in MS Teams and numbers formats supported by the IP Office. In this
case, the + is stripped from any numbers.
· Only a single voice route and single PSTN usage are now required for normal calls.

o In theory, the emergency calls could have used the same voice route and PSTN usage. However, using separate entries just for emergency calls means future
changes to normal call routing can be made and tested without affecting emergency call routing.
· We could in theory, have configured this using the global dial plan, global voice routing policy and global emergency routing policy.

Deploying MS Teams Direct Routing with IP Office Page 28

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Example Direct Routing Scenario: Multiple SBC Callflow

3.4 Multiple SBC Callflow

For an IP Office network, up to two MS Teams lines are supported. In this version of the callflow, the customer has two IP Office locations in a Server Edition/SC N network.
Each has its own ASBC E connection to MS Teams.

· The voice routes allow calls to internal extension numbers to be routed to either the primary or secondary IP Office servers. C alls are then routed across the IP Office
network as necessary.
· During IP Office resilience, IP Office IP telephony users will failover and internal calls from MS Teams can continue.

· Other calls will use the voice route matching the MS Teams user's location. However, if connection is not possible, the alternate SBC and IP Office can be used.
However, this will require each IP Office to have routing to handle how the customer wants outgoing PSTN calls from the other location handled. For example, allowed
after suitable number changes using ARS shortcodes, or dropped after hearing a suitable prompt such as "Service currently not available".

Deploying MS Teams Direct Routing with IP Office Page 29

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 30
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 4.
Configuring the Users in MS
Teams

Deploying MS Teams Direct Routing with IP Office Page 31

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
4. Configuring the Users in MS Teams
This section covers the general configuration of users within MS Teams.

Summary
32
1. User C onfiguration in MS Teams
33
2. C hecking MS Teams User Numbers

4.1 User Configuration in MS Teams

The user telephone numbers for MS Teams users are configured through Azure Active Directory.
· The MS Teams user details can be automatically shared with the IP Office systems. See Direct Routing
56
Synchronization .

Procedure
1. Using a user account with full administrator rights, login to Azure Active Directory at https://portal.azure.com.
2. Select Azure AD and then Users.
3. Select the required user.
4. Select Contact Info.
5. Set the user's Office phone number as required. This is stored as the businessPhone value with Azure Active
Directory.The format varies depending on the type of number being set (see Telephone and Extension
11
Numbers ).

Number Example Azure Active Directory Phone Number Format

Telephone Number and +441632768000;ext=402

Extension

Telephone Number Only +441632768402

Extension Number Only x402

5. Direct Routing Users

For all users allowed to make PSTN calls using direct routing, you also need to check that they have a suitable
MS Teams license.
a. Ensure that the user's Location field is populated. This allows MS Teams to determine the country dial
plan that should be used for any dialing by the user.
b. Select Licenses.
c. C lick Assignments and add a license that includes support for Direct Routing.
6. Repeat this process for all other users.

Deploying MS Teams Direct Routing with IP Office Page 32

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the Users in MS Teams: User Configuration in MS Teams

4.2 Checking MS Teams User Numbers

Use the following process to check that the Office phone number values set for users in Azure Active Directory
are shown correctly in MS Teams. In MS Teams it is listed as the user's Phone number.

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com/user

2. If necessary, select User.

3. The list of users is displayed, including their MS Teams telephone numbers.

4. Verify that the Phone number for the user is shown as expected. For more information, see Telephone and
11
Extension Numbers .

Number Example MS Teams Format

Telephone Number and Extension tel:441632768202;ext=202

Telephone Number Only tel:441632768202

Extension Number Only 202

Deploying MS Teams Direct Routing with IP Office Page 33

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 34
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 5.
Configuring the IP Office for
MS Teams

Deploying MS Teams Direct Routing with IP Office Page 35

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
5. Configuring the IP Office for MS Teams
This section cover the basic steps for configuring the IP Office system to support MS Teams.

Summary
36
1. Manually Adding MS Teams+IP Office Users
37
2. Manually Adding Directory Entries for MS Teams Only Users
38
3. Adding an MS Teams Line
38
4. C heck C ollaboration Service

5.1 Manually Adding MS Teams+IP Office Users

The process below describes the steps for adding a MS Teams+IP Office user manually. For the process to add a
56
user automatically, see Azure Active Directory Synchronization for Direct Routing . However, it is useful to
understand the process below and how the user settings should be set in any template used for automatic
synchronization.

Procedure
1. Using IP Office Manager or IP Office Web Manager, access the IP Office system configuration.
2. C onfigure the user as required for their IP Office operation. This process only covers the changes required for
MS Teams.
3. Select User or Call Management | Users.
4. Add a new user as normal or select the existing user you want to edit.
5. Select the User tab:
a. Select a Profile that supports MS Teams user integration:
· On subscription mode systems: MS Teams+IP Office users are supported by the UC User profile.

· On PLDS licensed systems: MS Teams+IP Office users are supported by the Office Worker,
Teleworker and Power User profiles.
b. Select Enable MS Teams Client.
6. Select the Mobility tab:

a. The Coverage Delay sets a pause, if required, between calls alerting on the user's IP Office extension
devices and then also altering on their MS Teams client.
b. The user's MS Teams URI should match their Office phone setting as specified in Azure Active Directory
11
(for more information, see MS Teams Telephone Numbers ):

Number Example MS Teams URI Format

Telephone Number and Extension +441632768202;ext=202

Telephone Number Only +441632768202

Extension Only +202

· If the MS Teams URI field is grayed out, the system has been configured to only allow automatic
57
updates through Azure Active Directory synchronization. See Preventing Manual URI Editing .
7. C lick OK or Save.
8. If prompted to allow the system to automatically create an matching extension entry, allow the system to
create one matching the type of IP Office extension the user will be using.
9. If using IP Office Manager, save the configuration back to the IP Office system.

Deploying MS Teams Direct Routing with IP Office Page 36

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the IP Office for MS Teams: Manually Adding MS Teams+IP Office Users

5.2 Manually Adding Directory Entries for MS Teams Only Users

MS Teams only users do not exist in the IP Office configuration. However, their details can be added to the IP Office
system directory. This then allows those users to be selected and called from the directory by IP Office users.
· The process below describes the steps for adding a MS Teams only user directory details manually. For the
56
process to add them automatically, see Azure Active Directory Synchronization .However, it is useful to
understand the process below and how the system directory settings should be changed by automatic
synchronization.

Procedure
1. Using IP Office Web Manager, access the IP Office system configuration.
2. Select System Settings | Directory.
3. Select Add Directory Entry.
4. For the Name, enter the user name followed by a space and MST. For example; Diego Siciliani MST
5. For the Number, use one of the following formats (for more information, see Telephone and Extension
Numbers 11 ):

Number IP Office Format

Extension and DDI Number 441632768402-402 (1, 2)

Telephone Number Only 441632768402

Extension Number Only +402

· Note 1: A dash is a delimiter signifying that the following number is an extension number.

· Note 2: Dialing either number matches the directory entry.

6. C lick Save.

Deploying MS Teams Direct Routing with IP Office Page 37

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
5.3 Adding an MS Teams Line
The MS Teams line links the IP Office to the ASBC E required for direct routing.
· This document assumes that the IP Office system has already been configured to support SIP trunks.

Procedure
1. Using IP Office Manager or IP Office Web Manager, access the IP Office system configuration.

2. Select Line or System Settings | Lines.

3. C lick Add and select MS Teams Line. If using IP Office Web Manager in a Server Edition network, also
select the server to which you want to add the line. C lick OK.
4. On the MS Teams tab, configure the number of calls:

a. Set the Proxy Address to the IP Address of the ASBC E interface being used (A1 or A2).
b. Ensure that the Max Calls value matches the Concurrent call capacity of the ASBC E entry in MS
Teams.
5. On the VoIP tab, ensure that only a single codec is selected

6. C lick Save or OK.

7. If using IP Office Manager, save the configuration back to the IP Office system.

5.4 Check Collaboration Service

Use of automatic Azure Active Directory synchronization requires the IP Office system hosting the MS Teams line to
also be running the C ollaboration Service. The service is normally present and started automatically. However, this
should be check, especially on systems upgraded to IP Office R11.1 FP2. For a standalone-IP500 V2 system, the
service is provided by an IP Office Application server.

Procedure
1. Using a web browser, access the IP Office server on port 7071.
2. Select the System tab.

Deploying MS Teams Direct Routing with IP Office Page 38

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the IP Office for MS Teams: Check Collaboration Service
3. In the list of Services, check that the Collaboration Services service is running. If necessary, click Start to
start the service.
4. C heck that the auto-start checkbox next to the service is selected.

Deploying MS Teams Direct Routing with IP Office Page 39

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 40
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 6.
Configuring MS Teams Direct
Routing

Deploying MS Teams Direct Routing with IP Office Page 41

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
6. Configuring MS Teams Direct Routing
This section of the document contains a summary of the configuration done within MS Teams to support direct
routing to the IP Office via the ASBC E.

· Note that the processes shown in this document are just examples. Processes such as assigning policies to
users can be performed for a whole tenancy, for a group of users or for individual users. PowerShell scripts
can also be used for most processes rather than using the MS Teams UI menus.
· Note also that a policy assigned to an individual user overrides any assigned to a group, which itself overrides
any assigned globally. Bear this is mind for ease of maintenance when planning the customer's policies and
how to assign those policies. For more information, see https://docs.microsoft.com/en-
us/microsoftteams/assign-policies-users-and-groups
· In mixed scenarios, the setting applied directly to a user typically overrides any applied to their group, which
themselves override any applied to the whole tenancy. This should be kept in mind when planning the
implementation as it will also affect maintenance.

Summary
43
1. Adding an MS Teams Line
44
2. Verify the SBC Domain
45
3. Adding the ASBC E to MS Teams
46
4. C reating Dial Plans
48
5. C reating Voice Routing Policies
50
6. C reating Voice Routes
52
7. C onfigure Emergency C alling

Deploying MS Teams Direct Routing with IP Office Page 42

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring MS Teams Direct Routing:

6.1 Adding an MS Teams Line

The MS Teams line links the IP Office to the ASBC E required for direct routing.
· This document assumes that the IP Office system has already been configured to support SIP trunks.

Procedure
1. Using IP Office Manager or IP Office Web Manager, access the IP Office system configuration.

2. Select Line or System Settings | Lines.

3. C lick Add and select MS Teams Line. If using IP Office Web Manager in a Server Edition network, also
select the server to which you want to add the line. C lick OK.
4. On the MS Teams tab, configure the number of calls:

a. Set the Proxy Address to the IP Address of the ASBC E interface being used (A1 or A2).
b. Ensure that the Max Calls value matches the Concurrent call capacity of the ASBC E entry in MS
Teams.
5. On the VoIP tab, ensure that only a single codec is selected

6. C lick Save or OK.

7. If using IP Office Manager, save the configuration back to the IP Office system.

Deploying MS Teams Direct Routing with IP Office Page 43

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
6.2 Verify the SBC Domain
To an SBC (ASBC E) with MS Teams, the domain used in its FQDN needs to be verified. This requires you to be able
to do one of the following:
· Add a TXT record to the domain's DNS records.

· Add an MX record to the domain's DNS records.

· Add a text file to the root of the domain's default web site.

Procedure
1. Login to the admin portal at https://admin.microsoft.com/Adminportal.
2. Select Settings | Domain.
3. Select Add Domain.
4. Enter the domain name and click Use this domain.
5. Select the method you want to use to verify the domain and click Continue.
6. Follow the instructions provided for the values that need to be added to the domain's DNS server or root
website.
7. When you have prepared the DNS server records or web site files as requested, click Verify.
8. Skip any other actions and click Continue.
9. C lick Done.

Deploying MS Teams Direct Routing with IP Office Page 44

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring MS Teams Direct Routing: Verify the SBC Domain

6.3 Adding the ASBCE to MS Teams

This process configures the SIP connection from MS Teams to the Avaya ASBC E being used by the IP Office.

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com/direct-routing/v2
2. Select Voice and then Direct Routing.

3. Select the SBCs tab and select Add.

4. Enter the FQDN of the ASBC E. If the domain used in the FQDN is not already one verified by Microsoft (see
44
Verify the SBC Domain ), follow the instructions displayed by MS Teams after adding the SBC entry.
5. Enable the SBC and set the SIP signaling port to 5061.
6. Ensure that the Concurrent call capacity matches the Max Calls setting of the IP Office MS Teams line.
43
See Adding an MS Teams Line .
7. C lick Save.

Deploying MS Teams Direct Routing with IP Office Page 45

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
6.4 Creating Dial Plans
Dial plans are sets of rules for how to translate any numbers dialed by MS Teams users. For more information, go
to https://docs.microsoft.com/en-us/microsoftteams/what-are-dial-plans
Each dial plan contains up to 50 dialing rules. These rules are checked for a match to the number dialed by the
user.
When a match occurs, that rule's settings determine what changes should be applied to the dialed number. The
translated number is then used for routing through the user's associated voice routing policy.
There are several types of dial plan:
· Country dial plans - Microsoft maintain dial plans for different countries. When the MS Teams user's location
is set to a particular country, the appropriate country dial plan is automatically associated with the user's
dialing.
· Global dial plan - Each tenancy in MS Teams has a default global dial plan. This is applied to all users who
are not associated with a user plan (below). The dialing rules in the global plan are checked for a dialing match
before then being checked against the country dial plan.
o The global dial plan can also be used as a template for any user dial plans. When adding a new user dial
plan, the new plan is created with a copy of the dialing rules currently in the global plan.

· User dial plans - For each tenancy you can create up to a 1000 additional dial plans. Some or all MS Teams
users can be associated with one of those user plans. The dialing rules in that user plan are then checked for a
dialing match before then being checked against the country dialing plan.

Planning a dial plan

1. Decide whether to use the Global dial plan or create a customer specific plan or plan. Using a dial plan is
recommended as it provides a method to to override the default translations that would otherwise be applied
by the country plans.
2. List all types of numbers for which custom dial rules are needed.
· This list should be as comprehensive as possible. Any number formats likely to be used that do not have a
match in the global or user plan may instead be matched by the country dial plan. This frequently leads to
the number being prefixed with + or + and the country code for the user's location.
3. List which users or groups of users need to dial which numbers. Use this to assess whether the dialing rules
can be added to the tenancies global dial plan or need to be grouped in a number of separate user dial plans.
In some cases, the global plan may be suitable for most users but with user plans required for some specific
groups.

6.4.1 Creating a Dial Plan

Dial plans are sets of rules for how to translate any numbers dialed by MS Teams users into the format required by
the IP Office.

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com/policies/teamsdialplan
2. If necessary, select Voice and then select Dial plans.
3. Either select the Global dial plan or click Add to add a new plan.
· The global plan is applied to the dialing of all users who are not associated with any specific user plan.

· Adding a new plan creates a copy of the existing global plan including its existing translations.

4. Edit the plan details as required.

5. For a new plan, replace the label at the top of the menu with a unique descriptive name for the dial plan.
6. Edit the dialed digits matches and their translations as required:
a. To add a new match, click Add.
i. Enter a name for the dialing rule and, if needed, a description.
ii. Either select Basic or Advanced mode to define the actions of the dialing rule. Basic mode uses the
menu options to create the required regex expressions. Advanced mode allows direct entry of the
regex strings used for the match and translation.
iii. Enter the regex string needed to match the number and the string for the resulting translation. For
108
details of regex, see Regex Examples .
b. To edit an existing match, click to the left of the rule translation name and then click Edit.

Deploying MS Teams Direct Routing with IP Office Page 46

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring MS Teams Direct Routing: Creating Dial Plans
c. Sort the matches by selecting the match that needs moving and then clicking Move up or Move down. In
use, entries are checked from the top-down and the first match is used.
7. The final plan should for our example scenario looks like the following.

8. C lick Save.

6.4.2 Assigning a Dial Plan to Users

If using user dial plans for some or all users, use the following process to associate the user with the dial plan.
· This process assigns a policy to individual users and is an example only. Policies can also be assigned to
groups of users or globally. For more information, see https://docs.microsoft.com/en-
us/microsoftteams/assign-policies-users-and-groups

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com
2. Select Users.
3. Select the required user or users.
4. C lick Edit settings.
5. Select the dial plan you want to assigned to the user or users and click Apply.

Deploying MS Teams Direct Routing with IP Office Page 47

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
6.5 Creating Voice Routing Policies
For direct routing, each MS Teams user is associated with a Voice Routing Policy. For dialing that has been matched
to an entry in the user's assigned dial plan, the resulting translation is then checked for matches against the
available voice routes.
Each voice routing policy can list a number of PSTN usages. When matching out going calls to voice routes, only
routes that have a usage matching one of those in the voice routing policy are considered.

· The different usages are checked for a matching voice route in the order that the usages are listed in the voice
routing policy. That is, all the voice routes with the same usage are checked for a match as a set, using their
dial pattern and priority settings.

The Global Policy

Each tenancy in MS Teams has a default global voice routing policy. This policy is applied to the dialing of all direct
routing users who are not associated with a specific voice routing policy that you create.
o The global policy is also be used as a template for any new policies. When adding a new policy, the new
policy is created with a copy of the settings of currently in the global policy.

Planning Voice Routing Policies

1. Decide whether separate policies are required. For example, through the use of policies with different sets of
PSTN usage records, configure policies for control of local/national/ international calling.
2. List those numbers of types of number for which different policies may be required.
3. List which users or groups of users need to dial which numbers. Use this to assess whether the PSTN usages
can be added to the tenancies global dial plan or need to be grouped in a number of separate user dial plans.
In some cases, the global plan may be suitable for most users but with user plans required for some specific
groups.
For more details, refer to https://docs.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies

6.5.1 Creating a Voice Routing Policy

For direct routing, each MS Teams user is associated with a Voice Routing Policy. That policy contains a number of
PSTN usage records. Each of these records defines a number pattern that can be checked for a match to the user's
dialing.

Procedure
1. Log in to the MS Teams admin portal at https://admin.teams.microsoft.com/policies/teamsonlinevoicerouting
2. If necessary, select Voice and then Voice routing policies.

Deploying MS Teams Direct Routing with IP Office Page 48

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring MS Teams Direct Routing: Creating Voice Routing Policies
3. Select Add to add a new policy. Otherwise, select an existing policy and click Edit.

4. For a new policy, add a unique descriptive name and, if necessary, a description.
5. To add PSTN usage records:
a. C lick Add or remove PSTN usage records.
b. Select an existing PSTN usage from the list of those available and click Save and apply. Alternatively, to
create a new PSTN usage, click Add and when completed, select it and click Save and apply.
6. C heck that the usages are listed in the required order for matching to potential voice routes. If necessary,
select a record and click Move up or Move down. The order of the usages sets the order in which matching
voice routes are checked for dial pattern matches.
7. C lick Save.
8. C reate any other voice policies required.

6.5.2 Assigning a Voice Routing Policy to a User

Each MS Teams users uses either the default global voice routing policy or the policy specifically assigned to them.
Assigning a policy is done either:
· Manually using the process below.
56
· Automatically using IP Office synchronization. See Direct Routing Synchronization .
· This process assigns a policy to individual users and is an example only. Policies can also be assigned to
groups of users or globally. For more information, see https://docs.microsoft.com/en-
us/microsoftteams/assign-policies-users-and-groups

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com
2. Select Users.
3. Select the required user or users.
4. C lick Edit settings.
5. Select the Policies tab and click Edit.
6. In Voice routing policy drop-down, select the policy you want to assigned to the user or users and click
Apply.

Deploying MS Teams Direct Routing with IP Office Page 49

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
6.6 Creating Voice Routes
Once a user's dialing has been matched processed through their associated dial plan and voice routing policy, the
resulting number is checked for matches in the MS Teams Voice Route entries. The match then used defines the
SBC connection that should be used for the call.
Each voice route has three settings that are used for this matching; a usage label, a dial pattern and a priority.
These are used as follows:

· The routes are grouped by usage and then checked in the order of the usages as listed in the user's assigned
voice routing policy.
o The first set of usage voice routes are checked for a dial pattern match.

o If no dial pattern match is found, then the next set of usage voice routes are checked, based on the order of
usages in the voice routing policy.
o If a dial pattern match is found, a connection to the SBC (or SBC s) listed in the matched usage route with
the highest priority is attempted.
§ The SBC s which have recently had a successful handshake are checked first, in random order. In MS
Teams, these are referred to as the 'healthy' SBC s.

§ If not successful, any other SBC s specified are checked, again in random order. In MS Teams, these are
referred to as the 'demoted' SBC s.
§ If successful SBC connection occurs, the call now follows the SBC s routing settings.

· If no successfully routed match occurs, the call is re-routed to Microsoft calling plans if enabled for the user,
otherwise the call is dropped.

Emergency Call Route

52
If you want to also include a route for emergency calls (see C onfigure Emergency C alling ), add a route with a
dial pattern that will match the primary emergency number (the Emergency Dial String) with and without a
proceeding +. For example, ^\+?112. Set the voice route's usage to match that specified in the emergency routing
profile.

Deploying MS Teams Direct Routing with IP Office Page 50

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring MS Teams Direct Routing: Creating Voice Routes
6.6.1 Creating a Voice Route
Use the following process to create voice routes.

Procedure
1. Log in to the MS Teams admin portal at https://admin.teams.microsoft.com/direct-routing/v2/voice-routes
2. Select Voice and then Direct Routing.

3. Select the Voice Routes tab. The existing voice routes are displayed.

24
· In this example from our simple single server scenario (see Example Scenario ), the Dial number
pattern matches any dialed number following their processing through the user voice routing policies. The
single ASBC E is set as the destination for calls.
4. To add an new route, click Add. To edit an existing route, select it and then click Edit.
a. Enter a unique descriptive name for the voice route and, if necessary, a description.
b. Set the Priority. When multiple voice route matches occur, the highest priority one is tested first.

c. Enter the Dialed number match. This dial pattern is used to match for numbers that should then be
routed using the voice route. The dial pattern uses regex format syntax. For example, ^2\d{2})$
108
matches 3-digit extension numbers being with a 2. See Using Regular Expressions (regex) .
d. To add an SBC to the list of SBC s used by this voice route:
i. C lick Add SBCs.
ii. Select the ASBC E from the list of enrolled SBC s and click Apply.
e. Add a PSTN usage for the voice route. Only calls by users who have the same usage in their associated
voice routing policy can use the voice route.
i. C lick Add PSTN usage or from the list of those already shown, click Add.
ii. Select an existing PSTN usage from the list of those available and click Save and apply.
Alternatively, to create a new PSTN usage, click Add and when completed, select it and click Save
and apply.
f. C lick Save.
5. Repeat the process to define any additional voice routes required.
6. Once you've added the voice routes required, check they are in the required order. If necessary, select a
record and click Move up or Move down.

Deploying MS Teams Direct Routing with IP Office Page 51

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
6.7 Configure Emergency Calling
You can use emergency policies in MS Teams to set up emergency numbers and specify how emergency calls are
routed. An emergency policy determines the numbers used to call emergency services, and how calls to emergency
services are routed.
You can use the global policy or create and assign custom policies. Users automatically use the global policy unless
you create and assign them a custom policy.

For more information, go to https://docs.microsoft.com/en-us/microsoftteams/manage-emergency-call-routing-

policies

Summary
52
1. C onfiguring an Emergency Policy
53
2. Assigning an Emergency Policy to Users

6.7.1 Configuring an Emergency Policy

Use the following process to configure emergency policy. This defines the emergency number and any other
numbers that should be mapped to it. It also defines the PSTN usage for the voice routes that emergency calls can
then use.

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com/direct-routing/v2
2. Select Voice and then Emergency policies.
3. Either click Add to add a new policy or select an existing policy and click Edit.
· The Global policy is used for all users to who you do not specifically assign an emergency policy.

4. If adding a new policy, enter a unique descriptive name for the policy and, if necessary, add a description.
5. If Dynamic emergency calling is enabled, Teams retrieves policy and location information from the
service and includes that information as part of the emergency call.
6. Define the emergency numbers required:
a. C lick Add.
b. In the Emergency dial string, enter the main emergency number that users will dial. For example 112.
c. You can also define an optional Emergency dial mask. This can contain any other numbers that should
be automatically translated to the Emergency dial string when dialed. For example, 999. To add
multiple additional numbers to the mask, separate each number with a semi-colon. For example, 999;911.

· For locales where all emergency calls go to the same emergency service operator, using an
Emergency dial mask simplifies configuration.
· Use of a mask also allows you to include numbers that might be dialed by visitors from locales where
other numbers are used for emergency calls.
· For locales where emergency calls go to different operators based on the number dialed, repeat this
step to add a separate Emergency dial string for each different operator service rather than using
masks.
d. Select a PSTN usage record. The record is used to determine which voice route is used to route
emergency calls.
7. C lick Save.
8. If using an emergency policy other than the global one, assign the policy to the required users. See Assigning
53
an Emergency Policy to Users .

Deploying MS Teams Direct Routing with IP Office Page 52

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring MS Teams Direct Routing: Configure Emergency Calling
6.7.2 Assigning an Emergency Policy to Users
Use the following process to assign an emergency call routing policy to a user. This is necessary if you have
configured your emergency settings in a policy other than the global emergency routing policy.
· This process assigns a policy to individual users and is an example only. Policies can also be assigned to
groups of users or globally. For more information, see https://docs.microsoft.com/en-
us/microsoftteams/assign-policies-users-and-groups

Procedure
1. Login to the MS Teams admin portal at https://admin.teams.microsoft.com
2. Select Users.
3. Select the required user or users.
4. C lick Edit settings.
5. Select the Policies tab and click Edit.
6. In Emergency call routing policy drop-down, select the policy you want to assigned to the user or users
and click Apply.

Deploying MS Teams Direct Routing with IP Office Page 53

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 54
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 7.
Azure Active Directory
Synchronization

Deploying MS Teams Direct Routing with IP Office Page 55

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
7. Azure Active Directory Synchronization
This section provides notes for Azure Active Directory synchronization to support systems using direct routing. This
synchronization can perform a range of actions (using multiple separate synchronization entries if necessary).

· Directory Synchronization
Add the name and telephone number details of MS Teams only users to the IP Office system directory. Also
add the contact details of other contacts that the customer stores in Azure Active Directory.
· MS Teams Voice Routing Policy Synchronization
For MS Teams users, assign which voice routing policy they should use.
· IP Office User Creation and Maintenance
User details from Azure Active Directory can be used to create and update users and extensions on the IP
Office system. This can be used to create IP Office only and MS Teams+IP Office users.

User Type Directory Sync Routing Policy Create/Maintain

Sync IP Office Users

MS Teams Only Users –

IP Office Only Users – –
MS Teams+IP Office Users –

· Azure Active Directory Groups

Users created in Azure Active Directory can be added to defined groups. Separate synchronization processes
can then be run for the users in particular groups. For example:
· One to run directory/voice routing policy synchronization for the group containing MS Teams only users.

· One to run synchronization to create IP Office only users, with appropriate IP Office user and extension
templates for those users. Groups can also be used to allow separate synchronization processes using
different templates. For example, to create SIP extension users and DEC T extension users.
· One to run synchronization to create MS Teams+IP Office users with appropriate templates for that role.

· IP500 V2 Systems
Azure Active Directory connection uses the C ollaboration Service on Linux-based IP Office servers. For
standalone IP500 V2 systems, the service requires an IP Office Application Server or UC M Module. However,
only directory synchronization is supported.

Summary
57
1. Preventing Manual URI Editing
57
2. Enabling Directory Synchronization
58
3. C onfiguring Azure Active Directory App Registration
59
4. C onfiguring a Teams Administrator
60
5. C reating User and Extension Templates
61
6. C reating User Provisioning Rules
62
7. Setting Up a Direct Routing Synchronization Process

Deploying MS Teams Direct Routing with IP Office Page 56

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Azure Active Directory Synchronization:

7.1 Preventing Manual URI Editing

If automatic Azure Active Directory synchronization is being used to create and update MS Teams+IP Office users,
it is recommended to prevent the manual editing of the user MS Team URI settings that appear in the IP Office
configuration.

Procedure
1. Using IP Office Manager or IP Office Web Manager, load the IP Office system configuration.

2. Select System or System Settings | System.

3. Select the Telephony settings and then select the MS Teams tab.
4. To prevent manual editing of MS Teams URI settings, select Auto Populate MS Teams Data.
5. C lick Update or OK.
6. If using IP Office Manager, save the configuration changes back to the IP Office system.

7.2 Enabling Directory Synchronization

Directory synchronization with Azure Active Directory uses a service called C ollaboration Service running on the IP
Office server. For IP500 V2 systems, the service is provided by the IP Office Application Server or UC M Module
installed with the system.

Procedure
1. Using IP Office Manager or IP Office Web Manager, load the IP Office configuration.
2. Select System or System Settings | System. If necessary, select the required server in the network.
3. Select Directory Services.
4. Select HTTP.
5. Set the Directory Type to Collaboration Services.
6. The default Resync Interval is set to 3600 seconds (1 hour). Adjust the value if required.
7. C lick OK or Update to save the changes.
8. If using IP Office Manager, save the configuration back to the IP Office system.

Deploying MS Teams Direct Routing with IP Office Page 57

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
7.3 Configuring Azure Active Directory App Registration
In order to connect the IP Office to Azure Active Directory, you need to register an application ('app') in Azure
Active Directory. During that process, the app is given a Client ID and Client Secret. Those two values are
needed by the IP Office for its connection to Azure Active Directory.
In addition, IP Office connections require the customer's Tenant ID and, if setting up a connection for a specific
group of users, that group's Group ID. Those value can also be obtained during the first stages of the following
process.

Procedure
1. Using a user account with full administrator rights, login to Azure Active Directory at https://portal.azure.com.
2. Search for and select Azure Active Directory.
3. Select Overview.
4. The Basic Information section includes the Tenant ID that is required for IP Office connections. C opy the
value to a text file.
5. If planning to create a connection for a particular group of users:
a. Select Groups and locate the required group.

b. Select the group. Select Properties.

c. The Object ID shown next to the group name is the Group ID needed for the connection. C opy the value
to the text file.
6. Select App registrations.
a. C lick New registration.
b. For the Display name, enter a unique descriptive name such as IPOSync.
c. Note the displayed Application (client) ID. This is the Client ID value required by the IP Office. C opy
the value to the text file.
d. C lick the link next to Client credentials.
e. C lick New client secret.
f. C opy the Value shown (not the Secret ID) to the text file.
7. Select API Permissions.
a. Using Add a permission option, add read permission for calendars and contacts. Add read all permission
for the directory and groups.
8. You now have the information required to create connections between the IP Office and Azure Active
Directory.

Deploying MS Teams Direct Routing with IP Office Page 58

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Azure Active Directory Synchronization: Configuring Azure Active Directory App Registration

7.4 Configuring a Teams Administrator

MS Teams only user synchronization requires the user name and password of a user who has been configured in
Azure Active Directory as a Teams Administrator.

Procedure
1. C reate a new user whose name and password will be used for the IP Office connection:

a. Using a user account with administrator rights, login to Azure Active Directory at https://portal.azure.com.
b. Search for and select Azure Active Directory.
c. Select Users and add a new user and set a unique descriptive name for their function. For example,
IPOLink. No user licenses are required for this user.
d. Select Assigned Roles.
e. Select Add Assignment.
f. Select Teams Administrator and click Add.
2. After creating the user:

a. Login at https://admin.teams.microsoft.com using the user details and set a password when prompted. Do
not enable multi-factor authentication.
b. If a password expiry policy is in place for users, that feature should be disabled for this user. Note the
user's UserID. Then, using PowerShell, connect to Azure Active Directory and use the following
command:

Get -AzureADUser -ObjectId <user ID> -PasswordPolicies DisablePasswordExpiration

Deploying MS Teams Direct Routing with IP Office Page 59

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
7.5 Creating User and Extension Templates
This process is not needed for MS Teams only user synchronization.
When creating new IP Office users, the synchronization process can use a 'user provisioning rule' to define element
such as the starting extension number and extension type. It can also use extension and user templates to
automatically configuration those settings not defined from the Azure Active Directory details. If templates are not
used, then those settings use the IP Office system default values.

· The process below uses the template management menus to create or upload new templates. Templates can
also be created from existing users or extensions by selecting to edit their details and then clicking Save As
Template. The new template will then appear in template management menu described below.
· For MS Teams+IP Office users, the user template used must configure the user's Profile settings to one of the
following and enabled the Enable MS Teams Client setting.
· On subscription mode systems: MS Teams+IP Office users are supported by the UC User profile.

· On PLDS licensed systems: MS Teams+IP Office users are supported by the Office Worker, Teleworker
and Power User profiles.

Procedure
1. Using IP Office Web Manager, access the IP Office system configuration.

2. Select Call Management and then either Users or Extensions.

3. C lick Actions and select Template Management.
4. A list of the existing templates for user or extensions is shown. The menu can be used for a range of actions:
a. To create a new template, click +Add. For extension templates, you also need to select the type of
extension.
b. You can use the menu to edit, rename and delete existing templates.
c. You can also download the templates as .xml files.
d. You can upload .xml template files that you have previously downloaded from another system.

Deploying MS Teams Direct Routing with IP Office Page 60

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Azure Active Directory Synchronization: Creating User and Extension Templates

7.6 Creating User Provisioning Rules

This process is not needed for MS Teams only user synchronization.
When using a connection to Azure Active Directory to create new IP Office users, the connection settings specify a
'user provisioning rule' that should be applied. That rule:
· Sets the starting extension number for new users.

· Sets the extension type for the new users using either a specified extension template or specified extension
type (in which case default extension settings are applied).
· Sets user settings, other than those taken from Azure Active Directory, for the new users using a user
template. If no user template is specified, default user settings are applied.
· Optionally configures on which system the new users should be created.

Procedure
1. Using IP Office Web Manager, access the IP Office system configuration.
2. Select Solution.
3. Select Solution Settings and then User Synchronization.

4. C lick +ADD and select User Synchronization using Microsoft Teams.

5. C lick Manage User Provisioning Rules.
6. C lick +Add User Provisioning Rule.
7. Enter a name for the rule.
8. Determine how you want to configure on which IP Office system in a network the new users are created.
Either:
· Use the IP Office field to select the system on which the users should be created.

· Use a field in the each users Azure Active Directory directory settings to set the system name, FQDN or
LAN1/LAN2 IP address of the required system.
· If neither of the above methods is used, the new users are all created on the primary server.

9. If not setting the extension numbers using a value received from Azure Active Directory, set the Starting
Extension number. Otherwise, leave this field blank.
10. Select the required extension template or select an extension type. If you select an extension type, then the
default IP Office settings are applied to the new users associated extensions.
11. Select the required user template. If you do not select a user template, then the default IP Office settings are
applied to the new users.
12. C lick Save.

Deploying MS Teams Direct Routing with IP Office Page 61

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
7.7 Setting Up a Direct Routing Synchronization Process
Having configured any templates and/or user provisioning rules required, use the following process to configure
direct routing synchronization. You can configure multiple synchronization settings if necessary. For example, for
different groups of users using different voice routing policies.

Procedure
1. C heck you have the require configuration IDs from Azure Active Directory. See C onfiguring Azure Active
Directory App Registration 58 .
2. Using IP Office Web Manager, access the IP Office system configuration.
3. Select Solution.
4. Select Solution Settings and then User Synchronization.
5. C lick +ADD and select User Synchronization using Microsoft Teams.
6. Select the Connect to Directory Service tab.
a. Enter a Configuration Name to identify the purpose for this connection. For example, DirectRoutingSync.
b. For Collaboration Client, select Direct Call Routing.

c. Use User Synchronization type to select the roles that the synchronization should perform. The
selection affects the additional fields and tabs available:

Setting Description

IP Office Users Only Support the creation, updating and deletion of IP Office users to match the
users in Azure Active Directory.

Microsoft Teams Add details of the MS Teams only users to the IP Office user directory.
Users Only
· Also update their settings in MS Teams with any Office telephone number
configured for them in Azure Active Directory.
· Optionally, also assign a specific voice routing policy to the MS Teams
user settings.

Both Perform a combination of the above actions.

· The user template used should be configured to a Profile that support
MS Teams+IP Office users (Office Worker, Teleworker, Power User
or UC User) and have Enable MS Teams Client enabled.

d. Select the type of Directory.

· Use Tenant Directory to manage IP Office entries for all the customer's Azure Active Directory
users.

· Use Group Directory to manage IP Office entries for just those users who are members of a specific
Azure Active Directory group.
e. Enter the details obtained from Azure Active Directory into the matching fields.
f. C lick Test Connection and wait a couple of minutes.
g. If successful, continue with the configuration. Otherwise, check and adjust the settings.
7. If using MS Teams Users Only:
The Azure Active Directory fields from which the user name and number information is taken need to be set.
For other modes, the values are set through the Synchronize User Fields settings below.
a. In the Name Attribute field, enter the name of the Azure Active Directory user field that should be used
to populate the user name in the IP Office system directory entries. The name is displayed with a suffix of
MST. The default is to use the displayName from Azure Active Directory.
b. The Azure Active Directory field from which the user's telephone number information is taken is fixed as
businessPhones.
8. If using MS Teams Users Only or Both:
The details of the MS Teams admin user to use for the connection are needed. In addition, direct routing
settings to be applied to the users can be specified.
a. In the Microsoft Teams PowerShell Username and Microsoft Teams PowerShell Password fields,
enter the user name and password of the Azure Active Directory user configured as a MS Teams
59
administrator .
b. The Voice Routing Policy Name and Voice Routing Policy Usage fields can be used to specify the
voice routing policy assigned to the users.

Deploying MS Teams Direct Routing with IP Office Page 62

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Azure Active Directory Synchronization: Setting Up a Direct Routing Synchronization Process
· The usage must already exist in MS Teams admin.

· If the policy does not already exist, it is created and the usage is added to it. The policy is then
assigned to the users.
· If the policy already exists, it is assigned to the users with no changes the usages it contains (the
Voice Routing Policy Usage value, if set in the IP Office sync settings, is ignored).

9. If using IP Office Users Only or Both:

Specify which fields in Azure Active Directory should be mapped onto IP Office user settings, and how the new
values should be used.
a. Select the Synchronize User Fields tab:
i. Use the drop-down menus in the Microsoft Teams Fields column to select which Azure Active
Directory directory field should be used to set the value for the the matching IP Office configuration
settings.
· Selecting fields for the User Identification and Name fields is mandatory. All other fields are
optional and will use the values defined by the user/extension templates or default IP Office values.
· The User Identification must be unique. It is used to ensure that future synchronization actions to
update or delete users are applied to the correct user.

· The final pair of drop-downs can be used to set on which IP Office system in a network new users
should be created. If not set, the required system can be specified in the user provisioning rule
selected. If otherwise, new users are created on the primary system.
ii. Select which functions should be performed by this user synchronization entry. You can select any or
all of the roles:
· New - C reate new IP Office user and extension records for any user whose user identification is not
already present.
· Update - Update the settings, if required, of the user with the same user identification.

· Delete - Delete the user and extension records for any users whose user identification is not
present in the latest synchronization.
iii. If the synchronization actions should be performed regularly, click Use Schedule and define the
required schedule.
iv. C lick Preview Results. A summary of the changes that would be made is shown. If necessary, make
changes to the settings.
v. When complete, click Synchronize.
9. C lick Save.

Deploying MS Teams Direct Routing with IP Office Page 63

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 64
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 8.
Configuring the ASBCE

Deploying MS Teams Direct Routing with IP Office Page 65

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8. Configuring the ASBCE
The Avaya SBC E provides SIP connectivity between MS Teams and IP Office. These steps assume that the
installation and basic configuration of the ASBC E internal and external IP addresses has been completed.

· Use Unique Names

ASBC E setup requires configuration of multiple components, which are then linked to each other. Using unique
and descriptive names for each component greatly simplifies the process and future maintenance. For
example, do not simply name all the components relating to the IP Office connection as "IPOffice".

Summary
67
1. Example Schematic
67
2. Information Required
68
3. Get the ASBC E Version
69
4. Obtain the ASBC E C ertificates
74
5. Adding a Root C ertificate to the ASBC E
75
6. Adding an Identity C ertificate to the ASBC E
76
7. Define the IP Office Server Interworking Profile
78
8. Define the MS Teams Server Interworking Profile
80
9. C reate a TLS C lient Profile for the IP Office
81
10. C reate a TLS C lient Profile for MS Teams
82
11. C reate the TLS Server Profiles
83
12. C reate the SIGMA Script Files
85
13. Upload the SIGMA Scripts
86
14. C reate a SIP Server for the IP Office
88
15. C reate a SIP Server for MS Teams
90
16. Define a SIP C all Routing Profile for the IP Office
91
17. C reate a URI Group for IP Office Extensions
92
18. Define a SIP C all Routing Profile for MS Teams
94
19. C onfigure Topology Hiding for the IP Office
95
20. C onfigure Topology Hiding for MS Teams
96
21. Define the Media Rules for the IP Office
97
22. Define the Media Rules for MS Teams
99
23. C reate the Endpoint Policy Groups
100
24. C reate the SIP Signaling Interfaces
101
25. C reate the SIP Media Interfaces
102
26. C onfigure the Server Flow for IP Office
104
27. C onfigure the Server Flow for MS Teams
105
28. ASBC E Flowchart

Deploying MS Teams Direct Routing with IP Office Page 66

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE:

8.1 Example Schematic

For this documentation, the following example addresses and FQDNs were used.

· The configuration of the private and public DNS to ensure correct resolution of any FQDNs used is not
covered in this document.

8.2 Information Required

Before proceeding, ensure that you have the following information available:
1. Details for administrator access to the ASBC E using a browser. That is, the management IP address, user
name and password. The server's root password in order to run traces.
2. Software for SSH access to the ASBC E. This is required for certificate installation and downloading of trace
logs during troubleshooting.
3. The IP address of the IP Office LAN interface being used for the connection.
4. The FQDN of the ASBC E.
5. The IP address of the ASBC E internal port (A1 or A2) that will be used for the connection to the IP Office.
6. The IP address of the ASBC E external port (B1 or B2) that will be used for the connection to MS Teams.

68
Proceed to getting the ASBC E version .

Deploying MS Teams Direct Routing with IP Office Page 67

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.3 Get the ASBCE Version
The ASBC E version is needed as a value in the process for customizing the SIGMA scripts. It should also be check
to ensure that the ASBC E is running 8.1.3 or higher.

Procedure
1. After logging in to the ASBC E, note its version number in full. This must be 8.1.3 or higher.
69
2. Proceed to adding the certificates .

Deploying MS Teams Direct Routing with IP Office Page 68

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Get the ASBCE Version

8.4 Obtain the ASBCE Certificates

The ASBC E requires certificates from both MS Teams and the IP Office in order to validate the connections to each.
These certificates, and their private key files must be in base-64 format

MS Teams Certificates
To support MS Teams, the ASBC E requires the following certificates:

· MS Teams Root Certificate

This is the root certificate used by Microsoft for MS Teams. The certificate and details of the certificate can be
obtained from https://baltimore-cybertrust-root.chain-demos.digicert.com/info/index.html.

· Using the details provided, copy the text from

-----BEGIN CERTIFICATE to END
CERTIFICATE----- into a text file and save that as with the .crt file extension.
· For the examples in this document, the certificate is named BaltimoreCyberTrustRoot.crt

· ASBCE MS Teams Certificate

This certificate is used by the ASBC E to communicate with MS Teams. For details of how to request the
certificate, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#public-trusted-
certificate-for-the-sbc

o For the examples in this document, the certificate is named MSTeamsSBC.crt

IP Office Certificates
To support IP Office, the ASBC E requires the following certificates. If IP Office certificates are already present, for
example if the ASBC E is supported remote IP Office extensions, those existing certificates can also without any
further changes.
· IP Office Root Certificate
This is the root certificate used by IP Office for SIP TLS. If the IP Office root certificate is self signed,
Verification depth has to be set to 1. If the certificate is coming from external verification authority, verification
depth should be set to 2 (length of certificate chain).
o For the examples in this document, the certificate is named IPO_RootCA.pem

· IP Office Identity Certificate for the ASBCE

This is the certificate the ASBC E uses with IP Office and needs to be trusted by IP Office. It can either be an
identity certificate for another server generated by the IP Office, or one provided by the same external C A as
imported as a trusted certificate.
o For the examples in this document, the certificate is named IPO_SBCID.pem.

Summary
70
o Downloading the IP Office Root C ertificate
71
o Generating an Identity C ertificate in IP Office Web C ontrol
72
o Generating an Identity C ertificate in IP Office Web Manager
73
o Extracting the ASBC E Private Key and Identity C ertificate

Deploying MS Teams Direct Routing with IP Office Page 69

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.4.1 Downloading the IP Office Root Certificate
If the IP Office system is using a self-signed certificates, the following process can be used to download the
system's root certificate.

Procedure
1. Login to the IP Office Web C ontrol by either:

· From within IP Office Web Manager, select the primary server. C lick on and select Platform View.
· or browse to https://<IP Office IP address>:7071 and login as the Administrator.

2. Select the Settings tab and scroll down to Certificates.

3. Under CA Certificate, click on Download (PEM-encoded) and save the root_ca.pem file to your PC .
4. Proceed to generating an ID certificate for the ASBC E:
72
· For IP Office subscription mode systems with Automatic C ertificate Management enabled.
71
· For other IP Office systems.

Deploying MS Teams Direct Routing with IP Office Page 70

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Obtain the ASBCE Certificates
8.4.2 Generating an Identity Certificate in IP Office Web Control
When the IP Office is using self-signed certificates, it can also generate an identity certificate for the ASBC E to use
for its connections to the IP Office. The necessary identity key file is extracted from the identity certificate in a later
process.
· On subscription mode systems using Automatic Certificate Management, this process is performed from IP
72
Office Web Manager. See Generating an IP Office Identity C ertificate in IP Office Web Manager .

Procedure
1. Login to the IP Office Web C ontrol by either:
· From within IP Office Web Manager, select the primary server. C lick on and select Platform View.
· or browse to https://<IP Office IP address>:7071 and login as the Administrator.

2. Go to Settings tab and scroll down to Certificates.

3. C heck Create certificate for a different machine.

4. Enter the following data:

a. Machine IP: Enter the internal IP address of the ASBC E. That is, either the A1 or A2 interface of the
ASBC E to which the IP Office connects.
b. Password: Enter a password to encrypt the certificate and key.
· Note that if any special characters are used in the password, to enter that password at the command
line requires the character to be prefixed with a \. For example, a @ in the password would be typed
as \@ at the command line.
c. Subject Name: Enter the FQDN of the ASBC E.
d. Subject Alternative Name(s): Enter comma separate values for the DNS:<FQDN> and IP:<IP
address>.
5. C lick Regenerate.
6. C lick on the link in the popup window and save the file.

71
7. Proceed to extracting the private key and identity certificate .

Deploying MS Teams Direct Routing with IP Office Page 71

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.4.3 Generating an Identity Certificate in IP Office Web Manager
When the IP Office is using self-signed certificates, it can also generate an identity certificate for the ASBC E to use
for its connections to the IP Office. The necessary identity key file is extracted from the identity certificate in a later
process.
· This process is only for subscription mode systems using Automatic Certificate Management. For other
71
systems, see Generating an IP Office Identity C ertificate in IP Office Web C ontrol .

Procedure
1. Login to IP Office Web Manager for the subscription mode IP Office system.
2. Select Security | Security Settings.

3. If the system is in a Server Edition network, click on the next to the primary server.
4. Select Certificates.
5. C lick Regenerate.
6. Enable For Different Machine.

7. In Subject Name enter the FQDN of the ASBC E.

8. In Subject Alternative Name(s), enter any additional values for other IP Office servers and services to
which the ASBC E may also need to connect.
9. C lick OK. Wait up to a minute whilst the certificate is generated.

10. When prompted, set an encryption password for the identity certificate and click Yes.
11. The browser will prompt you to download and save the certificate file.
71
12. Proceed to extracting the private key and identity certificate .

Deploying MS Teams Direct Routing with IP Office Page 72

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Obtain the ASBCE Certificates
8.4.4 Extracting the ASBCE Private Key and Identity Certificate
The IP Office identity certificate created for the ASBC E is a single file. For the ASBC E configuration it needs to be
split into two files; a certificate file and a private key for the certificate. This splitting can be done using utilities
provided by the ASBC E.

Procedure
1. Using SFTP, connect to the ASBC E management IP address using port 222 and the ipcs login.
71
2. C opy the IP Office identity certificate created for the ASBC E (SBCE_ID.p12) to the /home/ipcs
directory.
3. Using SSH, login to the ASBC E management IP using port 222 and ipcs login.
4. Enter the command sudo su and type the root password.
5. Enter the following commands. When prompted for a password or PEM pass phrase, enter the password
specified when generating an identity certificate for the ASBC E 71 .
· Note that if any special characters are used in the password, to enter that password at the
command line requires the character to be prefixed with a \. For example, a @ in the password
would be typed as \@ at the command line.

a. openssl pkcs12 -in SBCE_ID.p12 -out SBCE_ID.crt -nokeys -clcerts

b. openssl pkcs12 -in SBCE_ID.p12 -out SBCE_ID.key -nocerts
The whole sequence should look similar to the following:
[root@sbce ipcs]# openssl pkcs12 -in SBCE_ID.p12 -out SBCE_ID.crt -nokeys -clcerts
Enter Import Password: ********
MAC verified OK
Enter PEM pass phrase: ********
Verifying - Enter PEM pass phrase: ********
[root@sbce ipcs]# openssl pkcs12 -in SBCE_ID.p12 -out SBCE_ID.key -nocerts
Enter Import Password: ********
MAC verified OK
Enter PEM pass phrase: ********
Verifying - Enter PEM pass phrase: ********
6. C opy the new SBCE_ID.crt and SBCE_ID.key files from ASBC E to your PC
71
7. The SBCE_ID.crt file contains the ID certificate we generated for ASBC E , the IP Office root C A
certificate, and the private key. To be able to properly import this file to the ASBC E, the C A certificate and
the private key must be removed from this file.
a. Open SBCE_ID.crt in WordPad on your PC .
b. Remove all lines except those which are between and including the first BEGIN CERTIFICATE and END
CERTIFICATE lines. The resulting file should look similar to the following:

74
8. Proceed to adding the root certificates to the ASBC E .

Deploying MS Teams Direct Routing with IP Office Page 73

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.5 Adding a Root Certificate to the ASBCE
The following process adds root certificates to the ASBC E. Do this for both the MS Teams and IP Office root
certificates.

Procedure
69
First obtain certificates for the ASBC E , then:

1. Login to ASBC E web interface.

2. Go to TLS Management | Certificates.
3. C lick Install.

a. Type: Select CA Certificate.

b. Name: Enter a unique descriptive name for the root C A certificate.
c. Allow Weak Certificate/Key: Enable this option.
d. Certificate File: C lick Choose File and select the certificate file.
4. C lick Upload.
5. If a warning that this is a self-signed certificate is displayed, click Proceed.
6. The certificate is displayed. C lick Install and then Finish.
7. Repeat the process for the next root certificate.
75
8. Process to adding the identity certificates .

Deploying MS Teams Direct Routing with IP Office Page 74

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Adding a Root Certificate to the ASBCE

8.6 Adding an Identity Certificate to the ASBCE

The following process adds identity certificates to the ASBC E. Do this for both the MS Teams and IP Office root
certificates.

Procedure
74
First add the root certificates to the ASBC E , then:

1. Login to ASBC E web interface.

2. Go to TLS Management | Certificates.
3. C lick Install.

a. Type: Select Certificate.

b. Name: Enter a unique descriptive name for the certificate.
c. Certificate File: C lick Choose File and select the identity certificate.
d. Trust Chain File: Leave this field empty.
e. Key: Select Upload Key File.
f. Key File: C lick Choose File and select the private key file for the identity certificate.
4. C lick Upload. The certificate is displayed.
5. C lick Install and then Finish.
76
7. Proceed to defining the server interworking profile for the IP Office .

Deploying MS Teams Direct Routing with IP Office Page 75

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.7 Define the IP Office Server Interworking Profile
An interworking profile is needed to support the SIP connection from the IP Office (the MS Teams Line).

Procedure
75
First add the identity certificates to the ASBC E , then:
1. Select Configuration Profiles and then Server Interworking.

2. C lick Add.
3. For the Profile Name, enter a unique descriptive name.
4. On the General settings tab:
a. Set the Refer Handling to Yes.
b. Set the URI Scheme to SIP.
5. On the Advanced settings tab:
a. Set Record Routes to Both Sides and Extensions to Avaya.
6. All other tabs should be left as their default values. C lick Finish.

7. The IP Office interworking profile should look similar to the following:

Deploying MS Teams Direct Routing with IP Office Page 76

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Define the IP Office Server Interworking Profile

78
8. Proceed to creating a server interworking profile for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 77

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.8 Define the MS Teams Server Interworking Profile
An interworking profile is needed to support the SIP connection from the IP Office (the MS Teams Line).

Procedure
76
First define the IP Office server interworking profile , then:
1. Select Configuration Profiles and then Server Interworking.

2. C lick Add.
3. For the Profile Name, enter a unique descriptive name.
4. On the General settings tab:
a. Set the Hold Support to Microsoft Teams
b. Set the Refer Handling to Yes.
c. Set the Delayed Offer to Yes.
d. Set the URI Scheme to SIP.
5. On the Advanced settings tab, set Record Routes to Both Sides and Extensions to Lync.

6. All other tabs should be left as their default values. C lick Finish. The MS Teams interworking profile should
look similar to the following:

Deploying MS Teams Direct Routing with IP Office Page 78

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Define the MS Teams Server Interworking Profile

80
7. Proceed to creating a TLS client profile for the IP Office .

Deploying MS Teams Direct Routing with IP Office Page 79

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.9 Create a TLS Client Profile for the IP Office
Each connection to the ASBC E requires a TLS client and TLS server entry in the ASBC E configuration. This process
creates a TLS client profile for the IP Office connection.

Procedure
78
First define the MS Teams server interworking profile , then:

1. Select TLS Management and then Client Profiles.

2. C lick Add.
3. For the Profile Name, enter a unique descriptive name to help select this profile later in other menus. For
example, IPO_Client.
4. For the Certificate, select the IP Office identity certificate created for the ASBC E. For this example,
IPO_SBCID.pem.
5. For Peer Certificate Authorities, select the IP Office system's root certificate. For this example,
IPO_RootCA.pem.
6. For the Verification Depth, :

· If the IP Office root certificate is self-signed, set this to 1. That includes subscription systems using
Automatic Certificate Management.
· If the certificate is coming from external verification authority, set this to 2 (length of certificate chain).

7. C lick Next and then Finish.

8. The TLS client profile for the IP Office system should look similar to the following.

81
9. Proceed to creating TLS client profile for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 80

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Create a TLS Client Profile for the IP Office

8.10 Create a TLS Client Profile for MS Teams

Each connection to the ASBC E requires a TLS client and TLS server entry in the ASBC E configuration. This process
creates a TLS client profile for the MS Teams connection.

Procedure
80
First create a TLS client profile for the IP Office , then:

1. Select TLS Management and then Client Profiles.

2. C lick Add.
3. For the Profile Name, enter a unique descriptive name to help select this profile later in other menus.
4. For the Certificate, select the certificate requested from MS Teams for the ASBC E. For this example,
MSTeamsSBC.crt.
5. For Peer Certificate Authorities, select the MS Teams root certificate. That is the
BaltimoreCyberTrustRoot.crt.
6. For the Verification Depth , set this to 2.
7. C lick Next and then Finish.

8. The TLS client profile for MS Teams should look similar to the following.

80
9. Proceed to creating TLS Server profiles .

Deploying MS Teams Direct Routing with IP Office Page 81

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.11 Create the TLS Server Profiles
Define the TLS server profiles for the IP Office and MS Teams connections.

Procedure
81
First create a TLS client profile for MS Teams , then:
1. Select TLS Management | Client Profiles.

2. C lick Add and create a TLS server profile for the IP Office.
a. Profile Name - Enter a unique descriptive name to help select this profile later in other menus.
b. Certificate - Select the IP Office identity certificate created for the ASBC E.
c. Peer Verification - Select None.
d. C lick Next and then Finish.
e. The TLS server profile setting for the IP Office system should look similar to the following.

3. C lick Add and create a TLS server profile for MS Teams.

a. Profile Name - Enter a unique descriptive name to help select this profile later in other menus.
b. Certificate - Select the certificate requested from MS Teams for the ASBC E.
c. Peer Verification - Select None.
d. C lick Next and then Finish.

e. The TLS server profile setting for MS Teams should look similar to the following.

83
4. Proceed to create the SIGMA scripts .

Deploying MS Teams Direct Routing with IP Office Page 82

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Create the TLS Server Profiles

8.12 Create the SIGMA Script Files

SIGMA (Signal Manipulation) scripts are used by the ASBC E to modify the content of SIP signaling headers.

Procedure
82
First create the TLS server profiles , then:
1. On your PC , create 2 text files. One containing the script for the IP Office, the other the script for MS Teams.
The details for the script files are listed below.
85
2. Proceed to uploading the SIGMA scripts .

The IP Office SIGMA Script

The following is a template for the SIGMA script used for the connection between the ASBC E and the IP Office. Use
this template to create a text file on your PC .
For the examples in this document, the IP Office script file is named Add_rr
within session "INVITE"
{
act on request where %DIRECTION="INBOUND" and %ENTRY_POINT="AFTER_NETWORK"
{
%ContactValue = %HEADERS["Contact"][1];
%HEADERS["Record-Route"][1] = %ContactValue;
}
}
The MS Teams SIGMA Script
The following (overleaf) is a template for the SIGMA script used for the connection between the ASBC E and MS
Teams. Use this template to create a text file on your PC .
For the examples in this document, the MS Teams script file is named sdpchange.
In the sample script shown overleaf:

1. Replace each instance of <ASBCE_FQDN> with the public FQDN of the ASBC E.

2. Replace each instance of <ASBCE_IP_ADDRESS> with the public IP address of the ASBC E to which that
FQDN resolves.

3. Replace <ASBCE_VERSION> with AVAYA SBCE-<version> where <version> is the Version value
shown on the ASBC E's initial menu after logging in. See Get the ASBC E Version 68 .

Deploying MS Teams Direct Routing with IP Office Page 83

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
The MS Teams SIGMA Script (Continued)
The script is as follows prior to replacing the values indicated by < > brackets.
within session "all"
{
act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
%SDP[1].regex_replace("a=sendonly","a=inactive");
%SDP[1].regex_replace("a=recvonly","a=inactive");
}
}
within session "all"
{
act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
%HEADERS["Contact"][1].URI.HOST = "<ASBCE_FQDN>";
%HEADERS["Record-Route"][1].URI.HOST = "<ASBCE_FQDN>";
%HEADERS["From"][1].URI.USER.regex_replace("^214","+1214");
%HEADERS["To"][1].URI.USER.regex_replace("^719","+1719");
%HEADERS["Request_Line"][1].URI.USER.regex_replace("719","+1719");
}
}
within session "all"
{
act on request where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
%HEADERS["X-MS-SBC"][1] = "<ASBCE_VERSION>";
}
}
within session "all"
{
act on message where %DIRECTION="INBOUND" and %ENTRY_POINT="PRE_ROUTING"
{
%HEADERS["Request_Line"][1].URI.HOST = "<ASBCE_IP_ADDRESS>";
if (%HEADERS["Record-Route"][1].regex_match("<ASBCE_FQDN>")) then
{
%HEADERS["Record-Route"][1].regex_replace("<ASBCE_FQDN>","<ASBCE_IP_ADDRESS>");
}
if (%HEADERS["Record-Route"][2]. regex_match("<ASBCE_FQDN>")) then
{
%HEADERS["Record-Route"][1].regex_replace("<ASBCE_FQDN>","<ASBCE_IP_ADDRESS>");
}
if (%HEADERS["Route"][1].regex_match("<ASBCE_FQDN>")) then
{
%HEADERS["Route"][1].regex_replace("<ASBCE_FQDN>","<ASBCE_IP_ADDRESS>");
}
if (%HEADERS["Route"][2].regex_match("<ASBCE_FQDN>")) then
{
%HEADERS["Route"][2].regex_replace("<ASBCE_FQDN>","<ASBCE_IP_ADDRESS>");
}
}
}
within session "INVITE"
{
act on response where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
if (%SDP[1].regex_match("c=IN IP4 0.0.0.0")) then
{
%SDP[1].regex_replace("c=IN IP4 0.0.0.0","c=IN IP4 <ASBCE_IP_ADDRESS>");
}
}
}

Deploying MS Teams Direct Routing with IP Office Page 84

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Create the SIGMA Script Files

8.13 Upload the SIGMA Scripts

Upload the two SIGMA script files to the ASBC E.

Procedure
83
First create the SIGMA script files , then:
1. Select C onfiguration Profiles and then Signaling Manipulation.

2. C lick Upload and select the SIGMA file created for the IP Office.

3. C lick Upload again and select the SIGMA file created for MS Teams.
86
4. Proceed to creating SIP server entries for the IP Office .

Deploying MS Teams Direct Routing with IP Office Page 85

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.14 Create a SIP Server for the IP Office
A SIP server definition is required for each server connected to the ASBC E.

Procedure
85
First upload the SIGMA scripts , then:
1. Select Services and then SIP Server.

2. C lick Add and add a SIP server profile for the IP Office.
3. Enter a Profile Name. C lick Next.
4. In the General Settings menu:

a. Set the Server Type to Call Server.

b. Set the TLS Client Profile to the one previously created for the IP Office connection.
c. Set the address, port and transport details to match the IP Office setting.
d. C lick Next.
5. There are no changes to the default Authentication settings. C lick Next.
6. In the Heartbeat settings:

a. Select Enable heartbeat.

b. For the From URI and To URI values, enter a dummy value.
c. C lick Next.
7. There are no changes to the default Registration and Ping settings. C lick Next to skip each.

Deploying MS Teams Direct Routing with IP Office Page 86

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Create a SIP Server for the IP Office
8. In the Advance settings:

a. Enable Grooming - Enable this setting.

o Note: This SIP Server connection with the IP Office has grooming enabled. For a SIP Server for
endpoints such as remote extension, any similar connection to the IP Office should have grooming
disabled because the IP Office does not support TC P connection sharing between endpoints.
b. Interworking Profile - Select the interworking profile previously created for the IP Office.
c. Signaling Manipulation Script - Select the SIGMA script uploaded for the IP Office.
d. C lick Finish.
88
9. Proceed to creating a SIP server entry for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 87

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.15 Create a SIP Server for MS Teams
C reate a SIP Server record for MS Teams as below.

Procedure
86
First create a SIP server for the IP Office , then:
1. Select Services and then SIP Servers.

2. C lick Add and add a SIP server profile for MS Teams.

3. Enter a Profile Name. C lick Next.
4. In the General Settings menu:

a. Set the Server Type to Trunk Server.

b. Set the TLS Client Profile to the one previously created for the MS Teams connection.
c. Add three entries for the address/port/transport settings. These are:
· sip.pstnhub.microsoft.com/5061/TLS

· sip2.pstnhub.microsoft.com/5061/TLS

· sip3.pstnhub.microsoft.com/5061/TLS

d. C lick Next.
5. There are no changes to the default Authentication settings. C lick Next.

6. In the Heartbeat settings:

a. Select Enable heartbeat.

b. C lick Next.
7. There are no changes to the default Registration and Ping settings. C lick Next to skip each.

Deploying MS Teams Direct Routing with IP Office Page 88

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Create a SIP Server for MS Teams
8. In the Advance settings:

a. Enable Grooming - Enable this setting.

a. Interworking Profile - Select the interworking profile previously created for MS Teams.
b. Signaling Manipulation Script - Select the SIGMA script uploaded for MS Teams.
c. C lick Finish.
90
9. Proceed to defining the routing for SIP calls .

Deploying MS Teams Direct Routing with IP Office Page 89

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.16 Define a SIP Call Routing Profile for the IP Office
Routing information is required for routing calls to the configured SIP Servers. The IP addresses, ports and
transport defined here are used as the destination addresses for signalling messages.
This process creates a routing profile for the connection to the IP Office.

Procedure
88
First create a SIP server for MS Teams , then:
1. Select Global Profiles and then Routing.
2. C lick Add.
3. Enter a Profile Name and click Next.
4. In the routing profile settings, click Add to specify the IP route details:

a. Set the Priority/Weight to 1.

b. For the Server Configuration, select the SIP server entry created for the IP Office.
c. In the Next Hop Address, enter the address for the IP Office and the port to use.
5. C lick Finish.
91
6. Proceed to creating a URI group for IP Office extensions .

Deploying MS Teams Direct Routing with IP Office Page 90

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Define a SIP Call Routing Profile for the IP Office

8.17 Create a URI Group for IP Office Extensions

In some scenarios, such as some call transfers, MS Teams may send a REFER addressed with an IP Office
extension number and the MS Teams domain. A URI group can be used to match that traffic to a SIP C alling Route
that redirects such calls back to the IP Office system.

Procedure
90
First define a SIP call routing profile for the IP Office , then:

1. Select Configuration Profiles and then URI Groups.

2. C lick Add and set a unique descriptive name for the URI group.
3. C lick Add a define the string that should trigger a match. For example:
4. Repeat the steps above for any other extension number patterns that are required.
5. C lick Finish.
6. The URI group details should look similar to the following:

· In our example scenario, IP Office extensions use the range 200 to 299. MS Teams only users with
extension numbers use the range 400 to 499. In our URI Group, only an entry of the IP Office range is
required.
92
7. Proceed to creating a SIP call route profile for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 91

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.18 Define a SIP Call Routing Profile for MS Teams
Routing information is required for routing calls to the configured SIP Servers. The IP addresses, ports and
transport defined here are used as the destination addresses for signalling messages.
This process creates a routing profile for the connection to MS Teams.

Procedure
91
First create a URI group for IP Office extensions , then:
1. Select Global Profiles and then Routing.
2. Enter a Profile Name and click Next.
3. Create a route for IP Office extension numbers:
In some scenarios, such as some call transfers, MS Teams may send a REFER addressed with an IP Office
extension number and the MS Teams domain. Using the URI match previously configured, this entry routes
such calls back to the IP Office system.
a. C lick Add.
b. For the URI Group, select the group previously created to match IP Office extension numbers. C alls
addressed to these should be rerouted back to the IP Office.

c. In the routing profile settings, click Add and add a call route with the following setting:
i. Set the Priority/Weight to 1.
ii. For the Server Configuration, select the SIP server profile entry created for the IP Office.
iii. For the Next Hop Address, enter the address for the IP Office and the port to use. For example:
10.1.1.17:5061.
d. The settings should now look similar to the following:

4. Create a route for all other numbers addressed to MS Teams:

a. C lick Add.
b. Enter a Profile Name and click Next.
c. In the routing profile settings, click Add and add a call route with the following setting:
i. Set the Priority/Weight to 2.
ii. For the Server Configuration, select the SIP server entry created for MS Teams.
iii. For the Next Hop Address, enter sip.pstnhub.microsoft.com:5061.
d. Repeat the above to add sip2.pstnhub.microsoft.com:5061 with priority 2 and
sip3.pstnhub.microsoft.com:5061 with priority 3.

Deploying MS Teams Direct Routing with IP Office Page 92

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Define a SIP Call Routing Profile for MS Teams
e. The settings should now look similar to the following:

f. C lick Finish.
5. The final routing profile should look similar to the following:

94
6. Proceed to configuring topology hiding .

Deploying MS Teams Direct Routing with IP Office Page 93

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.19 Configure Topology Hiding for the IP Office
Topology Hiding is used to modify the content of SIP headers. This is used for two main roles:
· As a security feature to preventing private enterprise network information from being propagated to the
untrusted public network.
· As an interoperability tool to adapt the headers to the IP addresses or domains expected by the remote the
service provider or enterprise networks.

Procedure
92
First define a SIP call routing profile for MS Teams , then:
1. Select Global Profiles and then Topology Hiding.
2. Select the default profile and click Clone.
3. Enter a unique descriptive name for the profile for connections to the IP Office and click Finish.
4. Select the new profile and click Edit.

5. Set the To, Request-Line, Refer-To, Referred-By and From headers to Overwrite. For each, set the
Overwrite Value to the IP Office system's SIP domain .
95
6. Proceed to creating topology hiding for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 94

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Configure Topology Hiding for the IP Office

8.20 Configure Topology Hiding for MS Teams

Topology hiding is used to modify the content of SIP headers. This is used for two main roles:
· As a security feature to preventing private enterprise network information from being propagated to the
untrusted public network.
· As an interoperability tool to adapt the headers to the IP addresses or domains expected by the remote the
service provider or enterprise networks.

Procedure
94
First configure topology hiding for the IP Office , then:
1. Select Global Profiles and then Topology Hiding.
2. Select the default profile and click Clone.
3. Enter a unique descriptive name for the profile for connections to the MS Teams and click Finish.
4. Select the new profile and click Edit.

a. Set the From header to Overwrite, with the Overwrite Value set to the FQDN of the ASBC E.
b. C heck that all the other values at their defaults of Auto.
96
5. Proceed to creating the media rules for IP Office .

Deploying MS Teams Direct Routing with IP Office Page 95

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.21 Define the Media Rules for the IP Office
Media rules are used to define RTP media packet parameters, such as prioritizing encryption techniques and packet
encryption techniques. This process creates the media rules used for the MS Teams connection.

Procedure
95
First configure topology hiding for MS Teams , then:

1. Select Domain Policies and then Media Rules.

2. Select the existing default-low-med rule and click Clone.
3. Enter a unique descriptive name for the new media rule and click Finish.
4. Select the new media rule and click Edit.
5. On the Encryption settings tab, set the settings as shown below:

6. C lick Finish.
97
7. Proceed to creating the media rules for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 96

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Define the Media Rules for the IP Office

8.22 Define the Media Rules for MS Teams

Media rules are used to define RTP media packet parameters, such as prioritizing encryption techniques and packet
encryption techniques. This process creates the media rules used for the MS Teams connection.

Procedure
96
First define the media rules for the IP Office , then:

1. Select Domain Policies and then Media Rules.

2. Select the existing default-low-med rule and click Clone.
3. Enter a unique descriptive name for the new media rule and click Finish.
4. Select the new media rule and click Edit.
5. On the Encryption settings tab, set the settings as shown below:

Deploying MS Teams Direct Routing with IP Office Page 97

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 6. On the Advanced settings tab, set the settings as shown below:

7. C lick Finish.
99
8. Proceed to creating the endpoint policies .

Deploying MS Teams Direct Routing with IP Office Page 98

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Define the Media Rules for MS Teams

8.23 Create the Endpoint Policy Groups

Endpoint policy groups comprise a group of endpoint policy sets, all of which are specifically configured using a
number of relevant parameters.

Procedure
97
First define the media rules for MS Teams , then:

1. Select Domain Policies and then Endpoint Policy Groups.

2. Create an endpoint policy for the IP Office:
a. Select the existing default-low policy and click Clone.
b. Enter a unique descriptive name for the new policy and click Finish.
c. Select the new policy and click Edit.
d. Set the Media Rule to the media rule previously created for the IP Office connection.

e. C lick Finish.
3. Create an endpoint policy for MS Teams:
a. Select the existing default-low policy and click Clone.
b. Enter a unique descriptive name for the new policy and click Finish.
c. Select the new policy and click Edit.
d. Set the Media Rule to the media rule previously created for the MS Teams connection.

e. C lick Finish.
100
4. Proceed to creating the SIP signaling interfaces .

Deploying MS Teams Direct Routing with IP Office Page 99

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.24 Create the SIP Signaling Interfaces
A signaling interface needs to be defined for each SIP Server.

Procedure
99
First create the endpoint policy groups , then:
1. Select Network & Flows and then Signaling Interface.

2. Add a signaling interface for the IP Office:

a. C lick Add.
b. In the Name field, enter a description name for the interface.
c. In the IP Address field, select the ASBC E's internal network interface.
d. Set the ports to match those configured for SIP on the IP Office system.
e. In the TLS Profile, select the TLS server profile previously created for the IP Office.
f. C lick Finish.
3. Add a signaling interface for MS Teams:

a. C lick Add.
b. In the Name field, enter a description name for the interface.
c. In the IP Address field, select the ASBC E's external network interface.
d. Set the ports to match those configured for SIP with MS Teams.
e. In the TLS Profile, select the TLS server profile previously created for MS Teams.
f. C lick Finish.
4. The final settings should appear similar to the following:

101
5. Proceed to creating SIP media interfaces .

Deploying MS Teams Direct Routing with IP Office Page 100

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Create the SIP Signaling Interfaces

8.25 Create the SIP Media Interfaces

A media interface needs to be defined for each SIP Server to send and receive media (RTP or SRTP).

Procedure
100
First create the SIP signaling interfaces , then:
1. Select Network & Flows and then Media Interface.

2. Add a media interface for the IP Office:

a. C lick Add.
b. In the Name field, enter a description name for the interface.
c. In the IP Address field, select the ASBC E's internal network interface.
d. Set the ports range to match the RTP port range configured on the IP Office system. The default range is
46750 to 50750.
e. C lick Finish.
3. Add a media interface for MS Teams:

a. C lick Add.
b. In the Name field, enter a description name for the interface.
c. In the IP Address field, select the ASBC E's external network interface.
d. Set the ports to match those used for SIP media with MS Teams.
e. C lick Finish.
4. The final settings should appear similar to the following:

102
5. Proceed to configuring the server flow .

Deploying MS Teams Direct Routing with IP Office Page 101

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.26 Configure the Server Flow for IP Office
When a packet is received by the ASBC E, its contents (IP addresses, URIs, etc.) are used to determine which
server flow it matches. Once the server flow is determined, the policies for the destination endpoint are applied.

Procedure
101
First create the SIP media interfaces , then:

1. Select Network & Flows and then End Point Flows.

2. Select the Server Flows tab.
3. Create a flow for calls from the IP Office to MS Teams:
a. C lick Add.
b. For the Flow Name, enter a unique descriptive name.

c. In the SIP Server Profile, Signaling Interface, Media Interface, End Point Policy Group and
Topology Hiding fields, select entries created for the IP Office.
d. For the Received Interface, and Routing Profiles, select the signaling interface and routing profiles
created for the MS Teams.
e. C lick Finish.
4. Create a server flow for calls being returned back to the IP Office:
a. C lick Add.

Deploying MS Teams Direct Routing with IP Office Page 102

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: Configure the Server Flow for IP Office
b. For the Flow Name, enter a unique descriptive name.

c. In the SIP Server Profile, Signaling Interface, Media Interface and End Point Policy Group
fields, select entries created for the IP Office.
d. For the Received Interface, and Routing Profiles, also select the profiles created for IP Office rather
than MS Teams.
e. C lick Finish.
5. The server flow details should look similar to the following:

104
6. Proceed to creating a server flow for MS Teams .

Deploying MS Teams Direct Routing with IP Office Page 103

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
8.27 Configure the Server Flow for MS Teams
When a packet is received by the ASBC E, its contents (IP addresses, URIs, etc.) are used to determine which
server flow it matches. Once the server flow is determined, the policies for the destination endpoint are applied.

Procedure
102
First configure the server flow for IP Office , then:

1. Select Network & Flows and then End Point Flows.

2. Select the Server Flows tab.
3. C lick Add.

4. For the Flow Name, enter a unique descriptive name.

5. In the SIP Server Profile, Signaling Interface, Media Interface, End Point Policy Group and
Topology Hiding fields, select entries created for the MS Teams.
6. For the Received Interface, and Routing Profiles, select the signaling interface and routing profiles
created for the IP Office.
7. C lick Finish. The server flow details should look similar to the following:

Deploying MS Teams Direct Routing with IP Office Page 104

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Configuring the ASBCE: ASBCE Flowchart

8.28 ASBCE Flowchart

The following diagram is a summary of the elements configured on the ASBC E for our example scenario.

Deploying MS Teams Direct Routing with IP Office Page 105

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 106
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 9.
Using Regular Expressions
(regex)

Deploying MS Teams Direct Routing with IP Office Page 107

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
9. Using Regular Expressions (regex)
Several MS Teams menus use 'dial patterns' to match the number dialed or to be dialed. These patterns use regex
(regular expression) strings to check for matches to the dialed digits. For example, the regex pattern ^2\d{2}$
matches any three-digit number beginning with a 2.
· In Dial plans, they are used to match numbers dialed by a user and then apply a number translation.

· In Voice routes, they are used to match the number on outgoing calls to the routes for the call.

For additional information, go to:

· https://docs.microsoft.com/en-us/dotnet/standard/base-types/regular-expression-language-quick-reference

· https://support.microsoft.com/en-us/topic/6ea76427-0892-4237-b024-10b418dcb05e

· https://regex101.com/
This site provides a useful tool for testing the operation of your own regex strings.

Summary
109
· Interpreting Regex Strings
110
· Regex Syntax
111
· Telephone Number Examples
111
· Digit Translations

Deploying MS Teams Direct Routing with IP Office Page 108

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Using Regular Expressions (regex):

9.1 Interpreting Regex Strings

The following take you through some examples of how regex strings are interpreted and how they operate to match
particular types of telephone number.

Example 1: Extension Number Matching

In our example scenario, we wanted a string that matched any 3-digit number that begins with a 2. That will match
internal extension numbers on our IP Office system. For this, we used the following regex string:

^\+?(2\d{2})$
The string works as follows:

^\+?(2\d{2})$ · The ^ starts matching at the start of the number.

^\+?(2\d{2})$ · The \+ matches a literal + character (the E.164 international prefix indicator). The \ is
needed as a + on its own is a specific regex command.

^\+?(2\d{2})$ · The ? modifies the preceding \+ to mean match if it is present or not.

^\+?(2\d{2})$ · The ( ) brackets group elements. This can be important when translating numbers, as
translations can include references the digits that matched the different pairs of
brackets.

^\+?(2\d{2})$ · The 2 matches a 2 digit at the start of the number.

^\+?(2\d{2})$ · The \d matches any digit. The \ is needed to indicate that it is not a match for an
alphabetic d character.

^\+?(2\d{2})$ · The {2} modifies the preceding element to match 2 instance of that element.

^\+?(2\d{2})$ · So the \d{2} operate together to match any two digits.

^\+?(2\d{2})$ · The $ matches the end of the string. Including this means the pattern will not match
longer numbers that begin with a 2.

Example 2: International Number Matching

In our example scenario, we also wanted a string that matched any international calls. That is, calls prefixed with
either + or 00 (the UK dialing prefix for international calls). For this, we used the following regex string:

^(\+|00)(.+)$
The string works as follows:

^(\+|00)(.+)$ · The ^ starts matching at the start of the number.

^(\+|00)(.+)$ · The ( ) brackets group elements for processing and, potentially, for future translation.

^(\+|00)(.+)$ · The \+ matches a literal + character.

^(\+|00)(.+)$ · The | separates alternate match possibilities.

^(\+|00)(.+)$ · So the 1st pair of brackets indicates a match to any number beginning with + or 00.

^(\+|00)(.+)$ · The . matches any digit or character.

^(\+|00)(.+)$ · The + modifies the preceding . to match any number of matches.

^(\+|00)(.+)$ · So the .+ operate together to match any number of digits and characters.

^(\+|00)(.+)$ · The 2nd pair of brackets enclose the match for any number of characters. In this
example, a translation can use the value $2 to refer to the matched characters, without
their + or 00 prefix, since that was matched by the first pair of brackets.

^(\+|00)(.+)$ · The $ matches the end of the string.

Deploying MS Teams Direct Routing with IP Office Page 109

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
9.2 Regex Syntax
This is not a comprehensive list. It only considers items useful in the matching of telephone numbers.

String Position
Enclose a pattern with these ensures matching to the full number only.

Syntax Description

^ Start of String: A ^ indicates the start of the string.

$ End of String: A $ matches the end of the string.

Character Types
Syntax Description

. Any Character: Match any character.

\d Any Digit: Match any digit. This just matches 0 to 9, not the dialing characters *, + and #.
\ Escape: Use \ to escape characters that otherwise are regex commands. For example, \* matches a
* digit, \+ matches a +.

Group
Syntax Description

| Or: Separate alternate possible matches. For example:569|669 matches either 569 or 669. Multiple
alternates can be specified, for example: 569|669|779.
() Group: Use ( ) brackets to group syntax. When performing digit translations, the element $1 in a
translation represents the digits matched by the syntax in the first pair of ( ) brackets in the original
pattern, $2 the second pair of brackets and so on.
[] Range of Characters: Use [ ] square brackets to group specific characters or a character range to
match. For example: [569] matches a 5, 6 or 9; [5-7] matches a 5, 6 or 7; [0-9*#+] matches
any telephone number character.
· When used in [ ] brackets, characters such as + and * are literal matches.
· Use a ^ character inside the [] brackets to perform a non-match. For example: [^569] matches
an digit other than 5, 6 or 9.

Number of Matches
Syntax Description

? Match zero or one: Use a ? question mark to match zero or one occurrences of the preceding
element. For example: ^\+? matches numbers beginning with or without a + prefix.

* Match zero or more: Use an * to match zero or more occurrences of the preceding element. For
example: ^1.*$ matches 1 and numbers beginning with a 1. To match an actual *, use \*

+ Match one or more: Use a + plus sign to match one or more occurrences of the preceding element.
For example: ^1.+$ matches number beginning with a 1 but not just 1. To match an actual +, use \+

{n} Match N times: Match the preceding item exactly n times. For example: ^.{3} matches 3-digit
numbers.
{n,} Match N or more times: Match the preceding item n or more times. For example: ^. {3,}$
matches 3-digit or longer numbers.
{,m} Match up to M times: Match the preceding item up to m times. For example: ^.{,4}$ matches
numbers up to 4-digits long.
{n,m} Match between N to M times: Match the preceding item at least m times, but no more than n times.
For example: ^.{3,4}$ matches 3 and 4-digit numbers.

Deploying MS Teams Direct Routing with IP Office Page 110

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Using Regular Expressions (regex): Telephone Number Examples

9.3 Telephone Number Examples

The following are some example regex strings for telephone number matching.

Purpose Pattern Description

Match any numeric ^\d+$ –

telephone number

Match any dialing ^.+$ This differs from the above match for any numbers as it also
includes +, * and # elements that may occur in telephone
number.

^[0-9*#]$ This differs from the above match in that is only matches
telephone numbers using the numeric digits, * and #.

Match any seven digit ^(\d{7})$ This would for example, match the dialing of a local number in
number the US. In order to be properly handled, the number would
require a transform to add the digits for national dialing with the
local area code.

Match any eleven digit ^\+1(\d{10})$ This would for example, match the dialing of a national number
number beginning with a within the US.
+1

Match any eleven digit ^\+1(555|666) This would for example, match the dialing of national numbers
number beginning with (\d{7})$ in the US with the particular area codes 555 or 565.
1555 or 1666

9.4 Digit Translations

46
The MS Teams Dial plan forms (see C reating Dial Plans ) use regex strings to perform digit translations. For
these, it is important to understand the role of ( ) in the original digit pattern and the $ elements in the
translations.
( ) brackets are used to group elements in the original match. When performing translations, you can refer to each
pair of brackets using the format $n in the translation. That is, the characters that were matched by the regex
pattern in the first pair of brackets can be represented by $1 in the translation, the second pair of brackets by $2
and so on.
The brackets are numbered in order of the opening ( bracket symbols from left-to-right in the original patterns.
That includes patterns with nested bracket pairs, for example ((\+44)|(044)|(0)) contains $1 [((\
+44)|(044)|(0))], $2 [((\+44)|(044)|(0))] , $3 [((\+44)|(044)|(0)) ] and $4 ((\
+44)|(044)|(0)) ].
Note, in these examples, spaces in the numbers are just present for readability and do not represent actual spaces
in the number strings.

Name Original Number Pattern Translation Translated Number

Add UK 01632 area code 309348 ^(\d{6})$ 01632$1 01632 309348

to any 6 digit numbers

Add US 416 area code 555 0134 ^(\d{7})$ 416$1 416 555 0134
to 7 digit numbers

Change 00 prefix 0044 1632 309348 ^00(.+)$ +1$1 +44 1632 309348
numbers to E.164
format 001 416 555 0134 +1 416 555 0134

Change E.164 format +44 1632 309348 ^\+(.*)$ 00$1 0044 1632 309348
numbers to non-E.164
format +1 416 555 0134 001 416 555 0134

Convert an international 0044 1632 309348 ^(00|\+)44(.+)$ 0$2 01632 309348

number back to a
national number +44 1632 309348 01632 309348

Deploying MS Teams Direct Routing with IP Office Page 111

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 112
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 10.
Troubleshooting

Deploying MS Teams Direct Routing with IP Office Page 113

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
10. Troubleshooting
This section provides some notes for obtaining
114
1. IP Office System Status
115
2. IP Office System Monitor
116
3. ASBC E SIP Tracing
118
4. Monitoring Direct Routing

10.1 IP Office System Status

IP Office System Status can be used to check the status of the MS Teams Line and the users.

MS Teams Line Status

The MS Teams Line is presented similarly to other types of SIP trunks.

User
MS teams IP Office users are presented similarly to simultaneous users.

Deploying MS Teams Direct Routing with IP Office Page 114

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Troubleshooting: IP Office System Status

10.2 IP Office System Monitor

IP Office System Monitor can be used for more detailed troubleshooting.

Connection Status
Supporting MS Teams uses 2 TLS sockets between ASBC E and IP Office. These can be verified in the SIP TC P
Users status menu (Status | SIP TCP User Data...).

If there are not 2 TC P sockets to the ASBC E IP address, the most likely cause is a certificate issue between ASBC E
and IP Office.

User Status
C onfiguration of individual users for MS Teams can be verified using SIP Phone Status menu (Status | SIP
Phone Status).

Tracing Calls
In order to escalating issues, IP Office System Monitor traces are required. These should be generated using the
default filters plus, on the Filters | Trace Options | SIP tab, enable SIP and Verbose. For call related issues,
116
ASBC E traces for the same event/time period are also required, see ASBC E SIP Tracing .

Deploying MS Teams Direct Routing with IP Office Page 115

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
10.3 ASBCE SIP Tracing
This section provides a quick summary of generating and downloading SIP call traces from the ASBC E.
· The processes require you to know the ipcs and root passwords for ASBC E.

· SSH is used to access the ASBC E command line.

· SFTP/SSH file transfer is used to download the trace files.

· For full details of the ASBC E trace command, see

https://documentation.avaya.com/bundle/AdministeringAvayaSBC E_r7.2.2/page/TraceSBC -C ommand.html

Summary
116
1. Tracing Address
117
2. Tracing SIP C alls on the ASBC E
117
3. Downloading Traces from the ASBC E

10.3.1 Tracing Address

First login into EMS web page of SBC to check the IP address of the SBC E_HA (Primary). That address is needed to
an SSH session to it. If the SBC E setup is not a setup with High Availability, then the SSH session is opened to the
SBC E IP address.
In the upper left corner of the web page, choose Device:SBCE and click on Device Management. Note the IP
address of the SBCE_HA(Primary). In the example below, 172.29.25.251.

Deploying MS Teams Direct Routing with IP Office Page 116

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Troubleshooting: ASBCE SIP Tracing
10.3.2 Tracing SIP Calls on the ASBCE
Use the following process to obtain SIP traces from the ASBC E.

Procedure
1. Open an SSH command line session to the SBC E_HA(Primary) IP address.

2. Enter the command login as: ipcs and enter the ipcs user password when requested.
3. Enter the command [ipcs@SBCE ~]$ su - and enter the root password when requested.
4. The cursor should now be prefixed [root@SBCE ~].

5. Enter the command traceSBC

6. Press S to start setting up the trace capture.

7. Using the space and cursor keys, select SIP.

8. Select OK and press enter.The trace for current SIP activities is displayed.

9. Run any call scenarios for which you want traces.

10. When completed, press Q to quit tracing.
11. The screen displays the details of the log file into which the traces have been saved. Note those details.

10.3.3 Downloading Traces from the ASBCE

The files for SIP traces taken by the ASBC E are stored in the directory /archive/log/tracesbc/tracesbc_sip.
Using an SFTP client, those files can be downloaded using the ipcs user name and password.

Deploying MS Teams Direct Routing with IP Office Page 117

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
10.4 Monitoring Direct Routing
The MS Teams admin portal displays a summary of the status of all SBC connections including the ASBC E. To
display these details, after logging in select Voice | Direct Routing. The dashboard shown lists various details for
the SBC connections and indicates if there are any issues such as certificate errors.
For details, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-health-dashboard

Deploying MS Teams Direct Routing with IP Office Page 118

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Chapter 11.
Document History

Deploying MS Teams Direct Routing with IP Office Page 119

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
11. Document History
Date Version Description

10th November 2021 01a First release. Support with IP Office R11.1 FP2.

23rd November 2021 01b Removal of media bypass notes from direct routing.

Only a single MS-Teams line

Deploying MS Teams Direct Routing with IP Office Page 120

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
© 2021 AVAYA All Rights Reserved.

Notice
While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to
make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.

Documentation disclaimer
“ Documentation” means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make
available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original
published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and
employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the ex tent made by End User.

Link disclaimer
Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all
the time and has no control over the availability of the linked pages.

Warranty
Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is available to Avaya customers and other parties through the Avaya Support website:
https://support.avaya.com/helpcenter/getGenericDetails?detailId=C20091120112456651010 under the link “ Warranty & Product Lifecycle” or such successor site as designated by Avaya. Please note that if
You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya.

“ Hosted Service” means a hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service
description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in
connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information.

Hosted Service
THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED
SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER THE LINK “ Avaya Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS
DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING
OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “ YOU” AND “ END USER” ),
AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO
BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE
THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE LIMITED BY THE NUMBER AND TYPE OF
LICENSES PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED SERVICES IF APPLICABLE, YOU MAY HAVE THE
OPPORTUNITY TO USE FLEX LICENSES, WHICH WILL BE INVOICED ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL
PARTNER FOR MORE INFORMATION ABOUT THE LICENSES FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND BILLING
INFORMATION, AND OTHER IMPORTANT INFORMATION REGARDING THE HOSTED SERVICE.

Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, UNDER THE LINK “ AVAYA SOFTWARE LICENSE TERMS (Avaya
Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM
AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE
OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “ YOU” AND “ END USER” ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE (“ AVAYA” ).

Avaya grants You a license within the scope of the license types described below, with the ex ception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order
documentation does not ex pressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted
will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. “ Software” means computer programs in object code, provided by
Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fix es, or modified versions thereto. “ Designated Processor”
means a single stand-alone computing device. “ Server” means a Designated Processor that hosts a software application to be accessed by multiple users. “ Instance” means a single copy of the Software
ex ecuting at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine (“ VM” ) or similar deployment.

License type(s)
Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may
require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic
means established by Avaya specifically for this purpose.

Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the
Software at any given time. A “ Unit” means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account
in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units
may be linked to a specific, identified Server or an Instance of the Software.

Deploying MS Teams Direct Routing with IP Office Page 121

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Database License (DL). End User may install and use each copy or an Instance of the Sof tware on one Serv er or on multiple Serv ers prov ided that each of the
Serv ers on which the Sof tware is installed communicates with no more than one Instance of the same database.

CPU License (CP). End User may install and use each copy or Instance of the Sof tware on a number of Serv ers up to the number indicated in the order
prov ided that the perf ormance capacity of the Serv er(s) does not exceed the perf ormance capacity specif ied f or the Sof tware. End User may not re-install or
operate the Sof tware on Serv er(s) with a larger perf ormance capacity without Av ay a’s prior consent and pay ment of an upgrade f ee.

Named User License (NU). Y ou may : (i) install and use each copy or Instance of the Sof tware on a single Designated Processor or Serv er per authorized Named
User (def ined below); or (ii) install and use each copy or Instance of the Sof tware on a Serv er so long as only authorized Named Users access and use the
Sof tware. “Named User”, means a user or dev ice that has been expressly authorized by Av ay a to access and use the Sof tware. At Av ay a’s sole discretion, a
“Named User” may be, without limitation, designated by name, corporate f unction (e.g., webmaster or helpdesk), an e-mail or v oice mail account in the name of
a person or corporate f unction, or a directory entry in the administrativ e database utilized by the Sof tware that permits one user to interf ace with the Sof tware.

Shrinkwrap License (SR). Y ou may install and use the Sof tware in accordance with the terms and conditions of the applicable license agreements, such as
“shrinkwrap” or “clickthrough” license accompany ing or applicable to the Sof tware (“Shrinkwrap License”).

Heritage Nortel Sof tware

“Heritage Nortel Sof tware” means the sof tware that was acquired by Av ay a as part of its purchase of the Nortel Enterprise Solutions Business in December
2009. The Heritage Nortel Sof tware is the sof tware contained within the list of Heritage Nortel Products located at https://support.av ay a.com/LicenseInf o under
the link “Heritage Nortel Products” or such successor site as designated by Av ay a. For Heritage Nortel Sof tware, Av ay a grants Customer a license to use
Heritage Nortel Sof tware prov ided hereunder solely to the extent of the authorized activ ation or authorized usage lev el, solely f or the purpose specif ied in the
Documentation, and solely as embedded in, f or execution on, or f or communication with Av ay a equipment. Charges f or Heritage Nortel Sof tware may be based
on extent of activ ation or use authorized as specif ied in an order or inv oice.

Copy right
Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Sof tware, Hosted Serv ice, or hardware prov ided
by Av ay a. All content on this site, the documentation, Hosted Serv ice, and the product prov ided by Av ay a including the selection, arrangement and design of
the content is owned either by Av ay a or its licensors and is protected by copy right and other intellectual property laws including the sui generis rights relating to
the protection of databases. Y ou may not modif y , copy , reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part,
including any code and sof tware unless expressly authorized by Av ay a. Unauthorized reproduction, transmission, dissemination, storage, and or use without the
express written consent of Av ay a can be a criminal, as well as a civ il of f ense under the applicable law.

Virtualization
The f ollowing applies if the product is deploy ed on a v irtual machine. Each product has its own ordering code and license ty pes. Note that each Instance of a
product must be separately licensed and ordered. For example, if the end user customer or Av ay a Channel Partner would like to install two Instances of the
same ty pe of products, then two products of that ty pe must be ordered.

Third Party Components

“Third Party Components” mean certain sof tware programs or portions thereof included in the Sof tware or Hosted Serv ice may contain sof tware (including open
source sof tware) distributed under third party agreements (“Third Party Components”), which contain terms regarding the rights to use certain portions of the
Sof tware (“Third Party Terms”). As required, inf ormation regarding distributed Linux OS source code (f or those products that hav e distributed Linux OS source
code) and identif y ing the copy right holders of the Third Party Components and the Third Party Terms that apply is av ailable in the products, Documentation or on
Av ay a’s website at: https://support.av ay a.com/Copy right or such successor site as designated by Av ay a. The open source sof tware license terms prov ided as
Third Party Terms are consistent with the license rights granted in these Sof tware License Terms, and may contain additional rights benef iting Y ou, such as
modif ication and distribution of the open source sof tware. The Third Party Terms shall take precedence ov er these Sof tware License Terms, solely with respect
to the applicable Third Party Components to the extent that these Sof tware License Terms impose greater restrictions on Y ou than the applicable Third Party
Terms.

The f ollowing applies if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE
FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN
COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL
BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Serv ice Prov ider

THE FOLLOWING APPLIES TO AVAY A CHANNEL PARTNER’S HOSTING OF AVAY A PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE
MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED
DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAY A CHANNEL PARTNER’S HOSTING OF AVAY A PRODUCTS MUST BE AUTHORIZED IN
WRITING BY AVAY A AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO
MICROSOFT SOFTWARE OR CODECS, THE AVAY A CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE
AGREEMENTS, AT THE AVAY A CHANNEL PARTNER’S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER.

WITH RESPECT TO CODECS, IF THE AVAY A CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264
CODEC, OR H.265 CODEC, THE AVAY A CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAY A CHANNEL PARTNER IS RESPONSIBLE FOR
ANY AND ALL RELATED FEES AND/OR ROY ALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE
WWW.SIPRO.COM/CONTACT.HTML. THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE
OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC
STANDARD (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR
WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER
USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE
HTTP://WWW.MPEGLA.COM.

Deploying MS Teams Direct Routing with IP Office Page 122

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Compliance with Laws
Customer acknowledges and agrees that it is responsible f or comply ing with any applicable laws and regulations, including, but not limited to laws and regulations
related to call recording, data priv acy , intellectual property , trade secret, f raud, and music perf ormance rights, in the country or territory where the Av ay a
product is used.

Prev enting Toll Fraud

“Toll Fraud” is the unauthorized use of y our telecommunications sy stem by an unauthorized party (f or example, a person who is not a corporate employ ee, agent,
subcontractor, or is not working on y our company 's behalf ). Be aware that there can be a risk of Toll Fraud associated with y our sy stem and that, if Toll Fraud
occurs, it can result in substantial additional charges f or y our telecommunications serv ices.

Av ay a Toll Fraud interv ention

If Y ou suspect that Y ou are being v ictimized by Toll Fraud and Y ou need technical assistance or support, call Technical Serv ice Center Toll Fraud Interv ention
Hotline at +1-800-643-2353 f or the United States and Canada. For additional support telephone numbers, see the Av ay a Support website:
https://support.av ay a.com or such successor site as designated by Av ay a.

Security Vulnerabilities
Inf ormation about Av ay a’s security support policies can be f ound in the Security Policies and Support section of https://support.av ay a.com/security . Suspected
Av ay a product security v ulnerabilities are handled per the Av ay a Product Security Support Flow (https://support.av ay a.com/css/P8/documents/100161515).

Downloading Documentation
For the most current v ersions of Documentation, see the Av ay a Support website: https://support.av ay a.com, or such successor site as designated by Av ay a.

Contact Av ay a Support
See the Av ay a Support website: https://support.av ay a.com f or product or Hosted Serv ice notices and articles, or to report a problem with y our Av ay a product or
Hosted Serv ice. For a list of support telephone numbers and contact addresses, go to the Av ay a Support website: https://support.av ay a.com (or such
successor site as designated by Av ay a), scroll to the bottom of the page, and select Contact Av ay a Support.

Deploying MS Teams Direct Routing with IP Office Page 123

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 124
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Index
Collaboration Service 57
Index Configure
A ASBCE 66
Active Directory Direct Routing 42
App Registration 58 SBC 66
Resync Interval 57 Country
Synchronization 56 Dial Plan 17, 46
Teams Administrator 59 Coverage Delay 36
Add Create
Directory Contact 37 Dial Plan 46
Alternate Name 71 Emergency Routing Policy 52
API Permissions 58 Teams Administrator 59
App Registration 58 Voice Routes 50
Application ID 58 Voice Routing Policy 48
ASBCE 19 D
Add 45
Demoted SBCs 18, 50
Call Routing Profile 90, 92
Dial Mask 52
Certificates 69
Dial Pattern 18, 46, 108
Configuration 66
Voice Route 18, 50
Endpoint Policy 99
Dial Patterns 108
Example schemmatic 67
Dial Plan 46
Flowchart 105
Assign 47
Identity Certficate 71
Dial Plans 17, 46
Interworking 76, 78
Regex strings 108
Media Interface 101
Dial String
Media Rules 96, 97
Emergency 52
Next Hop Address 90, 92
Digit Translations 111
Root Certificate Upload 74
Direct Routing 7, 16
Routing Profile 90, 92
Add SBC 45
Server Flow 102, 104
Callflow 20
Server Interworking 76, 78
Components 17
Signaling Interface 100
Configure 42
SIP Call Routing Profile 90, 92
Dial Plan 17, 46
SIP Media Interface 101
Emergency Routing Policy 19, 52
SIP Server 86, 88
Example Scenario 25
SIP Signaling Interface 100
Flowchart 21
TLS Client 80, 81
Monitor 118
TLS Server 82
Normalization Rules 46
Topology Hiding 94, 95
PSTN Usage 19
Trace 116
Resync Interval 57
Upload identity certificate 75
Synchronization 56
URI Group 90, 91, 92
Translation 46
Version 68
Usage 19
Assign
Verify Domain 44
Dial Plan 47
Voice Routes 18, 50
Emergency Routing Policy 53
Voice Routing Policy 48
Policies 47, 49, 53
Directory
Voice Routing Policy 49
Add user manually 37
Avaya Call 7
Directory Sync 57
Azure Active Directory
DNS
App Registration 58
Verify Domain 22
Resync Interval 57
Domain
Synchronization 56
Verify 22, 44
Teams Administrator 59
Download
C IP Office Root Certificate 70
Call Routing Profile 90, 92 Logs 116
Calling Plans 7 Traces 116
Certificate E
Download IP Office Root Certificate 70
Emergency Calls
Identity Certificate 71
Emergency Policies 19, 52
Root Certificate 70, 74
Emergency Routing Policy 19, 52
Certificates 69
Assign 53
Client ID 58
Create 52
Client secret 58
Enable Heartbeat 86, 88

Deploying MS Teams Direct Routing with IP Office Page 125

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Enable MS Teams Client 36 System Status 114
Endpoint Policy 99 Logging 114, 116
Example Login
ASBCE Schemmatic 67 Web Control 70, 71
Direct Routing 25 M
Regex strings 111 Manager
Extension Add Teams Line 38, 43
Templates 60 Auto Populate 57
User Provisioning Rule 61 MS Teams URI 57
Extension Number Matching
Display 33 Regex syntax 110
Extension Numbers 11 Media Interface 101
Extract Media Rules 96, 97
Private Key 73 Microsoft Calling Plans 7
F Mobile Number 62
Flowchart Monitor 115
ASBCE 105 Monitoring 114
Direct Routing 21 MS Teams Line 19, 38, 43
Dual SBC 29 System Monitor 115
Example scenario 27 System Status 114
Simple scenario 28 MS Teams URI 36
From URI 86, 88 MX Record 22
G N
Generate Name updates 13
Identity Certificate 71 Next Hop Address 90, 92
Global Normalization Rules 46
Dial Plan 17, 46 Number
Group Mobile 62
Assign Policies 47, 49, 53 Number Translations 111
Group ID 58 Numbers 11
H O
Healthy SBCs 18, 50 Object ID 58
Heartbeat 86, 88 Operator Connect 7
Hold status 13 P
I Password
Identity Certificate Special Characters 73
ASBCE 71 Pattern 46
Extract 73 Policies
Upload 75 Assign 47, 49, 53
Interworking Profile 76, 78 Emergency Routing Policy 19, 52
IP Office Voice Routing Policies 18, 48
Add user 36 Voice Routing Policy 48
MS Teams Line 19, 38, 43 Policy
Root Certificate Download 70 Assign 53
IP Office Manager PowerShell 42
Add Teams Line 38, 43 Priority
Auto Populate 57 Voice Route 18, 50
MS Teams URI 57 Private Key 73
IP Office System Monitor 115 PSTN Usage 19
IP Office System Status 114 Synchronization 62
IP Office Web Manager R
User and Extension Templates 60 Regex 18, 108
User Provisioning Rule 61 Digit translations 111
IPO_RootCA.crt 70 Examples 111
K Syntax 110
Key 73 Register
Known Issues 13 Azure Active Directory 58
L Regular Expressions 18, 108
License Resync Interval 57
IP Office user 36 Synchronization 62
Limitations 13 Root Certificate
Line Upload 74
System Monitor 115 Root Certificate Download 70

Deploying MS Teams Direct Routing with IP Office Page 126

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Index
Routing Policies 18, 48 Supported
Routing Policy ASBCE 68
Synchronization 62 Synchronization 56
Routing Profile 90, 92 Teams Administrator 59
S User Identification 62
SBC 19 System Monitor 115
Add 45 System Status 114
Call Routing Profile 90, 92 T
Certificates 69 Teams
Configuration 66 Certificates 69
Endpoint Policy 99 Teams Administrator 59
Example schemmatic 67 Teams Line 19, 38, 43
Flowchart 105 Telephone Number
Interworking 76, 78 Display 33
Media Interface 101 Mobile 62
Media Rules 96, 97 Translation 111
Next Hop Address 90, 92 Telephone Numbers 11
Routing Profile 90, 92 Template
Server Flow 102, 104 User & Extension 60
Server Interworking 76, 78 User Provisioning Rule 61
Signaling Interface 100 TLS Client 80, 81
SIP Call Routing Profile 90, 92 TLS Server 82
SIP Media Interface 101 To URI 86, 88
SIP Server 86, 88 Topology Hiding 94, 95
SIP Signaling Interface 100 Trace 116
TLS Client 80, 81 Translation 18, 46, 108
TLS Server 82 SIP headers 94, 95
Topology Hiding 94, 95 Translations 111
Trace 116 Troubleshooting 114
URI Group 90, 91, 92 TXT Record 22
Verify Domain 22 U
Version 68 Upload
SBCE_ID.crt 73 Identity Certificate 75
SBCE_ID.p12 71 Root Certificate 74
SBCs SIGMA script file 85
Demoted 18, 50 URI
Healthy 18, 50 From/To URI 86, 88
Scenario URI Group 90, 91, 92
Direct Routing Example 25 Usage 19
Schedule Synchronization 62
Synchronization 62 User
Script Add manually 36
SIGMA 83 Assign Policies 47, 49, 53
Upload 85 Coverage Delay 36
Server Flow 102, 104 Dial Plan 17, 46
Server Interworking Profile 76, 78 Enable MS Teams Client 36, 60
SIGMA MS Teams URI 36
Create 83 Profile 36, 60
Upload 85 Templates 60
Signal Manipulation User Provisioning Rule 61
Script 83 User Identification 62
Upload script 85 Users
Signaling Interface 100 System Monitor 115
SIP System Status 114
Trace 116
V
SIP Call Routing Profile 90, 92
SIP Media Interface 101 Verification Depth 80, 81
SIP Server 86, 88 Verify
SIP Signaling Interface 100 SBC 22
Special Characters 73 SBC Domain 44
Start Extension 61 Version
Subject Name ASBCE 68
Alternate Name 71 Voice Routes 18, 50
Subscription 36 Regex strings 108
Voice Routing Policies 18, 48
Deploying MS Teams Direct Routing with IP Office Page 127
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Voice Routing Policy 48
Assign 49
Create 48
Synchronization 62
W
Web Control 70, 71
Web Manager
Add Teams Line 38, 43
Auto Populate 57
MS Teams URI 57
User and Extension Templates 60
User Provisioning Rule 61

Deploying MS Teams Direct Routing with IP Office Page 128

IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
Deploying MS Teams Direct Routing with IP Office Page 129
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com
 Template: 30th May 2018

© 2021 Avaya Inc. All rights reserved.

Deploying MS Teams Direct Routing with IP Office Page 130
IP Office Issue 01b (Tuesday, November 23, 2021)
Comments on this document? infodev@avaya.com