Soluciones de Movilidad Corporativa Con Comunicaciones Unificadas

Mobility: Enabling the Mobile Worker With Cisco Unified Communications
BRKUCC-2060
Cisco Unified Communications Enterprise Mobility Solutions

Yves Torjman Consulting Systems Engineer Emerging Market ytorjman@cisco.com
Cisco Mobility Applications chapter (from the Unified Communications Solution Reference Network Design (SRND) at www.cisco.com/go/ucsrnd):
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/mobilapp.html
BRKUCC-2060 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
BRKUCC-2060 Abstract
This session covers Cisco's unified communications enterprise mobility solutions and in particular the following three solutions:
1. 2. 3. Cisco Unified Mobility Dual-mode phones and clients Cisco Unified Mobile Communicator
These solutions provide a comprehensive set of mobility features and functions for enterprise mobile workers and ensures that mobile workers have persistent reachability and access to enterprise voice services regardless of location.
Individually or in tandem the three solutions not only provide enterprise connectivity to mobile users, but they also provide productivity improvements both for the mobile user as well as users inside the enterprise that the mobile user may communicate with. At the end of the session it will be clear how these solutions work to provide a seamless mobility solution for enterprise mobile workers.
The following will *NOT* be covered in this session: Campus mobility Enterprise wireless phones, intra-campus roaming, and device mobility Dual cellular radio and non-802.11 dual-mode phones Mobile phones with dual cellular radios or non-802.11 wireless radios like DECT BRKUCC-2060 Cisco Confidential 2010 Cisco and/or its affiliates. All rights reserved. 4
Agenda
Cisco UC Mobility Solutions Overview Cisco Unified Mobility
Dual-Mode Phones and Clients

Cisco Unified Mobile Communicator Cisco UC Mobility Solutions Summary
BRKUCC-2060
2010 Cisco and/or its affiliates. All rights reserved.
Cisco Confidential
Cisco Unified Mobility

Unified Mobility User

Enterprise
PSTN
Fully integrated feature set within Cisco Unified Communications Manager (Unified CM) 6.0 and later. Includes the following features: Mobile Connect Mobile Voice Access (MVA) and Enterprise Feature Access (EFA) 2 Stage-Dialing Mid-Call Features Single Enterprise Voicemail Box Access Lists and Time of Day Call Filtering


Enterprise
PSTN
Mobile Voice Network

WLAN
(802.11b/g)
WLAN AP
Enables mobile phones to leverage the enterprise IP telephony infrastructure for making and receiving calls. When associated to the enteprise Cisco Unified Wireless Network, the mobile phone uses SCCP or SIP client to register with Cisco Unified CM as a phone. When the WLAN coverage is unavailable, the mobile phone uses the mobile voice network for calls
Cisco Unified Mobile Communicator

Cisco Unified Mobility Solution allows mobile users to access enterprise applications from their mobile
phones using a mobile client Mobile phone client provides access to enterprise applications and services like call processing, conferencing, presence, voicemail, and corporate directory. Enterprise Client connects to Cisco Unified Mobility Advantage server in the enterprise via PSTN secure data connection
WLAN
(802.11b/g)
WLAN AP
BES (w./ MDS)
Internet
BRKUCC-2060 2010 Cisco and/or its affiliates. All rights reserved.
ASA TLS Proxy

Cisco Confidential
Cisco Unified Mobility Advantage

8
Cisco Unified Mobility with Cisco Unified Communications Manager
BRKSPM-2604_c1
Cisco Confidential

Agenda Feature Review and Basic Functionality
Dial Plan Considerations

Design and Deployment Considerations
BRKUCC-2060
Cisco Confidential
10

Feature Review and Basic Functionality
BRKSPM-2604_c1
Cisco Confidential
11

Configuration and Call Routing Concept
Remote Destination Profile
Virtual Phone
IP Phone
Shared Line Line Level Settings DN: 408 555-1234 Partition Calling Search Space
Remote Destination Profile Level Configuration

Device Pool Calling Search Space Rerouting CSS User Hold Audio Source Network Hold Audio Source
Call Routing and Media Resource Allocation for Remote Destinations
Call Routing and Media Resource Allocation for IP Phones
Device Level Configuration

Device Pool Common Device Configuration Calling Search Space Media Resource Group List User Hold Audio Source Network Hold Audio Source
408 555-7890
Remote Destination #1
BRKUCC-2060
408 555-6789
Remote Destination #2
XXX XXX-XXXX
Remote Destination N
Cisco Confidential
12

Feature Review: Mobile Connect, MVA, and EFA
Mobile Connect Incoming calls to users enterprise number rings both desk phone and configured Remote Destination(s)
Unified Mobility User PSTN
Mobile Voice Access (MVA) Provides the ability to make calls from mobile phone using the enterprise IP telephony infrastructure IVR based application requiring H.323 or SIP* VXML gateway
Mobile Connect
User can also enable/disable Mobile Connect Benefits:

Potential cost savings (e.g. international calls) Enterprise DN as caller ID (privacy, return calls) Centralized billing/call detail records for business calls Access to internal-only (non-DID) enterprise extensions Call Anchoring
Enterprise Feature Access (EFA) Two-Stage Dialing Provides identical functionality as MVA without the IVR component
MVA/EFA Two-Stage
* Requires minimum of Unified CM 7.1(3)

13

Feature Review: Pickup and Mid-Call Features
Desk Phone/Remote Destination PickupOnce incoming mobility call has been answered, call can be moved between desk phone and RD(s) Desk phone pickup: Hangup and resume, midcall hold (*81) and resume, or mid-call session handoff * (*74) and answer.
Remote destination pickup: Mobility softkey

(Send call to mobile) and answer.
Desk/RD Pickup
Mid-Call FeaturesProvides the ability to invoke enterprise features Hold, Resume, Transfer, Conference, Directed Call Park, and Session Handoff* from the RD/mobile phone for active mobility calls
Mid-Call Features
* Requires minimum of Unified CM 8.0(1)

14

Feature Review: Single Enterprise VM Box & Access Lists
Single Enterprise Voicemail Box (mobile voicemail avoidance) Per RD timers ensure that when mobility user is unavailable, unanswered incoming calls are forwarded to enterprise voicemail box rather than mobile or other voicemail box Access Lists Per RD access lists can be defined to filter or screen incoming calls to a mobility user based on caller ID. Filtering allows or blocks calls from being extended to the users RD. Time of day filtering* can also be applied.
Mobile Voicemail
PSTN
Unavailable
Single Enterprise Voicemail Box
Enterprise Voicemail
Access List
PSTN
Access Lists
* Requires minimum of Unified CM 7.0
15

Remote Destination Configuration
DN DN Enterprise Phone / Directory Number Remote Destination Profile
Remote Destination #1 Remote Destination N
Line association Remote Destination pickup / Mobile Connect on/off
BRKUCC-2060
Remote Destination/Mobile number End-user timers (mobile VM avoidance, etc.) RDP this Remote Destination is associated to Time of day and access list call filtering
2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential
16

Dial Plan Considerations: Automatic Caller ID Matching
For all inbound calls to Cisco Unified CM the caller ID is automatically compared against all configured remote destinations
Cisco Unified CM Cluster
Inbound caller ID: 9195552345
Configured Remote Destinations: 4085551234 4085555678 4085550987 . . . 9195552345 9195556789 9195558765
PSTN Gateway
MATCH
PSTN
If a match is found, the following occurs:
Call is flagged as a mobility call by Unified CM Call is anchored in the enterprise gateway
Automatic Caller ID matching also results in the replacement of the users remote destination/mobile number with the users enterprise directory number.
17

Enterprise Call Anchoring: Mobility Calls All calls made or received on behalf of users RD are automatically anchored in the enterprise gateway
1 8 *
Mobile Connect
Inbound Calls Answered at Desk Phone or at Remote Destination Phone
Mid-Call Features
DTMF
Mobile Voice Access

Outbound Calls Generated from Remote Destination Phone
In-Progress Call
PSTN Gateway
Enterprise
PSTN
Enterprise Feature Access

(Two-Stage Dialing) Outbound Calls Generated from Remote Destination Phone
Inbound Calls from Remote Destination

Incoming Calls from Configured Remote Destination Phones
BRKUCC-2060
Desk phone Pickup

Cisco Confidential
18

