unsupported configuration

  1. BLF on second line/account

    Hi, I appreciate that this will be an unsupported matter, but I would like to ask any Yealink users if they have been able to get BLF working correctly on a second line. Phone = Yealink T54W 3CX servers = Professional (x2) both self hosted on Azure and the instances are not related to each...
    • UK-Steve
    • Thread
    • unsupported configuration
    • Replies: 4
    • Forum: Yealink

  2. Cisco 8831

    Hi all, Has anyone had luck integrating 3CX with a Cisco 8831? I followed some examples I found on this site and Cisco's but I cannot get the phone to register with 3CX. Connectivity is good and am seeing the Cisco pull files from my TFTP server. I know it's not supported but this is a special...
    • Matt_NM
    • Thread
    • 8831 cisco cisco 8831 unsupported unsupported configuration unsupported phones
    • Replies: 1
    • Forum: Phone System / PBX

  3. Solved Privacy: id Withheld Caller ID

    We have an "unsupprted" sip trunk we use. The provider has asked for the below value for withholding the caller ID to be passed to the VoIP provider. They have referenced the below RFC3325 standard which uses a privacy type value. Any ideas how I can get 3CX to do this...

  4. Solved Unsupported Point to Point configuration

    Hi all, I know this is an unsupported configuration, but has anyone been able to force their sip traffic between 2 fiber connected LAN's? I find it very stupid that I must send my calls between offices out over the internet when I have a better connection available. And before I get bombarded...
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom