Cisco Unified Communications Manager Features and Services Guide, Release 7.1(2)
Device Mobility
Downloads: This chapterpdf (PDF - 255.0KB) The complete bookPDF (PDF - 21.17MB) | Feedback

Device Mobility

Table Of Contents

Device Mobility

Configuration Checklist for Device Mobility

Introducing Device Mobility

Understanding How Device Mobility Works

Device Mobility Operations Summary

Device Mobility Groups Operations Summary

Network Considerations

Interactions and Restrictions

System Requirements

Installing Device Mobility

Configuring Device Mobility

Configuration Tips for Device Mobility

Enabling Device Mobility

Finding a Physical Location

Configuring a Physical Location

Physical Location Configuration Settings

Deleting a Physical Location

Finding Device Mobility Groups

Configuring a Device Mobility Group

Device Mobility Group Configuration Settings

Deleting a Device Mobility Group

Finding Device Mobility Info

Configuring Device Mobility Information

Device Mobility Info Configuration Settings

Deleting a Device Mobility Info

Configuring Device Pools for Device Mobility

Viewing Roaming Device Pool Parameters

Related Topics


Device Mobility


With Cisco Unified Communications Manager, a site or a physical location gets identified by using various settings, such as locations, regions, calling search spaces, and media resources. Cisco Unified IP Phones that reside at a particular site get statically configured with these settings, and Cisco Unified Communications Manager uses these settings for proper call establishment, call routing, media resource selection, and so forth. However, when phones get moved from the home location to a remote location, these phone retain the home settings that are statically configured on the phones. Cisco Unified Communications Manager uses these home settings for the phones that are located at the remote site, which may cause problems with call routing, codec selection, media resource selection, and other call processing functions.

You can configure device mobility, which allows Cisco Unified Communications Manager to determine whether the phone is at its home location or at a roaming location. Cisco Unified Communications Manager uses the device IP subnets to determine the exact location of the phone. By enabling device mobility within a cluster, mobile users can roam from one site to another and acquire the site-specific settings. Cisco Unified Communications Manager then uses these dynamically-allocated settings for call routing, codec section, media resource selection, and so forth.

This chapter includes information on the following topics:

Configuration Checklist for Device Mobility

Introducing Device Mobility

Understanding How Device Mobility Works

Device Mobility Operations Summary

Device Mobility Groups Operations Summary

Network Considerations

Interactions and Restrictions

System Requirements

Installing Device Mobility

Configuring Device Mobility

Viewing Roaming Device Pool Parameters

Related Topics

Configuration Checklist for Device Mobility

With Cisco Unified Communications Manager, a site or a physical location gets identified by using various settings, such as locations, regions, calling search spaces, and media resources. Cisco Unified IP Phones that reside at a particular site get statically configured with these settings, and Cisco Unified Communications Manager uses these settings for proper call establishment, call routing, media resource selection, and so forth. However, when phones get moved from the home location to a remote location, these phone retain the home settings that are statically configured on the phones. Cisco Unified Communications Manager uses these home settings for the phones that are located at the remote site, which may cause problems with call routing, codec selection, media resource selection, and other call processing functions.

You can configure device mobility, which allows Cisco Unified Communications Manager to determine whether the phone is at its home location or at a roaming location. Cisco Unified Communications Manager uses the device IP subnets to determine the exact location of the phone. By enabling device mobility, mobile users can roam from one site to another and acquire the site-specific settings. Cisco Unified Communications Manager then uses these dynamically-allocated settings for call routing, codec section, media resource selection, and so forth.

For more information on device mobility, see the "Introducing Device Mobility" section and the "Related Topics" section.

Table 18-1 shows the steps for configuring device mobility.

Table 18-1 Cisco Unified Communications Manager Device Mobility Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

Review the related device mobility documentation.

Tip For information on dial plan design considerations, refer to the Cisco Unified Communications Solution Reference Network Design (SRND), which provides information on building class of service if you use device mobility.

Cisco Unified Communications Solution Reference Network Design (SRND)

Device Mobility

Step 2 

Enable the device mobility mode in the Service Parameter Configuration or Phone Configuration window. (System > Service Parameters (choose Cisco CallManager service) or Device > Phone)

Viewing Roaming Device Pool Parameters

Step 3 

Configure physical locations. (System > Physical Location)

Configuring a Physical Location

Physical Location Configuration Settings

Step 4 

Configure device mobility groups. (System > Device Mobility > Device Mobility Groups)

Configuring a Device Mobility Group

