Solved Confused about FQDN for the SBC and generating a SSL certificate

[ahbladmin]

Thanks in advance for any advice. We have our instance in Azure with the 3CX supplied domain of xxxx.my3cx.ca. I understand that the FQDN of the SBC should just be sbc.<our email domain>. So a new A record was created for sbc.<our email domain> pointing to the same IP as the 3CX instance in Azure.

So the configuration is successful as far as allowing calls in both directions from Teams to Teams, or incoming from PSTN to Teams, but failing when outgoing from Teams to PSTN with the error "We couldn't complete the call.". I suspect the issue is with the SSL certificate for sbc.<our email domain> because when I use an online tool to verify it, the check fails because the IP address is already associated with xxxx.my3cx.ca.

Am I ignorant in my understanding of SSL or does this require additional configuration because our 3CX server is not hosted with our own email domain?

We are running the Azure Linux instance version 18.0.1880.

George

 

[ahbladmin]

Another post falling in the category of "fixed it myself". Turns out nothing wrong with the certificate. I didn't realize that the outbound rules in 3CX still had to be configured as the PSTN calls are routing from Teams to the 3CX server. Once those were set, the calls completed. Hopes this helps other noobs.

 

[NickD_3CX]

Glad to hear you got it figured out!

It's exactly as you said, once an outbound call from Teams reaches 3CX, it is still subject to the 3CX Outbound Rules, Country Code restrictions, etc.

Also, although this was not the case here, after configuring Teams for the first time, you may have to wait up to 24 hours for changes to be applied, so if you have triple-checked everything, waiting a day and then trying again might also be a good idea.

Setting this thread as "Solved".