Integrating and migrating video with Unified CM and VCS · 2013. 10. 25. · • Update endpoint versions (89xx, 99xx, touch 12” support URI dialing) • Update video endpoint version

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 1

Integrating and migrating video with Unified CM and VCS

Lasse Melbye Collaboration SE

Per Toft Collaboration CSE

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2

The Cisco products, service or features identified in this document may not yet be available or may not be available in all areas and may be subject to change without notice. Consult your local Cisco business contact for information on the products or services available in your area. You can find additional information via Cisco’s World Wide Web server at http://www.cisco.com. Actual performance and environmental costs of Cisco products will vary depending on individual customer configurations and conditions.


•  The session will provide a guidance for considerations to register video endpoints, whether to the Unified CM or the VCS. It will provide recommendations for the same.

•  If customers have made a decision to migrate video endpoints to register to the Unified CM, the session will outline the steps needed to achieve the migration

•  The session will also discuss basic Licensing needs needed for a successful migration


•  Unified CM and VCS call routing

•  Endpoint deployments CUCM VCS

•  Migration user dial plan directory Registration license

•  Best practices



Call control

Ext

erna

l A

pplic

atio

ns

End

poin

ts

Unified CM

3rd Party Video Endpoints

MCU’s, TS

Video Communication Server (VCS)

Jabber, 99xx

Ad-hoc Conf

TX, CTS Series MXP, T, Profile Series

VCS-E H.320 GW’s

SCCP H.323 SIP

EX, MX C-Series

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 7 7

•  Mapping between DN and URI

•  Unified CM DN now maps upto 5 URIs

•  Allow for multiple URIs under one primary

•  Primary URI can be synced directly from LDAP in Unified CM

Primary URI

Mobile Jabber ID

Office device Email ID

Primary DN


•  Mapping between URI and DN

•  Allow for multiple URIs under one primary ID

•  Allows single user to have more that one device

•  Its a VCS feature

Jabber URI

FindMe ID

Email ID

Office device

Jabber tablet URI


•  Shared line •  Simultaneous ring to all devices

associated with that DN •  Hold on one and resume on other device •  Support for EX, SX, MX, C and profile

series along with other Cisco IP phones •  Remote destination •  To provide simultaneous ring for Jabber

(movi) URI •  To route calls to endpoints that register

with device specific URI

DN

EX90 Jabber

MX300

Jabber (movi)

Unified CM


Is RHS the IP address of a cluster

member?

Does RHS match

CFQDN?

Does RHS match OTLD?

Match RHS against SIP

route pattern?

Route or block

Does LHS find a match?

No

Yes

No

Yes

No

Yes No

Yes

Is LHS a DN? Does whole URI match one

in the CSS and URI table?

Does whole URI match one in ILS?

Match RHS against SIP

route pattern? Route or

block

Route using SIP route patterns based on routing string provided by ILS Offer call

No

Yes No

Yes

No

Yes No match Route/block based

on existing DN rules


Simplified Routing Process Transforms

Transform: (\d{4})

Transform: (\d+)@1.1.1.1

1

2

Transforms: preliminary

manipulation of dialed string

based on pattern

Search Rules Zones RegEx:

(\d+)@cisco.com

AnyAlias

1

2 3

Local Zone

Neighbor Zone 1

81234

[email protected]

[email protected]

RegEx: (.*)@.+

Search Rules: match based on pattern and route call to a

destination Zone. Optional manipulation of

dialed string

alias matches

transform? Apply

transform

alias matches search rule?

alias found?

‘continue’ configured?

Yes

VCS receives alias

Yes

No

Yes

Place Call

No Yes

No

Next lower-priority rule

alias matches FindMe?

Yes



•  Registration •  Native registration to CUCM •  TC 6.2 supports endpoint registration redundancy •  Common configuration and management as CUCM

phone device with support for MIC and signed images and signed configuration files

•  Image upgrades through CUCM •  Common profile with Device pool and MRGLs •  Support for Ad-hoc conferencing using CUCM as well

as multisite. •  Endpoint Admin Lockout with password


•  Dial Plan •  Shared line with other phones for the DN •  URI dialing •  Flat address book from the Unified CM •  URI Address displayed on endpoint

(Added in UCM 10)


