This chapter
provides information about
Cisco Unified Mobile
Communicator clients in conjunction with a
Cisco Unified Mobility
Advantage server. This chapter discusses the features and the
required configurations on both servers.

See the user guide for a
particular
Cisco Unified IP
Phone for procedures that end users follow to configure the
Cisco Unified
Mobility settings for their phones by using the
Cisco Unified CM User
Options windows.

Note

For details of
configuring
Cisco Unified
Mobility features that you configure within
Cisco Unified Communications
Manager and that do not require configuration of
Cisco Unified Mobile
Communicator nor
Cisco Unified Mobility
Advantage, see the Cisco Unified Mobility chapter.

For more information on
Cisco Unified Mobility features that are native to
Cisco Unified Communications Manager and that do not require configuration
of
Cisco Unified Mobile Communicator nor
Cisco Unified Mobility Advantage, see the
List of Cisco Unified Mobility Features
in the
Cisco Unified Mobility chapter.

Cisco Unified Mobility with Cisco Unified Mobility Advantage

Administrators configure the basic setup of
Cisco Unified Mobility for end users by using the
Cisco Unified Communications Manager Administration windows. See the
Cisco Unified Mobility chapter for
details.

Be aware that special configuration in
Cisco Unified Communications Manager Administration is required for features that
the
Cisco Unified Mobile Communicator provides on user phones in conjunction
with the
Cisco Unified Mobility Advantage server.

This section provides a list of
Cisco Unified Mobility features that are available to mobile phone users when the
required configuration for
Cisco Unified Mobility Advantage has also been
performed. This material discusses configuration within
Cisco Unified Communications Manager Administration.

For a complete discussion of
Cisco Unified Mobility Advantage configuration, see the
following documentation:

Session Resumption - This feature provides one-touch reconnect to
the last dialed target in case of any unexpected DVO-F call drop. This feature
helps users who are making DVO-F calls and who experience a network failure.
Prior to the implementation of this feature, if the mobile user pressed Redial
(either by calling the last dialed number from the phone call history or by
pressing Call Back if the phone provides such an option), the redial number
specified the Dial-via-Office Forward Feature Access Number (configured under
Service Parameter) or Enterprise Feature Access Number (configured under Call
Routing > Mobility > Enterprise Feature Access Number Configuration).
Cisco Unified Communications Manager treated the call as an Enterprise
Feature Access call, and the user could not connect to the last redial target.
With the implementation of this feature, when the user presses Redial,
Cisco Unified Communications Manager reconnects the mobile user with the
actual target DN.

The following features, which were originally part of Cisco
Unified Mobility Manager, now reside in
Cisco Unified Communications Manager:

Cisco Unified Mobile Communicator

The
Cisco Unified Mobile Communicator specifies a device type that you can
configure in
Cisco Unified Communications Manager Administration in the Phone Configuration
window. The
Cisco Unified Mobile Communicator uses Mobility Multiplexing Protocol (MMP)
to communicate via the mobile phone data connection with the
Cisco Unified Mobility Advantage server, which in turn registers the device
with
Cisco Unified Communications Manager through SIP. The
Cisco Unified Mobile Communicator uses one Device License Unit (DLU) if the
user has a desktop phone and three DLUs if the user does not have a desktop
phone.

Mobility User ID
- You must configure this field. You can only choose the user ID of an end user
for which the Enable Mobility check box in the Mobility Information pane of the
End User Configuration window (User
Management > End User) has been checked.

Mobility
Identity - This field must specify the
Cisco Unified Mobile
Communicator-enabled smartphone mobile number as the destination
number. Be aware that the Mobility Identity configuration characteristics are
identical to those of the Remote Destination configuration. To access the
field, click the Add New Mobility Identity link in the Phone Configuration
window, which takes you to the Remote Destination Configuration window so that
you can add a mobile identity.

Rerouting
Calling Search Space - Ensure that this field is configured for basic calls to
work. This setting applies to the
Cisco Unified Mobile
Communicator. This setting gets used to route calls to the mobility
identity (that is, the
Cisco Unified Mobile
Communicator client phone). The setting gets used to route the
Dial-via-Office callback call leg toward the mobility identity and to route the
call leg toward the mobility identity for Cisco Unified Mobility and SNR calls.

Calling Search
Space - Ensure that this field is configured for basic calls to work. This
setting gets used to route calls from the mobility identity. The setting gets
used to route the call leg toward the dialed or target phone for
Dial-via-Office calls.

Ensure
that a directory number is assigned to the
Cisco Unified Mobile
Communicator.

Keep in
mind these other configuration requirements that apply to the
Cisco Unified Mobile
Communicator:

Due to the lack
of an integrated End User Configuration window for
Cisco Unified Communications
Manager and the
Cisco Unified Mobility
Advantage server, the
Cisco Unified Mobile
Communicator client user must configure identical remote destination
numbers in both
Cisco Unified Communications
Manager Administration and in the
Cisco Unified Mobility
Advantage server.

If a
Cisco Unified Mobile
Communicator client user ever changes his SIM card, the user must
update the mobile number in the
Cisco Unified Mobility
Advantage server by deleting the old mobile phone number and adding
the new mobile phone number. The corresponding configuration must take place in
Cisco Unified Communications
Manager Administration as well.

General
Considerations

Keep in
mind the following general considerations for the
Cisco Unified Mobile
Communicator device:

You can add one
or more remote destinations in addition to the mobility identity to the
Cisco Unified Mobile
Communicator device (similar to the remote destination profile).

No automatic
migration support exists. You must manually reconfigure the device as a
Cisco Unified Mobile
Communicator device.

Only the first
call gets supported because, in 2.5G, the data channel does not remain
available after the voice call connects.

The
Cisco Unified Mobility
Advantage server can activate only one
Cisco Unified Mobile
Communicator device per user. (A user can have multiple mobile phones
configured within
Cisco Unified Mobility
Advantage, but only one of mobile phones can be actively connected to
the
Cisco Unified Mobility
Advantage server at a given time.)

In all Dial-via-Office scenarios, the callback leg from
Cisco Unified Communications Manager either to the
Cisco Unified Mobile Communicator client mobile
phone/mobility identity or to an alternate number always specifies the caller
ID of the Enterprise Feature Access DID. The caller ID that gets sent for the
call leg from
Cisco Unified Communications Manager to the target or dialed number always
specifies the user enterprise desk number (based on the shared line between the
user desktop phone and the
Cisco Unified Mobile Communicator client device type
that is configured within
Cisco Unified Communications Manager).

Example of Dial-via-Office Reverse Callback

The following example illustrates the sequence of events
that takes place in an instance of dial-via-office reverse callback:

User invokes the Dial-via-Office feature on the phone and calls
target DN 2000.

Phone sends INVITE 2000 with the callback number that is specified
in the SDP parameter
"c=PSTN E164 4085551234."

Cisco Unified Communications Manager sends back 183 Session In Progress
with Enterprise Feature Access Number DID (4085556666) in SDP parameter.

Use Case Scenarios

Limitations for Dial-via-Office Reverse Callback Feature

See the
Limitations
for a list of limitations that apply to this feature.

Dial-via-Office Forward Configuration

Users that have Cisco Mobile, a
Cisco Unified Mobile Communicator application,
installed on their mobile devices can take advantage of the Dial-via-Office
Forward feature.
Cisco Unified Mobile Communicator invokes the
Dial-via-Office Forward feature from the mobile device through SIP signaling
over the data channel between
Cisco Unified Mobile Communicator-Cisco Unified Mobility Advantage and
Cisco Unified Mobility Advantage-Cisco Unified Communications Manager to initiate calls to a final target. Because the calls are
anchored at the enterprise, the feature offers a cost-saving solution to
Cisco Unified Mobile Communicator mobile users.

Cisco Unified Communications Manager returns the
Dial-via-Office Forward (DVO-F) service access number, if the DVO-F service
access number has been configured, or the Enterprise Feature Access (EFA)
directory number (DN) through the data channel. The
Cisco Unified Mobile Communicator client that runs on
the mobile phone calls the number that it receives from
Cisco Unified Communications Manager. The phone number of the mobile device
that makes the DVO-F call gets matched against configured Mobility Identities
(MI), thus ensuring that the system places only those calls that authorized
users make. If a match occurs, the call request gets sent to the target party.
Both complete match and partial match get supported, depending on the setting
of the Matching Caller ID with Remote Destination service parameter.

For limitations that apply to the Dial-via-Office Forward feature, see
Limitations.

If the
Cisco Unified Mobile Communicator caller ID that the
Cisco Unified Communications Manager receives does not match the
provisioned MI completely, perform the following configuration:

Set the Matching Caller ID with Remote Destination service
parameter to Partial Match.

Specify the number of matched digits in the Number of Digits
for Caller ID Partial Match service parameter.

Make sure the ingress gateway gets configured properly, so the
called party number matches either the EFA DN or the DVO-F Service Access
Number service parameter.

If the called party number is expected to match the EFA DN, ensure
that the Inbound Calling Search Space for Remote Destination service parameter
is set properly as follows:

If the Trunk or Gateway Inbound Calling Search Space option is
chosen, the EFA DN partition must belong to the trunk or gateway calling search
space.

If the Remote Destination Profile + Line Calling Search Space
option is chosen, the EFA DN partition must belong to the calling search spaces
of the
Cisco Unified Mobile Communicator device and its
enterprise DN.

Dial-via-Office Forward Service Access Number

The Dial-via-Office Forward Service Access Number service
parameter provides customers the option to set up a dedicated number for
Cisco Unified Mobile Communicator users to dial DVO-F
while
Cisco Unified Communications Manager receives the calls on a different
number (for example, through 1-800 support). The DVO-F service access number
can specify a toll-free 1-800 number, which the service provider can map to a
local number that reaches the enterprise or to any other alternative number for
Cisco Mobile clients to invoke DVO-F calls.

The Dial-via-Office Forward Service Access Number service
parameter has the following characteristics:

Length specifies up to 24 dialable digits.

Does not specify a partition.

The Dial-via-Office Service Access Number service parameter
interacts with the existing Enterprise Feature Access (EFA) DN as follows:

The EFA DN must be configured to invoke the DVO-F feature. Whether
DVO-F service access number is configured or not, the EFA DN terminates the
inbound call from the
Cisco Unified Mobile Communicator device.

For the 183 Session in progress message response, the following
rules apply:

If the Dial-via-Office Forward Service Access Number service
parameter number is configured,
Cisco Unified Communications Manager sends this
alternative number to
Cisco Unified Mobility Advantage in SDP.

Called party number gets matched against either the EFA DN or
the DVO-F service access number. Either Partial Match or Complete Match takes
place. The Partial/Complete Match matches the calling number with the calling
number in the original SIP INVITE message that the
Cisco Unified Mobility Advantage forwarded to
Cisco Unified Communications Manager.

Actually this is not accurate. Certainly, the system expects
the inbound DVO-F call leg from CUMC to be to (called number) EFA DN or DVO-F
service access number. But once the call is received on that number, called
number is no longer important. The Partial/Complete Match portion is matching
the calling number and the match is not made against the EFA/DVO-F service
access number, but the calling number specified in the original SIP INVITE
forwarded to Unified CM by CUMA.

If a match is found, the voice call correlates with the
original SIP Invite, and the Call Await Timer gets stopped. Next, a call gets
extended to the called number or target number that the user originally dialed
and that the SIP Invite that the
Cisco Unified Communications Manager received from
Cisco Unified Mobility Advantage contains.

If no match is found, after the Call Await Timer expires, the
call disconnects, and the 503 Service Unavailable message gets sent.

Globalization Support for EFA DN and DVO-F Service Access Number

Both the Enterprise Feature Access Directory Number and the
Dial-via-Office Forward Service Access Number support the following dialable
digits:

0 through 9

+, which must be preceded by backslash (\). Because backslash is
not a dialable digit, it does not count toward the maximum length of 24 digits.

* and #

A through D

The preceding special characters can occur in any position.

Dial-via-Office Forward Call Characteristics

The following example illustrates the sequence of events
that takes place in an instance of Dial-via-Office Forward (DVO-F):

Cisco Unified Mobile Communicator autodials the number
that the SDP specifies.

Cisco Unified Communications Manager correlates this voice call with the
SIP data channel call by comparing the calling party number with the Mobility
Identity and by comparing the called party number with the EFA DN or the DVO-F
service access number.

The call then progresses normally.

Using the preceding example, the following characteristics
apply to a Dial-via-Office Forward call:

Based on the INVITE SDP parameter
"a=setup:active,"Cisco Unified Communications Manager determines that the Cisco Mobile
client wants to initiate a DVO-F call.

The Call Await Timer, which is set to 30 seconds, starts when
Cisco Unified Communications Manager sends the 183 Session In Progress
message to
Cisco Unified Mobility Advantage.

If the
Cisco Unified Communications Manager does not receive a PSTN call from
Cisco Unified Mobile Communicator before the Call Await
Timer expires,
Cisco Unified Communications Manager sends a
"503 Service Unavailable" message and clears resources that
are associated with the DVO-F Invite.

When a PSTN call arrives, the following attempts at matching take
place:

Cisco Unified Communications Manager tries to match the
calling party number against known Mobility Identities (MIs) to determine
whether the call will get anchored.
Cisco Unified Communications Manager performs the match
based on the option that is set for the Matching Caller ID with Remote
Destination service parameter (either Partial Match or Complete Match).

Cisco Unified Communications Manager also tries to
match the called party number against the EFA DN or DVO-F service access number
and determines whether the call is a DVO-F call.

After the call gets established, the user can invoke other
Cisco Unified Mobility features, such as hold, resume, conference,
transfer, and desk pickup.

Confirmed Answer and DVO VM Detection

Single Number Reach (SNR) voice mail is a mobility enhancement to Cisco Unified Communications Manager that determines if users answer a call on their mobile devices from a remote destination (RD). By detecting if a RD call offered to mobile users reaches an external voice mail system, this feature provides users with a single enterprise voice mail box for their enterprise mobility.

In order to prevent calls being answered by the mobile service provider voice mail, Unified CM implements a timer that determines whether or not the mobile service provider voice mail answers a call. This is required to avoid situations where a mobile phone is switched off or unreachable. The network diverts immediately to mobile voice mail.

Note

The single number reach voice mail feature is not supported for dusting calls.

Device Level Setting for RD/MI

For each RD and MI, there is a drop-down list box to configure the voice mail Selection Policy for supported devices. Acceptable values are Default, Timer Control and User Control. The RD/MI page setting overrides the system wide setting. When you select Default, Unified CM defaults to the system setting via a service parameter.

Timer Control

Timer Control uses the Answer Too Soon timer to determine whether a call is answered by the mobile user or mobile service provider voice mail. If a call is answered within the Answer Too Soon Timer, SNR voice mail determines that mobile service provider voice mail answered the call. As a result, this feature drops this call leg and reroutes the call to enterprise voice mail if no other shared line or remote destination answers the call.

User Control

When the user control is applied, Unified CM expects to receive an explicit notification in the form of a DTMF digit, even after the voice channel connects a call.

Depending on the VoiceMail Selection User Control Delayed Announcement Timer, Unified CM may not insert any announcement. When you apply user control, Unified CM ensures that the PSTN side answers the call before extending the call.

If the client is not registered, the announcement always plays for RD or MI.

Note

In case of a failure scenario, Unified CM tries to send an error message that indicates the call failure via data channel. For SendCallToMobile, Unified CM displays the following error message on the desk phone with SendCallToMobile enabled:

Call fail due to Voicemail selection failure, please retry or contact system administrator.

Cisco Unified Communications Manager Administration Considerations

The following service parameters in Unified CM allow you to define the behavior of SNR voice mail.

Voice Mail Selection Policy

The Voice Mail Selection Policy drop-down allows you to select either Timer Control or User Control. The default is set to Timer Control.

Voice Mail Selection User Control Delayed Announcement Timer

Unified CM uses this timer to delay the announcement that is played to RD users after they answer an RD call.

If Unified CM receives a user answer notification in DTMF or a data channel that the smart phone client generated, Unified CM does not play the announcement and connects the calling and called parties.

If Unified CM does not receive a user answer notification within the allotted time, Unified CM plays an announcement that prompts users to enter a DTMF digit to have their call connected.

If the client is able to send the DTMF digits or a notification via the data channel, the client ensures that the system sends the explicit answer notification after a user answers the call.