Device Mobility Group Configuration Settings

Step 5 

Configure subnets and assign one or more device pools to a subnet in the Device Mobility Info window. (System > Device Mobility > Device Mobility Info)

Configuring Device Mobility Information

Device Mobility Info Configuration Settings

Step 6 

In the Device Pool Configuration window, update your device pools for device mobility settings, if you have not already done so. (System > Device Pool)

Configuring Device Pools for Device Mobility

Step 7 

If you have not already done so, update your dial plans for device mobility; for example, update calling search spaces, AAR group settings, and so on. (Call Routing > ...)

Location Configuration, Cisco Unified Communications Manager Administration Guide

Calling Search Space Configuration, Cisco Unified Communications Manager Administration Guide

Automated Alternate Routing Group Configuration, Cisco Unified Communications Manager Administration Guide

Introducing Device Mobility

With Cisco Unified Communications Manager, a site or a physical location gets identified by using various settings, such as locations, regions, calling search spaces, and media resources. Cisco Unified IP Phones that reside at a particular site get statically configured with these settings, and Cisco Unified Communications Manager uses these settings for proper call establishment, call routing, media resource selection, and so forth. However, when phones get moved from the home location to a remote location, these phone retain the home settings that are statically configured on the phones. Cisco Unified Communications Manager uses these home settings for the phones that are located at the remote site, which may cause problems with call routing, codec selection, media resource selection, and other call processing functions.

You can configure device mobility, which allows Cisco Unified Communications Manager to determine whether the phone is at its home location or at a roaming location. Cisco Unified Communications Manager uses the device IP subnets to determine the exact location of the phone. By enabling device mobility within a cluster, mobile users can roam from one site to another and acquire the site-specific settings. Cisco Unified Communications Manager then uses these dynamically-allocated settings for call routing, codec section, media resource selection, and so forth.

The dynamically reconfigured location settings ensure that voice quality and allocation of resources are appropriate for the new phone location:

When a mobile user moves to another location, call admission control (CAC) can ensure video and audio quality with the appropriate bandwidth allocations.

When a mobile user makes a PSTN call, the phone can access the local gateway instead of the home gateway.

When a mobile user calls the home location, Cisco Unified Communications Manager can assign the appropriate codec for the region.

Understanding How Device Mobility Works

When a phone device has mobility mode enabled, Cisco Unified Communications Manager uses the IP address of the registering device to find the proper location settings. The system compares the physical location that is configured in the device pool for the IP subnet and for the device to determine when a phone is away from its home location.

For example, phone A in Richardson with an IP address 10.81.17.9 registers with Cisco Unified Communications Manager. This IP address maps to subnet 10.81.16.0/16. Cisco Unified Communications Manager checks the device pool settings for the device and the subnet in the database. The physical location setting for the device pool in the phone record matches the physical location setting for the device pool in the subnet. The system considers the phone to be in its home location and uses the configuration settings in the phone record.

If phone A moves to Boulder, the phone queries the local DHCP server and gets an IP address of 130.5.5.25, which maps to subnet 130.5.5.0/8. Cisco Unified Communications Manager compares the physical location for the device pool in the phone record to the device pool location setting that is configured for the subnet. The system determines that the device is roaming because the physical locations do not match. Cisco Unified Communications Manager overwrites the phone record configuration settings with configuration settings for the subnet, downloads the settings in a new configuration file, and resets the device. The phone reregisters with the settings from the roaming device pool.


Note The phone must have a dynamic IP address to use device mobility. If a phone with a static IP address roams, Cisco Unified Communications Manager uses the configuration settings from its home location.


For roaming devices, Cisco Unified Communications Manager overwrites the following device pool parameters with the device pool settings for the subnet:

Date/Time Group

Region

Location

Network Locale

SRST Reference

Connection Monitor Duration

Physical Location

Device Mobility Group

Media Resource Group List

When networks span geographic locations outside the United States, you can configure device mobility groups to allow phone users to use their configured dial plan no matter where they roam. When a device is roaming but remains in the same device mobility group, Cisco Unified Communications Manager also overwrites the following device pool parameters:

AAR Group

AAR Calling Search Space

Device Calling Search Space

When the phone returns to its home location, the system disassociates the roaming device pool, downloads the configuration settings for home location, and resets the device. The device registers with the home location configuration settings.

Refer to these topics for more specific details about the device mobility operations in different scenarios:

Device Mobility Operations Summary

Device Mobility Groups Operations Summary

Device Mobility Operations Summary


