Mobile UC Design Session - Cisco

S Mobile UC

Mobile UC Design Session

© 2010 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1Mobile UC Design Session

UC SEVT, October 2010

S Mobile UC

Design Session

Surapong Niramoncherdchai

At the end of the session, the participants should be able to:

� Identify new products in the campus mobility space

� Explain new Unified Mobility features available with Unified Communications Manager 8.0 and 8.5

Session ObjectivesMobile UC Design Session



� Identify and understand dual-mode product portfolio and capabilities of the various offerings

� Discuss the current Cisco Unified Mobile Communicator offering and our transition to direct-connect clients.

� Describe the RIM Mobile Voice System (MVS) partner offering and the integration with Unified CM.

� Campus/Enterprise Mobility

� Unified Mobility with Unified CM

� Dual-Mode Phones and Clients

� Cisco Unified Mobile Communicator

Agenda




� RIM Mobile Voice System (MVS)

� The Future: Transitioning to Direct Connect

� Summary

Unified Mobility

Dual-Mode PhonesMobile Voice

Network

Enterprise

Campus/Single Site

DN: 51234

Extension MobilityHardware Moves WLAN Roaming

DN: 51234 Extension Mobility

Inside, Outside, and BetweenCisco Mobility Solutions Architecture



Mobile Voice

Network

Cisco Unified Mobile Communicator

PSTN

Mobile Voice/

Data Network

Network

Mobile Data Network

Bridging Enterprise and

Provider Mobility

Remote

Internet

Cisco Mobile

IP/WAN

PSTN

VPN IP Phone or Soft Client w./ PC VPNCisco Virtual Office

Mobility

Device Mobility

WLAN Roaming

DirectConnect

Campus/Enterprise Mobility



� New 802.11 a/b/g SCCP phone model based on 7925G design

� Product differences include:

� Certified as non-sparking (CSA Div 2, Class 1, ATEX Zone 2) for explosive environments.

� Enclosure change to comply with non-sparking requirements.

New

WLAN Phone: 7925G-EX

Cisco Unified Wireless IP Phone



sparking requirements.

� New color scheme to differentiate from 7925G.

� Increased IP rating from IP54 to IP64 (IEC 60529).

� Increased operating temperature range (-10 +50 C)

� Ideal for demanding environments such as energy, utilities, and manufacturing

� Hermetically sealed

Provides protection against dust, spark, and liquid splashes.

� IP64 rated

–Dust tight:

No ingress of dust; Complete protection

Dust Test: Unit subjected to talcum dust for 8 hrs.Unit fully functional after the test.

New

7925G-EX Enclosure ProtectionCisco Unified Wireless IP Phone



No ingress of dust; Complete protection against contact

–Splashing water protected:

Water splashing against the enclosure from any direction shall have no harmful effect

� Competitive comparison

–Polycom/Spectralink – IP53

–Ascom – IP40

Shower Test: Unit subjected tocontinuous water flow for 10 mins.Unit fully functional after the test.

� First digit indicates level of protection that the enclosure provides against access to hazardous parts and the ingress of solid foreign objects

Level Object size protected against Effective against

0 - No protection against contact and ingress of objects

1 >40 mm Any large surface of the body, such as the back of a hand, but no protection against deliberate contact with a body part

2 >12.5 mm Fingers or similar objects

3 >2.5 mm Tools, thick wires, etc.

4 >1 mm Most wires, screws, etc.

7925G-EX rating:

IP64

For Your Reference

Int'l Standard IEC 60529 IP Codes: 7925G-EXCisco Unified Wireless IP Phone



� Second digit indicates level of protection of the equipment inside the enclosure against harmful ingress of water

4 >1 mm Most wires, screws, etc.

5 Dust protected Ingress of dust is not entirely prevented, but it must not enter in sufficient qty to interfere with the satisfactory operation of the equipment; Complete protection against contact

6 Dust tight No ingress of dust; Complete protection against contact

Level Protected against Details

0 Not protected -

1 Dripping water Dripping water (vertically falling drops) shall have no harmful effect

2 Dripping water when tilted up to 15%

Vertically dripping water shall have no harmful effect when the enclosure is tilted at an angle up to 15% from its normal position

3 Spraying water Water falling as a spray at any angle up to 60% from the vertical shall have no harmful effect

4 Splashing water Water splashing against the enclosure from any direction shall have no harmful effect

5 Water jets Water projected by a nozzle against enclosure from any direction shall have no harmful effects

6 Powerful water jets Water projected in powerful jets against enclosure from any direction shall have no harmful effects

� New 802.11 a/b/g SCCP phone model based on 7925G form factor:

� Same form factor, battery/accessories, and IP rating as 7925G (IP54)

� Addition of 2D Bar Code Scanner*

1D

TOP VIEW

2D

ComingSoon

Expected FCS: Dec. (Q4CY10)Expected FCS: Dec. (Q4CY10)Expected FCS: Dec. (Q4CY10)WLAN Phone: 7926GCisco Unified Wireless IP Phone



1D

�Scanner supports both basic and extended bar code types. (See next slide for more info).

� Image decoding integrated into hardware

� Java Midlet client application integrates scan engine with back end systems in order to do lookups and to display pricing, location, inventory information, etc.

2D

* Scanner leveraged with Java MIDP support –requires version 1.4(1) of firmware.

� Bar Code Symbology Group

This device level Unified CM configuration field specifies the symbology the scanner will use to scan bar codes. Select either basic or extended symbology from the dropdown menu depending on barcode types being used.

� Scanner Commands

This device level Unified CM configuration field allows for further customization of the scanner features. Below are

7926G: Bar Code Symbology Group & Scanner Commands

For Your Reference Cisco Unified Wireless IP Phone



further customization of the scanner features. Below are some examples of commands that can be used:

•A simple scanner command to set UPC->EAN13 conversion:

� 414b5a01 enables UPC->EAN13 conversion

When enabled, a ‘0’ will be prepended to the scanned UPC barcode (e.g. “017229123496” will show as “0017229123496”)

� 414b5a00 disables conversion

•Scanner command to set scanner trigger time out

� 4170800005 sets scanner trigger time out at 5 seconds (i.e. the red LED will turn off after 5 seconds if no bar code is scanned)

Please refer to the Java MIDP SDK for additional information on scanner commands.

SDK, firmware/COP files, and MIDlets info including developers guide available here:

http://developer.cisco.com/web/jmapi/docs

ComingSoon

Expected availability: Nov. 2010Expected availability: Nov. 2010Expected availability: Nov. 2010

Phone firmware version 1.4(1) provides the following features/functions:

�Java MIDP support for 7925G/7925G-EX/7926G devices*

�2D Barcode Scanner for 7926G – w./ symbology group & scanner commands

�Administrator control of Bluetooth

�Bluetooth volume control from handset