Enterprise Call Anchoring: Mobility Calls (cont.) All calls made or received on behalf of users RD are automatically anchored in the enterprise gateway
Mobile Connect
Inbound Calls Answered at Desk Phone or at Remote Destination Phone
Mid-Call Features
Mobile Voice Access

Outbound Calls Generated from Remote Destination Phone
PSTN Gateway
Enterprise
PSTN
Enterprise Feature Access

(Two-Stage Dialing) Outbound Calls Generated from Remote Destination Phone
Inbound Calls from Remote Destination

Incoming Calls from Configured Remote Destination Phones
BRKUCC-2060
Desk Phone Pickup
Internally Originated Direct Calls to Remote Destination *

Internally Originated Direct Calls to Remote Destination Numbers
* Intelligent Session Control requires minimum of Unified CM 8.0

Cisco Confidential
19

Dial Plan Considerations
BRKSPM-2604_c1
Cisco Confidential
20

Dial Plan Considerations: Outbound v. Inbound Calling
Outbound calls for mobility-enabled users
Remote Destination
Associated IP phone / enterprise number
BRKUCC-2060
Cisco Confidential
21

Dial Plan Considerations: Outbound Call Routing (from RD)
PSTN
Outgoing Calls from RDP: Routing from Remote Destination

(MVA/EFA 2-Stage Dialing, Mid-Call Conferencing/Transfer)
Remote Destination Profile (RDP) contains two CSS settings which control call routing from an RDP perspective:
Calling Search Space
22

Dial Plan Considerations: Outbound Call Routing (to RD)
PSTN
Outgoing Call to RDP: Routing to Remote Destination

(Mobile Connect)
Remote Destination Profile (RDP) contains two CSS settings which control call routing from an RDP perspective:
Calling Search Space Rerouting Calling Search Space
23

Dial Plan Considerations: Outbound v. Inbound Calling
Remote Destination Profile: CSS Rerouting CSS

Remote Destination
Inbound calls for mobility-enabled users
BRKUCC-2060
Cisco Confidential
24

Dial Plan Considerations: Inbound Call Routing
Inbound call routing behavior for calls from RDs is dependent upon Inbound Calling Search Space for Remote Destination service parameter
If set to Trunk or Gateway Inbound Calling Search Space (default), then incoming calls from configured RDs will be routed like all other inbound calls via the trunk/gateway Inbound CSS
If set to Remote Destination Profile + Line Calling Search Space, then incoming calls from configured RDs bypass trunk/gateways inbound CSS and use the RDP CSS.
Enterprise
Line CSS
Partition 4 Partition 5 Partition 6
MVA DID EFA DID Internal DNs
Remote Destination Profile PSTN Gateway Remote Destination Phone
+
RDP CSS
PSTN
GW CSS
Resulting CSS
Incoming calls coming from non-RDs are not affected by this service parameter they will always use the BRKUCC-2060 Cisco Confidential 2010 Cisco and/or its affiliates. All rights reserved. trunk or gateway inbound CSS. Likewise this parameter has no impact on outbound call routing 25

RD Number Configuration: PSTN Steering v. Caller ID Matching There are two options when configuring RD numbers:
1. Configure the number as it would be dialed from the enterprise including any PSTN access or steering digits
To Dial PSTN:
9 + 1 + (XXX) XXX - XXXX

2. Configure the number to match incoming caller ID from the PSTN
Caller ID from PSTN:
(XXX) XXX - XXXX

If option 2 is chosen, an Application Dial Rule (or other prefixing mechanism) is used to add appropriate PSTN access/steering digits
408 PSTN_SJ BRKUCC-2060
10
Cisco Confidential
91
26

RD Number Configuration: Complete v. Partial Matching
If RD numbers are configured to match incoming caller ID (with Application Dial Rules or other digit prefixing used for outgoing call routing), incoming calls from remote destinations are automatically matched for: Mobile Voice Access/Enterprise Feature Access identification Remote destination direct inbound call anchoring
Complete Match
CID: Remote Destination Enterprise Enterprise PSTN GW Remote Destination Profile
Default
4085557890
=
RD#:
4085557890
Remote Destination
Mobile Voice Access Enterprise Feature Access

Automatic Caller ID Matching/Call Anchoring
PSTN
408 555-7890
Complete match v. partial match is controlled by the Matching Caller ID with Remote Destination Cisco CallManager service parameter
27

RD Number Configuration: Complete v. Partial Matching
If RD numbers are NOT configured to match incoming CallerID (i.e. PSTN steering digits are included), Partial Matching must be configured in order to match CallerID for incoming calls from Remote Destinations.
Complete Partial Match Match
CID:
Default
# of Digits to Match:
4085557890
Remote Destination Enterprise Enterprise PSTN GW Remote Destination Profile
=
RD#:
10
9 1 4085557890
Remote Destination
Mobile Voice Access Enterprise Feature Access

Automatic Caller ID Matching/Call Anchoring
PSTN
408 555-7890
Number of digits matched when using partial match is controlled by the Number of Digits for Caller ID Partial Match Cisco CallManager service parameter
28

RD Number Configuration: Summary
RD number configured with PSTN steering digits:
Outbound: Mobile Connect calls routed to RD without need for Application Dial Rule
Inbound: Caller ID matching (identification and automatic):

Matching Caller ID with Remote Destination Set to Partial Match Number of Digits for Caller ID Partial Match Set to appropriate number of digits based on inbound caller ID from provider
RD number configured to match inbound Caller ID:

Outbound: Mobile Connect calls routed to RD using configured Application Dial Rule(s) Inbound: Caller ID matching (identification and automatic):
Matching Caller ID with Remote Destination Set to default Complete Match
Note that prefixing of steering digits for outbound routing can also be done using translation or route patterns, or route list/route group constructs
BRKUCC-2060
Cisco Confidential
29

Dial Plan Considerations: Inbound v. Outbound Calling
Remote Destination Profile: CSS Rerouting CSS

Remote Destination
Inbound CSS for RD: Inbound Trunk/Gateway RDP CSS (+ line CSS) Remote Destination Number: Include PSTN Steering Digits Match Caller ID Inbound Caller ID Matching: Complete Partial
Inbound calls for mobility-enabled users
BRKUCC-2060
Cisco Confidential
30

BRKSPM-2604_c1
Cisco Confidential
31

Design Considerations: Scalability
Cisco Unified Mobility supports the following capacities:
Mobility-Enabled Users per Cluster MCS-7845 MCS-7835 MCS-7825 15,000 10,000 4,000 Mobility-Enabled Users per Node 3,750 2,500 1,000
Mobility-enabled user: A user that has an RDP and at least one RD configured Capacity numbers are based on a single RD per user As number of RDs per user increases, the number of mobility-enabled users decreases
BRKUCC-2060
Cisco Confidential
32

Design Considerations: Redundancy
Redundancy for RD and RDP configuration provided via device pools/CM groups. Mobile Connect (including desk / remote phone pickup), Enterprise Feature Access (EFA), and mid-call feature functionality are all natively redundant No redundancy for Mobile Voice Access
X X
If Publisher is down, MVA is not available Enterprise Feature Access 2-Stage Dialing is
still possible.
If Publisher is down, changes to Mobile Connect status (on/off) via EFA are not saved (and therefore do not take affect).
BRKUCC-2060
Cisco Confidential
33

Design Considerations: Redundancy (cont.)
Gateway and PSTN access redundancy as usual, however branches in SRST mode will have no or very restricted Unified Mobility functionality:
If call comes into central site/originates from extension in central site, then call may be extended to RD because Unified CM is reachable. Call will not be extended to desk phone. If call comes into remote site/originates from remote site while site is in SRST mode, call will not be extended to remote destination because Unified CM is not available to determine remote destination number. Call will be extended to desk phones
X X
BRKUCC-2060
Cisco Confidential
34

Design Considerations: PSTN Connectivity
DTMF Relay:
Mid-call features and Enterprise Feature Access 2-Stage Dialing require out-of-band (OOB) DTMF relay between enterprise PSTN gateway and CUCM Mobile Connect functionality is supported only with PRI for TDM PSTN connections (no T1-CAS, FXO, FXS, or BRI connections)
PRI required for timely connect/disconnect indication to Unified CM.
TDM Connectivity:
For inbound Mobile Connect calls: Unified CM needs to know answer has occurred at remote destination in order to stop ringing other devices (desk phone and other remote destinations).
For desk phone pickup: Unified CM needs to know disconnect has occurred at remote destination in order to put desk phone in hold state so user can resume call.
For single enterprise voice mail box: Unified CM needs to know that mobile voicemail has answered (Answer Too Soon Timer) in order to disconnect the call leg.
BRKUCC-2060
35

