telepresence/video: integrating cucm and...

Telepresence/Video: Integrating CUCM and VCS BRKEVT-2811

Mike Dybka - Network Consulting Engineer

© 2013 Cisco and/or its affiliates. All rights reserved. BRKEVT-2811 Cisco Public

Telepresence Architecture Overview

3

Campus

Branch

Conferencing Call Control

Endpoints

Scheduling

And

Management

Monitoring Recording

and

Streaming

Endpoints Conferencing

WAN

Internet Global B2B Inter-

Network

External Connections

Mobile Office


Overall Architecture

4

Cisco

Unified Call Control

CUCM VCS

B2B

&

Remote Workers

webex Cisco

VCS

Expressway

VCS

Expressway

H.323

&

Third Party

Immersive

Multipurpose

Personal

CTS Manager TMS


Immersive Endpoints - TX9000, TX9200, TX1300 Series

5

Models TX 9000, TX9200, TX1300

• Newest generation of immersive rooms.

• Best of breed features from T3 and CTS

• Incorporate Touch 12 interface

• 60 FPS optimized hardware

• CUCM based only

• Replaces previous CTS series


Multipurpose Endpoints

6

MX Series, Profile 65 Series, C series

• Oriented for rooms used for multiple purpose.

• Smaller footprint than Immersive, no integrated furniture.

• MX200, MX300

• Profile 65, Profile 65 Dual

• C Series


Personal Telepresence Endpoints

7

• EX 60 and EX90

• Cisco Jabber Video for Telepresence

Case Study 1 – Established VCS Implementation

8


Internet/Extranet

VCS Infrastructure – Reference Environment

Expressway

Cluster

TMS

Control

Cluster

TS / MCU’s

Resource Pool A Resource Pool B

Conference Conductor

CUCM

Cluster

1. Exchange

2. Lotus

3. Scheduling API

9

EX / MXP/ C series/ Movi / 3rd

party Endpoints


Endpoint Support

10

Endpoint Model Cisco UCM Cisco VCS

CTS Series (3K/1K/500) Yes No

TX9000 Series Yes No

TX1300 Series Yes No

T-series (T1/T3) No Yes

MX Series Yes Yes

Profile Series/C Series Yes Yes

EX Series Yes Yes

MXP Series No Yes

99xx Series Yes No

Jabber Video for Telepresence (Movi) No Yes

Jabber for Window Yes No

Jabber for iPAD Yes Yes

CUPC Yes No


Migration Considerations – Endpoint view

Unique endpoint considerations in VCS environment:

Third party or H.323 endpoint support is needed

Existing PBX in place

Endpoints with lack of CUCM support in place: T3, MXP.

Jabber Video investment in place.

Video only deployment, and no Immersive.

11


Provisioning on VCS with TMS

12

Direct TMS Management

• C Series, Profile Series

• Devices register to VCS

control and HTTP

connection to TMS server.

• Systems appear in system

navigator

• Model is endpoint based.

• TMS 13.2 : 2000 Devices

• TMS 14.1 : 5000 Devices

Provisioning Agent / Provisioning Extension

Jabber Video, E20, EX, MX series

Distributed architecture

Devices only register to VCS

Designing for managing large scales of

endpoints.

Model is user based, with either local or AD

login possible.

Provides Phonebook provisioning through

VCS.

TMS Scales to 100K users (14.1

recommended)


Provisioning Agent/Provisioning Extension

Provisioning agent first introduced in 12.6

Provisioning extension first supported in 13.2 as a separate installation. Provides better scalability and performance compared to Agent.

Provisioning agent no longer exists in 14.1, utilizes Provisioning Extension.

Highly recommended to utilize PE, minimum code 13.2.

13

Device Model Provisioning Model

C20,C40,C60,C90

C codec based Profile Series

Direct management

E20 TE 4.1.1+

EX60, EX90 TC 5.1 +

Jabber Video(Movi) 4.3 +

TMS Provisioning Extension 1.0

TMS 13.2 +


TMS

VCS Cluster

with PE or TMS Agent

2 – TMS Agent /PE replicates

the provisioning data to the

cluster

3

• VCS challenges user for

credentials.

• When authenticated, endpoint

receives provisioning profile by

SIP Notify Message.

• Endpoint registers to a VCS per

the provisioning profile.

• Endpoint subscribes to VCS for

Directory services.

4 – Success! endpoint is

ready for SIP or H.323 calls

1 –Administrator imports users

from AD and creates

provisioning profiles.

AD

Administrator

SMTP Server

User

2 TMS emails user the

account credentials

Automated Provisioning with VCS & TMS

Endpoint

14


TMS

Control

Cluster

1. Subscribe

message to

Expressway

AD

Administrator

SMTP Server

Provisioning Outside the Enterprise

Expressway

Cluster

Mobile Users

Home Users

Remote Office

2. Proxy to Control

for provisioning

15


Provision TelePresence endpoints on VCS/TMS Provisioning of external endpoints

SUBSCRIBE

Regular updates between

TMS Agent and TMS Server

TMS VCS C w/ TMS Agent Endpoint

401 Unauthorized

SUBSCRIBE w/Digest

200 OK

NOTIFY

200 OK

200 OK

REGISTER Register with the server

provided in the NOTIFY

(in this case the VCS

Expressway)

VCS E

SUBSCRIBE

401 Unauthorized

SUBSCRIBE w/Digest

200 OK

NOTIFY

200 OK

16


Provision TelePresence endpoints on VCS/TMS

*It is recommended to use the latest Cisco TMS and Cisco VCS software.

Please note that there is a dependency between the TMS and VCS software version for TMS Agent. Check the TMS and VCS software release notes for details.

The XML provisioning files required by TMS must be uploaded to TMS for the different TelePresence endpoints.

Requirements and considerations

TelePresence endpoints Endpoint Software version TMS version*

Jabber video (Movi) Version 2 or higher 12.6 or higher

E20 TE 2.1 12.6 or higher

EX60 TC 4.1 13 or higher

EX90 TC 4.1 13 or higher

MX200 TC 4.2 13.1

MX300 TC 5.0 13.1

17


Provision TelePresence endpoints on VCS/TMS Creating users

Add users manually

Importing users from

Active Directory

Create a folder

structure to organize

the users

18


Provision TelePresence endpoints on VCS/TMS Configuration settings

Configuration settings

on folder level

Or user specific

configuration settings

19


Provision TelePresence endpoints on VCS/TMS Device templates

Important to upload

DeviceConfiguration

Templates

20


Directly Managed Endpoints

Multipurpose endpoints are not associated to a specific end user

These endpoints are directly managed through TMS.

21

TelePresence Endpoint category TelePresence Endpoint platform

C-Series Based Endpoints (all run same TC software)

C20

C40

C60

C90

Profile 42

Profile 52

Profile 65


Conferencing on VCS – with Conference Conductor

TMS VCS Cluster

Resource Pool A Resource Pool B

Conference Conductor 2.0

1. Exchange

2. Lotus

3. Scheduling API

• MCU’s and TS can be scheduled by TMS directly or via TMS Integration

• Conference Conductor is an optional component.

• Conference conductor may be used for rendezvous or ad-hoc

• CC version 2.0 supports MCU’s and TS

22


TMS Conference Scheduling

23

Automatic connect: Automatically connect all the participants at the specified time.

One Button to Push: Conference dial-in information is provided on endpoints with One Button to Push support.

Manual connect: The system that is the VC-Master will be prompted to begin the call. The call automatically connects when the VC-Master accepts.

No connect: Reserves room(s) and generate the call route. Route will be connected by clicking Connect for the participants in Conference Control Center.

Reservation: Reserves the room(s). No connections are established.

Case Study 2 - CUCM Integrations

24


Stage 1 - Greenfield Immersive Rooms

Expressway

Cluster

TMS

Control

Cluster

TS / MCU’s


CUCM

Cluster

Immersive Endpoints

25

EX / MXP/ C series/ Movi / 3rd

party Endpoints


Stage 2 - CUCM Centric Endpoint Registration

Expressway

Cluster

TMS

Control

