do you mean bridge_answer_timeout?<br><br>if you see the wiki, that variable only pertains to bridged calls in early_media state.<br><br>you probably want:<br><br><a href="http://wiki.freeswitch.org/wiki/Channel_Variables#originate_timeout">http://wiki.freeswitch.org/wiki/Channel_Variables#originate_timeout</a><br>
<br><br><br><div class="gmail_quote">On Tue, Mar 2, 2010 at 12:47 PM, Mark Sobkow <span dir="ltr"><<a href="mailto:m.sobkow@marketelsystems.com">m.sobkow@marketelsystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I tried changing the answer timeout to 2 seconds, but Freeswitch<br>
"originate" is definitely not honouring that request. The originate<br>
command is:<br>
<br>
originate, sofia/external/533@rats.marketel '&erlang( pbx_called_cust<br>
pursuit@testsrv )' 5<br>
<div><div></div><div class="h5"><br>
Mark Sobkow wrote:<br>
> Never mind. What's actually happening is now that I've got the Erlang<br>
> events firing, the timeout on the originate command doesn't seem to be<br>
> working. I had a timeout of 5 seconds set, but Freeswitch kept<br>
> ringing until our voice mail system answered my phone (30 seconds.)<br>
><br>
> *sigh*<br>
><br>
> Not that it's any better a result, as we DO need to timeout calls that<br>
> aren't being answered.<br>
><br>
> Mark Sobkow wrote:<br>
>> I think I may have found a bug in Freeswitch, as both answered and<br>
>> ringing calls have an "Answer-State" "answered" and<br>
>> variable_endpoint_disposition ANSWER, though in one case the call has<br>
>> NOT been answered.<br>
>><br>
>> For a normally answered call, the following Freeswitch events are<br>
>> propagated to Erlang:<br>
>><br>
>> CHANNEL_DATA<br>
>> CHANNEL_PARK<br>
>> CHANNEL_HANGUP<br>
>> CHANNEL_UNPARK<br>
>> CHANNEL_EXECUTE_COMPLETE<br>
>> CHANNEL_STATE<br>
>> CHANNEL_HANGUP_COMPLETE<br>
>> CHANNEL_STATE<br>
>> CHANNEL_DESTROY<br>
>> CHANNEL_STATE<br>
>><br>
>> For an unanswered call, the events are:<br>
>><br>
>> CHANNEL_DATA<br>
>> CHANNEL_EXECUTE<br>
>> CHANNEL_PARK<br>
>> CHANNEL_HANGUP<br>
>> CHANNEL_UNPARK<br>
>> CHANNEL_EXECUTE_COMPLETE<br>
>> CHANNEL_STATE<br>
>> CHANNEL_HANGUP_COMPLETE<br>
>> CHANNEL_STATE<br>
>> CHANNEL_DESTROY<br>
>> CHANNEL_STATE<br>
>><br>
>> This is going to make the call processing a little complex, as both<br>
>> variants produce a CHANNEL_PARK early in the call processing, and<br>
>> later produce the HANGUP event.<br>
>><br>
>> The problem is that with an answered call, I have to uuid_bridge the<br>
>> operator on the CHANNEL_PARK event within 2 seconds to meet legal<br>
>> requirements, while with an unanswered call it's another 30 seconds<br>
>> (configurable) before the CHANNEL_HANGUP event propagates to let me<br>
>> know that the call went unanswered.<br>
>><br>
><br>
><br>
<br>
<br>
--<br>
Mark Sobkow<br>
Senior Developer<br>
MarkeTel Multi-Line Dialing Systems LTD.<br>
428 Victoria Ave<br>
Regina, SK S4N-0P6<br>
Toll-Free: 800-289-8616-X533<br>
Local: 306-359-6893-X533<br>
Fax: 306-359-6879<br>
Email: <a href="mailto:m.sobkow@marketelsystems.com">m.sobkow@marketelsystems.com</a><br>
Web: <a href="http://www.marketelsystems.com" target="_blank">http://www.marketelsystems.com</a><br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:+19193869900<br>