Cisco Unified Communications Manager Features and Services Guide, Release 6.0(1)
Mobile Connect and Mobile Voice Access
Downloads: This chapterpdf (PDF - 529.0KB) The complete bookPDF (PDF - 17.04MB) | Feedback

Mobile Connect and Mobile Voice Access

Table Of Contents

Mobile Connect and Mobile Voice Access

Introducing Mobile Connect and Mobile Voice Access

Definitions

Features and Benefits

Use Case Scenarios

Interactions and Restrictions

System Requirements

Migrating from Cisco Unified MobilityManager

Configuring Mobile Connect and Mobile Voice Access

Configuring Access Lists

Finding Access Lists

Adding Access Lists

Updating Access Lists

Deleting Access Lists

Access List Configuration Settings

Access List Member Detail Configuration Settings

Configuring Remote Destination Profiles

Finding Remote Destination Profiles

Adding a Remote Destination Profile

Associating a Directory Number with a Remote Destination Profile

Updating Remote Destination Profiles

Deleting Remote Destination Profiles

Remote Destination Profile Configuration Settings

Configuring Remote Destinations

Finding Remote Destinations

Adding Remote Destinations

Updating Remote Destinations

Deleting Remote Destinations

Remote Destination Configuration Settings

Configuring Mobile Voice Access Media Resources

Mobile Voice Access Configuration Settings

Configuring H.323 Gateways for Mobile Voice Access

Configuring a H.323 Gateway for System Remote Access Using PRI

Configuring a H.323 Gateway for System Remote Access Using Hairpinning

Configuring Mobility Settings

Mobility Configuration Settings

Configuring Mobility Softkeys

Related Topics


Mobile Connect and Mobile Voice Access


Mobile Connect enables users to manage business calls using a single phone number and pick up in-progress calls on the desktop phone and cellular phone. Mobile Voice Access extends Mobile Connect capabilities by way of an integrated voice response (IVR) system used to initiate Mobile Connect calls and activate or deactivate Mobile Connect capabilities.

This chapter includes information on the following topics:

Introducing Mobile Connect and Mobile Voice Access

Interactions and Restrictions

System Requirements

Configuring Mobile Connect and Mobile Voice Access

Configuring Access Lists

Configuring Remote Destination Profiles

Configuring Remote Destinations

Configuring Mobile Voice Access Media Resources

Configuring H.323 Gateways for Mobile Voice Access

Configuring Mobility Settings

Configuring Mobility Softkeys

Related Topics

Introducing Mobile Connect and Mobile Voice Access

Mobile Connect allows users to answer incoming calls on the desktop phone or cellular phone, to pick up in-progress calls on the desktop phone or cellular phone without losing the connection, and to originate enterprise calls from the cellular phone.

Mobile Voice Access extends Mobile Connect capabilities by allowing users to originate a call from a remote destination such as a cellular phone as if dialing from the desktop phone. A remote destination is a phone that is designated as available for Mobile Connect responses and pickup. The user dials Mobile Voice Access from the remote destination. The user is prompted for the PIN assigned to the user in Cisco Unified Communications Manager. Once authenticated, the user can make a call using the same Mobile Connect features that would be available if the user originated the call from the enterprise desktop phone.

When calling Mobile Voice Access, the system prompts the user for the originating phone number in addition to the PIN if any of the following is true:

The number the user is calling from is not one of the user's remote destinations.

The number is blocked by the user or the user's carrier (shown as "Unknown Number").

The number is not accurately matched in the Cisco Unified Communications Manager database; for example, if the number is 510-666-9999, but it is listed as 666-9999 in the database, or the number is 408-999-6666, but it is entered as 1-408-999-6666 in the database.

If the user incorrectly enters any requested information (such as cellular phone number or PIN) three times in a row, the Mobile Voice Access call disconnects, and the user is locked out for a period of time.


Note Existing cellular phones, including Code Division Multiple Access (CDMA) and Global System for Mobile Communications (GSM) phones can be used for Mobile Connect and Mobile Voice Access. In some cases, however, it may be necessary to modify timer settings in Cisco Unified Communications Manager to assure compatibility. See the "Adding Remote Destinations" section.


Definitions

Table 24-1 lists definitions of terms related to Mobile Connect and Mobile Voice Access.

Table 24-1 Definitions

Term
Definition

Access List

List that determines the phone numbers that are permitted to be passed or blocked from being passed to remote destinations.

Mobile Connect

Feature that allows users to answer incoming calls on the desktop phone or remote destination and to pick up in-progress calls on the desktop phone or remote destination without losing the connection.

Mobile Voice Access

Integrated voice response (IVR) system used to initiate Mobile Connect calls and to activate or deactivate Mobile Connect capabilities.

Remote Destination

Phones that are available for Mobile Connect responses and pickup, plus locations that are used to reach Mobile Voice Access. Remote destinations may include any of the following devices:

Single mode cellular phones

Smart phones

Dual mode phones

Enterprise IP phones not in the same cluster as the desktop phone

Home phone numbers in the PSTN.

Remote Destination Profile

Set of parameters that apply to all of a user's remote destinations.


Features and Benefits

Mobile Connect and Mobile Voice Access enable flexible management of enterprise and cellular telephone communications and provide these features and benefits:

Simultaneous desktop ringing—Incoming calls ring simultaneously on the IP phone extension and the designated mobile handset.When the user answers one line, the unanswered line automatically stops ringing. Users can choose the preferred device each time a call comes in.

Desktop call pickup—Users can switch between desktop phone and cellular phone during an active call without losing the connection. Based on the needs of the moment, they can take advantage of the reliability of the wired office phone or the mobility of the cellular phone.

Single enterprise voice mailbox—The enterprise voice mail box can serve as single, consolidated voicemail box for all business, including calls to the desktop or configured remote devices. Incoming callers have a predictable means of contacting employees and less time is required for users to check multiple voice mail systems.

System remote access—A user's cellular phone can initiate calls as if it were a local IP PBX extension. User-initiated calls can take advantage of local voice gateways and WAN trunking, and the enterprise can track employee call initiation.

Allowed and blocked access lists—Users can restrict the set of callers that cause a designated remote destination to ring on an incoming call (allowed access list) or for which the remote destinations do not ring on an incoming call (blocked access list). Each remote destination presents a cellular or other phone that can be configured to accept transfers from the user's desktop phone.

Caller ID—Caller ID is preserved and displayed on all calls. Users can take advantage of Mobile Connect with no loss of expected IP phone features.

Remote on/off control—Users can turn their Mobile Connect features on or off from the cellular phone using Mobile Voice Access or from the end user configuration pages.

Call tracing—Detailed Mobile Connect calls are logged, providing information to help the enterprise optimize trunk usage and debug connection problems.

Security and privacy for Mobile Connect calls—During an active Mobile Connect call, the associated desktop IP phone is secured. Access to the call from the desktop is eliminated as soon as the cellular connection becomes active, precluding the possibility of an unauthorized person listening in on the call that is bridged to the cellular phone.

Mid-call enterprise feature support—DTMF feature codes are configurable as Cisco Unified Communications Manager service parameters: Hold (default is *81), exclusive hold (default is *82), resume (default is *83), transfer (default is *84), and conference (default is *85).

Smart phone support—Users can use the enterprise hold, resume, transfer, conference softkeys on the smartphone in an active call. Users can also enable or disable Mobile Connect from a smartphone.

Enterprise feature access for two-stage dialing—Enterprise features are available with two-stage dialing for smartphones. Two-stage dialing allows smartphones to make outgoing calls through Cisco Unified Communications Manager if the smartphone is in business mode. The smartphone dials the Enterprise Feature Access number for Cisco Unified Communications Manager and then dials the destination number.

Manual handoff calls on dual mode phone—Dual-mode devices offer an option to manually hand off calls from the PSTN to WLAN and vice versa.

Use Case Scenarios

Mobile Connect supports these use case scenarios:

Receiving an outside call on desktop or cellular phone—An outside caller dials the user's desktop extension. The desktop phone and cellular phone ring simultaneously. When the user answers one of the phones, the other phone stops from a desktop telephone to a cellular phone. The user can switch from the desktop phone to cellular phone during a call without losing the connection. Switching is supported for incoming and outgoing calls.

Moving back from a cellular phone to a desktop phone—If a call was initiated to or from the desktop phone and then shifted to the cellular phone, the call can be shifted back to the desktop phone.

Using mid-call enterprise features—During a Mobile Connect call, users can perform mid-call functions, including hold/resume, exclusive hold, transfer, and conference.

Using enterprise features with two- stage dialing—When a user wants to place a call from a smartphone and the smartphone is in business mode, the call is made through Cisco Unified Communications Manager. The function is similar to Mobile Voice Access, but without voice prompts. Users can also use this method to turn Mobile Connect on or off.

Mobile Voice Access supports these scenarios:

Initiating a mobility call from a remote phone, such as a cellular phone—Users can use Mobile Voice Access to initiate calls from a cellular phone as if dialing from the desktop phone.

Moving from a cellular phone to a desktop phone during a cellular-phone initiated call—If the user has initiated a call from a cellular phone using Mobile Voice Access, the user can shift to the desktop phone during the call without losing the connection, and can shift back again as needed.

Interactions and Restrictions

Most standard Cisco Unified Communications Manager features are compatible with Mobile Connect and Mobile Voice Access, except as indicated here:

Up to two simultaneous Mobile Connect calls are supported at one time. Any additional calls that come in are automatically transferred to the user's voice mail.

To use Mobile Connect features, you must first disable the Auto Call Pickup feature.

The Forced Authorization Code and Client Matter Code (FAC/CMC) feature does not work with Mobile Voice Access.

