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
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,
MCOn 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:Tony, thanks for the clarification. Also, note the typo: it is
> {origiation_timeout=10} is the global timeout despite any smaller
> timeouts which can be set per leg with [leg_timeout=N]
"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