Search results

I feel so ashamed. Turns out I had a spending block on my outgoing calls that prevent many international calls. I reset the spending limit, and it now works. I am so sorry to be a bother, but thank you so much Adrian for taking the time to look at my post, and to give me help.

I have a domestic carrier (gateway) that works fine, but they do not provide international calls, only domestic calls. I just setup an international carrier (gateway) and the calls fail. I am using the default international dial plan expression provided in FusionPBX: ^(011\d{9,17})$ When I...

Happy to send you a copy of the dial plan in question. I hope it helps. I would really like to know why this is happening.

Adrian, Thank you for being willing to help. The inbound destination was generated automatically as: ^(xxxxxxxxxx)$ when I created the destination, and it did not work. It was only when I changed the destination to the extension number that it worked. By the way 100 is not in the number. This...

I installed FusionPBX on Digital Ocean using Debian, as recommended. I setup two extensions, with two destinations, per the manual. I installed an origination gateway, and a termination gateway. Outbound calls work, but inbound do not. I did some investigating on this forum and found another...

Thank you Adrian for your response to my request for help. What you told me kind of pointed me in the right direction. I finally found out what was wrong. I had both ipv4 and ipv6 dns records for my FQDN. What I didn't realize is that Lets Encrypt now prefers ipv6 over ipv4, so the script...

Thank you for your response and help, but after contacting digital ocean about this issue their tech seems to think it is an error in the installation script. I do recall that the first time I installed fusionPBX letsencrypt used a dns challenge with a single domain, now it uses an http...

I installed FusionPBX on Digital Ocean Droplet using Debian 10 pointed to a FQDN that is not encrypted. The installation works fine until I install Lets Encrypt. The Lets Encrypt installation fails, and I get the following terminal output: (I changed the names to protect the innocent.)...

Okay, I did some more research and I discovered that if I make a change in my outbound route it works. Problem is, I don't know what the change means. If anyone who reads XML could give me a clue I would appreciate it. I don't want to make my PBX work in an improper way. This is the before...

Thanks for being willing to help. Here is my outbound route. <extension name="carrier #1.1d10" continue="false" uuid="c29c679b-11a8-4292-b58c-842bd7faa610"> <condition field="${user_exists}" expression="false"/> <condition field="destination_number" expression="^\+?1?(\d{10})$">...

Thank you for your help, but your suggestion implies there is a real problem with FusionPBX. I followed the manual precisely, and outbound calls do work if I register with a carrier who requires registration. It is only when I use a carrier where I don't register that it fails. It may not be...

I just installed FusionPBx on a VPS on the hosting platform Digital Ocean, I have a domain for the PBX, and I have secured it with Letsencrypt per the instructions from FusionPBX. I setup my gateway provider as a global outbound route, not registered. I had no trouble registering a device, or...

I just installed FusionPBX and I posted a new thread with better information about my problem, and I couldn't figure out how to delete this one.