Checking SIP Messages to Verify the Local Media Optimization Between Teams Client and SBC

Direct Routing, Enterprise Voice, Local Media Optimization, Ribbon, SBC 1000, SBC Edge, Teams, Teams Client / August 3, 2024 August 3, 2024

Why Do You Need to Check SIP Messages

After configuring Direct Routing with Local Media Optimization, you need to check that Local Media Optimization is working correctly

One way to verify that Local Media Optimization is working correctly is to check the headers in the invite SIP message to examine whether the headers contain the correct values.

Tool Used to Capture SIP Messages (LX Tool from Ribbon)

Ribbon SBC Edge family of products sends the logs using the Syslog protocol.

These logs can include SIP messages and other types of logs depending on the level and settings of logging.

To capture the logs from my Ribbon SBC 1000 (a member of the SBC Edge family), I am using the LX Tool from Ribbon to capture the SIP messages

The LX tool captures the logs by acting as a Syslog server to capture the logs.

After capturing the logs, I have used this tool to verify the header of the invite message

Teams Client Detects That It Is External

When Teams Client is inside the internal network, but the Direct Routing with Local Media Optimization is not configured correctly (or the Teams Client is external)

The X-MS-UserLocation header is set to external. In the invite message (as the image below shows)
X-MS-MediaPath is set to the SBC FQDN (this is a single SBC setup)

Note:

When Teams Client is really in the external network, the X-MS-UserLocation is set to external (which is the correct setting)

The image below shows the invite message between Teams Client and Ribbon SBC 1000 captured using the LX tool (Ribbon tool to capture Syslog we discussed above). The headers mentioned above are in a red box.

Teams Client Detects That It Is Internal

When the Teams client is inside the internal and Direct Routing with Local Media Optimization is configured correctly,

The Invite message will have the X-MS-UserLocation header set to internal.
X-MS-UserSite header will appear in the invite message and will be set to the site of the Teams Client
X-MS-MediaPath is set to the SBCs FQDN in the correct order (In the example below, X-MS-MediaPath shows only one SBC, since we have only one SBC in our setup)

The image below shows the invite message between Teams Client and Ribbon SBC 1000 captured using the LX tool. It contains the three headers we mentioned (The headers are in a red box)

Configuring Direct Routing Local Media Optimization for Single-Site and Single SBC (Using Teams Admin Center)

Direct Routing, Enterprise Voice, Local Media Optimization, Teams / July 28, 2024 July 28, 2024

You can use Local Media Optimization with a single site with a single SBC only. This is useful for keeping media traffic inside the internal network (without using Media Bypass). In a previous post, I explained how to configure such a setup using PowerShell. In this post, I will show how to do such configurations using the Teams Admin Center.

My previous post is found on:

Direct Routing Local Media Optimization for Single-Site and Single SBC – Jay’s Lab (jayslab.online)

How Teams Client Determines Whether It Is Going To Use Local Media Optimization

When a Teams Client starts, it will do the following:

It will try to determine if it is external or internal by checking if its public IP is in the list of Trusted IPs
If it is internal, it will try to determine to which site it belongs to based on its subnets
It will communicate with the internal interface of the SBC for the audio of PSTN calls

The last is based on the following note:

Which is from the following Microsoft link:

Configure Local Media Optimization for Direct Routing – Microsoft Teams | Microsoft Learn

Network Topology Page

Configuring Trusted IP, Region, Site, and Subnet is done under the Network Topology page.

Network Topology page can be accessed through Teams Admin Center > Location > Network Topology.

Go to Location > Network topology.

The following shows the Network topology page.

Adding a Trusted IP

Trusted IP is the fixed IP that clients use to access the internet. It is used by Teams to determine if the client is inside the internal network. Local Media Optimization will be utilized by the client when it determines that it is connected to Microsoft servers using a Trusted IP. If you cannot have a fixed IP to access the internet, you will not be able to configure a Trusted IP and in this case you can use Local Media Optimization.