Mobile Connect does not work with Multilevel Precedence and Preemption (MLPP). If a call is preempted with MLPP, Mobile Connect features are disabled for that call.

Mobile Connect services do not extend to video calls. A video call received at the desktop phone cannot be picked up on the cellular phone.

Remote destinations must be Time Division Multiplex (TDM) devices. You cannot configure IP phones within a Cisco Unified Communications Manager cluster as remote destinations.

Users can not initiate a meet-me conference as conference controller using Mobile Voice Access, but can join a meet-me conference.

QSIG (Q Signaling) path replacement is not supported.

Dual mode handoff requires that caller ID be available in the cellular network.

While a dual mode phone is in Wi-Fi enterprise mode, it is not controlled or monitored by any CTI applications.

Availability of enterprise features in GSM using DTMF depends upon the features that are supported in the third party smartphones.

Only H.323 VoIP gateways are supported for Mobile Voice Access.

Enterprise features from cellular networks require out-of-band DTMF.

Call anchoring is performed based on caller ID and is supported only from calls from registered single mode or dual mode phones

Remote destinations are limited to PSTN numbers or numbers across ICT trunks.

Calls put on hold by Cisco Unified IP Phones, cannot be resumed by remote destinations.

The In Use Remote indicator for dual mode phones on a shared line call in the WLAN will disappear if the dual mode phone goes out of WLAN range.

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

If an existing conference call is initiated from a shared-line IP phone or dual mode phone or smartphone that is a remote destination, no new conference party can be added to the existing conference after the call has been sent to a cellular for or a dual mode handoff action has been taken. To permit the addition of new conference parties, use the Advanced Ad Hoc Conference Enabled service parameter.

When configuring a directory number associated with a remote destination profile, you must use ASCII characters only in the Display (Internal Caller ID) field on the Directory Number Configuration page.

It is not necessary to configure settings for call forward unregistered, if the end user has configured remote destinations. Appropriate call forwarding will is handled as part of the Mobile Connect process.

In a multiple node cluster environment, if the Cisco Unified Communications Manager 6.0 publisher is unreachable, any changes that end users make to turn Mobile Connect off or on by way of Mobile Voice Access or two-stage dialing are not saved.

Enterprise feature access service parameters apply to standard phones and smartphones; however, smartphones generally use on-touch keys to send the appropriate codes. Administrators must configure any smartphones that will be used with Mobile Connect to use either the default codes for enterprise feature access or the codes specified in the smartphone documentation.


Note The enterprise feature access virtual device is always in the Default region. If you change the default to another region, the field still remains as Default.


System Requirements

Mobile Connect and Mobile Voice Access is supported with SCCP and TNP-based SIP Cisco Unified IP Phones. The following software components are required.

Cisco Unified Communications Manager 6.0.

Cisco Unified Mobile Voice Access Service running on Cisco Unified Communications Manager Publisher only.

Cisco Unified Communications Manager Locale Installer (if you want to use non-English phone locales or country-specific tones).

Migrating from Cisco Unified MobilityManager

Follow this process to migrate standalone Cisco Unified MobilityManager data to Cisco Unified Communications Manager Release 6.0(1):

1. Upgrade the Cisco Unified MobilityManager system to Release 1.2(5), if necessary. See the Release Notes for Cisco Unified MobilityManager Release 1.2(5).

2. Log into Cisco Unified MobilityManager and export the configuration data in CSV format. For instructions, see the Release Notes for Cisco Unified MobilityManager Release 1.2(5).

3. Log into Cisco Unified Communications Manager Administration Release 6.0(1) and use the Bulk Administration Import/Export windows to import the CSV data files that were previously exported from Cisco Unified MobilityManager. See the "Access List," "Remote Destination," and "Remote Destination Profile" chapters in the Cisco Unified Communications Manager Bulk Administration Guide Release 6.0(1).

Configuring Mobile Connect and Mobile Voice Access

Table 24-2 summarizes the steps for configuring Mobile Connect and Mobile Voice Access. For detailed instructions, see the chapters and sections listed in the table.

Table 24-2 Cisco Unified Communications Manager Mobile Connect and Mobile Voice Access
Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

Configure user accounts.

Note Make sure that the Enable Mobility and Enable Mobile Voice Access check boxes are selected in the End User Configuration page.

See the End User Configuration chapter in the Cisco Unified Communications Manager Administration Guide.

Step 2 

Create access lists for Mobile Connect, assigning each list to the Mobile Connect user and specifying whether the list is allowed or not.

See the "Adding Access Lists" section.

Step 3 

Create remote destination profiles, assigning each user to a profile.

See "Adding a Remote Destination Profile" section.

Step 4 

Associate desktop directory numbers (DNs) for the user.

See the "Associating a Directory Number with a Remote Destination Profile" section.

Step 5 

Add remote destinations, selecting the previously-defined profile as part of the configuration.

See the "Adding Remote Destinations" section.

Step 6 

On the Service Parameters page:

Select True for Enable Mobile Voice Access and enter the Mobile Voice Access number. This is the DID number that end users use to reach Mobile Voice Access.

Note To make Mobile Voice Access calls, you must configure these service parameters and select Enable Mobile Voice Access on the End User Configuration page (as listed in the first step in this table).

Select True for Enable Enterprise Feature Access to enable access to hold, resume, transfer, and conference features from remote destinations.

See the Service Parameters Configuration chapter in the Cisco Unified Communications Manager Administration Guide.

Step 7 

Configure the media resources for Mobile Voice Access.

See the "Configuring Mobile Voice Access Media Resources" section.

Step 8 

Configure mobility settings for dual mode phone handoff.

See the "Configuring Mobility Settings" section.

Configuring Access Lists

After the remote destination profiles are created, you can define access lists to explicitly allow or block the use of specific phone numbers for Mobile Connect.

To configure access lists, see the following sections:

Finding Access Lists

Adding Access Lists

Updating Access Lists

Deleting Access Lists

Finding Access Lists

Cisco Unified Communications Manager lets you locate specific access lists on the basis of specific criteria. To locate access lists, follow these steps:

Procedure


Step 1 Choose Device > Device Settings > Access List.

The Find and List Access Lists window displays. Records from an active (prior) query may also display in the window.

Step 2 To find all records in the database, ensure the dialog box is empty; go to Step 3.

To filter or search records

From the first drop-down list box, choose a search parameter.

From the second drop-down list box, choose a search pattern.

Specify the appropriate search text, if applicable.


Note To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the - button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.


Step 3 Click Find.

All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.


Note You can delete multiple records from the database by checking the check boxes next to the appropriate record and clicking Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected.


Step 4 From the list of records that display, click the link for the record that you want to view.


Note To reverse the sort order, click the up or down arrow, if available, in the list header.


The window displays the item that you choose.


Additional Information

See the "Related Topics" section.

Adding Access Lists

To create access lists, perform the following procedure:

Procedure


Step 1 Choose Device > Device Settings > Access Lists.

Step 2 Click Add New.

The Access List Configuration window displays.

Step 3 Enter values for the parameters described in Table 24-3.

Step 4 Click Save.

The window reopens to display Access List Member Information area.

Step 5 Click Add Member.

The Access List Member Detail window opens.

Step 6 Enter values for the parameters described in Table 24-4.

Step 7 Click Save.

The Access List Configuration window reopens to show the new number or filter in the Selected Filters area.

Step 8 From the Access Configuration window, add additional filters and also modify any existing access list as needed:

To modify a DN mask, click the link for the directory number at the bottom of the screen under Access List Members, enter your change, and click Save.

To delete a filter, select the filter and click Delete.

To inactivate a filter without deleting it, select the filter in the Selected Filters area and click the downward-facing arrow to move it to the Removed Filters area.

To activate a filter, select the filter in the Removed Filters area, and click the upward-facing arrow to move it to the Selected filters area.

To create a new access list with the same members as the existing list, click Copy.


Additional Information

See the "Related Topics" section.

Updating Access Lists

To update an access list in Cisco Unified Communications Manager Administration, perform the following procedure:

Procedure


Step 1 Locate the access list that you want to update, as described in the "Finding Access Lists" section.

Step 2 Update the fields that display.

Step 3 Click Update.


Additional Information

See the "Related Topics" section.

Deleting Access Lists

To delete an access list in Cisco Unified Communications Manager Administration, perform the following procedure:

Procedure


Step 1 Locate the access list that you want to delete, as described in the "Finding Remote Destination Profiles" section.

Step 2 After the Access Lists window displays, click Delete.

Step 3 To continue with the deletion, click OK.


Additional Information

See the "Related Topics" section.

Access List Configuration Settings

Table 24-3 describes the available settings in the Access Lists window.

Table 24-3 Access List Configuration Settings 

Field
Description

Name

Enter a text name for the remote destination profile.

Description

Enter a text description of the remote destination profile.

Owner

Select the user to whom the access list applies from the Owner drop-down list box.

Allowed

Select the check box to allow calls from phone numbers from being passed to the remote destinations. If the check box is blank, the access list blocked calls from the specified phone numbers from being passed to the remote destinations.

Selected Filters

Use the arrows to move the access list members that you want to include to this area.

Removed Filters

Use the arrows to move the access list members that you want to exclude to this area.


Additional Information

See the "Related Topics" section.

Access List Member Detail Configuration Settings

Table 24-4 describes the available settings in the Access List Detail window.

Table 24-4 Access List Detail Configuration Settings 

Field
Description

Filter Mask

Select an option from the drop-down list box. You can 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).

DN Mask

If you chose Directory Number in the Filter Mask field, enter a phone number or filter in the DN Mask field. You can use the following wild cards to define a filter:

X (upper or lower case)—Matches a single digit.

!—Matches any number of digits.

#—Used as a single digit for exact match.

Examples:

408! matches any number starts with 408.

408555123X matches any number between 4085551230 and 4085551239.


Additional Information

See the "Related Topics" section.

Configuring Remote Destination Profiles

To configure remote destination profiles, see the following sections:

Finding Remote Destination Profiles

Adding a Remote Destination Profile

Updating Remote Destination Profiles

Deleting Remote Destination Profiles

Finding Remote Destination Profiles

Cisco Unified Communications Manager lets you locate specific remote destination profiles on the basis of specific criteria. To locate remote destination profiles, follow these steps:

Procedure


Step 1 Choose Device > Device Settings > Remote Destination Profile.

The Find and List Remote Destination Profiles window displays. Records from an active (prior) query may also display in the window.

Step 2 To find all records in the database, ensure the dialog box is empty; go to Step 3.

To filter or search records

From the first drop-down list box, choose a search parameter.

From the second drop-down list box, choose a search pattern.

Specify the appropriate search text, if applicable.


Note To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the - button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.


Step 3 Click Find.

All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.


Note You can delete multiple records from the database by checking the check boxes next to the appropriate record and clicking Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected.


Step 4 From the list of records that display, click the link for the record that you want to view.


Note To reverse the sort order, click the up or down arrow, if available, in the list header.


The window displays the item that you choose.


Additional Information

See the "Related Topics" section.

Adding a Remote Destination Profile

The remote destination profile contains the parameters that apply to all of the user's remote destinations. After configuring user accounts for Mobile Connect (see the End User Configuration, chapter in the Cisco Unified Communications Manager Administration Guide), you can create a remote destination profile for the user.

To create a remote destination profile, perform the following procedure:

Procedure


Step 1 Choose Device > Device Settings > Remote Destination Profile.

Step 2 Click Add New.

The Remote Destination Profile Configuration window displays.

Step 3 Enter values for the parameters described in Table 24-5.

Step 4 Click Save.


Associating a Directory Number with a Remote Destination Profile

After creating a remote destination profile, you must associate the DN record for the user's desktop phone or phones. Click the Add a New DN link on the Remote Destination Profiles window, and follow the instructions in the Directory Number Configuration chapter in the Cisco Unified Communications Manager Administration Guide.


Note If the remote destination profile is dissociated on the Directory Number configuration page, you must select the Line Association check box for the DN on the Remote Destination page to reassociate it.


Additional Information

See the "Related Topics" section.

Updating Remote Destination Profiles

To update a remote destination profile in Cisco Unified Communications Manager Administration, perform the following procedure:

Procedure


Step 1 Locate the remote destination profile that you want to update, as described in the "Finding Remote Destination Profiles" section.

Step 2 Use Table 24-5 as a guide to update the fields that display.

Step 3 Click Update.


Additional Information

See the "Related Topics" section.

Deleting Remote Destination Profiles

To delete a remote destination profile in Cisco Unified Communications Manager Administration, perform the following procedure:

Procedure


Step 1 Locate the remote destination profile that you want to update, as described in the "Finding Remote Destination Profiles" section.

Step 2 After the Remote Destination Profiles window displays, click Delete.

Step 3 To continue with the deletion, click OK.


Additional Information

See the "Related Topics" section.

Remote Destination Profile Configuration Settings

Table 24-5 describes the available settings in the Remote Destination Profile window.

Table 24-5 Remote Destination Profile Configuration Settings 

Field
Description

Name

Enter a text name for the remote destination profile.

Description

Enter a text description of the remote destination profile.

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.

Device Pool

Select the device pool that applies to this profile. The device pool defines sets of common characteristics for devices, such as region, date/time group, softkey template, and MLPP information.

Calling Search Space

Select the calling search space to be used for routing Mobile Connect and Mobile Voice Access calls.

User Hold Audio Source

Select the audio option for users on hold for Mobile Connect and Mobile Voice Access calls.

Network Hold MOH Audio Source

Select the audio source from the IOS gateway that provides multicasting audio source for Mobile Connect and Mobile Voice Access calls.

Privacy

Select a privacy option for the profile.

For more configuration information, refer to Barge and Privacy in the Cisco Unified Communications Manager Features and Services Guide.

Rerouting Calling Search Space

Select a calling search space to be used if Mobile Connect calls need to be rerouted.

Note The gateway that is configured for routing mobile calls must be assigned to the partition that belongs to the Rerouting Calling Search Space. Cisco Unified Communications Manager determines how to route calls based on the remote destination number and the Rerouting Calling Search Space.

Calling Party Transformation CSS

Select the calling search space for transformations.

Note The partitions in the calling search space should contain only calling party transformations.

Note The calling search space should not be null, because no transformations can apply to null partitions.

Ignore presentation indicators

