Home
Microsoft

Direct Routing NOW in Public Preview

EDIT: we have announced GA for Direct Routing - please continue the conversation there.

 

Today, May 15, 2018, we are announcing that Microsoft Phone System Direct Routing is in public preview. If your country is supported by Teams and Phone System you can start a self-managed preview of Direct Routing now.

 

Back in December of last year, we began offering calling in Teams by turning on Microsoft Calling Plans. This enabled customers to begin exploring voice in Teams in 9 different countries. Today Direct Routing takes the next big step by allowing customers to connect voice trunks to Microsoft Teams in many more countries around the world.

direct routing - alternate diagram.png

 

 

Customers will need to focus on these key areas for a successful self-managed preview:

 

OFFICE 365. Ensure your Office 365 tenant is ready for a Direct Routing preview by having Teams working and ready for use. Begin piloting Teams today prior to getting the Direct Routing Preview started. You will also need to have Phone System in your Tenant. Phone System comes with E5 or can be acquired separately.

 

SESSION BORDER CONTROLLERS (SBC). Arrange to work with one of our partners who are being certified for Direct Routing. Due to the criticality of Enterprise Voice, Microsoft has been working closely with these partners to ensure compatibility. These vendors are in process and plan to have their SBC certification complete at the time of General Availability. Please review the content for Direct Routing from AudioCodes, Ribbon, and ThinkTel to understand their offers and start a pilot with them.

 

VOICE TRUNKS. Reach out to your telecom provider to arrange for new voice trunks or plan on using existing capacity from those provider(s).

 

GETTING STARTED. if you are new to Teams, please review our practical starting guidance.  It helps to be comfortable with Teams before proceeding to Calling. Next - review these two articles:  Plan Direct Routing and Configure Direct Routing. We have also recorded a deeper dive on Direct Routing to further aid in your understanding.

 

After reviewing this content, you will know if you are ready to begin with your resources. However, If you would like more assistance, please reach out to our partners referenced above. Either way, we look forward to you starting with Direct Routing and Calling in Teams.

26 Comments
Occasional Contributor

Great news! As an PSTN provider we have been working closely with Ribbon to deliver Direct Routing to #MicrosoftTeams for a while now. If you are based in Europe please feel free to reach out and I will help you get started with telephony in Teams.

Frequent Contributor

Please let us know which 9 countries DR is currently in Public Preview? 

@thet naing the Direct Routing available in worldwide (not only in 9 countries) It is available in any country where Microsoft sells Office 365

Frequent Contributor

@Nikolay Muravlyannikov Thank you, noted. 

Occasional Contributor

I assume you would sign-up for the public preview at www.skypepreview.com but I can’t see any Direct Routing product that you can sign up for. Is there anyone else who can see it there?

Frequent Contributor

@Nikolay Muravlyannikov

 

I am reading this article

https://docs.microsoft.com/en-us/SkypeForBusiness/skype-for-business-hybrid-solutions/plan-your-phon...

 

Feedback:

 

  1. Please check there is no IP range of the Media Processors in the article? Are they the same as of SIP Signalling? 
  2. The port is 49152 or 49 and 152? Because there is a space between? 

Media traffic: IP addresses and port ranges

The media traffic flows to and from a separate service in the Microsoft Cloud. The IP range of the Media Processors is shown in the following table:

Traffic From To Source port Destination port

UDP/SRTPMedia ProcessorSBC49 152 – 53 247Defined on the SBC
UDP/SRTPSBCMedia ProcessorDefined on the SBC49 152 – 53 247
 

Hi @Mårten Hellebro you do not need to sign up. The commands to configure are available in the PowerShell. The  documentation published, links in the blog. Just read the documentation, watch the training and configure. Let me know if you need any help.

Hi @thet naing for the Media processors we do not have the static IPs yet, will be available later this month. We will update the article. Currently the Media can flow from any IP form the Azure Datacenter  IP range https://www.microsoft.com/en-us/download/details.aspx?id=41653.

The ports are 49152 to 53247

 

Occasional Visitor

Hello.

 