�XSI Keypad unlock for remote keypad locking

�Increase font size option

†

Firmware 1.4(1)Cisco Unified Wireless IP Phone




�Minimum ring volume – Ring volume access even when phone configuration menu is

administratively locked and admin specified minimum ring volume

�Longer caller ID field

�Digit confirmation – Digits entered after connection are shown

�Increased local phone book capacity (from 100 to 200 entries)

�Bluetooth speakerphone enabled desktop charger* support

* Not supported with 7921G

English only at FCS†

ComingSoon

Expected availability: Nov. 2010Expected availability: Nov. 2010Expected availability: Nov. 2010

Phone firmware version 1.4(1) provides the following features/functions:

�Java MIDP support for 7925G/7925G-EX/7926G devices*

�2D Barcode Scanner for 7926G – w./ symbology group & scanner commands

�Administrator control of Bluetooth

�Bluetooth volume control from handset

�XSI Keypad unlock for remote keypad locking


†

Check out the Java MIDlet API page on Cisco Developer Network : http://developer.cisco.com/web/jmapi/home

Firmware 1.4(1)Cisco Unified Wireless IP Phone




�Minimum ring volume – Ring volume access even when phone configuration menu is

administratively locked and admin specified minimum ring volume

�Longer caller ID field

�Digit confirmation – Digits entered after connection are shown

�Increased local phone book capacity (from 100 to 200 entries)

�Bluetooth speakerphone enabled desktop charger* support

* Not supported with 7921G

English only at FCS†

Provides resources and a forum for Java development with 1.4(1) firmware on Cisco wireless IP phones.

Durability: Rugged phones with high drop specifications

�5 ft (1.5 m) drop to concrete without carrying case

�Designed to meet military’s

Durability: 7925G, 7925G-EX, 7926GCisco Unified Wireless IP Phone



�Designed to meet military’s toughest standards:

Compliant to MIL-STD-810F, Method 516.5, Procedure I

Resistance to shock – Material is required to function during shock and to survive without damage to shocks representative of those that may be encountered during operational service

Cisco Unified Mobility



WAN

PSTN

Unified Mobility User

Headquarters

Branch/ Regional OfficeOverview




PSTN

Unified Mobility

User

Unified Mobility provides a mechanism for associating a user’s enterprise desk phone (or enterprise DN) to their mobile device(s).

Unified Mobility includes the following set of features:

– Mobile Connect (aka SNR)

– Mobile Voice Access (MVA)

– Enterprise Feature Access (EFA)

– Desk Phone and Remote Destination pickup

– Single Enterprise Voicemail Box

– Mid-call Supplementary Services

– Time of Day Access Lists

Unified Mobility call flows and functionality are supported over service provider SIP trunk PSTN connections with the following caveats:

� Cisco Unified Border Element is required to terminate Unified CM

Unified Mobility User

PSTN

IP

SIP Trunks

Cisco Unified Border Element

VoIP PSTN Connectivity




� 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 Unified CM for Mobile Voice Access (MVA). Transcoders needed if inbound MVA call leg is G.729.

� Requires Unified CM 6.1(2) and later or 7.1(2) and later.

The Intelligent Session Control feature provides the following functionality:

� Enables enterprise call anchoring for internally dialed direct calls to remote destination or mobility identity numbers.

� Allows desk phone pickup and mid-call features (enterprise call anchoring)

New

Unified CM 8.0: Intelligent Session ControlCisco Unified Mobility



(enterprise call anchoring)

� Partial (v. Complete) digit matching needed if PSTN steering digits required when dialing internally.

� Disabled by default - Reroute Remote Destination Calls to Enterprise Number service parameter (True/False) should be set to ‘True’ to enable.

Note: Intelligent Session Control feature does not ring desk phone

Enterprise

PSTNGateway

Mobile Connect

Inbound Calls Answeredat Desk Phone or at

Remote Destination Phone

Mid-CallFeatures

Mobile Voice Access

All calls made or received on behalf of user’s RD Are automatically anchored in the enterprise gateway

New

Intelligent Session Control: Enterprise Call Anchoring




Cisco UnifiedCM Cluster

PSTN

Enterprise Feature Access

(Two-Stage Dialing)Outbound Calls

Generated from Remote Destination Phone

Inbound Calls fromRemote Destination

Incoming Calls from Configured Remote Destination Phones

Mobile Voice Access

Outbound Calls Generated from

Remote Destination Phone

Internally Originated DirectCalls to Remote Destination *

Internally Originated Direct Calls to Remote Destination Numbers

* Intelligent Session Control feature – requires minimum

of Unified CM 8.0.

Desk PhonePickup

The Session Handoff (*74) mid-call feature provides additional desk phone pickup method:

� When invoked desk phone flashes/rings and user must answer.

� Improved pickup experience over existing desk phone pickup methods:

� Remote destination hang-up and desk phone resume

New

Unified CM 8.0: Session Handoff (*74)Cisco Unified Mobility



� Remote destination hang-up and desk phone resume

� Remote destination mid-call hold (*81) and desk phone resume

� Session Handoff user experience:

� Original media path and conversation maintained until answer at desk phone

� No music on hold

� Allows mid-call desk phone registration

� Boot up of PC running IP Communicator

� Extension Mobility login

� Desk phone reload

PSTN

Unified MobilityUser

The Mobile Toll Bypass Optimization feature provides improved functionality to mobile client Dial-via-Office operations

Two aspects of this feature:

1. Mobility Profile

� Per user or per user group profile configuration containing: DVO

ComingSoon

8.5 release: November 30th *8.5 release: November 30th *8.5 release: November 30th *

Unified CM 8.5: Mobile Toll Bypass OptimizationCisco Unified Mobility



� Per user or per user group profile configuration containing: DVO direction (F or R), DVO-F Service Access Number and EFA Number pair, DVO-R Caller ID.

� Applied to user's Mobility Identity (CUMC, Dual-mode, and direct-connect clients)

2. Multiple Enterprise Feature Access Numbers

� Configuration of multiple system DIDs for Enterprise Feature Access (DVO and 2-stage dialing access numbers)

� Enables configuration of per geographic location local number

* Release date subject to changeDeveloped for new direct-connect clients, but also applicable to CUMC

ComingSoon

Multiple Enterprise Feature Access Numbers

Per User/Group SJ Users profile

Unified CM 8.5: Mobile Toll Bypass Optimization (cont.)




Per User/Group Mobility Profiles

RTP Users profile

Association of Mobility Profile to Mobility Identity

ComingSoon

In the event that a DVO-F call fails due to network connectivity issue, Unified CM uses cached dialed/target number* to reconnect call on redial

� User experience prior to feature: After DVO-F call setup and

subsequent network failure, redial by user would fail

The Dial-via-Office Forward (DVO-F) Redial feature provides improved user experience to mobile client DVO-F operations

Developed for new direct-connect clients, but also applicable to CUMCUnified CM 8.5: DVO-F Redial




subsequent network failure, redial by user would fail

x Redial to DVO-F Service Access Number/Enterprise Feature Access Number FAILS because Unified CM does not know where to route the call

� User experience after feature: After DVO-F call setup and

subsequent network failure, redial by user succeeds

� Redial to DVO-F Service Access Number/Enterprise Feature Access Number SUCCEEDS because Unified CM caches previously dialed number

* Amount of time Unified CM caches last DVO-F dialed number is based on Redial Await Timer service

parameter (default is 3 minutes – 180 seconds).

ComingSoon

� Mobile Client Support without CUMA

� Improvements within Unified CM to accommodate forthcoming direct connect mobile client registration and support existing mobility features like dial-via-office without the need for a CUMA server.

� Mobile Connect Status and Update

Requires forthcoming

direct-connect

The following additional mobility features will be included in Unified CM 8.5

Unified CM 8.5: Additional Mobility FeaturesCisco Unified Mobility



� Mobile Connect Status and Update

� Enhancement of SIP messaging to enable Mobile Connect on/off updates as well as to provide status indication of current state. (Previously this was only possible with CUMC clients via AXL/SOAP interaction between CUMA and Unified CM)

� RIM Send Call to Mobile

� Provides the ability for RIM MVS users to move call on desk phone to BlackBerry mobile phone using Mobility Softkey and "Send call to mobile" feature.

direct-connect clients

� Capacity/Scalability

� Maximum of 15,000 remote destinations (e.g. mobile numbers) per Unified CM cluster (w./ MCS-7845 or UC on UCS equivalent).

� PSTN utilization will increase with this solution and

The following design-related information should be considered when deploying Unified Mobility:

Design ConsiderationsCisco Unified Mobility



� PSTN utilization will increase with this solution and additional gateway/CUBE capacity should be added.

� Redundancy

� All features/functions natively redundant within Unified CM with exception of:

� Mobile Voice Access (Publisher dependent)

� Remote site connectivity failures (users at site in SRST-mode will have limited/reduced functionality)

X

XX

� Caller ID

� Inbound caller ID required for automatic call anchoring and Enterprise Feature Access (2-stage dialing and mid-call transfer/conference/directed call park)

� Outbound caller ID for Mobile Connect calls will be original calling party number, however, PSTN provider may restrict to trunk-specific DID (RDNIS/SIP diversion header may resolve)

� PSTN Connectivity

Caller ID

Design Considerations (cont.)Cisco Unified Mobility



� PSTN Connectivity

� TDM: Mobile Connect requires PRI T1/E1, all other features/functions supported with various TDM connection types.

� IP PSTN: Requires Cisco Unified Border Element as demarcation point and mid-call features/DTMF not supported.

� Call Routing

� Outbound calls made on behalf of remote destination/mobile phone leverages RDP line + device Calling Search Space concatenation for call routing (MVA and EFA 2-stage dialed calls)

� Inbound calls forwarded to remote destination/mobile phone leverages RDP Rerouting Calling Search Space for call routing (Mobile Connect/SNR)

PSTN

Internet

Dual-Mode Phones and Clients



Dual-mode phones provide the ability to leverage enterprise IP telephony infrastructure (via WLAN connectivity) for making and receiving calls while inside the enterprise. When outside the enterprise the dual-mode device falls back to the mobile voice network for

Enterprise

Dual-mode phones and clients provide the following set of features:

– SCCP or SIP client registration to Unified CM

– Voice over WLAN with 802.11 b/g connectivity

– Access to enterprise supplementary features: hold, resume, transfer, conference, park

– Manual or Automatic handoff: Ability to move in and out of the enterprise while on active call

– Mobile Connect/SNR when integrated with Cisco Unified Mobility

– Device Mobility (Unified CM feature supported with versions 4.2, 6.0 and later)

OverviewDual-Mode Phones and Clients



back to the mobile voice network for voice services.

PSTN

WLANAPWLAN

(802.11 b/g)

Mobile VoiceNetwork

Enterprise

Dual-modeMobile Phone

versions 4.2, 6.0 and later)

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]

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)

Nokia Call Connect 2.x

Nokia E72

Devices & Clients: Nokia Call ConnectDual-Mode Phones and Clients



Additional features and services:

� Supplementary services (hold, resume, transfer, conference, park, etc.)

� 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*

Automatic* (and manual) handoff:

� Hand-in (Cellular to WLAN)

� Hand-out (WLAN to cellular)

* Supported only with 3.2 versions of handsets

Nokia E66

Nokia E71

Nokia E75

Nokia E61i

Cisco Mobile 8.0New

Handset support:

� iPhone 3G or 3GS

� Firmware 3.0.1 or later (including iOS 4)

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)

Devices & Clients: Cisco Mobile 8.0Dual-Mode Phones and Clients



Additional features and services:

� Supplementary services (hold, resume, transfer, conference, park, etc.)

� 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.

� Handoff number method (client calls system)

Moving calls from enterprise WLAN to cellular network and vice-versa is generally referred to as Handoff

PSTNGateway

AP

PSTNMobile Voice

Network

Hand-out: Moving calls from enterprise WLAN to cellular network

Handoff Terminology: Hand-Out v. Hand-InDual-Mode Phones and Clients



Enterprise WLANCellular/Mobile Voice

PSTNGateway

PSTNMobile Voice

Network

Cellular/Mobile Voice

Hand-in: Moving calls from cellular network to enterprise WLAN

Enterprise WLAN

AP

� Method used depends on Transfer to Mobile Network setting on

� Cisco Mobile 8 for iPhone supports two hand-out methods:

1. Mobility Softkey method: Handoff indication signaled to Unified CM over WLAN. System generates call TO dual-mode phone’s mobile voice network interface/number. (Same operation as "Send Call to Mobile Phone"/Remote Destination

pickup)

2. Handoff DN method: Device generates call FROM mobile voice network interface to Unified CM handoff number.

Cisco Mobile 8.0: Handoff ConsiderationsDual-Mode Phones and Clients



� Method used depends on Transfer to Mobile Network setting on Cisco Dual-Mode for iPhone device configuration page.

� Handoff number configured in Unified CM

� Unified CM 8.0 and earlier: Call Routing > Mobility Configuration

� Unified CM 8.5: Call Routing > Mobility > Handoff Configuration

� Hand-in (cellular to WLAN) is not supported with Cisco Mobile 8.0

� Call Park on hand-out failure

� 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.

EnterpriseCisco UnifiedCM Cluster

PSTNGateway

PSTNMobile Voice

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

1An existing call between the iPhone dual-mode device on the enterprise

Unified CM generates a call to the dual-mode user’s configured mobility identity number via the enterprise PSTN gateway

