extension mobility cross cluster...

© 2012 Cisco and/or its affiliates. All rights reserved. BRKUCC-2040 Cisco Public

Extension Mobility Cross Cluster (EMCC) Operation and Design BRKUCC-2040

2


Session Objectives

§ At the end of the session, participants should be able to: ‒ Understand the basic operation of EMCC ‒ Understand EMCC-related configuration ‒ Know limitations and supported features ‒ Able to describe EMCC call flows ‒ Understand EMCC Emergency calling

3


Agenda

EMCC Registration

EMCC Call Processing

EMCC Call Admission Control

EMCC Security

EMCC Design Considerations

EMCC Configuration Tasks discussed throughout

EMCC Overview

EMCC Service Overview

4

EMCC Overview

5


Overview – Extension Mobility

§  First released in Communications Manager v3.1 §  Extension Mobility has been limited to intra-cluster users/devices §  User wants: ‒ Seamless dialing, features and services on any physical device ‒ Familiar configuration (lines, speed dials, message button, MWI) on any device

§  Administrator needs: ‒ Security ‒ Call Admission Control (CAC)

‒ Appropriate media resource selection and local gateway access ‒ Serviceability ‒ Dynamic control of devices for CTI Applications

6


Extension Mobility Cross Cluster Challenges

§  With intra-cluster EM … ‒ … device information is available in the local database

‒ … user information is available in local database ‒ … global information is available in local database

§  With inter-cluster EM … ‒ … device information is in one cluster’s database ‒ … user information is in another cluster’s database ‒ … global information is in both

Either device information must be migrated to cluster managing user information, or vice versa

Either device information must be migrated to cluster managing user information, or vice versa

7


EMCC Overview

Good News – Features Work! §  User features are enabled when logging in from remote cluster ‒ Shared line ‒ Hunt lists ‒ Transfer/conference/hold ‒ Barge ‒ Speed dials ‒ MWI ‒  Intercom

§  Features supported in future releases ‒ Local Media resources (Other than RSVP Agents)

8

EMCC Service Overview and Configuration

9


Overview – Extension Mobility Cross Cluster Concepts

New terminology: “Visiting” & “Home” Clusters (from USER’s perspective!)

Visiting Phone registers with Home Cluster John C

Home Phone

Home Cluster

Visiting Phone

VisitingCluster

John C’s Info

Home Cluster dialing habits are maintained!

10


EMCC Service Configuration EMCC Trunk

Cisco Unified CM 8.0 (and later)SIP Trunk parameter => Trunk Service Type

Cluster 2 Cluster 1

TFTP

EM

TFTP

EM PSTN

EMCC SIP Trunk

ICT

11


Cluster 2 Cluster 1

EMCC Service Configuration EMCC Trunk

TFTP

EM

TFTP

EM PSTN

EMCC SIP Trunk

ICT

§ EMCC Trunk -Special Trunk with no remote destination -Only one SIP trunk to communicate to all other EMCC clusters -EMCC does not affect or interact with Inter Cluster Trunks -Carries login, RSVP and user location requests

12


EMCC Service Configuration Intercluster Service Profile

§  Intercluster Service Profile ‒ Activate EMCC locally

‒ Select an EMCC SIP Trunk PSTN Access (required)

‒ Select an EMCC SIP Trunk RSVP Agent (optional)

13


EMCC Service Configuration (v8.0 – v8.6) EMCC Remote Clusters

§  Each cluster (remote and local) must have a unique Cluster ID §  Administratively add Remote Clusters that will participate in EMCC §  Information exchanged between clusters via “Update”

14


EMCC Service Configuration (v9.0) Cluster View

§  Cluster View ‒ Same use as 8.x version

‒ No longer EMCC Specific ‒ Aggregates all remote cluster services in one page

15


EMCC Service Configuration EMCC Feature Configuration Settings

§  EMCC solution has built in redundancy with Default and Backup Server for Remote Cluster Update.

16

EMCC Phone Registration

17


Visiting Cluster

EMCC Login (1 of 4) The “Before” Picture …

Home Cluster

TFTP

John C

DB DB EM

TFTP

EM

0xABCD

JC ABCD

= Device Profile

= Phone Config

EMCC

18


Visiting Cluster Home Cluster

EMCC Login (2 of 4) Find User’s Home Cluster …

TFTP

DB DB EM

TFTP

EM

0xABCD

ABCD

John C

User not local

Do you have UserID?

Yes

Get device details

Get device details about 0xABCD such as Device Name, Protocol, Model, ClusterID, Geolocation …

EMCC JC

John C 19


DB

ABCD


EMCC Login (3 of 4) Home Cluster Preparation …

TFTP

DB EM

TFTP

EM

0xABCD

ABCD

UserID, Passwd, Device Name,

Protocol, Model,

ClusterID, Geolocation

Use EMCC base to create device EMCC

JC

JC ABCD

Change Notify (CN)

JC

User Login 10

Home TFTP

address

John C Note: User experience is like normal EM login during this process.

20


DB

ABCD


EMCC Login (4 of 4) Visiting Cluster Preparation

TFTP

DB EM

TFTP

EM

0xABCD

ABCD EMCC

ABCD

JC

ABCD

JC

Modify Device

11 CNotify 12

CNotify 12

altTFTP

Reset 13

ABCD altTFTP

14 TFTP Get

15 TFTP Get

§  Phone Loads are not enforced during the Login process. Removed from Home Cluster config.

§  Step 16: If HC locale is different, phone will download new locale from Visiting TFTP server. If not available, maintains VC locale.

§  DLUs are NOT consumed in the Home Cluster for the visiting phone. John C

10

Home TFTP

address

21


EMCC Login Process Summary

§  Users from a “Home” Cluster (HC) login to a phone at a “Visiting” Cluster (VC) §  Login procedure brings the visiting device information into the HC database §  HC database builds a temporary phone device with user’s device profile §  HC TFTP server builds the phone configuration file §  After login, VC directs the phone to HC TFTP server §  Phone downloads its TFTP configuration from HC TFTP server and then cross-

registers with HC CUCM

22


EMCC Login Performance

§  Cisco Unified CM Extension Mobility service can be enabled on 1 or 2 nodes in the cluster

§  EM login less overhead than EMCC, but total login rate is based on expected combined EM and EMCC logins

Single EM login server (I2/H2)

Dual EM login servers (I2/H2)

Intracluster only 250 375

Intercluster only 75 90

Inter/Intracluster 225 (40 EMCC/185 EM) 320 (40 EMCC/280 EM)

23


EMCC Registration

§ Where Do Device Attributes Come From? §  Common Device Configuration

Common Phone Profile ‒ Bulk Administration => EMCC => EMCC Template

24


Common Device Configuration and Common Phone Profile

25


EMCC Registration



§  Region settings (codec selection) ‒ Advanced features => EMCC => EMCC Feature Configuration

26


EMCC Region Settings

§  EMCC Region settings override normal region configuration §  All EMCC Region parameters MUST be configured with same

values in ALL clusters. If they are different, RSVP Agent for that cluster will be disabled by Remote Cluster Update operation.

27


EMCC Registration



§  Region Settings (codec selection) ‒ Advanced features => EMCC => EMCC Feature Configuration

§  EMCC Roaming Device Pool (determined via Geolocations & EMCC Geolocation Filter)

28


DB

ABCD


Geolocations, EMCC Geolocation Filter and Roaming Device Pool

TFTP

DB EM

TFTP

EM

0xABCD

ABCD

UserID, Pswd, Device Name,

Protocol, Model,


EMCC

ABCD

JC

John C

ABCD

JC

Geolocation= US:NC:Raleigh:Kit Creek:7200

29


Geolocations applied to a device - Civic Location Format having fields:

Country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, PC

- Based on RFC 4119

-Geolocation transportable over SIP Trunks

- Introduced in CUCM v7.1(2)

Label Description Example Country The country is

identified by the two-letter ISO 3166 code.

US, IN

A1 (State) national subdivisions (state, region, province, prefecture)

New York, Karnataka, Maharashtra, New Delhi