To configure a Trusted IP, on Teams Admin Center go to Location > Network topology and click on Trusted IPs

Click on Add

The “Add trusted IP address” pane will appear on the right side

Add the IP address, network range (number of network bits), and description for this IP. Note that the network range is 32 if it is a single IP (which is more of the cases)

Click on Apply

The newly configured Trusted IP will be under the list of Trusted IPs

Adding and a Network Site

When Teams Client stats and it notices that it is internal (communicating with Teams servers using a Trusted IP), it will try to determine to which sites it belongs to (by checking it is in one of the subnets of that site)

To configure a Trusted IP, on Teams Admin Center go to Location > Network Topology, and click on “Network sites”

Click on “Add”

Type the name for the network site you ar creating

Adding A Region and Linking It to The Site

Each site should belong to a region. A region is a geographical location that contains multiple site. You can associate the site you are creating to a region or add a new region as shown below

To add a new region to the network site, click on “+Add network region”

The “Network regions” pane will appear on the right side

Type the name of the region

Click on “Add”

After that, you will see the name of the newly added region. Click on it to select it (this is the list of all network regions in the environment)

After making sure that you have selected the region, click on “Link” and that will link your site to the region and close the “Network regions” pane

The newly linked network region will be shown under the details of the site

Adding a Subnet to The Site

Each site has subnets that belong to it. When a Teams Client starts and finds out that it is internal (based on Trusted ID), it will try to search to which subnet it belongs, and from that it will determine to which site it belongs

On the site properties page, under “Subnets”, click on “Add subnets”

A pane will appear on the right side that allows you to add a subnet

Add the IP address, network range (number of network bits), and description for this subnet

Click on Apply

The site properties page will show the newly added subnet

Click on “Save” on the Site properties page

You will get back to the main Network topology page and it will show the newly created network site

Teams’ Call Queues and Auto Attendants – Allowing an Auto Attendant to Call an External Number (PSTN Number)

Auto Attendants, Call Queues and Auto Attendants, Teams / September 7, 2023 September 7, 2023

One of the options for a Teams Auto Attendant is to redirect the incoming call to a PSTN number (called external number inside Auto Attendant settings). Based on the menu option the caller has selected.

If a such setting is selected for one or more menu options, you need to assign the “Resource Account” of that Auto Attendant a “Voice Routing Policy” in order to make it able to call the PSTN number mentioned as “External phone number” in the menu option.

How To Setup the Menu Option to Redirect the Call to an External Number (PSTN Number)

In the menu option settings, set the “Redirect to” field to “External phone number” as shown below

Specify the PSTN phone number (which is of course not part of your organization) under the “Destination” fields (you need to select the country code). The number could be a landline, or mobile number and it could be local, national, or even international.

The below shows two different external phone numbers (PSTN numbers).

About The “Voice Routing Policy”

The “Voice Routing Policy” should allow calling the number mentioned. For example, if the number is international, the policy should allow calling that international number (by containing a usage that allows that number pattern). It should specify which SBC Gateway should be used (the usage should be associated with a route that uses that SBC Gateway)

The Voice Policy

The Route Details Containing the Number Pattern and SBC Gateway

Below are the Route details in the “Admin Centre” and it shows the Number Pattern and the SBC Gateway associated with it

The Route Details Containing the PSTN Usage Associated with It

I have scrolled down to the Route details to show the PSTN Usage

How To Assign The “Voice Routing Policy”

Go to the “Resource Accounts” page and click on the Resource Account to Edit it

Select the “Voice Routing Policy” and click on save.

Teams’ Call Queues and Auto Attendants – Adding an operator to the Auto Attendant

Auto Attendants, Call Queues and Auto Attendants, Direct Routing, Operator, Teams / August 19, 2023 August 19, 2023

In this article, I am improving my Auto Attendant by adding an option to reach the operator. The operator in my case is accessed by clicking on 0 on the dial pad when calling the Auto Attendant.

My operator is a Teams user (Person in organization) named User5. But you have the option to send the call to another Auto Attendant or Call Queue (Voice app). You can also send the call to an external PSTN number.