Tip Cisco Unified Communications Manager always uses the Communications Manager Group setting from the phone record.The device always registers to its home location Cisco Unified Communications Manager server even when roaming. When a phone is roaming, only network location settings such as bandwidth allocation, media resource allocation, region configuration, and AAR group get changed.


Device Mobility Operations Summary

This section describes how Cisco Unified Communications Manager manages phone registration and assignment of parameters for device mobility.

Following initialization, the device mobility feature operates according to the following process:

1. A phone device record gets created for an IP phone that is provisioned to be mobile, and the phone gets assigned to a device pool. The phone registers with Cisco Unified Communications Manager, and an IP address gets assigned as part of the registration process.

2. Cisco Unified Communications Manager compares the IP address of the device to the subnets that are configured for device mobility in the Device Mobility Info window. The best match uses the largest number of bits in the IP subnet mask (longest match rule). For example, the IP address 9.9.8.2 matches the subnet 9.9.8.0/24 rather than the subnet 9.9.0.0/16.

3. If the device pool in the phone record matches the device pool in the matching subnet, the system considers the phone to be in its home location, and the phone retains the parameters of its home device pool.

4. If the device pool in the phone record does not match the device pools in the matching subnet, the system considers the phone to be roaming. Table 18-2 describes possible scenarios for device mobility and the system responses.

Table 18-2 Device Mobility Scenarios 

Scenario
System Response

The physical location setting in the phone device pool matches the physical location setting in a device pool that is associated with the matching subnet.

Note Although the phone may have moved from one subnet to another, the physical location and associated services have not changed.

The system does not consider the phone to be roaming, and the system uses the settings in the home location device pool.

The matching subnet has a single device pool that is assigned to it; the subnet device pool differs from the home location device pool, and the physical locations differ.

The system considers the phone to be roaming. It reregisters with the parameters of the device pool for the matching subnet.

The physical locations differ, and the matching subnet has multiple device pools assigned to it.

The system considers the phone to be roaming. The new device pool gets assigned according to a round-robin rule. Each time that a roaming devices comes in to be registered for the subnet, the next device pool in the set of available device pools gets assigned.

Physical location gets defined for the home device pool but is not defined for the device pools that are associated with the matching subnet

The physical location has not changed, so the phone remains registered in the home device pool.

Physical location that is not defined for the home device pool gets defined for the device pools that are associated with the matching subnet

The system considers the phone to be roaming to the defined physical location, and it registers with the parameters of the device pool for the matching subnet.

A subnet gets updated or removed.

The rules for roaming and assigning device pools get applied by using the remaining subnets.


Device Mobility Groups Operations Summary

You can use device mobility groups to determine when a device moves to another location within a geographic entity, so a user can use its own dial plan. For example, you can configure a device mobility group for the United States and another group for the United Kingdom. If a phone moves into a different mobility group (such as from the United States to the United Kingdom), Cisco Unified Communications Manager uses the Calling Search Space, AAR Group and AAR CSS from the phone record, and not from the roaming location.

If the device moves to another location with same mobility group (for example, Richardson, USA, to Boulder, USA), the CSS information will get taken from the roaming device pool settings. With this approach, if the user is dialing PSTN destinations, the user will reach the local gateway.

Table 18-3 describes the device pool parameters that the system uses for various scenarios.

Table 18-3 Device Mobility Group Scenarios 

Scenario
Parameters Used

A roaming device moves to another location in the same device mobility group.

Roaming Device Pool: yes

Location: Roaming device pool setting

Region: Roaming device pool setting

Media Resources Group List: Roaming device pool setting

Device CSS: Roaming device pool setting (Device Mobility CSS)

AAR Group: Roaming device pool setting

AAR CSS: Roaming device pool setting

A roaming device moves to another location in a different device mobility group.

Roaming Device Pool: yes

Location: Roaming device pool setting

Region: Roaming device pool setting

Media Resources Group List: Roaming device pool setting

Device CSS: Home location settings

AAR Group: Home location settings

AAR CSS: Home location settings

A device roams, and a device mobility group does not get defined for the home or roaming device pool.

Because the device is roaming, it takes the roaming device pool settings, including the Device Mobility Calling Search Space, AAR Calling Search Space, and AAR Group.


Network Considerations

The device mobility structure accommodates different network configurations.

For efficient device mobility design, divide the network into device mobility groups (optional), physical locations, and subnets. The number and levels of groups in the hierarchy depend on the size and complexity of the organization.

