Soluciones de Movilidad Corporativa Con Comunicaciones Unificadas

8/3/2019 Soluciones de Movilidad Corporativa Con Comunicaciones Unificadas

1/114


2/114

BRKUCC-2060

Mobility: Enabling the Mobile Worker WithCisco Unified Communications


3/114

2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialBRKUCC-2060 3

Cisco Unified Communications EnterpriseMobility Solutions

Yves TorjmanConsulting Systems EngineerEmerging [email protected]

Cisco Mobility Applications chapter (from the Unified CommunicationsSolution 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
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/mobilapp.htmlhttp://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/mobilapp.html


4/114


BRKUCC-2060 Abstract

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 radiosor non-802.11 wireless radios like DECT

This session covers Cisco's unified communications enterprisemobility solutions and in particular the following three solutions:

1. Cisco Unified Mobility

2. Dual-mode phones and clients

3. Cisco Unified Mobile Communicator

These solutions provide a comprehensive set of mobility features andfunctions for enterprise mobile workers and ensures that mobileworkers have persistent reachability and access to enterprise voiceservices regardless of location.

Individually or in tandem the three solutions not only provideenterprise connectivity to mobile users, but they also provideproductivity 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 toprovide a seamless mobility solution for enterprise mobile workers.


5/114


Agenda

Cisco UC Mobility Solutions Overview

Cisco Unified Mobility

Dual-Mode Phones and Clients

Cisco Unified Mobile Communicator

Cisco UC Mobility Solutions Summary


6/114


Cisco Unified MobilityCisco Unified Communications Enterprise Mobility Solutions

Fully integrated feature set within Cisco Unified CommunicationsManager (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

PSTN

Unified Mobility User Cisco UnifiedMobility

Enterprise


7/114 2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialBRKUCC-2060 7

Dual-Mode Phones and ClientsCisco Unified Communications Enterprise Mobility Solutions

PSTN


Enterprise

Dual-ModePhones and

Clients

Mobile VoiceNetwork

WLAN APWLAN(802.11b/g)

Enables mobile phones to leverage the enterprise IP telephony infrastructurefor making and receiving calls.

When associated to the enteprise Cisco Unified Wireless Network, the mobilephone 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 mobilevoice network for calls



Cisco Unified Mobile CommunicatorCisco Unified Communications Enterprise Mobility Solutions

PSTN


Enterprise

Dual-ModePhones and

Clients

Mobile VoiceNetwork

WLAN APWLAN(802.11b/g)

CiscoUnified

MobilityAdvantage

Internet

Cisco UnifiedMobile

CommunicatorASA TLS

Proxy

CiscoUnifiedMobile

Communicator

Solution allows mobile users to access enterprise applications from their mobilephones using a mobile client

Mobile phone client provides access to enterprise applications and services likecall processing, conferencing, presence, voicemail, and corporate directory.

Client connects to Cisco Unified Mobility Advantage server in the enterprise viasecure data connection

BES(w./ MDS)


9/114 2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialBRKSPM-2604_c1 9

Cisco Unified Mobility with CiscoUnified Communications Manager



Cisco Unified MobilityAgenda

Feature Review and Basic Functionality

Dial Plan Considerations

Design and Deployment Considerations



IP Phone

408 555-7890 408 555-6789

Remote Destination #1 Remote Destination #2

XXX XXX-XXXX

Remote Destination N

Remote Destination Profile

Virtual Phone

Unified Mobility

User

Call Routing andMedia ResourceAllocation for

RemoteDestinations

Call Routingand MediaResourceAllocation forIP Phones

Shared Line

Line Level SettingsDN: 408 555-1234

PartitionCalling Search Space

Cisco Unified MobilityConfiguration and Call Routing Concept

Remote DestinationProfile LevelConfiguration Device Pool

Calling Search Space Rerouting CSS User Hold Audio Source Network Hold Audio Source

Device LevelConfiguration Device Pool Common Device Configuration

Calling Search Space Media Resource Group List User Hold Audio Source Network Hold Audio Source



Cisco Unified MobilityFeature Review: Mobile Connect, MVA, and EFA

Mobile Connect Incoming calls to

users enterprise number rings bothdesk phone and configured RemoteDestination(s)

Mobile Voice Access (MVA) Providesthe ability to make calls from mobilephone using the enterprise IP telephony infrastructure

IVR based application requiring H.323 or SIP* VXML gateway

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 identicalfunctionality as MVA without the IVR component

PSTN

Unified

MobilityUser

MobileConnect

PSTN

UnifiedMobility

User

MVA/EFATwo-Stage

* Requires minimum of Unified CM 7.1(3)



Cisco Unified MobilityFeature Review: Pickup and Mid-Call Features

Desk Phone/Remote DestinationPickupOnce incoming mobility call hasbeen answered, call can be moved betweendesk phone and RD(s)

Desk phone pickup: Hangup and resume, mid-call hold (*81) and resume, or mid-call session

handoff * (*74) and answer.

Remote destination pickup: Mobility softkey(Send call to mobile) and answer.

Mid-Call FeaturesProvidesthe ability to invoke enterprise

features Hold, Resume, Transfer,Conference, Directed Call Park, andSession Handoff* from the RD/mobilephone for active mobility calls

PSTN

UnifiedMobility

User

Mid-CallFeatures

PSTN

UnifiedMobilityUser

Desk/RD

Pickup

* Requires minimum of Unified CM 8.0(1)



Single Enterprise VoicemailBox (mobile voicemailavoidance) Per RD timersensure that when mobility user isunavailable, unansweredincoming calls are forwarded to

enterprise voicemail box ratherthan mobile or other voicemailbox

Access Lists Per RD accesslists can be defined to filter or

screen incoming calls to amobility user based on caller ID.Filtering allows or blocks callsfrom being extended to theusers RD. Time of day filtering*can also be applied.

PSTN

UnifiedMobilityUser

Single Enterprise

Voicemail Box

Unavailable

X

EnterpriseVoicemail

MobileVoicemail

PSTN

Unified Mobility

User

AccessLists

AccessList

Cisco Unified MobilityFeature Review: Single Enterprise VM Box & Access Lists

* Requires minimum of Unified CM 7.0



Cisco Unified MobilityRemote Destination Configuration

DNEnterprise Phone / Directory Number

DN Remote Destination Profile

Remote Destination #1


Remote Destination/Mobile number

End-user timers(mobile VM avoidance, etc.)

RDP this RemoteDestination is associated toRemote Destination pickup

/ Mobile Connect on/off

Time of day andaccess list call filtering

Line association



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 thereplacement of the users remote destination/mobile

number with the users enterprise directory number.

PSTN

Cisco UnifiedCM Cluster

PSTNGateway

Configured RemoteDestinations:

408555123440855556784085550987

919555234591955567899195558765

.

.

.

Inbound caller ID:9195552345

MATCH

For all inbound calls to Cisco Unified CM thecaller ID is automatically compared against allconfigured remote destinations

Cisco Unified MobilityDial Plan Considerations: Automatic Caller ID Matching




PSTN

Enterprise

Enterprise FeatureAccess

(Two-Stage Dialing)Outbound Calls

Generated from RemoteDestination Phone

PSTN

Gateway

DTMF

Mobile Connect

Inbound Calls Answeredat Desk Phone or at

Remote Destination Phone

In-ProgressCall

Mid-CallFeatures

DeskphonePickup

*81

Inbound Calls fromRemote Destination

Incoming Calls fromConfigured RemoteDestination Phones

Cisco Unified MobilityEnterprise Call Anchoring: Mobility Calls

Mobile Voice Access

Outbound CallsGenerated from

Remote DestinationPhone

All calls made or received on behalf of users RD are

automatically anchored in the enterprise gateway




PSTN

Enterprise

Enterprise FeatureAccess

(Two-Stage Dialing)Outbound Calls

Generated from RemoteDestination Phone

PSTN

Gateway

Mobile Connect

Inbound Calls Answeredat Desk Phone or at

Remote Destination Phone

Mid-CallFeatures

Inbound Calls fromRemote Destination

Incoming Calls fromConfigured RemoteDestination Phones

Cisco Unified MobilityEnterprise Call Anchoring: Mobility Calls (cont.)

Mobile Voice Access

Outbound CallsGenerated from

Remote DestinationPhone

All calls made or received on behalf of users RD are

automatically anchored in the enterprise gateway

Internally Originated DirectCalls to Remote Destination *

Internally Originated Direct Calls toRemote Destination Numbers

* Intelligent Session Control requires minimum of Unified CM 8.0

DeskPhonePickup




Dial Plan Considerations


21/114


Cisco Unified MobilityDial Plan Considerations: Outbound v. Inbound Calling

Outbound calls formobility-enabled users

RemoteDestination

Associated IPphone / enterprise

number


22/114


PSTN

Outgoing Calls from RDP:Routing from Remote Destination(MVA/EFA 2-Stage Dialing, Mid-CallConferencing/Transfer)

Unified Mobility User

Cisco Unified MobilityDial Plan Considerations: Outbound Call Routing (from RD)

Calling Search Space

Remote Destination Profile (RDP) contains two CSS settingswhich control call routing from an RDP perspective:


23/114


PSTN

Outgoing Call to RDP:Routing to Remote Destination(Mobile Connect)


Cisco Unified MobilityDial Plan Considerations: Outbound Call Routing (to RD)

Calling Search Space

Rerouting Calling Search Space

Remote Destination Profile (RDP) contains two CSS settingswhich control call routing from an RDP perspective:


24/114


Cisco Unified MobilityDial Plan Considerations: Outbound v. Inbound Calling


RemoteDestination

Inbound calls formobility-enabled users

Remote Destination Profile:

CSS Rerouting CSS


number


25/114


PSTN

Enterprise



PSTNGateway

GW CSSPartition 1

Partition 2

Partition 3

RemoteDestination

Phone

MVA DID

EFA DID

Internal DNsRDP CSS

Partition 7

Partition 8

Partition 9

Line CSSPartition 4

Partition 5

Partition 6

+

Resulting CSS

Cisco Unified MobilityDial Plan Considerations: Inbound Call Routing

If set to Trunk or Gateway Inbound Calling Search Space (default), then incoming calls fromconfigured 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.

RemoteDestination

Profile

Incoming calls coming from non-RDs are not affected by this service parameter they will always use thetrunk or gateway inbound CSS. Likewise this parameter has no impact on outbound call routing

Inbound call routing behavior for calls from RDs isdependent upon Inbound Calling Search Space forRemote Destination service parameter


26/114


Cisco Unified MobilityRD Number Configuration: PSTN Steering v. Caller ID Matching

1. Configure the number as it would be dialed from the enterpriseincluding any PSTN access or steering digits

2. Configure the number to match incoming caller ID from the PSTN

9 + 1 + (XXX) XXX - XXXX

(XXX) XXX - XXXX

Caller ID from PSTN:

If option 2 is chosen, an Application Dial Rule (or other prefixingmechanism) is used to add appropriate PSTN access/steering digits

408 10 0 91PSTN_SJ

There are two options when configuring RD numbers:

To Dial PSTN:


27/114


Enterprise

PSTN

408 555-7890

Mobile Voice Access

Automatic CallerID Matching/Call Anchoring

Enterprise Feature Access

CompleteMatch

CID:

4085557890

RD#:

4085557890

EnterprisePSTN GW =

RemoteDestination

Complete match v. partial match is controlled by theMatching Caller ID with Remote Destination

Cisco CallManagerservice parameter

Default

Cisco Unified MobilityRD Number Configuration: Complete v. Partial Matching

Mobile Voice Access/Enterprise Feature Access identification

Remote destination direct inbound call anchoring

RemoteDestination

Profile

RemoteDestination

If RD numbers are configured to match incoming caller ID (with

Application Dial Rules or other digit prefixing used for outgoingcall routing), incoming calls from remote destinations areautomatically matched for:


28/114


Enterprise

PSTN408 555-7890

Mobile Voice Access

Automatic CallerID Matching/Call Anchoring

Enterprise Feature Access

Complete

Match

EnterprisePSTN GW

RemoteDestination

RemoteDestinationProfile

Partial

MatchCID:

4085557890

RD#:

9 1 4085557890

=

# of Digitsto Match:

10

Cisco Unified MobilityRD Number Configuration: Complete v. Partial Matching

If RD numbers are NOT configured to match incomingCallerID (i.e. PSTN steering digits are included), PartialMatching must be configured in order to matchCallerID for incoming calls from Remote Destinations.

Number of digits matched when using partial match is controlled bythe Number of Digits for Caller ID Partial Match Cisco CallManager

service parameter

RemoteDestination

Default


29/114


Cisco Unified MobilityRD 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 digitsbased 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 doneusing translation or route patterns, or route list/route group constructs


30/114


Cisco Unified MobilityDial Plan Considerations: Inbound v. Outbound Calling


RemoteDestination

Inbound calls formobility-enabled users

Remote Destination Profile:

CSS Rerouting CSS

Remote Destination Number:

Include PSTN Steering Digits Match Caller ID

Inbound Caller ID Matching:

Complete

Partial


number

Inbound CSS for RD:

Inbound Trunk/Gateway RDP CSS (+ line CSS)


31/114

2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialBRKSPM-2604_c1 31




32/114


Cisco Unified MobilityDesign Considerations: Scalability

Cisco Unified Mobility supports the following capacities:

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 usersdecreases

Mobility-Enabled Usersper Cluster

Mobility-Enabled Usersper Node

MCS-7845 15,000 3,750

MCS-7835 10,000 2,500

MCS-7825 4,000 1,000


33/114


Cisco Unified MobilityDesign Considerations: Redundancy

Redundancy for RD and RDP configurationprovided via device pools/CM groups.

Mobile Connect (including desk / remotephone pickup), Enterprise Feature Access(EFA), and mid-call feature functionality areall natively redundant

No redundancy for Mobile Voice Access

If Publisher is down, MVA is not available

Enterprise Feature Access 2-Stage Dialing isstill possible.

If Publisher is down, changes to MobileConnect status (on/off) via EFA are not

saved (and therefore do not take affect).

X X


34/114


Cisco Unified MobilityDesign Considerations: Redundancy (cont.)

Gateway and PSTN access redundancy asusual, however branches in SRST mode willhave no or very restricted Unified Mobilityfunctionality:

If call comes into central site/originates fromextension 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 fromremote site while site is in SRST mode, call willnot be extended to remote destination becauseUnified CM is not available to determine remote

destination number. Call will be extended to deskphones

X X


35/114


Cisco Unified MobilityDesign Considerations: PSTN Connectivity

DTMF Relay: Mid-call features and EnterpriseFeature Access 2-Stage Dialing require out-of-band (OOB)DTMF relay between enterprise PSTN gateway and CUCM

TDM Connectivity: Mobile Connect functionality issupported 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.

For inbound Mobile Connect calls: Unified CM needs to knowanswer has occurred at remote destination in order to stopringing other devices (desk phone and other remotedestinations).

For desk phone pickup: Unified CM needs to know disconnecthas occurred at remote destination in order to put desk phonein hold state so user can resume call.

For single enterprise voice mail box: Unified CM needs to knowthat mobile voicemail has answered (Answer Too Soon Timer) inorder to disconnect the call leg.


36/114


Cisco Unified MobilityDesign Considerations: PSTN Connectivity (cont.)

VoIP Connectivity: Unified Mobility call flows andfunctionality are supported over service provider SIP trunkPSTN connections.

Cisco Unified Border Element is required to terminateUnified CM SIP trunk and provider SIP trunk

Mid-call Features are not supported for this type of PSTNconnection due to potential DTMF interop issues

G.711 required between enterprise gateway and CUCM forMVA. 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.


37/114


Cisco Unified MobilityDesign Considerations: Caller ID

Caller ID For Unified Mobility deployments,customer should work with their service provider toensure the following:

Inbound Caller ID

If Enterprise Feature Access (mid-call features or 2-stagedialing) is required, service provider must send appropriateinbound caller ID to enterprise.


38/114


Cisco Unified MobilityDesign Considerations: Caller ID (cont.)

Outbound Caller ID

If original caller ID for Mobile Connect calls is to be sent to mobilityusers RD, service providermust not restrict caller ID on trunk toonly DIDs assigned to that trunk.

Redirected Dialed Number Identification Service (RDNIS) and SIPDiversion Header

Some providers allow unrestricted caller ID provided the RDNIS field or SIPDiversion Header contains a DID handled by the trunk. Contact your provider to seeif they honor RDNIS or SIP Diversion Header

When checking the Redirecting Number ID Delivery Outbound field on the gatewayor trunk configuration page in Unified CM 7.1(3) and later, system will populateRDNIS/SIP Diversion Header with called users enterprise number.

If unable to provide unrestricted caller ID, then ensure meaningfulenterprise caller ID is sent.


39/114


Cisco Unified MobilityDesign Considerations: PSTN Utilization

Planning and allocating PSTN gateway resources isextremely important for Unified Mobility

Mobility call flows typically involve multiple PSTN call legs

Must increase PSTN gateway resources to handle large numbersof mobility users

How much of an increased load on PSTN gateways willvary widely depending on call patterns and volumes.

Absent information about an enterprises call patternsand volumes, some techniques can be used to minimize

utilization of PSTN gateway resources.


40/114


PSTN

1

Dials: 1 408 555-1234

Call rings only oneRemote Destination(408 555-7890)

6408 555-7890

Cisco UnifiedCM cluster

5

Call to onlyone RemoteDestination

routed viagateway

DN: 408 555-1234

RemoteDestination

Profile

DN: 408 555-1234

Call extendedto desk phone

2

3

Call extended toRemote DestinationProfile

SHARED LINE

PSTNGateway

Phone A

RemoteDestination:408 555-7890

Call placed to only

one associatedRemoteDestination 4

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

Limit to oneRemote

Destination

Access List:

Block/allow calls

from incomingnumbers

Add ToDto Access

Lists

XX Disable Mobile

Connect when

not needed

Access listslimits calls to

PSTN

Each RD will consume a DS0.

DS0 will be utilized for up to 10seconds even if call is notanswered at RD

+

* ToD ACLs supported with Unified CM 7.0 and later

Cisco Unified MobilityDesign Considerations: Minimizing PSTN Utilization


41/114




42/114


Dual-Mode Phones and ClientsAgenda


Cisco Unified Mobility Integration

Basic Call Flows and Dial Plan Considerations

Handoff Call Flows



43/114





44/114


Dual-Mode Phones and ClientsArchitecture

PSTN

WLANAPWLAN

(802.11 a/b/g)

Mobile VoiceNetwork

Enterprise

Dual-mode phones provide the ability to leverage the enterprise IP

telephony infrastructure (via WLAN connectivity) for making andreceiving calls inside the enterprise.

When outside the enterprise the dual-mode device falls back to theGSM/PSTN network.

Dual-mode client runs on the dual-mode phone device and registers

to Unified CM for call processing services

Dual-modeMobile Phone


45/114


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 activecall

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.

Dual-Mode Phones and ClientsFeature Summary PSTN

WLAN


46/114


PSTN

WLAN

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]

Dual-Mode Phones and ClientsDevices & Clients: Nokia Call Connect

Additional features and services:

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 4support (handset dependent).

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)

