Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified Mobility

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_cisco-unified-mobility-1251.html

Published

unknown

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• An access list is applied in the remote destination's ring schedule area by choosing either 'Ring this destination only if caller is in' or 'Do not ring this destination if caller is in' and selecting the list. in context
• Access list members are defined with a Filter Mask of Not Available, Private or Directory Number, and a Directory Number filter takes a DN Mask. in context
• Access lists for Unified Mobility are configured at Call Routing > Class of Control > Access List and are tied to a user through the Owner drop-down. in context
• An access list is either Allowed, where all numbers in the list are allowed, or Blocked, where all numbers in the list are blocked. in context
• A remote destination call does not work when auto answer is enabled. in context
• Call Forward Unregistered is not supported and does not work when a remote destination is configured, or when a Mobility Identity has a mobile number with Single Number Reach enabled. in context
• Cisco states that its mobility solution is verified only with Cisco equipment. in context
• The default Maximum Wait Time for Desk Pickup is 10 seconds. in context
• Maximum Wait Time for Desk Pickup, set in milliseconds on the end user, is the time after hanging up a call from a remote destination during which the user can still resume it from the desk phone. in context
• If Do Not Disturb is enabled on the desk phone, a direct call to the remote destination is not anchored and the desk phone cannot be placed in the remote In use state. in context
• A Jabber dual-mode device is added at Device > Phone as Cisco Dual Mode for Android or Cisco Dual Mode for iPhone with Device Name, Device Pool, Softkey Template, Owner User ID, Mobility User ID, Device Security Profile and SIP Profile, and then a directory number is associated. in context
• The default Enterprise Feature Access DTMF codes are Hold *81, Exclusive Hold *82, Resume *83, Transfer *84, Conference *85, Session Handoff *74, Start Selective Recording *86 and Stop Selective Recording *87, editable under Clusterwide Parameters (System - Mobility). in context
• The Enterprise Feature Access number is configured at Call Routing > Mobility > Enterprise Feature Access Number Configuration with a unique DID Number, a Route Partition and an optional Default Enterprise Feature Access Number checkbox. in context
• Enterprise features used from cellular networks require out-of-band DTMF. in context
• Enterprise Feature Access also requires the Cisco CallManager service parameter Enable Enterprise Feature Access to be set to True. in context
• If Mobility is disabled in the Feature Control Policy that phones use, the Mobility softkey is disabled on those phones; it is enabled at Device > Device Settings > Feature Control Policy with Override Default and Enable Setting checked. in context
• Cisco Unified Mobility features are not supported for T1 CAS, FXO, FXS and BRI. in context
• The handoff number for Wi-Fi to mobile network handoff is a DID set at Call Routing > Mobility > Handoff Configuration with its Route Partition, and a number starting with + must be entered with a preceding backslash. in context
• Intelligent Session Control does not support direct URI dialing. in context
• Intelligent Session Control is enabled by setting the Cisco CallManager service parameter Reroute Remote Destination Calls to Enterprise Number to True; Ring All Shared Lines and Ignore Call Forward All on Enterprise DN (default True) sit under the same heading. in context
• When first configured, Jabber devices count as registered devices toward the node's Maximum Number of Registered Devices service parameter. in context
• The Cisco Jabber dual-mode task flow is: configure a Mobility Profile, add a dual-mode device for Cisco Jabber, configure a Mobility Identity, and configure the Handoff number. in context
• Cisco Unified Mobility is included in all Unified CM user-based licenses from basic to professional. in context
• For Single Number Reach calls to a remote destination, the originating caller's device pool selects the standard local route group. in context
• To find which Cisco IP Phones support the Mobility softkey, Cisco directs administrators to generate a phone feature list report for the Mobility feature. in context
• A Mobility Identity, added from the dual-mode device with Add New Mobility Identity, holds the device's mobile number as Destination and the Mobility Profile, and checking Enable Single Number Reach lets the device be reached on the enterprise number. in context
• A Mobility Profile is created at Call Routing > Mobility > Mobility Profile, choosing Dial via Office Reverse as the Mobile Client Calling Option and setting the Callback Caller ID for Dial-via-Office Reverse. in context
• Checking Enable Move to Mobile on a remote destination includes it in the Mobility softkey list, letting the user transfer an active desk phone call to that mobile device. in context
• Mobile Voice Access requires the Interactive Voice Response service to be active and included in a Media Resource Group List. in context
• A cluster on 15SU4 or later that wants Mobile Voice Access has to use the native, IVR-based method, so it needs the IVR media resource in the users' media resource group list rather than a VXML gateway. inferred in context
• Mobile Voice Access is enabled on the publisher's Cisco CallManager service parameters by setting Enable Mobile Voice Access to True and entering the Mobile Voice Access Number users dial, then restarting the Cisco CallManager service. in context
• From Release 15SU4, Unified CM does not support Mobile Voice Access via H.323 and SIP VoiceXML (VXML) gateways, and the Cisco Unified Mobile Voice Access Service is deprecated. in context
• To configure an IP phone for mobility, at Device > Phone select the mobility softkey template, set the Owner User ID to the mobility-enabled user, optionally apply the Feature Control Policy, and save. in context
• Cisco states that enabling Mobility features requires planning so that the dial plan and call routing configuration can handle the deployment. in context
• Mobile Voice Access is not available while the publisher node is unreachable, and Single Number Reach cannot be toggled then either. in context
• A remote destination is added at Device > Remote Destination by entering the Destination number, choosing the Mobility User ID, checking Enable Unified Mobility features, selecting the Remote Destination Profile and the Single Number Reach Voicemail Policy, and checking Enable Single Number Reach. in context
• A Remote Destination Profile is created at Device > Device Profile > Remote Destination Profile with a Name, User ID and Device Pool, and the desk phone directory number is associated to it with Add a New DN. in context
• The end user's Remote Destination Limit field sets how many remote destinations the user may have as Single Number Reach targets. in context
• A remote destination's ring schedule can be All the time or a specified schedule, and a time zone is set when a schedule is used. in context
• Mobility service parameters are under System > Service Parameters > Cisco CallManager in the headings Clusterwide Parameters (System - Mobility), (System - Mobility Single Number Reach Voicemail) and (Feature - Reroute Remote Destination Calls to Enterprise Number). in context
• Each remote destination supports a maximum of six active calls. in context
• Single Number Reach gives the user one enterprise number and voicemail at which callers reach the desk phone or any configured remote destination. in context
• When a hunt group points at directory numbers that have Single Number Reach enabled, the call does not extend to the SNR remote destinations unless all devices in the hunt group are logged in. in context
• The Mobility softkey is added to a softkey template at Device > Device Settings > Softkey Template using Configure Softkey Layout, and it is enabled on all phones that use that template. in context
• The Release 15 Unified Mobility task flow runs: configure mobility users, configure mobility for IP phones, Mobile Voice Access (optional), Enterprise Feature Access (optional), Intelligent Session Control, mobility service parameters (optional), Cisco Jabber dual-mode, then other dual-mode devices. in context
• Time-of-day ringing for Single Number Reach is controlled per remote destination by its ring schedule, and an access list only narrows which callers ring that destination inside the schedule, so a reader who wants both must configure both on each remote destination. inferred in context
• A mobility user is configured at User Management > End User by checking Enable Mobility in the Mobility Information area; Enable Mobile Voice Access is an optional checkbox in the same area. in context
• Mobility can be enabled for existing users in bulk through Bulk Administration (Update Users > Query). in context
• Mobility settings can be provisioned through the Feature Group Template used by LDAP synchronization, and newly synced users inherit the mobility settings from that template. in context
• Mobility does not apply to video calls: a video call received at the desk phone cannot be picked up on the mobile phone. in context

Cite this source record

APA

WarmTransfer. (2026, October 2). Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified Mobility. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-featcfg-15-unified-mobility

BibTeX

@misc{warmtransfer-cisco-cucm-featcfg-15-unified-mobility,
  title  = {Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Cisco Unified Mobility},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cucm-featcfg-15-unified-mobility},
  note   = {Cisco Systems, accessed 2026-10-02}
}