[Freeswitch-users] strange behaviour using group_confirm and originate_timeout

[Grant Bagdasarian]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140722/d56c6840/attachment.html