Recent content by dsanetops

  1. Solved Inbound calls only to 3CX but not to Teams, Outbound ok

    It's working now. I did a few changes, and not sure which one got it to work. 1) changed the direct sip calls domain from sbc.domain.com to domain.com 2) the port that it was listening on previously was 5061, but after doing the above change, it moved to 5062. I re-aligned SBC port to 5062 in...

  2. Solved Inbound calls only to 3CX but not to Teams, Outbound ok

    Hello Nick. Info sent via PM. No I don't use wildcard. I have a fqdn specific certificate for this.

  3. Solved Inbound calls only to 3CX but not to Teams, Outbound ok

    Call to T:Extn:1001@[Dev:sip:+230xxxxxxx;[email protected]] from L:3.1[Extn:1003] failed, cause: Cause: 503 Transport failure: no transports left to try/INVITE from local Hello Nick. Each time I am trying a call, I can see the following logs.

  4. Solved Inbound calls only to 3CX but not to Teams, Outbound ok

    Hello Nick. This is what is see on mine.

  5. Solved Inbound calls only to 3CX but not to Teams, Outbound ok

    Yes, I can see user is synced as MS 365+Teams. And you are right, the other PBX is just a Cisco Callmanager cluster to which the PSTN is connected. I have followed the guide you shared in order to build the integration.

  6. Solved Inbound calls only to 3CX but not to Teams, Outbound ok

    Hello, our 3CX sits in the middle of Teams and another IPBX, Calls from Teams bridge successfully to the outside world (IPBX internal users and PSTN line) However the in the reverse direction, calls come to 3CX and ring on a phone or web client registered on 3CX but not on the corresponding...
See more
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom