47 thoughts on “Configure Direct Trunking to Microsoft Teams with Ribbon SBC Edge”

1. Great Article Damien !!

   Reply

2. Very good articole Damien

   Reply

3. Pingback: Configure Direct Trunking to Microsoft Teams with Ribbon SBC Edge – dmunified – JC's Blog-O-Gibberish

4. Pingback: Microsoft Teams Direct Routing explained – msunified.net

5. G-Day Damien, Great Article. I would say you had a few runs at this. I have rolled up my sleeves already. Your blogs is a great reference point. Keep up the good work

   Reply

6. Hi Damien,

   thanks this is useful – quick question…actually on O365 rather than the SBC! When I try and execute the Set-CsUser command it fails saying that the parameter ‘OnPremLineURI’ doesn’t exist (error is: A parameter cannot be found that matches parameter name ‘OnPremLineURI’.). If I check using the command ‘Get-CsOnlineUser’ I can see that parm is there and correctly configured but not sure why I cannot set it myself (interesting, there is also a parameter “OnPremLineURIManuallySet” which is set to False for me).

   Not sure if this is causing my issue – basically I never see the ‘Calls’ icon in my Teams client regardless of what InterOp policy or Upgrade mode I set. Would appreciate any suggestions!!

   Reply

   • Hi Antony,

     Checking my cloud account, “OnPremLineURIManuallySet” is set to true, and cloud voice was configured with the following:

     Set-CsUser -Identity “damien.margaritis@insynctechnology.com.au” -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI “tel:+61311111111;ext=111”

     Are you syncing any attributes from on-prem? Old on-premises msRTCSIP=* attributes? This will cause issues for you

     Reply

     • Dear Damien…

       Your have a great blog with very useful informations, thanks for sharing the informations with us!

       I enabled a Teams room system with Enterprise voice and assigned a wrong tel. number, now I’m not able to change the tel. number because the system says “Can not update OnPremLineURI as the user has dirsynced onpremise LineURI”.

       I see that “OnPremLineURIManuallySet” is set to false! We never had a Onpremise Infrastructure. we always were in the cloud, so we do not have msRTCP attributes in our AD!

       Do you know how to change “OnPremLineURIManuallySet” to true?

       Thank you for a feedback and kind regards,
       Walter

     • Hi Walter,

       If you first gave a user account a phone number, then setup as a meeting room (Enable-CsMeetingRoom), you’ll need to disable as a meeting room to then change the phone number. In my experience, I’ve found it less hassle to disable the meeting room, remove Skype for Business\Teams\Phone System license, wait for user to disappear in SfB and Teams admin centres, then add licenses back and configure again.

       Let me know if this works?

       Damien

     • Hi Damien…

       Thanks for your reply!
       I already tried this, but it does not work, always the error “Can not update OnPremLineURI as the user has dirsynced onpremise LineURI” 😦
       Anyway, I’m now in contact with the Microsoft support, I’ll let know about the outcome!

       Thanks and have a nice day!
       Walter

7. Pingback: Microsoft Teams Direct Routing Now Generally Available | dmunified

8. Hi Damian,

   Thanks this really helped me. But i keep getting stuck at one point.
   When i try to assign the routing policy to the user. It keep giving me the following error:

   Policy “Australia” is not a user policy. You can assign only a user policy to a specific user.
   + CategoryInfo : InvalidOperation: (CN=ac3ddb74-e7a…c1e001,DC=local:OCSADUserOrAppContact) [Grant-CsOnlineVoiceRoutingPolicy], ManagementException
   + FullyQualifiedErrorId : GrantPolicy,Microsoft.Rtc.Management.Xds.GrantOnlineVoiceRoutingPolicyCmdlet
   + PSComputerName : admin1e.online.lync.com

   And i just cant get any further than this. The rest all succeeded. But i cant get that policy on my user.

   Reply

   • Did you run this?

     New-CsOnlineVoiceRoutingPolicy “Australia” -OnlinePstnUsages “Australia”

     Check you haven’t missed any steps when creating the user level policy

     Reply

9. Thanks Damien

   That has to be the most concise and well-worded description of Teams and Direct Routing I’ve found – thank you!

   I have an issue where the Calls button is not added to the Teams interface. Have you experienced this before?
   The user has E3 + Phone System, and shows “true” for EnterpriseVoiceEnabled + HostedVoiceMail and has a number and routing policy assigned.

   Many thanks,
   Jon

   Reply

   • hmmm – cancel that!!!
     the Calls button just turned up. I did nothing to the config, just had Teams running in the background whilst I did other stuff.
     grrrrr….

     cheers,
     Jon

     Reply

10. Hi Damien,

    If you use Teams DR, how did you manage existing phone number if organization want to move them to the cloud.
    Do we need to create a port phone number request from Office 365 or directly from the Telco provider ?

    Thanks

    Reply

    • Hi Jordan,

      With direct routing, PSTN connectivity is delivered via an SBC with a SIP trunk out of band of the Microsoft Office 365 environment. If you wanted to move a number range from this SIP Trunk to a Microsoft Calling Plan (Telstra Calling Plan in Australia), you would need to request a port from Carrier/Microsoft.

      Reply

      • Hi,

        Ok thanks and how it works for service numbers versus user numbers ?
        I mean, if i’m using Teams DR with a telco. Can I port my phone number to Office 365 as well to have call queue and auto attendant feature and port user numbers to the telco provider ?

      • Today, you cannot assign a telephone number from direct routing to a call queue or auto attendant. My understanding is that this is on the road map

11. Hi Damine,
    Just to start, Great article! Helped me alot in configuring DirectRouting along side the MS/Sonus documentation.

    I have a quick question in regards of debugging Calls via Teams direct routing.

    I have one way calling ability. That is I can call my teams client via pstn, but when I try calling from Teams the call does not come into my Sonus SBC and fails (obviously).
    I have a feeling it is related to network routing, but debugging this on the Teams end is something I have not been able to figure out yet.. I get the cause code in the Teams/Skype admin portal calling logs, but I would like a more detailed info on the call flow from Teams.

    I believe I have seen something in regards of this being in Azure, the local client logs are useless as far as I can see..

    Reply

    • Hi Darri,

      I’d start with logging on your firewall/Sonus to make sure the invite isn’t getting dropped at either firewall or SBC. Have you created the public DNS A Record for the Sonus?

      Reply

      • I have been logging on the client side with wireshark. For testing purposes I put my external address outside the firewall so that souldn’t be an issue with the Firewall.
        Yes I have DNS records and am able to connect to the IP externally via fqdn.
        Aren’t there any media logs available for debugging without having MS assist you ?
        I atleast get no viable data from the *.etl files using various readers.

      • Are you getting successful SIP Options in both directions?

      • I am getting the TLSv1.2 communications via Wireshark that I have not been able to decrypt so I can not be sure that the SIP options are successful in both directions.
        Fiddler is not giving me much to go on either as far as I can see.

12. Thanks for the great article, the following line saved my day 🙂

    Important: Make sure to add sip-all.pstnhub.microsoft.com to the Federated IP/FQDN list.

    Reply

    • You’re welcome Ayman 👍

      Reply

13. Hello, thanks for the article. I wanted to know what attributes are used by teams to know if the called number is a teams user? for example, Skype for Business checks the msRTCsip attributes in AD to do its RNL. what is the equivalent behavior in teams with direct routing, assuming that users are full online or synchedwith AAD.
    Thank you!

    Reply

    • Hi BC,

      I’m guessing you want to use this to support automatic routing of calls to Teams users from the SBC?

      You could possibly use the OnPremLineURI attribute, but that value only exists in AAD, not on-prem. You could potentially get it with MIM or similar and copy to an on-premises attribute that could then be queried for call routing. I haven’t come up with a solution to this just yet, will let you know if I do.

      Reply

