Lab 2 - Collaboration Meeting Rooms

7/24/2019 Lab 2 - Collaboration Meeting Rooms

1/34

Lab 2 Collaboration Meeting Rooms:Conferencing in a Cisco pervasive video deployment

Lab written by:

Gabe Moulton Collaboration CSE

[email protected]

Last Updated: August 23, 2014

Overview

The figure above illustrates the key components in a Cisco converged collaboration

architecture. In this lab you will be leveraging the subset of those components

focused around enabling conferencing or Cisco Collaboration Meeting Rooms. (CMR)

Those components are the Telepresence Management Suite (TMS), TelepresenceServer (TPS), Cisco Telepresence Conductor and of course Cisco Unified

Communications Manager (CUCM) all of which can be virtualized.

Telepresence Management Suite provides the scheduling and management for

converged collaboration architecture.

Cisco Telepresence Conductorhelps ensures simple, reliable, and efficient

multiparty rich media conferencing. It simplifies multiparty video communications,

orchestrating the different resources needed for each conference as required.

Telepresence Server provides the bridging capacity to mix together multiple videoendpoints at whatever resolution each endpoint supports while maintaining visual

engagement.

Cisco Unified Communications Manageris the call control quarterback that

routes your collaboration calls, audio or video, seamlessly through the architecture.


2/34

Cisco Collaboration Meeting Rooms

Cisco Collaboration Meeting Rooms provide a highly scalable virtual meeting room

experience that combines industry-leading video, audio and data sharing

technologies to enable seamless video collaboration. CMR can be enabled as a

premise based or cloud based conferencing solution but the focus of this lab is onthe on-premise CMRs. CMR conferences include Personal (meet-me), Instant (ad-

hoc), or a Scheduled conference.

CUCM and Conductor

Conductor removes the hard link between CUCM and a physical rich media resource

allowing for conferences to connect even during a resource outage, or to allow them

to grow beyond the capacity of a single physical resource.

This lab walks you through configuring CUCM for efficient and resilient ad hoc

(instant) and rendezvous (personal) conferences as per the diagram below.


3/34

Figure 1 - CUCM and Conductor

How it works

The diagram below shows call flows for both ad-hoc (instant) and rendezvous(personal) conference.


4/34

Figure 2 - Call Flow


5/34

Section 1 Virtual Telepresence Server

Virtual Telepresence Server is a relatively new way to deploy Cisco Telepresence

Server. It allows you to leverage your compute platform of choice as long as it meets

the specifications outline at:

http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_TelePresence_Server

It is licensed via screen licenses; there is no charge for the VM software itself. These

licenses must be purchased a la carte for scheduled applications or can be obtained

for ad-hoc via CUWL Pro licensing Personal Multiparty feature. Further detail at the

link below:

http://www.cisco.com/c/en/us/solutions/collaboration/pervasive-

conferencing/index.html

Deploying a virtual Telepresence server initially involves selecting an appropriatecompute platform, configuring the host machine, deploying the OVA, and finally

addressing and licensing the TP server. Due to the nature of this lab these initial

steps have been done for you. For further guidance on that process reference the

link below.

Virtual Telepresence Server Install Guide

The Cisco TelePresence Server on Virtual Machine application must operate in

remotely managed mode. It must be administered through the Cisco TelePresence

Conductor XC2.2 (or later), or a similar system.

1)

Navigate tohttp://vtps.collab.comand login

a)

Username:admin

b)

Password:Cisco12345

2) Configure the SIP settings on the TPS

a)

Navigate to ConfigurationSIP Settings

i) Outbound Call Configuration: Use trunk

ii)

Outbound address:10.5.0.80

iii)

Outbound domain:collab.com

iv)

Outbound transport:TLS

v)

Click Apply Changes
http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_TelePresence_Serverhttp://docwiki.cisco.com/wiki/Virtualization_for_Cisco_TelePresence_Serverhttp://www.cisco.com/c/en/us/solutions/collaboration/pervasive-conferencing/index.htmlhttp://www.cisco.com/c/en/us/solutions/collaboration/pervasive-conferencing/index.htmlhttp://www.cisco.com/c/en/us/solutions/collaboration/pervasive-conferencing/index.htmlhttp://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/ts/install_guide/vts_install.pdfhttp://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/ts/install_guide/vts_install.pdfhttp://vtps.collab.com/http://vtps.collab.com/http://vtps.collab.com/http://vtps.collab.com/http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/ts/install_guide/vts_install.pdfhttp://www.cisco.com/c/en/us/solutions/collaboration/pervasive-conferencing/index.htmlhttp://www.cisco.com/c/en/us/solutions/collaboration/pervasive-conferencing/index.htmlhttp://docwiki.cisco.com/wiki/Virtualization_for_Cisco_TelePresence_Server


6/34

Figure 3 vTPS SIP Settings

3) Create a user for conductor to access the TPS

a)

Navigate to UsersAdd new Userb)

Enter the following parameters

i) User ID:conductor

ii)

Password:Cisco12345

iii)Re-Enter password:Cisco12345

iv)

Access rights:Administrator

v) ClickAdd user

c)

Navigate to NetworkServices

i)

Enable HTTPS port 443

ii)

ClickApply changes

Figure 4 - Add Conductor User to TPS


7/34

Figure 5 - Enable HTTPS

Section 2 Configure Conductor

1)

Navigate tohttps://conductor.collab.comand login

a)

Username:admin

b) Password:Cisco12345

2) When CUCM communicates with Conductor it does so through the API via an

authenticated administrative account which we will now create.

a) Navigate to Users Administrator Accounts

b)

Click New

c) Enter the following parameters:

i)

Name:CUCMii)Access Level:Read-write

iii)Password:Cisco12345

iv)

Web Access:No

v) API access:Yes

vi)

State:Enabled
https://conductor.collab.com/https://conductor.collab.com/https://conductor.collab.com/https://conductor.collab.com/


8/34

vii)

Click Save

Figure 6 - CUCM User Account

3) CUCM needs two trunks to conductor, one for instant meetings and one for

personal meetings. Each of these trunks targets a specific IP address, so we haveto add those to Conductor.

a)

Navigate to System IP

b) Click New

Figure 7 Additional IP Addresses

c)

Enter 10.5.0.81


9/34

d)

ClickAdd Address

Figure 8 Adding new address

e) Repeat above steps to add 10.5.0.82

f)

Conductor will require a reboot to accept these changes

i) Click the word restartin the notification window at the top of your

browser window.ii)

Click Restarton the following page

iii)Click Ok in the pop up to confirm restart.

4)

When calls arrive at conductor via the CUCM trunks it then directs them to the

appropriate bridging resources. Individual MCUs or Telepresence servers can be

grouped together in pools of similar resources. Now we will create a

Telepresence conference bridge pool:

a)

Log back into conductor after the restart

b) Navigate to Conference configuration Conference bridge pools.

i)

Click New

Figure 9 - Create Conference bridge pool

c)

Fill in the following details

i) Pool name:CUCM Pool

ii)

Conference Bridge Type: Telepresence Server


10/34

iii)

Click Create Pool

Figure 10 - Create the bridge pool

5) Each conference bridge pool must contain one or more conference bridges, TP

servers or MCUs. For this lab we only have one but adding several to a pool

gives you scale and redundancy. Add a conference bridge to the pool

a)

Click Create Conference bridge

Figure 11 - Create Conference Bridge

b)

Fill in the following parameters:

i)

Name:vTPS

ii) State:Enabled

iii)IP Address or FQDN:10.5.0.75

iv)

Protocol:HTTPS

v)

Port:443

vi)Conference Bridge username:conductor

vii)

Conference Bridge Password:Cisco12345

viii) SIP port:5061

ix)

Click Create Conference bridge

x) Refresh you browser - The vTPS status should change to Active


11/34

Figure 12 - Add Conference Bridge


12/34

6)

For any particular conference, you can determine which conference bridge pools

the TelePresence Conductor will attempt to use to host that conference, in order

of preference. You do this by creating a Service Preference, and then assigning a

Service Preference to a conference template.

a)

Create a Service Preference

b)

Navigate to Conference configuration Service Preferences.c) Click New

Figure 13 Conference Bridge Service Preferences

d) Enter the following data:

i)

Service Preference Name:Lab CUCM TPSs

ii) Conference Bridge Type:Telepresence Server

iii)

ClickAdd Service Preference

Figure 14 Conference Bridge Service Preferences

iv)

Select Pool name: CUCM Poolfrom the drop down

v)

ClickAdd Selected Pool


13/34

vi)

Click Save

Figure 15 Adding the pool

7)

Conference templates define the settings to be applied to different conferences

when they are created. The same template can be used by more than one

conference alias.

a)