Automatic* (and manual) handoff: Hand-in (Cellular to WLAN)

Hand-out (WLAN to cellular)

* Supported only with NCC 2.1 and 3.2 versions of handsets

Nokia Call Connect 2.1

Nokia E72

Nokia E66

Nokia E71

Nokia E75

Nokia E61i

CWLAN


47/114


Dual-Mode Phones and ClientsDevices & Clients: Cisco Mobile 8.0 (iPhone)

Cisco Mobile 8.0NewHandset support: iPhone 3G, 3GS, 4

Firmware 3.0.1 or later

Additional features and services:

Two active call support with call swap

Corporate Directory Lookup integration to Microsoft ActiveDirectory 2003 or 2008 (global cataloging must be enabled).

Visual voicemail lists when integrated to Unity Connection 7.x or8.0 (includes enterprise voicemail MWI)

Motion-activated voice dialing integration to Unity Connection 7.xor 8.0 leveraging Speech Connect/voice-enabled directoryhandlers.

Transfer of active call from desk phone to iPhone using deskphone integration.

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)

Manually invoked handout : Hand-out (WLAN to cellular):

Mobility softkey method (system calls client) Handoff number method (client calls system)

PSTN

WLAN


48/114




D l M d Ph d Cli


49/114


PSTN

WLANAPWLAN

(802.11 a/b/g)

Mobile VoiceNetwork

Dual-mode

Mobile Phone

WLAN client on dual-mode phone registers to Cisco Unified CM asusers 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)

UnifiedMobility User Cisco Unified

Mobility

Dual-ModePhones and

Clients

Dual-Mode Phones and ClientsCisco Unified Mobility Integration

D l M d Ph d Cli t


50/114



DN

Remote Destination Profile



Mobile phone number of dual-mode phone


Dual-mode phone this

Mobility Identity isassociated to. (Note: No lineassociation required)

Remote Destination pickup/ Mobile Connect on/off


DN

Dual-Mode Device

Mobility Identity

Remote Destination(s)

+

Dual-Mode Phones and ClientsCisco Unified Mobility Integration: Configuration


51/114


Basic Call Flows and Dial Plan Considerations


D l M d Ph d Cli t


52/114


EnterpriseCisco UnifiedCM Cluster

MobilityIdentity

PSTNGateway

PSTNMobile VoiceNetwork

Call 51234

408 555-7890SamePhone

Note: When the dual-mode phone is in the WLAN, incoming

calls to the enterprise number will not ring the mobile voice/cellular interface

DN: 51234DID: 408 555-1234

Dual-Mode MobileVoice NetworkConnectivity Only

Dual-Mode WLANConnectivity

Unified MobilityUser

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.

Call 1 408 555-1234

AP

Dual-Mode Phones and ClientsIncoming Call Routing

WLAN

X

SIP Dual Mode Alert Timer serviceparameter: Determines how long

Unified CM checks for Cisco Mobile8.0 client on the network beforeextending call to mobile voiceinterface (via Mobile Connect). Default is 1500 msecs Recommend 3000 msecs

D l M d Ph d Cli t


53/114


Dial plan is challenging: User dialing method within enterprise will bedifferent than from mobile voice network

Enterprise

Outgoing calls from GSM are dialed just like a typical mobilephone call

Outgoing calls are routed within WLAN just like any enterprisephone


MobilityIdentity

PSTNGateway

PSTN

SamePhone


AP

Dual-Mode Phones and ClientsOutgoing Call Routing

WLAN

Mobile VoiceNetwork

X


Dual-Mode WLANConnectivity

Emergency calls should always be dialeddirectly over the mobile voice network.

CAUTION!

D l M d Ph d Cli t


54/114


Enterprise

Dial plan within Unified CM can be configured to prefix steeringdigits to calls made by dual-mode devices when in the WLAN

Contacts on mobile device will all need to be configureduniformly (e.g. ten-digit/full E.164 or + followed by ten-digits/E.164)


MobilityIdentity

PSTNGateway

PSTN

SamePhone


AP

Dual-Mode Phones and ClientsOutgoing Call Routing: Normalization

WLAN

Mobile VoiceNetwork

X


Dual-Mode WLAN

Connectivity

User dials tendigits (manuallyor from contacts)

User dials tendigits (manuallyor from contacts)

Call is then forwarded toPSTN or rerouted to localextension as appropriate

Translation Pattern

Prefix Digits: 9 1

D l M d Ph d Cli t


55/114


1. User Effort: Users checks for Unified CMregistration icon.

If present, user dials using enterprise dial plan (abbreviateddialing, PSTN steering digits, etc.)

If not present, user dials using PSTN dialing method (+ and/orE.164)

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 appropriateand/or prefixes appropriate PSTN steering digits.

End-User dialing behavior Dialing on the mobile voicenetwork/PSTN is different than dialing within the enterprise network.

Dual-Mode Phones and ClientsDesign Considerations: Dial Plan

Nokia CC 2.x

Cisco Mobile 8.0 Nokia CC 2.x client provides + prefix translation option and Dialingprefix 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 rulesfrom Unified CM to improve user dialing experience

Recommended


56/114


Handoff Call Flows


Dual Mode Phones and Clients


57/114


Dual-Mode Phones and ClientsHandoff Terminology: Hand-Out v. Hand-InMoving calls from enterprise WLAN to cellular network and

vice-versa is generally referred to as HandoffPSTN

Gateway

AP

PSTNMobile Voice

Network

Enterprise WLANCellular/Mobile Voice

PSTN

Gateway

PSTNMobile Voice

Network

Cellular/Mobile Voice

Hand-out: Moving calls fromenterprise WLAN to cellular network

Hand-in: Moving calls from cellularnetwork to enterprise WLAN

Enterprise WLAN

AP



58/114


Cisco Mobile 8.0 supports two methods of hand-out:

Mobility softkey method user/client receives call from Unified CM system onmobile voice interface

Handoff DN method user/client automatically makes call to handoff numberconfigured in Unified CM

o Method used depends on Transfer to Mobile Network setting on CiscoDual-Mode for iPhone device configuration page

Call Park: Application will auto-park calls on handoff failure enabling userto 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 whereapplication is closed. On return to application user is prompted to auto-retrievethe parked call (assuming caller is still on the line).

Dual-Mode Phones and ClientsCisco Mobile 8.0: Handoff Considerations

Handoff number configured inUnified CM (Call Routing > MobilityConfiguration)

Hand-in is not supported with

Cisco Mobile 8.0



59/114


EnterpriseCisco Unified

CM Cluster

PSTNGateway

PSTNMobile

VoiceNetwork

AP

SamePhone

Handoff Number: 1234Handoff Number DID: +1 408 555 1234

1

MobileVoice

WLAN

An existing call between

the iPhone dual-modedevice on the enterprise

WLAN and a phone on thePSTN.

User pushes Use Mobile

Network softkey from in-

call menu and iPhone

dual-mode client indicates

to Unified CM its intentionto hand-out.

2

Unified CM generates a

call to the dual-mode

users configured mobilityidentity number via theenterprise PSTN gateway

3

User is now able to moveout of the enterprise and

away from enterprise

WLAN coverage.

4

On answer, Unified CM

redirects original RTPstream that was traversing

the WLAN to the

enterprise PSTN gateway

resulting in enterprise call

anchoring.

5

Handoff indication signaled to Unified CM overWLAN which in turn generates call to dual-modephones mobile voice network interface. Onceanswered call media is redirected from WLAN to

enterprise PSTN gateway.

Initial voice mediapath

Handoff backgroundcall leg

Final voice mediapath

Dual-Mode Phones and ClientsCisco Mobile 8.0: Hand-Out Mobility Softkey method



60/114



CM Cluster

PSTNGateway

PSTNMobile

VoiceNetwork

AP

SamePhone


MobileVoice

WLAN

Hand-off indication signaled to Unified CM overWLAN which in turn generates call from dual-modephones mobile voice network interface to handoff

number. Once answered call media is redirected

from WLAN to enterprise PSTN gateway.

1


the iPhone dual-modedevice on the enterprise

WLAN and a phone on thePSTN.

iPhone dual-mode client

automatically makes call

via mobile voice networkinterface to HandoffNumber configured within

Unifed CM.

3

User is now able to move

out of the enterprise and

away from enterprise

WLAN coverage.

4

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.

5




Dual-Mode Phones and ClientsCisco Mobile 8.0: Hand-Out Handoff DN method

Because Unified CMrelies on inbound

caller ID to identifythe call beinghanded off, ensurenative iPhone callerID is(Tap: Settings > Phone >Show My Caller ID)

User pushes Use Mobile

Network softkey from in-

call menu and iPhone

dual-mode client indicates

to Unified CM its intentionto hand-out.

2



61/114



CM Cluster

PSTNGateway

PSTNMobile

VoiceNetwork

APMobileVoice

SamePhone


WLAN2

The Nokia dual-mode userbegins to leave the

enterprise.

1


the Nokia dual-mode

device on the enterpriseWLAN and a phone on the

PSTN.

4

Once background call received by

Unified CM, calling number is

compared against system dual-

mode mobility identities andprovided a match is found, media

stream on WLAN is redirected to

the PSTN gateway

As the WLAN signal strength

drops below

-73dBm (default) for a period

of 1 second (default), a silentbackground call is opened toCellular handover number+1 408 555 1234 on the

Unified CM system

3

Background call opened to the configuredCellular Handover Number in VCC settings (onNokia device) which corresponds to the

Handoff Number configured within Unified CM.

Dual-Mode Phones and ClientsNokia Call Connect 2.x: Hand-Out (WLAN to Cellular)




Hand-out can also be invoked manually by the userusing the in-call menu Switch to Cellular orSwitch to GSM options.

Manual invocation of handoff stops operationof auto-handoff for duration of call.

This option must be used for devices thatdont support automatic-handoff.

Automatic handoff isonly supported on theNokia E52, E55, E72,and E75 handsets

Unified CM relies on inboundcaller ID to identify the callbeing handed off Ensureinbound caller ID ispresented to Unified CM



62/114



CM Cluster

PSTNGateway

PSTNMobile

VoiceNetwork

APMobileVoice

SamePhone





WLAN

The Nokia dual-mode usermoves into the enterprise

and the device associates

in the background to

WLAN infrastructure and

registers to Unified CM

Once background call received byUnified CM, calling number is

compared against system dual-

mode mobility identities andprovided a match is found, RTP

stream on PSTN gateway is

redirected to the PSTN gateway


the Nokia dual-mode

device on the mobile voice

network and a phone on

the PSTN.

1

2

After registration the

device waits for 60seconds (default) andthen opens a silent

background call to VoIPHandover number 1234on the Unified CM system

3

4

Background call opened to the configured VoIPHandover Number in VCC settings (on Nokiadevice) which corresponds to the Handoff

Number configured within Unified CM.

Dual-Mode Phones and ClientsNokia Call Connect 2.x: Hand-In (Cellular to WLAN)

Hand-in can also be invoked manually by the userusing the in-call menu Switch to WLAN option.Manual invocation of handoff stops operation of

auto-handoff for duration of call.

Automatic handoff isonly supported on theNokia E52, E55, E72,

and E75 handsets


63/114






64/114


Similar VoWLAN network designrequirements as Cisco UnifiedWireless IP Phone 7921G and7925G

Cell radius or power-level boundary ofapproximately -67 dBm (or less) isrecommended in order to minimize packetloss.

Same channel cell separation of 19 dBm is

recommended to minimize co-channelinterference

Channel cell overlap (on non-adjacentchannels) should be 15-20% to ensureseamless roaming between APs.

Bluetooth headsets are notrecommended with dual-mode

handsets due to potentialinterference on the 2.4 GHz band.

Bluetooth headsets are notsupported for handling calls inCisco Mobile 8.0. Can only be usedto listen to voicemail messages.

For more information on VoWLAN Design, seethe Voice over Wireless LAN 4.1 DesignGuideat:

-

Dual-Mode Phones and ClientsDesign Considerations: Voice over WLAN

http://www.cisco.com/en/US/docs/solutions/Enterprise/M

obility/vowlan/41dg/vowlan41dg-book.html

Dual-Mode Phones and ClientsWLAN


65/114


Dual-Mode Phones and ClientsDesign Considerations: Scalability

Scalability implications for dual-mode phones and clients

include:Registration/device load on Unified CM for each dual-mode device/client Theoretical maximum of 30,000

Traffic load on the Wireless LAN Infrastructure Per AP

call capacity: 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 ofactive 802.11b clients, a maximum of 7 simultaneous VoWLAN calls per channelcell is supported.

Unified Mobility remote destination/mobility identitycapacity Maximum of 15,000 total

A single call between two dual-mode phones associated to the same APis considered to be two simultaneous VoWLAN calls.

PSTN



66/114


Dual-Mode Phones and ClientsDesign 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

PSTN

WLAN

X

XX

Gateway and PSTN access redundancy is as usual, howeverbranches 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 nativelyredundant within Unified CM



67/114


Dual-Mode Phones and ClientsDesign Considerations: Caller ID

Caller ID For dual-mode deployments, work with yourservice provider to ensure proper caller ID behavior.

Inbound Caller ID Service provider must send appropriateinbound caller ID to enterprise if any of the following are required:

Hand-out (WLAN to cellular) for Nokia CC or Cisco Mobile 8.0 (HandoffDN method only).

2-stage dialing automation (Enterprise Feature Access) on Nokia CC.

Any other Unified Mobility features that rely on inbound caller ID (mid-

call features, automatic inbound call anchoring).

Dual-mode device must also have native caller ID enabled in order toensure caller ID is sent to provider network

Outbound Caller ID

All VoIP calls and 2-stage dialed calls will send users enterprise numberrather than the users mobile number.

Mobile Connect considerations (original caller ID, RDNIS/SIP Diversionheader).

Caller ID


68/114





69/114



Security


Dial-via-Office Call Flows and 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)

Cisco Unified Mobile CommunicatorAgenda


70/114






71/114

2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialBRKUCC-2060 71Cisco Adaptive

Security Appliance (ASA)

CiscoMeetingPlace

Cisco Unity/Unity

Connection

Microsoft ActiveDirectory

Cisco Unified CM

Cisco UnifiedPresence

DMZ

UU

MPMPMicrosoftExchange

PSTN

PSTNGateway

Enterprise and UCApplications

iPhone

Cisco Unified Mobile CommunicatorArchitecture

Cisco UnifiedMobile

Communicator/Cisco Mobile 7.x

Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)

The Cisco Unified Mobile Communicator (CUMC) solution enables mobileusers to utilize enterprise applications from their mobile phones using amobility client that communicates with a mobility server inside theenterprise (client-server architecture)

Cisco UnifiedMobility Advantage

MMPover SSL

MMPover SSL

MMP

over BES

MMP

over BES



72/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ

Cisco AdaptiveSecurity Appliance(ASA)

UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Administration and Text Messaging

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


REQUIRED Web-based Administration and User

portals

Native support for messaging betweenCUMC/Cisco Mobile clients (IM/Text).*

Secure and guaranteed delivery

No SMS/Text message charges

Caveat: Text messaging only supportedbetween CUMC clients

Cisco Unified Mobility Advantage

* Messaging not supported on CiscoMobile 7 for iPhone.



73/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Secure Connectivity

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


REQUIRED(except for Blackberry-only deployments)

Provides certificate-based secure TLSconnection between client and enterprise.

One-way certificate exchange serverprovides CA-signed (VeriSign orGeoTrust) certificate.

Client verifies server certificate using pre-

loaded root certificate. ASA also provides additional security with

deep packet inspection for MMP traffic.

Adaptive Security Appliance (ASA)

REQUIRED if Blackberry clients deployed Provides secureTLS connection between

client and enterprise.

Pushes client software to Blackberrydevices.

Manages security policies for clientsoftware distribution as well as client

operation.

Blackberry Enterprise Server (BES)



74/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Directory Integration

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


REQUIRED Integration via LDAP

No change to schema Server uses read-only account

Client /user authentication

Neither CUMA server nor CUMCclient store password

Corporate directory lookups

Active Directory 2000, 2003 or 2008

Microsoft Active DirectoryLDAP



75/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Call Logs and Dial-via-Office

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


REQUIRED Unified CM 4.x, 5.x, 6.x, 7.x, and 8.x

Desk phone call log integration

Call history (missed, placed,received)

Integration via JTAPI/CTI

Dial-via-Office Integration via SIP

Requires Unified CM 7.0 and later

Unified Communications

Manager

SIP, JTAPI/CTI



76/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Voicemail Integration

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


OPTIONAL Cisco Unity 4.x or later (unified or

integrated messaging)

Cisco Unity Connection 7.x or later

Enterprise message waiting indication(MWI)

Visual voicemail allowing visualnavigation of voicemail messages.

Messages downloaded to client overdata connection

No need to dial in and navigate TUI

Integration via IMAP

Secure messaging support

Cisco Unity/Unity Connection 7.x

Cisco Unity/Unity Connection

IMAP



77/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Conferencing Integration

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


OPTIONAL Requires Microsoft Exchange 2000,2003, or 2007

Meeting list/conference notifications*

Integration via WebDAV to MicrosoftExchange

List of meetings and reminders

Requires Cisco Unified

MeetingPlace 6.x, 7.x, or 8.x Call Me (click/tap-to-join)**

Integration via SOAP to CiscoUnified MeetingPlace

Cisco Unified MeetingPlace callsclient back automatically withoutneed for entering meeting ID orpassword

Cross launch of WebEx MeetingCenter client for meetings withWebEx data share.**

Cisco Unified MeetingPlace

SOAP

WebDAV

** Supported only on Cisco Mobile 7clients for Blackberry and iPhone

* Meeting lists not supported on CiscoMobile 7 client for Blackberry.Conference notifications/lists arehandled via native Blackberry calendarand BES integration to Exchange.

Dept. All Hands1:45 PM



78/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Presence Integration

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


OPTIONAL Requires Cisco Unified Presence 7.0(2)

or later

Ability to set and sendpresence/availability status*

Ability to receive presence/availability*status for all enterprise contacts.

Synchronized buddy list with CiscoUnified Personal Communicator (CUPC)PC client.

Integration via SIP/SIMPLE

Cisco Unified Presence

SIP/SIMPLE

* Presence not supported on CiscoMobile 7 for iPhone.



79/114


CiscoMeetingPlace

Cisco Unity/Unity

Connection


Cisco Unified CM


DMZ


UU


PSTN

PSTNGateway


iPhone

Cisco Unified Mobile CommunicatorFeature Review: Personal Contacts and Calendaring

Cisco UnifiedMobile


Mobile VoiceNetwork

Internet

Mobile DataNetwork

(Data Channel)

BES(w./ MDS)


Cisco UnifiedMobile


OPTIONAL Microsoft Exchange 2000, 2003, or 2007

Personal Outlook integration

Access to users personal Outlookcontact lists

Integration with users Outlookcalendar

Automatic presence status updatesbased on calendar entries(meeting/appointment start and stop times).

User must have an Exchangemailbox.

Integration via WebDAV

Microsoft Exchange

WebDAV



80/114


Example devices

E61i E71E51 N95 N96

Cisco Unified Mobile CommunicatorHandset Support

iPhone

3G or 3GS

Cisco Mobile 7 (CUMC client) supported oniPhone 3G, 3GS , 4 handsets meeting thefollowing criteria:Firmware version 3.0.1 or lateriTunes 8.2 or later

Cisco Unified Mobile Communicator 7.0supported on most Nokia E-series and N-series handsets meeting the followingcriteria: 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

9700 Bold

Cisco Mobile 7.1 (CUMC client) supported on Blackberryhandsets meeting the following criteria:

BlackBerry OS version 4.3 or higher Non-touchscreen devices only Enterprise activated

9000 Bold 9600 Tour8300 Curve 8900 Curve8200 Flip

ProtgG710

SamsungBlackjack II HTC S620

MotorollaQ9H

SamsungACE

Example devices

Cisco Unified Mobile Communciator 7.0supported on Windows Mobile handsets meetingthe 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

All handsets require the following: Insalled VeriSign or GeoTrust root certificate.No restrictions on running 3rd party applicationsData plan from the service provider which includes full

internet access, not just email

Example devices



81/114


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)

iPhone

Via integration with Unified Mobility* Microsoft Exchange required

Cisco Unified Mobile CommunicatorMobile OS Feature Summary


82/114


Security Considerations




83/114


Cisco UnifiedMobility

Advantage

ASATLS Proxy

DMZ

Option 1:ASA acts as both firewalland TLS Proxy

Enterprise

MPMP

UU

UCApplications

Internet

Mobile DataNetwork

(Data Channel)

MMP overSSL

MMP overSSL

Cisco UnifiedMobile Communicator

VeriSign or GeoTrust (CA) Certificate Self-signed (or CA) Certificate

ASA must run version 8.0(4) or later.8.2 or later recommended for built-inmobility proxy licensing

The Cisco Adaptive Security Appliance (ASA)

can be deployed in one of two ways.

ASA Deployment: ASA TLS Proxy and Firewall



84/114



Advantage

ASATLS Proxy

Option 2:ASA as TLS Proxy only(external firewalls used)

Enterprise

MPMP

UU

UCApplications

Internet

Mobile DataNetwork

(Data Channel)

MMP over

SSL

MMP overSSL

Cisco UnifiedMobile Communicator


DMZ

The Cisco Adaptive Security Appliance (ASA)

can be deployed in one of two ways.

ASA Deployment: ASA TLS Proxy Only

ASA must run version 8.0(4) or later.8.2 or later recommended for built-inmobility proxy licensing



85/114


ASA

Platform

Maximum UC/Mobility

Proxy Function Limit

Max. Number of CUMC/

Cisco Mobile ClientsASA 5505 24 24

ASA 5510 100 100

ASA 5520 1,000 1,000

ASA 5540 2,000 2,000

ASA 5550 3,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 clientsmay be less

Firmware version 8.2 recommended in order to leverage built-inmobility proxy licensing for Cisco Unified Mobile Communicatorsolution. Versions prior to 8.2 will require purchase of licensing.

* Requires firmware version 8.2

ASA Deployment: Scalability



86/114


Cisco Mobile 7 for Blackberry is dependent uponBlackberry Enterprise Server for the following:

Secure connectivity to CUMA in order to leverage back-end applicationservices (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 ConnectionService and MDS Integration Service required)

The following settings must be enabled in order to distribute clientsoftware and to support Cisco Mobile:

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 thefollowing set to Allow for Cisco Mobile :

Cross Application Communication Internal network Connections External network Connections Local Connection Phone Access Email

BES Deployment: Cisco Mobile 7 for Blackberry

User Data Event Injection Bluetooth Serial Profile Security Data

Blackberry Device Keystore Medium Security



87/114