A3 (City) city, township, shi (JP)

New York, Bangalore, Mumbai, New Delhi

LOC Additional location information

Room 543, Building 1, bldg2, bld3

NAM Name (residence, business or office occupant)

gw1, gw1_port1

Geolocations

30


Geolocations

A Geolocation: used to identify where a device is located.

Geolocation filter: used to indicate what parts of the Geolocation are significant

31


System => Geolocation Filter

Advanced Features => EMCC => EMCC Feature Configuration

Geolocation Information and Conveyance details can be found at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_1/ccmfeat/fsgeoloc.html

Geolocations Filter Configuration

32


DB

ABCD


Geolocations, EMCC Geolocation Filter and Roaming Device Pool

TFTP

DB EM

TFTP

EM

0xABCD

ABCD


Protocol, Model,


EMCC

ABCD

JC

John C

ABCD

JC

Geolocation= US:NC:Raleigh:Kit Creek:7200

EMCC Geolocation Filter = {Country, A1}

{US:NC}

Filter

Note: EMCC capable phones MUST have a Geolocation configured via device configuration or Device Pool.

33


EMCC Roaming Device Pool

Recommended: Configure only one Device Pool per Remote Cluster

{US:NC}

EMCC Geo. Filter

34


EMCC Roaming Device Pool

§  Visiting phone inherits select parameters of its Roaming Device Pool (CM Group, Adjunct CSS, etc.)

§  After login, the visiting phone will splash a roaming status message for 5 seconds.

35


EMCC Roaming Device Pool Assignment Summary 1)  HC configures at least one roaming device pool per remote cluster

-distinct geolocation characterizing that cluster 2)  Phones enabled for EMCC in VC must have be assigned a Geolocation

-At Device Pool or Phone Device level 3)  Login process sends phone’s Geolocation from VC to HC 4)  Phone’s Geolocation is filtered by ‘EMCC Geolocation Filter’ on HC 5)  Using filtered geolocation, HC finds the most suitable DP for roaming DP 6)  HC uses roaming device pool to build EMCC Phone configuration in database

36


37



§  EMCC Call Search Spaces §  EMCC Various Call Flows §  EMCC Emergency Call Routing

38


DB

ABCD


EMCC Call Processing What s the CSS of the Visiting Phone?

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC

altTFTP ABCD altTFTP

§  Visiting Phone is registered to the Home Cluster

§  We want to make a call … but first … What is the Call Search Space of the Visiting Phone??!!

John C

PSTN

EMCC SIP Trunk

ICT

39


EMCC Visiting Phone CSS Summary

Home cluster builds a CSS for the phone that consists of three elements, in priority order:

1)  Adjunct CSS (More Later) §  Configured in roaming DP to support country specific emergency dialing plan (e.g., UK

phone remotely registers back to US cluster; user dials 9.999 (UK emergency#) that US cluster will normally not recognize. HC=US, VC=UK)

§  May skip Adjunct CSS configuration if HC and VC share the same emergency pattern and Local Route Groups are implemented.

2)  Line CSS §  Normal configuration on Device Profile Directory Numbers.

3)  EMCC CSS §  Visiting phone will not have a configured Device CSS in the HC. §  HC takes the EMCC CSS (new) setting from the Device Profile configuration page and

uses this as the Device CSS.

40


Adjunct CSS (from Roaming Device Pool)

Adjunct CSS Partition A1

Partition A2

EMCC CSS Partition D1

Partition D2

EMCC CSS

Resulting CSS Partition A1

Partition A2

Partition L1

Partition L1

Partition D1

Partition D2

The resulting CSS is the concatenation of all three.

EMCC Call Processing CSS Determination

Line CSS

Line CSS Partition L1

Partition L2

Reminder: Partition order in a CSS is the tie-breaker only when two patterns are an equal best match.

Device Profile Config

41


EMCC CSS in Device Profile

§  Required for Line restricted Class of Service configuration §  Device needs CSS to allow all calls, but line still applies restrictions

42



§  EMCC Call Search Spaces §  EMCC Various Call Flows §  EMCC Emergency Call Routing

43


DB

ABCD


EMCC Call Flows Phone to Home Cluster Phone

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC


John C

PSTN

ICT

x1002 x2001

EMCC SIP Trunk

IP

Media

Signaling Signaling

x1001

44


DB

ABCD


EMCC Call Flows Phone to Visiting Cluster Phone

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC


John C

PSTN

ICT

x1002 x1001 x2001

EMCC SIP Trunk

IP

Signaling

Media Keep in mind, the user will dial the phone next

to them as if they were in the Home cluster:

Home Cluster Dialing Habits Maintained!

45


DB

ABCD


EMCC Call Flows Phone to PSTN – NO Local Route Group

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC


John C

PSTN

ICT

x1002 x2001

EMCC SIP Trunk

IP

Signaling

Media

x1001

Incoming calls for this DID will always be received on the Home Cluster GW!

46


DB

ABCD


EMCC Call Flows Phone to PSTN – WITH Local Route Group

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC


John C

PSTN

ICT

x1002 x2001

EMCC SIP Trunk

IP

Signaling

Media

x1001

47


EMCC Call Flows Phone to PSTN – WITH Local Route Group

§  Let’s examine a few aspects of using the EMCC SIP Trunk for PSTN Access … ‒  SIP Invite arrives at Visiting Cluster – Call Search Spaces are involved again.

‒  Advanced Features => EMCC => EMCC Feature Configuration

CSS of the Visiting phone!

48


EMCC Call Flows EMCC SIP Trunk for PSTN Access

§  Home cluster may or may not use LRG. If no LRG, then call follows the configured Route List => Route Group => Gateway path.

§  If the home cluster is using LRG, then a Visiting cluster receives call and looks up the original Visiting phone configuration in the database to determine its LRG setting (via its Device Pool) to find the appropriate gateway for the call.

§  If Visiting phone does not have a Standard Local Route Group configured in the Visiting cluster Device Pool, calls will fail.

§  Emergency calls REQUIRE the use of Local Route Groups – Unified CM 8.0 allows for EMCC Emergency Calls to be handled with LRGs even if the rest of the Dial Plan does not use LRGs … (next slide) …

49


Local Route Group

§  Device pool is site-specific §  Local route group

is associated with device pool §  Local route group is thus

associated with all devices using a given device pool: e.g. phones, gateways

50


Local Route Group With it: GW Chosen by Association to Calling Device

DFWDevices

CSS’s Partitions Route Lists Route Groups

DFW

dev

ices

D

P: D

FW_D

P

JFK RG

JFK Gateways

JFKDevices

SFO RG

SFO Gateways

SFODevices 9.1[2-9]XX[2-9]XXXXXX

US_pstn_part Std Local Route Group

US LOC RL

DFW RG

DFW Gateways

Choice of Local Route Group based on calling

device’s Device Pool configuration

SFO

dev

ices

D

P: S

FO_D

P JF

K e

vice

s D

P: K

F_D

P

51


DB

ABCD


EMCC Call Flows Phone to PSTN – Emergency Calls

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC


John C

PSTN

ICT

x1002 x2001

EMCC SIP Trunk

IP

Signaling

Media

x1001 Emergency!

Call MUST go out a local gateway for proper

Emergency Call handling 52


EMCC Emergency Calls

§  Emergency calls REQUIRE the use of LRGs in the Home cluster to ensure calls are routed via visiting phone’s local gateways.

§  EMCC adds the “Adjunct CSS” - Inherited from EMCC Roaming Device Pool (discussed earlier).

§  Allows for configuration of the Visiting cluster’s emergency route pattern, only to be applied to Visiting phones from that cluster.

§  When Home cluster and Visiting cluster use the same emergency route pattern, but Home cluster does not implement Local Route Groups, a 2nd replica emergency route pattern using LRG can be created, only accessible via Adjunct CSS.

§  Note: If Local Route Groups are already deployed for the Emergency route pattern AND a home and visiting cluster pair have the same Emergency dial string, use of the Adjunct CSS is not required.

53