The default is set to 1 second.

Voice Mail Selection User Control Confirmed Answer Indication Timer

Cisco Unified Mobility uses this timer to wait for an answer notification, either from the received DTMF or from the mobile client via a data channel. When the timer expires, Cisco Unified Mobility drops the call.

The default is set to 5 seconds.

Note

The Unified CM service parameter at the system level controls Single Number Reach Voice mail. The RD/MI device level setting controls the feature as well, however, the device level setting overrides the system setting. Unified CM uses the system setting if the device level setting is set to Default.

Session Resumption

The Session Resumption feature allows the user to call back
to a meeting (after a signal loss) without inputting the meeting ID and
password again.

Mobile call failure is very common in the cellular network.
For DVO-F calls, the dialed number that is stored on the mobile handset
specifies the DVO-F service access number, which is an internally configured
DID number. When the user presses Redial on the user handset (either by calling
the last dialed number from the phone call history or by pressing Call Back if
the phone provides such an option), the stored number has already been dialed,
so
Cisco Unified Communications Manager cannot reach the original target.

Upon implementation of the Session Resumption feature,
Cisco Unified Communications Manager stores the target number DN when the
DVO-F call initially gets made. If the user presses Redial after a network
failure,
Cisco Unified Communications Manager receives the call for the DVO-F
service access number, which Unified CM replaces with the stored target DN.
Thus, the redial request succeeds: either a new call gets extended to the
original target, or the original call gets reconnected, depending on whether
the original call got released.

For a list of limitations that apply to the Session Resumption feature, see Limitations.

Configuration Details

The following configuration details apply to the Session
Resumption feature.

The Session Resumption feature uses the setting of the Session
Resumption Await Timer service parameter, which you configure in the Service
Parameter Configuration window (System > Service Parameters) for the Cisco
CallManager service in the Clusterwide Parameters (System - Mobility) pane. The
Session Resumption Await Timer service parameter has a default setting of
180 seconds (3 minutes), but can be set to any value between 0 seconds and
300 seconds (5 minutes). Setting the Session Resumption Await Timer service
parameter to 0 seconds disables the timer and the Session Resumption feature.

After the Session Resumption Await Timer expires in the case of a
DVO-F call that was interrupted due to network failure, the record of the
original target DN for this DVO-F call gets deleted. Any Redial call that is
placed after the timer expires gets invoked as an enterprise feature access
(EFA) call: the Session Resumption feature does not get triggered.

If a Redial call gets extended to a busy target DN, the user
receives a busy tone.

Use Case Scenarios for Cisco Unified Mobility Features

This section describes use case
scenarios for Dial-via-Office Reverse, Dial-via-Office Forward, and session resumption that
Cisco Unified Communications Manager supports for
Cisco Unified Mobility features if the required configuration for
Cisco Unified Mobility Advantage is also performed:

Enterprise provides a 1-800 toll-free number for DVO-F calls.
Enterprise sets up a toll-free number, which may be mapped to an actual number (ring-to number) when the service provider receives the call.
If the ring-to number gets applied, administrator must configure the toll-free number (for example, 18008889999) by using the Dial-via-Office Forward Service Access Number service parameter and the ring-to number (for example, 4081239876) as the EFA DN.
Example
EFA DN = 1239876 (localized format, depending on service provider)
DVO-F Service Access Number service parameter = 18008889999
Cisco Unified Communications Manager sends 18008889999 in 183 Session in progress message and receives PSTN call, which maps to 1239876.

Enterprise provides globalized number for DVO-F calls
Enterprise sets up a globalized access number, which allows its Cisco Unified Mobile Communicator users to invoke the DVO-F calls anywhere in the world without the need to know the international escape code for the country where they are located.
If the service provider delivers only a localized number, administrator must configure the globalized number (for example, \+14081239876) as the DVO-F Service Access Number service parameter and the localized number that Cisco Unified Communications Manager receives (for example, 1239876) as the EFA DN.
Example
EFA DN = 1239876 (localized format, depending on service provider)
DVO-F Service Access Number service parameter = \+14081239876 (requires backslash as escape for + character)
Cisco Unified Communications Manager sends +14081239876 in message 183 Session in progress and receives PSTN call, which maps to 1239876.