Create a template for an Instant Meeting-type conference

b)

Navigate to Conference configuration Conference templates.

c)

Click New.

Figure 16

Conference templates

d)


i)

Name:Instant CUCM Meetings

ii) Conference Type:Meeting

iii)

Conference Bridge Service Preference:Lab CUCM TPSs

iv)Participant quality:HD (720P 30fps video, stereo audio)

v)

Content quality:HD (720P 30fps)

vi)Optimize resources: Yes


14/34

vii)

Click Create conference template

Figure 17 Conference templates Instant Meetings


15/34

8)

Create a conference template for Personal conferences

a) Click New.

b)

Repeat the Previous steps with the following change:

i) Name:Personal CUCM Conference

9)

A conference alias maps dialed aliases to conferences using regular expressionsand specifies the user's role in the conference (participant, chairperson or

guest).

a) Create a conference alias for a personal conferences

b)

Navigate to Conference configuration Conference aliases.

c) Click New.

Figure 18 Conference alias

d) Enter the following parameters

i)

Name:CUCM Personal Meeting

ii)

Incoming Alias:(5...)@.*iii)

Conference Name:\1.personal_mtg

iv)Conference Template:Personal CUCM Conference

v)

Click Create conference alias

Figure 19 personal conference aliases


16/34

10)

TelePresence Conductor supports conferences between endpoints registered

directly with Unified CM version 8.6.2 or later. A Location is needed to mimic the

Unified CM's expectation that it is connecting to separate conference bridges in

different locations. Both ad hoc conferences and rendezvous conferences are

supported.

a)

Create Unified CM Locations in Conductorb) Go to Conference Configuration Locations.

c)

Click New.

Figure 20 CUCM Locations in Conductor

d)

Enter the location name Lab vTPS

e)

Select Bothfrom the Conference type drop down

Figure 21 Unified CM Locations

f)


i) Ad hoc IP address (local):10.5.0.81

ii)

Template:Instant CUCM Meetings

iii)

Rendezvous IP address:10.5.0.82


17/34

iv)

ClickAdd Location

Figure 22 Adding CUCM Locations

11)

Add Unified CM locations to conference bridge poolsa)

Go to Conference Configuration Conference bridge pools.

b)

Click on CUCM Pool

Figure 23 Adding locations to conference bridge pools


18/34

c)

Select Lab vTPS from the Location Drop down

d) Click Save

Figure 24 Adding locations to pools

Section 3 Configure CUCM

1) Navigate tohttp://cucm.collab.com

2)

Click Cisco Unified Communications Manager

3)

Login

a)

Username:Administratorb) Password:Cisco12345

4)

As mentioned earlier in the lab CUCM communicates with its conferencing

resources via SIP trunks set up for specific needs.

a)

Create a SIP trunk to Conductor for instant conferences

b) Navigate to Device Trunk

c)

Click Add New
http://cucm.collab.com/http://cucm.collab.com/http://cucm.collab.com/http://cucm.collab.com/


19/34

d)

Configure as depicted in the next three figures

e) Click Save

Figure 25 SIP Trunk Creation

Figure 26 SIP Trunk Configurations

Figure 27 Trunk SIP detail

5)

Now that we have established a SIP trunk to conductor, we have to tell CUCM to

use that trunk as an instant conference bridge resource. The first step to do this

is to define Conductor as a Conference Bridge resource.

a)

Navigate to Media Resources Conference Bridge


20/34

b)

ClickAdd New

Figure 28 Adding a conference bridge to CUCM

c)

Fill in the parameters per the screen shot below

i)

Note Username is CUCMand password is Cisco12345

Figure 29 Conference Bridge Parameters

d) Find the Related Links: Back to Find/List and click Go.

e)

NOTE:The conference bridge will not register until after you finish updating

the Device Pool in Step 7 below.

6)

Media Resource Groups (MRGs) and Media Resource Group Lists (MRGLs) areused in order to allow an administrator to allocate media resources to particular

devices. The most common use of MRGs and MRGLs is to restrict media resource

usage on a geographic basis. In this lab we have a single conference bridge and

need to create the MRG and MRGL for it to be used.

a)

Add the Telepresence conductor to an MRG and MRGL

b) Navigate to Media Resources Media Resource Group.

c)

ClickAdd New to create a new media resource group.


21/34

d)

Enter Conductor_MRGfor the name.

e) Move Conductor_Instantdown to the Selected Media Resources box.

f)

