1. Features and Applications for Multisite Deployments
Implementing Cisco Unified Mobility
Features and Applications for Multisite Deployments 1

2. Outline Cisco Unified Mobility Overview
Cisco Unified Mobility Call Flow
Cisco Unified Mobility Components
Cisco Unified Mobility Configuration

3. Cisco Unified Mobility Overview

4. Cisco Unified Mobility
Cisco Unified Communications Manager
Customer
Mobile Voice Access establishes a system to create enterprise calls from any location.
Call to Mobile Voice Access directory number.
Call to office number.
PSTN
Gateway
Mobile Connect lets remote and office phones ring simultaneously.
Remote Phone
Office Phone
Cisco Unified Mobility has two components: Mobile Connect and Mobile Voice Access (MVA).
With Mobile Connect, calls placed to office phones ring the office phones and associated remote phone.
MVA allows users to call into the enterprise from any phone and place outgoing calls that appear to come from their office phone.

5. Mobile Connect and MVA Characteristics
Mobile Connect characteristics:
Receive calls on multiple devices by using a single phone number
Answer incoming calls on office or remote phone
Switch active calls between office and remote phone
MVA characteristics:
Originate enterprise calls from any remote destination by:
Dialing to the enterprise MVA number
Entering ID (if required) and PIN
Entering destination number to be called
Called party sees the office phone number as the calling party

6. Cisco Unified Mobility Features
Single (office) number for multiple devices:
Enterprise caller ID preservation
Single enterprise voice mailbox
User-configurable access lists to permit or deny calling numbers that can ring a specific remote phone
User interface to enable or disable Cisco Unified Mobility:
Mobile Voice Access TUI
Cisco Unified Communications Manager user webpages
Access to enterprise features from remote phones using DTMF:
Softkeys can be used on phones with smart client installed.
Call logging (CDR)

7. Cisco Unified Mobility Call Flow

8. Mobile Connect Call Flow—Incoming Calls to Office Phone
Cisco Unified Communications Manager
Outside Caller
Gateway
XXX
Call to
Mobile Connect
PSTN
Caller ID:
Office Phone
2001
Remote Phone of 2001
Outside caller calls office phone 2001 (dials ).
Mobile Connect rings office phone and remote phone.
Call is picked up at remote phone; caller ID of outside caller is preserved at remote phone.

9. Mobile Connect Call Flow—Internal Calls Placed from Remote Phone
Cisco Unified Communications Manager
Gateway
XXX
Mobile Connect
Caller ID: 2001
Call to
PSTN
Office Phone
2001
2002
Remote Phone of 2001
Remote phone calls internal phone 2002 (dials ).
Mobile Connect replaces caller ID ( ) of remote phone with directory number of associated office phone (2001). 9

10. MVA Call Flow Remote phone dials MVA number (1-511-555-2999).
Cisco Unified Communications Manager
VoiceXML—Enter ID And PIN
Outside Destination
Gateway IVR Application
XXX
2999
Caller ID:
MVA
VoiceXML
PSTN
Call to
Office Phone 2001
Remote Phone of 2001
Remote phone dials MVA number ( ).
Caller is authenticated at Cisco Unified Communications Manager and requests call to outside destination
Caller is connected to MVA media resource from where the outgoing call is placed on behalf of the office phone (2001). 10

11. Cisco Unified Mobility
Components

12. Cisco Unified Mobility Requirements
Cisco Unified Mobility requires:
Cisco Unified Communications Manager 6.0
Cisco Unified Mobile Voice Access service activated
H.323 or SIP gateway providing Mobile Voice Access IVR application
Out-of-band DTMF
Remote Destinations must be external devices

13. Cisco Unified Mobility Configuration Elements
Configuration Element Name
Configuration Element Function
End User
The end user is referenced by the office phone and remote destination profile. Mobile Connect and/or MVA must be enabled. A maximum number of remote destinations can be configured.
Phone
The office phone needs to 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.
MVA Media Resource
Media resource used to interact with the VoiceXML call application running on a Cisco IOS router. Only required for MVA. 13

14. Shared Line Between Phone and Remote Destination Profile
Line1: 2001 Partition
CSS
etc.
Office Phone 1
MAC Address
Owner
CSS
etc.
Line1: 2002 Partition
CSS
etc.
Office Phone 2
MAC Address
Owner
CSS
etc.
shared line
shared line
Call to shared line rings office phone line and remote destination(s) associated with corresponding line of remote destination profile.
Remote Destination1:
Line1: 2001 Partition
CSS
etc.
Remote Destination Profile
User ID
CSS
Rerouting CSS
etc.
Remote Destination2:
Line2: 2002 Partition
CSS
etc. 14

15. Relationship of Cisco Unified Mobility Configuration Elements
Service Activation
MVA Service
Softkeys
Mobility Softkey
Owner
Service Parameter
Enable MVA, Enterprise Feature Access
IP phone
Owner
ACL
Media Resources
MVA Number, Localization
PIN
User
Enable Mobility
Enable MVA
RD Limit
User ID
RDP
IVR Application VoiceXML
Call MVA Enter RD and PIN
RD1
Enable MC
RD2
Enable MC
H.323 Gateway
ACL: Access List, MC: Mobile Connect, MVA: Mobility Voice Access, RD: Remote Destination, RDP: Remote Destination Profile 15

