Thanks for your reply, the honest answer is it simply seemed like the best
way to do it.
Could you recommend another way to implement such features into my service,
I am using the ESL to do as much as possible but att_xfer seemed to cater for
most features I needed to implement.
This sort of call swapping is not implemented on the source code. I
was one of the guys that wanted this type of feature implemented on the core
instead of on the endpoint modules or endpoints itself and I have to say that
once you understand the code you understand why it is not supposed to be there.
I now advocate to completely remove the feature because it causes only headaches
and make you look for a solution in the wrong place.
So, to the real question, why are you using att_xfer? I am still waiting
for a valid use case.
Regards,
JM
_________________________________________________________________________
Professional
FreeSWITCH Consulting
Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered
IP PBX: The CudaTel Communication
Server
http://www.cudatel.com
Official FreeSWITCH
Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
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