Search results

CDR by default shows only the Aleg of the call so you won't get 2 records in a call forward scenario. I agree that in the case of a call forward, it should be marked as an inbound call.

What's the reason the first gateway fails? It will only failover if the failure reason matches one of the failure reasons in the continue_on_fail variable. You can set continue_on_fail=true to always failover regardless of the failure reason.

So why do you need a lua script for this? Call the API from any external script, update the fusionpbx v_extensions table with the new caller id values, and flush the fusionpbx file cache.

Unless I don't understand what you're trying to do, this should be very simple. Caller IDs are set by setting origination_caller_id_name or effective_caller_id_name. you can do it from lua with session:setVariable().

There was a slight error in the regex of the snippet I gave you. If it doesn't work, can you show your dialplan and logs?

Can you explain what you're trying to accomplish?

You can do it with a simple dialplan like this. <extension name="extension_call_permissions" continue="true"> <!--block if caller is 2006 and calls 2000,1,2--> <condition field="${sip_from_user}" expression="2006"/> <condition field="destination_number" expression="^200[0-2]$">...

You can find the generated xml files in /var/cache/fusionpbx

Fusion saves those data in the postgres database and builds the freeswitch XML config files dynamically.

Ironically freeswitch doesn't provide any way to parse sip headers. The header gets set as a channel variable sip_h_P-Charge-Info you can parse it with lua. hdr = session:getVariable("sip_h_P-Charge-Info") trk = hdr:match("Trk=(.+)") I edited this message what I initially wrote doesn't apply...

Something like this should work for you. ^\+?1?([2-9]\d{2}[2-9]\d{2}\d{4}|(?<![\+?1])(?:011\d{9,17}|911|311|411))$

The backtrace is only useful when the dump is taken when the system is frozen and locked.

There are a lot of scripts and guides circling here on the forum about this, just give it a search.

You'll have to get a core dump when this happens. You can follow the guide in the link below on how to get one, and then upload the gdb output here. If you're using wss, there's currently ongoing development in freeswitch on fixing issues with sofia freezing when using wss...

Hello and welcome!

In any case, with the external numbers, what are the chances the receiving carrier will trust the caller ID name?

External calls are using loopback, which might be the reason. The ring group lua script exports effective_caller_id_name with the prefix to the bleg, but in the case of loopback it might not get exported to the real b channel. The logs should show you whether it was set on the bleg.

It is possible, but you have to add the functionality in the lua hangup hook script to handle it.

You can do that with group_confirm_file and group_confirm_key. You'll have to create a dialplan or dialplan tool that makes use of it.

Fusion plays that file only for extensions matched by the direct dial. It won't play it for any match in the ivr options even if it's an extension. You can manually set two ivr option 1s and have the 1st one play the file and the 2nd do the transfer. Another cool way to accomplish this is by...