3

5

Cisco Mobile 8.0: Hand-Out – Mobility Softkey method




VoiceNetwork

AP

SamePhone

MobileVoice

WLAN

device on the enterprise WLAN and a phone on the PSTN.

User pushes ‘Use Mobile Network’ softkey from in-call menu and iPhone dual-mode client indicates to Unified CM its intention to hand-out.

2

User is now able to move out of the enterprise and away from enterprise WLAN coverage.

4

On answer, Unified CM redirects original RTP stream that was traversing the WLAN to the enterprise PSTN gateway resulting in enterprise call anchoring.

Handoff indication signaled to Unified CM over WLAN which in turn generates call to dual-mode phone’s mobile voice network interface. Once answered call media is redirected from WLAN to enterprise PSTN gateway.

Initial voice media path

Handoff background call leg

Final voice media path


PSTNGateway

PSTNMobile Voice


1An existing call between the iPhone dual-mode device on the enterprise

iPhone dual-mode client automatically makes call via mobile voice network interface to Handoff Number configured within Unified CM.

3

Unified CM verifies caller

5

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)

Cisco Mobile 8.0: Hand-Out – Handoff DN methodDual-Mode Phones and Clients



VoiceNetwork

AP

SamePhone

MobileVoice

WLAN

Hand-off indication signaled to Unified CM over WLAN which in turn generates call from dual-mode phone’s mobile voice network interface to handoff number. Once answered call media is redirected from WLAN to enterprise PSTN gateway.

device on the enterprise WLAN and a phone on the PSTN.

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.




User pushes ‘Use Mobile Network’ softkey from in-call menu and iPhone dual-mode client indicates to Unified CM its intention to hand-out.

2


PSTNGateway

PSTNMobile Voice


1

An existing call between the Nokia dual-mode device on the enterprise WLAN and a phone on

4

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

3

Unified CM relies on inbound caller ID to identify the call being handed off – Ensure inbound caller ID is presented to Unified CM

Nokia Call Connect 2.x: Hand-Out (WLAN to Cellular)




VoiceNetwork

APMobileVoice

SamePhone

WLAN2

The Nokia dual-mode user begins to leave the enterprise.

1WLAN and a phone on the PSTN.

Once background call received by Unified CM, calling number is compared against system dual-mode mobility identities and provided a match is found, media stream on WLAN is redirected to the PSTN gateway

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.




Hand-out can also be invoked manually by the user using the in-call menu “Switch to Cellular” or “Switch to GSM” options.

� Manual invocation of handoff stops operation of auto-handoff for duration of call.

� This option must be used for devices that don’t support automatic-handoff.

Hand-out can also be invoked manually by the user using the in-call menu “Switch to Cellular” or “Switch to GSM” options.

� Manual invocation of handoff stops operation of auto-handoff for duration of call.

� This option must be used for devices that don’t support automatic-handoff.


PSTNGateway

PSTNMobile Voice


Once background call received by Unified CM, calling number is compared against system dual-mode mobility identities and provided a match is found, RTP

1

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

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



VoiceNetwork

APMobileVoice

SamePhone




WLAN

The Nokia dual-mode user moves into the enterprise and the device associates in the background to WLAN infrastructure and registers to Unified CM

provided a match is found, RTP stream on PSTN gateway is redirected to the WLAN

An existing call between the Nokia dual-mode device on the mobile voice network and a phone on the PSTN.

2

3

4

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.

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.

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.

The desk phone integration feature of Cisco Mobile senses active call at desk phone via CTI and provides ability to move active or held call from desk phone to mobile.

Cisco Unified

Cisco Mobile prompts user to transfer/resume the call on the mobile

Cisco Mobile also prompts user at client launch to transfer active desk phone call to mobile.

Requires call park configuration within Unified CM as move of call is facilitated via call park

Dual-Mode Phones and ClientsCisco Mobile 8.0: Desk Phone Integration



WLAN(802.11)

1

Cisco UnifiedCM Cluster

Shared Line

User places call on hold at desk phone

mobileto mobile.

3

Active call can be moved from mobile to desk phone by simply placing VoIP call on hold at mobile and resuming at desk phone.

2

While VPN connection from dual-mode device/client to

enterprise is supported, Cisco cannot guarantee voice quality when dual-mode devices are connected to the enterprise via public or private WiFi hotspots or over 3G.

� Cisco Mobile 8.0 (iPhone) supports native IPSec VPN client as well as new AnyConnect client for VPN on-demand access for connectivity back to enterprise (Cisco Mobile 8 client �� VPN ��

Dual-Mode Phones and ClientsRemote Connectivity



WLAN

connectivity back to enterprise (Cisco Mobile 8 client �� VPN ��Provider data connection (3G) / WLAN AP (WiFi) �� Internet)

� Nokia CC supports native IPSec VPN client for VPN on-demand access for connectivity back to enterprise (Nokia CC client �� VPN �� Provider data connection (3G) / WLAN AP �� Internet)

DMZ

Internet

Mobile Data Network

PSTNMobile Voice Network

Nokia CC Cisco Mobile 8.0

VPN

� Basic VoWLAN network design requirements:

� Cell radius or power-level boundary of approximately -67 dBm (or less) is recommended in order to minimizes packet loss.

� Same channel cell separation of 19 dBm is recommended to minimize co-channel interference

� Channel cell overlap (on non-adjacent

Dual-Mode Phones and ClientsVoice over WLAN Design Considerations



� Channel cell overlap (on non-adjacent channels) should be 15-20% to ensure seamless roaming between APs.

� Site-survey required prior to adding VoWLAN devices. Each VoWLAN device type should be tested

� Bluetooth headsets are not recommended with dual-mode handsets due to potential interference on the 2.4 GHz band.

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/Mobility/vowlan/41dg/vowlan41dg-book.html

Conference Room

Conference Room

66

1111

11

11

WLAN Roaming with Cisco Mobile 8.0:

�iPhone dual-mode clients should only roam at layer 2

Roaming at layer 3 will result in dropped calls due to change in IP address.

�iPhone dual-mode client should only roam with same SSID

Roaming between APs is much slower if SSIDs are different.

Dual-Mode Phones and ClientsVoWLAN Design: Cisco Mobile 8/Nokia CC



Conference Room

Conference Room

66 11

WLAN Roaming with Nokia Call Connect 2.x:

�WLAN HO Threshold setting (under Voice Continuity Configuration (VCC)) should be left at default setting (73

for Nokia CC 2.1) unless experiencing: 1) delayed automatic hand-out, 2) slow AP to AP roaming, or 3) poor voice quality on WLAN.

Lowering will engage automatic hand-out (WLAN to cellular) more quickly, but will also impact AP to AP roaming resulting in faster AP to AP roaming

the call

different.

�iPhone dual-mode client should only be deployed on WLAN infrastructure that broadcasts SSID