16. Cisco Unified Mobility Configuration

17. Cisco Unified Mobility—Mobile Connect Configuration Procedure
Configure Mobile Connect:
Add mobility softkey to IP phone softkey templates.
Configure end user.
Configure IP phone.
Configure remote destination profile with shared line.
Configure remote destination(s) to remote destination profile.
Configure service parameters.
Optional: Implement access lists to specify which caller ID is allowed to ring a remote destination when a call to the office phone is received.
Configure access lists.
Apply access lists to remote destination. 17

18. Step 1: Configure Softkey Template
Device > Device Settings > Softkey Template
Add the Mobility softkey to On Hook and to Connected call state.

19. Step 2: Configure End User
User Management > End User
Enable Mobile Connect for end user.
Set maximum number of remote destinations for end user. 19

20. Step 3: Configure IP Phone
Device > Phone
This line will be shared with remote destination profile.
Assign softkey template.
Set Owner User ID. 20

21. Step 4: Configure Remote Destination Profile
Device > Device Settings > Remote Destination Profile
CSS used for outgoing calls placed using MVA.
Click here and add line of office phone. After add, screen updates.
CSS used for ringing remote destination(s) when receiving a call at the office phone.
Note: Line is shared with office phone. Configured line CSS and partition apply to both devices: office phone and remote destination profile. Line CSS and device CSS are combined (partitions of line CSS considered first). 21

22. Step 5: Add Remote Destination(s) to Remote Destination Profile
Device > Remote Destination
Number of remote destination.
Line(s) of remote destination profile are shown only after setting remote destination profile and clicking Save.
Once saved, remote destination profile cannot be changed.
Allows transfers of active calls from office phone to remote destination using the Mobility softkey.
Associate remote destination with line(s) of remote destination profile.
Allows calls placed to office phones to also ring the remote destination. 22

23. Step 6: Configure Service Parameters
System > Service Parameters
If configured remote destination number does not match caller ID of remote phone (e.g., because of 9-1 prefix in remote destination number), change from Complete Match to Partial Match and set the number of digits that have to match.
Otherwise, calls to internal devices are not shown with caller ID of office phone. 23

24. Step 7a: Configure Access List
Device > Device Settings > Access List
Enter name and description and select owner.
Select type of ACL: Allowed (if checked) or Blocked (if unchecked)
Click Add Member for initial configuration of an access list member.
Click entry from list at bottom to change configuration of existing member. 24

25. Step 7b: Apply Access List to Remote Destination
Device > Remote Destination
Either allowed or blocked acess list can be set. If blocked access list is set, all numbers not listed in access list are allowed (and vice versa). 25

26. Cisco Unified Mobility—Mobile Voice Access Configuration Procedure
Configure MVA:
Activate Cisco Unified Mobile Voice Access Service.
Configure service parameters:
Enable MVA globally.
Enable and configure enterprise feature access.
Enable MVA per end user.
Configure MVA media resource.
Configure MVA VoiceXML application at Cisco IOS gateway. 26

27. Step 1: Activate Cisco Unified Mobile Voice Access Service
Cisco Unified Serviceability > Tools Service Activation 27

28. Step 2: Configure Service Parameters
System > Service Parameters
View default enterprise feature codes and change if required.
Enable access to enterprise features.
Enable MVA globally. 28

29. Step 3: Enable MVA per End User
User Management > End User
Enable MVA for end user. 29

30. Step 4: Configure MVA Media Resource
Media Resources > Mobile Voice Access
Enter number of MVA media resource.
The H.323 gateway running the MVA call application needs to have access to the partition of the MVA number (if set).
At least one locale has to be selected for the MVA media resource.

31. Step 5: Configure MVA at Cisco IOS Gateway
application
service mva !
voice-port 0/0/0:23
translation-profile incoming pstn-in
voice translation-profile pstn-in
translate called 1
voice translation-rule 1
rule 1 /.*5552\(...$\)/ /2\1/
dial-peer voice pots
service mva
incoming called-number 2999
direct-inward-dial
dial-peer voice voip
destination-pattern 2999
session target ipv4:
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
dial-peer voice 1 pots
destination-pattern 9T
incoming called-number 2...
direct-inward-dial
port 0/0/0:23 !
dial-peer voice 2 voip
destination-pattern 2...
session target ipv4:
incoming called-number 9T
codec g771ulaw

32. Summary
Mobile Connect enables users to receive calls placed to their enterprise number at the enterprise phone and remote phones such as cell phones. Mobile Voice Access extends the Mobile Connect functionality by allowing enterprise calls placed from a remote phone to first connect to the enterprise and then break back out to the called number using the enterprise number of the user as the calling number.
Mobile Voice Access requires an H.323 gateway providing an IVR application to Mobile Voice Access users.
The Cisco Unified Mobile Voice Access service must be activated in the Cisco Unified Communications Manager cluster for Mobile Voice Access.
Implementation of Cisco Unified Mobility includes the configuration of access lists, remote destination profile, and remote destinations.