/mcpset), the CTI RD processes the call first and then offers the call to the RDP. If the application is not active, the RDP processes the call first and does not offer the call to the CTI RD. When only the CTI RD is configured for a user, the existing "Cisco Extend and Connect" feature behavior with remote destinations remains unchanged. When only RDP is configured for a user, there is no application support because the devices are not controllable from a CTI. Interface Changes There are no interface changes for this feature. Use Cases There are no new use cases for this feature. (Add/Update/Delete Remote Destination) are added for CTIRD, and are applicable (without any change from App/User). Backward Compatibility There are no backward compatibility issues for this feature. Call Forwarding Starting with Unified Communications Manager 10.0(1), a new feature called “CTI Rd Call Forward” allows users to control when incoming calls are forwarded to all configured Remote Destinations on the CTI Remote Device, when no active remote destination is set. A new check box, Route calls to all remote destinations when client is not connected, is added to the Unified Communications Manager device window. The check box determines whether calls are routed to all remote destinations when Active Remote Destination is not set. When you enable the Route calls to all remote destinations when client is not connected check box, and Active Remote Destination is not set, the call is routed to all remote destinations. If this check box is disabled, and Active Remote Destination is not set, the call is disconnected with User_Busy error on the CTI Remote Device. In scenarios where Active Remote Destination is set, the call is always routed to the Active Remote Destination regardless of whether the Route calls to all remote destinations when client is not connected check box is enabled or disabled. Interface Changes There are no interface changes for this feature. Message Sequence See CTI RD Call Forwarding, on page 639. Backward Compatibility There are no backward-compatibility issues for this feature. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 48 Features Supported by TSP Call Forwarding