If you're getting RECOVERY_ON_TIMER_EXPIRE then you have maybe a NAT
issue.
/b
On Jun 19, 2009, at 1:38 AM, Matthew Fong wrote:
the script is not part of a session or dial plan. :(
On Thu, Jun 18, 2009 at 11:31 PM, Jason White <[email protected]>
wrote:
Mathieu Rene <[email protected]> wrote:
> <action application="set"
> data="failure_causes=user_busy,recovery_on_timer_expire" /> and then
> originate it.
Or if you're originating from a script, set that as a channel
variable first.
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
