Search results

@mdriaz This is correct. When it rings through the ring group or another similar dialplan, it will not execute the local_extension dialplan. I think you need to look into Freeswitch events. You will probably be able to catch an event where a particular extension rings and then execute your script.

@ou812 What is your use case for multiple domains? All large VoIP providers have one single URL for users to use.

Could you please clarify how an external caller dials extension 123? For instance, is this accomplished through an IVR or another mechanism? Typically, external callers cannot directly dial internal extensions without additional steps, so this context will help us provide a more accurate answer...

Hello everyone, I have prepared a comprehensive tutorial on enabling TLS support for FS PBX and FreeSWITCH. If you notice any missing elements from the required steps, please feel free to let me know...

It will probbaly be something like this action set result=${system(usr/bin/php /path/bash.php)} I didn't test this myself but I'm pretty sure you need system to execute php scripts You may have to play with the INLINE option, too. However, Lua scripts integrate seamlessly with Diaplan, and...

@ou812 One of the key advantages of using FX PBX is that you only need a single domain. This domain directs traffic to your primary IP, and all users log in through the same URL and email addresses. Additionally, our script facilitates the generation of a Let's Encrypt certificate for this...

@vuthy09 I found no issues enabling TLS on the recent FS PBX install. However, it is not a simple procedure. It originates from how FusionPBX works behind the scenes. I'm going to streamline this in future releases of FS PBX. Here is a few things you can check on your installation. Run this...

@vuthy09 I'm going to install a TLS certificate for a client tomorrow, and I will investigate if there are any issues. I'll keep you posted.

Thank you for confirming!

@DigitalDaz @vuthy09 I was able to reproduce the issue and have identified a permanent solution for future installations. For your current deployment, please manually delete all settings under Default Settings -> Switch and then execute the following command: cd /var/www/fspbx && /usr/bin/php...

Ah, they are still empty. Now I know what's going on. I'm going to fix it today and update everyone. Apparently, the fix I made didn't apply to new installs.

How about all the other settings under the switch category? Do they look like they got populated? There was an issue with those not getting populated. I thought I had fixed it about a week or so ago. So right now, I'm trying to figure out if this is the only setting with an issue or if they are...

@DigitalDaz thank you for confirming that this issue exists on some installations. Could you or @vuthy09 tell me if the default setting on the screen shot is empty on your installations? It will help me narrow the issue further.

@vuthy09 send me a private message. We can it offline and figure out what's going on.

This is only needed if you specifically changed the default settings for the ESL connection. Have you confirmed that you can open fs_cli?

I'm glad you like it. I post new videos whenever I can. There is so much I could make videos for, but it's a tedious process. You can use all sources (FS PBX wiki on Github, my YouTube channel and general FusionPBX docs)

If you are using SQlite for your freeswtch database, you can create a script that will remove stale calls. Sometimes calls get stuck and need to be removed manually. I've posted a script example here earlier https://www.pbxforums.com/threads/active-call-stuck.7872/#post-32062

@franciscom.corona, I haven't tried it myself, but you would be able to change the external to internal IP in the .env file based on the wiki page and have everything working locally.

@vuthy09 Something is not working on your machine. I just checked a newly installed server, and sip profiles and modules pages load without any issue. Is Freeswitch running on your machine?

@vuthy09 Did the link above not help you? You get this error when the session variable doesn't match the browser URL address. It's a security measure that the Laravel framework has against people trying to brute force. If you follow all the steps in the article, you should be able to fix it. If...