[Freeswitch-users] strange behaviour using group_confirm and originate_timeout

[Grant Bagdasarian]

Yes!!!
That did the trick. I removed the global originate_timeout and set the leg_timeout for each leg enclosed in [ ].

Thank you Michael!

From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Michael Collins
Sent: Wednesday, July 23, 2014 11:22 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] strange behaviour using group_confirm and originate_timeout

What about this?
https://wiki.freeswitch.org/wiki/Channel_Variables#group_confirm_cancel_timeout
It implies you need to use leg_timeout on each leg vs. originate_timeout globally but you could test and verify and then let the doc team know for sure. ;)
-MC


On Tue, Jul 22, 2014 at 7:54 AM, Grant Bagdasarian <GB at cm.nl<mailto:GB at cm.nl>> wrote:
Hello,

I’m using the enterprise originate to ring multiple destinations after the a leg has answered.
These are the global parameters: <ignore_early_media=true,monitor_early_media_fail=user_busy:2:480+620!destination_out_of_order:2:1776.7,originate_continue_on_timeout=true,originate_timeout=15>

Notice the originate_timeout has been set to 15.

When one of the ringing destinations answers the call, group_confirm is used to have them complete a script in order to get connected.

session.execute("export", "group_confirm_key=exec");
session.execute("export", "group_confirm_file=javascript /usr/src/freeswitch/conf/scripts/confirm.js);

When the confirm script is being executed, a file is being played and some digits need to be collected. Using play_and_get_digits. Audio file is about 12 seconds.
But as soon as the 15 seconds timeout is hit which was set before, the destination is disconnected.

What do I need to set in order for freeswitch to know the destination has answered, so it leaves that answered destination alone and does not enforce the originate_timeout?
I’d expect the originate_timeout to be the time from starting to ring a destination till it has answered. Not continue enforcing it once the destination has been answered.
Then again, group_confirm is required to be completed in order for freeswitch to mark the call as accepted, so this behavior might make sense.

It comes down to the destinations being called not having enough time to complete the script because the originate_timeout is set to 15 seconds.
Changing it to 25 gives them more time, but 15 seconds is the requirement for this application.

Any ideas? because I’m lost..

Grant

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting at freeswitch.org<mailto:consulting at freeswitch.org>
http://www.freeswitchsolutions.com




Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org<mailto:FreeSWITCH-users at lists.freeswitch.org>
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140724/c7cb92cd/attachment.html