Select the check box if you want to ignore the connected line ID presentation. This is recommended for internal calls.


Configuring Remote Destinations

After remote destination profiles and access lists are created, you can enter individual remote destinations, assigning each to a profile. Each remote destination presents a cellular or other phone that can be configured to accept transfers from the user's desktop phone.

When you save a new remote destination, the screen is redrawn to show an Association Information section in the left panel. This section lists the desk phone numbers that have been assigned to the remote destination profile. You can click a link to open the associated Directory Number Information page. See Configuring a Directory Number in the Cisco Unified Communications Manager Administration Guide.


Note This section describes how to access remote destination records by opening the Remote Destination page. You can also open an existing or new record in the Remote Destination Configuration page by licking the Add a New Remote Destination link at the bottom of the remote destination profile. See the "Finding Remote Destination Profiles" section for instructions on displaying a remote destination profile.


To configure remote destinations, see the following sections:

Finding Access Lists

Adding Access Lists

Updating Access Lists

Deleting Access Lists

Finding Remote Destinations

Cisco Unified Communications Manager lets you locate specific remote destinations on the basis of specific criteria.

To locate remote destinations, follow these steps:

Procedure


Step 1 Choose Device > Remote Destination.

The Find and List Remote Destinations window displays. Records from an active (prior) query may also display in the window.

Step 2 To find all records in the database, ensure the dialog box is empty; go to Step 3.

To filter or search records

From the first drop-down list box, choose a search parameter.

From the second drop-down list box, choose a search pattern.

Specify the appropriate search text, if applicable.


Note To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the - button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.


Step 3 Click Find.

All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.


Note You can delete multiple records from the database by checking the check boxes next to the appropriate record and clicking Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected.


Step 4 From the list of records that display, click the link for the record that you want to view.


Note To reverse the sort order, click the up or down arrow, if available, in the list header.


The window displays the item that you choose.


Additional Information

See the "Related Topics" section.

Adding Remote Destinations


Note End users can create their own remote destinations in the User Options pages. See the User Guide for the phone model.


To add a new remote destination, perform the following procedure:

Procedure


Step 1 Choose Device > Remote Destination.

Step 2 Click Add New.

Step 3 The Remote Destination Configuration window displays.

Step 4 Enter values for the parameters described in Table 24-6.


Note The appropriate timer settings in Table 24-6 may be vendor-specific. If difficulties in transferring calls occur using the default timer settings, it may be necessary to adjust the settings to be compatible with the vendor of the remote destination phone.


Step 5 Select the Line Association check boxes for the desktop phones that will be used with this remote destination. This is required for Mobile Connect to work.

Step 6 Click Save.

Additional Information

See the "Related Topics" section.

Updating Remote Destinations

To update a remote destination in Cisco Unified Communications Manager Administration, perform the following procedure:

Procedure


Step 1 Locate the remote destination that you want to update, as described in the "Finding Remote Destinations" section.

Step 2 Use Table 24-6 as a guide to update the fields that display.

Step 3 Click Update.


Additional Information

See the "Related Topics" section.

Deleting Remote Destinations

To delete a remote destination in Cisco Unified Communications Manager Administration, perform the following procedure:

Procedure


Step 1 Locate the remote destination that you want to update, as described in the "Finding Remote Destinations" section.

Step 2 After the Remote Destination window displays, click Delete.

Step 3 To continue with the deletion, click OK.


Additional Information

See the "Related Topics" section.

Remote Destination Configuration Settings

Table 24-6 describes the available settings in the Remote Destination window.

Table 24-6 Remote Destination Configuration Settings 

Field
Description

Name

Enter a name that identifies the remote destination.

Destination Number

Enter the telephone number for the destination. Include the area code and any additional digits required to obtain an outside line. Maximum field length is 20 characters; individual characters can take the values 0-9 or A-D. It is recommended that you configure the caller ID of the remote destination.

Note Add the necessary translation pattern or route patterns to route the destination number.

Answer Too Soon Timer

Enter the minimum time that must pass before the cellular phone can be answered.

Range: 0 - 10,000 milliseconds

Default: 1,500 milliseconds

Answer Too Late Timer

Enter the maximum time that can pass before the cellular phone must be answered.

Range: 10,000 - 300,000 milliseconds

Default: 19,000 milliseconds

Delay Before Ringing Timer

Enter the time that elapses before the cellular phone rings when a call is transferred from the desktop phone.

Range: 0 - 30,000 milliseconds

Default: 4,000 milliseconds

Remote Destination Profile

Select from the drop-down list box to assign this remote destination to a remote destination profile.

Allowed Access List

Select from the drop-down list box to add this remote destination to the allowed list.

Note You cannot add a remote destination to both the allowed and blocked access list.

Blocked Access List

Select from the drop-down list box to add this remote destination to the blocked list.

Note You cannot add a remote destination to both the allowed and blocked access list.