•  Call bandwidth •  Endpoint bandwidth policy controlled through the

CUCM •  Common CAC through locations or thorough

RSVP agents •  Supplementary calls follow CUCM policies •  Downspeed on call setup to voice only •  Conference calls for Multisite feature or CUCM

ad-hoc feature are similar


•  Applications •  CTI support for use with Contact center

applications Skill based routing of Videocalls •  Click to call from Jabber soft clients •  Support for voicemail and MWI •  Meeting/Calendar support for TMS one button to

push, No change from VCS


•  Limitations •  Extensive changes to configuration such as adjusting

gain, camera source etc. cannot be configured through the CUCM

•  No call preservation •  No retry video call at lower bandwidth, CUCM retries call

as audio


•  URI registration •  Jabber (Movi) registration •  Phone books through TMS •  Endpoint templates for configuration and

monitoring using TMS •  Endpoint management with TMS •  Support early offer for calls •  SIP Proxy function for 3rd party devices •  H.323 protocol •  Minimize interworking and license costs


VCS-C

Endpoints registered on CUCM gain the following key features and benefits: Single Pt. of Dial Plan Administration Single Call Admission Control Domain CUCM Phones features : Voice Mail indicator /Call Forward All /Consultative Transfer Shared Lines /SNR /Ad Hoc conferencing/CTI Control/BLF CSS/Partitions /Hunt Groups/ Music on Hold/ Announcements

Register Endpoints on VCS if you require : US DoD certification Fine Control of Endpoint Features (Room Systems) Release Key Management


VCS-C Unified CM

Keep Endpoints on VCS if you require : TMS Management Tiered phonebooks ACL’s for phonebooks US DoD certification H323 and 3rd Party Endpoint registration Downspeeding/ MOVI Clients Zone /Sub-Zone Encryption

Endpoints registered on CUCM gain the following key features and benefits: Single Pt. of Administration for Dial Plan Single Call Admission Control Domain CUCM Phones features : Voice Mail indicator /Call Forward All /Consultative Transfer Shared Lines /SNR /Ad Hoc conferencing/CTI Control/BLF CSS/Partitions /Hunt Groups/ Music on Hold/ Announcements


•  Register new endpoints to Unified CM with UCM 10.0 •  If VCS is already used for video endpoint registration,

then register to VCS •  If Unified CM is already used to register video endpoints,

then register to Unified CM •  VCS and VCS Expressway for Jabber (movi) registration •  Address books can be through Unified CM-UDS or

through TMS •  Register video endpoints to minimize call interworking •  Register video endpoints to optimize media path •  Consider endpoints features to choose where to register



Scenarios Unified CM VCS-C

•  Endpoints •  EX series, MX series, SX series, C series, Profile series •  H.323 to SIP

•  MCUs •  H.323 to SIP


•  Update server versions (10.0 support URI dialing) •  Update endpoint versions (89xx, 99xx, touch 12” support URI dialing) •  Update video endpoint version •  Identify endpoint numbers and alias •  Sync LDAP users from AD into UDS or add as end users •  Map the URIs in the DN •  Use BAT tool to do bulk import of endpoints to UCM •  Move FindMe to Shared line in CUCM •  Configure SIP registration or enable CDP on the endpoint •  If needed change the Endpoints provisioning mode to CUCM in TMS if endpoint is provisioned •  Phone books and directory


•  Devices •  Identify video devices •  Group them into a subzone in the VCS

•  URI •  Identify the URIs that are to be migrated •  Delete the URI entries from the ILS catalog

•  DNs •  Update the Unified CM route patterns that point

to the VCS


•  Associate user with device •  Update the Primary DN in the end user

configuration •  In DN configure the alias for the user •  Use BAT tool to configure the phones into the

Unified CM •  Enable SNR functionality if needed •  Configure remote destination for Jabber

(movi) URI on the VCS / VCS expressway. This ensures simultaneous ring for this device


•  Upgrade video endpoints software to version desired •  Update the release key and option keys* •  If Protocol is changed from H.323 to SIP, then update protocol configuration and default call protocol configuration •  Access the endpoint using browser or SSH and change the provisioning mode and the Vlan mode to auto. This enables CDP and uses option 150 to register with the Unified CM •  If setting VLAN is not possible, then configure SIP information and configure Unified CM as registrar

*note release key will not be needed in the future on CUCM


Call agent and Endpoints

Unified CM VCS

TX Series

EX, MX C-Series

SME

EX, MX C-Series

Call routing based on Alias and URIs

Call routing based on DN

and ILS

Dials URI or Phone book directories Dials DN or Phone

book directories

Dials URIs or Phone book directories

•  Unified CM sends DN@<domain> •  Video endpoints send URI (user@domain) •  Unified CM version 8.6 or earlier need ways to

resolve user@domain URI


Unified CM 8.6 and later with VCS for URI to DN translation

Unified CM VC

S

TX Series

Number range 55000 - 59599

URI [email protected]

EX, MX C-Series

SME •  Endpoints dial URI, but the

call agent (UCM 8.5 and earlier) cannot terminate calls with URI

•  Uses FindMe in VCS •  VCS forwards call back and

is no longer in call path •  Dedicated VCS for

translation for large number of DNs

•  Enum or CPL can also be used for this purpose

[email protected]

[email protected]

[email protected]

[email protected]

FindMe URI [email protected] 56000

56000

56000


•  Directory synchronized with LDAP •  User Data Service (UDS) provides phone directory for

Unified CM registered endpoints •  UDS supports blended addresses, that send DN and

URI information to display and use for history and redial/missed call lists

•  Address book is automatically configured for C-series endpoints and points to UDS

•  TMS supports Unified CM directory for phone books •  VCS endpoints have phone books through TMS

30


Unified CM VCS

TX Series

C, Profile Series

MCU

EX, MX C-Series

SME

[email protected]

[email protected]

Users meeting URI

•  Rendezvous •  VCS Search rule to CUCM for Multiway numbers •  Configure route pattern on CUCM for Multiway numbers •  ILS import for user allocated bridges into CUCM/SME •  Move registration of the MCUs to the CUCM/Conductor

•  Scheduled conferences •  Map DN to Alias conferences

ILS import

MCU



What is the Converged Call Control Investment Protection Plan?

The Converged Call Control Investment Protection plan is a strategic initiative

by Cisco that provides Cisco TelePresence VCS Control and Cisco Unified

Communications Manager customers the maximum level of investment

protection, reassurance, and flexibility in converging their TelePresence Call

Control to UCM.

•  The plan is available until 10/25/2013


•  You must have made an investment in VCS, specifically in non-traversal calls

•  This means that participants in the plan, must maintain a device registration to non-traversal call ratio of 10:1 for TelePresence endpoints and 5:1 for Jabber Video (Movi) clients. The customer must have purchased the non-traversal licenses that are deployed on VCS Control.

•  UCSS Required •  Although there will be $0 charge for the UCM licenses, the

customer will be required to purchase necessary UCSS for each device migrated


Device Type Migrating to Unified CM

Required Ratio of Devices to Non-traversal Calls Purchased

for VCS Control to Qualify Telepresence Endpoints (EX, MX, SX, etc.) 10:1

Jabber Video (Movi) 5:1


Examples

•  If a customer wants to migrate 100 TelePresence endpoints from their VCS Control to Unified CM, it is required that the customer has purchased at least 10 non-traversal calls for their VCS Control

•  If a customer wants to migrate 100 Jabber Video for TelePresence clients from their VCS Control to UCM, it is required that the customer has purchased at least 20 non-traversal calls for their VCS Control


Benefits •  Ensuring future and ongoing flexibility between VCS and Unified

CM 8.6+ allowing the customer flexibility to remove the barriers to transition to Unified CM.

•  Provide continued support for VCS as a TelePresence centric application, supporting Firewall traversal, H323 and 3.party registration.


•  Greenfield deployments use Unified CM for endpoint registration

•  Standardize to SIP protocol

•  Use VCS registration for scenarios and features desired

•  Endpoint registration decision dependent on features needed

•  Update software versions for servers and endpoints

•  Migrate dial plan first

•  Migrate supporting services and then the endpoint

•  Migrate licenses to Unified CM

Thank you.

Documents

Integrating and migrating video with Unified CM and VCS · 2013. 10. 25. · • Update endpoint versions (89xx, 99xx, touch 12” support URI dialing) • Update video endpoint version