Cluster

TS / MCU’s


CUCM

Cluster

Immersive Endpoints

26

Movi / 3rd party Endpoints/

Legacy / H.320 GW

EX / C / Profile


TS / MCU’s

Stage 3 - CUCM Centric

Expressway

Cluster

TMS

Control

Cluster


CUCM

Cluster

Immersive Endpoints

27

Movi / 3rd party Endpoints/

Legacy / H.320 GW

EX / C / Profile

Stage 2 : Endpoints on CUCM

28


First Time Registration to CUCM

29


Migrating endpoints, TMS to CUCM

• If an endpoint is managed by TMS and is being moved to CUCM a factory reset is required first.

• Remove endpoint from TMS

• Disable TMS auto discovery of endpoints

30


Endpoint – Initial CUCM Connection

Upon boot up from factory default state:

(VLAN mode = Off by default)

1. Do an untagged DHCP request, receive an address in the Data VLAN

2. Prompt the user for language choice and provisioning mode

3. CUCM mode selected, set VLAN mode = Auto, restart network stack, and do a tagged DHCP request (with option 150)

to receive a new address in the Aux VLAN

4. If DHCP Option 150 in Aux VLAN DHCP Offer is present, proceed to step 5. Otherwise prompt user for CUCM TFTP server address

5. Download configuration and firmware from CUCM via HTTP port 6970.upgrade firmware and reboot if necessary, and proceed to register with UC Manager

31


Call Settings

If CTMS is used, set the Default Call Rate to 2500 or better

Auto Answer must be manually set

Default Call Protocol will be set automatically to SIP when provisioning mode is set to CUCM.

Only SIP is supported.

32


CDP CDP

CDP

TFTP HTTP on port 6970

SIP

SIP

XML

No 802.1Q VLAN tag Tagged with 802.1Q ID of Voice VLAN

Shared Line

802.3af

DHCP DHCP

XML

Changes to CTS Provision CTS endpoints on CUCM

Cisco 7975G IP Phone

Access-Edge Switch

Cisco Unified CallManager

Cisco TelePresence

Manager

LAN / WAN

TelePresence Primary Codec

33

Image push

Codec Registration


Add endpoint to CUCM

CTS 1300-47 and 500-32 introduced in UCM 8.5(1)

Also back ported to 7.1(5) and 8.0(3)

E20 introduced in UCM 8.5(1)

Additional enhancements in 8.6(1) and 8.6(2)

TX , EX and C-Series introduced in UCM 8.6(1)

MX200 and Profile 42 (C40) support introduced in 8.6(2) and also available in latest 8.6(1) device pack

34


Phone Configuration - High Level - CUCM

1. Set CUCM for auto registration or explicitly configure by entering phone MAC

2. Set up a SIP profile for these endpoints,

Copy default SIP profile

Enable Redirect by Application for call forward all

Set SDP Session level Bandwidth Modifier for Early Offer and Re-invites to TIAS and AS

Enable Use Fully Qualified Domain Name in SIP Request

Enable , Allow Presentation Sharing using BFCP

3. Assign this SIP profile to the endpoint

35


Phone Configuration - High Level – CUCM

4. Set the organizational top level domain , e.g. cisco.com

System > Enterprise parameters::Clusterwide Domain Configuration

4. Configure regions and locations

5. Set Calling search spaces, partitions, and presence permissions

6. Set NTP reference

Continued

36

Stage 2 or Stage 3: Conferencing Resources

37


Telepresence Components

Call Control

Cisco

TelePresence Conductor

MCU Resource Pool

MCU 4200 Series

MCU 4500 Series

TelePresence Server

MSE 8420 SD MCU

MSE 8510 HD MCU

Management

Endpoints

Telepresence Resource Pool

MCU 5300 Series

38


Conferencing for Integrated Environments

39

Telepresence

Server MCU

MSE Chassis

Based

Standalone

8420

4501,/05/10/15/20

4203/05/10/15/20

8710

7010

8510

5310/20


Telepresence Server 3.0 Adaptive resource allocation

Full HD HD SD

Conductor allocates

appropriate TS

