Search results

  1. SBC controller showing as "inactive" in Teams admin

    Thanks, however I have already tried that (a couple of times). The SSL certificate for the teams FQDN was issued by SSL.com in accordance with the 3CX guide, so I can only assume that it's correct.

  2. SBC controller showing as "inactive" in Teams admin

    Yeah that's all understood. I've tried it with the SSL.com certificate for the teams.businessname.com.au domain in secure SIP, and the SSL certificate that was in those fields by default. It doesn't seem to work either way. The domain for which the SSL.com certificate has been issued is the same...

  3. SBC controller showing as "inactive" in Teams admin

    Hi Charles We have a custom FQDN for the Teams integration (teams.businessname.com.au), but the standard accountname.3cx.com.au FQDN for 3CX in general. So should the certificate under "Secure SIP" be the same as the certificate for the Teams integration, or should it be a different...

  4. SBC controller showing as "inactive" in Teams admin

    Hi I'm attempting to implement the 3CX/Teams integration, however having a lot of difficulty in getting the SBC controller to connect (using a custom domain and on-prem 3CX appliance). No matter what I seem to do the "TLS connectivity status" for the SBC shows as Inactive and I'm unable to make...

  5. DTMF issues

    Thanks for the response - it's RFC2833. Oddly enough, it started working again shortly after I posted this thread. So seems to be an intermittent issue

  6. DTMF issues

    Hi all New to 3CX, we moved over from Elastix last week. Initially I had some trouble with the digital receptionist/IVR, in that it wasn't seeing any DTMF tones come through from inbound calls. The IVR greeting would just play over and over and any key press from the inbound call had no result...
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom