Transfer is used to restart the dialplan processing with the data provided... Application=”transfer” data=”extension DIALPLAN context” where extension is the same as “destination_number” field for the dialplan conditions... The XML in your example refers to XML dialplan, this could be a different dialplan module such as ENUM... The context is the dialplan context ie: default or public in the example configs...
Bridge sends the call to an endpoint.. User/1001 is a special endpoint processor that translates via the user director to a bridge string of where that user is registered...
On 1/17/14 5:09 AM, "Fredrik Åhlén" <fredrik.h.ahlen@gmail.com> wrote:
Hi, I am playing around with my demo installation of FreeSwitch and have a question regarding dialplans and dialplan applications. I’ve looked in the wiki but I am not sure of the practical differens between the transfer and bridge application?
For example, you can “route” an inbound call to extension 1001 with both these configs:
1. <action application="transfer" data="1001 XML default"/>
2. <action application="bridge" data="user/1001"/>
Is the only diff that the transfer application executes the dialplan for the new extension but not in the bride case?
With Best Regards,
Fred
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
--
Ken
http://www.FreeSWITCH.org
http://www.ClueCon.com
http://www.OSTAG.org
irc.freenode.net #freeswitch
Twitter: @FreeSWITCH