/mcpInteraction Feature For direct calls to remote destinations that are anchored to the enterprise number, mobile users can use the session handoff feature to hand off the call to their deskphones. You must enable Cisco Unified Mobility before you implement intelligent session control. Intelligent Session Control and Session Handoff Cisco Unified Mobility is included in all user-based licenses from basic to professional. Licensing For single number reach calls to a remote destination, the device pool of the originating calling party determines the selection of the standard local route group. Note Local Route Group is not supported when the AgentGreeting with BiB (Built in Bridge) is invoked. Local Route Groups Each remote destination supports a maximum of six active calls. However, the number of supported calls depends on the Unified Communications Manager configuration. For example, the Cisco Unified Mobility user receives a call while the user already has six calls for the remote destination or while the user is using DTMF to transfer or conference a call from the remote destination. The received call is sent to the enterprise voice mail when: • The number of calls with user exceeds Busy trigger configuration • CFB is configured • All shared lines are busy Note The calls sent to the enterprise voice mail is not based on the maximum supported calls. Number of Supported Calls Cisco Unified Mobility supports the Cisco Unified Mobility feature without midcall features over SIP trunks with Cisco Unified Border Element (CUBE). SIP Trunks with Cisco Unified Border Element Cisco Unified Mobility Restrictions Table 4: Cisco Unified Mobility Interactions Description Restriction A remote destination call does not work when auto answer is enabled. Note Auto Answer is not supported with Dual-Mode phones. Auto Answer Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 38 Remote Worker Features Cisco Unified Mobility Restrictions