You could also export it instead so it executes on the bleg not the aleg. That should work regardless of whether you have the aleg answered already or not.

I'd personally prefer not answering the aleg unless you need to - most systems start billing from time answered. So the caller'll get charged for ringing time even if the call isn't answered.

Not sure what would cause the 3s difference. If anything there should be a small delay on answer before executing sched_hangup - I could understand 61s much more than 57s.

-Steve





On 16 October 2013 08:29, Samir Doshi <smrdoshi@gmail.com> wrote:
That works. Thanks

However I notice one thing, If I set 60 seconds sched time then my call hang
up at 57 seconds. I tried many times and all the time it hangup at 57
seconds. Not sure if that's something related to fs. Any thoughts?



-----
Thanks,
Samir
--
View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Call-hangup-not-working-in-perl-session-tp7595714p7595737.html
Sent from the freeswitch-users mailing list archive at Nabble.com.

_________________________________________________________________________
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