If SSID is not broadcast by AP, user may be prompted by iPhone to join other WLAN networks which will interrupt the call

1. User Effort: Users checks for Unified CM registration icon.

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

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

Nokia CC 2.x

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

Dual-Mode Phones and ClientsDesign Considerations: Dial Plan



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.

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

Recommended

Caller ID – For dual-mode deployments, work with 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).

Caller IDDual-Mode Phones and ClientsDesign Considerations: Caller ID



� 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 to ensure caller ID is sent to provider network

Outbound Caller ID

� All VoIP calls and 2-stage dialed calls will send user’’’’s enterprise number rather than the user’’’’s mobile number.

� Mobile Connect considerations (original caller ID, RDNIS/SIP Diversion header).

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:

PSTN

WLAN

Dual-Mode Phones and ClientsDesign Considerations: Scalability



� 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.

�Unified Mobility remote destination/mobility identity

capacity – Maximum of 15,000 total

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

� 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

Dual-Mode Phones and ClientsDesign Considerations: Redundancy



� 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

Cisco Mobile 8.1 (maintenance release) – Dec. 2010*� Support for backgrounding of application

� Requires minimum of 4.0 firmware

� Support for iPhone 4G & 3GS (drop support for 3G)

� Support for audio over Bluetooth headset

ComingSoonDual-Mode Phones and Clients

Cisco Mobile 8.1 for iPhone


UC SEVT, October 2010* All information subject to change

PROBLEM: iPhone iOS suspends background applications and only

wakes every 10 minutes if no activity. This causes registration issues with Unified CM which disconnects any device that takes longer than 2 minutes to respond.

SOLUTION: Use SIP profile to adjust Unified CM behavior.

1. Create new SIP profile and configure Timer Keep Alive Expires setting to 660 (seconds).

2. Apply this SIP profile to all Dual-Mode for iPhone devices

This ensures that device stays registered longer than the iOS suspension interval of 10 minutes so that incoming calls are handled.

Cisco Unified Mobile Communicator



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 CM

PSTNCisco Unified Mobile

Communicator/ Cisco Mobile 7.x

Mobile Voice Network

Cisco Unified Mobile Communicator includes the following set of features:

– Enterprise directory lookups and single sign-on

– Secure text messaging between CUMC clients*

– Presence integration*

– Enterprise visual voicemail and MWI

– Conference notifications and click-to-join (Call

Me)*

– Desk phone call log integration

– Dial-via-office*

– Mobile Connect (via Unified Mobility *

Cisco Unified Mobile CommunicatorOverview



Cisco Adaptive Security Appliance (ASA)

Cisco MeetingPlace

Cisco Unity/Unity

Connection

Microsoft Active Directory

Cisco Unified Presence

DMZ

UU

MPMPMicrosoft Exchange

PSTN Gateway

Enterprise and UCApplications

iPhoneiPhone

Internet

Mobile Data Network

(Data Channel)

BES(w./ MDS)

Cisco Unified Mobility Advantage

MMPover SSL

MMPover SSL

MMPover BES

MMPover BES

– Mobile Connect (via Unified Mobility integration)

* Not supported on all clients

Voice

Data

Example devicesiPhoneiPhone Cisco Mobile 7 (CUMC client) supported on

iPhone 3G or 3GS handsets meeting the following criteria:�Firmware version 3.0.1 or later�iTunes 8.2 or later

9700 Bold

Cisco Mobile 7.1 (CUMC client) supported on Blackberry handsets meeting the following criteria:�BlackBerry OS version 4.3 or higher�Non-touch screen devices only�Enterprise activated

9000 Bold 9600 Tour8300 Curve 8900 Curve8200 Flip

Example devices

Cisco Unified Mobile CommunicatorHandset Support



E61i E71E51 N95 N96

3G or 3GS�iTunes 8.2 or later

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

Protégé G710

SamsungBlackjack II

HTC S620 Motorola Q9H

Samsung ACE

Example devices

Cisco Unified Mobile Communicator 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

All handsets require the following:� Installed 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

Example devicesiPhoneiPhone Cisco Mobile 7 (CUMC client) supported on

iPhone 3G or 3GS handsets meeting the following criteria:�Firmware version 3.0.1 or later�iTunes 8.2 or later

9700 Bold

Cisco Mobile 7.1 (CUMC client) supported on Blackberry handsets meeting the following criteria:�BlackBerry OS version 4.3 or higher�Non-touch screen devices only�Enterprise activated

9000 Bold 9600 Tour8300 Curve 8900 Curve8200 Flip

Example devices

Cisco Unified Mobile CommunicatorHandset Support

For a complete list of supported phones and required hardware and software, please see the CUMC/CUMA Compatibility Matrix:



E61i E71E51 N95 N96

3G or 3GS�iTunes 8.2 or later

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

Protégé G710

SamsungBlackjack II

HTC S620 Motorola Q9H

Samsung ACE

Example devices

Cisco Unified Mobile Communicator 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

All handsets require the following:� Installed 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

atibility_Matrix.html

and software, please see the CUMC/CUMA Compatibility Matrix:

http://www.cisco.com/en/US/docs/voice_ip_comm/cuma/CUMA_CUMC_Compatibility_Matrix.html

Enterprise Directory Lookup and single sign-on ��

Enterprise Desk Phone Call Log Integration ��

IM/Text Messaging ��

iPhoneiPhone

Cisco Unified Mobile CommunicatorMobile OS Feature Summary



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) † ��

† Via integration with Unified Mobility* Microsoft Exchange required

What does this mean for Cisco Unified Mobile Communicator deployments?

�All existing 1024-bit keyed certificates will continue to be supported and

Non-BlackBerry CUMC deployment w./ cert on ASA

Certificate Authorities are in the process of migrating to 2048-bit keyed certificates based on U.S. National Institute of Standard & Technology (NIST) mandate that Certificate Authorities issue SSL certificates with minimum bit length of 2048 by 2013.

Cisco Unified Mobile CommunicatorSecurity Architecture: Certificate Considerations (cont.)



�All existing 1024-bit keyed certificates will continue to be supported and are backward compatible with new 2048-bit key infrastructures

�For new non-BlackBerry deployments of CUMC: ASA running firmware 8.2 and later supports 2048-bit keyed Certificate Signing Requests (CSRs).

�For new deployments with BES integration to CUMA (required for all BlackBerry client deployments): Because CUMA supports only 1024-bit keyed CSRs SSL certificate purchases are only possible for certificates that expire by 2013.

� GeoTrust : Only 1 and 2 year certificates can be purchased with 1024-bit keyed CSRs

� VeriSign: 3 year certificates can be purchased with 1024-bit keyed CSRs if prior to Dec. 31st (or 2 years or less beyond that).

BES

Blackberry CUMC deployment w./ cert on CUMA

Existing CUMC/Cisco Mobile 7.x clients and CUMA 7.1(3) server are able to leverage new Unified CM 8.5 Toll Bypass Optimization feature.

2

DVO-F: Client automatically dials DID number received from

Once call received (DVO-F) or answered (DVO-R) Unified CM sets up call to dialed/target number Call anchored in

enterprise gateway

ComingSoon

No impact to CUMC behavior

Cisco Unified Mobile CommunicatorDial-via-Office: Mobile Toll Bypass Optimization



Cisco Unified Mobility AdvantageInternet

Cisco Unified CM 8.5

MobileDataNetwork

PSTNMobileVoiceNetwork

Mobile Data Connection

Mobile Voice Connection

Call Signaling

DVO-F call leg setup

DVO-R call-back leg setup

Target call leg setupASA

1

CUMC client signals call setup request to dialed/target number over secure mobile data connection.

Unified CM checks user's mobility profile to determine DID number to send for DVO-F or number to use for caller ID for DVO-R

3A

3B

received from CUMA/Unified CM

4

5

DVO-F: Unified CM sends appropriate DVO-F DID (EFA/SA number) to client via CUMA .

6

enterprise gateway

DVO-R: Unified CM sets up call to mobility identity with appropriate caller ID

Existing CUMC/Cisco Mobile 7.x clients and CUMA 7.1(3)

server are able to leverage new Unified CM 8.5 DVO-F Redial

feature.

Client automatically dials number received from

Once call from client received and caller ID match is successful Unified CM sets up call to dialed/target number

Network failure results in call failure

ComingSoon

408 555 1234

San Jose user's Mobility ProfileDVO-F EFA Number: 444 1000DVO-F Service Access Number: 408 444 1000

Assuming caller ID match is again successful Unified CM sets up new call to last dialed

number*

Cisco Unified Mobile CommunicatorDial-via-Office: DVO-F Redial



Cisco Unified Mobility AdvantageInternet

Cisco Unified CM 8.5

MobileDataNetwork

PSTNMobileVoiceNetwork

Mobile Data Connection

Mobile Voice Connection

Call Signaling

DVO-F call leg setup

Target call leg setupASA

1User dials 408 555 1234 and CUMC client signals call setup request to dialed number over secure mobile data connection.

2

Unified CM caches dialed number (408 555 1234) and starts Redial Await Timer.

3

4

received from CUMA/Unified CM (408 444 1000)

65

Unified CM sends SJ Service Access number (408 444 1000) to client via CUMA .

DVO-F Service Access Number: 408 444 1000

San Jose Mobile user

X7

User presses redialgenerating call back to Service Access number (408 555 1000)

8

* If Redial Await Timer

has not expired

The Cisco Unified Mobile Communicator (CUMC) client can be run co-resident with Nokia CC dual-mode clients

+

� Client awareness: CUMC will not invoke dial-via-office (DVO) while Nokia CC is registered to Unified CM. DVO only available when Nokia is outside the enterprise.

� Unified CM Configuration: No configuration of CUMC device. Instead ““““Enable Cisco Unified Mobile Communicator”””” on Nokia S60 device.

� Mobility identity associated to Nokia CC device sufficient for

Cisco Unified Mobile CommunicatorInteroperation w./ Nokia Call Connect Dual-Mode



Nokia CC CUMC 7

� Mobility identity associated to Nokia CC device sufficient for

both Mobile Connect/SNR and DVO.

The CUMC/Cisco Mobile 7 client can be installed co-resident with

Cisco Mobile 8.0 dual-mode client in Unified CM 7.1(5) and 8.5*

environments.

+

� Cisco Mobile 7 (CUMC) Dial-via-office (DVO) is compatible with Cisco Mobile 8.0. Both clients can be installed, but cannot run simultaneously due to multitasking limitation.

� If both clients are used, directory lookups and visual voicemail should be done within Cisco Mobile 7 (CUMC) as user experience is superior.

� Mobility identity associated to Cisco Dual Mode for iPhone

Cisco Unified Mobile CommunicatorInteroperation w./ Cisco Mobile 8.0 Dual-Mode



Cisco Mobile 8.0 Cisco Mobile 7 (CUMC)

device sufficient for both Mobile Connect/SNR and DVO.

NOTE: With Unified CM versions 7.1(3) and 8.0(x) Cisco Mobile 7 (CUMC) DVO and Cisco Mobile 8 dual-mode are not compatible. "Enable Cisco Unified Mobile Communicator" option NOT available. Clients can still be co-resident in order for user to leverage CUMC for other features (but CUMC device not configured)

* Not yet released

The following design-related information should be considered when deploying Cisco Unified Mobile Communicator:

Cisco Unified Mobile CommunicatorDesign Considerations



Internet

XX

MobileDataX

� Caller ID

� Inbound caller ID required for Dial-via-Office Forward (DVO-F)

� Data Channel Bandwidth Utilization

� Unlimited data plan highly recommended

� Highly variable based on end-user usage patterns.

Caller ID

Cisco Unified Mobile CommunicatorDesign Considerations (cont.)



� Per user average monthly bandwidth (w./out visual voicemail) is 5.6 MBytes.

� If bandwidth an issue consider the following:

� Conduct testing within deployment to determine average bandwidth utilization for common operations.

� Start with conservative per user per month average and then adjust as utilization data becomes available.

� Consider reducing number of features enabled for users in order to minimize bandwidth utilization (e.g. only enable DVO and presence services, but not call logs, conferencing, or visual voicemail)

� Roaming across country boundaries will result in roaming data charges – Consider SIM swapping or multiple mobile devices

Internet

Mobile Data Network

RIM Mobile Voice System (MVS) solution enables BlackBerry mobile users to utilize secure enterprise connectivity to leverage enterprise telephony infrastructure for making and receiving calls using the MVS client which communicates with the MVS server inside the enterprise (client-server architecture)


RIM Mobile Voice

System (MVS)

RIM Mobile Voice SystemArchitecture



Cisco Unified CM

PSTN Gateway

Internet

Mobile Data Network

(Data Channel)

RIM BlackberryEnterprise Server

(BES)

RIM Mobile Voice System Server

(MVS)

WLAN(802.11)

Voice

Data

VoWLAN

System (MVS) Client

MVS 5 required for dual-mode functionality

SIP

� The RIM MVS solution relies on Unified CM to provide SIP device registration as well as underlying call routing.

� The solution is similar to Cisco mobility solutions for other vendor handsets and provides similar or equivalent functionality to Cisco Unified Mobile Communicator, Dual-Mode Clients, and Unified Mobility


UnifiedMobility

SNRRIM Mobile

Voice System (MVS)

RIM Mobile Voice SystemOverview



Cisco Unified CM

PSTN Gateway

Internet

Mobile Data Network

(Data Channel)

RIM BlackberryEnterprise Server

(BES)

SIP

WLAN(802.11)

Voice

Data

VoWLAN

ASACUMA

CUMC

Dial-via-Office (DVO)

Dual-mode

RIM Mobile Voice System Server

(MVS)

Dual-mode(Cisco Mobile/

Nokia CC)

RIM MVS may be deployed in parallel with Cisco Unified Mobility, CUMC, and Cisco dual-mode clients for non-Blackberry handsets.

System (MVS) Client

� Provide access to UC features directly from native integrated client on BlackBerry� Single number reach

� Dial-via-office

� Enterprise MWI and single voicemail box for all enterprise calls

� Enterprise mid-call features over data channel or via DTMF (KPML): Transfer, Hold, Resume, Call Waiting

� Mobile phone masking (outgoing enterprise caller ID)

� Move active calls between Blackberry mobile device and desk phone*

RIM Mobile Voice SystemFeatures and Functionality



� Move active calls between Blackberry mobile device and desk phone*

� Call filtering and call screening

� Dual-mode support for Voice over WLAN

� Relies on Unified CM for device registration and call routing via SIP integration (SIP line and trunk).

� SNR and dial-via-office are delivered natively rather than via Unified Mobility (no Remote Destination Profile or Remote Destination/Mobility Identity)

� MVS 5 supports VoWLAN/dual-mode functionality (co-resident with native SNR and DVO functionality)

� Leverages existing secure enterprise BES infrastructure* Send Call to Mobile (move to mobile) requires Unified CM 8.5

BlackBerry Enterprise Server (BES):

�Provides secure connectivity to the enterprise for BlackBerry devices �Provides device management and control including ability to push software to BlackBerry devices�Provides interface to BlackBerry configuration database (local or off-box)

BES

BES Configuration

Database

MVS Server

RIM Mobile Voice SystemBlackBerry Solution Components



BlackBerry Mobile Voice System (MVS) Server:

Two components (co-res or on separate boxes):

1.MVS Console:� Access to BlackBerry configuration database� Profile management and configuration changes� Web console for MVS administration

2.MVS Session Manager�Interfaces with Unified CM via SIP (trunk/line)�Interfaces with BES over IP�Handles call-control, mid-call features, and call filtering/screening�Sends/receives call information to/from BlackBerry devices

BlackBerry MVS Client:

�Installs on BlackBerry smartphone�Seamless integration, not a separate application�Adds desk phone features to native menus�Communicates with the MVS server via secure BES server connection

MVS Client

BES Server:�2 Intel Xeon 2.0 GHz (or higher) processors�4 GB of RAM�Minimum of 2 HDDs (RAID 1 or higher)�OS: Windows Server 2003 R2 SP2+ (Enterprise or Standard, 32 or 64-bit), Windows Server 2008 SP1+ (32 or 64-bit), or Windows Server 2008 R2 (64-bit)�BES software for Microsoft Exchange, Lotus Domino, or Novell Groupwise integration.�SQL database software

MVS Server Console and Session Manager (same hardware

:

Servers may also be virtualized (virtual machines allocated with equivalent of two Xeon 2.0 GHz processors and 4 GB RAM)

RIM Mobile Voice SystemSolution Requirements



requirements as BES):�2 Intel Xeon 2.0 GHz (or higher) processors�4 GB of RAM�Minimum of 2 HDDs (RAID 1 or higher)�OS: Windows Server 2003 R2 SP2+, Windows Server 2008 SP1+ or R2

BlackBerrry Smartphone:�Devices: BlackBerry Pearl (8100, 8220, 9100, 9105), Curve (8300, 8310, 8520, 8900), 8700 series, 8820, 8800, Bold (9000, 9650, 9700), Storm (9500, 9530), Storm 2 series, Tour 9630, Torch 9800�Firmware: 4.5 or higher (GSM), 4.7.1 or higher (CDMA), and 5.0 or higher (VoWLAN/dual-mode)

Cisco Unified CM:�Versions: 6.1, 7.0, 7.1, and 8.0 (Unified CM 8.5 is currently in IOT testing)�COP file from RIM must be loaded.�DLUs: 3 DLUs for regular MVS device or 6 DLUs for VoWLAN MVS device

The RIM MVS solution and documentation uses a slightly different call flow terminology than Cisco solutions.

Call Direction:(always from perspective of BlackBerry mobile device)

� Mobility Terminated – Inbound calls to user's enterprise number are extended to BlackBerry device.

COMPARE WITH: Mobile Connect (single number reach)

�

RIM Mobile Voice SystemCall Flow Terminology and Cisco Equivalents



� Mobility Originated – Outbound calls made from BlackBerry devicethrough enterprise telephony infrastructure.

COMPARE WITH: Dial-via-Office (or MVA/EFA 2-stage dialing)

Call Type:� PBX Initiated – Call setup is initiated by MVS thru Unified CM

COMPARE WITH: CUMC DVO Reverse where Unified CM calls client and Mobile

Connect call forking to remote destination/mobility identity

� Device Initiated – Call setup is initiated by BlackBerry device into Unified CM system.

COMPARE WITH: CUMC DVO Forward where client calls Unified CM system

High-level Unified CM configuration:

1. Configuration of BlackBerry MVS Client with Voice over WiFi (or BlackBerry MVS Client) device. (Requires COP file install on Unified CM)

� MVS client device shares line with user's desk phone

2. Configuration of SIP trunk pointing to RIM MVS

DN: 1001

RIM Mobile Voice SystemUnified CM Configuration



2. Configuration of SIP trunk pointing to RIM MVS server for SIP integration. Requires equivalent Telephony Connector configuration on MVS server to point back to Unified CM node(s).

� Multiple telephony connectors can be configured to connect to multiple Unified CM nodes and/or clusters.

� Users distributed across connectors (per user/user groups).

SIP trunkTelephony

Connector (TC)

Unified CM cluster 1

Unified CM cluster 2

RIM MVS

RIM MVS Unified CM

TC 1

TC 2

TC 3User distribution

a. Device-initiated calling:

Configure route pattern on Unified CM pointing to MVS SIP trunk. Route pattern must be equivalent to DID/DDI number configured within MVS. MVS configuration:

Unified CM configuration:

3. Configure appropriate device-initiated and PBX-initiated settings on Unified CM and RIM MVS as follows:

RIM Mobile Voice SystemUnified CM Configuration (cont.)



b. PBX-initiated calling:

Configure Caller ID DN on dedicated Unified CM PSTN trunk to ensure outbound caller ID for PBX-initiated calls matches Caller Identification Number configured within MVS. This number is sent over data channel/WLAN to MVS client and compared against incoming calls to the device.

MVS configuration: Unified CM configuration:

� 802.11 a/b/g/n support depending on device type:

� BlackBerry 9100/9105 (Pearl) – 802.11 b/g/n

� BlackBerry 9000 (Bold) – 802.11 a/b/g

� All other MVS supported BlackBerry devices – 802.11 b/g

� G.711 only for VoWLAN (G.729 support coming)

Requires firmware 5.0 or later

RIM Mobile Voice SystemDual-Mode Considerations



� Handoff between WLAN and cellular� Always PBX-initiated (Similar to Cisco Mobile 8 Mobility Softkey method of hand-out)

� Manual hand-out (WLAN to cellular): Move call to Mobile

� Manual hand-in (cellular to WLAN): Move call to WiFi

� Support for automatic handoff based on WLAN signal strength expected in Q4 2010.

WLAN(802.11)


RIM MVS 5client

� Capacity/Scalability

� Maximum of 10,000 MVS mobile clients per MVS Session Manager

� Add additional MVS Session Managers to scale beyond 10,000 (note each MVS Session Manager requires separate BES)

� Unified CM node/cluster device registration capacity must be considered

The following design-related information should be considered when deploying RIM MVS:

RIM Mobile Voice SystemDesign Considerations



� Unified CM node/cluster device registration capacity must be considered

� Dual-mode and VoWLAN

� Same or similar deployment considerations as with other dual-mode devices/solutions (Cisco Mobile 8 and Nokia CC):

� Requirement for WLAN site survey and device testing

� WLAN QoS to provide priority to voice traffic

� Channel cell radius (-65 dBm or less) and same channel cell separation of 19 dBm

� Channel cell overlap (15-20%),

� AP call capacityWLAN

(802.11)

� Redundancy

� RIM MVS Session Managers can be deployed for high-availability by deploying one BES server and three MVS servers:

• MVS Console

• MVS Session Manager (active)

• MVS Session Manager (standby)

BES

MVS Session Managers

ACTIVE STANDBY

X

RIM Mobile Voice SystemDesign Considerations (cont.)



� No redundancy available for BES or MVS Console

� Network Latency

� Maximum of 240 ms round-trip time must be maintained between the following components:

• MVS Console and BES Configuration Database

• MVS Console and MVS Session Manager(s)

• MVS Session Manager and BES

• MVS Session Manager and Unified CM

MVS Console

Additional SIP trunk on Unified CM and DID for device-initiated calling

required with high-availability MVS server deployments



The Future: Transitioning to Direct Connect

Everything contained within this section is subject to change. No guarantees of delivery or commitments of applications and features herein.CAUTION

!

PSTN

MeetingPlace/MeetingPlace Express

Unity/Unity Connection

MPMP

Cisco Unified Mobile Communicator Cisco Unified CM

Dual-ModePhones/ Clients


iPhoneiPhone

Cisco Mobile 8.x

Nokia CC

WLAN

(802.11)

Unified Mobility

Transitioning to Direct Connect ClientsArchitecture – Today



MS Active Directory 2000/2003

MS Exchange 2000/2003/

2007

Mobile Data Network

(Data Channel)

UU

iPhoneiPhone

DMZ

Internet

BES(w./ MDS)

Cisco Adaptive Security Appliance (ASA)


IMAP

LDAP

SIP

JTAPI

SIP/SIMPLE/ WebDAV

(BlackBerry-only)

PSTN

MeetingPlace/MeetingPlace

Express

Unity/Unity Connection

MPMP

Direct-connect clients


Cisco Unified CM

JTAPI

WLAN(802.11)

+ Dual-Mode clients

Unified Mobility

Mobile VoiceSystem (MVS)

FutureTransitioning to Direct Connect ClientsArchitecture – Future



MS Active Directory 2000/2003

MS Exchange 2000/2003/

2007

Internet

Mobile Data Network

(Data Channel)

UU

LDAP

IMAP

WebDAV

SIP

JTAPI

iPhoneiPhone Cisco Unified

Presence

XMPP

iPhoneiPhoneROADMAP: � Cisco Mobile 8 MR to support multitasking with iOS 4 – Dec. 2010� XMPP IM/presence, DVO client (w./ dual-mode) – 1HCY2011

ROADMAP: � XMPP IM/presence support, DVO, mid-call features, etc. (w./ dual-

mode NCC) – Feb./Mar. 2011

FutureTransitioning to Direct Connect ClientsUpcoming Client Roadmap



ROADMAP: � Dual-mode/VoIP client – 1HCY2011� XMPP IM/presence support, DVO, mid-call features, etc. (w./ dual-

mode) – 2HCY2011

ROADMAP: � Dual-mode auto handoff – Dec. 2010� XMPP IM/presence support – 1HCY2011

!!!! CAUTION !!!!! ALL DATES AND FEATURES SUBJECT TO CHANGE

Cisco UnifiedMeetingPlace

Cisco Unity/Unity Connection

MPMP

UU

Cisco Unified CM

DMZ

Direct-connect/VoIP 8.x and later clients

iPhoneiPhone

Cisco Unified


PSTN

Unified MobilityWLAN

(802.11)

Transitioning to Direct Connect ClientsParallel Deployments and Migration




MS Active Directory

MS Exchange

ASA TLS ProxyCUMC/Cisco Mobile 7.x

clients

Cisco Unified Presence

iPhoneiPhone

Cisco Mobile 7.x /RIM MVS clients

Internet

RIMBES

(w./ MDS)

Mobile Data Network

RIMMVS

MMP over SSL

MMP over SSL / RIM BES

Secure Access(VPN)

Mobile Data

Mobile Voice

Data Flow



Q & A

Cisco UC Mobility SolutionsApplication Feature Matrix (1 of 2)

FEATURE BlackBerry iPhone NokiaWindows

Mobile

APPLICATION CUMC v. 7.1 RIM MVS 5.0 CUMC v. 7.1 Cisco Mobile 8 CUMC v. 7.0 CUMC v. 7.0

Single Number



Single Number Reach and Single VM Box

��

Single Number Reach On/Off from mobile

��

Voice over WLAN(dual-mode)

�� Nokia Call

Connect 2.1

Hand-out (WLAN to Cellular)

Manual Manual Automatic

Hand-in (Cellular to WLAN)

Manual Automatic

Dial-via-Office DVO-F & -R DVO-F & -R DVO-F Over WLAN DVO-R DVO-R

Cisco UC Mobility SolutionsApplication Feature Matrix (2 of 2)

FEATURE BlackBerry iPhone NokiaWindows

Mobile

APPLICATION CUMC v. 7.1 RIM MVS 5.0 CUMC v. 7.1 Cisco Mobile 8 CUMC v. 7.0 CUMC v. 7.0

Desk Phone ��

ERROR: undefined

OFFENDING COMMAND: ‘~

STACK:

Mobile UC Design Session - Cisco

Documents

Transcript of Mobile UC Design Session - Cisco