unified mobility

33
© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-1 Features and Applications for Multisite Deployments Implementing Cisco Unified Mobility

Upload: gilles-de-paimpol

Post on 23-Oct-2015

19 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-1

Features and Applications for Multisite Deployments

Implementing Cisco Unified Mobility

Page 2: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-2

Outline

Cisco Unified Mobility Overview

Cisco Unified Mobility Call Flow

Cisco Unified Mobility Components

Cisco Unified Mobility Configuration

Page 3: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-3

Cisco Unified Mobility Overview

Page 4: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-4

Cisco Unified Mobility

Cisco Unified Mobility has two components: Mobile Connect and Mobile Voice Access (MVA).

With Mobile Connect, calls placed to office phones ring the office phones and associated remote phone.

MVA allows users to call into the enterprise from any phone and place outgoing calls that appear to come from their office phone.

Cisco Unified Communications

Manager

Gateway

PSTN

Mobile Connect lets remote and office

phones ring simultaneously.

Call to office number.

Call to Mobile Voice Access directory number.

Mobile Voice Access establishes a system to create enterprise calls from any location.

Remote

PhoneOffice Phone

Customer

Page 5: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-5

Mobile Connect and MVA Characteristics

Mobile Connect characteristics: Receive calls on multiple devices by using a single phone number

Answer incoming calls on office or remote phone

Switch active calls between office and remote phone

MVA characteristics: Originate enterprise calls from any remote destination by:

– Dialing to the enterprise MVA number

– Entering ID (if required) and PIN

– Entering destination number to be called

Called party sees the office phone number as the calling party

Switch active calls between office and remote phone

Page 6: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-6

Cisco Unified Mobility Features

Single (office) number for multiple devices:

– Enterprise caller ID preservation

– Single enterprise voice mailbox

User-configurable access lists to permit or deny calling numbers that can ring a specific remote phone

User interface to enable or disable Cisco Unified Mobility:

– Mobile Voice Access TUI

– Cisco Unified Communications Manager user webpages

Access to enterprise features from remote phones using DTMF:

– Softkeys can be used on phones with smart client installed.

Call logging (CDR)

Page 7: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-7

Cisco Unified Mobility Call Flow

Page 8: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-8

PSTN

Outside Caller

Remote Phone of 2001

Cisco Unified Communications

Manager

Mobile Connect

Office Phone2001

Call to 1-511-555-2001

Gateway479-555-1555

Caller ID:479-555-1555

408-555-1001

511-555-2XXX

Outside caller calls office phone 2001 (dials 1-511-555-2001).

Mobile Connect rings office phone and remote phone.

Call is picked up at remote phone; caller ID of outside caller is preserved at remote phone.

Mobile Connect Call Flow—Incoming Calls to Office Phone

Page 9: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-9

Mobile Connect Call Flow—Internal Calls Placed from Remote Phone

Remote phone calls internal phone 2002 (dials 1-511-555-2002).

Mobile Connect replaces caller ID (408-555-1001) of remote phone with directory number of associated office phone (2001).

PSTN

Gateway

2002

Mobile Connect Call to 1-511-555-2002

Caller ID:2001

Office Phone2001

511-555-2XXX

Cisco Unified Communications

Manager

408-555-1001

Remote Phone of 2001

Page 10: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-10

PSTN

Remote Phone of 2001

Cisco Unified Communications

Manager

MVA

Office Phone 2001

511-555-2XXX

479-555-1555

408-555-1001

Gateway IVR

Application

VoiceXML—Enter ID And

PIN

Remote phone dials MVA number (1-511-555-2999).

Caller is authenticated at Cisco Unified Communications Manager and requests call to outside destination 9-1-479-555-1555.

Caller is connected to MVA media resource from where the outgoing call is placed on behalf of the office phone (2001).

VoiceXML

2999

Call to 1-511-555-2999

Caller ID:511-555-2001

MVA Call Flow

Outside Destination

Page 11: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-11

Cisco Unified MobilityComponents

Page 12: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-12

Cisco Unified Mobility Requirements

Cisco Unified Mobility requires: Cisco Unified Communications Manager 6.0

Cisco Unified Mobile Voice Access service activated

H.323 or SIP gateway providing Mobile Voice Access IVR application

Out-of-band DTMF

Remote Destinations must be external devices

Page 13: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-13

Cisco Unified Mobility Configuration Elements

Configuration Element Name

Configuration Element Function

End UserThe end user is referenced by the office phone and remote destination profile. Mobile Connect and/or MVA must be enabled. A maximum number of remote destinations can be configured.

PhoneThe office phone needs to be configured with an owner (i.e., the end user).

Remote Destination Profile

A virtual phone device. Per office phone number, a shared line is configured. End user, (device) CSSs, and MOH audio sources are specified. One or more remote destinations are added.

Remote Destination

Associated with shared line(s) of remote destination profile. Configured with destination number. Optionally, access lists can be applied. Mobile Phone and Mobile Connect functions are selectively enabled.

Access ListFilters used to permit or deny incoming calls placed to the office phone to ring a remote destination. Permitted or denied caller IDs are specified.

MVA Media Resource

Media resource used to interact with the VoiceXML call application running on a Cisco IOS router. Only required for MVA.

Page 14: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-14

Remote Destination

ProfileUser ID

CSSRerouting CSS

etc.

Shared Line Between Phone and Remote Destination Profile

Office Phone 1MAC Address

OwnerCSSetc.

Line1: 2001Partition

CSSetc.

Office Phone 2MAC Address

OwnerCSSetc.

Line1: 2002Partition

CSSetc.

Line1: 2001Partition

CSSetc.

Line2: 2002Partition

CSSetc.

Remote Destination1:9-1-408-555-

1001

Remote Destination2:9-1-479-555-

1555

shared line shared line

Call to shared line rings office phone line and remote destination(s)

associated with corresponding line of remote

destination profile.

Page 15: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-15

Relationship of Cisco Unified Mobility Configuration Elements

Service ActivationMVA Service

UserEnable Mobility

Enable MVARD Limit

SoftkeysMobility Softkey

IP phone

ACL

RDP

RD1Enable MC

RD2Enable MC

Service ParameterEnable MVA, Enterprise Feature Access

Media ResourcesMVA Number, Localization

H.323 Gateway

ACL: Access List, MC: Mobile Connect, MVA: Mobility Voice Access, RD: Remote Destination, RDP: Remote Destination Profile

IVR Application VoiceXML Call MVA

Enter RD and PIN

Owner

Owner

User ID

PIN

Page 16: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-16

Cisco Unified Mobility Configuration

Page 17: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-17

Cisco Unified Mobility—Mobile Connect Configuration Procedure

Configure Mobile Connect:1. Add mobility softkey to IP phone softkey templates.

2. Configure end user.

3. Configure IP phone.

4. Configure remote destination profile with shared line.

5. Configure remote destination(s) to remote destination profile.

6. Configure service parameters.

7. Optional: Implement access lists to specify which caller ID is allowed to ring a remote destination when a call to the office phone is received.

a) Configure access lists.

b) Apply access lists to remote destination.

Page 18: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-18

Step 1: Configure Softkey Template

Device > Device Settings > Softkey Template

Add the Mobility softkey to On Hook and to

Connected call state.

Page 19: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-19

Step 2: Configure End User

User Management > End User

Enable Mobile Connect for end user.

Set maximum number of remote

destinations for end user.

Page 20: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-20

Step 3: Configure IP PhoneDevice > Phone

This line will be shared with remote destination profile.

Set Owner User ID.

Assign softkey template.

Page 21: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-21

Click here and add line of office phone. After add, screen updates.

Step 4: Configure Remote Destination Profile

Device > Device Settings > Remote Destination Profile

CSS used for outgoing calls placed using

MVA.

CSS used for ringing remote

destination(s) when receiving a call at the office phone.

Note: Line is shared with office phone. Configured line CSS and partition apply to both devices: office phone and remote destination profile. Line CSS and device CSS are combined (partitions of line CSS considered first).

Page 22: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-22

Associate remote destination with line(s) of remote

destination profile.

Step 5: Add Remote Destination(s) to Remote Destination Profile

Device > Remote Destination

Line(s) of remote destination profile

are shown only after setting remote destination profile and clicking Save.

Once saved, remote destination profile cannot be

changed.

Number of remote destination.

Allows transfers of active calls from office phone to remote destination using

the Mobility softkey.

Allows calls placed to office phones to also ring the remote destination.

Page 23: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-23

Step 6: Configure Service ParametersSystem > Service Parameters

If configured remote destination number does not

match caller ID of remote phone (e.g., because of 9-1 prefix in remote destination

number), change from Complete Match to Partial

Match and set the number of digits that have to match.

Otherwise, calls to internal devices are not shown with

caller ID of office phone.

Page 24: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-24

Step 7a: Configure Access List

Enter name and description and select owner.

Device > Device Settings > Access List

Select type of ACL: Allowed (if checked) or Blocked (if

unchecked)

Click Add Member for initial configuration of an access list

member.Click entry from list at bottom

to change configuration of existing member.

Page 25: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-25

Step 7b: Apply Access List to Remote Destination

Device > Remote Destination

Either allowed or blocked acess list can

be set. If blocked access list is set, all numbers not listed in

access list are allowed (and vice versa).

Page 26: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-26

Cisco Unified Mobility—Mobile Voice Access Configuration Procedure

Configure MVA:1. Activate Cisco Unified Mobile Voice Access Service.

2. Configure service parameters:

a) Enable MVA globally.

b) Enable and configure enterprise feature access.

3. Enable MVA per end user.

4. Configure MVA media resource.

5. Configure MVA VoiceXML application at Cisco IOS gateway.

Page 27: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-27

Step 1: Activate Cisco Unified Mobile Voice Access Service

Cisco Unified Serviceability > Tools Service Activation

Page 28: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-28

Step 2: Configure Service ParametersSystem > Service Parameters

Enable access to enterprise features.

Enable MVA globally.

View default enterprise feature

codes and change if required.

Page 29: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-29

Step 3: Enable MVA per End User

User Management > End User

Enable MVA for end user.

Page 30: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-30

Step 4: Configure MVA Media Resource

Media Resources > Mobile Voice Access

Enter number of MVA media resource.

The H.323 gateway running the MVA call application needs to have access to the partition

of the MVA number (if set).

At least one locale has to be selected for the MVA media

resource.

Page 31: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-31

application service mva http://10.1.1.1:8080/ccmivr/pages/IVRMainpage.vxml!voice-port 0/0/0:23 translation-profile incoming pstn-in!voice translation-profile pstn-in translate called 1!voice translation-rule 1 rule 1 /.*5552\(...$\)/ /2\1/!dial-peer voice 29991 pots service mva incoming called-number 2999 direct-inward-dial!dial-peer voice 29992 voip destination-pattern 2999 session target ipv4:10.1.1.1 dtmf-relay h245-alphanumeric codec g711ulaw no vad

Step 5: Configure MVA at Cisco IOS Gateway

dial-peer voice 1 pots destination-pattern 9T incoming called-number 2... direct-inward-dial port 0/0/0:23!dial-peer voice 2 voip destination-pattern 2... session target ipv4:10.1.1.1 incoming called-number 9T codec g771ulaw

Page 32: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-32

Summary

Mobile Connect enables users to receive calls placed to their enterprise number at the enterprise phone and remote phones such as cell phones. Mobile Voice Access extends the Mobile Connect functionality by allowing enterprise calls placed from a remote phone to first connect to the enterprise and then break back out to the called number using the enterprise number of the user as the calling number.

Mobile Voice Access requires an H.323 gateway providing an IVR application to Mobile Voice Access users.

The Cisco Unified Mobile Voice Access service must be activated in the Cisco Unified Communications Manager cluster for Mobile Voice Access.

Implementation of Cisco Unified Mobility includes the configuration of access lists, remote destination profile, and remote destinations.

Page 33: Unified Mobility

© 2008 Cisco Systems, Inc. All rights reserved. CIPT2 v6.0—4-33