Behavior of call_timeout during sequential bridge
Hello, I have a dialplan app (mod_xml_curl) that fetches a number of users from my DB and composes a brigde command that will try to contact each user in sequence. Each user should be attempted for at most 5 seconds and the total bridge attempt should not surpass 10 seconds. So my app generates something like this: <application app_name="set" app_data="call_timeout=10"/> <application app_name="bridge" app_data="[leg_timeout=5]sofia/internal/ user1@192.168.2.2|[leg_timeout=5]sofia/internal/user2@192.168.2.2 |[leg_timeout=5]sofia/internal/user3@192.168.2.2"/> However, in this case, call_timeout is ignored and the whole sequence of users will be attempted. Is there any way to enforce at timeout for the whole bridge operation when bridging sequentially? br, takeshi
Try putting the call_timeout=10 in the dialstring instead: <application app_name="bridge" app_data="{call_timeout=10}[leg_timeout=5]sofia/internal/user1@192.168.2.2|[leg_timeout=5]sofia/internal/user2@192.168.2.2|[leg_timeout=5]sofia/internal/user3@192.168.2.2"/> Alternatively you might try using export instead of set since you need the call_timeout to be on the other call leg. -MC On 11/2/10, mayamatakeshi <mayamatakeshi@gmail.com> wrote:
Hello, I have a dialplan app (mod_xml_curl) that fetches a number of users from my DB and composes a brigde command that will try to contact each user in sequence. Each user should be attempted for at most 5 seconds and the total bridge attempt should not surpass 10 seconds. So my app generates something like this:
<application app_name="set" app_data="call_timeout=10"/> <application app_name="bridge" app_data="[leg_timeout=5]sofia/internal/ user1@192.168.2.2|[leg_timeout=5]sofia/internal/user2@192.168.2.2 |[leg_timeout=5]sofia/internal/user3@192.168.2.2"/>
However, in this case, call_timeout is ignored and the whole sequence of users will be attempted. Is there any way to enforce at timeout for the whole bridge operation when bridging sequentially?
br, takeshi
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N] On Thu, Nov 4, 2010 at 1:25 PM, Michael Collins <msc@freeswitch.org> wrote:
Try putting the call_timeout=10 in the dialstring instead:
<application app_name="bridge" app_data="{call_timeout=10}[leg_timeout=5]sofia/internal/user1@192.168.2.2|[leg_timeout=5]sofia/internal/user2@192.168.2.2|[leg_timeout=5]sofia/internal/user3@192.168.2.2"/>
Alternatively you might try using export instead of set since you need the call_timeout to be on the other call leg.
-MC
On 11/2/10, mayamatakeshi <mayamatakeshi@gmail.com> wrote:
Hello, I have a dialplan app (mod_xml_curl) that fetches a number of users from my DB and composes a brigde command that will try to contact each user in sequence. Each user should be attempted for at most 5 seconds and the total bridge attempt should not surpass 10 seconds. So my app generates something like this:
<application app_name="set" app_data="call_timeout=10"/> <application app_name="bridge" app_data="[leg_timeout=5]sofia/internal/ user1@192.168.2.2|[leg_timeout=5]sofia/internal/user2@192.168.2.2 |[leg_timeout=5]sofia/internal/user3@192.168.2.2"/>
However, in this case, call_timeout is ignored and the whole sequence of users will be attempted. Is there any way to enforce at timeout for the whole bridge operation when bridging sequentially?
br, takeshi
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
On 11/4/10, Anthony Minessale <anthony.minessale@gmail.com> wrote:
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N]
Tony, thanks for the clarification. Also, note the typo: it is "origination_timeout". I will put this on the wiki channel variables page for future reference. -MC
D'oh! Thanks to Math. The correct var is "originate_timeout" and not "origination_timeout". It is now listed on the wiki: http://wiki.freeswitch.org/wiki/Variable_originate_timeout Thanks, MC On Thu, Nov 4, 2010 at 1:49 PM, Michael Collins <msc@freeswitch.org> wrote:
On 11/4/10, Anthony Minessale <anthony.minessale@gmail.com> wrote:
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N]
Tony, thanks for the clarification. Also, note the typo: it is "origination_timeout".
I will put this on the wiki channel variables page for future reference. -MC
I have tried <extension name="test"> <condition field="destination_number" expression="^111122223333$"> <action application="bridge" data="{originate_timeout=10}[leg_timeout=5]sofia/internal/user1@192.168.88.29:6666 |[leg_timeout=5]sofia/internal/user2@192.168.88.29:6666 |[leg_timeout=5]sofia/internal/user3@192.168.88.29:6666"/> </condition> </extension> But it doesn't work: total answer timeout is still the sum of leg_timeouts. I have also tried origination_timeout and setting call_timeout in the bridge data, but nothing works. On Fri, Nov 5, 2010 at 7:53 AM, Michael Collins <msc@freeswitch.org> wrote:
D'oh!
Thanks to Math. The correct var is "originate_timeout" and not "origination_timeout". It is now listed on the wiki:
http://wiki.freeswitch.org/wiki/Variable_originate_timeout
Thanks, MC
On Thu, Nov 4, 2010 at 1:49 PM, Michael Collins <msc@freeswitch.org>wrote:
On 11/4/10, Anthony Minessale <anthony.minessale@gmail.com> wrote:
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N]
Tony, thanks for the clarification. Also, note the typo: it is "origination_timeout".
I will put this on the wiki channel variables page for future reference. -MC
_______________________________________________ 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
Try setting: <action application="set" data="call_timeout=10"/> -Robert From: mayamatakeshi [mailto:mayamatakeshi@gmail.com] Sent: Friday, November 05, 2010 2:47 AM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Behavior of call_timeout during sequential bridge I have tried <extension name="test"> <condition field="destination_number" expression="^111122223333$"> <action application="bridge" data="{originate_timeout=10}[leg_timeout=5]sofia/internal/user1@192.168.88.29:6666|[leg_timeout=5]sofia/internal/user2@192.168.88.29:6666|[leg_timeout=5]sofia/internal/user3@192.168.88.29:6666<http://user3@192.168.88.29:6666>"/> </condition> </extension> But it doesn't work: total answer timeout is still the sum of leg_timeouts. I have also tried origination_timeout and setting call_timeout in the bridge data, but nothing works. On Fri, Nov 5, 2010 at 7:53 AM, Michael Collins <msc@freeswitch.org<mailto:msc@freeswitch.org>> wrote: D'oh! Thanks to Math. The correct var is "originate_timeout" and not "origination_timeout". It is now listed on the wiki: http://wiki.freeswitch.org/wiki/Variable_originate_timeout Thanks, MC On Thu, Nov 4, 2010 at 1:49 PM, Michael Collins <msc@freeswitch.org<mailto:msc@freeswitch.org>> wrote: On 11/4/10, Anthony Minessale <anthony.minessale@gmail.com<mailto:anthony.minessale@gmail.com>> wrote:
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N] Tony, thanks for the clarification. Also, note the typo: it is "origination_timeout".
I will put this on the wiki channel variables page for future reference. -MC _______________________________________________ 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
Yes, that was the first thing I tried. It doesn't work either. On Sat, Nov 6, 2010 at 12:52 AM, Robert Hadley <robert.hadley@teotech.com>wrote:
Try setting:
<action application="set" data="call_timeout=10"/>
-Robert
*From:* mayamatakeshi [mailto:mayamatakeshi@gmail.com] *Sent:* Friday, November 05, 2010 2:47 AM *To:* FreeSWITCH Users Help *Subject:* Re: [Freeswitch-users] Behavior of call_timeout during sequential bridge
I have tried
<extension name="test"> <condition field="destination_number" expression="^111122223333$"> <action application="bridge" data="{originate_timeout=10}[leg_timeout=5]sofia/internal/user1@192.168.88.29:6666 |[leg_timeout=5]sofia/internal/user2@192.168.88.29:6666 |[leg_timeout=5]sofia/internal/user3@192.168.88.29:6666"/> </condition> </extension>
But it doesn't work: total answer timeout is still the sum of leg_timeouts.
I have also tried origination_timeout and setting call_timeout in the bridge data, but nothing works.
On Fri, Nov 5, 2010 at 7:53 AM, Michael Collins <msc@freeswitch.org> wrote:
D'oh!
Thanks to Math. The correct var is "originate_timeout" and not "origination_timeout". It is now listed on the wiki:
http://wiki.freeswitch.org/wiki/Variable_originate_timeout
Thanks, MC
On Thu, Nov 4, 2010 at 1:49 PM, Michael Collins <msc@freeswitch.org> wrote:
On 11/4/10, Anthony Minessale <anthony.minessale@gmail.com> wrote:
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N]
Tony, thanks for the clarification. Also, note the typo: it is "origination_timeout".
I will put this on the wiki channel variables page for future reference. -MC
_______________________________________________ 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
_______________________________________________ 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 eventually solved this by trying to brigde to each user individually and in case of failure, transferring the call to an extension that recalculates the remaining time and tries the next user. br, takeshi On Fri, Nov 5, 2010 at 6:46 PM, mayamatakeshi <mayamatakeshi@gmail.com>wrote:
I have tried
<extension name="test"> <condition field="destination_number" expression="^111122223333$"> <action application="bridge" data="{originate_timeout=10}[leg_timeout=5]sofia/internal/user1@192.168.88.29:6666 |[leg_timeout=5]sofia/internal/user2@192.168.88.29:6666 |[leg_timeout=5]sofia/internal/user3@192.168.88.29:6666"/> </condition> </extension>
But it doesn't work: total answer timeout is still the sum of leg_timeouts.
I have also tried origination_timeout and setting call_timeout in the bridge data, but nothing works.
On Fri, Nov 5, 2010 at 7:53 AM, Michael Collins <msc@freeswitch.org>wrote:
D'oh!
Thanks to Math. The correct var is "originate_timeout" and not "origination_timeout". It is now listed on the wiki:
http://wiki.freeswitch.org/wiki/Variable_originate_timeout
Thanks, MC
On Thu, Nov 4, 2010 at 1:49 PM, Michael Collins <msc@freeswitch.org>wrote:
On 11/4/10, Anthony Minessale <anthony.minessale@gmail.com> wrote:
{origiation_timeout=10} is the global timeout despite any smaller timeouts which can be set per leg with [leg_timeout=N]
Tony, thanks for the clarification. Also, note the typo: it is "origination_timeout".
I will put this on the wiki channel variables page for future reference. -MC
_______________________________________________ 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
participants (4)
-
Anthony Minessale
-
mayamatakeshi
-
Michael Collins
-
Robert Hadley