14. Hello, thanks for the article. I wanted to know what attributes are used by teams to know if the called number is a teams user? for example, Skype for Business checks the msRTCsip attributes in AD to do its RNL. what is the equivalent behavior in teams with direct routing, assuming that users are full online or synchedwith AAD.
    Thank you!

    Reply

    • Hi Bouthainac, apologies for the delayed response.

      That’s a good question. I would say it looks at OnPremLineURI if it’s a Direct Route number, or the equivalent for a Calling Plan (pure online) user. If no match on RNL will route via configured routes for that particular user.

      Hope this helps?

      Damien

      Reply

15. Hi there,
    Great post.
    Looking at rolling this out in our office, but a question.
    Once direct routing is set up, can the user make and receive calls through a combination of physical desk phone and Teams?
    Sometimes it’s difficult to teach an old dog new tricks, and there are features such as paging that I’m not sure works through the Teams client.
    Cheers,

    Reply

    • Hi Nicholas,

      Great to hear the post was useful for you. In answer to your question: yes you can. Once you have added the Direct Route and setup calling for a Teams user, there’s nothing stopping an outbound call being made from either their legacy handset or Microsoft Teams (same direct in dial number will be used too). If you want to get both Teams and legacy phone to ring at the same time for an inbound call, you would need a forking licence on the Ribbon SBC. I try to avoid using this feature, I’d rather let users call out from wither platform but manage which client rings for inbound.

      Reply

16. Hello Damien,

    Great article. I appreciate your effort.
    Please, I have a question with regards to the article.

    “The dedicated one-to-one NAT on the perimeter firewall: 121.50.209.233 192.168.1.187. The private address was then bound as an additional IP address to Ethernet 1”

    Based on my set up, I have five logical interfaces on different networks (Admin IP, Ethernet 1, Ethernet 2, Ethernet 3 and Ethernet 4). The IP address used for Ethernet 1 – 4 all have Media Next Hop IP. This means that each of them has two IP addresses. Only the Admin IP has one IP address which is used to access the Web UI

    **Here is my question**
    From the quote above on the article, the IP address that has to be NAT to a public address. Is it the Admin IP address or the Media Next Hop IP address that needs to be NAT to a Public IP address?

    I look forward to reading from you soon.

    Best Regards,
    Onyinye

    Reply

    • Hi Onyinye,

      No need for you to have separate media IP addresses on all NICs, or even to have that many configured NICs. In my setup, I didn’t have an available NIC I could dedicate for direct route IP address so I just bound another address to an existing NIC.

      I would remove additional media IPs from NIC (unless you need them for some reason) and simply NAT to one of the primary IP addresses. Not the Admin IP, this should be dedicated for admin access.

      Hope this helps,

      Damien

      Reply

17. HI Damien,
    Great article thanks this helped me out a lot. However I have an issue with the Auto Attendant to forward to Call Queue. I’ve read that this has to do something with a REFER that the TEAMS engine is putting back on the SBC. I’ve tried configuring the REFER as Ribbon is suggesting in their documentation, but that didn’t work. So I’ve read that disabling REFER on the SBC will force Teams to do internal forwarding itself. However, I have no clue on where to disable REFER. Could you help me with this?

    Thanks a lot

    Ronald

    Reply

    • Hi Ronald,

      Check out this post: https://ucgeek.co/2019/07/dont-forget-the-refer-microsoft-teams-direct-routing-with-swe-lite/

      Reply

18. Wait a sec.

    If I’m hybrid OPCH with most/all users homed in the cloud and my “From PSTN” call routing still works while sending to my on-prem mediation servers in my signaling group, how do I manage individual user routing and/or pilot groups if I setup DR on my SBC? Do I have to go through a whole “find an attribute to sync on” exercise or do i just add “MS Phone System” as a 2nd signaling group in the existing call route table and assume it will simulring both signaling groups at the same time and then control invite notifications with client policies?

    Reply

    • Hi robg,

      One way or another, you’ll need to update the routing table for users you want to move to Teams voice (via Direct Route). You could do this a number of ways:

      – Manually update routing table\transformation table
      – Use an AD attribute to allow the SBC to dynamically route to Direct Route signalling group on an LDAP lookup
      – Use REST API to update routing table\transformation table when you move a user to Teams for voice

      The last one is handy if the SBC is in a DMZ and access to AD for LDAP lookup is problematic. What makes this even simpler is the existence of the PowerShell module for Ribbon (Sonus) SBCs: http://www.allthingsuc.co.uk/powershell-module-for-sonus-sbc-10002000

      I have used the latter to automate the whole process, using PowerShell to:

      – Check user is licensed for Teams\Phone System etc
      – Enable user for Teams with Phone System
      – Enable Voicemail (enabled by default these days)
      – Reach into SBC via PowerShell REST module and update call routing to route calls via Direct Route

      Hope this helps.

      Damien

      Reply

      • Hi Damien,
        if you want to use the second option, you can read and use my guide “How to dynamically route calls to Microsoft Teams instead of SfB with Ribbon SBC 1K/2K” here https://lucavitali.wordpress.com/2019/03/04/how-to-dynamically-route-calls-to-microsoft-teams-instead-of-sfb-with-ribbon-sbc-1k-2k/
        Best. Luca

19. How do I route calls through LDAP lookup to know if user is on CCE/SkypeOnline or Teams ? Rightnow I am doing LDAP query based on msrtcsip_line and if LDAP record is found, I am sending it to CCE. But How do I route to Teams with LDAP ?

    Reply

    • Hi pateshra,

      Given that there’s on on-prem attribute you can query, I have been using a customer attribute field from on-premises AD that I update as part of on-boarding script for any cloud voice users. I then query this attribute with LDAP from the SBC in order to dynamically route.

      Reply

20. Hi Damian,

    Thank you for a great article.

    I keep reading about the firewall configuration and what ports to open, it mentions “Defined on SBC”. Also watching the MS direct routing deep dive video, they mention “the ports will be configured under media profile”.

    Now, I used the Sonus easy configuration wizard which created everything automatically, but when I try to identify the media ports “Which supposedly defined on SBC”, I cannot find them anywhere.

    Any help on what are these port numbers? both for media and SIP signaling? and where they are defined?

    Thanks a million.

    Fayez

    Reply

    • Hi Fayez,

      There’s three places you’re going to find port config on a Ribbon (Sonus) SBC:

      – The listen port is configured in the signalling group (5061 for example)
      – The far end signalling port configured on each SIP Server entry on the SIP Server Table (5061 for example)
      – Media port range under Media System Configuration (16384-17584 for example)

      Thanks,
      Damien

      Reply

21. Can I assign Direct Routing number to audioconferencing user or bridge?

    Reply

    • Hi Zbigniew,

      This is not possible today.

      Cheers,

      Damien

      Reply

      • Hi Damien,

        Thanks for your quick reply, and great article!

        So, if I’m going to deploy Direct Routing, how will be look flow between Audioconferencing and Direct Routing?
        Could you explain me this point?

        Thanks,
        Zbigniew

      • Hi Zbigniew,

        These are mutually exclusive. Direct Routing allows you to route PSTN calls to\from your users and AutoAttendants\Call Queues. If you want Dial-in conferencing capabilities, you will need Audio Conferencing Office 365 licenses for every user that requires it. Once a user has teh Audio Conferencing license, they will get dial in conferencing information added to their Teams meeting invites.

        You don’t need a Direct Route to support Audio Conferencing: an Office 365 license gives you this.

Leave a Reply Cancel reply

Enter your comment here...

Fill in your details below or click an icon to log in:

Email (required) (Address never made public)

Name (required)

Website

You are commenting using your WordPress.com account. ( Log Out /  Change )

You are commenting using your Google account. ( Log Out /  Change )

You are commenting using your Twitter account. ( Log Out /  Change )

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

Notify me of new comments via email.

Notify me of new posts via email.

This site uses Akismet to reduce spam. Learn how your comment data is processed.