Acme Packet (MOSC)

MOSC Banner

Config changes needed due to new MS Teams TLS certificates

edited Mar 9, 2022 5:22PM in Acme Packet (MOSC) 5 comments

Hi!

It looks like MS will replace the TLS cert used by MS Teams -> https://techcommunity.microsoft.com/t5/microsoft-teams-blog/tls-certificate-changes-to-microsoft-365-services-including/ba-p/3249676

When setting up MS Teams Direct routing the following procedure is followed;

"The DNS name of the Microsoft Teams Direct Routing interface is sip.pstnhub.microsoft.com. Microsoft presents a certificate to the SBC which is signed by Baltimore Cyber Baltimore CyberTrust Root. To trust this certificate, your SBC must have the certificate listed as a trusted ca certificate. You can download this certificate here: https://cacert.omniroot.com/bc2025.pem "

The announced change from the MS side (using a cert relying on new Root CA "DigiCert Global Root G2") will it affect our SBC Teams configuration i.e. do I need to download and install the new certificate? And can they co-exist? I guess so, maybe just a matter of adding the new one to the list of trusted CA-certificate in the TLS-profile?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center