I see this is an old thread, but I'll add that in the 101076951 document referenced above (which is helpful), it states that a SigMa script should be used to modify Record-Routes and Contact headers, but the provided script in the document only adjusts the Record-Route headers. We add another line to adjust the Contact header as well. This enables MS Teams to send OPTIONS messages back to your SBCs.
act on message where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
%HEADERS["X-MS-SBC"][1] = "AVAYA SBCE-x.x.x.x-xx-xxxxx";
%HEADERS["Record-Route"][1].URI.HOST = "<your sbc fqdn>";
%HEADERS["Contact"][1].URI.HOST = "<your sbc fqdn>";
}
------------------------------
Tyler Preder
Telecommunications Design Engineer
University of Washington
Seattle WA
------------------------------
Original Message:
Sent: 09-10-2021 09:55 AM
From: William Harris
Subject: Avaya SBC Integration with Microsoft Teams
We are researching feasibility and value of integrating our on-premises Avaya solutions with Microsoft Teams to allow user-to-user calling across the platforms and provide Teams access to some of our Avaya connected public Telco services. Current plan is to use Avaya SBCE and Microsoft Direct Routing as outlined in the following guides:
The recent Avaya/MS CPaaS partnership announcement included certification of Avaya SBCE 8.1.3 for Teams Direct Routing with Media Bypass, which seems to indicate a roadmap for continued support and development. Other than the above links and the announcement though, posts and info for this specific option aren't so easy to find. Wondering if any other Avaya customers have experience with this type of integration and would be willing to share any lessons learned? Thanks.