Hi Guillermo, Michael, Thanks for your responses. To give some more background, our specific use case is an incoming call (from user A) creates the outbound socket, then our app asks FreeSWITCH to originate a new call (between users B&C). User A then hangs up but the call between B&C will continue. When user A hangs up I still want to receive events from the newly originated (B->C) channel. Inbound mode sounds like it might be the way to go but I like the way outbound socket mode creates an individual socket per call - from my app's point of view it's nicely compartmentalised. Options I'm considering now are : 1) Use a single socket in inbound mode for all calls and rewrite my app accordingly 2) Keep using the socket dialplan application to establish an outbound socket, then have my app immediately park the call, close the outbound socket and establish an inbound socket and 'takeover' the call. This retains the advantage of individual sockets per call, but is rather clunky. Alternatively is there a way of marking the newly originated channel (B->C) as being a child of the original channel so that when the inbound A leg hangs up the socket stays in place? Any thoughts on the best way to go are much appreciated. Thanks, Sean.