Mobile Phone

Select the check box if you want calls answered by the desktop phone to be sent to your cellular phone as the remote destination.

Note This check box must be selected for Mobile Connect to work with this remote destination.

Enable Mobile Connect

Select the box to allow an incoming call to ring your desktop phone and remote destination at the same time.

Smart Client Installed

Select the check box if the remote destination is a smartphone.


Configuring Mobile Voice Access Media Resources

The Mobile Voice Access window under Media Resources is used to assign sets of localized user prompts for Mobile Voice Access.

To assign localized users prompts or Mobile Voice Access, perform the following procedure:

Procedure


Step 1 Choose Media Resources > Mobile Voice Access.

Step 2 Enter values for the parameters described in Table 24-7.

Step 3 Click Save.


Mobile Voice Access Configuration Settings

Table 24-7 describes the available settings in the Mobile Voice Access window.

Table 24-7 Mobile Voice Access Configuration Settings 

Field
Description

Mobile Voice Access Directory Number

Enter the internal DN to receive Mobile Voice Access calls from the gateway.

Mobile Voice Access Partition

Choose a partition for Mobile Voice Access from the Mobile Voice Access Partition drop-down list box. The combination of directory number and partition makes the Mobile Voice Access directory number unique.

Available Locales

Use the arrows to move the locales that you do not want selected to this area.

Selected Locales

Use the arrows to move the locales that you want to select to this area.


Configuring H.323 Gateways for Mobile Voice Access

To configure H.323 gateways for Mobile Voice Access, you have two options available, depending on whether you are using PRI or not:

Configuring a H.323 Gateway for System Remote Access Using PRI

Configuring a H.323 Gateway for System Remote Access Using Hairpinning

Configuring a H.323 Gateway for System Remote Access Using PRI

If you already have an H.323 gateway configured in Cisco Unified Communications Manager, you can use it to support system remote access. If you do not have an H.323 gateway, then you must add and configure one. For more information, see the section on adding a Cisco IOS H.323 Gateway in the Cisco Unified Communications Manager Administration Guide.


Note When a Mobile Connect call is placed from an internal extension, only the internal extension is presented as the caller ID. If an H.323 gateway is used, you can use translation patterns to address this issue.


To configure the gateway, follow these steps.

Procedure


Step 1 Configure the T1/E1 controller for PRI from PSTN.

Sample configuration:

controller T1 1/0

framing esf

linecode b8zs

pri-group timeslots 1-24

Step 2 Configure the serial interface for the PRI (T1/E1).

Sample configuration:

interface Serial 1/0:23

ip address none

logging event link-status none

isdn switch-type primary 4ess

isdn incoming-voice voice

isdn bchan-number-order ascending

no cdp enable

Step 3 Load the VXML application from the Cisco Unified Communications Manager server (Publisher).

Sample configuration for IOS Version 12.3 (13) and later:

application service CCM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml

Sample configuration before IOS Version 12.3(12):

call application voice Unified CM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml


Note Although, VXML was added in Version 12.2(11), Versions 12.3(8), 12.3(9), 12.3(14)T1, and 12.2(15) have VXML issues and should not be used.


Step 4 Configure the dial-peer to associate Mobile Connect application with system remote access.

Sample configuration for IOS 12.3(13) and later:

dial-peer voice 58888 pots

service cmm

incoming called-number 58888

no digit-strip

Sample configuration for IOS 12.3(12) and earlier:

dial-peer voice 100 pots

application CMM (Mobile Connect VXML application)

incoming called-number 58888 (where 58888 is the Mobile Voice Access number)

no digit-strip

Step 5 Add a dial-peer to transfer the calls to the Mobile Voice Access DN configured in Configuring Mobile Voice Access Media Resources.

Sample configuration for primary Cisco Unified Communications Manager:

dial-peer voice 101 voip

preference 1

destination-number <Mobile Voice Access DN>


Note If a generic dial-peer is already configured to terminate the calls and is consistent with the Mobile Voice Access DN, then this step is not necessary.


session target ipv4:10.1.30.3

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad

Sample configuration for secondary Cisco Unified Communications Manager (if needed):

dial-peer voice 102 voip

preference 2

destination-number <Mobile Voice Access DN>


Note If a generic dial-peer already configured to terminate the calls and is consistent with the Mobile Voice Access DN, then this step is not necessary.


session target ipv4:10.1.30.4

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad


Configuring a H.323 Gateway for System Remote Access Using Hairpinning

If you do not have an H.323 gateway, and do not want to connect a separate PRI to H.323 gateway and want to use H.323 gateway only to support System Remote Access, then you must add and configure one. For more information, see the section on adding a Cisco IOS H.323 Gateway in the Cisco Unified Communications Manager Administration Guide.


Note When adding an H.323 gateway in Cisco Unified Communications Manager for hairpin configuration, you must check the Media Termination Point Required parameter. Without this parameter checked, calls might not complete properly for most gateway images