resources for each

end-point

All end-points

consume Full HD

resource, even SD

end-point

Maximizes capacity for

more conference

attendees to join

Once full,

additional

endpoints cannot

join

With Conductor 2.0 +

TelePresence Server 3.0 Without Conductor

40


MCU Scaling

41

Model Mode Video

Ports

Audio-

only

ports

Ports

activated

per LIC-

5300-4PL

MCU 5310 nHD 24 0 8

SD 20 0 4

HD 10 10 2

Full HD 5 5 1

Sinlge

MCU 5320

Single

8510

nHD 48 0 8

SD 40 0 4

HD 20 20 2

Full HD 10 10 1

HD : Up to 720p30, or w448p60

Full HD :Up to 1080p30 or 720p60

SD : Up to w448p30

nHD : Up to w360p30


Conference Types

42

Ad Hoc Point-to-point escalation to multipoint call.

• CUCM: MRG/MRGL with Conf / Join Softkey features.

• VCS: Multi-way (Add / Join) feature . Endpoint escalates to an MCU registered

to VCS.

• VCS Multi-site (Add / Join) feature. Endpoint has embedded 4-port MCU

Rendezvous • Participants dial into the meeting at a pre-arranged time by dialing a pre-

determined number or URI.

• Bridge ports pre-allocated or spontaneously allocated at meeting start

Scheduled • Setup in advance by scheduling/management server that has integration with

the enterprise calendaring application server

• Conference resources are managed and automatically scheduled, reserved and

guaranteed to be available at the start of the meeting.

• Manually or OBTP dialing into bridge, bridge may also dial out to the

participants


Conference Resource Placement

43

UC Manager

VCS Control VCS Expressway

Internet

Rendezvous MCU

CTMS

TS

Ad hoc

MCU

TS MCU

Rendezvous

Ad hoc

MCU

Conductor

Scheduled

MCU

TS

TMS

Scheduled MCU

CTMS

TS

CTS Manager


UCM configuration – Ad Hoc

44

1. Add Conference Bridge

2. Add Conference Bridge To MRG

3. Add MRG to MRGL

4. Add MRGL to Device Pool


UCM configuration – Rendezvous with Conductor

45

1. Add SIP trunk to the Bridge

4. Add Route List for this Route Pattern

3. Add Add Route Groups to Route List

2. Add trunk to Route Group


TMS Scheduling and Management

46

TMS 14.1+

CUCM 9.0+

CTS 6.0+ TC6.0+

• TMS support for CTS and TX systems :

• Endpoint system information

• Endpoint and call status monitoring

• Dialing from endpoint

• Scheduled P2P calls

• One Button to Push

• Allows booking with MCU and TS systems, with resources on VCS.

• C/EX/MX/SX series registered to CUCM can be scheduled via TMS.

• OBTP on any Touch, 797x, and OSD

Version recommendation is based on maximizing feature/functionality across platforms. These are the minimums for functionality described in this presentation..

Earlier versions may be acceptable , yet with diminished capabilities . See slide notes

Dial Plan and Trunking

47


URI Support on CUCM 9.0

48

Uniform Resource Identifier (URI) is a string of characters used to identify a name or a resource, email style.

All VCS versions support URI and E.164 dialing.

On CUCM :

End-points register to CUCM using the DN, making DN@DOMAIN the main end-point URI

URIs are aliases for directory numbers. Call to the URI behaves like calls dialed to the DN.

URI example

[email protected]

E.164 example

9195552103


CUCM 9.0 URI Configuration

49

•On the DN configuration page, in the URI section. Maximum of 5 URI’s associated to a DN

•

Cisco Unified CM Administration->Device->Phone-><DEVICE>->Line [x]

[email protected] Case

Sensitive


CUCM

VCS

Dialplan Interworking - VCS to CUCM

Neighbor

Zone

Peer 1

Peer 2

Peer 3

SIP

Trunks

Search Rule

[email protected]

Replace video.domain with IP address.

Transform Rule

dn@IP Address

to

[email protected]

Cluster FQDN :

“video.domain”

3XXX 4XXX

50