Device mobility groups represent the top-level geographic entities in your network. The device mobility group setting determines whether the device is moved within the same geographical entity, primarily to allow users to keep their own dial plans. The device mobility group defines a logical group of sites with similar dialing patterns (for example, US_dmg and EUR_dmg). For example, if you want a roaming device to access the local gateway for PSTN calls, be sure that the device mobility group for the home location device pool and roaming location device pool are the same.

Device mobility groups could represent countries, regions, states or provinces, cities, or other entities. An enterprise with a worldwide network might choose device mobility groups that represent individual countries, whereas an enterprise with a national or regional network might define device mobility groups that represent states, provinces, or cities. The system does not require defining device mobility groups to use the device mobility feature.

Physical location, the next level in the hierarchy, identifies a geographic location for device pool parameters that are location-based, such as date/time, region, and so on. Cisco Unified Communications Manager uses the geographic location to determine which network resources to assign to a phone. If a user moves away from the home location, the system ensures that the phone user uses local media resources and the correct bandwidth for the call.

For example, a Music on Hold (MOH) server may serve a specific office or campus within the enterprise. When a device roams to another office or campus and reregisters with Cisco Unified Communications Manager, having the device served by the MOH server at the roaming location represents best practice.

By defining the physical location according to availability of services such as MOH, you can assure efficient and cost-effective reassignment of services as devices move from one physical location to another. Depending upon the network structure and allocation of services, you can define physical locations based upon city, enterprise campus, or building.

Ideally, your network configuration places each network in one physical location, so a network can be mapped to a single physical location.

A subnet may include all the devices at a geographical location, within the same building, or on the same LAN. You can configure one or more device pools, including device mobility group and physical location, for a subnet.

Location identifies the CAC for a centralized call-processing system. You configure a location for a phone and a device pool. See the Call Admission Control chapter in the Cisco Unified Communications Manager System Guide for more information.


Tip For information on dial plan design considerations, refer to the Cisco Unified Communications Solution Reference Network Design (SRND), which provides information on building class of service if you use device mobility.


Interactions and Restrictions

Calling Party Normalization

Calling party normalization enhances the dialing capabilities of some phones and improves call back functionality when a call is routed to multiple geographical locations; that is, the feature ensures that the called party can return a call without the need to modify the directory number in the call log directories on the phone. Additionally, calling party normalization allows you to globalize and localize phone numbers, so the appropriate calling number presentation displays on the phone. For information on how calling party normalization works with device mobility, see the "Interactions and Restrictions" section on page 7-10 in the "Calling Party Normalization" chapter.

IP Address

The Device Mobility feature depends on the IPv4 address of the device that registers with Cisco Unified Communications Manager.

The phone must have a dynamic IPv4 address to use device mobility.

If the device is assigned an IP address by using NAT/PAT, the IP address that is provided during registration may not match the actual IP address of the device.

IPv6 and Device Mobility

Device mobility supports IPv4 addresses only, so you cannot use phones with an IP Addressing Mode of IPv6 Only with device mobility. For more information on IPv6, refer to the "Internet Protocol Version 6 (IPv6)" section on page 25-1.

Roaming

When a device is roaming in the same device mobility group, Cisco Unified Communications Manager uses the Device Mobility CSS to reach the local gateway. If a user sets Call Forward All at the phone, the CFA CSS is set to None, and the CFA CSS Activation Policy is set to With Activating Device/Line CSS, then:

The Device CSS and Line CSS get used as the CFA CSS when the device is in its home location.

If the device is roaming within the same device mobility group, the Device Mobility CSS from the Roaming Device Pool and the Line CSS get used as the CFA CSS.

If the device is roaming within a different device mobility group, the Device CSS and Line CSS get used as the CFA CSS.

For more information about configuration options for Call Forward All, refer to the Directory Number Configuration chapter in the Cisco Unified Communications Manager Administration Guide and the Understanding Directory Numbers chapter in the Cisco Unified Communications Manager System Guide.

System Requirements

Device Mobility requires the following software components:

Cisco CallManager service running on at least one server in the cluster

Cisco Database Layer Monitor service running on the same server as the Cisco CallManager service

Cisco TFTP service running on at least one server in the cluster

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

Any phone that is running either SCCP or SIP and that can be configured in Cisco Unified Communications Manager Administration supports device mobility, including

Cisco Unified IP Phone 7900 series

Cisco Unified IP Phone 30 VIP

Cisco Unified IP Phone 12 SP+

Computer Telephony Integration (CTI) Ports

Cisco IP Communicator

Installing Device Mobility