To configure the gateway, follow these steps.

Procedure


Step 1 Load the VXML application from the Cisco Unified Communications Manager server (Publisher).

Sample configuration for IOS Version 12.3 (13) and later:

application service CMM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml

Sample configuration before IOS Version 12.3(12):

call application voice CMM

http://<Unified CM cluster Publisher IP Addr>:8080/ccmivr/pages/IVRMainpage.vxml


Note Although VXML was added in Version 12.2(11); however, Versions 12.3(8), 12.3(9), 12.3(14)T1, and 12.2(15) have VXML issues and should not be used.


Step 2 Configure the dial-peer to associate Mobile Connect application with system remote access.

Sample configuration for IOS 12.3(13) and later:

dial-peer voice 1234567 voip

service CMM

incoming called-number 1234567

codec g711u

session target ipv4:<ip_address of call manager>

Sample configuration for IOS 12.3(12) and earlier:

dial-peer voice 1234567 voip

application CMM

incoming called-number 1234567

codec g711u

session target ipv4:<ip_address of call manager>

Step 3 Add a dial-peer for transferring calls to the outgoing CTI port.

Sample configuration for primary Cisco Communications Manager:

dial-peer voice 101 voip

preference 1

destination-number <Mobile Voice Access DN>


Note If a generic dial-peer is already configured to terminate the calls and is consistent with the Mobile Voice Access DN, then this step is not necessary.


session target ipv4:10.1.30.3

voice-class h323 1

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad

Sample configuration for secondary Cisco Communications Manager (if needed):

dial-peer voice 102 voip

preference 2

destination-number <Mobile Voice Access DN>


Note If a generic dial-peer already configured to terminate the calls and is consistent with the Mobile Voice Access DN, then this step is not necessary.


session target ipv4:10.1.30.4

voice-class h323 1

codec g711ulaw

dtmf-relay h245-alphanumeric

no vad

Step 4 Configure hairpin.

voice service voip

allow-connections h323 to h323


Configuring Mobility Settings

To configure mobility settings for handoff of dual mode phones between the Wi-Fi and Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA) networks, perform the following procedure:

Procedure


Step 1 Choose Call Routing > Mobility Configuration.

Step 2 Enter the DID number for handoff between the Wi-Fi and GSM or CDMA networks. This number is required for the handoff feature to work.

Step 3 From the drop-down list box, select the partition to which the handoff direct inward dial (DID) belongs.

Step 4 Enter the DID number required for enterprise feature access in the Enterprise Feature Access Directory Number field. This number is required to support transfer, conference, and resume, and for two-stage dialing from smartphones.


Note Each DID number must be unique.


Step 5 Select a partition for the enterprise feature access number from the drop-down list box.

Step 6 Click Save.


Mobility Configuration Settings

Table 24-5 describes the available settings in the Mobility Configuration window.

Table 24-8 Mobility Configuration Settings 

Field
Description

Handoff Number

Enter the DID number for handoff between the Wi-Fi and GSM or CDMA networks. This number is required for the handoff feature to work.

Handoff Partition

Select the partition to which the handoff direct inward dial (DID) belongs.

Enterprise Feature Access Directory Number

Enter the DID number required for enterprise feature access. This number is required to support transfer, conference, and resume, and for two-stage dialing from smartphones.

Enterprise Feature Access Directory Number Partition

Select the partition of the DID that is required for enterprise feature access.


Configuring Mobility Softkeys

To configure mobility handoff settings for dual mode phones that are used for Mobile Connect, perform the following procedure:

Procedure


Step 1 Choose Device > Device Settings > Softkey Template.

Step 2 Click Find to list the existing templates.

Step 3 Click Standard User and then click Copy to create the new template.

Step 4 Enter a name and description for the Softkey template and click Save.

Step 5 Select Configure Software Layout from the Go next to Related Link menu in the upper right corner of the page, and click Go.

Step 6 Select On Hook from the pull-down list box.

Step 7 Add Mobility to the selected Softkeys and click Save.

Step 8 Select Connected from the pull-down list box.

Step 9 Add Mobility to the selected Softkeys and Click Save.

Step 10 Open the Phone configuration page and associate the Softkey Template on the phone configuration page with the created Softkey template. See Configuring Cisco Unified IP Phones in the Cisco Unified Communications Manager Administration Guide.

Step 11 Select the Owner User ID for the Mobile Connect phone user.

Step 12 Click Save.


Additional Information

See the "Related Topics" section.

Related Topics

End User Configuration, Cisco Unified Communications Manager Administration Guide

Service Parameters Configuration, Cisco Unified Communications Manager Administration Guide

Additional Cisco Documentation

Cisco Unified Communications Manager Serviceability System Guide

Applicable Cisco Unified IP Phone User Guides

Applicable Cisco Unified IP Phone Administration Guides