Click Save

Figure 30 Media Resource Group

g)

Navigate to Media Resources Media Resource Group Lists.

h) ClickAdd New to create a new media bridge group or find an existing MRGL

and click on it to edit it.

i) Enter a name for the Conductor_Instant_MRGL.

j)

Move the Conductor_MRGdown to the Selected Media Resource Groupsbox.

k) Click Save


22/34

Figure 31 Media Resource Group List

7)

Administrators can configure individual devices to use specific bridging

resources or apply them across groups of devices by leveraging Device Pools. In

this lab we want all of our devices to use these resources so we will apply the

MRGL to the Default device pool.

a)

Add the MRGL to the Device Poolb) Navigate to System Device Pool

c)

Click Find

d)

Click Default

Figure 32 Editing the Device pool

e) Add the Conductor_Instant_MRGLin Roaming Sensitive SettingsSection


23/34

f)

Click Save

Figure 33 Editing the device pool

g) ClickApply Config

8)

Navigate back to Media ResourcesConference Bridge in order to verify theconference bridge registered.

a) Click Find to show all bridges

b)

Verify that your Conductor bridge is now registered with CUCM

9)

A SIP profile comprises the set of SIP attributes that are associated with SIP

trunks and SIP endpoints. SIP profiles include information such as name,

description, timing, retry, call pickup URI, and so on. The profiles contain some

standard entries that cannot be deleted or changed. In order to communicate

with Conductor for Personal conferences one of the changeable fields must be

set.

a)

Create a new SIP profile for Personal conferencesb)

Navigate to Device Device Settings SIP Profile.

c) Click Find


24/34

d)

Click on the Copybutton to the right of the Standard SIP Profile for

TelePresence Conferencing.This will create a new SIP profile with the same

settings as the Standard SIP Profile for TelePresence Conferencing.

Figure 34 Copying a SIP profile

e) In the Name field, enter SIP profile for Conductor.

f)

Under the Parameters used in Phone section, change the Timer Invite

Expires (seconds) to '30'.

g)

Click Save.

Figure 35 Editing the new SIP profile


25/34

10)

As with instant conferences we also need a SIP trunk to conductor for personal

conferences. This time we will point it at the IP address we setup earlier for

Rendezvous conferences.

a) Add a SIP Trunk to Conductor for Personal Conferences

b)

Navigate to Device Trunk.

c)

ClickAdd New to create a new SIP trunk.d) Enter the information as below

Figure 36 Creating the SIP trunk for Conductor

e) Click Next

f)

Enter the information as below

Figure 37 Creating the SIP trunk for Conductor continued


26/34

g)

Scroll all the way to the bottom and enter the following information

Figure 38 SIP Trunk final settings

h) Click Save

i)

Click Reset and confirm the reset

11)

Now that the SIP trunk is in place for personal conferences we have to teach

CUCM what extension patterns it should route over to conductor. These numbers

should match up with the conference alias we setup earlier for personal

conferences.

a)

Add a route Pattern for Personal conferences

b) Navigate to Call Routing Route/Hunt Route Pattern.

c)

ClickAdd New to create a new route pattern.


27/34

d)

Enter the following into the relevant fields, leave other fields as their default

values:

Figure 39 Creating the Route Pattern for Personal Conferences

e)

Click Save

Section 4 Testing Conductor

1)

Create an instant call via Conductor on CUCM

a)

Open a Remote Desktop window to each of the 3 PCs in your lab and log in

with the appropriate user as listed belowi) PC1 srogers / Cisco12345

ii)

PC3 nfury / Cisco12345

iii)PCX-Ext dblake / Cisco12345

b) Open Jabber on each of the 3 PCs.

c) Initiate a call from srogers to nfury.

d)

Conference in dblake.

e)

All three users should now be joined together on vTPS.

i) Verify this by logging intohttp://vtps.collab.com

(1)

User:admin

(2)

Password:Cisco12345

(3)

Click Okto finish logging inii) Click on Conferences
http://vtps.collab.com/http://vtps.collab.com/http://vtps.collab.com/http://vtps.collab.com/


28/34

iii)

You should see a single conference created with a random character

conference name as depicted below.

Figure 40 vTPS with instant meeting on it

f)

Verify Conductors involvement by logging intohttp://conductor.collab.com

i) Username:admin

ii)

Password:Cisco12345

iii)

Navigate to Status Conferencesiv)

Click Expand All

v) You should see your instant conference as below