Go to

Teams Admin Center > Auto attendants > Click on the Auto Attendant that you want to modify. This will open the Auto Attendant Wizard

Part 1 – Adding an operator

On the “General Info” page, you will see the “Operator (optional)” setting

Open the box and select “Person in organization”

It will give you a place to “Search by display name” filed

Type the display name or at least the first 3 letters, and select (click) the user name

The username will be selected and will be designated as the operator

Now we can use the operator in the Call flow for this Auto Attendant as I am showing in the next part.

Part 2 – Making the operator a Call Flow Destination (reached when clicking)

Go to the “Call flow” page (on the settings of the Auto Attendant you are modifying)

Modify the Greeting Message of the Auto Attendant to let the caller hear the option about the operator

Click on “Assign a dial key”. This will add a new “dial key” option the caller can dial

The default option for the new key is Operator and it will automatically configure the call to be redirected to User5 (which is the operator that we have selected in the previous step)

Select the 0 as the dial key

Click on the Submit button to save the changes

Teams’ Call Queues and Auto Attendants – Creating an Auto Attendant

Auto Attendants, Call Queues and Auto Attendants, Direct Routing, Teams / August 19, 2023 August 19, 2023

What Is an Auto Attendant

A person can call this an auto attendant (via Teams client or a PSTN number)
The caller can hear a menu and set of messages to direct him/her to which key on the dial pad to press
Based on the key the caller pressed on the dial pad of their phone (or Team client), the callers will reach a call queue, a person, or an operator
The callers will reach their destination quickly, without relying on a human operator to handle incoming calls.

About The Steps Below

In the steps below, I will show how to link a new auto attendant with 2 call queues (we created 2 call queues in the previous steps)
The auto attendant will ask the caller to press 1 for Sales or press 2 for Support
Based on the caller selection (key pressed on the dial pad of the caller’s phone), it will forward the call to the corresponding Call Queue (Sales or Support)
Each of the call queues that I created earlier will forward the call to a specific channel in a specific team
This will form a simple IVR (Interactive Voice Response)
Although this IVR is simple, it will demonstrate how to create a functional IVR that can be easily improved and expanded

Auto Attendants Pane

Starting Auto Attendant Wizard

On Teams Admin Center, expand the “Voice” menu and select “Auto attendants”

To add a new “Auto Attendant” click on Add

The “Add a call queue” wizard will appear, and it will start with the General info page

General Info Page

On the “General info page” Type the name of the Call Queue. For me, the name is “Main Auto Attendant” (there is no other Auto Attendant, I have just called it “Main” since it will be the first thing the PSTN call will be routed to)

On this page, I have selected my time zone (This is useful for the “Set business hours” page on “Advanced settings”)

Scroll down until you reach “Language”. This is where you specify the language that will be used for the automatically generated voice messages. I have set my language to “English”

Click on the “Next” button

Call Flow Page

The next page is “Call Flow”

Under “Greeting options”, I have selected “Add a greeting message”. And I have typed a simple message “Welcome to our company”

When the call gets connected, the calling user will hear this greeting message

For “Call routing options”, scroll down to see the details and select “Play menu option” to put your voice menu options and actions

For my menu, I have added a greeting message (this message to inform the caller which phone key should be pressed)

Below images show my “greeting message” which is “Select 1 for Sales or 2 for Support”

Under “Set menu options”, click on “Assign a dial key”

An empty menu entry will be added

In the new menu entry/option, select the key the caller will click to select this menu option

I am selecting 1 for the first entry

The following shows that key 1 is selected

Click the menu for “Redirect to”

Select “Voice app” (since we want to redirect the call to the call queue that was created earlier)

The following shows “Redirect to” is set to “Voice app” which means it will redirect the call to another Call Queue or Auto Attendant

Under “Destination”, I am searching for the “Sales Call Queue” by typing the word “sale”

I am selecting the “Sales Call Queue” that I have created earlier