Design Considerations: PSTN Connectivity (cont.)
VoIP Connectivity: Unified Mobility call flows and
functionality are supported over service provider SIP trunk PSTN connections.
Cisco Unified Border Element is required to terminate Unified CM SIP trunk and provider SIP trunk Mid-call Features are not supported for this type of PSTN connection due to potential DTMF interop issues G.711 required between enterprise gateway and CUCM for MVA. Transcoders will be needed if inbound call leg is G.729 Requires Unified CM 6.1(2) and later or 7.1(2) and later.
BRKUCC-2060
Cisco Confidential
36

Design Considerations: Caller ID
Caller ID For Unified Mobility deployments,

customer should work with their service provider to ensure the following:
Inbound Caller ID
If Enterprise Feature Access (mid-call features or 2-stage dialing) is required, service provider must send appropriate inbound caller ID to enterprise.
BRKUCC-2060
Cisco Confidential
37

Design Considerations: Caller ID (cont.)
Outbound Caller ID
If original caller ID for Mobile Connect calls is to be sent to mobility users RD, service provider must not restrict caller ID on trunk to only DIDs assigned to that trunk.
Redirected Dialed Number Identification Service (RDNIS) and SIP Diversion Header Some providers allow unrestricted caller ID provided the RDNIS field or SIP
Diversion Header contains a DID handled by the trunk. Contact your provider to see if they honor RDNIS or SIP Diversion Header
When checking the Redirecting Number ID Delivery Outbound field on the gateway
or trunk configuration page in Unified CM 7.1(3) and later, system will populate RDNIS/SIP Diversion Header with called users enterprise number.
If unable to provide unrestricted caller ID, then ensure meaningful enterprise caller ID is sent.
BRKUCC-2060
Cisco Confidential
38

Design Considerations: PSTN Utilization
Planning and allocating PSTN gateway resources is extremely important for Unified Mobility
Mobility call flows typically involve multiple PSTN call legs
Must increase PSTN gateway resources to handle large numbers of mobility users
How much of an increased load on PSTN gateways will vary widely depending on call patterns and volumes. Absent information about an enterprises call patterns and volumes, some techniques can be used to minimize utilization of PSTN gateway resources.
BRKUCC-2060
Cisco Confidential
39

Design Considerations: Minimizing PSTN Utilization
Call rings only one Remote Destination (408 555-7890) Call to only one Remote Destination routed via gateway
+
5 Add ToD to Access Lists
Access List: Block/allow calls from incoming numbers
6
408 555-7890
PSTN Gateway
PSTN
1
Dials: 1 408 555-1234 Phone A
Call placed to only one associated Remote Destination
X X
Access lists limits calls to PSTN Cisco Unified Limit to one CM cluster Remote Destination
Remote Destination: 408 555-7890
Disable Mobile Connect when not needed
4 Remote Destination Profile

Call extended to Remote Destination Profile
2
Call extended to desk phone
Each RD will consume a DS0. DS0 will be utilized for up to 10 seconds even if call is not answered at RD
DN: 408 555-1234
DN: 408 555-1234
SHARED LINE
PSTN resource utilization reduction for Cisco Unified Mobility Limit to one Remote Destination per user Utilize allow/block Access Lists to limit calls forwarded to PSTN Use time of day (ToD) Access Lists to limit calls forwarded to PSTN* Users to disable Mobile Connect when not in use
* ToD ACLs supported with Unified CM 7.0 and later
40
BRKSPM-2604_c1
Cisco Confidential
41

Agenda Feature Review and Basic Functionality
Cisco Unified Mobility Integration

Basic Call Flows and Dial Plan Considerations Handoff Call Flows
BRKUCC-2060
Cisco Confidential
42

BRKSPM-2604_c1
Cisco Confidential
43

Architecture
Enterprise
PSTN
WLAN
Dual-mode Mobile Phone
WLAN AP
(802.11 a/b/g)
Dual-mode phones provide the ability to leverage the enterprise IP telephony infrastructure (via WLAN connectivity) for making and receiving calls inside the enterprise. When outside the enterprise the dual-mode device falls back to the GSM/PSTN network. Dual-mode client runs on the dual-mode phone device and registers to Unified CM for call processing services
44

Feature Summary
WLAN
PSTN
Dual-mode phone solution provides the following high-level features and functionality: SCCP or SIP client registration to Unified CM WLAN: Voice over WLAN with 802.11 b/g connectivity*
Access to enterprise supplementary features: hold, resume, transfer, conference, park

Manual or Automatic handoff (WLAN to cellular / Cellular to WLAN): Ability to move in and out of the enterprise while on active call Mobile Connect/SNR when integrated with Unified Mobility Device Mobility (CUCM feature supported with versions 4.2, 6.0 and later)
* Cisco cannot guarantee voice quality when dual-mode devices are connected via public or private WiFi hotspots.
45

Devices & Clients: Nokia Call Connect
Nokia Call Connect 2.1
Nokia E72
WLAN
PSTN
SCCP client registers via 802.11 b/g WLAN to Unified CM as Nokia S60 (supported with Unified CM 4.3 and
later but some features not available with all versions of Unified CM)
Handset support:
Nokia S60 3.2 handsets (Nokia E52, E55, E72, and E75) [S60 3rd Edition, Feature Pack 2] Nokia S60 3.1 handsets (Nokia E51, E61i, E63, E66, E71, and E90). Not all advanced features supported.
[S60 3rd Edition, Feature Pack 1]
Nokia E61i Nokia E66
Automatic* (and manual) handoff:
Hand-in (Cellular to WLAN) Hand-out (WLAN to cellular)
Nokia E75
Additional features and services:

Nokia E71
Unified CM Directory access Unified CM XML-based IP phone services access Enterprise voicemail indication Automated 2-stage dialing using Cisco Unified Mobility Enterprise Feature Access* Cisco Compatible Extensions (CCX) version 3 or 4 support (handset dependent).
Cisco Confidential
* Supported only with NCC 2.1 and 3.2 versions of handsets

46

Devices & Clients: Cisco Mobile 8.0 (iPhone)
New
WLAN
PSTN
Cisco Mobile 8.0
SIP client registers via 802.11 b/g WLAN to Unified CM as Cisco Dual-Mode for iPhone device (Unified CM 7.1(3) and later) Handset support:
iPhone 3G, 3GS, 4 Firmware 3.0.1 or later
Manually invoked handout :
Hand-out (WLAN to cellular): Mobility softkey method (system calls client) Handoff number method (client calls system)
Additional features and services:
Two active call support with call swap Corporate Directory Lookup integration to Microsoft Active Directory 2003 or 2008 (global cataloging must be enabled). Visual voicemail lists when integrated to Unity Connection 7.x or 8.0 (includes enterprise voicemail MWI) Motion-activated voice dialing integration to Unity Connection 7.x or 8.0 leveraging Speech Connect/voice-enabled directory handlers. Transfer of active call from desk phone to iPhone using desk phone integration.
Cisco Confidential
BRKUCC-2060
47

BRKSPM-2604_c1
Cisco Confidential
48

PSTN

WLAN
WLAN AP
Dual-mode Mobile Phone
(802.11 a/b/g)
WLAN client on dual-mode phone registers to Cisco Unified CM as users enterprise IP phoneno Remote Destination Profile needed Mobile phone number is defined as a Mobility Identity associated directly to dual-mode device (just like a Remote Destination)
49

Cisco Unified Mobility Integration: Configuration
Enterprise Phone / Directory Number DN Remote Destination Profile DN
DN
Dual-Mode Device
Mobility Identity
Remote Destination(s)
Mobile phone number of dual-mode phone End-user timers (mobile VM avoidance, etc.)
Dual-mode phone this Mobility Identity is associated to. (Note: No line
association required)
Remote Destination pickup / Mobile Connect on/off
+
Time of day and access list call filtering
50

Basic Call Flows and Dial Plan Considerations
BRKSPM-2604_c1
Cisco Confidential
51

Incoming Call Routing
Incoming calls are routed to mobile voice network via Mobile Connect when phone is not associated/registered to enterprise Incoming calls are routed to dual-mode client when phone is associated to enterprise WLAN and registered to Cisco Unified CM.
Enterprise
Call 1 408 555-1234

