Teams Direct Routing - SBC TLS inactive

%3CLINGO-SUB%20id%3D%22lingo-sub-3186664%22%20slang%3D%22en-US%22%3ETeams%20Direct%20Routing%20-%20SBC%20TLS%20inactive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3186664%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Teams%20Community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20i%20need%20your%20help%20on%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20Teams%20Direct%20Routing%20dashboard%20our%20SBC%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fulsbc01.ul.ie%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Eulsbc01.ul.ie%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eis%20showing%20up%20with%20a%20TLS%20Connectivity%20Status%20of%20Inactive.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExamining%20the%20cert%20loaded%20on%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fulsbc01.ul.ie%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Eulsbc01.ul.ie%3C%2FA%3E%2C%20its%20root%20signing%20certificate%20is%20Sectigo%20(AAA)%20with%20the%20Subject%20Key%20Identifier%20of%20%E2%80%9Ca0110a233e96f107ece2af29ef82a57fd030a4b4%E2%80%9D.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20verify%20this%20was%20correct%20we%20accessed%20the%20following%20through%20the%20screenshot%20below%20which%20contains%20the%20Microsoft%20CA%20certificate%20list.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20it%20we%20noted%20that%20Sectigo%20%5D%20AAA%20Certificate%20Services%20is%20listed%20and%20when%20we%20downloaded%20the%20cert%20from%20there%20we%20noted%20that%20its%20Subject%20Key%20Identifier%20on%20the%20cert%20is%20also%20%E2%80%9Ca0110a233e96f107ece2af29ef82a57fd030a4b4%E2%80%9D.%20Screenshots%20attached.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20any%20idea%20why%20our%20TLS%20connectivity%20status%20is%20showing%20as%20Inactive%3F%20When%20I%20click%20on%20the%20error%20it%20says%20%22Inactive.%20The%20trunk%20never%20connected.%22%20Any%20help%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3186664%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20Call%20Queue%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20DR%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3187605%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Direct%20Routing%20-%20SBC%20TLS%20inactive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3187605%22%20slang%3D%22en-US%22%3EHello!%3CBR%20%2F%3EIf%20the%20certificate%20is%20ok%2C%20I%20would%20check%20connectivity%2Ffirewall%2C%20there's%20got%20to%20be%20SIP%20Options%20between%20the%20SBC%20and%20Microsoft%20infra.%3CBR%20%2F%3EWas%20anything%20changed%20recently%20at%20that%20level%3F%3C%2FLINGO-BODY%3E
Super Contributor

Hello Teams Community,

 

Please i need your help on this.

 

In the Teams Direct Routing dashboard our SBC ulsbc01.ul.ie is showing up with a TLS Connectivity Status of Inactive.

 

Examining the cert loaded on ulsbc01.ul.ie, its root signing certificate is Sectigo (AAA) with the Subject Key Identifier of “a0110a233e96f107ece2af29ef82a57fd030a4b4”.

 

To verify this was correct we accessed the following through the screenshot below which contains the Microsoft CA certificate list.

 

From it we noted that Sectigo ] AAA Certificate Services is listed and when we downloaded the cert from there we noted that its Subject Key Identifier on the cert is also “a0110a233e96f107ece2af29ef82a57fd030a4b4”. Screenshots attached.

 

Do you have any idea why our TLS connectivity status is showing as Inactive? When I click on the error it says "Inactive. The trunk never connected." Any help would be greatly appreciated.

 

 

1 Reply
Hello!
If the certificate is ok, I would check connectivity/firewall, there's got to be SIP Options between the SBC and Microsoft infra.
Was anything changed recently at that level?