Search results

  1. Allowing PBX to Connect to the MCU via Firewall Whitelist

    Thanks Charles, adding v18-vc-qos.3cx.net to the firewall did the trick and it's able to connect now.
  2. Allowing PBX to Connect to the MCU via Firewall Whitelist

    On the firewall for the PBX we are whitelisting what destinations are accessible, and I'm having a difficult time with the MCU functionality. I found this post https://www.3cx.com/community/threads/ports-required-to-connect-mcu-webmeeting.73303/ and have whitelisted the domains that it...
  3. Cannot get Caller ID for Outbound Calls to Work

    It appears that you can't chain IIf functions together? For example I want to leave numbers that start with + alone, just add the URL encoding. Then if a number starts with 1, just add a +. And otherwise add +1. <Request...
  4. Cannot get Caller ID for Outbound Calls to Work

    Hmm ok. I thought about editing the template, in fact I already did edit it to use token authentication instead of password. But we'll also need to support international numbers, I've just started with US/Canada numbers. I see that the XML template uses a .Replace function, not sure if that...
  5. Cannot get Caller ID for Outbound Calls to Work

    No the SIP trunk works fine with E164 numbers. And since I disabled "E164 Processing Settings" if I dial out this way it links to the Zendesk contact just fine. But I want users to be able to type in the 10-digit number and dial that way as well and still link to the correct contact.
  6. Cannot get Caller ID for Outbound Calls to Work

    In Zendesk all of our contacts have phone numbers stored in the E.164 format. So I created reformat rules that simply take 10 digit phone numbers and prepend them with +1. It's working fine for inbound calls, but for outbound the phone numbers remain in the 10 digit format. I have tried...