Dual-Mode Mobile Voice Network Connectivity Only Dual-Mode WLAN Connectivity
Call 51234
PSTN Gateway
SIP Dual Mode Alert Timer service parameter: Determines how long Unified CM checks for Cisco Mobile 8.0 client on the network before extending call to mobile voice interface (via Mobile Connect). Default is 1500 msecs Recommend 3000 msecs
PSTN
AP
WLAN DN: 51234 DID: 408 555-1234
Mobility Identity
408 555-7890

Same Phone
Note: When the dual-mode phone is in the WLAN, incoming calls to the enterprise number will not ring the mobile voice/cellular interface
52

Outgoing Call Routing
Outgoing calls from GSM are dialed just like a typical mobile phone call Outgoing calls are routed within WLAN just like any enterprise phone Enterprise
Dual-Mode Mobile Voice Network Connectivity Only Dual-Mode WLAN Connectivity
PSTN Gateway Mobile Voice Network
PSTN
AP
WLAN
!
CAUTION
Emergency calls should always be dialed directly over the mobile voice network.
Mobility Identity

Same Phone
Dial plan is challenging: User dialing method within enterprise will be different than from mobile voice network
53

Outgoing Call Routing: Normalization
Dial plan within Unified CM can be configured to prefix steering digits to calls made by dual-mode devices when in the WLAN Contacts on mobile device will all need to be configured uniformly (e.g. ten-digit/full E.164 or + followed by ten-digits/E.164)
Enterprise
Call is then forwarded to PSTN or rerouted to local extension as appropriate

Dual-Mode Mobile Voice Network Connectivity Only
PSTN Gateway Mobile Voice Network
Dual-Mode WLAN Connectivity
PSTN
AP
Translation Pattern
Prefix Digits: 9 1
User dials ten digits (manually or from contacts)
WLAN
Mobility Identity
User dials ten digits (manually or from contacts)

Same Phone
54

Design Considerations: Dial Plan
End-User dialing behavior Dialing on the mobile voice
network/PSTN is different than dialing within the enterprise network. 1. User Effort: Users checks for Unified CM
registration icon.
Nokia CC 2.x
If present, user dials using enterprise dial plan (abbreviated dialing, PSTN steering digits, etc.) If not present, user dials using PSTN dialing method (+ and/or E.164)
Cisco Mobile 8.0
Nokia CC 2.x client provides + prefix translation option and Dialing prefix option (2.1 only) which can be used to translate dialed numbers and improve user dialing experience iPhone Cisco Mobile 8.0 client can download application dial rules from Unified CM to improve user dialing experience
2.
Administrator Effort: Unified CM dial plan configured to

accommodate PSTN/mobile voice network dialing.
User always dials all calls using + or full E.164 number (manually or from contacts) Unified CM dial plan routes to local extensions as appropriate and/or prefixes appropriate PSTN steering digits.
Recommended
BRKUCC-2060
Cisco Confidential
55

Handoff Call Flows
BRKSPM-2604_c1
Cisco Confidential
56

Handoff Terminology: Hand-Out v. Hand-In
Moving calls from enterprise WLAN to cellular network and vice-versa is generally referred to as Handoff Hand-out: Moving calls from
enterprise WLAN to cellular network
Mobile Voice Network PSTN
PSTN Gateway
AP
Cellular/Mobile Voice
Enterprise WLAN
Hand-in: Moving calls from cellular

network to enterprise WLAN
Mobile Voice Network PSTN
PSTN Gateway
AP
Cellular/Mobile Voice
Enterprise WLAN
57

Cisco Mobile 8.0: Handoff Considerations
Cisco Mobile 8.0 supports two methods of hand-out: Mobility softkey method user/client receives call from Unified CM system on
mobile voice interface
Handoff DN method user/client automatically makes call to handoff number

configured in Unified CM
o Method used depends on Transfer to Mobile Network setting on Cisco

Dual-Mode for iPhone device configuration page
Handoff number configured in Unified CM (Call Routing > Mobility

Configuration)
Hand-in is not supported with Cisco Mobile 8.0
BRKUCC-2060
Call Park:
Application will auto-park calls on handoff failure enabling user to manually call the park number from PSTN/mobile voice network to retrieve. Call park number must be a DID reachable from the PSTN. Cisco Mobile 8.0 will also auto-park in progress calls in scenarios where application is closed. On return to application user is prompted to auto-retrieve the parked call (assuming caller is still on the line).
58

Unified CM generates a call to the dual-mode users configured mobility identity number via the enterprise PSTN gateway Enterprise Cisco Unified CM Cluster
Cisco Mobile 8.0: Hand-Out Mobility Softkey method
PSTN Gateway
Handoff Number: 1234 Handoff Number DID: +1 408 555 1234
PSTN
Mobile 5 Voice Network
On answer, Unified CM redirects original RTP stream that was traversing the WLAN to the enterprise PSTN gateway resulting in enterprise call anchoring.
3 1
An existing call between the iPhone dual-mode device on the enterprise WLAN and a phone on the PSTN.
Mobile Voice
AP 2
4
WLAN
User is now able to move out of the enterprise and away from enterprise WLAN coverage. Same Phone
User pushes Use Mobile Network softkey from incall menu and iPhone dual-mode client indicates to Unified CM its intention to hand-out.
Initial voice media path Handoff background call leg Final voice media path
Handoff indication signaled to Unified CM over WLAN which in turn generates call to dual-mode phones mobile voice network interface. Once answered call media is redirected from WLAN to enterprise PSTN gateway.
BRKUCC-2060
59

Because Unified CM relies on inbound caller ID to identify the call being handed off, ensure native iPhone caller ID is
(Tap: Settings > Phone > Show My Caller ID) iPhone dual-mode client automatically makes call via mobile voice network interface to Handoff Number configured within Unifed CM. Enterprise Cisco Unified CM Cluster
Cisco Mobile 8.0: Hand-Out Handoff DN method
PSTN Gateway
PSTN
Mobile Voice
3 1
An existing call between the iPhone dual-mode device on the enterprise WLAN and a phone on the PSTN.
Unified CM verifies caller ID of inbound call to handoff number to ensure it matches configured mobility identity. If so, Unified CM redirects original media stream that was traversing the WLAN to the enterprise PSTN gateway and call is anchored in the enterprise.
AP 2
4
WLAN
User is now able to move out of the enterprise and away from enterprise WLAN coverage. Same Phone
User pushes Use Mobile Network softkey from incall menu and iPhone dual-mode client indicates to Unified CM its intention to hand-out.
Initial voice media path Handoff background call leg Final voice media path
Hand-off indication signaled to Unified CM over WLAN which in turn generates call from dual-mode phones mobile voice network interface to handoff number. Once answered call media is redirected from WLAN to enterprise PSTN gateway.
BRKUCC-2060
60

Nokia Call Connect 2.x: Hand-Out (WLAN to Cellular)
Automatic handoff is only supported on the Nokia E52, E55, E72, and E75 handsets As the WLAN signal strength drops below -73dBm (default) for a period of 1 second (default), a silent background call is opened to Cellular handover number +1 408 555 1234 on the Unified CM system Enterprise Cisco Unified CM Cluster
Unified CM relies on inbound caller ID to identify the call being handed off Ensure inbound caller ID is Mobile presented to Unified CM
PSTN Gateway
PSTN
4
3 1
Voice Network
Mobile Voice
An existing call between the Nokia dual-mode device on the enterprise WLAN and a phone on the PSTN.
Once background call received by Unified CM, calling number is compared against system dualmode mobility identities and provided a match is found, media stream on WLAN is redirected to the PSTN gateway
AP
Initial voice media path
WLAN
Handoff background call leg Final voice media path
The Nokia dual-mode user begins to leave the enterprise. Hand-out can also be invoked manually by the user using the in-call menu Switch to Cellular or Switch to GSM options.
Same Phone
Manual invocation of handoff stops operation of auto-handoff for duration of call. This option must be used for devices that dont support automatic-handoff. Cisco and/or its affiliates. All rights reserved. BRKUCC-2060 2010
Background call opened to the configured Cellular Handover Number in VCC settings (on Nokia device) which corresponds to the Handoff Number configured within Unified CM.
Cisco Confidential
61

Nokia Call Connect 2.x: Hand-In (Cellular to WLAN)
After registration the device waits for 60 seconds (default) and then opens a silent background call to VoIP Handover number 1234 on the Unified CM system Enterprise Cisco Unified CM Cluster Automatic handoff is only supported on the Nokia E52, E55, E72, and E75 handsets
PSTN Gateway

