Direct Routing explained from an infrastructure point of view


I wrote a blogpost recently with the goal to explain the basic around Direct Routing from an infrastructure point of view. I learned a lot writing it and here are my key takeaways


  • Direct Routing will provide voice only for users homed in Microsoft Teams
    • You still need to use CCE or Skype for Business Server hybrid to provide PSTN connectivity for Skype for Business Online users
  • Wildcard certificates are supported
  • Clear understanding of ports, protocols and firewall directions
    • You can choose any port for SIP signalling on the SBC side
    • The SIP Proxy in Microsoft datacenter always uses port 5061 for SIP signalling

Read the full article on Direct Routing explained on my blog:


What are your key takeaways when learning about Microsoft Teams Direct Routing?

1 Reply

@Ståle Hansen Hi, and thanks for the information, but I have some questions before start, that I want to be sure and I´m not having luck to found clear information. I have  couple of costumer with a Skype for Business Server Implementation with local PSTN and we are planning a Pilot with Phone system in Teams.

1. If we have a Skype for Business Server implementation and the customer don´t has an actual certificated SBC like Sangoma for example, still can use intertrunk routing, do you know if the SBC can enable direct routing for Teams? 

2. Or the customer needs to invest in a certificated SBC?


Thanks in advance