Figure 41 Conductor with instant meeting on it

2)

Test personal conferencing via Conductor

a)

Dial 5010 from all of your endpoints one by one

b)

Note that all endpoints end up in the same conference on your vTPS

c)

Verify this by logging into both vTPS and conductor as described above.
http://conductor.collab.com/http://conductor.collab.com/http://conductor.collab.com/http://conductor.collab.com/


29/34

Section 5 Personal Collaboration Meeting Rooms

1)

An administrator of the collaboration system provisions personal Collaboration

Meetings rooms for users or groups of users via the Telepresence Management

Suite Provisioning Engine. These personal CMRs then get distributed to

appropriate bridge resources at launch time by Conductor.a.

Navigate tohttp://tms.collab.com

b. Login

i.

Username:Administrator

ii.

Password:Cisco12345

c. Navigate to SystemsProvisioningUsers

Figure 42 TMS Provisioning Menu

d. Click Telepresence Conductor Settings

e.

ClickAdd New in the popup window

f. Enter the following information:

i.

Hostname/IP: conductor.collab.comii. Name: Lab Conductor

iii.

Port: 443

iv. Username: CUCM

v.

Password: Cisco12345

vi.

Domain: Collab.com

vii.

Click Save

Figure 43 Conductor settings in TMS
http://tms.collab.com/http://tms.collab.com/http://tms.collab.com/http://tms.collab.com/


30/34

viii.

Close the popup window by clicking the X in the top right corner

2)

Now that TMS knows how to connect to conductor we can setup the template for

users personal Collaboration Meeting Rooms (CMR)

a.

Click New Template

b.

Enter the information per the screen shot below

Figure 44 New CMR Template

c.

Click the radio button next to your new template in order to make it

active

d.

Click Yes in the popup window to confirm the action

3)

You have now the created the template for all members of collab.com, now we

have to login as a specific user and setup their personal CMR.

a. Expand the Users folder below collab.com

b. Click on Natasha Romanoff to show her user settings


31/34

c.

Click Edit CMR in User Portal

Figure 45 Accessing Natasha's CMR

4)

This loads the user portal as if you were logged in as Natasha

a. Click Set up your Collaboration Meeting Room now

5)

Walk through the guide using the following information

a.

Room Name: Natashas CMRb. Pin: 123456

c.

Click Next

6) You are now dropped onto Natashas CMR page where you can further

personalize her CMR

a. Note you can call into this CMR with either a URI or extension

i.

URI:[email protected]

ii. Note the extension shown should be in the 6000s

b.

Select theActive layout to get the film strip layout
mailto:[email protected]:[email protected]:[email protected]:[email protected]


32/34

c.

Note that you can add participants who are auto connect to the CMR

when it is called into.

Figure 46 Collaboration Meeting Room User Portal

7)

In order to test our newly deployed CMR extension dialing we must tell CUCM

how to route calls to it. We will modify the route pattern used earlier for

personal conferences.

a. Browse tohttp://cucm.collab.com

b.

Login as administrator/Cisco12345

c. Navigate to Call Routing Route/Hunt Route Pattern

d.

Click on 5XXX to edit that route pattern

e. Change the Route Pattern from 5XXX to [5-6]XXX

f.

Click Saveg.

Navigate to Call Routing SIP Route Patterns

h.

Click onAdd New to create a pattern
http://cucm.collab.com/http://cucm.collab.com/http://cucm.collab.com/http://cucm.collab.com/


33/34

i.

Enter the parameters in Figure 48below

Figure 47 CUCM Route Pattern Edit

Figure 48 SIP Route Pattern Configuration

8) Connect to Steve Rogers computer via Remote desktop

a.

Address: pc1.collab.com

b. Username: collab.com\srogers

c.

Password: Cisco12345

9)

Dial the extension or URI to Natashas CMR via Jabber, you should connect to the

vTPS and be prompted to enter the pin

a.

URI: [email protected]

b. PIN: 123456

10)Connect to Nick Furys computer via Remote desktop

a. Address: pc3.collab.com


34/34

b.

Username: collab.com\nfury

c. Password: Cisco12345

11)

Dial the extension or URI to Natashas CMR via Jabber, you should connect to the

vTPS and be prompted to enter the pin

a.

URI [email protected]

b.

PIN: 12345612)Congratulations you should now be connected to Natashas personal CMR.

Documents

Lab 2 - Collaboration Meeting Rooms