Once background call received by Unified CM, calling number is compared against system dualmode mobility identities and provided a match is found, RTP stream on PSTN gateway is redirected to the PSTN gateway
PSTN
An existing call between the Nokia dual-mode device on the mobile voice network and a phone on the PSTN.
3
Mobile Voice
AP
4 2
Initial voice media path
WLAN
Handoff background call leg Final voice media path
The Nokia dual-mode user moves into the enterprise and the device associates in the background to WLAN infrastructure and registers to Unified CM Hand-in can also be invoked manually by the user using the in-call menu Switch to WLAN option. Manual invocation of handoff stops operation of auto-handoff for duration of call.
BRKUCC-2060
Same Phone
Background call opened to the configured VoIP Handover Number in VCC settings (on Nokia device) which corresponds to the Handoff Number configured within Unified CM.
Cisco Confidential
62

BRKSPM-2604_c1
Cisco Confidential
63

Design Considerations: Voice over WLAN
Similar VoWLAN network design requirements as Cisco Unified Wireless IP Phone 7921G and 7925G
Cell radius or power-level boundary of
approximately -67 dBm (or less) is recommended in order to minimize packet loss.
Same channel cell separation of 19 dBm is recommended to minimize co-channel interference Channel cell overlap (on non-adjacent channels) should be 15-20% to ensure seamless roaming between APs.
Bluetooth headsets are not recommended with dual-mode handsets due to potential interference on the 2.4 GHz band. Bluetooth headsets are not supported for handling calls in Cisco Mobile 8.0. Can only be used to listen to voicemail messages.
For more information on VoWLAN Design, see the Voice over Wireless LAN 4.1 Design Guide at:
http://www.cisco.com/en/US/docs/solutions/Enterprise/M obility/vowlan/41dg/vowlan41dg-book.html 64
Cisco Confidential

Design Considerations: Scalability
WLAN
PSTN
Scalability implications for dual-mode phones and clients include:
Registration/device load on Unified CM for each dualmode device/client Theoretical maximum of 30,000
call capacity:
Traffic load on the Wireless LAN Infrastructure Per AP

Maximum of 14 simultaneous VoWLAN calls per 2.4 GHz (802.11b/g) channel cell. For 802.11b-only deployments or deployments where there are large numbers of active 802.11b clients, a maximum of 7 simultaneous VoWLAN calls per channel cell is supported.
A single call between two dual-mode phones associated to the same AP is considered to be two simultaneous VoWLAN calls.
Unified Mobility remote destination/mobility identity

capacity Maximum of 15,000 total
BRKUCC-2060
Cisco Confidential
65

Design Considerations: Redundancy
Redundancy for registration to Unified CM provided via device pools/CM groups. Dual-mode VoIP features and operations (VoIP, handoff, mid-call features, automatic park, and move to desk phone) all natively redundant within Unified CM
WLAN
X
PSTN
Gateway and PSTN access redundancy is as usual, however branches in SRST mode will have no dual-mode support.
Device will automatically fall-back to cellular/mobile voice network

when client de-registers from Unified CM.
Cisco Unified Mobility features (Mobile Connect, 2-stage dialing, desk phone/remote destination pickup, etc.) are all natively redundant within Unified CM
BRKUCC-2060
Cisco Confidential
66

Design Considerations: Caller ID
Caller ID
Caller ID For dual-mode deployments, work with your

service provider to ensure proper caller ID behavior.
Inbound Caller ID Service provider must send appropriate
inbound caller ID to enterprise if any of the following are required:
Hand-out (WLAN to cellular) for Nokia CC or Cisco Mobile 8.0 (Handoff DN method only).
Dual-mode device must also have native caller ID enabled in order to ensure caller ID is sent to provider network
2-stage dialing automation (Enterprise Feature Access) on Nokia CC.
Any other Unified Mobility features that rely on inbound caller ID (midcall features, automatic inbound call anchoring).
Outbound Caller ID All VoIP calls and 2-stage dialed calls will send users enterprise number
rather than the users mobile number.
BRKUCC-2060
Mobile Connect considerations (original caller ID, RDNIS/SIP Diversion header).

67
BRKSPM-2604_c1
Cisco Confidential
68

Agenda

Security Cisco Unified Mobility Integration Dial-via-Office Call Flows and Considerations Design and Deployment Considerations
Product naming decoder ring: Cisco Unified Mobile Communicator (CUMC) Name of the solution and client Cisco Unified Mobility Advantage (CUMA) Name of the server Cisco Mobile 7 Newer name for client (iPhone and Blackberry) still CUMC Cisco Mobile 8.0 New dual-mode client (different than CUMC)
69

BRKSPM-2604_c1
Cisco Confidential
70

Architecture
The Cisco Unified Mobile Communicator (CUMC) solution enables mobile users to utilize enterprise applications from their mobile phones using a mobility client that communicates with a mobility server inside the enterprise (client-server architecture)
Cisco Unified Mobile Communicator/ Cisco Mobile 7.x
PSTN
Cisco Unified CM
iPhone
PSTN Gateway DMZ

MMP over BES MMP over BES
Cisco Unified Presence
BES (w./ MDS)
Cisco Unity/ Unity Connection
Microsoft Active Directory
MMP over SSL
Mobile Data Network (Data Channel)
Internet
MP
Cisco MeetingPlace
Microsoft Exchange
MMP over SSL
BRKUCC-2060
Cisco Adaptive Security Appliance (ASA) Cisco Confidential 2010 Cisco and/or its affiliates. All rights reserved.
Enterprise and UC Applications
71

Feature Review: Administration and Text Messaging
REQUIRED
Web-based Administration and User

PSTN
Cisco Unified CM
portals Native support for messaging between CUMC/Cisco Mobile clients (IM/Text).* Secure and guaranteed delivery No SMS/Text message charges Caveat: Text messaging only supported between CUMC clients
iPhone
PSTN Gateway DMZ BES (w./ MDS)
Internet * Messaging not supported on Cisco

Mobile 7 for iPhone. Cisco Adaptive
BRKUCC-2060
MP
Cisco MeetingPlace
Microsoft Exchange
Cisco Confidential 2010 Cisco and/or its affiliates. All rightsAppliance(ASA) Security reserved.
72

Feature Review: Secure Connectivity
Adaptive Security Appliance (ASA) Blackberry Enterprise Server (BES)
REQUIRED
REQUIRED if Blackberry clients deployed

Provides secureTLS connection between
client and enterprise. Pushes client software to Blackberry Cisco Unified PSTN Mobile Voice Mobile devices. Network Manages security policies for client Communicator/ software distribution as well as client Cisco Mobile 7.x operation.
Cisco Unified CM
(except for Blackberry-only deployments) Provides certificate-based secure TLS connection between client and enterprise. One-way certificate exchange server provides CA-signed (VeriSign or GeoTrust) certificate. Client verifies server certificate using preloaded root certificate. ASA also provides additional security with deep packet inspection for MMP traffic.
iPhone
Internet
MP
Cisco MeetingPlace
Microsoft Exchange
Cisco Adaptive
BRKUCC-2060
73

Feature Review: Directory Integration
PSTN
Cisco Unified CM
iPhone
Cisco Unified Presence LDAP
REQUIRED

Integration via LDAP No change to schema Server Mobile read-only account uses Data Network Client /user authentication (Data Channel) Internet Neither CUMA server nor CUMC client store password Corporate directory lookups Active Directory 2000, 2003 or 2008
MP
Cisco MeetingPlace
Microsoft Exchange
Cisco Adaptive
BRKUCC-2060
74

Feature Review: Call Logs and Dial-via-Office
Unified Communications Manager
REQUIRED
Cisco Unified PSTN Mobile Voice Call Mobile history (missed, placed, Network received) Communicator/ Cisco Integration via JTAPI/CTI Mobile 7.x Dial-via-Office Integration via SIP Requires Unified CM 7.0 and later
iPhone
PSTN Gateway DMZ BES (w./ MDS) Mobile Data Network (Data Channel)
Unified CM 4.x, 5.x, 6.x, 7.x, and 8.x Desk phone call log integration
Cisco Unified CM
SIP, JTAPI/CTI
Internet
MP
Cisco MeetingPlace
Microsoft Exchange
Cisco Adaptive
BRKUCC-2060
75

