On Sat, 2009-11-14 at 23:44 -0500, M. Ranganathan wrote: > Hi, > > I submitted some code to sipXcallController that includes a third > party call control capability where the controller stays in the > signaling path. I got to thinking that it would be interesting to have > XMPP based call transfer whereby one can @call for an ongoing chat to > set up a phone call (as we currently do) and then @xfer to another > party. This would be > enabled by sending a REST command to the third party call controller > to move one of the call legs of the ongoing call to another party. > Since the call controller is in line it can initiate the transfer ( > the REFER based one cannot since it is no longer in the signaling path > once it sets up the call). > > Does this seem a useful capability to add? Naturally one can also just > use the phone to do the transfer so I am not sure how useful this > might be. > > Any opinions?
Wouldn't this require sipXcallController to be a full b2bua? What call ids would it use for the two legs? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
