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,

João Mesquita
FreeSWITCH™ Solutions

On Wed, Jun 26, 2013 at 6:38 AM, Stuart Mills <stuart.mills3@btopenworld.com> wrote:

Hi all,

I have a question which is hopefully not too complicated.

I’m playing with mid call transfer features, I have an extension in features.conf to do the MCT which works fine, a_leg connects to the b_leg, then b_leg transfer to destination c_leg and can talk.

My question is this, is it then easy for b_leg to toggle the call between a_leg and c_leg, I take it it’s just another feature extension that bridges calls between the 2 legs, could it be that simple?

Kind Regards,

Stuart Mills

_________________________________________________________________________
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