Feature Review: Voicemail Integration
Cisco Unity/Unity Connection
OPTIONAL
Cisco Unity 4.x or later (unified or
integrated messaging) Cisco Unity Connection 7.x or later Cisco Unified message waiting indication Enterprise Mobile Voice PSTN Mobile (MWI) Network Communicator/ Visual voicemail allowing visual Cisco Mobile 7.x navigation of voicemail messages. Messages downloaded to client over data connection No need to dial in and navigate TUI iPhone PSTN Integration via IMAP Gateway Secure messaging support DMZ Cisco Unity/Unity Connection 7.x
BES (w./ MDS) Mobile Data Network (Data Channel)
Cisco Unified CM
IMAP
Internet
MP
Cisco MeetingPlace
Microsoft Exchange
Cisco Adaptive
BRKUCC-2060
76

Feature Review: Conferencing Integration
Cisco Unified MeetingPlace
OPTIONAL
Requires Microsoft Exchange 2000,
2003, or 2007
1:45 PM Dept. All Hands
Integration via WebDAV to Microsoft CiscoExchange Unified PSTN Mobile Voice Mobile Network List of meetings and reminders Communicator/ Cisco Mobile 7.x Cisco Unified Requires MeetingPlace 6.x, 7.x, or 8.x
Meeting list/conference notifications*
Cisco Unified CM
Call Me (click/tap-to-join)** Integration via SOAP to Cisco UnifiediPhone MeetingPlace Cisco Unified MeetingPlace calls client back automatically without need for entering meeting ID or password Cross launch of WebEx Meeting Center client for meetings with Mobile Data WebEx data share.** Network
(Data Channel)
WebDAV Cisco SOAP MP MeetingPlace
* Meeting lists not supported on Cisco Internet

Mobile 7 client for Blackberry. Conference notifications/lists are handled via native Blackberry calendar and BES integration to Exchange.
Microsoft Exchange
** Supported only on Cisco Mobile 7
Cisco Adaptive clients for Blackberry and 2010 Cisco and/or its affiliates. All rights reserved. iPhone BRKUCC-2060 Cisco Security Appliance(ASA)Confidential
77

Feature Review: Presence Integration
OPTIONAL
Requires Cisco Unified Presence 7.0(2)
or later Cisco Unified PSTN Mobile Voice Ability to set and send Mobile Network Communicator/ presence/availability status* Cisco Mobile 7.x Ability to receive presence/availability* Cisco Unified CM status for all enterprise contacts. Synchronized buddy list with Cisco Unified Personal Communicator (CUPC) PC iPhone client. PSTN Integration via SIP/SIMPLE Gateway
DMZ BES (w./ MDS) Mobile Data Network (Data Channel)
SIP/ SIMPLE
Internet
MP
Cisco MeetingPlace
Microsoft Exchange
* Presence not supported on Cisco

Mobile 7 for iPhone.
BRKUCC-2060
Cisco Adaptive
78

Feature Review: Personal Contacts and Calendaring
Microsoft Exchange
OPTIONAL
Unified CiscoAccess to users personal Outlook PSTN contact lists Mobile Voice Mobile Network Communicator/ with users Outlook Integration Cisco Mobile 7.x calendar Automatic presence status updates based on calendar entries
iPhone User must have an Exchange
Microsoft Exchange 2000, 2003, or 2007 Personal Outlook integration
Cisco Unified CM
(meeting/appointment start and stop times). PSTN Gateway DMZ BES (w./ MDS) Mobile Data Network (Data Channel)
mailbox. Integration via WebDAV
WebDAV
Internet
MP
Cisco MeetingPlace
Microsoft Exchange
Cisco Adaptive
BRKUCC-2060
79

Handset Support
Example devices
Cisco Mobile 7.1 (CUMC client) supported on Blackberry handsets meeting the following criteria: BlackBerry OS version 4.3 or higher Non-touchscreen devices only Enterprise activated
8200 Flip 8300 Curve 8900 Curve 9000 Bold 9600 Tour 9700 Bold
iPhone
3G or 3GS
Cisco Mobile 7 (CUMC client) supported on iPhone 3G, 3GS , 4 handsets meeting the following criteria: Firmware version 3.0.1 or later iTunes 8.2 or later
Example devices
E51 E61i
Example devices
E71
N95
N96
Protg G710
Samsung HTC S620 Blackjack II
Motorolla Q9H
Samsung ACE
Cisco Unified Mobile Communciator 7.0 supported on Windows Mobile handsets meeting the following criteria: Windows Mobile versions 6.0 Standard or 6.1 Standard (Professional not supported) PDA-style form factor with full QWERTY keyboard, and screen size of 320x240 pixels
Cisco Unified Mobile Communicator 7.0 supported on most Nokia E-series and Nseries handsets meeting the following criteria: Minimum firmware versions: S60 3rd edition S60 3rd edition feature pack 1 (3.1) S60 3rd edition feature pack 2 (3.2) S60 5th edition All handsets require the following: Insalled VeriSign or GeoTrust root certificate. No restrictions on running 3rd party applications Data plan from the service provider which includes full internet access, not just email
Cisco Confidential
80

Mobile OS Feature Summary
iPhone
Enterprise Directory Lookup and single sign-on Enterprise Desk Phone Call Log Integration IM/Text Messaging Presence
Voicemail (visual and MWI)

Conference Integration Meeting List * Conferencing Integration Call Me (click-to-join) Dial-via- Office (DVO-F) Dial-via-Office Reverse/Callback (DVO-R) Mobile Connect (Single Number Reach)

81
* Microsoft Exchange requiredConfidential Cisco
Via integration with Unified Mobility

Security Considerations
BRKSPM-2604_c1
Cisco Confidential
82

ASA Deployment: ASA TLS Proxy and Firewall The Cisco Adaptive Security Appliance (ASA) can be deployed in one of two ways.
Option 1:
ASA acts as both firewall and TLS Proxy

MMP over SSL
Enterprise
MP
U U
UC Applications
DMZ Mobile Data Network (Data Channel)

MMP over SSL
Internet ASA must run version 8.0(4) or later. 8.2 or later recommended for built-in mobility proxy licensing
ASA TLS Proxy
VeriSign or GeoTrust (CA) Certificate

Self-signed (or CA) Certificate

83

ASA Deployment: ASA TLS Proxy Only The Cisco Adaptive Security Appliance (ASA) can be deployed in one of two ways.
Option 2:
ASA as TLS Proxy only

(external firewalls used)
MMP over SSL
Enterprise
MP
U U
UC Applications
DMZ
MMP over SSL
Internet ASA must run version 8.0(4) or later. 8.2 or later recommended for built-in mobility proxy licensing
ASA TLS Proxy


84

ASA Deployment: Scalability
ASA Platform
ASA 5505 ASA 5510 ASA 5520 ASA 5540 ASA 5550
Maximum UC/Mobility Proxy Function Limit

24 100 1,000 2,000 3,000
Max. Number of CUMC/ Cisco Mobile Clients

24 100 1,000 2,000 3,000
ASA 5580 *
10,000
10,000
If ASA is used for other UC applications (e.g. Phone Proxy), number of supported Cisco Unified Mobile Communicator clients may be less Firmware version 8.2 recommended in order to leverage built-in mobility proxy licensing for Cisco Unified Mobile Communicator solution. Versions prior to 8.2 will require purchase of licensing.
BRKUCC-2060
* Requires firmware version 8.2
85

BES Deployment: Cisco Mobile 7 for Blackberry Cisco Mobile 7 for Blackberry is dependent upon
Blackberry Enterprise Server for the following: Secure connectivity to CUMA in order to leverage back-end application
services (directory, presence, dial-via-office, etc.) Client software push (can also be manually loaded on handsets)
BES deployment has the following requirements:

BES version must be 4.1.6 (version 4.1 w./ service pack 6) or 5.0 (requires Cisco
Mobile client version 7.1.026 or later)
BES server must be installed with MDS (both Blackberry MDS Connection
Service and MDS Integration Service required)
The following settings must be enabled in order to distribute client software and to support Cisco Mobile:

BRKUCC-2060
IT Policy > Security Policy group:
Disallow Third Party Application Downloads : False Allow Internal Connections : True Allow External Connections : True
Software Configuration Application Control Policy must have the following set to Allow for Cisco Mobile :
Cross Application Communication Internal network Connections External network Connections Local Connection Phone Access Email
User Data Event Injection Bluetooth Serial Profile Security Data Blackberry Device Keystore Medium Security 86
Cisco Confidential