Device mobility automatically installs when you install Cisco Unified Communications Manager. After you install Cisco Unified Communications Manager, you must configure device mobility settings in Cisco Unified Communications Manager Administration to enable the feature.


Note Existing device pools automatically migrate to the new device pool and common profile structure as part of the upgrade to Cisco Unified Communications Manager Release 6.0 or later.


Configuring Device Mobility

For successful configuration of the device mobility feature, review the network design considerations, review the steps in the configuration checklist, perform the configuration requirements, and activate the Cisco CallManager service, if it is not already activated.

For an overview of device mobility parameter settings, refer to the following sections:

Configuration Tips for Device Mobility

Enabling Device Mobility

Configuring Device Pools for Device Mobility

Physical Locations

Finding a Physical Location

Configuring a Physical Location

Physical Location Configuration Settings

Deleting a Physical Location

Device Mobility Groups

Finding Device Mobility Groups

Configuring a Device Mobility Group

Device Mobility Group Configuration Settings

Deleting a Device Mobility Group

Device Mobility Info

Finding Device Mobility Info

Configuring Device Mobility Information

Device Mobility Info Configuration Settings

Deleting a Device Mobility Info


Tip Before you configure device mobility, review the "Configuration Checklist for Device Mobility" section.


Configuration Tips for Device Mobility

Consider the following information when you configure device mobility in Cisco Unified Communications Manager Administration:

When the Device Mobility Mode is set to Default in the Phone Configuration window, the Device Mobility Mode service parameter determines whether the device is enabled for the device mobility feature.

Cisco Unified Communications Manager uses the longest match rule to match IP addresses and subnets, meaning the best match uses the largest number of bits in the IP subnet mask. For example, the IP address 9.9.8.2 matches the subnet 9.9.8.0/24 rather than the subnet 9.9.0.0/16.

If no device mobility information entries match the device IP address, the device uses the home location device pool settings.

You assign the device pool to the phone device in the Phone Configuration window; you assign device pools to subnets in the Device Mobility Info Configuration window.

You can assign one or more device pools to a subnet address. Cisco Unified Communications Manager assigns device pools for the same subnet to roaming devices in round-robin fashion; for example, roaming device 1 gets assigned the first device pool in the list, and roaming device 2 gets assigned the second device pool in the list. This process allows you to load share when you expect a large number of phones to roam into an area, such as a meeting in the head office that employees from all branch locations will attend.

Although physical location does not represent a required setting in the Device Pool Configuration window, you must define a physical location for a device pool to use the device mobility feature. Be sure to configure physical location for the home location device pool and for the roaming device pool.

After the device mobility structure is in place, you can turn device mobility on for IP phones that support device mobility.

.Additional Information

See the "Related Topics" section.

Enabling Device Mobility

This section describes the procedure to enable the device mobility feature in the Service Parameter or Phone Configuration window.

Consider the following information when enabling the device mobility feature:

When device mobility mode is enabled or disabled for the cluster, the cluster setting applies to all phones in the cluster that support device mobility.At installation, the default setting for the Device Mobility Mode service parameter specifies Off, which means that device mobility is disabled.

When device mobility mode is enabled or disabled in the Phone Configuration window, the Device Mobility Mode phone settings take precedence over the service parameter setting.

When the phone setting for Device Mobility Mode equals Default, Cisco Unified Communications Manager uses the service parameter setting for the device.

Procedure


Step 1 To enable the Device Mobility service parameter, perform the following tasks:

a. Choose System > Service Parameters in Cisco Unified Communications Manager Administration.

b. From the Server drop-down list box, select the server that is running the Cisco CallManager service.

c. From the Service drop-down list box, select the Cisco CallManager service. The Service Parameters Configuration window displays.

d. To enable the Device Mobility Mode service parameter, choose On.

Step 2 To configure the Device Mobility Mode setting for a specific phone, perform the following tasks:

a. Choose Device > Phone in Cisco Unified Communications Manager Administration.

b. Click Find to display the device pools list, or use the search results from an active query.

c. Choose a device from the phone list that displays in the Find and List Phones window. The Phone Configuration window displays.

d. In the Device Mobility Mode drop-down list box, choose On to enable device mobility, choose Off to disable device mobility, or choose Default, which ensures that the phone uses the configuration from the Device Mobility Mode service parameter.


Finding a Physical Location

Because you may have several physical locations in your network, Cisco Unified Communications Manager lets you locate specific physical locations on the basis of specific criteria. Use the following procedure to locate physical locations.


