Search results

It tells you that the domain doesn't exist with that name. It's also a domain that looks like IP address. Have you tried a simple name?

Technically, yes, but you do have an extension like that in your dial plan, so it's possible that the ${user_exist} variable is set to true at that point. You can check the variable values and confirm.

This is your issue. Why are you making your IVR numbers 10 digits? It will match the REGEX for outbound trunk. Make it 3 digit long and it will work as you expect.

This must be how your dialplan external routes are set up. Your conditions for sending external calls through the trunk are too lose so it matches even internal extensions. I'd recommend you investigate the external dialplan to only match outbound calls.

I know some people do it outside of FusionPNX with ASTPP. All calls will be sent to ASTPP trunk and then ASTPP will do the LCR.

Give it a try—I hope you find it useful! We're constantly innovating and adding new features. Currently, we're redesigning the outdated IVR page to make it more intuitive and user-friendly. Additionally, we're working on integrating webhooks with Yealink and Polycom redirect services to...

if you are using the HTTP upload method, check if the cron job Is running.

I have built both inbound and outbound webhooks for the FS PBX dashboard, enabling seamless integration with external systems. For instance, the faxing functionality in FS PBX leverages webhooks from Postmark. When Postmark receives an email containing a fax, it triggers a webhook request to FS...

Recent updates to Debian 12 have disrupted the FusionPBX installation script, leading to installation failures. While Debian 11 was a viable alternative until recently, similar updates have now affected its compatibility as well. The FusionPBX support team is aware of these issues and is...

If you modified the Lua script in the FusionPBX directory, you need to run the Update command (you can do it from the web). It copies all Lua scripts to the correct directories for FreeSWITCH.

You may need a custom dialplan for this instead of using ring groups.

Welcome to the community!

Yes you should see the blocks in the IP Tables

@smokinjo, did you restart the gateway after making changes? A restart is necessary after each update, as simply saving the changes won’t fully apply them.

Yes, those two suggestions above are the most optimal.

I can't answer why the same call goes through different paths. It seems like an issue with dialplan or how the number is dialed.

I think what you are loking for is a setting in Gateways. It's called Caller ID in From. It will pass your phone number to the carrier in the header instead of Freeswith. I had the same issue with US trunk providers.

This, in fact, was an issue some time ago. Probbaly a year or os ago. A bug in the LUA script made those buttons not work properly. You must ensure you have the updated voicemail LUA script in the right folder.

That doesn't seem right. If the agent is logged out, the queue will not send calls to that agent. You may have some misconfiguration.

For optimal queue operation, it's recommended that agents log out rather than use Do Not Disturb (DND). The queue system is designed to function most effectively when agents actively log in and out, ensuring smooth workflow and accurate agent availability tracking.