Search results

In voicemail there is a option to forward the voicemails to other extensions

You can also use toll allow to limit which extension uses which route

have you tried creating a extension in fusion and use it as a gateway with registration in freepbx?

If I remember correctly the default is us-ring. you can look at the freeswitch logs as to why the calls are not working when setting uk-ring.

You added new variables (ringback and transfer_ringback) under defaults section in variables or you changed the existing ones from $${us-ring} to $${uk-ring}?

You have to assign the newly created menu to the domain. You can change the menu setting in default settings under domain for all domains, or you can add this setting to the domain you would like to change the menu for in domain settings.

It's set in /usr/share/freeswitch/scripts/confirm.lua You can set it there to another audio file, or you can set it to a variable that you'll be able to set to a different audio file per domain.

Is it calls that are being answered on the extension that's set to call record all? If the inbound call is only reaching IVR etc and you want it to be recorded, you have to set it in destinations.

How about creating 2 rows, 1 for inbound and 1 for outbound? This is how it's with ring groups and follow me.

In ring group 5510, If you scroll down and set "Call Forward" to true, the call forward rule on ext 6000 will work.

You can set call forward to true in the ring group.

is it possible to play the IVR option selected, to the callee before connecting the call? Let's say the caller selects option 5 from the IVR, it's transferred to an extension, when the extension picks up the phone it should play "option 5 selected" (only for the callee, not for the caller) and...

In IVR when direct dialing an extension, there is an announcement "Your call is being transferred" before starting to ring, using the dial plan please_hold. When selecting an option (for example 1) that transfers to an extension, there is no announcement. Is there a way to have the...

In default settings cdr category there is a setting is to save b_leg to CDR, options are inbound, outbound and local. No matter what I'm enabling or disabling, all the b_leg's are saved to the database.

Have you deleted the JSON field in the database?

By default, when there is a incoming call and the call is forwarded to another outside number, fusion will combine both legs of the call into 1 CDR record and the direction will be outbound even though it is originally a inbound call, because this was applied later, at the stage when the call...

You can do a separate ring group for every option in the IVR and in the ring group you can provide the IVR selection as CID name prefix

There are a few threads about converting call recording and it seems that everyone took the route of converting them overnight as to not put load on the system when there are calls, but what happens when you have few thousand recordings a day, which uses enormous resources to convert at once, is...

Adding those to the call_direction-outbound, will only set the $call_direction to "outbound", it won't actually route your calls. You can add those conditions in the same way to your outbound route dialplan, so the outbound route will catch all of those dialed scenarios and route them the same...

You can have all your outbound routes regex conditions in one call_direction-outbound condition. <condition field="destination_number" expression="^(\d{7})$" break="on-true"> <action application="export" data="call_direction=outbound" inline="true"/> </condition> <condition...