Cisco Unified Communications Manager (CallManager)

Unified Mobility in Unified Communications Manager 7.x / 8.x Configuration Example

Document ID: 113060

Updated: Jul 01, 2011



Cisco Unified Mobility refers to the native mobility functionality within the Cisco Unified Communications Manager (Unified CM) and includes the Mobile Connect, Mobile Voice Access, and Enterprise Feature Access features. This document describes how to configure Mobile Connect in Cisco Unified CM 7.x / 8.x.



Consider these points before you enable Mobile Connect:

  • Cisco Unified Communications Manager Administration does not allow you to assign the same device for Cisco Unified Mobility to multiple users.

  • When you plan your configuration, determine whether the user uses both a desktop phone and a cell phone. If the user uses both a desktop phone and a cell phone, make sure that you assign an adjunct device to the user after you enable Mobile Connect in the End User Configuration window.

  • Checking the Enable Mobility check box in the End User Configuration window triggers licensing to consume device license units for Mobile Connect.

  • For call forwarding to another network, the call has to go out of the gateway. As a result, Unified Mobility cannot be within the same IP Network and could be forwarded to only one phone number.

  • Mobile Connect features are not supported for T1 CAS, FXO, FXS, and BRI.

  • Mobile Connect users can enable or disable mobile connect from their Cisco IP Phone.

  • Depending on the Cellular carrier, Answer too Soon/Late timers will need to be adjusted accordingly.

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco Unified CM 8.x

  • Cisco IP Phone 7961

  • Cisco ISR 2811 acting as a CUBE configured as an H323 Gateway in UCM

  • SIP Trunk to the PSTN

  • Cell phone carrier

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Network Diagram

This document uses this network setup:


  1. Phone A on the PSTN calls a Mobile Connect user's enterprise directory number (DN) 408-555-1234.

  2. The call comes into the enterprise PSTN gateway, is extended through Unified CM to the IP phone with DN 408-555-1234, and this phone begins to ring.

  3. The call is also extended to the user's Remote Destination Profile, which shares the same DN.

  4. In turn, a call is placed to the remote destination associated with the user's remote destination profile (in this case 408-555-7890).

  5. The outgoing call to the remote destination is routed through the PSTN gateway.

  6. Finally, the call rings at the remote destination PSTN phone with number 408 555-7890.

The call can then be answered at either phone.


Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Background Information

Cisco Unified Mobility allows users to consolidate all their incoming business calls into a single business phone number and receive them wherever they are working. If mobile users are unable to answer a call, Cisco Unified Mobility consolidates the unanswered calls into a single business voice mailbox on Cisco Unity voicemail. With Cisco Unified Mobility and Cisco Unified CM, employees can receive calls from colleagues and customers on a device of their choosing whether they are in the office but away from their desk, or outside the campus traveling, in a hotel, or at home.

Note: This document assumes that the PSTN gateway is configured to route calls between the mobile user and the CUCM and hence does not discuss the configuration on the PSTN gateway.

Cisco Unified Mobility Configuration

Configuration Steps

Complete these steps:

  1. Configure user accounts.

  2. Create two "Mobility" softkeys in ON HOOK and CONNECTED mode.

  3. Associate the Softkey Template on the IP Phone.

  4. Configure a Remote Destination Profile.

  5. Create a new Remote Destination.

Configure user accounts

Complete these steps:

  1. Go to the Cisco Unified CM Administration page.

  2. Choose End User from the User Management menu.

  3. Click Add New.

  4. Enter UserID, password, PIN, etc.

  5. Scroll down and make sure that you check the Enable Mobility check box in the Mobility Information section of the End User Configuration window.


Create two "Mobility" softkeys on ON HOOK and CONNECTED mode

Complete these step:

  1. Navigate to the Cisco Unified Communications Manager Administration page.

  2. Go to Device > device settings > softkey template.

  3. Click Add New.

  4. The system will ask on what softkey template do you want to base your new template. Choose the Standard User template, and then click Copy.


  5. Change the name of the Standard User Softkey Template to Mobility-Softkey, and click Save.


  6. Click GO after you choose the related link option Configure Softkey Layout from the drop-down located in the top right corner.

  7. Make sure the Selected Softkeys section has the Mobility (Mobility) softkey key for these two states:

    • On Hook

    • Connected

    Note: Step 7 has to be repeated for both On Hook and Connected states separately.


  8. Click Save.

Associate the Softkey Template on the IP Phone

Complete these steps:

  1. Go to the Cisco Unified Communications Manager Administration page.

  2. Choose Device > Phone.

  3. Click Find, and choose IP Phone.

  4. On the Phone Configuration page, choose Softkey Template as Mobility-Softkey.


  5. Click Save, and Reset the Phone.

Configure a Remote Destination Profile

Complete these steps:

  1. Go to Cisco Unified Communications Manager Administration page.

  2. Go to Device > Device Settings > Remote Destination Profile.

  3. Click Add New.

  4. This window appears:


  5. Configure these settings:

    1. Name: mobilityuser_RDP

    2. Description: Mobilityuser Remote Destination Profile

    3. User ID: your mobility user

    4. Device Pool: an appropriate device pool

    5. Calling Search Space: an appropriate CSS

    6. User Hold Audio Source: your option of preference

    7. Network Hold MOH Audio Source: your option of preference

    8. Privacy: Off

    9. Rerouting Calling Search: preferably a CSS that have access to the PSTN

    10. Calling Party Transformation CSS: None

    11. Leave the rest as default.


  6. Click Save.

  7. Click on Line[1] - Add a new DN link in order to proceed to a new DN.

  8. When you enter the DN and partition as the desk phone, it should auto populate.

  9. Click Save.

Create a new Remote Destination

Complete these steps:

  1. Go to the Cisco Unified Communications Manager Administration page.

  2. Choose Device > Remote Destination.

  3. Click Add New.


  4. Configure these settings:

    1. Name: mobilityuser_mobilephone

    2. Destination Number: 9+mobile phone number (If 9 is pressed to make an outbound call)

    3. Answer too Soon Timer: leave as default

    4. Answer too Late Timer: leave as default

    5. Delay Before Ringing Timer: leave as default

    6. Remote Destination Profile: [select the newly created remote destination profile that is mobilityuser_RDP]

    7. Check the Mobile Phone check box.

  5. Click Save.

  6. Check the Line association check box, and click Save.

You may need to reset the phone associated with the Mobile Connect user. Your user is now ready to begin using the Mobile Connect feature.

Caller ID Transformations


An H323 gateway has been configured to accept a call to the Mobile Voice Access IVR number. In this case, when you make a call to any DID phone via the PSTN (not using the MVA IVR number), it still appears as though you are calling from an internal extension. In this case, any call from the user's remote destination phone destined for any directory number in the cluster will automatically have the caller ID changed from the remote destination number to the enterprise directory number.


Any calls made into the cluster by configured remote destination numbers will automatically have their caller ID or calling number changed from the calling remote destination phone number to the enterprise directory number of the associated desk phone. This ensures that the active call caller ID display and call history log caller ID reflect a mobility user's enterprise desk phone number rather than their mobile phone number, and it makes sure that any return calls are made to the user's enterprise number, thus anchoring those calls within the enterprise.

Remote Destination Configuration Failed


The Add failed. [10108] Remote Destination cannot be added because the associated EndUser does not have Mobility Enabled. error message is received.


In order to resolve this problem, make sure the Enable Mobility checkbox on the end user page is checked.

Complete these steps:

  1. Go to the ccmadmin page, and select User Management > End User.

  2. Select the end user for whom you are configuring mobility.

  3. Check the Enable Mobility checkbox.

Related Information

Updated: Jul 01, 2011
Document ID: 113060