Configuring Cisco Unified Mobility

Created by Rami Kandah

Introduction

This document gives a step-by-step configuration for the Cisco Unified Mobility feature on Cisco Unified
Communications Manager 6.x.

This document illustrates configurations with screen shots for Mobile Voice Access and Mobile Connect.

For more information on the operation of these features, refer to the configuration guides for Cisco Unified
Communications Manager on www.cisco.com.

Configuration Steps:

This list summarizes the steps to configure Mobile Connect and Mobile Voice Access:

Step 1 Activate the Mobile Voice Access service.

Step 2 Create the softkey templates for Cisco Unified Mobility.
Step 3 Configure user accounts.
Step 4 Create access lists for Mobile Connect, assigning each list to the Mobile Connect
user and specifying whether the list is allowed or blocked.
Step 5 Create Remote Destination Profiles, assigning each user to a profile and associating
desktop phone numbers for each user.
Step 6 Add Remote Destinations, selecting the previously defined profile as part of the
configuration.
Step 7 Enable Mobile Voice Access and configure the number to dial Mobile Voice Access in
the Service Parameters.
Step 8 Configure the Media Resources for Mobile Voice Access.
Step 9 Configure H.323 gateways for Mobile Voice Access.

1 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

1. Service Activation

The first step of configuring Cisco Unified Mobility is to activate the appropriate service.

Navigate to the Cisco Unified Serviceability page. In the menu Tools > Service Activation, activate the
Cisco Unified Mobile Voice Access Service. When activated, verify that the Cisco Unified Mobile Voice
Access service is started using the Control Center > Feature Services.

2 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

2. Softkey Templates

In order to allow calls to be switched between the IP phone and the remote phone, configure a softkey
template that includes the Mobility softkey.

In Cisco Unified Communications Manager Administration, go to Device > Device Settings > Softkey
Template, create a new softkey template, and assign the Mobility softkey for the following call states:

„ On Hook
„ Connected

Then assign the newly created softkey template to the IP phones that are configured for Cisco Unified
Mobility and reset the IP phones.

3 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

3. User Accounts

End-user accounts have to be created and configured for Cisco Unified Mobility.

The Enable Mobility check box allows the user to manage calls using a single number and to transfer calls
in progress between the desktop phone and the remote destination (for example, a mobile phone).

The Enable Mobile Voice Access check box allows the user to access the Mobile Voice Access Integrated
Voice Response system to initiate Mobile Connect calls and to activate or deactivate Mobile Connect
capabilities.

4 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

4. Access Lists

Access lists are configured at Device > Device Settings > Access Lists. Enter a name and a description
for the access list. Select the user to whom the access list applies from the Owner drop-down list. Then
select the Allowed check box to create a list of phone numbers that can be transferred to the remote
destinations of the user. If you leave this check box blank, then the phone numbers in the access list are
blocked and cannot be forwarded to the remote destinations of the user.

After saving these preferences, the window reopens to display the Access List Member Information area.
When adding a member, the Access List Member Detail window opens. Select an option from the Filter
Mask drop-down list. Choose to enter a directory number, filter out calls that do not have caller ID (Not
Available), or specify a number that will be allowed or blocked without displaying the caller ID (Private).

5 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

5. Remote Destination Profiles

Remote destination profiles are configured at Device > Device Settings > Remote Destination Profile.
The remote destination profile contains the parameters that apply to all of the remote destinations for the
user. Enter a name, description, device pool, calling search space, rerouting calling search space, media
resource list, and the user hold audio source for the remote destination profile. Parameters specific to Cisco
Unified Mobility are:
„ User ID: Select the user to whom this profile is assigned. The selection must match the ID
of a user on the End User Configuration page for whom Enable Mobility is selected.
„ Privacy: Select a privacy option for this profile. The value is on, off, or default.
„ Ignore Presentation Indicators: Select the check box to ignore the connected line ID
presentation. This step is recommended for internal calls.
„ Calling Search Space (CSS): Set the CSS that is used for placing calls from the remote
destination phone.
„ Rerouting Calling Search Space: Set the CSS that is used to send calls that are received at
the enterprise number of the user to remote destinations.
After creating a remote destination profile, the directory number (DN) record must be associated for the
desktop phone or phones of the user by clicking Add a New DN on the Remote Destination Profiles
window.

