Dialplan Tools: bridge - pipe vs. :_:
Hello, What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command? They both seem to do sequential calling. Regards, Ali Pey
See: http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate Enterprise originate The so called 'enterprise originate' syntax is a way to simultaneously originate multiple calls in several threads (regular simultaneous originate is single threaded). To use it simply separate valid dial strings by :_: . Each dial string can have its own {} and [] blocks and can themselves be simultaneous or sequential (containing ',' or '|') as above. To add channel variables to the entire enterprise originate use <> blocks: originate <all_threads=true>{first_thread=true}sofia/gw/foo/bar:_:{second_thread=true}sofia/gw/foo/baz This can be helpful when dealing with call forwarding. Without it, FreeSWITCH™ would drop the simultaneous dial and transfer to the forwarded extension. For example, I'm bridging to two SIP phones, 101 and 102, with "," between them. 101 redirects to some other URL. 102 will now stop ringing. With :_: it wouldn't. By default each new thread is it's own A-leg in the CDRs. You can access the variable ent_originate_aleg_uuid to put the call back together. -Avi On Wed, Nov 20, 2013 at 12:03 AM, Ali Pey <alipey@gmail.com> wrote:
Hello,
What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command?
They both seem to do sequential calling.
Regards, Ali Pey
_________________________________________________________________________ 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
Hello Avi, As you can tell from the subject line and my one line question, I was asking about the "bridge" command and not originate. Also, I wasn't asking what it does. My question was "the difference" between pipe | and :_:? Thank you for responding though. Regards, Ali Pey On Tue, Nov 19, 2013 at 11:40 PM, Avi Marcus <avi@avimarcus.net> wrote:
See: http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate
Enterprise originate
The so called 'enterprise originate' syntax is a way to simultaneously originate multiple calls in several threads (regular simultaneous originate is single threaded). To use it simply separate valid dial strings by :_: . Each dial string can have its own {} and [] blocks and can themselves be simultaneous or sequential (containing ',' or '|') as above. To add channel variables to the entire enterprise originate use <> blocks:
originate <all_threads=true>{first_thread=true}sofia/gw/foo/bar:_:{second_thread=true}sofia/gw/foo/baz
This can be helpful when dealing with call forwarding. Without it, FreeSWITCH™ would drop the simultaneous dial and transfer to the forwarded extension.
For example, I'm bridging to two SIP phones, 101 and 102, with "," between them. 101 redirects to some other URL. 102 will now stop ringing. With :_: it wouldn't.
By default each new thread is it's own A-leg in the CDRs. You can access the variable ent_originate_aleg_uuid to put the call back together.
-Avi
On Wed, Nov 20, 2013 at 12:03 AM, Ali Pey <alipey@gmail.com> wrote:
Hello,
What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command?
They both seem to do sequential calling.
Regards, Ali Pey
_________________________________________________________________________ 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
_________________________________________________________________________ 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
Bridge uses originate underneath.
On Nov 20, 2013, at 8:36 AM, Ali Pey <alipey@gmail.com> wrote:
Hello Avi,
As you can tell from the subject line and my one line question, I was asking about the "bridge" command and not originate.
Also, I wasn't asking what it does. My question was "the difference" between pipe | and :_:?
Thank you for responding though.
Regards, Ali Pey
On Tue, Nov 19, 2013 at 11:40 PM, Avi Marcus <avi@avimarcus.net> wrote: See: http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate
Enterprise originate The so called 'enterprise originate' syntax is a way to simultaneously originate multiple calls in several threads (regular simultaneous originate is single threaded). To use it simply separate valid dial strings by :_: . Each dial string can have its own {} and [] blocks and can themselves be simultaneous or sequential (containing ',' or '|') as above. To add channel variables to the entire enterprise originate use <> blocks: originate <all_threads=true>{first_thread=true}sofia/gw/foo/bar:_:{second_thread=true}sofia/gw/foo/baz This can be helpful when dealing with call forwarding. Without it, FreeSWITCH™ would drop the simultaneous dial and transfer to the forwarded extension. For example, I'm bridging to two SIP phones, 101 and 102, with "," between them. 101 redirects to some other URL. 102 will now stop ringing. With :_: it wouldn't. By default each new thread is it's own A-leg in the CDRs. You can access the variable ent_originate_aleg_uuid to put the call back together.
-Avi
On Wed, Nov 20, 2013 at 12:03 AM, Ali Pey <alipey@gmail.com> wrote: Hello,
What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command?
They both seem to do sequential calling.
Regards, Ali Pey
_________________________________________________________________________ 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
_________________________________________________________________________ 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
_________________________________________________________________________ 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
I read your message, and referred you to the wiki page that discusses it. It's called enterprise originate. It is actually also mentioned on the bridge page, http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_bridge#Calling_multiple... However it isn't explained much. It's parallel dialing (like a ,) but in it's own thread, which I think is necessary for user/ endpoints. The | is for failover which only dials the second if the first one fails. We need a better wiki entry on these 3.. -Avi On Wed, Nov 20, 2013 at 3:36 PM, Ali Pey <alipey@gmail.com> wrote:
Hello Avi,
As you can tell from the subject line and my one line question, I was asking about the "bridge" command and not originate.
Also, I wasn't asking what it does. My question was "the difference" between pipe | and :_:?
Thank you for responding though.
Regards, Ali Pey
On Tue, Nov 19, 2013 at 11:40 PM, Avi Marcus <avi@avimarcus.net> wrote:
See: http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate
Enterprise originate
The so called 'enterprise originate' syntax is a way to simultaneously originate multiple calls in several threads (regular simultaneous originate is single threaded). To use it simply separate valid dial strings by :_: . Each dial string can have its own {} and [] blocks and can themselves be simultaneous or sequential (containing ',' or '|') as above. To add channel variables to the entire enterprise originate use <> blocks:
originate <all_threads=true>{first_thread=true}sofia/gw/foo/bar:_:{second_thread=true}sofia/gw/foo/baz
This can be helpful when dealing with call forwarding. Without it, FreeSWITCH™ would drop the simultaneous dial and transfer to the forwarded extension.
For example, I'm bridging to two SIP phones, 101 and 102, with "," between them. 101 redirects to some other URL. 102 will now stop ringing. With :_: it wouldn't.
By default each new thread is it's own A-leg in the CDRs. You can access the variable ent_originate_aleg_uuid to put the call back together.
-Avi
On Wed, Nov 20, 2013 at 12:03 AM, Ali Pey <alipey@gmail.com> wrote:
Hello,
What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command?
They both seem to do sequential calling.
Regards, Ali Pey
_________________________________________________________________________ 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
_________________________________________________________________________ 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
_________________________________________________________________________ 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
Great. Thanks. I also had read the wiki but I couldn't understand when you would use :_: It seems ',' and :_: do parallel dialing, when would you use one vs. the other? Regards, Ali On Wed, Nov 20, 2013 at 9:13 AM, Avi Marcus <avi@avimarcus.net> wrote:
I read your message, and referred you to the wiki page that discusses it.
It's called enterprise originate. It is actually also mentioned on the bridge page, http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_bridge#Calling_multiple...
However it isn't explained much. It's parallel dialing (like a ,) but in it's own thread, which I think is necessary for user/ endpoints. The | is for failover which only dials the second if the first one fails. We need a better wiki entry on these 3..
-Avi
On Wed, Nov 20, 2013 at 3:36 PM, Ali Pey <alipey@gmail.com> wrote:
Hello Avi,
As you can tell from the subject line and my one line question, I was asking about the "bridge" command and not originate.
Also, I wasn't asking what it does. My question was "the difference" between pipe | and :_:?
Thank you for responding though.
Regards, Ali Pey
On Tue, Nov 19, 2013 at 11:40 PM, Avi Marcus <avi@avimarcus.net> wrote:
See: http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate
Enterprise originate
The so called 'enterprise originate' syntax is a way to simultaneously originate multiple calls in several threads (regular simultaneous originate is single threaded). To use it simply separate valid dial strings by :_: . Each dial string can have its own {} and [] blocks and can themselves be simultaneous or sequential (containing ',' or '|') as above. To add channel variables to the entire enterprise originate use <> blocks:
originate <all_threads=true>{first_thread=true}sofia/gw/foo/bar:_:{second_thread=true}sofia/gw/foo/baz
This can be helpful when dealing with call forwarding. Without it, FreeSWITCH™ would drop the simultaneous dial and transfer to the forwarded extension.
For example, I'm bridging to two SIP phones, 101 and 102, with "," between them. 101 redirects to some other URL. 102 will now stop ringing. With :_: it wouldn't.
By default each new thread is it's own A-leg in the CDRs. You can access the variable ent_originate_aleg_uuid to put the call back together.
-Avi
On Wed, Nov 20, 2013 at 12:03 AM, Ali Pey <alipey@gmail.com> wrote:
Hello,
What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command?
They both seem to do sequential calling.
Regards, Ali Pey
_________________________________________________________________________ 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
_________________________________________________________________________ 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
_________________________________________________________________________ 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
_________________________________________________________________________ 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
Hello Ali, as far as I know, if you dial multiple endpoints (e.g. 200|201|202) and e.g. 202 has 2 registerered phones, then only one of the 202-phones will ring. If you bridge with :_: all phones for 202 will ring. That's what we experienced for a while. Best regards Peter On 11/20/13 15:23, Ali Pey wrote:
Great. Thanks.
I also had read the wiki but I couldn't understand when you would use :_:
It seems ',' and :_: do parallel dialing, when would you use one vs. the other?
Regards, Ali
On Wed, Nov 20, 2013 at 9:13 AM, Avi Marcus <avi@avimarcus.net <mailto:avi@avimarcus.net>> wrote:
I read your message, and referred you to the wiki page that discusses it.
It's called enterprise originate. It is actually also mentioned on the bridge page, http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_bridge#Calling_multiple...
However it isn't explained much. It's parallel dialing (like a ,) but in it's own thread, which I think is necessary for user/ endpoints. The | is for failover which only dials the second if the first one fails. We need a better wiki entry on these 3..
-Avi
On Wed, Nov 20, 2013 at 3:36 PM, Ali Pey <alipey@gmail.com <mailto:alipey@gmail.com>> wrote:
Hello Avi,
As you can tell from the subject line and my one line question, I was asking about the "bridge" command and not originate.
Also, I wasn't asking what it does. My question was "the difference" between pipe | and :_:?
Thank you for responding though.
Regards, Ali Pey
On Tue, Nov 19, 2013 at 11:40 PM, Avi Marcus <avi@avimarcus.net <mailto:avi@avimarcus.net>> wrote:
See: http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate
Enterprise originate
The so called 'enterprise originate' syntax is a way to simultaneously originate multiple calls in several threads (regular simultaneous originate is single threaded). To use it simply separate valid dial strings by :_: . Each dial string can have its own {} and [] blocks and can themselves be simultaneous or sequential (containing ',' or '|') as above. To add channel variables to the entire enterprise originate use <> blocks:
originate <all_threads=true>{first_thread=true}sofia/gw/foo/bar:_:{second_thread=true}sofia/gw/foo/baz
This can be helpful when dealing with call forwarding. Without it, FreeSWITCH^(TM) would drop the simultaneous dial and transfer to the forwarded extension.
For example, I'm bridging to two SIP phones, 101 and 102, with "," between them. 101 redirects to some other URL. 102 will now stop ringing. With :_: it wouldn't.
By default each new thread is it's own A-leg in the CDRs. You can access the variable ent_originate_aleg_uuid to put the call back together.
-Avi
On Wed, Nov 20, 2013 at 12:03 AM, Ali Pey <alipey@gmail.com <mailto:alipey@gmail.com>> wrote:
Hello,
What's the difference between pipe '|' and :_: in a multiple sequential bridge destinations command?
They both seem to do sequential calling.
Regards, Ali Pey
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto: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 <mailto: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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto: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 <mailto: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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto: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 <mailto: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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto: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 <mailto: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
_________________________________________________________________________ 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
-- With kind regards Peter Steinbach Telefaks Services GmbH mailto:lists (att) telefaks.de Internet: www.telefaks.de
participants (4)
-
Ali Pey
-
Avi Marcus
-
cmrienzo＠gmail.com
-
Peter Steinbach