This menu entry/option is completed

Using similar steps, I have added a menu entry/option for “Support Call Queue” when the caller clicks on “2” on his/her dial pad

Under “Directory search”, I am selecting “None”. Since I don’t need the caller to call internal users of the organization

Adding a Resource Account to Our Auto Attendant

For simplicity, I am keeping “Advance setting (optional)” as default and I kept clicking next until I reached the “Resource account” page (the last page).

To add a Resource account, click on the “Add” button

The “Add account” pane will appear on the right side, I searched and added the resource account for this auto attendant as the image below shows

Click on “Add” at the bottom of the pane

When you back to the “Resource accounts” page, you will see the resource account(s) that you have added

Submitting the changes

Click on the Submit button at the bottom of the Wizard to save the changes of the new auto attendant

The auto attendant will be created, and it will be listed on the main page “Auto attendants”

Teams’ Call Queues and Auto Attendants – Creating a Call Queue

Call Queue, Call Queues and Auto Attendants, Direct Routing, Teams / August 19, 2023 August 19, 2023

What is Call Queue

Call queues route incoming calls to specific Teams users (Teams, Groups, or Users). Call queues control how the call is routed and distributed to Teams users (agents).

The following steps show how to create a call queue:

It redirects the call to an Office 365 Team
Members of that team are going to be the agents
The agent that has been ideal for the longest time will have the call

Call Queues Pane

On Teams Admin Center, expand the “Voice” menu and select “Call queues”

Adding a New Call Queue

To add a new “Call Queue” click on Add

General Info Page

The “Add a call queue” wizard will appear, and it will start with the General info page

Type the name of the Call Queue. For me, the name is “Sales Call Queue”

Adding a Resource Account to The Call Queue

Under “Resource accounts”, click on the “Add” button

The “Add account” pane will appear on the right side

In the search box, search for the name of the resource account that you created earlier. For me, I am typing “Sales Call Queue”. (You can type at least 3 letters to search)

It will show all the resource accounts display name matches for the search. Hover the mouse pointer over the resource account name and an “Add” button will appear next to the resource account Click on it

The added resource account will be listed (you can add more accounts if your setup needs that)

Click on “Add” bottom of the pane

When you back to the “General Info”, you will see the resource account(s) that you have added

Scroll down until you reach “Language”. This is where you specify the language that will be used for the automatically generated voice messages

Search and select the language

The below image shows my selection of language is “English (United States)”

Greeting and Music Page

Click on Next, and you will be on the “Greeting and music page. I will keep it as it is for simplicity. Then, click on “Next” to reach the “Call answering” page

Call Answering Page

Here, you select who will handle the call. you can select a channel of a team, or you can select specific users and groups

For me, I kept the “Choose a team” option selected, and I clicked on “Add a channel” (you need to select a Team, then select the channel from the list of channels for that Teams)

The “Add a channel” pane will be shown on the right side

First, you need to select the team

Then, select a channel from that team

For me, I have selected the default “General” channel of the team named Sales

Click on Apply

The “Call answering” page will now show the selected channel and to which team that channel belongs to

Click on Next

Agent Selection Page

An agent is a member of the Teams that we have selected in the previous step.

On the “Agent selection” page, I am selecting the “Longest idle” method of routing. This way, the agent that has been ideal for the longest time will have the call forwarded to him/her. Note that

I am keeping the remaining of this page as default and I am clicking on the “Next” button

Call Overflow Handling Page

I am keeping the “Maximum calls in the queue” as 50, and if more calls are there, the calls will be disconnected

Important note:

In case you are using Teams Direct Routing, you need to keep some channels to regular Teams Direct Routing calls, you achieve this by reducing the “Maximum number of calls in the queue” so that you will not let your Call Queues consume the full PSTN connections (PRI or SIP Trunking),

Keeping a high number of calls waiting in a call queue might consume your channels (channels of the PRI or the SIP Trunking). And that might make you not able to do outgoing PSTN calls or receive incoming PSTN calls on Teams