Securing the data connection to the CUMA server is critical for securecommunication.

Cisco recommends CA-signed certificates on ASA or CUMA depending onclient for highest level of security.

Optional: Additional security can be implemented to secure the dataconnection between CUMA and back-end application servers


Advantage

DMZ

MPMP

UU

UC

Applications

MMPoverSSL

Cisco UnifiedMobile

Communicator/Cisco Mobile

Internet

Mobile DataNetwork(Data Channel)

BES(w./ MDS)

ASATLS Proxy

MMP overBES

Security Architecture: Certificate Considerations

VeriSign or GeoTrust Certificate Self-signed (or CA) Certificate

Self-signed certificate caveats: Results in warning on client on

each connection Self- signed certificate needs to be

uploaded to device to eliminatewarning.


Self-signed certificate caveats: On MDS server properties under

TLS/HTTPS, the Allow UntrustedTLS Connectionssetting must beset to 'True' if you plan to use a self-signed/untrusted certificate onCUMA.



88/114


Enforce specific handset hardware on a per userbasis, 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 beconfigured prior to provisioning of CUMC/Cisco Mobile client

Cisco Unified Mobility Advantage: Security



89/114


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 connectionattempt client will wipe configuration and all user data

Cisco Unified Mobility Advantage: Security (cont.)

CiscoUnified

MobilityAdvantage

Internet

Mobile DataNetworkX

ASATLS Proxy


90/114


Unified Mobility Integration




91/114



DNRemote Destination Profile



CUMC device this MobilityIdentity is associated to.

DN Cisco Unified Mobile Communicator

Mobility Identity


+

Cisco Unified Mobility Integration: Configuration

Mobile phone number of client device -must match exactly the mobile numberconfigured within Cisco Unified MobilityAdvantage


Remote Destination pickup/ Mobile Connect on/off


DN

Dual-Mode Device

Mobility Identity


+


92/114


Dial-via-Office: Call Flows and Deployment Considerations




93/114


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 betweenthe 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 )

The dial-via-office feature enables the Cisco Unified

Mobile Communicator/Cisco Mobile client to dial anoutgoing call through the enterprise

Dial-via-Office Feature



94/114


With Dial-via-OfficeReverse (DVO-R)Unified CM calls users

mobile number(configured mobility identity)


Internet


MobileDataNetwork

PSTNMobileVoiceNetwork

Mobile Data Connection

Mobile Voice Connection

Call Signaling

DVO-R call-back leg setup

Target call leg setup

CUMA extends SIPcall setup request to

Unified CM.

Once call leg isextended totarget/called number,Unified CM connectsthe two call legs(mobile call leg andtarget call leg) at the

PSTN gateway andcall is anchored.

Once call leg tomobile is setup,Unified CM extends

call to target/callednumber

2

4

5

Caller ID on call-back call leg is the EnterpriseFeature Access number as configured within UnifiedCM (Call Routing > Mobility Configuration).

Cisco Unified Mobile Communciator/Cisco Mobileclient auto-answers call-back call leg

Unified CM extendscall to mobile deviceover PSTN

Note:DVO-R requires Unified CM 7.0(2) or later

Dial-via-Office: Reverse

BES(w./ MDS)

CUMC signals call setuprequest over mobile dataconnection.

1

3

ASATLS Proxy



95/114


ASATLS Proxy


Internet


MobileDataNetwork

PSTN



Call Signaling

DVO-R call-back leg setup



Unified CM.

Once call leg is

extended totarget/called number,Unified CM connectsthe two call legs(alternate number callleg and target callleg) at the PSTNgateway.

Once call leg toalternate number issetup, Unified CMextends call totarget/called number

2

4

5

Unified CM calls user specified number

Alternate extension will not be auto-answered.

Dial-via-Office: Reverse Alternate Number

BES(w./ MDS)


1

Call-back call leg canbe sent to user-

directed alternatenumber (rather thanmobility identity)

NOTE: DVO-R alternate number calls are not anchored inthe enterprise gateway. Mid-call features and desk phone

pickup will not be possible with these types of calls.

MobileVoice

Network

3

Unified CM extendscall to user specifiednumber over PSTN.

Cisco Unified Mobile CommunicatorO


96/114


With Dial-via-OfficeForward (DVO-F) clientcalls into Unified CMsystem usingconfigured EnterpriseFeature Accessnumber.


Internet


MobileDataNetwork

PSTNMobileVoiceNetwork



Call Signaling

DVO-F call leg setup



Unified CM.

Once call leg isextended totarget/called number,Unified CM connectsthe two call legs(mobile call leg andtarget call leg) at the

PSTN gateway andcall is anchored.

Once call leg frommobile is setup,Unified CM extends

call to target/callednumber

2

5

6

Inbound caller ID must be available to the UnifiedCM used to identify inbound call from client.

Cisco Unified Mobile Communicator/Cisco Mobileclient automatically sets up call to Unified CMEnterprise Feature Access number.

Note:DVO-F requires Unified CM 7.1(3) or later

Dial-via-Office: Forward

BES(w./ MDS)


1

ASATLS Proxy

Unified CM sendscall setup signalingto mobile deviceover mobile dateconnection.

3

Mobile client dialsinto system usingnumber indicated in

signaling fromUnified CM. Caller IDmust be received byUnified CM and mustmatch configuredmobility identity

4

iPhone

Cisco Unified Mobile CommunicatorDi l i Offi DVO F D i C id i


97/114


Timer: At initiation of DVO-F call Unified CMsets 30 second timer.

Inbound call from Cisco Mobile device must bereceived before this timer expires or DVO-F call will

fail. Caller ID requirement: Unified CM correlates

caller ID of inbound call from Cisco Mobilewith SIP invite received over data channel. If

inbound caller ID is not received or does notmatch, DVO-F call will fail

Inbound caller ID must be received by Unified CM for DVO-F calls to succeed

CAUTION

!

Dial-via-Office: DVO-F Design Considerations

Cisco Unified Mobile CommunicatorDi l i Offi CUMC/Ci M bil Cli S i

Documents

Soluciones de Movilidad Corporativa Con Comunicaciones Unificadas