Call routing mode : Always

mailto:[email protected]


CUCM

VCS

Dialplan Interworking - CUCM to VCS

Local Zone:

Endpoints [email protected]

Search Rule

Suffix :@video.domain

Transform Rule

dn@<cluster FQDN>

to

[email protected]

SIP Trunk:

Destination 1

Destination 2

Destination 3

SIP

Trunks

Route Pattern:

4xxx

Route

Pattern:

[email protected]

51

4XXX 3XXX

mailto:[email protected]


CUCM SIP Settings

52

SIP Profile Redirect by Application : Checked

Use Fully Qualified Domain in SIP Requests : Checked

Allow Presentation Sharing Using BFCP : Checked.

SIP Trunk Security Profile

Secured and Not Secure:

Accept Unsolicited Notification : Checked

Accept Replaces Header : Checked

Secured: Device Security Mode : Encrypted

Incoming/Outgoing Transports : TLS

X.509 Subject Name : Match certificate

Incoming port : 5061

Change the following when starting with a default profile:


CUCM Service Parameters

53

SIP max Incoming Message Size


Encryption – CUCM 8.6 , TE/C 6

54

ANY VERSION Up to TE/TC 5.1

VCS

E20, EX, MX, SX and C-Series on CUCM 8.6(2) or higher will be able to establish secure calls

TLS/sRTP No encryption

From TE/TC 6.0

TLS/sRTP

CUCM


Encryption - On Screen Status

Main Benefit A consistent encryption behaviour on all CUCM Registered Endpoints

Personal TelePresence Encryption is shown on the Touch UI

Room TelePresence Encryption is showed on the screen (OSD)

Photo needed

55


CUCM1

CUCM2

CAPF

TFTP

etc…

CTL, ITL

CUCM Encryption Mechanism

1. Admin enables CAPF, and CTL provider on CUCM Cluster

2. Admin runs CTL app. CTL is created in CUCM and security mode set to mixed for the cluster

3. CTL, ITL and configuration are downloaded to end-point from TFTP while booting-up. Communication initiated by end-point

4. Each end-point uses CAPF Client to request a LSC from CUCM CAPF –end-point uses self signed certs– *

5. LSC downloaded to each end-point*

6. Secured communication is established between end-point and CUCM over TLS now using the LSC

7. sRTP between end-points is now possible

CUCM1

CUCM2

CAPF

TFTP

etc…

CT

L

CAP

F

CUCM

Windows

Computer

EX90 Profile 65

1

2

4

sRTP

3 6 6 3

7

Note: Configuration encryption and MIC are not

available in TC/TE 6

EX90’s LSC

5 CUCM1

CUCM2

CAPF

TFTP

etc…

CTL, ITL

5

Profile’s LSC

56

Cross Platform Enhancements Unified Experience

57


Touch 12 Interface Common interface across the portfolio

58

Scheduled meetings list Active meeting


Touch Support

59

Touch 8 EX 60, EX90

Profile 42, Profile 55, Profile 65

MX200, MX300

C40,C60, C90

C20, SX20

Touch 12 TX9000, TX9200, TX1310

CTS 3010, CTS 3210

CTS 1300-45, CTS 1300-65

CTS 1100, CTS-32, CTS-37


Retrofitting CTS

60

• Aux Ethernet port of the main codec is used for the Touch

• Minimum code is 1.8.0


Telepresence System Image distribution - CUCM

New release mechanism as of 1.8.0 and later code

Used both for systems that use Cisco Telepresence Touch 12 and Cisco Unified IP Phones

Includes the codec image for the main codec and a loads file

Unlike an IP Phone the Touch 12 is not defined as a separate device in CUCM and does not register.

It has its own code image that is downloaded from CUCM, but the codec utilizes the COP file to determine the image load for the Touch.

Cisco Option Package ( COP)

61


COP File contents

The COP file contains at least :

Codec image file

CTT 12 image file

LOADS file

LOADS file determines the file which the Touch will load.

62

TC6.1 New Features

63


Software Branching

TE6.1

64


1080p60 codec support

TC6 will enable the following codecs with 1080p60

