Well, I would randomly insert all of those cases to make it more realistic... only thing I cannot manage to issue USER_BUSY from lua (and neither from the dialplan, actually). 

<anti-action application="respond" data="407" /> (407 or 486 or whatever...)

doesn't behave as I expected and neither

<action application="hangup" data="407" /> (407 or 486 or USER_BUSY or whatever...)

and I cannot find a a session:reject(<hangupcause>) method in lua.

Can you give me a hint? 

On Thu, Aug 6, 2009 at 01:23, Brian West <brian@freeswitch.org> wrote:
The bigger problem is some end points won't hang up the call in a consistent manner... some phones say user_rejected or user_busy when you reject the call with the reject button.

/b

On Aug 5, 2009, at 5:16 PM, Michael Collins wrote:



On Wed, Aug 5, 2009 at 3:54 PM, Raffaele P. Guidi <raffaele.p.guidi@gmail.com> wrote:
interesting! what values can contain "variable_originate_disposition"? And can I set them manually in a script to reject a call simulating user busy or call rejected? A lua example?

Thanks,
   Raffaele

Start here:
http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_hangup

And note the link to the hangup causes. As far as Lua, I'm not sure there's a good reason to do it there. Could you give us pseudo code example of what you're thinking of doing?
-MC



_______________________________________________
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