Beruflich Dokumente
Kultur Dokumente
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), Telepresence
Server (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 Conductor helps 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 video
endpoints at whatever resolution each endpoint supports while maintaining visual
engagement.
Cisco Unified Communications Manager is the call control quarterback that
routes your collaboration calls, audio or video, seamlessly through the architecture.
How it works
The diagram below shows call flows for both ad-hoc (instant) and rendezvous
(personal) conference.
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 have
to add those to Conductor.
a) Navigate to System IP
b) Click New
c) Enter 10.5.0.81
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
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
iv) Select Pool name: CUCM Pool from the drop down
v) Click Add Selected Pool
Figure 16
Conference templates
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
f) Click Save
d) Click on the Copy button 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.
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) Click Add New to create a new SIP trunk.
d) Enter the information as below
e) Click Next
f) Enter the information as below
g) Scroll all the way to the bottom and enter the following information
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) Click Add New to create a new route pattern.
d) Enter the following into the relevant fields, leave other fields as their default
values:
e) Click Save
iii) You should see a single conference created with a random character
conference name as depicted below.
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
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
c. Note that you can add participants who are auto connect to the CMR
when it is called into.
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 to http://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 Save
g. Navigate to Call Routing SIP Route Patterns
h. Click on Add New to create a pattern
i.
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 nromanoff@join.collab.com
b. PIN: 123456
12) Congratulations you should now be connected to Natashas personal CMR.