Avaya Session Border Controllers Certified for Microsoft Teams Direct Routing














After Cisco Cube/Voice Gateway/SBC was certified for Microsoft Teams Direct Routing its now another vendor which has been certified for Teams Direct Routing Services. Avaya SBC are now certified for Microsoft Teams Direct Routing enabling the organization who are using the Avaya SBC to Interop with the PSTN Integration with Microsoft Teams.

Currently SBC Avaya Session Border Controller for Enterprise (ASBCE) with the Release 8.1.1 version is Certified for Microsoft Teams Direct Routing. This will only support the Non-Media-Bypass Test Cases for Microsoft Teams Direct Routing.

Microsoft Roadmap reference 66465

Reference: -
All the SBC Certified for Microsoft Teams Direct Routing List here.


Comments

Post a Comment

Popular posts from this blog

Multiple Instances Microsoft Teams Application

Microsoft Teams Application has always been improving based on the feature’s availability in the Teams Application. Microsoft has been enhancing the features some based on the existing Skype for Business Application and some based on the User Voice Request. There is already an ongoing User Voice Request to have multiple instances of Microsoft Teams on the Windows Machine. The major use of the multiple instances of Microsoft Teams Application: - 1.       Being from the Support industry the people need to be logged into the corporate account and a test account for testing the features simultaneously 2.       To do multitasking project with multiple people viewing the desktop from two different people. 3.    Attending Two Different Meeting at a same time wherein one of the meeting you are a silent participant or just the host of the meeting Disadvantages of using multiple instances of Microsoft Teams Application 1.       Multiple Notification of Chat Messages Cal
Read more

Microsoft Teams Voice Gets Enhanced with New PSTN Call Routing Feature

Image
Microsoft Teams Voice has recently added a new feature that allows administrators to control how PSTN calls are routed to user accounts. This is a critical feature for many organizations, as it allows them to separate PSTN calls from internal calls. The new feature is part of Microsoft Teams Calling Policy. To enable it, administrators need to log in to the Teams Admin Centre and navigate to the Voice section. Under Teams Calling Policy, they will see two options for PSTN calls: Inbound PSTN: This option covers any incoming call coming into the tenant via Direct Routing, Microsoft Calling Plan, or Operator Connect. Inbound federated: This option covers any incoming non-PSTN call that is originating outside your own tenant. Once administrators have selected the desired option, they need to click Save. The new settings will take effect immediately. It is important to note that the Teams client end setting for end users to manage this configuration is currently
Read more

Delegate Features in Microsoft Teams Get a Major Overhaul, Including Call Barging

Image
Microsoft Teams has added new features for Delegate. One of the key features added recently is Call Barge. Is this the start of the Contact Centre Development within Microsoft? Let’s see what the major changes are introduce to the Microsoft Teams Voice Delegate.        1.   Firstly, Microsoft introduce a separate Call Logs for the Delegates and Delegator. All the Person Calls              will be in a separate Call History and Delegate Call History will be separate.  Delegate’s Personal Call History Delegator’s Call History 2.      In case the users are using New Teams Client the Delegation Feature is in Call Tabs. It is still under the General Tab in the Old Teams Client 3.      Earlier we only had three configurations while Delegating the Access. Now we have Five configuration which includes the configuration for Call Barging or Joining the Active Call and Pick Up Held Calls. 4.      If a Delegator has multip
Read more