This chapter provides information about 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.
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 phones
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.
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 phones
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.
Perform the following steps to configure device mobility.
Procedure
Step 1
Review the related device mobility documentation.
Tip
For information on dial plan design considerations,
see the
Cisco Unified Communications Solution Reference Network Design (SRND),
which provides information on building class of service if you use 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)
Configure subnets and assign one or more device pools to a subnet
in the Device Mobility Info Configuration window.
(System > Device
Mobility > Device Mobility Info)
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)
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 > ...)
Related Tasks
Related References
Related Information
Device Mobility feature
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 phones 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.
Device Mobility description
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.
Tip
Cisco Unified Communications Manager always uses the Communications Manager
Group setting from the phone record. The Communications Manager Group setting
applies to the single server in a
Cisco Business Edition 5000 system. 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.
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:
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.
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 Configuration 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. The
following table describes possible scenarios for device mobility and the system
responses.
Table 1 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.
The following table describes the device pool parameters
that the system uses for various scenarios.
Table 2 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
Cisco Unified Communications Manager System Guide for more
information.
Tip
For information on dial plan design considerations, see 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
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, see the
Internet Protocol Version 6 (IPv6).
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, see the
Cisco Unified Communications Manager Administration Guide and 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 CallManager service running on the server
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 TFTP service running on the server
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 6900 series (except 6901 and 6911)
Cisco Unified IP Phone 7900 series
Cisco Unified IP Phone 8900 series
Cisco Unified IP Phone 9900 series
Computer Telephony Integration (CTI) Ports
Cisco IP Communicator
For more information about IP Phones and the device mobility
feature, see the user guides at the following sites:
Use the
Cisco Unified Reporting application to generate a complete list of devices
that support device mobility. To do so, follow these steps:
Start
Cisco Unified Reporting by using any of the methods that follow.
The system uses the Cisco Tomcat service to authenticate users
before allowing access to the web application. You can access the application
by choosing
Cisco Unified Reporting in the Navigation menu in
Cisco Unified Communications Manager Administration and clicking
Go.
by choosing
File > Cisco Unified Reporting at the Cisco Unified
Real Time Monitoring Tool (RTMT) menu.
by entering https://<server name or IP
address>:8443/cucreports/ and then entering your authorized username and
password.
Click
System Reports in the navigation bar.
In the list of reports that displays in the left column, click the
Unified CM Phone Feature List option.
Click the Generate a new report link to generate a new report, or
click the Unified CM Phone Feature List link if a report already exists.
To generate a report of all devices that support device mobility,
choose these settings from the respective drop-down list boxes and click the
Submit button:
Product: All
Feature: Mobility
The List Features pane displays a list of all devices that support
the mobility feature. You can click on the Up and Down arrows next to the
column headers (Product or Protocol) to sort the list.
For additional information about the
Cisco Unified Reporting application, see the
Cisco Unified Reporting Administration Guide, which you
can find at this URL:
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.
Configure Device Mobility
For successful configuration of the Device Mobility feature,
review the network design considerations, review the steps in the configuration
summary task, perform the configuration requirements, and activate the Cisco
CallManager service, if it is not already activated.
This section provides information to configure and enable Device Mobility, including configuring device pools for device mobility, physical location parameters, Device Mobility groups, and other Device Mobility information parameters. Instructions to delete Device Mobility information is also provided.
Tip
Before you configure device mobility, review the
configuration summary task 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.
Enable Device Mobility
This section describes the procedure to enable the device
mobility feature in the Service Parameter or Phone Configuration window.
Note
In a
Cisco Business Edition 5000 system, the cluster
setting applies to the single server. For example, enabling device mobility for
a cluster in a
Cisco Business Edition 5000 system means enabling it
for the single server.
Consider the following information when enabling the device
mobility feature:
When device mobility mode
is enabled or disabled, the setting applies to all phones for the server 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:
Choose
System > Service
Parameters in
Cisco Unified Communications Manager Administration.
From the Server drop-down list box, select the server that is
running the Cisco CallManager service.
From the Service drop-down list box, select the Cisco
CallManager service. The Service Parameters Configuration window displays.
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:
Choose
Device > Phone
in
Cisco Unified Communications Manager Administration.
Click
Find to display the device pools list, or
use the search results from an active query.
Choose a device from the phone list that displays in the Find
and List Phones window. The Phone Configuration window displays.
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.
Find 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 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
To find all records in the database, ensure the dialog box is
empty, 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.
Configure 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
Find a Physical location,
click the
Copy button next to the physical location
that you want to copy, and continue with
Step Configure a Physical location.
To save the physical location information in the database, click
Save.
Physical location configuration
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.
The following table describes the physical location
configuration settings. For related procedures, see the
Device Mobility.
Table 3 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 include up to 50 characters in any language, but it cannot include
double-quotes (“), percentage sign (%), ampersand (&), or angle brackets
(<>).
Delete 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
Find a Physical location.
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.
Find 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 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
To find all records in the database, ensure the dialog box is
empty, 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.
Configure 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
Find Device Mobility groups,
click the
Copy button next to the device mobility
group that you want to copy.
To add a new device mobility group, click the
Add New button.
To update an existing device mobility group, locate the
appropriate device mobility group as described in the
Find Device Mobility groups.
Click
Save to save the device mobility group
information to the database.
Device Mobility group configuration
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).
The following table describes the device mobility group
configuration settings. For related procedures, see the
Device Mobility.
Table 4 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. The description can
include up to 50 characters in any language, but it cannot include
double-quotes (“), percentage sign (%), ampersand (&), or angle brackets
(<>).
Delete 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
Find Device Mobility groups.
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.
Find Device Mobility information
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 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 seTo find all records in the database,
ensure the dialog box is emptyarch 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
To find all records in the database, ensure the dialog box is
empty, 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.
Configure 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
Find Device Mobility information,
click the
Copy button next to the device mobility
info that you want to copy.
To add a new device mobility info, click the
Add New button.
To update an existing device mobility info, locate the
appropriate device mobility info as described in the
Find Device Mobility information.
To save the device mobility info information to the database,
click
Save.
Device Mobility information configuration
The Device Mobility Info Configuration 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 Configuration 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.
Device Mobility operations summary
describes possible scenarios for device mobility and the system responses.
The following table describes the device mobility info
configuration settings. For related procedures, see the
Device Mobility.
Table 5 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.
Delete a Device Mobility information
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.
To delete a device mobility info record, use the following
procedure.
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.
Configure 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.
See the
Cisco Unified Communications Manager Administration Guide to configure
device pool parameters.
View 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.