Configuring Cuvc For Cisco Telepresence Interoperability - Cisco MCS 7800 Series Administration Manual

Cisco systems multipoint switch administration guide
Hide thumbs Also See for MCS 7800 Series:
Table of Contents

Advertisement

Chapter 8
Interoperability with Legacy Video Conferencing Devices
Step 3
Enter the settings as indicated in
not included in
.
Table 8-3
Field
Pattern Definition
Route Pattern
Description
Gateway/Route List
Call Classification
Step 4
Click the Save button at the bottom of the page.

Configuring CUVC for Cisco TelePresence Interoperability

After basic CUVC configuration has been completed and the unit has been connected to the host
network, you need to perform the following tasks to configure the CUVC for Cisco TelePresence
Interoperability:
OL-12586-02
Table
8-3.
Route Pattern Configuration Settings
Verify that the MCU and EMP are running the correct software version.
Log into the CUVC Administration console and click the Media Processing tab.
Verify that the MCU is running Version 5.5.0.0.54:MP.
Verify that all EMPs are running Version 5.5.2.0.2:EMP.
EMP resources must be available and the MCU service must be defined to use HD/SD Continuous
Presence with a Max Call Rate of 768 kbps or greater. "HD Switch Mode" is not supported. If you
choose a service configuration such as "HD Switched Video," the cascade connection between
CTMS and CUVC will fail to connect.
Table 8-3
to configure the SIP trunk. Leave default settings for fields
Required
Setting
Yes
Enter the route pattern, including numbers and
wildcards (do not use spaces); for example, for
NANP, enter 9.@ for typical local access, or
8XXX for a typical private network numbering
plan. The uppercase characters A, B, C, and D are
valid characters.
Note
Note
Enter a text string describing this route pattern.
Yes
Select the SIP trunk that you created for CUVC.
Yes
Select OnNet.
Cisco TelePresence Multipoint Switch Release 1.1 Administration Guide
Configuring Cisco TelePresence Interoperability
The portion of the route pattern's digit
string sent to the CUVC must begin with
a valid service prefix as defined on the
CUVC.
See the "Wildcards and Special
Characters in Route Patterns and Hunt
Pilots" section in the Cisco CallManager
System Guide for more information about
wildcards.
8-81

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents