Re: [Freeswitch-dev] Bug with variable_endpoint_disposition and Answer-State event parameters

[Mark Sobkow]

Thanks, Andrew.  That was the ticket -- specifying the timeout at the end of the originate command doesn't work.  But the following works and causes the originate command to return an error status instead of a UUID, which is what I _originally_ wanted it to do! The working syntax is below.  Note that if the call goes unanswered the Erlang event callback does _not_ fire. originate {call_timeout=2,originate_timeout=2}sofia/external/5...@rats.marketel '&erlang( pbx_called_cust purs...@testsrv )' Andrew Thompson wrote: On Tue, Mar 02, 2010 at 12:39:18PM -0600, Mark Sobkow wrote: Never mind. What's actually happening is now that I've got the Erlang events firing, the timeout on the originate command doesn't seem to be working. I had a timeout of 5 seconds set, but Freeswitch kept ringing until our voice mail system answered my phone (30 seconds.) *sigh* Not that it's any better a result, as we DO need to timeout calls that aren't being answered. Which timeout variable(s) are you setting, there are several and they have different effects. See http://wiki.freeswitch.org/wiki/Channel_Variables for at least a partial list. Andrew -- Mark Sobkow Senior Developer MarkeTel Multi-Line Dialing Systems LTD. 428 Victoria Ave Regina, SK S4N-0P6 Toll-Free: 800-289-8616-X533 Local: 306-359-6893-X533 Fax: 306-359-6879 Email: m.sob...@marketelsystems.com Web: http://www.marketelsystems.com

_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org