If you have multiple call queues, you need to watch for the total sum of all “Maximum number of calls in the queue” of the call queues.

Call Timeout Handling Page

This is the last page of the wizard. Here you will specify how long the caller will be waiting for an agent to answer the call. If the call exceeds this wait time, the call will be disconnected, or you can select to redirect the call

I am keeping this number as the default 20 minutes.

Submitting the changes

After completing the wizard and you are fine with the settings, you can click on the “Submit” button

The call queue will be created, and it will be listed on the main page “Call queues”

Support Call Queue

For my setup, I am creating another call queue called “Support Call Queue”. The Support Call Queue has the exact settings, except that it routes the calls to the “Support” team (the setting is on the “Call Answering” page)

Teams’ Call Queues and Auto Attendants – Assigning the License to the Resource Account

Auto Attendants, Call Queue, Call Queues and Auto Attendants, Direct Routing, Teams / August 18, 2023 August 18, 2023

Why do we need to assign this license?

Each resource account requires a license to make it work with auto attendants and call queues. Instead of using a paid regular account, a special type of license named “Microsoft Teams Phone Resource Account” is created for this purpose and you can acquire it for free (explain in a previous article in this series)

The following steps show how to assign this license to the Resource Account (it is simply like assigning any other type of license)

Go to the “Microsoft 365 admin center”

Expand “Users”

Select “Active users”

You will find the resource accounts that you have created in the “Teams Admin Center” listed here with the rest of the users. You might need to search the account under “Filter”

Click on the resource account

The pane that shows the detail pane of the account will appear on the right side

A screenshot of a computer

Description automatically generated

Click on the “License and apps” tab

The list of the licenses will be shown. Among these licenses, you will see the “Microsoft Teams Phone Resource Account” license (which we acquired in a previous step in this series)

Select the “Microsoft Teams Phone Resource Account”

Click on “Save changes”

Teams’ Call Queues and Auto Attendants – Creating Resource Accounts

Auto Attendants, Call Queue, Call Queues and Auto Attendants, Direct Routing, Teams / August 18, 2023 August 18, 2023

What is Resource Account:

Each Auto Attendant and Call Queue requires a Resource Account.
Without a Resource Account, you will not be able to create an Auto Attendant or a Call Queue
You can assign a phone number to a Resource Account. When you call that number, you will reach the Auto Attendant and Call Queue associated with that Resource Account
You can create a Resource Account in Teams Admin Center
Resource Account will be listed in Microsoft 365 Admin Center like any other type of accounts
You assign the needed special license to the Resource Account using Microsoft 365 Admin Center the same way you assign a license to any regular account. The license name is “Microsoft Teams Phone Resource Account”

Creating a Resource Account for the “Sales Call Queue”

The following are the steps to create a resource account

On Teams Admin Center, expand the “Voice” menu

Select “Resource accounts”

The “Resource accounts” page will appear

Click on Add

The “Add resource account” pane appears on the right side of the browser

The following image shows an empty “Add resource account” pane

Fill in the following fields:

Display Name

The display name makes the account easier to be identified and also it will appear in the “Microsoft 365 Admin Center”

Username

And also type the Username. This username will appear in Microsoft 365 Admin Center where you can assign the “Microsoft Teams Phone Resource Account” license to it.

Resource account type

Here, you select if the account is going to be used for “Auto attendant” or for “Call queue”

Click on Save to save the changes and close the “Add resource account” pane

The following image shows the “Sales Call Queue” on the main page of “Resource accounts”

Resource Account for “Support Call Queue”

In the same way, I am adding the resource account for the “Support Call Queue”

Resource Account for “Main Auto Attendant”

And also, I am adding the resource account for “Main Auto Attendant”

The Newly Created Accounts Listed Under The Resource Accounts Page

The following image shows all the 3 resource accounts that we are going to use

Teams’ Call Queues and Auto Attendants – Obtaining the Resource Account License

Auto Attendants, Call Queue, Call Queues and Auto Attendants, Direct Routing, Teams / August 18, 2023 August 18, 2023