How Does Adjunct CSS Work?

Adjunct CSS for UK Cluster has only one member partition: EMCC Emergency Partition for UK

Configured in DP, the adjunct CSS {Adjunct CSS for UK Cluster} enables UK emergency dialing from UK phone that registers to US cluster after login and binding to this roaming DP. US Cluster is the home cluster.

54


Configuring Emergency Patterns

… and we configure the {RL to Local PSTN} Route List with only one Route Group member – the Standard LRG. As a result, HC (US cluster) will route this call across the EMCC SIP Trunk and the Visiting cluster will direct the call to the device’s Local Route Group.

If visiting Phone (in UK) that registers to HC (in US) dials 9.999, it matches RP 9.999/{EMCC emergency partition for UK} because of the Adjunct CSS in the phone’s roaming DP. We direct this call to a Route List …

55


Emergency Routing Example With LRG Using EMCC SIP Trunk

signal path media path

Visiting Cluster (UK) Home Cluster (RTP)

EMCC SIP Trunk

visiting pstn

vPhone

User dials 9999

This device has Adjunct CSS w/ partition {EMCC emergency partition for UK} I can match the RP: 9.999/{EMCC emergency partition for UK} with route resolved to Standard LRG.

Mmm ... this device is an EMCC device from UK cluster, I am going to route this call to UK cluster via the configured EMCC SIP Trunk for PSTN Access. (System > EMCC > Intercluster Service Profile)

INVITE (999,device name,...)

Given device name, I can find this device’s LRG and route the call to GWs in the group

DA indicates that 999 call should route to Standard LRG. Because this is EMCC SIP Trunk, I will use calling device’s LRG, not SIP Trunk’s LRG, to route the call.

VC may override the CSS of EMCC SIP Trunk with calling phone’s CSS (System >EMCC > EMCC Configuration > CSS for PSTN Access SIP Trunk)

2

4

3 1

7 6

5

56


EMCC Emergency Calls Considerations

§  Design considerations must be made regarding Calling Party for EMCC emergency calls. ‒ Depending on dial plan configurations, the Calling Party number leaving the

Visiting cluster gateway could be the Home cluster User’s DID.

‒ May have to transform calling number incoming on EMCC SIP Trunk, on Route Patterns, or egress on the Visiting Gateways.

§  When EMCC is deployed with CER, CER must be deployed on all clusters ‒  If one cluster is deployed with CER and another is not, CER will NOT be able to

identify the visiting phone that is registered with another cluster without CER ‒ To accurately route emergency calls, CER is deployed everywhere

57

EMCC Call Admission Control

58


EMCC SIP Trunk and RSVP

§  Placeholder §  A SIP REFER message will be sent to

the Visiting cluster over the EMCC SIP Trunk with information about reserving resources.

§  Device Name included! §  Unified CM Locations-based CAC

is NOT supported with EMCC.

59


DB

ABCD


EMCC Call Flows Phone to Home Cluster Phone with RSVP

TFTP

DB EM

TFTP

EM

ABCD EMCC

ABCD

JC

ABCD

JC


John C

PSTN

ICT

x1002 x2001

EMCC SIP Trunk

IP

x1001

vRSVP hRSVP

Signaling

Media RSVP Reservation

60


EMCC RSVP Agent Request to Visiting Cluster

61


Configure RSVP for EMCC Phones

§  Configure a Location in the Home Cluster, and assign to the EMCC roaming device pool. §  Set RSVP policy for Location pairs in the Home Cluster that include this Location

associated with the EMCC roaming device pool. §  Home Cluster and Visiting Cluster, must have RSVP Agent media resources configured. §  Visiting phone must have an RSVP resource available in the visiting cluster MRGL.

62


Configure RSVP for EMCC Phones (Cont)

§  When allocating RSVP agent, Home Cluster: 1. CUCM recognizes the RSVP agent is for EMCC phone

2. Redirect the request to Visiting Cluster over “RSVP SIP Trunk”

§  Note: When allocating all other media resources, Home Cluster Unified CM will allocate them based on the MRGL configured in Home Cluster EMCC roaming device pool.

§  Note: For more details on RSVP configuration and design, please attend BRKUCC-3099: Advanced RSVP Design and Deployment UC 8.x

63

EMCC Security

64


EMCC Security Bulk Certificate Management

 Cisco Unified OS Administration => Bulk Certificate Management

1)  Export (TFTP, Tomcat, CAPF) The publisher of each cluster must export its certificates to a common SFTP server for the cluster.

2)  Consolidate (TFTP, Tomcat, CAPF) This combines the certificates from all the clusters into a single file on the SFTP server. Only one cluster must perform this step.

3)  Import (TFTP, Tomcat, CAPF) The publisher of each cluster must import the consolidated certificates file.

SFTP Server

65


EMCC Secure URL

Secure: https://x.x.x.x:8443/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#

UnSecure: http://x.x.x.x:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#

Supported phones: 7906, 7911, 7921, 7925, 7931, 7941, 7961, 7970, 7971, 7942, 7945, 7962, 7965, 7975, 8961, 9951, 9971 If the device does not support HTTPS, non-secure version of URL used

66


EMCC Secure Device Registration

§  If both home and visiting clusters are on 9.0 or later release:

9.0 Visiting Cluster Visiting Phone

9.0 Home Cluster

Mixed Mode Non-secure Mode

Mixed Mode Secure Secure EMCC Fail Login

Non-secure Non-secure EMCC Non-secure EMCC

Non-secure Mode Non-secure Non-secure EMCC Non-secure EMCC

67


EMCC Secure Device Registration

§  If either home clusters or visiting cluster is on 8.x release, then EMCC will be non-secure :


9.0 Home Cluster


Mixed Mode Secure Not supported Not supported




8.0 Home Cluster


Mixed Mode Secure Fail Login Fail Login



68


Security By Default (SBD) & Trust Verification Service (TVS)

§  Automatic phone security features ‒ Signing of phone configuration files

‒ Phone configuration file encryption ‒ HTTPS with Tomcat and other Web services (Midlets)

§  Trust Verification Service (TVS) runs on each CUCM server and authenticates certificates on behalf of the phone (ITL File)

§  Instead of downloading all the trusted certificates, phones need only to trust TVS (TVS will validate HC certs for Visiting phone)

69


DB

ABCD


EMCC Secure Communications

TFTP

DB EM

TFTP

EM

0xABCD

ABCD


Protocol, Model,


EMCC

ABCD

JC

John C

ABCD

JC

Communication between Home and Visiting cluster EM nodes via HTTPS (port 8443)

70


EMCC Security Option

§  Don’t forget about “Validate IP Address” & “Allow Proxy” options added in 7.x.

71


72



§  Total number of EMCC logins controlled via BAT ‒  number of device templates inserted

§  Users must be unique across all clusters. If DirSync pulling in common users for multiple clusters, must apply some type of filtering.

§  If H323/SIP gateways are only setup for G711, but EMCC phones coming across now as G729 – must add multiple codec capability to dial-peers (or use transcoders).

§  Calling number for Emergency Calls leaving Visiting gateways may potentially have a Home cluster DID.

§  Calls sent across the EMCC SIP Trunk will have gone through digit manipulation. Called number may require manipulation to match Visiting cluster route patterns

§  WAN Bandwidth must be over-provisioned if not using RSVP CAC

73


Other Supported Features in EMCC

§  Consider the delays between the clusters in combination with the features you plan to use. Not all applications/features have been tested with delays – User Experience may vary.

§  CTI control of visiting phone o  In CUCM 7.x and earlier, CTI control is based on static assignment of devices to a user

o  In CUCM 8.x and later, CTI device assignment can be dynamic. Device Profile login triggers CTI to control device

§  EMCC does not allow Hlog functionality (fixed in 8.5(1) and later).

§  Phone firmware version is not sent in xml config from home cluster o  Prevents phones from having to download new firmware images

§  Home Cluster Locales supported if Visiting Cluster has locale files in TFTP server.

74

EMCC Device Status and Monitoring

75


