Microsoft Teams Direct Routing (Connect your own SBC for PSTN), including Direct Carrier Support

-
As in the general availability:
Microsoft Teams will support a Direct SIP connection (bring your own SIP) with SBCs on-premise.

Requirements:
  • You will require a certified SBC from Ribbon (Sonus) or AudioCodes
  • Other SBC vendors may be added in the future
  • Microsoft Teams and Phone System licences, or E5 license




    •  Besides the primary Direct Routing scenario, we anticipate customers will want to use this capability to integrate with other 3rd party voice applications. There are several additional scenarios:

    Easy Transition to Calling in Teams. By integrating with an existing PBX, pilot users can be moved to Calling in Teams while users remain on their legacy PBX. Eventually all users can be easily transitioned to Calling in Teams. The call traffic between these users during the transition stay within the organization.

    Telephony System Inter/Op. While users are being transitioned to Calling in Teams, Call Center agents can continue to use their application. Direct Routing enables both use cases to coexist. The call traffic between call center agents and Teams users stay within the organization.

    Support for Analog Devices. If an organization decides to move to Calling in Teams but has analog devices such as elevator phones or overhead pagers, these devices can be connected to Teams and Phone System via Direct Routing. Call traffic between analog devices and Teams users stay within the organization.

    Microsoft will certify select SBC vendors to insure they are compatible with our Direct Routing guidelines. We will start with AudioCodes, Ribbon Communications, and ThinkTel. Our plan is to continue to evaluate SBC vendors and certify as needed.

    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.

    Getting started with Calling in Teams

    If you are new to Teams, please review our quick start guide.  We also invite you to mark your calendars for March 22 for a Teams on Air episode with guest Nikolay Muravlyannikov, Sr. Program Manager where he will discuss Direct Routing in more detail.

     (Blog Post Reference: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Direct-Routing-enables-new-enterprise-voice-options-in-Microsoft/ba-p/170450)

    Comments

    Post a Comment

    Popular posts from this blog

    How to hide users from GAL if they are AD Connect synchronized

    -
    Image
    How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
    Read more

    Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

    -
    Image
    Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, uniqu...
    Read more

    MFA with Guest Access and different tenants settings

    -
    Image
    There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
    Read more