The diagram above shows the path from "Phone System" to "PSTN Provider" going *through* Contoso's premise:

[Contoso's PSTN Provider] <----> [Contoso's Premise] <----> [Phone System] <----> [Contoso Teams user]


Will it be possible to create a Direct Routing path from "Phone System" *directly* to "PSTN Provider", therefore bypassing the need to back haul voice trunks / voice traffic through customer's premise for trunking, as follows? 

[Contoso's PSTN Provider] <----> [Phone System] <----> [Contoso Teams user] 

 

Microsoft

@Rafael Benitez - thanks for the question. This blog discusses what architecture(s) are available for the public preview. As we get to GA, we will have more information on other Direct Routing options. 

Occasional Visitor

Just to clarify, will Direct Routing be supported in Skype for Business Online or is it just for Teams?

Occasional Contributor

@Martin Venø Jensen Direct Routing is just for Teams. 

Occasional Visitor

@Martin Venø Jensen just more context on what @Mårten Hellebro said:

 

"It’s important to note that Direct Routing is designed to work with Microsoft Teams. Customers using Skype for Business Online should continue to use Cloud Connector Edition (CCE) or connect via or a on-premises SFB Pool for their SIP trunk connection needs."   Source: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Direct-Routing-enables-new-enterprise-vo...
 
IMO not technically difficult to extend SIP Trunking to SFBO, but it seems that Microsoft wants to (a) encourage the transition to Teams, and (b) reduce dev effort on SFBO since it will eventually be decommed. 
Occasional Visitor

@Paul Cannon, in the diagram in the blog the line from "Phone System" to "Contoso" is labeled "internet".  Will other BYO transport options be possible for customers that want to ensure performance and availability?  For instance, aside from "internet" access, would a private networking arrangement (e.g. private MPLS service from any Telco into O365) also be supported by Microsoft?

Occasional Contributor

@Rafael Benitez I don’t see anything stopping you from using Azure ExpressRoute from customer to Office 365. And then a MPLS between customer and PSTN provider. And while you’re at it, why not Azure ExpressRoute from PSTN provider to Office 365. That should do it. 😊

Thank @Mårten Hellebro@Martin Venø Jensen for a private connection between the SBC and Microsoft we support Azure Express Route, you can also use a private connection between the telco trunk and the SBC

Regular Visitor

We are testing this internally now with a few users on a Sonus SBC 1000 - everything is working really well so far, we just need to get some of the routing working between our legacy PBX and our Teams test users - but this is an SBC configuration and not a Teams one.

 

One thing that has come up during the testing relates to your calling features like call queues and auto attendants - will we be able to hook those up to numbers on our SIP trunks, or will be we required to get numbers from Microsoft / port them in?

Occasional Contributor
With CCE you could translate an on-prem DDI to a hunt group's SIP address but I don't think this is doable with direct routing.
Contributor

Can you have multiple SIP trunks coming into an SBC using Direct Routing?

Regular Visitor

I can't see why not @Bradley Weir - it is still a single SIP trunk to Teams. So if you have multiple types of PSTN (SIP, ISDN, Analog) all terminated on the SBC, you could route them all to Teams.

Regular Visitor

I have a support case open at the moment but am unsure if that's the correct place to send issues while this is in preview. Is Teams meant to match CLIs in the call log to GAL entries? Our GAL is populated with people's office and mobile numbers in E.164 format. When I receive a missed call email it is successfully matching to a name, but my call history in Teams is just a list of numbers.

Hi Jonny Marlborough thanks, we will triage the bug. 

New Contributor

Does anyone know if there's a way to implement Direct Route in India while remaining in compliance with local laws that restrict bridging PSTN and IP calls? Are there any telcos in India that will be providing Direct Route as a product offering since it's not legal to do this on prem?

Hi @Jimmy Grewal this requires a feature which in on-premises version of Skype for Business we call Location Based Routing. It is not part of Microsoft Cloud offer yet


New Contributor

Hi @Nikolay Muravlyannikov, thanks for the quick reply. Will Location Based Routing ever be available via the MSFT Cloud?

@Jimmy Grewal I don't have such information.