Use Case Scenarios for Session Resumption

The Session Resumption feature supports the following use case scenarios.

Session Resumption Use Case 1: New Call to Target

In the case of a DVO-F Redial call where a new call gets made to the target, the following steps take place:

User makes DVO-F call, for example, to target DN 1000.

While user and target are in a call, a mobile network failure happens.

Cisco Unified Communications Manager finds that target (1000) was the last target, stops MOH, and reconnects user with the target who was still waiting for user.

Note that no new call is extended to DN 1000: only media switching takes place as the original call to DN 1000 gets reconnected. From the DN 1000 user point of view, when a network failure occurs, DN 1000 first hears MOH. After a few seconds, if the mobile user pressed Redial before the desk pickup timer expires, the original call reconnects and the parties continue the call.

Interactions and Limitations

Be aware that most standard
Cisco Unified Communications Manager features are fully compatible with
Cisco Unified Mobility features; however, some exceptions do exist. See topics in this chapter that are related to interactions and limitations for details.

Additionally, the limitations that apply to features that
require
Cisco Unified Mobility Advantage and
Cisco Unified Mobile Communicator functionality are detailed in this section.

Dial-via-Office Limitations (DVO-R and DVO-F)

Only one outstanding DVO-F call that is getting established from a
particular
Cisco Unified Mobile Communicator device can be
supported at a time.

DVO-F cannot support simultaneous calls from a single
Cisco Unified Mobile Communicator device.

DVO-F can support two simultaneous DVO-F calls from a single
Cisco Unified Mobile Communicator device.

DVO-F relies on caller ID in the SIP Invite message to correlate a
PSTN call with the SIP call:

If the calling party number or called party number cannot go
through the mobile voice network (for example, GSM), the DVO-F call fails. A
standard service provider announcement plays.
Cisco Unified Communications Manager sends a 503
Service Unavailable message after the Call Await Timer expires.

If
Cisco Unified Communications Manager does not receive
the calling party number (that is, the
Cisco Unified Mobile Communicator user blocks his or
her caller ID), the DVO-F call fails. A reorder tone will play.
Cisco Unified Communications Manager sends the 503
Service Unavailable message after the Call Await Timer expires.

Session Resumption Limitation

The Session Resumption feature specifies the following
limitation:

Session Resumption feature provides support only for
Dial-via-Office Forward calls.

The
Configure Cisco Unified Mobility of the
Cisco Unified Mobility chapter provides an overview
checklist of the procedures and steps that are necessary for an administrator
to configure
Cisco Unified
Mobility features that are native to
Cisco Unified Communications
Manager.

The
Cisco Unified Mobility Configuration of the
Cisco Unified Mobility chapter provides detailed procedures
for each
Cisco Unified Communications
Manager Administration menu option that must be configured to
provision
Cisco Unified
Mobility features that are native to
Cisco Unified Communications
Manager. The section covers configuration of the following entities
in
Cisco Unified Communications
Manager Administration:

Access lists

Remote
destination profiles (You do not need nor use these resources for integration
with
Cisco Unified Mobility
Advantage.)

Remote
destinations

Mobile voice
access media resources (You do not need nor use these resources for integration
with
Cisco Unified Mobility
Advantage.)

H.323 and SIP
gateways for mobile voice access (You do not need nor use these resources for
integration with
Cisco Unified Mobility
Advantage.)

Enterprise
feature access two-stage dialing (Integration with
Cisco Unified Mobility
Advantage does not require configuration of this feature; however,
configuration of the Enterprise Feature Access DID is needed because this DID
provides the caller ID that
Cisco Unified Communications
Manager sends for Dial-via-Office callback call legs.)

Mobility
Enterprise Feature configuration

Mobility
profiles

Handoff mobility
configuration

Mobility
softkeys

End users use the
Cisco Unified CM User
Options windows to further configure or modify the
Cisco Unified
Mobility settings that apply to their mobile phones.

For the
steps that are necessary to configure
Cisco Unified Mobility
Advantage with
Cisco Unified Communications
Manager to provide
Cisco Unified
Mobility features that require
Cisco Unified Mobility
Advantage, see the following documentation: