/mcpconns[i].getTerminalConnections(); for(j = 0; j<termConns.length; j++) { if(termConns[j].getTerminal().getName.equals(termName) && termConns[i].getState() ! = TerminalConnection.PASSIVE) { return termConns[i].getConnection(); } } } } There is no common address for controllers in final and consult call, but the controller TerminalName is same for both the controller Addreses. So, application should rely on CommonTerminalName to find out the connections, terminal connections and controllers. Note Interface Changes See CiscoTransferStartEv, on page 665 Message Sequences See Direct Transfer Across Lines Use Cases, on page 1157 Backward Compatibility This feature is backward compatible. To provide backward compatibility for applications, a new permission to devices that allow connected transfer across lines has been added, along with a new standard role and a standard user group for this permission. Applications can control these devices only if this new role Standard Supports Connected Xfer/Conf is associated to the application user. Applications will be able to control these devices only if this new role "Standard CTI Allow Control of Phones supporting Connected Xfer/Conf" is associated to the application user. So, by default these devices are listed as restricted, assuming that the application uses JTAPI 7.1.2 or higher and only if application upgrades to handle this feature and associates the new permission can it control these devices. If the application uses an older JTAPI client the devices are not restricted but if the application tries to observe these devices (which supports this feature to be invoked manually), JTAPI throws an exception and marks these devices as restricted from there on. However, the application can invoke DirectTransfer Across Lines from existing JTAPI transfer() API on any type of phone and there is no restriction on this behavior as applications are expected to issue this request only if they support this feature. Also, a FarEnd point performing a Direct/Connected Transfer Across Lines is uncontrolled and can cause problems to applications. This means that JTAPI always reports events for Direct Transfer Across Lines for all the phones. Be aware that any old JTAPI application will not have any BWC issues if it is run in an environment where Direct Transfer Across Lines is not invoked (either on phones or through JTAPI API). However, applications changes are required if this this feature is used in such a setup. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 81 Features Supported by Cisco Unified JTAPI Event Flow Comparison and Sample Code