Search results

I like to keep an eye on the nginx access log. You can still be trying to break in constantly until their IP is caught and blocked by Fail2ban. tail -f /var/log/nginx/access.log

I found this post about how to make changes in FreeSwitch and FusionPBX to have the Call Center queue announce the position in queue to the customer. The post form @TurabG got me thinking that it would be nice to tell you your position as soon as you enter the queue. This is his post...

Another option is to lock down the PBX and whitelist the providers, and basic IP addresses for the building where the phones are. Then implement an OpenVPN server and use it for remote and roving workers. This makes the PBX almost invisible on the internet and eliminates the continual probes...

Obviously, the outbound route can be modified as such and I have done that. The changing of the XML code is probably too much for novice users. I'll leave it at that.

Most other systems, including FusionPBX, are not sending the +1 unless you tell it too. Yes, the +1 is accepted by most SIP vendors but is superfluous. It is especially annoying when someone on another system like a Cisco or Avaya switch has not prepared their systems to strip the +1 on an...

For all phone numbers and outbound caller-id, allow an option to not have the outbound caller-id show +1. I can understand that might be necessary for other countries, but most of the USA just has the 10-digit caller-id and the E164 format is not required (or desired.) The outbound route...

Is your module a premium one since I don't see it in the stock FS PBX?

Add Call Centers to the Applications menu but modify the recordings section to utilize the openai TTS generation for announcements.

I'm running FusionPBX version 5.3.8. Inbound and outbound talls to/from extensions work fine. However, in a ring group which has several extensions plus an outbound external number, the origination to that number always fails, rejected by the VSP. In the CDR, it shows CODEC L16/L16 which is...