This topic lists the requirements for implementing and installing Cisco Unified Mobility.
Cisco Unified Mobility requires:
- Cisco Unified Communications Manager
- Cisco Unified Mobile Voice Access service activated
- H.323 or SIP gateway providing Mobile Voice Access IVR application
- OOB DTMF
- Remote destinations must be external devices
To implement Cisco Unified Mobility features, you must start the Cisco Unified Mobile Voice Access service, which interacts with the call application that runs on a Cisco IOS gateway, on at least one Cisco Unified Communications Manager system.
Mobile Voice Access requires an H.323 or SIP gateway to provide a VXML call application to remote callers who dial a certain number. MGCP is not supported because it does not support call applications.
The remote destination cannot be an IP phone within the enterprise. The remote destination must be an external device, typically a PSTN number. As many as 10 remote destinations can be configured. CoS can be configured, to limit access to the PSTN.
Cisco Unified Mobility Configuration Elements
The figure lists the configuration elements of Cisco Unified Mobility and describes their functions.
|Configuration Element Name||Configuration Element Function|
|End user||The end user is referenced by the office phone and remote destination profile. Mobile Connect or Mobile Voice Access must be enabled. A maximum number of remote destinations can be configured.|
|Phone||The office phone must be configured with an owner (i.e., the end user).|
|Remote destination profile||A virtual phone device. Per office phone number, a shared line is configured. End user, (device) CSSs, and MOH audio sources are specified. One or more remote destinations are added.|
|Remote destination||Associated with shared line(s) of remote destination profile. Configured with destination number. Optionally, access lists can be applied. Mobile phone and Mobile Connect functions are selectively enabled.|
|Access list||Filters used to permit or deny incoming calls placed to the office phone to ring a remote destination. Permitted or denied caller IDs are specified.|
|Mobile Voice Access media resource||Media resource used to interact with the VXML call application running on a Cisco IOS router. Required for Mobile Voice Access only.|
The configuration elements and their functions are as follows:
- End user: Each end user must have a configured PIN that is used for authentication when Mobile Voice Access is used. Three important Cisco Unified Mobility-related settings can be configured for the end user:
- Enable Mobility: This check box must be checked to allow the user to use the Mobile Connect feature (that is, to receive enterprise calls at one or more remote destinations and to place calls from a remote phone into the enterprise).
- Enable Mobile Voice Access: This check box must be checked to allow the user to place Mobile Voice Access calls. These calls are outgoing enterprise calls that are placed from a remote phone on behalf of the office phone.
- Remote Destination Limit: This setting is used to limit the number of remote destinations that can be configured. The maximum is 10.
- IP phone: The office phone of a Cisco Unified Mobility user must refer to the end-user name. This task is done by setting the owner in the Phone Configuration window to the user ID of the end user.
In the End User Configuration window, the end user can be associated with one or more devices, such as IP phones. Such an association allows the end user to configure the device from the Cisco Unified Communications Manager user web pages, but it is not relevant for Cisco Unified Mobility. The mapping of the IP phone to the end user must be done by setting the owner in the Phone Configuration window.
- Remote destination profile: This setting creates a virtual phone that is linked to the end user and that represents all remote destinations that are associated with the user. The profile includes phone device-level configuration settings, such as user and network MOHaudio sources and CSSs. For each office phone that an end user should be able to use for Cisco Unified Mobility, a shared line with the line or lines of the office phone or phones must be added to the remote destination profile. In addition, the remote destination profile is configured with remote destinations.
- Remote destination: A remote destination is associated with one or more shared lines of a remote destination profile. For each remote destination, the remote destination number, as dialed from within the enterprise, must be specified. The rerouting CSS of the specified remote destination profile is used to look up the configured remote destination number.
The remote destination profile has two CSSs that are used for call routing. One standard CSS is used for outgoing calls that are initiated by using Mobile Voice Access and the rerouting CSS. The rerouting CSS is used to place a call to the remote destination (when receiving a call to the number of the line that is shared by the office phone and the remote destination profile, or when a call is handed over from the office phone to the remote destination). Therefore, the remote destination number must be reachable by the rerouting CSS. For Mobile Voice Access calls, the rerouting CSS is composed of the CSS that is configured at the shared line and the CSS of the remote destination profile (with priority to the CSS of the shared line).
- Access list: Access lists can be configured to permit or deny calls that are placed to a remote destination when the shared line is called. The filter is based on the calling number. An access list is configured with one or more numbers that specify the calling number that should be permitted or denied. Access lists are also configured with an owner (end-user ID) and are applied to remote destinations. You can apply an allowed list, a blocked list, or no access list. If an allowed access list is applied, all calling numbers that are not listed in the access list are blocked. If a blocked access list is applied, all unlisted numbers are allowed. If no access list is applied, all calling numbers are allowed to ring the remote destination.
- Mobile Voice Access media resource: This media resource interacts with the VXML call application that runs on the Cisco IOS gateway. The resource is required for Mobile Voice Access only. The number at which the Cisco IOS router can reach the media resource must be specified, a partition can be applied, and one or more locales must be chosen.
The CSS of the gateway that runs the VXML call application must include the partition that is applied to the number of the Mobile Voice Access media resource.
Shared Line Between Phone and Remote Destination Profile
The figure illustrates how a remote destination profile shares its line or lines with the associated Cisco IP phone or phones.
A remote destination profile is associated with one or more IP phones. Each phone line that an end user should be able to use with Cisco Unified Mobility must be added to the remote destination profile that is associated with the end user. The directory number for the user is thus associated with two devices: the IP phone and the remote destination profile. Such a directory number is also called a shared line. The IP phone or phones that share a line with the remote destination profile must be owned by the end user who is associated with the remote destination profile.
Remote destinations are associated with one or more shared lines that are configured at remote destinations.
The settings of the shared directory number (including the partition and CSS) apply to all associated devices. The remote destination profile is configured with a (standard) CSS, which is used for calls that a remote phone places when it uses Mobile Voice Access, and a rerouting CSS, which is applicable to calls that are placed to a remote destination.
For example, if a call is placed to directory number 2002, Line1 at Office Phone2 rings and all remote destinations that are associated with Line2 of the remote destination also ring. For the call to the remote destination number, the rerouting CSS is used.
If the remote phone with number 9 1 479 555-1555 calls in to the mobile voice application and requests an outgoing call to be placed, the CSS of Line2 and the CSS of the remote destination profile are used for the outgoing enterprise call that Remote Destination2 initiates.
Relationship of Cisco Unified Mobility Configuration Elements
The figure shows how Cisco Unified Mobility configuration elements interact with one another.
To use Cisco Unified Mobility, the Cisco Unified Mobile Voice Access service must be activated if Mobile Voice Access is necessary in addition to Mobile Connect functionality.
When the Cisco Unified Mobile Voice Access service is activated, a corresponding media resource is automatically added. The media resource must be configured with the Mobile Voice Access number, a partition, and locales.
The configured number must be reachable from the Cisco IOS router that provides remote phones with access to a VXML IVR call application.
Incoming Mobile Voice Access callers are authenticated by remote destination number. Callers are also authenticated by the PIN that is configured for the user who is associated with the remote destination profile that the corresponding remote destination number references.
When Mobile Connect is used and incoming calls are sent to a line that is shared by an IP phone and a remote destination profile (both referring to the same end-user ID), access lists that are applied to remote destinations can be used to control which callers are allowed to ring the remote destination. The access list must refer to the end user who is configured in the remote destination profile to which the remote destination has been assigned.
To allow an active call to be handed over from an IP phone to a remote destination, the IP phone must have the Mobility softkey configured for the Connected call state. If the Mobility softkey is also added to the On Hook call state, the softkey can be used to check the status of Cisco Unified Mobility (Mobile Connect on or off).
In summary, the end user is the central element that is associated with IP phones (at which the user is configured as the owner), access lists, and remote destination profiles. Remote destinations are associated with shared lines of remote destination profiles and access lists. For Mobile Voice Access, the appropriate service must be activated, and the automatically generated media resource is made available to a router that runs the VXML call application.