6 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

6. Remote Destinations

Remote destinations are configured by navigating to Device > Remote Destination. Enter a name for the
remote destination and configure the following parameters:
„ Destination Number: Enter the telephone number for the remote destination. Include the
area code and any additional digits required to obtain an outside line. The maximum field
length is 20 characters.
„ Allowed or Blocked Access List: Specifies the calling numbers that are allowed or denied to
send calls to the remote destination.
„ Mobile Phone: Select the check box if the remote destination is a mobile phone. This check
box must be selected for Mobile Connect to work with this remote destination.
„ Enable Mobile Connect: Allows this remote destination to be used for desktop phone
transfers.
When associating a line with the Remote Destination information, the calling number behavior changes.
When dialing with an associated Remote Destination device, the calling number on the display of the
enterprise phones is 1000 and not 918526625555. If the calling number is not prefixed with the 9, the
display will show the calling number 8526625555, because the incoming caller is not identified as a remote
destination (due to the 91 missing in the calling number).

7 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

7. Service Parameters

To configure Cisco Unified Mobility service parameters, go to System > Service Parameters and select
Cisco Unified Mobility. You can enable access to enterprise features by setting the Enable Enterprise
Feature Access parameter to True. In this case, the following features can be used from a remote
destination phone, and the corresponding feature access codes can be modified from their default values:

„ Hold: *81
„ Exclusive Hold: *82
„ Resume: *83
„ Transfer: *84
„ Conference: *85

These parameters must be unique and 2 or 3 characters in length. Allowed values are 0-9, A-D, and *.

In order to enable Mobile Voice Access, set the Enable Mobile Voice Access parameter to True.

8 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

8. Media Resources

To assign localized user prompts or Mobile Voice Access numbers, navigate to Media Resources > Mobile
Voice Access. In the Mobile Voice Access Directory Number field, enter the number to reach Mobile Voice
Access. Choose a partition for Mobile Voice Access from the Mobile Voice Access Partition drop-down list.
The combination of directory number and partition makes the Mobile Voice Access number unique. Choose
the localization areas to be supported for Mobile Voice Access.

9 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

9. H.323 Gateways

Configure the H.323 gateway to use the Mobile Voice Access application and load the Integrated Voice
Response Voice Extensible Markup Language (VXML) application from the Cisco Unified Mobility server.
Here is a sample configuration for Cisco IOS release 12.3(13) and later:

application
service CCM http://172.18.1.241:8080/ccmivr/pages/
IVRMainpage.vxml

Here is a sample configuration before Cisco IOS release 12.3(12):

call application voice CCM http://172.18.1.241:8080/ccmivr/

pages/IVRMainpage.vxml

Configure the dial peer and associate it with Mobile Voice Access application. Here is a sample
configuration for Cisco IOS release 12.3(13) and later:

dial-peer voice 1111 pots

service CCM
incoming called-number 14085551111
direct-inward-dial

10 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.

Here is a sample configuration for Cisco IOS release 12.3(12) and earlier:

dial-peer voice 1111 pots

application CCM
incoming called-number 14085551111
direct-inward-dial

Add a dial peer to transfer the calls to the Mobile Voice Access number:

dial-peer voice 1112 voip

destination-number 14085551111
session target ipv4:172.18.1.241
codec g711ulaw
dtmf-relay h245-alphanumeric
no vad

If the application is available for internal phones, configure a route pattern to the H.323 gateway and hairpin
the calls on the H.323 gateway with a dial peer. Associate the Mobile Voice Access application with the
service CCM command. For inbound dial-peer matching, configure the answer-address 14085551...
command. Here is an example:

dial-peer voice 9999 voip

service CCM
incoming called-number 14085551111
codec g711ulaw
dtmf-relay h245-alphanumeric
no vad

11 Configuring Cisco Unified Mobility © 2008 Cisco Systems, Inc.