Recent content by agree

Of course, you can do it from the GUI. I just demonstrated how to do it using a PL/SQL function. In fact, it's actually faster than using the UI (at least in the version I'm running)

Your lua script is being called after freeswitch checks all conditions, so group 2 conditions are checked before the lua script is called. Solution: After the lua script action, transfer the call to a different dialplan that will check the action vars are set.

If fusion had used domain_uuid with a foreign key reference to v_domains with ON DELETE CASCADE, removing domains would require deleting just a single row.

I would like to share how you can simply remove a domain from the system with this simple function. CREATE OR REPLACE FUNCTION delete_domain(id UUID) RETURNS void AS $$ DECLARE r RECORD; BEGIN FOR r IN SELECT table_schema, table_name FROM information_schema.columns...

You can easily do it by modifying the park dialplan and adding a ${sip_from user} condition to check for the extensions and modifying the destination_number condition for the park extensions you want. Copy the dialplan and set it for every group of extensions.

Create a dialplan to set the area code <extension name="set-area-code" continue="true"> <condition field="${outbound_caller_id_number}" expression="^1?(\d{3})"> <action application="set" data="area_code=$1" inline="true"/> </condition> </extension> In the 7 digit gateway, use...

The contact string in callcenter can be any valid freeswitch dialstring. From the agent page in fusion, set the agent's contact field to something like {execute_on_ring='lua curl.lua'}user/100@domain.com or any other application you want to execute. You can read more about dialstrings and the...

uuid-standby is for agents to dial in and listen to music until there are callers in the queue that need to be bridged. You don't need this for loopback.

As I suspected, you don't have the call_direction=outbound set in your dialplan. I also don't see the user_record dialplan being parsed.

Callcenter agents get originated with the contact string set on the agent page agents, and they do not traverse the dialplan (unless you use loopback). You can set in the contact string execute_on_ring='curl https://your url'

@hamagid His issue is with outbound call recording, not inbound. @jimmygee2003 Can you post the freeswitch logs of the call?

You're probably missing a call_direction-outbound dialplan that matches your outbound route regex.

You probably didn't whitelist your provider's IP address in the ACL.

I didn't understand your second question.

You seem to have a typo in the SMS::SEND_MESSAGE event "sip_prifile" instead of "sip_profile"