This chapter provides information about functionality for Cisco
Mobile VoiP Clients which connect directly with
Cisco Unified Communications Manager. This chapter discusses the features and the
required configurations.
Beginning in Release 8.5(1) of
Cisco Unified Communications Manager, Cisco Mobile VoiP Clients register directly
with
Cisco Unified Communications Manager and no longer need to register with the
Cisco Unified Mobility Advantage server.
Note
The name
"Cisco Mobile" has also been used for several mobility clients
that require a
Cisco Unified Mobility Advantage server. Those clients
are unrelated to the clients that this chapter discusses. For more information
about those clients, see the
Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator integration
chapter.
Cisco Mobile is the name given to a family of clients that run
on mobile devices. Different Cisco Mobile clients offer different features.
Features may include the following:
Direct connection from
Cisco Unified Communications Manager to mobile client without proxy server
Dial-via-Office (DVO) optimization settings for toll reduction
Enable/disable Mobile Connect from mobile phone
Dial-via-Office Reverse Callback
Dial-via-Office Forward
Ability to transfer active Dial-via-Office calls between the mobile
device and the desktop phone
Complete configuration details about configuring the Cisco
Mobile VoiP Clients, see the following documentation:
See the end-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.
For more information on
Cisco Unified Mobility features that are available upon configuration of the
Cisco Unified Mobility Advantage server, see the
List of Cisco Mobile VoiP client features.
Cisco Mobile VoiP clients
This section provides information about Cisco Mobile VoiP clients.
Be aware that special configuration in
Cisco Unified Communications Manager Administration is required for features that
Cisco Mobile VoiP Clients provide.
The following table provides definitions of terms that are
related to
Cisco Unified Mobility with Cisco Mobile VoiP Clients.
Table 1 Definitions
Term
Definition
Cisco Mobile 8.x
These direct-connect dual-mode clients support
voice-over-Wi-Fi (for costing savings) in addition to cellular. They connect to
Cisco Unified Communications Manager directly without the need of a proxy
server.
List of Cisco Mobile VoiP client features
This section provides a list of
Cisco Unified Mobility features that are available to mobile phone users when the
Cisco Mobile VoiP Client has been configured. This material discusses
configuration within
Cisco Unified Communications Manager Administration.
The following entities and features require configuration of
Cisco Unified Mobility in
Cisco Unified Communications Manager Administration:
Direct connection from
Cisco Unified Communications Manager to mobile client without proxy server
- This feature provides server-side support for Cisco Mobile VoiP Clients to
connect to
Cisco Unified Communications Manager directly and thus eliminate
Cisco Unified Mobility Advantage in the deployment.
Cisco Unified Communications Manager adjusts to support direct connection
with the Cisco Mobile VoiP Client.
DVO Optimization Settings for Toll Reduction - This feature
supports a pre-configured policy to determine which mobile origination call
(DVO-R or DVO-F) yields the least cost to the enterprise; this determination is
typically based on locations. Administrators assign a profile based on the user
location and any other available information. Least cost routing negotiates
with
Cisco Unified Communications Manager to determine whether DVO-R or DVO-F
generates the least cost, then chooses the less costly method for making the
call.
Enable/Disable Mobile Connect From Mobile Phone - This feature
allows the Cisco Mobile VoiP Client to change the Mobile Connect status
dynamically and keep the Mobile Connect Status between
Cisco Unified Communications Manager and the client in sync. This feature
provides the flexibility to the end user: the end user can change the user
Mobile Connect status from the user mobile phone, not just from the GUI
website.
The following features, which were originally part of Cisco
Unified MobilityManager, now reside in
Cisco Unified Communications Manager:
Mobile Connect
Desktop Call Pickup
Access List
Cisco Unified Communications Manager also supports the
following
Cisco Unified Mobility features:
Midcall Enterprise Feature Support Using DTMF
Dual-mode Phone Support
Manual Handoff of Calls on a Dual-mode Phone
Time-of-Day Access
Directed Call Park via DTMF
SIP URI Dialing
See topics related to the benefits of Cisco Unified Mobility features
for a discussion of other benefits of
Cisco Unified Mobility features, such as simultaneous desktop ringing, single
enterprise voice mailbox, system remote access, caller ID, remote on/off
control, call tracing, security and privacy for Mobile Connect calls, and
smartphone support.
Registration between the Cisco Mobile VoiP Client and
Cisco Unified Communications Manager takes place over a separate TCP port.
(The shared or pooled connection that was used by the
Cisco Unified Mobility Advantage server is not used.)
Keepalive messages between the Cisco Mobile VoiP Client and
Cisco Unified Communications Manager remain the same as those passed
between
Cisco Unified Communications Manager and
Cisco Unified Mobility Advantage. Cisco Mobile VoiP
Client registration with
Cisco Unified Communications Manager introduces no new alarms, and
registration takes place over the SIP channel.
Figure 1. Cisco Mobile VoiP Client Registration With
Cisco Unified Communications Manager
If the client is running on the iPhone and the Cisco Mobile
VoiP Client is unable to complete the SIP dialog, the
Cisco Unified Communications Manager retains the PSTN call. (The PSTN call
does not drop even if the SIP stat times out.) For example, if
Cisco Unified Communications Manager does not receive an ACK message after
it sends a 200 OK message, the PSTN call gets retained.
Limitation for Direct Connection From
Cisco Unified Communications Manager to Mobile Client
This feature specifies the following limitation:
If the SIP dialog between
Cisco Unified Communications Manager and the Cisco Mobile VoiP Client is
not complete, the dialog cannot be used for further midcall feature
invocations. The user can, however, invoke midcall features through the DTMF
interface.
DVO optimization settings
This feature supports a pre-configured policy to determine
which mobile origination call (DVO-R or DVO-F) yields the least cost to the
enterprise; this determination is typically based on locations. This feature
benefits the mobile user by allowing the user to find the least cost when
making a mobile call. The DNIS pool provides a list of Direct Inward Dialing
(DID) numbers so that the user, if roaming, can choose a non-international
number for the mobile call. Least cost routing negotiates with
Cisco Unified Communications Manager to determine whether DVO-R or DVO-F
generates the least cost, then chooses the less costly method for making the
call.
Reasons for Least Cost Routing and DNIS Pool
The following reasons make this feature desirable:
Administrator can decide upon the DVO call type, DVO-F or DVO-R,
for least cost call routing. In certain regions and with certain service
providers, DVO-F can be more economical for mobile users; in other regions,
DVO-R can be more economical. For example, in regions where incoming calls are
free for mobile phone users, configuring a DVO-R call for mobile phone users
achieves least cost call routing.
Scalability - Multiple users in a given region can use a single
mobility profile, which comprises region, service provider, location, and so
forth. Here,
"users" refers to the clients under actual end users. The
administrator does not need to create a mobility profile for each end user.
Single DID within a cluster for all DVO-F calls - For such DVO-F
calls, the client makes an incoming call to
Cisco Unified Communications Manager by using a particular DID.
Multisite cluster - For a multisite cluster, a client in cluster A
(such as the UK) uses the DID of cluster B (such as San Jose) for DVO-F calls,
which incurs costs.
DVO-R - Trunk allows calls that originate from a local DID. At
times, when a client makes an outgoing DVO-R call, the client trunk may not
allow an outgoing call if the caller ID does not lie in a specific range. For
example, if a UK client invokes DVO-R, the callback call from the trunk at the
San Jose cluster shows 408. When this call reaches the UK, the service provider
trunk may not recognize the 408 and therefore not allow the call. Therefore,
the caller IDs need to specify the local identifiable values.
Characteristics of DVO Optimization Settings for Toll
Reduction
This feature involves the use of mobility profiles, which
the administrator configures by using the Call Routing > Mobility >
Mobility Profile menu path in
Cisco Unified Communications Manager Administration. See the
Mobility profile configuration
for additional details about mobility profiles.
The DVO Optimization Settings for Toll Reduction feature
does not change the alternate callback mechanism that DVO-R calls use: the
client continues to control alternate callback.
Limitation of DVO Optimization Settings for Toll Reduction
The DVO Optimization Settings for Toll Reduction feature
specifies the following limitation:
Least Cost Routing (LCR) rules are applied after application dial
rules. Called party transformations and call forward scenarios do not get
considered for LCR.
Enable/disable Mobile Connect From mobile phone
Prior to Release 8.5(1) of Cisco Unified Communications Manager, Cisco Unified Communications Manager sent Mobile Connect status updates to the Cisco Unified Mobile Communicator client via Cisco Unified Mobility Advantage by AXL messages. Direct SIP messages between the Cisco Mobile VoiP Client and Cisco Unified Communications Manager now allow the client to change the client Mobile Connect status.
Beginning with Release 8.5(1) of Cisco Unified Communications Manager, the Cisco Mobile VoiP Client can update its Mobile Connect status directly.
Interactions and limitations
Be aware that most standard
Cisco Unified Communications Manager features are fully compatible with
Cisco Unified Mobility features. See the chapter for Cisco Unified Mobility for
details of any exceptions.