Dynamic emergency calling assists in routing calls and notifying security personnel during an emergency scenario based on the location of the Teams Client. Earlier this setup was working on Microsoft Calling plan and Direct Routing. Now with Operator connect being public GA setting up a emergency calling is a mandatory prerequisite before enabling the operator connect on the Teams Admin Center.
The dynamic emergency calling works completely with the help of the Location information service. The Location Information Service (LIS) delivers geodetic (latitude/longitude) or civic address location information. The LIS is used by emergency services to make location-based call routing decisions and to properly locate callers for dispatch. LIS addresses the intermediate solution for providing e911 service for users of VoIP telephony.
Microsoft Teams uses this same LIS based on the Network Topology Information. This is collected from the Teams Client location data which works based upon two information
- Network Settings
- Location Information Service Configuration
Continuing the previous article now we’ll go through the next steps that is required to complete the enterprise voice configuration. Now we have setup the AudioCodes SBC , configured SIP trunk from Office 365 to SBC the next step is to setup PSTN trunk from the SBC to the Telephony Provider.
If there is already an existing setup then this part is not required because the configuration will be already present in that case. In this article we will have a look at how to configure the PSTN Trunk for a new telephony provider.
There are multiple PSTN Sip Providers that we can use to complete this configuration. In our case we have chosen Telnyx as the PSTN Sip Provider for this demo purpose. They provide us the flexibility to purchase numbers as low as 10 USD and hence have chosen this for our testing.
Over here we are not going to deep dive much into Telnyx configuration since our task is to create a PSTN Trunk between them and our SBC. So we will go through only the steps that is required to complete the Direct Routing Configuration.
The moment when we subscribe with Telnyx they provide an advance credit of 10 USD and a portal like below. As per the Telnyx documentation we need to create a new SIP connection to our SBC in the below section where we could see they have a SIP connection with their backend system as a default setup.
Continuing the previous article there are few more steps to complete the configuration of the Direct Routing with the office 365 tenant and in this article we will run through those steps.
Currently the SBC is up and running configured with the certificates and required SBC DNS records now the next step is to enable the direct routing. Well there are two options to enable the Direct Routing via skype online powershell session or via the Microsoft Teams Admin center. In our example we will try to enable them via the Teams admin center.
Before doing this make sure to meet the network prerequisite that is required for Direct Routing and have written an article about the same almost a year ago.
Login to the admin portal with the appropriate credentials.
Enter the DNS name of the SBC that was configured in our case its sbc.nl.exchangequery.com
Subsequently we must add all the required information over here. One important point to note over here is that the SIP signaling port that is present by default is port 5067. The Direct Routing SIP Trunk can be configured only by using a TLS connection. We can choose the SIP port any port of our choice. If we try to configure the port 5060 it will not work since the TCP connectivity is not supported due to security reasons.
Microsoft have been providing us the option bring your own sip trunk for enabling the enterprise voice functionality. With Microsoft Teams Direct Routing we can provide the phone system to Teams users ,connect the SIP Trunks and use the local telecommunications provider. This option provides most of the customers for an easy transition to Microsoft Teams in parallel by utilizing the existing infrastructure and moving the users to the new system.
In order to leverage this functionality we need to setup certified session border controllers. Previously there is an article written which can be referred to check the readiness and steps that is required to configure Direct Routing in Microsoft Teams.
In this article series we will see on setting up audiocodes session border controller that will help in configuring the Direct Routing.
There are multiple ways to achieve this and we have an option to configure this from the Azure Market place. We will see on configuring this from the Azure Market Place.
First prerequisite is we need a valid azure subscription. Login to Azure and search in the Azure Market Place for Audio Codes.