Teams SBC TLS still showing unactive

[APF1]

We have attempted to setup the teams intergration but have been stuck at with the SBC tls showing as inactive. We have tried a couple of different SSL certificates for our a-record, and the most recent one was the free trial from ssl.com.

Checking with openssl appears the cert is all corrrect;

CONNECTED(00000280)
depth=3 C = PL, O = Unizeto Technologies S.A., OU = Certum Certification Authority, CN = Certum Trusted Network CA
verify error:num=19:self signed certificate in certificate chain
verify return:0
---
Certificate chain
0 s:/CN=teams.xxxxx.com.au
i:/C=US/ST=Texas/L=Houston/O=SSL Corporation/CN=SSL.com RSA SSL subCA
1 s:/C=US/ST=Texas/L=Houston/O=SSL Corporation/CN=SSL.com RSA SSL subCA
i:/C=US/ST=Texas/L=Houston/O=SSL Corporation/CN=SSL.com Root Certification Authority RSA
2 s:/C=US/ST=Texas/L=Houston/O=SSL Corporation/CN=SSL.com Root Certification Authority RSA
i:/C=PL/O=Unizeto Technologies S.A./OU=Certum Certification Authority/CN=Certum Trusted Network CA
3 s:/C=PL/O=Unizeto Technologies S.A./OU=Certum Certification Authority/CN=Certum Trusted Network CA
i:/C=PL/O=Unizeto Technologies S.A./OU=Certum Certification Authority/CN=Certum Trusted Network CA


Is there a particule log file we should be recviewing to help identify if the issue is with our 3cx instance or teams still provisioning the phone system. (We only added on the licenses about 16hours ago)

 

[NickD_3CX]

Hi!

First of all I would highly suggest reading our FAQ guide which helps most overcome most issues:
https://www.3cx.com/docs/microsoft-teams-integration-faqs/

In your specific case, I suspect either:

• The key/cert combination is not correct. You can check here how to verify it:
  https://www.3cx.com/community/threa...5062-not-allowed-by-default.83936/post-393631
  
  
• In the Management Console --> Security --> Secure SIP, make sure it is enabled and there are valid certificates there (if you have used 3CX FQDN you should be fine, if custom FQDN, this could be a problem)
  
  
• From Settings --> Microsoft 365 --> Teams Direct Routing, verify which TCP port it tells you must be open, then check the following post how to check that 3CX is listening on this port:
  https://www.3cx.com/community/threa...5062-not-allowed-by-default.83936/post-393244
  
  
  
• Double-check that on your Firewall, you have opened the specific port you found in the above bullet.

 

[APF1]

Thanks for your reply Nick. Oddly we tested it shortly after my previous post and we had perfect call flow 3cx to teams, teams to 3cx, teams to external, external to teams all without issue. I followed up with ms who provided this answer regarding the tls staying inactive;

[8:33 pm] xx
It will not cause any issues

[8:34 pm] xx
The active status is used incase you have multiple SBC and you want to route call with the one from which SBC received TLS SIP options.

[8:35 pm] xx
Its moreover a heartbeat check.

Another thing I noticed is we are unable to call our main sip number from teams, but this is probably by design or a rule we need to adjust. Lastly what is the correct way to remove teams intergration for an extension (Remove the phone license?)

 

[NickD_3CX]

Great to hear that it is now working!
Sometimes it does take MS some time to get things provisioned or their end... (we have heard some cases of up to 24h).

Another thing I noticed is we are unable to call our main sip number from teams, but this is probably by design or a rule we need to adjust.

Are you trying to call this number from a Teams client that you have synced with 3CX?
If yes, then what you are doing does not make much sense, essentially you are trying to call your own number, from your own number.

Lastly what is the correct way to remove teams intergration for an extension (Remove the phone license?)

Yes, this should be enough, just bear in mind that once you remove the License, it may take a few hours for it to be removed. You can check with this is done by going to the "Users" node in the Management Console and checking the "Synced with" column, once the "MS 365+Teams" turns into "Microsoft 365", it should be done.
If this hasn't happened automatically after 24 hours, try restarting all the 3CX Services once.