Note During your work in a browser session, Cisco Unified Communications Manager Administration retains your physical location search preferences. If you navigate to other menu items and return to this menu item, Cisco Unified Communications Manager Administration retains your physical location search preferences until you modify your search or close the browser.


Procedure


Step 1 Choose System > Physical Location.

The Find and List Physical Locations 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, select a search parameter.

From the second drop-down list box, select 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.

Configuring a Physical Location

To add a physical location for a device pool, use the following procedure.

Procedure


Step 1 Choose System > Physical Location.

The Find and List Physical Locations window displays.

Step 2 Perform one of the following tasks:

To copy an existing physical location, locate the appropriate physical location as described in the "Finding a Physical Location" section, click the Copy button next to the physical location that you want to copy, and continue with Step 3.

To add a new physical location, click the Add New button and continue with Step 3.

To update an existing physical location, locate the appropriate physical location as described in the "Finding a Physical Location" section and continue with Step 3.

Step 3 Enter the appropriate settings as described in Table 18-5.

Step 4 To save the physical location information in the database, click Save.


Additional Information

See the "Related Topics" section.

Physical Location Configuration Settings

A physical location, which is used with the device mobility feature, identifies a geographic location for device pool parameters that are location-based, such as date/time, region, and so on. Cisco Unified Communications Manager uses the geographic location to determine which network resources to assign to a phone. If a user moves away from the home location, the system ensures that the phone user uses local media resources and the correct bandwidth for the call.

For example, a Music on Hold (MOH) server may serve a specific office or campus within the enterprise. When a device roams to another office or campus and reregisters with Cisco Unified Communications Manager, having the device served by the MOH server at the roaming location represents best practice.

By defining the physical location according to availability of services such as MOH, you can assure efficient and cost-effective reassignment of services as devices move from one physical location to another. Depending upon the network structure and allocation of services, you can define physical locations based upon city, enterprise campus, or building.

Ideally, your network configuration places each network in one physical location, so a network can be mapped to a single physical location. Depending upon the network structure and allocation of services, you may define physical locations based upon a city, enterprise campus, or building.

Refer to Device Mobility in the Cisco Unified Communications Manager Features and Services Guide for more information on the device mobility feature.

Table 18-5 describes the physical location configuration settings. For related procedures, see the "Related Topics" section.

Table 18-4 Physical Location Configuration Settings 

Field
Description
Physical Location Information

Name

Enter a name to identify the physical location. The name can contain up to 50 alphanumeric characters with any combination of spaces, periods (.), hyphens (-), underscore characters (_).

Description

Enter text describing the physical location. The description can contain up to 50 alphanumeric characters with any combination of spaces, periods (.), hyphens (-), underscore characters (_), as well as the following characters: * ( ) , + ^ @ ! $ = ~ ? / ; : '


Deleting a Physical Location

If a physical location is currently used in a device pool, you cannot delete it. To delete the physical location, you can first find the associated device pools from the dependency record and disassociate them before deleting the physical location.

To delete a physical location, use the following procedure.

Procedure


Step 1 To locate the physical location that you want to delete, follow the procedure on "Finding a Physical Location" section.

Step 2 Check the check box next to the physical locations that you want to delete. To select all the physical locations in the window, check the check box in the matching records title bar.

Step 3 Click Delete Selected.

Step 4 To confirm your selection, click OK.


Additional Information

See the "Related Topics" section.

Finding Device Mobility Groups

Because you may have several device mobility groups in your network, Cisco Unified Communications Manager lets you locate specific device mobility groups on the basis of specific criteria. Use the following procedure to locate device mobility groups.


Note During your work in a browser session, Cisco Unified Communications Manager Administration retains your device mobility group search preferences. If you navigate to other menu items and return to this menu item, Cisco Unified Communications Manager Administration retains your device mobility group search preferences until you modify your search or close the browser.


Procedure


Step 1 Choose System > Device Mobility > Device Mobility Group.

The Find and List Device Mobility Groups 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, select a search parameter.

From the second drop-down list box, select 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.

Configuring a Device Mobility Group

To configure a device mobility group, which supports the device mobility feature, use the following procedure.

Procedure


Step 1 Choose System > Device Mobility > Device Mobility Group.

The Find and List Device Mobility Groups window displays.

Step 2 Perform one of the following tasks:

To copy an existing device mobility group, locate the appropriate device mobility group as described in the "Finding Device Mobility Groups" section, click the Copy button next to the device mobility group that you want to copy, and continue with Step 3.