EMCC Active/Remote Login Summary §  In the user’s Home Cluster, the administrator can view a list of cluster users who

have logged in from remote devices. §  DEVICE ► PHONE ‒  Under Related Links choose “Remotely Logged In Device”

§ Note: “Actively Logged In Device Report” will provide the list of devices logged in via Intra-cluster EM and in addition, devices that are currently registered with Remote Clusters (due to EMCC).

76


EMCC Cisco Unified Reporting EM System Report

§  In Cisco Unified Reporting, choose the “Unified CM EM” system report.

77


EMCC Error Code – EMApp Error Code

Phone Display Quick Description

Description

201 Please try to login again (201)

Authentication Error

If the user is an EMCC user, this error can occur if “EMCC” is not activated in the Inter-cluster Service Profile page.

208 Login is Unavailable (208) Logout is Unavailable (208)

EMService Connection Error

1. Visiting EMApp could not connect to any Visiting EMService. (service down or not activated) 2. Visiting EMService could not connect to Home EMService (WAN down or Certificates not trusted)

211 Login is unavailable(211) Logout is unavailable(211)

EMCC Not Activated

Occurs when PSTN is not activated in the inter-cluster service profile page of the visiting cluster

212 Login is unavailable(212) Cluster ID is invalid

Occurs when a remote cluster updated (keep-alive) fails by sending an incorrect Cluster ID to remote cluster


Device does not support EMCC

Occurs when a device (phone load) does not have EMCC capability (for e.g. Legacy Phones, TNP phones with older phone load)

78


EMCC Error Code – EMService Error Code


Description


User does not exist

Occurs when the given user ID is not found (in any of the remote cluster).


EMCC Not Activated for the user

Occurs when “Enable EMCC” check box is not checked in the End User page of the home cluster.


Device does not support EMCC

Occurs when a device model does not have EMCC capability (for e.g. Legacy Phones)


No free EMCC dummy device

Occurs when all the EMCC Dummy Devices are in use by other EMCC logins.


Visiting Cluster Information is not present in Home Cluster

Occurs when the home cluster does not have an entry for this visiting cluster.


No Remote Cluster

Occurs when the administrator has not added any Remote Cluster.

79


EMCC Error Code – EMService (Contd…) Error Code


Description


Duplicate Device Name

Occurs when the same device name exists in both home cluster and visiting cluster.


EMCC Not Allowed

Occurs when home cluster does not want to allow EMCC login (“Enable EMCC” check box is not checked in the home cluster).


Invalid ClusterID Occurs when the remote cluster ID is not valid (happens during Remote Cluster Update)

80


EMCC Performance Counters (RTMT)

81


HTTPS for EM Services: New Alarm

§  Cisco Unified Serviceability ► Alarm ►Definitions §  EM alarms are now categorized into “EMAlarmCatalog” in the ”System Alarm

Catalog” §  New “NodeNotTrusted” indicates the communication with another node failed

because certificate untrusted

82

EMCC Configuration

83


At this point, intracluster EM is configured

EMCC Configuration Tasks

1)  Activate EM Service “Cisco EM Application” network service handles logins – enabled by default. Enable the “Cisco EM” feature service on select nodes

2)  Configure EM Phone Service http://10.80.1.101:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC# https://10.80.1.101:8443/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#

3)  Configure Device Profiles New field “EM Cross Cluster CSS”

4)  Associate Device Profile with End User Select “Enable EM Cross Cluster”

5)  Enable phones for EM

84


EMCC Deployment Tasks New EMCC Configuration

6)  Bulk Certificate Management Process to export, consolidate, import each clusters tomcat, tftp and CAPF certs

7)  Add EMCC devices via BAT -Create EMCC specific Common Device Configuration and Common Phone Profile -Create an ‘EMCC Template’ -Update EMCC Devices to set ‘Default EMCC Template’ -Insert EMCC Devices (Remember: this is where we limit number of EMCC devices)

8)  Configure Enterprise Parameters, Geolocations, & Geolocation Filters

9)  Configure EMCC Feature Configuration Parameters

10)  Configure an EMCC SIP Trunk

