paint-brush
Direct Routing in Dynamics 365 Customer Service: Using Your Own Carrier for PSTN Callsby@thecognitiveservicesninja
514 reads
514 reads

Direct Routing in Dynamics 365 Customer Service: Using Your Own Carrier for PSTN Calls

by Holger ImberyApril 21st, 2023
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

When you create a free Dynamics Customer Service trial, you will get sixty minutes of PSTN Calls (US Toll-free Numbers) If you are in Europe, you must go with the SIP-Trunk integration. Even though direct routing in Azure Communication Services is still in preview, Microsoft fully supports it on a GA level if you use it with Dynamics 365 Customer Service Enterprise**.
featured image - Direct Routing in Dynamics 365 Customer Service: Using Your Own Carrier for PSTN Calls
Holger Imbery HackerNoon profile picture


Using Your Own Carrier as an Alternative to Microsoft’s Calling Plans

When you create a free Dynamics Customer Service trial, you will get sixty minutes of PSTN Calls (US Toll-free Numbers).



After 60 minutes, you can bring your SIP-Trunk via Azure Communication Services or buy a dialing plan via Microsoft. If you are in Europe, you must go with the SIP-Trunk integration. This is a straightforward and menu-based setup. Your SIP-Trunk provider should give you an FQDN of "your" Session Border Controller and a Port. Even though direct routing in Azure Communication Services is still in preview, Microsoft fully supports it on a GA level if you use it with Dynamics 365 Customer Service Enterprise.



Microsofts disclaimer


Configurations steps

Azure Communication Services


First, go to your OmniChannel Admin Center.In the site map, select Phone numbers in General settings.


Click on "Get Started" to start



  • create a new resource
  • select your Azure Subscription
  • select a new resource group or create a new one.
  • Give the new resource a meaningful name.


Create a new resource



Leave the Omnichannel Admin Center window open, open another tab for the Azure Portal, and configure the SBC/Port for Direct Routing.


Create a new Session Border Controller Configuration




enter SBC FQDN and Port




and a number pattern for outbound




Go back to your Omnichannel Admin Center tab and configure your phone numbers.



Add Phone Numbers - part 1




Add Phone Numbers - part 2




Add Phone Numbers - part 3




Add Phone Numbers - part 4




The new phone number will be displayed in the Phone numbers list and is ready for setup. You can now connect it to a voice workstream, configure outbound calling, or even assign it to an agent.



SMS is not supported with direct routing


Carrier Setup

Production Environment

if you are deploying for production, you should go for a carrier with post-paid contracts and a managed SBC Solution on the carrier site. Here you will get an FQDN and Port of the Carrier side, and you are done.

Development Environment

For example, I will describe how to configure a development direct routing connection via TELNYX.

Add a Sip Connection

Create a new sip connection via Voice, SIP Routing, and select MS Teams SBC.

Create new SIP Connection


Assign a number to the Telnyx SBC Connection

You are now required to assign a Number to the Azure Communications Resource connection you created.


  1. If you have not done so, you'll need to purchase a number from Telnyx.
  2. Once you have a number, navigate to the Numbers page of your Telnyx Mission Control Portal and assign your Azure Communications Resource connection to the desired DID, as shown below.


Assign numbers



Add your SIP Connection to your Outbound Voice Profile


Create an Outbound Voice Profile and assign it to the connection you created above.



Assign Outbound Voice Profile


Test the implementation.

Configure some workstreams with the newly created numbers and test inbound and outbound calls.



Also published here.