What Is Resource Account

Each auto attendant or call queue always needs a resource account that is assigned to it.

To call an auto attendant or a call queue using PSTN, The Resource account should be assigned a Teams telephone number. This telephone number could be a Direct Routing number or it could be a Microsoft Phone number.

What Is Resource Account License

Each resource account requires a license to make it work with auto attendants or call queues. The name of this license is “Microsoft Teams Phone Resource Account license”. This license is free and costs nothing. It is intended to be used only for Resource Accounts. After acquiring this license, you can assign it to a resource account, and it will appear as Microsoft Teams Phone Resource Account under licenses.

The below steps show how to obtain this license

Obtaining The Resource Account License

Open “Microsoft 365 admin center”

Go to

Microsoft 365 admin center > Billing > Purchase services

Under the “Search all products categories” box, search for “resource account”

Wait for the results to appear

You will see “Microsoft Teams Phone Resource Account” among the results

Click on the “Details” button of “Microsoft Teams Phone Resource Account”

Under “Select license quantity”, put the number of licenses that you need (which is the number of your Resource Accounts that you are planning to have)

Notice that these licenses cost nothing

I have selected 5 under “Select license quantity”

I am scrolling down to see more details as the image below shows

Click on the “Buy” button to acquire this special license

The Checkout page will appear

Scroll down to “Billed to”

And select “Invoice” to avoid putting credit card information

Fill up the information (name and address)

Click on the “Save” button

The Summary section will appear on the right side of the screen

Under Summary, click on the “Place Order” button

The order will be processed

When it is done, you will get the “You’re all set!” message

Now you can assign these licenses to your Resource Account

SIP-TLS Server Handshake Failure/SIP-TLS Handshake Negotiation Start Failure warnings/errors on Monitor Tab of SBC Edge

Access Control List (ACL), Direct Routing, Direct Routing, Enterprise Voice, Ribbon, SBC, SBC 1000, SBC 2000, SBC Edge, SWe Lite / December 10, 2022 August 24, 2023

If you are using Ribbon SBC Edge (SBC 1000 / SBC 2000 / SBC SWe Lite) that is integrated with Teams Direct Routing, you noticed on your SBC Edge repeated warnings/errors under the Alarm View on the Monitor tab like the following:

SIP-TLS Server Handshake Failure

SIP-TLS Handshake Negotiation Start Failure

You might have different causes of the alarm (the cause is inside the description of the alarm)

Reason for these Warnings and Errors:

The reason for these warnings and errors is that there are many machines on the net that keeps scanning SIP servers on well know SIP ports trying to hack them to make calls.

To avoid these machines from scanning your SBC, you need to limit SIP communication only with Microsoft Teams server (SIP Proxy) which consists of these two ranges (52.112.0.0/14 and 52.120.0.0/14) as explained in the link:

https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan-media-bypass

Under the section “SIP Signaling: Ports”

The following is from the above link

Using Firewall

If your SBC is behind a firewall, you can simply configure the firewall to limit SIP communication to only (52.112.0.0/14 and 52.120.0.0/14)

Using SBC Edge Access Control List (ACL)

Another method is to utilize applying Access Control List (ACL) on the “Logical Interface” of SBC that is connected to the internet.

You can create your own ACL or you can utilize the existing ACL created by running “Easy Config Wizard” and selecting Teams as a scenario

Notes About Using Access Control List (ACL):

You need to allow HTTPS allowed on the interface to control the SBC if you have the same interface for both managing the SBC and for SIP and Media communication
If you configured allowing HTTPS incorrectly in the ACL, you will lose access to the Web Interface of the SBC
It is better to have an additional interface enabled with the correct IP and connected to the network. This would help in case you have applied an ACL that is incorrectly not allowing HTTPS. This way, you will not end up with your SBC Web Interface inaccessible
In the case of SBC 2000, the Admin Port is usually configured by default and has the default IP of 192.168.128.2.
Do a backup of your SBC before applying changes