Security Architecture: Certificate Considerations
Securing the data connection to the CUMA server is critical for secure communication. Cisco recommends CA-signed certificates on ASA or CUMA depending on client for highest level of security. Optional: Additional security can be implemented to secure the data connection between CUMA and back-end application servers
Self-signed certificate caveats: On MDS server properties under TLS/HTTPS, the Allow Untrusted TLS Connections setting must be set to 'True' if you plan to use a selfsigned/untrusted certificate on CUMA. MMP over BES
BES
(w./ MDS)
Cisco Unified Mobile Communicator/ Cisco Mobile
MP U U
Internet
MMP over SSL Self-signed certificate caveats: Results in warning on client on each connection Self- signed certificate needs to be uploaded to device to eliminate warning.
DMZ
UC Applications
ASA TLS Proxy
VeriSign or GeoTrust Certificate


Cisco Confidential
87

Cisco Unified Mobility Advantage: Security
Enforce specific handset hardware on a per user basis, based on IMEI, ESN, or UDID Configured under Device Identity Maintenance tab for each user Setting: Allow Any Device Default setting is FALSE meaning IMEI, ESN, or UDID must be
configured prior to provisioning of CUMC/Cisco Mobile client
BRKUCC-2060
Cisco Confidential
88

Cisco Unified Mobility Advantage: Security (cont.)
Melt operation allows remote wipe in scenarios where handset is lost or stolen
Melt icon next to user handset on CUMA Admin portal Once selected and confirmed, at next connection
attempt client will wipe configuration and all user data
X
Mobile Data Network
Internet
ASA TLS Proxy
89

Unified Mobility Integration
BRKSPM-2604_c1
Cisco Confidential
90

Cisco Unified Mobility Integration: Configuration
Enterprise Phone / Directory Number DN Remote Destination Profile DN
DN

Mobility Identity
Dual-Mode Device
DN
Mobility Identity Remote Destination(s)
Remote Destination(s)
Mobile phone number of client device must match exactly the mobile number configured within Cisco Unified Mobility Advantage
End-user timers (mobile VM avoidance, etc.)

CUMC device this Mobility Identity is associated to. Remote Destination pickup / Mobile Connect on/off
Time of day and access list call filtering
BRKUCC-2060
Cisco Confidential
91

Dial-via-Office: Call Flows and Deployment Considerations
BRKSPM-2604_c1
Cisco Confidential
92

Dial-via-Office Feature
The dial-via-office feature enables the Cisco Unified Mobile Communicator/Cisco Mobile client to dial an outgoing call through the enterprise All voice media traverses the mobile voice network and PSTN.

Media traverses only the enterprise PSTN gateway. All voice signaling is SIP and traverses the data connection between the client and Unified CM (via CUMA server). Dial-via-Office calls hairpinned in the enterprise PSTN gateway Benefits:
Cost savings for international and possibly long distance calls Ability to dial internal-only (non-DID) enterprise extensions System sends users enterprise number as caller ID (not mobile number) Centralized enterprise CDR and call logs Enterprise call anchoring (except with reverse alternate number )
BRKUCC-2060
Cisco Confidential
93

Dial-via-Office: Reverse
With Dial-via-Office Reverse (DVO-R) Unified CM calls users mobile number
(configured mobility identity)
Once call leg to mobile is setup, Unified CM extends call to target/called number Unified CM extends call to mobile device over PSTN
Note: DVO-R requires Unified CM 7.0(2) or later
PSTN
CUMA extends SIP call setup request to Unified CM. CUMC signals call setup request over mobile data connection.
Once call leg is extended to target/called number, Unified CM connects the two call legs (mobile call leg and target call leg) at the PSTN gateway and call is anchored.
1 Mobile Data Network
BES
(w./ MDS)
Internet
Caller ID on call-back call leg is the Enterprise Feature Access number as configured within Unified CM (Call Routing > Mobility Configuration). Cisco Unified Mobile Communciator/Cisco Mobile client auto-answers call-back call leg
ASA TLS Proxy Mobile Voice Connection Mobile Data Connection Call Signaling DVO-R call-back leg setup Target call leg setup 94

Dial-via-Office: Reverse Alternate Number
Call-back call leg can be sent to userdirected alternate number (rather than
mobility identity)
Once call leg to alternate number is setup, Unified CM extends call to target/called number
PSTN
Unified CM extends call to user specified number over PSTN.
CUMA extends SIP call setup request to Unified CM.
CUMC signals call setup request over mobile data connection.
BES
(w./ MDS)
Once call leg is extended to target/called number, Unified CM connects the two call legs (alternate number call leg and target call leg) at the PSTN gateway.
Internet
Unified CM calls user specified number Alternate extension will not be autoanswered.
Cisco Unified Mobility Advantage ASA TLS Proxy Mobile Voice Connection Mobile Data Connection Call Signaling
NOTE: DVO-R alternate number calls are not anchored in the enterprise gateway. Mid-call features and desk phone pickup will not be possible with these types of calls.
DVO-R call-back leg setup Target call leg setup 95

Dial-via-Office: Forward
With Dial-via-Office Forward (DVO-F) client calls into Unified CM system using configured Enterprise Feature Access number.
Mobile client dials into system using number indicated in signaling from Unified CM. Caller ID must be received by Unified CM and must match configured mobility identity Once call leg from mobile is setup, Unified CM extends call to target/called number
Note: DVO-F requires Unified CM 7.1(3) or later
Mobile Voice 4 Network
PSTN
CUMA extends SIP call setup request to Unified CM. CUMC signals call setup request over mobile data connection.
Once call leg is extended to target/called number, Unified CM connects the two call legs (mobile call leg and target call leg) at the PSTN gateway and call is anchored.
BES
(w./ MDS)
Unified CM sends call setup signaling to mobile device over mobile date connection.
iPhone
Internet
3 Cisco Unified Mobility Advantage
Inbound caller ID must be available to the Unified CM used to identify inbound call from client. Cisco Unified Mobile Communicator/Cisco Mobile client automatically sets up call to Unified CM Enterprise Feature Access number.
ASA TLS Proxy Mobile Voice Connection Mobile Data Connection Call Signaling DVO-F call leg setup Target call leg setup 96

Dial-via-Office: DVO-F Design Considerations
Timer: At initiation of DVO-F call Unified CM

sets 30 second timer.
Inbound call from Cisco Mobile device must be received before this timer expires or DVO-F call will fail.
Caller ID requirement: Unified CM correlates

caller ID of inbound call from Cisco Mobile with SIP invite received over data channel. If inbound caller ID is not received or does not match, DVO-F call will fail
!
CAUTION
Inbound caller ID must be received by Unified CM for DVO-F calls to succeed

97

Dial-via-Office: CUMC/Cisco Mobile Client Settings If allowed by CUMA administrator, user can choose whether they want to:
Always dial via office Always dial direct Choose on a per call basis (Let me choose / Select per Call)
BRKUCC-2060
Cisco Confidential
Emergency numbers should always be dialed directly over the mobile voice network and not through the enterprise. CUMA administrator can specify emergency numbers that when dialed will bypass dialvia-office operation
99

Dial-via-Office: Cisco Unified Mobility Advantage Settings
If CUMA administrator forces Dial via Office, When dialing: / Dial Method setting is grayed out, missing, or DVO is only available choice.
BRKUCC-2060
Cisco Confidential
100

Dial-via-Office: DVO-F v. DVO-R Comparison
iPhone
Dial-via-Office Reverse/Call Back (DVO-R) Call flow description Inbound Caller ID required Enterprise Feature Access number must be reachable from PSTN User interaction required after dialing call CUMC receives call back from Unified CM after initiating a DVO call
Dial-via-Office Forward (DVO-F) CUMC calls in to Unified CM after initiating a DVO call
No No No
(call back leg is auto-answered)
Yes Yes No
(call forward leg is made automatically)
Users enterprise number presented to called party *

Yes
Cisco Confidential
Yes
101
* PSTN provider must support outbound caller ID

BRKSPM-2604_c1
Cisco Confidential
102

