Search results

If you need an "else" for the condition being false, you would use an Anti-Action. Freeswitch documentation link below: https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Dialplan/XML-Dialplan/#actions-and-anti-actions

Glad you have got it working. Just curious, what version of Fusion are you running?

There will be a reason! Check what you have inbound-codec-negotiation set to. I tend to use "generous". It may be worth getting a packet capture to find out exactly what is going on.

488 is "Not Acceptable Here". This can often be caused when the two endpoints could not agree on a common codec. I see from the log that one end is offering PCMA and PCMU, but it looks like the other end is only offering G722. This could be your problem.

The curl application sets the variables curl_response_data and curl_response_code, so you can test these variables to decide if any further action is required.

There are many ways in which you can do this. If using an endpoint, Yealink phones have an "Action URL" feature. If, as the title of your post suggests, you would like Freeswitch, to call an external URL, then you have these [not limited to] options: Use an .lua script to call the URL. Use...

You need to alter the cascading style sheet for the installation. The default CSS is created on th efly by fusionpbx/themes/default/css.php. There are defaults here that are used when the specified default setting does not exist. The following snippet of code from css.php may explain this a...

There is nothing in that screenshot that would affect audio. I would bet the problem is elsewhere. In situations like this I always get a packet capture so I can see where audio is being sent. Have you tried a different destination to see if the problem still exists. I often send or receive...

In its simplest form, you can create a dialplan entry with a couple of lines and set it's destination field to True, see the screenshot below. This uses local extension 788 to call external 123 (123 is the speaking clock in the UK). Of course you may want to also add other channel variables...

That is the way I have always done it.

A destination is any record in the Dialplan Manager that has the destination field set to True, see screenshot below. Your destination will typically be an outbound route, but there is nothing to stop anything being classed as a destination. You would add/modify the variables in the details of...

You can set the channel variables effective_caller_id_name and effective_caller_id_number in the destination itself.

You have not given much detail, so this is just a wild guess... You may need to set the variable sip_invite_domain in your outbound route to match whatever you have set in the From Domain in your gateway record.

You may find this post helpful... https://www.pbxforums.com/threads/ivr-prompt-choice-not-dialing-in.5922/#post-23907

The xml_handler .lua scripts are generally called by FreeSWITCH when it needs some configuration information. You can see this being set up in /etc/freeswitch/autoload_configs/lua.conf.xml. Here is the relevant section in that file: <!-- Deliver XML from lua with the XML Handler...

Look at /var/www/fusionpbx/resources/switch.php and find the function called save_dialplan_xml(), this updates the cache file(s) when a dialplan is edited, in your case when a time condition is edited.

Hi John, I would love to help you, but I am at a disadvantage because 1, I have not upgraded to Fusion V5 and, 2, I don't really use SMS on the PBX. I would start looking at the loaded modules, older Fusion versions will load the FreeeSWITCH module mod_sms. Look at the configuration files as...

You may find this post on the subject helpful... https://www.pbxforums.com/threads/ivr-prompt-choice-not-dialing-in.5922/#post-23907

The dig utility can help you to diagnose DNS issues. For example to see what google makes of this site: adrian@a2es-test1:~$ dig @8.8.8.8 www.pbxforums.com ; <<>> DiG 9.11.5-P4-5.1+deb10u8-Debian <<>> @8.8.8.8 www.pbxforums.com ; (1 server found) ;; global options: +cmd ;; Got answer: ...

I am very glad you have got this working, however non of this makes much sense without the context of before and after packet captures for comparison.