Thanks, it's working fine now. I am still getting the error messages but it seems that everything ok I updated the wiki about bind_meta_app Anthony Minessale wrote:
ok update again.
I also changed the behavior of the bind app.
the app now can take one of "a" "b" or "ab" as the fist arg for who can dial the digit and one of "a" "b" "o" and "s" for the which leg executes it.
a and b are self-explanatory, "s" means "same" and "o" means opposite in cases where you use both a and b
On Mon, May 19, 2008 at 12:38 PM, Csaba Zelei <csaba.zelei@gmail.com <mailto:csaba.zelei@gmail.com>> wrote:
tested it. It's working now, thanks!
The only problem now is that if the att_xfer cant call the number (destination out of order, busy etc.) then it hang up instead of restore the original call. Also if I follow the A->B, B att_xfer C then C hang up thus restoring the original call and then A or B hang up I get the following messages on the console:
2008-05-19 19:20:27 [DEBUG] switch_ivr_bridge.c:917 switch_ivr_uuid_bridge() originator uuid d9ac3302-25c7-11dd-b544-c756451990a3 is not present 2008-05-19 19:20:27 [DEBUG] mod_dptools.c:1367 hanguphook() Hangup Command uuid_bridge(d9ac3302-25c7-11dd-b544-c756451990a3 d5d9e918-25c7-11dd-b544-c756451990a3): -ERR Invalid uuid
I also documented it to the wiki as I promised. (http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_att_xfer)
Thanks for your time!