To add a new device mobility group, click the Add New button and continue with Step 3.

To update an existing device mobility group, locate the appropriate device mobility group as described in the "Finding Device Mobility Groups" section and continue with Step 3.

Step 3 Enter the appropriate fields as described in Table 18-5.

Step 4 Click Save to save the device mobility group information to the database.


Additional Information

See the "Related Topics" section.

Device Mobility Group Configuration Settings

Device mobility groups support the device mobility feature. Device mobility groups represent the highest level geographic entities in your network. Depending upon the network size and scope, your device mobility groups could represent countries, regions, states or provinces, cities, or other entities. For example, an enterprise with a worldwide network might choose device mobility groups that represent individual countries, whereas an enterprise with a national or regional network might define device mobility groups that represent states, provinces, or cities.


Tip The device mobility group defines a logical group of sites with similar dialing patterns (for example, US_dmg and EUR_dmg).


Refer to Device Mobility in the Cisco Unified Communications Manager Features and Services Guide for more information on the Device Mobility feature.

Table 18-5 describes the device mobility group configuration settings. For related procedures, see the "Related Topics" section.

Table 18-5 Device Mobility Group Configuration Settings 

Field
Description
Device Mobility Group Information

Name

Enter a name to identify the device mobility group.

Description

Enter the description of the profile.


Deleting a Device Mobility Group

If a device mobility group is currently used in a device pool, you cannot delete it. To delete the device mobility group, you must find the associated device pools from the dependency record, disassociate them, and then delete the device mobility group.

Procedure


Step 1 To locate the device mobility group that you want to delete, follow the procedure in "Finding Device Mobility Groups" section.

Step 2 Check the check box next to the device mobility groups that you want to delete. To select all the device mobility groups in the window, check the check box in the matching records title bar.

Step 3 Click Delete Selected.

Step 4 To confirm your selection, click OK.


Additional Information

See the "Related Topics" section.

Finding Device Mobility Info

Because you may have several device mobility info records in your network, Cisco Unified Communications Manager lets you locate specific device mobility information on the basis of specific criteria. Use the following procedure to locate device mobility information.


Note During your work in a browser session, Cisco Unified Communications Manager Administration retains your device mobility info search preferences. If you navigate to other menu items and return to this menu item, Cisco Unified Communications Manager Administration retains your device mobility info search preferences until you modify your search or close the browser.


Procedure


Step 1 Choose System > Device Mobility > Device Mobility Info.

The Find and List Device Mobility Infos 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, select a search parameter.

From the second drop-down list box, select 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.

Configuring Device Mobility Information

To add device mobility information, use the following procedure.

Procedure


Step 1 Choose System > Device Mobility > Device Mobility Info.

The Find and List Device Mobility Infos window displays.

Step 2 Perform one of the following tasks:

To copy an existing device mobility info, locate the appropriate device mobility info as described in the "Finding Device Mobility Info" section, click the Copy button next to the device mobility info that you want to copy, and continue with Step 3.

To add a new device mobility info, click the Add New button and continue with Step 3.

To update an existing device mobility info, locate the appropriate device mobility info as described in the "Finding Device Mobility Info" section and continue with Step 3.

Step 3 Enter the appropriate fields as described in Table 18-5.

Step 4 To save the device mobility info information to the database, click Save.


Additional Information

See the "Related Topics" section.

Device Mobility Info Configuration Settings

The Device Mobility Info window specifies the subnets and device pools that are used for device mobility. When a phone registers with Cisco Unified Communications Manager, the system compares the IP address of the device to the subnets that are configured for device mobility in the Device Mobility Info window. The best match uses the largest number of bits in the IP subnet mask (longest match rule). For example, the IP address 9.9.8.2 matches the subnet 9.9.8.0/24 rather than the subnet 9.9.0.0/16.

If the device pool in the phone record matches the device pool in the matching subnet, the system considers the phone to be in its home location, and the phone retains the parameters of its home device pool.

If the device pool in the phone record does not match the device pools in the matching subnet, the system considers the phone to be roaming. Table 18-2 describes possible scenarios for device mobility and the system responses.

Table 18-5 describes the device mobility info configuration settings. For related procedures, see the "Related Topics" section.

Table 18-6 Device Mobility Info Configuration Settings 

Field
Description
Device Mobility Info Information

Name

Enter a name to identify the device mobility info record.

Subnet

Enter the device mobility subnet in dotted decimal format; for example, xxx.xxx.xxx.xxx.

Subnet Mask (bits size)*