Design Considerations: CUMC/CUMA Scalability
Cisco Unified Mobile Communicator deployments scale in the following way:
Up to 1,000 mobile clients per CUMA servers with MCS-7845-H2/I2 Up to 500 mobile clients per CUMA servers with MCS-7825-H4/I4
CUMA 7.0(2) or later version) (Requires CUMA 7.1(3))
Up to 250 mobile clients per CUMA server with MCS-7825-H3/I3 or H2/I2 (Requires
Only one CUMA server per Unified CM cluster

For JTAPI call log integration within a deployment:
Up to 4 application or end users are configured within Unified CM each with a maximum of 250 associated user desk phones
CAUTION: With JTAPI call log integration each associated user desk phone will consume one CTI connection. The number of CTI connections utilized for CUMC must be considered with regard to overall cluster CTI limits
BRKUCC-2060
Cisco Confidential
103

Design Considerations: Redundancy Given a failure of CUMA or ASA or loss of mobile data network:
Data connection from CUMC client to the enterprise becomes unavailable Mobile device including Unified Mobility (Mobile Connect, 2 Stage Dialing, etc.) will continue to operate but without access to enterprise applications
(No dial via office, visual voicemail, conference notifications, directory access, messaging, or presence).
All calls will be dialed direct (even when DVO is forced) If Unified CM (or Unified CM to CUMA connection) fails, DVO is not possible. CUMC client receives message and may complete the call via direct dial.
X
MMP/SSL
MMP / SSL
DMZ
Internet
X
ASA TLS Proxy
X
CUMA 104

Cisco Confidential

Design Considerations: Bandwidth Utilization
Cisco recommends an unlimited data plan to avoid per minute or bandwidth-based charges In situations where unlimited plans are not available or cost prohibitive: Expect per user data utilization average of 5.6 MBytes per month without visual voicemail With visual voicemail, average will be much higher and therefore unlimited data plan highly recommended
Average bandwidth per user per month is 5.6 MB (without Visual Voicemail)
Each One Minute Voicemail Requires ~350 400 Kb DMZ

Operation Receive 30 second voice message Update a contact's availability Add contact from portal/device
Bandwidth (Bytes) 25,000 400 350
Receive/send 50 character text message

Receive a call log
450
400 1,000 2,500
Internet
MMP over SSL
MMP over SSL
ASA TLS Proxy
Receive a conference notification CUMA Make a successful DVO call
BRKUCC-2060
Cisco Confidential
105

Design Considerations: Roaming and Data Connection
Roaming across country boundaries with CUMC/Cisco Mobile clients can present challenges for data connectivity.
Typically moving across country boundaries results in roaming data charges even for unlimited data plans. Three ways to handle:
Pay data roaming charges. ($) Provision multiple handsets for CUMC within CUMA and Unified CM. ($$) Swap SIM cards in provisioned handset and manually update Unified CM Mobility Identity number (via user pages) and CUMC alternate call back number (on mobile device) DVO-R only. ($$ and user experience)
BRKUCC-2060
Cisco Confidential
106
BlackBerry MVS 5.0 Key End User Features

Powerful Cisco UC Features on your BlackBerry
Native BlackBerry Client Voice over WiFi Move calls between mobile and Wi-Fi networks Move calls to desk phone or one-time number Extension Dialing Outgoing Corporate Caller ID Transfer, Hold, Call Waiting One voicemail box
107
BlackBerry MVS 5.0 Architecture

Supports Wi-Fi and Mobile Networks
BRKUCC-2060
Cisco Confidential
108
Cisco UC Mobility Solutions

Summary
BRKSPM-2604_c1
Cisco Confidential
109

Summary
Unified Mobility User Unified Mobility Dial Plan and Call Routing Redundancy Scalability PSTN Connectivity and Utilization Caller ID Serviceability (CDRs and Logs)

Dual-mode Install and Configuration Enterprise Dial Plan and Call Routing Handoff Call Flows and Configuration Unified Mobility Integration WLAN Design Considerations Redundancy and Scalability
PSTN

WLAN
Communicator
BRKUCC-2060
Cisco Unified Mobile Communicator WLAN AP Application Integrations (802.11b/g) Security BES ProvisioningMDS) Configuration (w./ and Unified Mobility Integration Dial via Office and Deployment Considerations InternetRedundancy Scalability Cisco Bandwidth UtilizationUnified Cisco Unified ASA (Logs and CDRs) Mobility Mobile Serviceability TLS Advantage Proxy
Cisco Confidential

110
BRKUCC-2060
Cisco Confidential
111
Questions and Answers

Wrap Up
BRKSPM-2604_c1
Cisco Confidential
112

Additional Resources For additional information about Mobility solutions:
Check out the 7.x and 8.x Unified Communications SRNDs at:
http://www.cisco.com/go/ucsrnd
Consult product documentation and collateral:

Unified Mobility: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_2/ccmfeat/fsmobmgr.html Dual-mode Phones and Clients:
http://cisco.com/en/US/docs/voice_ip_comm/cumc/cisco_mobile/iPhone/8_0/FAQs/English/Cisco_Mobile_8_ch apter1.html (Cisco Mobile 8) http://cisco.com/en/US/docs/voice_ip_comm/cumc/cisco_mobile/iPhone/8_0/Cisco_Mobile_iPhone_8x_Admin_G uide.html (Cisco Mobile 8)
http://europe.nokia.com/support/download-software/nokia-call-connect-for-cisco (Nokia CC)

http://www.cisco.com/en/US/products/ps10589/tsd_products_support_series_home.html (Nokia CC)
Cisco Unified Mobile Communicator/Cisco Mobile and Cisco Unified Mobility Advantage: http://www.cisco.com/en/US/products/ps7270/prod_release_notes_list.html http://cisco.com/en/US/products/ps7270/products_installation_and_configuration_guides_list.html http://cisco.com/en/US/products/ps7271/products_user_guide_list.html http://www.cisco.com/en/US/docs/voice_ip_comm/cuma/CUMA_CUMC_Compatibility_Matrix.html http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_2/ccmfeat/fscumacumc.html
113
Complete Your Session Evaluation

Please give us your feedback!! Complete the evaluation form you were given when you entered the room This is session BRKUCC-2060 Yves Torjman Dont forget to complete the overall event evaluation form included in your registration kit
YOUR FEEDBACK IS VERY IMPORTANT FOR US!!! THANKS
BRKUCC-2060
Cisco Confidential
114
BRKUCC-2060
Cisco Confidential
115

Soluciones de Movilidad Corporativa Con Comunicaciones Unificadas

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Soluciones de Movilidad Corporativa Con Comunicaciones Unificadas

Uploaded by

Copyright:

Available Formats

Mobility: Enabling the Mobile Worker With Cisco Unified Communications

Cisco Unified Communications Enterprise Mobility Solutions

Dual-Mode Phones and Clients

2010 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Mobility

Cisco Unified Mobility

Dual-Mode Phones and Clients

Cisco Unified Mobility

Dual-Mode Phones and Clients

Cisco Unified Mobile Communicator

Dual-Mode Phones and Clients

BES (w./ MDS)

ASA TLS Proxy

Cisco Unified Mobility Advantage

Cisco Unified Mobile Communicator

Cisco Unified Mobility with Cisco Unified Communications Manager

2010 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Mobility

Dial Plan Considerations

2010 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Mobility

2010 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Mobility

Unified Mobility User

Remote Destination Profile Level Configuration

Call Routing and Media Resource Allocation for Remote Destinations

Call Routing and Media Resource Allocation for IP Phones

Device Level Configuration

2010 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Mobility

User can also enable/disable Mobile Connect Benefits:

* Requires minimum of Unified CM 7.1(3)

Cisco Unified Mobility

Remote destination pickup: Mobility softkey

Unified Mobility User PSTN

* Requires minimum of Unified CM 8.0(1)

Cisco Unified Mobility

Unified Mobility User

Single Enterprise Voicemail Box

Unified Mobility User

* Requires minimum of Unified CM 7.0

Cisco Unified Mobility

Line association Remote Destination pickup / Mobile Connect on/off

Cisco Unified Mobility

Inbound caller ID: 9195552345

Configured Remote Destinations: 4085551234 4085555678 4085550987 . . . 9195552345 9195556789 9195558765

If a match is found, the following occurs:

Cisco Unified Mobility

Mobile Voice Access

Enterprise Feature Access

Inbound Calls from Remote Destination

Desk phone Pickup

Cisco Unified CM Cluster

2010 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Mobility

Mobile Voice Access

Enterprise Feature Access

Inbound Calls from Remote Destination

Desk Phone Pickup

Internally Originated Direct Calls to Remote Destination *

Cisco Unified CM Cluster

* Intelligent Session Control requires minimum of Unified CM 8.0

2010 Cisco and/or its affiliates. All rights reserved.