11)  Configure Intercluser Service Profile and Remote Clusters

12)  At this point, deployment specific aspects are configured - CSS, MRGLs and Device Pools (for roaming EMCC devices) …

85


Key Takeaways

§ The key takeaways of this presentation are: ‒ Understand the basic operation of EMCC ‒ Understand EMCC-related configuration ‒ Know limitations and supported features ‒ Able to describe EMCC call flows ‒ Understand EMCC Emergency calling

86


Additional Resources

§  You can find additional information about the topics and products covered in this session at the following links:

CUCM Features and Services Guide for Release 8.5(1)

CUCM 8.5(1) Release Notes

CUCM SRND for 8.x

Geolocations and Location Conveyance

Extension Mobility Phone Behavior (EMCC Failure)

87

Q & A

88


Complete Your Online Session Evaluation §  Give us your feedback and you could

win fabulous prizes. Winners announced daily.

§  Receive 20 Passport points for each session evaluation you complete.

§  Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center.

Don’t forget to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the year. Activate your account at the Cisco booth in the World of Solutions or visit www.ciscolive.com.

89


Final Thoughts

§  Get hands-on experience with the Walk-in Labs located in World of Solutions, booth 1042

§  Come see demos of many key solutions and products in the main Cisco booth 2924

§  Visit www.ciscoLive365.com after the event for updated PDFs, on-demand session videos, networking, and more!

§  Follow Cisco Live! using social media: ‒ Facebook: https://www.facebook.com/ciscoliveus ‒ Twitter: https://twitter.com/#!/CiscoLive

‒ LinkedIn Group: http://linkd.in/CiscoLI

90


Thank You

91

Appendix A EMCC Phone Behavior During Failure

93


EMCC Login Failure – Configuration File Unavailable Phone Reregisters with Visiting Cluster

Visiting CM DB

Visiting TFTP

Home CM DB

Visiting phone

Home TFTP

Visiting CM cluster

Home CM cluster

L

Visiting DHCP

GET GET

x

logout

Visiting EM

Modify device record

Phone’s config in visiting. Original

any failure: DNS, TFTP Timeout, TFTP File-not-found, etc.

94


EMCC Login Failure – Registration Rejection Phone Reregisters with Visiting Cluster

Visiting CM DB

Visiting TFTP

Home CM DB

Visiting phone

Home TFTP

Visiting CM cluster Home CM cluster

L

Visiting DHCP

GET

Registration Rejection


logout

Visiting EM


95


EMCC Login Failure – Home CUCMs Unavailable Phone Reregisters with Visiting Cluster

Visiting CM DB

Visiting TFTP

Home CM DB

Visiting phone

Home TFTP


L

Visiting DHCP

GET


logout

Visiting EM


x All Visiting CUMC Unavailable

96


Home CUCM Unavailable/Interoffice Failure Phone Fails-Over to SRST

Visiting CM DB

Visiting TFTP

Home CM DB

Visiting phone

Home TFTP


L

L

L

Visiting cluster’s load

Phone’s config in visiting vCCM list, AltTFTP = hTFTP, SRST=vSRST

Home cluster’s load

Phone’s config in home with user settings hCCM list, AltTFTP=hTFTP, SRST=vSRST

Visiting SRST

L

Visiting EM

Connectivity Check


x

97


Home CUCM Unavailable/Inter-Cluster Failure Phone Reregisters with Visiting Cluster

Visiting CM DB

Visiting TFTP

Home CM DB

Visiting phone

Home TFTP


L

L

Home cluster’s load

Phone’s config in home with user settings hCCM list, AltTFTP=hTFTP, SRST=vSRST

Visiting SRST

L

Visiting EM

1. Connectivity Check


2.a. Modify device record

2. logout


98


Home CUCM Unavailable/Inter-Cluster Failure Phone Reregisters with Visiting Cluster (No Visiting SRST Case)

Visiting CM DB

Visiting TFTP

Home CM DB

Visiting phone

Home TFTP


Visiting EM

logout

x

All Visiting CUMC Unavailable



GET

99

extension mobility cross cluster...

Documents