Enter the device mobility subnet mask. Based on the bit mask, this value represents the number of IP addresses that are included in this subnet; for example, 24, which represents a standard class C subnet bit mask.

The value does not need to match the subnet mask on the phone.

Device Pools for This Device Mobility Info

Available Device Pools

Choose a device pool in the Available Device Pools list box by clicking the down arrow button between the two list boxes.

To add multiple device pools that are listed consecutively, click the first device pool in the range; then, hold down the Shift key while clicking the last device pool in the range. Click the down arrow button between the two list boxes to add the device pools.

To add multiple device pools that are not listed consecutively, hold down the Control (Ctrl) key while clicking device pools. Click the down arrow button between the two list boxes to add the chosen device pools.

Selected Device Pools

Select any device pools that you would like to remove from the device mobility record and double-click or use the up arrow to move the device pool back to the Available Device Pools field.


Deleting a Device Mobility Info

If you delete a device mobility info that is currently used by a device, Cisco Unified Communications Manager reapplies the appropriate device mobility rules according to the descriptions in the Device Mobility chapter of the Cisco Unified Communications Manager Features and Services Guide.

To delete a device mobility info record, use the following procedure.

Procedure


Step 1 To locate the device mobility info that you want to delete, follow the procedure in the "Finding Device Mobility Info" section.

Step 2 Check the check box next to the device mobility record that you want to delete. To select all the records in the window, check the check box in the matching records title bar.

Step 3 Click Delete Selected.

Step 4 To confirm your selection, click OK.


Additional Information

See the "Related Topics" section.

Configuring Device Pools for Device Mobility

The roaming sensitive settings in the Device Pool Configuration window override the device-level settings when the device roams within or outside a of device mobility group. The settings, which include Date/time Group, Region, Media Resource Group List, Location, Network Locale, SRST Reference, Physical Location, Device Mobility Group, and so on, provide call admission control and voice codec selection. Additionally, these settings update the media resource group list (MRGL), so appropriate remote media resources get used for music on hold, conferencing, transcoding, and so on. The roaming sensitive settings also update the Survivable Remote Site Telephony (SRST) gateway. Mobile users register to a different SRST gateway while roaming. This registration may affect the dialing behavior when the roaming phones are in SRST mode.

The device mobility related parameters in the Device Pool Configuration window override the device-level settings only when the device is roaming within a device mobility group. The device mobility related settings affect the dial plan because the calling search space dictates the patterns that can be dialed or the devices that can be reached.

Refer to Device Pool Configuration in the Cisco Unified Communications Manager Administration Guide to configure device pool parameters.

Viewing Roaming Device Pool Parameters

When the phone has device mobility mode enabled, you can view the roaming device pool settings by clicking View Current Device Mobility Settings next to the Device Mobility Mode field in the Phone Configuration window. If the device is not roaming, the home location settings display.

Related Topics

Configuration Checklist for Device Mobility

Introducing Device Mobility

Understanding How Device Mobility Works

Device Mobility Operations Summary

Device Mobility Groups Operations Summary

Network Considerations

Interactions and Restrictions

System Requirements

Installing Device Mobility

Configuring Device Mobility

Viewing Roaming Device Pool Parameters

Calling Party Normalization, page 7-1

Internet Protocol Version 6 (IPv6), page 25-1

Device Pool Configuration, Cisco Unified Communications Manager Administration Guide

Service Parameters Configuration, Cisco Unified Communications Manager Administration Guide

Common Device Configuration, Cisco Unified Communications Manager Administration Guide

Location Configuration, Cisco Unified Communications Manager Administration Guide

Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide

Survivable Remote Site Telephony Configuration, Cisco Unified Communications Manager Administration Guide

Automated Alternate Routing Group Configuration, Cisco Unified Communications Manager Administration Guide

Date/Time Group Configuration, Cisco Unified Communications Manager Administration Guide

Region Configuration, Cisco Unified Communications Manager Administration Guide

Calling Search Space Configuration, Cisco Unified Communications Manager Administration Guide

Media Resource Group Configuration, Cisco Unified Communications Manager Administration Guide

Call Admission Control, Cisco Unified Communications Manager System Guide

System-Level Configuration Settings, Cisco Unified Communications Manager System Guide

Cisco TFTP, Cisco Unified Communications Manager System Guide

Additional Cisco Documentation

Cisco Unified Communications Solution Reference Network Design (SRND)

Cisco Unified Serviceability Administration Guide

Troubleshooting Guide for Cisco Unified Communications Manager