Codec Name 1080p60 support

SX20 Yes

C20 No

C40 No

C60 Yes

C90 Yes

Note: All C90 sold after joint orderability will have support for 1080p60 with TC6

All C60 sold after August 1 2012 will have support for 1080p60 with TC6

The codec’s web interface will provide feedback on if the system supports or not 1080p60

65


Easy to access layout options

Layout - Improved flexibility

66

Predefined layout options. WSIWYG


Press to move overlayed pictures

Easy to..

Layout PIP Control

67


This feature is only supported when hosting a MultiSiteconference

Participants list

Select layout to send to far end

Control of Remote Layout

68


Local Phone Book Management

Add and remove contacts in local phonebook via web

Search in local phonebook (my contacts) via web

Search in corporate phonebook via web

69

TE6 Enhancements


Message Waiting

Indicator and direct

access to VoiceMail

Missed calls indicator

Help desk Bluetooth support

In Audio selection

Call forward

Dial pad for

numeric

dialling

EX Series Interface Refinements

71


1. Pick up a call on mobile 2. Resume call on the EX 3. Automatic escalation to video

Mobility Support

72


Shared Line Support

73

– manager and

administrative assistant

The admin assistant can answer calls on behalf of the manger.

Assisted Call handling

Admins can now fully manage calls and lines for executives using EX Systems


Shared Lines Support

Shared Line on CUCM: Same DN/Partition for two or more devices (DN not unique, “DN + Partition” forms the unique identifier)

Shared Line Appearances

Remote State Notifications

Hold / Resume

cBarge

Unified Mobility

– Hand-off from mobile to desk

74


Call-flows made easy

Consistent Cisco Experience Direct interaction

Consultative Transfer Interaction

Consultative Transfer

75


Unity Voicemail Integration

Endpoints registered to either VCS or UCM call the E20 or EX90 on UCM. Call forwards to voicemail on Busy | No Answer. Endpoint receives MWI notification from Unity and can press the messages button to retrieve its messages

In order to reply to the sender or call-back the sender, sender must have provided its numeric address to Unity. VCS can source re-write the callers URIs to the numeric alias assigned to the users FindMe account only if directly integrated with Unity

UC Manager

VCS Control VCS Expressway

Internet

SIP

H.323

E20

EX90

C-Series / MX200

CTS

Jabbe Video

E20

C-Series / MX200

EX

E20 EX

Jabber Video

Perspective: TTG endpoints registered to UCM and VCS

Unity

76


Voicemail and MWI

The red badge indicates how

many new voicemails you have.

By pressing the voicemail icon a

call is placed directly to your

voicemail.

Voice Mail Interface

77


Unity Voicemail Integration

If Unity is connected to UCM, and a VCS endpoint is diverted to voicemail, VCS must be X7.0 or greater

If Unity is directly integrated with VCS, and a VCS endpoint is diverted to voicemail, VCS must be X6.1 or greater

VCS endpoints must have a numeric address in order to work properly with voicemail

VCS endpoints that only have alpha-numeric URIs can leave messages for people but cannot be replied to or called back from voicemail

78


Review / Conclusion

Key point to select a deployment model are:

Basic support for the desired endpoints. EOL endpoints, Immersive, Jabber Video are examples.

Any remote endpoints - need for VCS-E.

Use cases enabled by shared lines or mobility feature on CUCM.

Scheduled calls

– Are immersive rooms in the mix.

– Is call scheduling required,

– Mixed immersive and non immersive conferences.

What third party, H.323 or eol endpoints need to be supported.

79


Maximize your Cisco Live experience with your

free Cisco Live 365 account. Download session

PDFs, view sessions on-demand and participate in

live activities throughout the year. Click the Enter

Cisco Live 365 button in your Cisco Live portal to

log in.

Complete Your Online Session Evaluation

Give us your feedback and you could win fabulous prizes. Winners announced daily.

Receive 20 Cisco Daily Challenge points for each session evaluation you complete.

Complete your session evaluation online now through either the mobile app or internet kiosk stations.

80

telepresence/video: integrating cucm and...

Documents