Table Of Contents
Configuring CTMS Administration Software
Contents
Overview
Access Management
Configuration Files
CTS-Manager
Interface Failover
Security
Services
Software Upgrade
System Settings
IP
NTP
Route Pattern
QoS
Resources
SNMP
Restart CTMS
Unified CM
Unified CM Settings
SIP Profile Settings
WebEx
Configuring CTMS Administration Software
Created: September 2010
Revised: April 2011
Contents
•
Overview
•
Access Management
•
Configuration Files
•
CTS-Manager
•
Interface Failover
•
Security
•
Services
•
Software Upgrade
•
System Settings
–
IP
–
NTP
–
Route Pattern
–
QoS
–
Resources
–
SNMP
–
Restart CTMS
•
Unified CM
–
Unified CM Settings
–
SIP Profile Settings
•
WebEx
Overview
The following sections describe configuration parameters for the Cisco TelePresence Multipoint Switch (CTMS). These configuration parameters are accessible from the left navigation of the CTMS browser-based administration UI:
•
Access Management
•
Configuration Files
•
CTS-Manager
•
Interface Failover
•
Security
•
Services
•
Software Upgrade
•
System Settings
•
Unified CM
•
WebEx
Figure 3-1 Configure—Left Navigation
Access Management
CTMS administration software recognizes three different administrative roles:
•
Administrator: Administrators have the authority to perform all tasks associated with CTMS, including configuring settings; managing multipoint meetings; and maintaining, monitoring, and troubleshooting CTMS.
•
Meeting Scheduler: Meeting Schedulers have the authority to perform multipoint meeting management tasks, such as defining meeting templates and setting up (and breaking down, as necessary) ad hoc, static, and scheduled meetings.
•
Diagnostic Technician: Diagnostic Technicians have the authority to perform CTMS monitoring and troubleshooting tasks.
Access to certain tasks and information is dependent on dependent on the administrative role. Administrative roles are considered a form of access management.
Figure 3-2 shows the Access Management page.
Figure 3-2 Access Management
To configure or edit Access Management settings:
Step 1
Click Access Management under Configure in the left navigation to open the Access Management page.
Step 2
Access Management displays a table providing the following information about previously defined users as described in Table 3-1.
Table 3-1 Access Management Table Field Descriptions
Field
|
Description
|
Username
|
Username of a specific CTMS user.
|
Administrator
|
Administrators have the authority to perform all tasks associated with CTMS, including configuring settings; managing multipoint meetings; and maintaining, monitoring, and troubleshooting CTMS. Administrators have access to all folders in CTMS administration software. A green check in this field indicates that the selected user has been designated as an administrator.
|
Meeting Scheduler
|
Meeting Schedulers have the authority to perform multipoint meeting management tasks, such as defining meeting templates and setting up (and breaking down, as necessary) ad hoc, static, and scheduled meetings. Meeting Schedulers have access to Manage in the left navigation. A green check in this field indicates that the user has been designated as a meeting scheduler.
|
Diagnostic Technician
|
Diagnostic Technicians have the authority to perform CTMS monitoring and troubleshooting tasks. Diagnostic Technicians have access to Troubleshoot in the left navigation. A green check in this field indicates that the user has been designated as a diagnostic technician.
|
•
To delete a user, click the radio button to the left of the entry. Then click Delete.
•
To edit a user, click the radio button to the left of the entry. Then click Edit.
•
To define a new user, click New,
Step 3
When you click New from the Access Management page, the Access Management dialog box to create a new user appears (Figure 3-3).
Figure 3-3 Access Management: New User
Step 4
Enter settings as described in Table 3-2.
Table 3-2 New User Settings
Field or Button
|
Setting
|
User Name
|
Username of the new user.
Note A username must be at least 5 characters, but not more than 64 characters in length. The username must contain letters and numbers, but it cannot contain special characters, except for the underscore character. Letters can be uppercase and lowercase.
The username cannot be all numbers.
The following usernames are not allowed: apache, daemon, nobody, operator, and shutdown.
|
Password
|
Password for the username indicated in the Username field.
Note Passwords must be at least 5 characters, but no more than 64 characters. Passwords must contain numbers and uppercase and lowercase letters. They can also contain special characters, such as the asterisk (*) or the hyphen (-).
Note When you change the Administrator role password for the first time after software installation, the new password cannot be similar to password that was configured during installation.
|
Verify Password
|
Re-enter the password defined for this user.
|
Role
|
Defines a specific user role. There are three possible roles, each with specific levels of administrative access:
• Administrator: Administrators have access to all pages and configuration tasks.
• Conference Scheduler (Meeting Scheduler): Conference schedulers have access only to the Manage pages and associated configuration tasks.
• Diagnostic Technician: Diagnostic technicians have access only to Troubleshoot pages and one task (system restart).
Note A single user can have more than one role.
Click the appropriate checkboxes to select.
|
•
To register new or modified settings, click Apply.
•
To close this window without applying settings, click Close.
Step 5
To edit an existing user profile, click the radio button to the left of the table entry to select the user. Then click Edit. When you click Edit, a dialog box appears.
Step 6
Enter settings as described in Table 3-3.
Table 3-3 Edit User Settings
Field or Button
|
Setting
|
Username
|
View only. Username of the CTMS user.
|
Current Password
|
Current password for the CTMS user.
|
New Password
|
New password for the CTMS user.
Note Passwords must be at least 5 characters, but no more than 64 characters. Passwords must contain numbers and uppercase and lowercase letters. They can also contain special characters, such as the asterisk (*) or the hyphen (-).
Note When you change the Administrator role password for the first time after software installation, the new password cannot be similar to password that was configured during installation.
|
Verify New Password
|
Re-enter the password defined for this user.
|
•
To register new settings, click Save.
•
To close this window without applying settings, click Close.
Configuration Files
To back up the CTMS configuration for use in case of a hardware failure or a need to rebuild the CTMS server, you must first export the files to a secure location (for example, to a local hard drive). After the hardware is stable or the server is rebuilt, you can re-import the configuration files that you backed up.
Figure 3-4 shows the Configuration Files page.
Figure 3-4 Configuration Files
To import or export files:
Step 1
Click Configuration Files under Configure in the left navigation.
Step 2
Click Export Files to export configuration files.
Step 3
Click Import Files to import defined user and configuration files. Click Browse to select the exported user and configuration files, then click Install Config Files to unzip and install the files.
CTS-Manager
The Cisco TelePresence Manager (CTS-Man) manages CTMS resources for scheduled meetings. This section describes the settings that are necessary to build the communication channel between CTMS and CTS-Man. This section also includes information that CTS-Man needs to provide to the scheduled CTS endpoints.
Figure 3-5 shows the CTS-Manager page.
Figure 3-5 CTS-Manager
To configure or edit CTS-Manager settings:
Step 1
Click CTS-Manager under Configure in the left navigation to open the CTS-Manager page.
Step 2
The page displays the Cisco TelePresence Manager settings.
Step 3
Enter or edit settings as described in Table 3-4.
Table 3-4 Cisco TelePresence Manager Settings
Field or Button
|
Setting
|
Description
|
Text describing or identifying this particular CTMS. The maximum number of characters for this field is 62 characters.
|
Time Zone
|
The time zone in which the CTMS is located. CTS-Man will use this setting to identify the closest CTMS for all scheduled CTS endpoints.
|
User
|
Username with which CTMS web services communicates with CTS Manager.
Note A username must be at least 5 characters, but not more than 64 characters in length. The username must contain letters and numbers, but it cannot contain special characters, except for the underscore character. Letters can be uppercase and lowercase.
The username cannot be all numbers.
The following usernames are not allowed: apache, daemon, nobody, operator, and shutdown.
Note The username and password configured on the CTMS and CTS-Man need to be the same.
|
Password
|
Password with which CTMS web services communicates with CTS Manager.
Note Passwords must be at least 5 characters, but not more than 64 characters in length. Passwords must contain numbers and uppercase and lowercase letters. They can contain the underscore and dash characters.
Note The username and password configured on the CTMS and CTS-Man need to be the same.
|
Host
|
IP address or hostname of the CTS-Man.
|
Dial Plan
|
The following fields define the dialing system CTMS and CTS-Man use to establish intercompany communication TelePresence meetings.
|
Site Access Code
|
Defines the dialed numbers prepended to a CTS endpoint extension number to create a fully qualified domain name (FQDN) in a Cisco Unified Communications Manager (Cisco Unified CM) multicluster environment.
|
Inter Site Access Code
|
Defines the dialed prefix used to reach another site within the same company in a Cisco Unified CM multicluster environment.
|
External Access Code
|
Defines the dialed prefix from within a company to reach a local outside line.
|
National Dialing Digits
|
Defines the specific digit(s) used to place a national call. For example, in the United States, the national dialing digit is 1.
|
International Dialing Digits
|
Defines the specific digit(s) used to place an international call. For example, in the United States, the international dialing digits are 011.
|
Directory Number
|
The following fields define the E.164 numbering plan used for intercompany communication.
|
Country Code
|
A unique set of digits used to identify a specific country as part of an E.164 number as defined by the International Telecommunications Union (ITU). The country code can consist of one, two, or three digits.
|
National Destination Code
|
A unique set of digits used to identify a specific national destination (area code) as part of an E.164 number as defined by the International Telecommunications Union (ITU).
|
Local Number
|
A unique set of digits used to identify a subscriber as part of an E.164 number as defined by the International Telecommunications Union (ITU).
|
Registration Status
|
View only. Status of the registration between the CTMS and CTS-Man defined in the host entry.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
Interface Failover
Interface failover provides a backup mechanism for Ethernet adapters. When enabled, the secondary adapter handles all network traffic if the primary adapter or its connection fails.
Figure 3-6 shows the Interface Failover page.
Figure 3-6 Interface Failover
To enable interface failover:
Step 1
Ensure that the primary Ethernet adapter (Ethernet interface 0) is connected to the network and that its static IP address and gateway parameters were correctly configured during system installation.
Step 2
Connect the secondary Ethernet cable (Ethernet interface 1) to a network switch. The connection port can be on the same switch as Ethernet interface 0 or on a different switch, but both Ethernet interface 0 and Ethernet interface 1 must be on the same gateway.
Note
We recommend that the Ethernet ports be connected to different switches for more resilient failover protection, but they can be connected to the same switch.
Step 3
From the Interface Failover window, click the Enable radio button, then click Apply.
Note
If the Enable button is grayed out, check your network connection.
To disable interface failover:
Step 1
With no active meetings in progress, click the Disable radio button.
Step 2
Click Apply. Your network adapters will be configured and restarted, and the interface failover will be disabled.
Security
Starting with CTMS Release 1.5, CTMS added support for secure communication between Cisco TelePresence devices using Certificate Authority Proxy Function (CAPF). Each Cisco TelePresence product downloads a Locally Significant Certificate (LSC) from a CAPF server; communication between devices is then authenticated using LSCs, Cisco Unified Communications Manager (Cisco Unified CM) Root Certificates and a CAPF Root Certificate.
To configure CTMS for security, you need to first complete preliminary steps in Cisco Unified CM. You must activate and start CAPF service, create application users, create Cisco Unified CM root certificates for every Cisco Unified CM server associated with Cisco TelePresence service, and create a CAPF root certificate. Then from the Security window in CTMS, you upload the applicable Cisco Unified CM and CAPF root certificates, and download the appropriate LSCs. When all certificates are in place and the LSC is downloaded, the CTMS reboots so that the security settings take effect.
Figure 3-7 shows the Security page.
Figure 3-7 Security
To configure CAPF Security for CTMS:
Step 1
From Cisco Unified CM: Configure Cisco Unified CM to run in secure mode. For more information, refer to Cisco Unified Communications Manager Installation Guide for the Cisco TelePresence System Release 1.7.
Step 2
From Cisco Unified CM: Create an application user in Cisco Unified CM. From the Cisco Unified CM Administration page, select Application User from the User Management drop-down menu. Click Add New and then complete all necessary Application User Information fields. Be sure that the user is included in the "Standard CTI Enabled" group, and the "Standard CTI Secure" group and the "Standard CTS Secured Connection" role under Permission Information. When finished, click Save.
Note
Create an application user for each Cisco TelePresence product (such as CTS, CTMS and CTS-Man) in your network.
CTI will be used to transport the LSC from the Cisco Unified CM to the CTMS later.
Step 3
From Cisco Unified CM: Create an Application User CAPF profile in Cisco Unified CM. From the Cisco Unified CM Administration page, select Application User CAPF Profile from the User Management drop-down menu. Click Add New. Select the application user you previously created from the Application User drop-down list and then complete the appropriate CAPF profile fields for that user:
•
Instance ID: Unique identifier (alpha-numeric) for the cluster
•
Certificate Operation: Select "Install/Upgrade."
Note
Certificate Operation resets automatically to "No Pending Operation" after a certificate is downloaded. You must reset this field to "Install/Upgrade" for additional certificate downloads.
•
Authorization String: Click "Generate String" to get a one-time authorization code to download certificates
•
Key size: Default value is 1024.
When finished, click Save.
Note
Create an Application User CAPF Profile for each CTMS in your network.
Step 4
From Cisco Unified CM: Download CAPF Root Certificate in Cisco Unified CM. From Cisco Unified OS Administration in Cisco Unified CM, select Certificate Management from the Security drop-down menu. Click Find to display a list of certificates. Find the CAPF Root Certificate (for example, CAPF.der), and click the hypertext link for that certificate. Click Download and then follow the download instructions. Save the CAPF Root Certificate to your desktop with the following name: CAPF.der.
Step 5
From CTMS: Upload the CAPF Root Certificate in CTMS. From the Security window in CTMS, click Upload. Select:
•
Unit: CAPF-Trust
•
Category: TRUST
•
Certificate: Select the CAPF Root certificate that you downloaded from Cisco Unified CM (CAPF.der).
Click Upload to upload the CAPF Root certificate.
Step 6
From Cisco Unified CM: Download Cisco Unified CM Root Certificate in Cisco Unified CM. From Cisco Unified OS Administration in Cisco Unified CM, select Certificate Management from the Security drop-down menu. Click Find to display a list of certificates. Find the Cisco Unified CM Root Certificate (for example, CallManager.der), and click the hypertext link for that certificate. Click Download and follow the download instructions. Save the Cisco Unified CM Root Certificate for the Publisher as CUCM0.der
Note
Names must be in the following format: CUCM#.der, where # is 0 for Publisher and 1 through 6 for Subscribers.
Step 7
From CTMS: Upload the Cisco Unified CM Root Certificate(s) in CTMS. From the Security window in CTMS, click Upload. Select:
•
Unit: CTM-Trust
•
Category: TRUST
•
Certificate: Select the Cisco Unified CM root certificate that you created in Cisco Unified CM (CUCM0.der).
Click Upload to upload the Cisco Unified CM root certificate.
Step 8
From CTMS: Download the LSC in CTMS. After creating the application user and application user CAPF profile, from CTMS, click Security to open the Security window. Click Download LSC and fill out the fields:
•
CAPF Instance ID: Must match instance ID created in Cisco Unified CM.
•
CAPF Auth String: Must match authorization string created in Cisco Unified CM.
•
TFTP Server Host: Cisco Unified CM TFTP server.
•
TFTP Server Port: Must match the Cisco Unified CM TFTP port, which is 69 by default.
•
CAPF Server Host: Cisco Unified CM CAPF server host.
•
CAPF Server Port: Must be 3804, which is the default value.
Click Download LSC. After the LSC has been successfully downloaded, the CTMS reboots automatically.
Step 9
From Configure > Security in CTMS: Inspect the downloaded LSC to find the X.509 subject name:
a.
Click the radio button with the certificate name "CTMS.pem."
b.
Click View.
c.
Locate the X.509 subject name, which is listed after "Subject: CN=."
Step 10
From Cisco Unified CM: Configure SIP Trunk Security in Cisco Unified CM. From the Cisco Unified CM Administration page, from the System menu, select Security Profile and then SIP Trunk Security Profile. Click Find to display a list of SIP Trunk Security profiles. Find the appropriate profile and click the hypertext link for that profile. Enter:
•
Name: Unique profile name
•
Description: Identifying description for this profile
•
Device Security Mode: Select "Encrypted"
•
Incoming Transport Type: TLS
•
Outgoing Transport Type TLS
•
X.509 Subject Name: Enter the subject name of the CTMS Root Certificate
•
Incoming Port: Unique port number
Note
Port 5060 is for the non-secure device security mode.
Click Save if you are revising an existing profile; click Add New if you are creating a new profile.
Step 11
From CTMS: Secure CTMS. From the Unified CM window in CTMS, click the SIP Profile Settings tab. For Device Security, select one of these settings:
•
Authenticated
•
Encrypted with SDP Keys (recommended if using Cisco Unified CM version 7.0 or later)
To select the default meeting security level:
Step 1
After the system reboots, you can select the default meeting security level: secure, non-secure, or best effort security mode. From the Security window, make the appropriate selection(s) as necessary.
Table 3-5 Security Settings
Field or Button
|
Setting
|
Meeting Security Policy
|
Indicates the meeting security policy for this CTMS. Choices are Secure, Non-Secure, and Best Effort. If no security certificates have been downloaded, CTMS automatically selects "Non-Secure."
|
Web Services Security
|
Indicates the web services security policy for this CTMS. This field will display "Secure" when CTMS is secure. This field will display "Non secure" when CTMS is not secure.
|
If the security certificates expire, or you change the Cisco Unified CM server with which you are interfacing, you need to delete all security certificates and then add new ones. Until you reestablish new security certificates, you will not be able to make secure Cisco TelePresence calls.
To delete security certificates from a secure CTMS:
Step 1
From the Security page, click the Delete All button. Follow the appropriate instructions as displayed:
•
Change Device Security to Non-Secure
•
Uncheck the Media Encryption checkbox
Step 2
After you have followed the instructions as displayed, click the Delete All button again. Then click OK or Cancel as appropriate.
Services
CTMS uses Conference Control Protocol (CCP) to provide CTS endpoints with access to in-meeting functions, such as the participant list; room or speaker switching policies; and the lock meeting feature.
The participant list should include all endpoints, including audio add-ins. However, if an audio add-in is included through a CTS 1.6 or older endpoint, the audio add-in is not included in the participant list.
CCP is delivered over HTTP or HTTPS and can be forwarded to HTTP proxies in a secure enterprise domain where direct HTTP Internet access is not possible.
The Services section specifies the HTTP proxy URL that CTMS should advertise to the CTS endpoints in a multipoint meeting. Enterprises wishing to make InterCompany multipoint calls should work with their TelePresence provider to define the proxy requirement. If the URL is not specified, CTMS advertises its own default CCP URL. An incorrect URL stops in-meeting features from functioning but will not affect regular call setup and teardown.
Figure 3-8 Services
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
Note
When you modify the URL and apply the change, the Web UI automatically restarts all CTMS processes to have Confgmr/CCS reload the new URL.
Software Upgrade
There are two functions to assist you in maintaining the system software:
•
Switch Versions: The hard drive of the server on which CTMS is installed is partitioned into two areas. Each area can contain a system image. Switch Versions allows you to switch the two versions of the system software.
•
Upgrade Software: CTMS provides a patch file for upgrading system software. The Cisco-supplied patch file can be stored on a CD-ROM or a Secure FTP (SFTP) host network. A wizard displays dialog boxes to prompt you through the process.
Figure 3-9 shows the Software Upgrade page.
Figure 3-9 Software Upgrade
To switch software versions:
•
Click the Switch Versions button.
The system will swap the software versions and reboot. Screens describe activity.
The active partition in the server hard drive contains the active system image. The software versions that are loaded are displayed as Active Version and Inactive Version.
To upgrade software:
Step 1
To start the software upgrade process, click the Upgrade Software button.
The Source Selection dialog box appears.
If you need to stop the software installation, click the Cancel button when the button is active.
Step 2
Click the CD-ROM or Network radio button to choose the location of the patch file.
If you choose CD-ROM, click Next to go to the File Selection window.
If you choose Network, click the SFTP or FTP radio button. Provide the Host, Port, Username, Password, and the Storage Path to the software file. By default, port 22 is used to access the server; supply the correct port number, if required. Click Next to go to File Selection.
Step 3
In File Selection window, select the file to load by clicking its radio button. Then click Next.
Step 4
The Patch File Preparation window appears. Watch this window to monitor the progress of the file download. Buttons will be inactive until the patch file is loaded.
Once the file is loaded, the window displays a confirmation message.
The software wizard displays the software versions that are installed and provides active Yes and No radio buttons so you can choose to switch the newly loaded software to the active partition.
Step 5
Click Yes or No to make your choice. Then click Next to finish the software upgrade task.
The install wizard displays a dialog window that logs the progress of the update.
Step 6
When the log indicates that the files have been switched, click Finish to complete this task.
System Settings
System Settings are initially configured during CTMS administration software set up. Use System Settings to make changes to these initial settings:
•
IP
•
NTP
•
Route Pattern
•
QoS
•
Resources
•
SNMP
•
Restart CTMS
IP
Figure 3-10 shows the IP Settings page.
Figure 3-10 IP Settings
To edit IP settings:
Step 1
Click System Settings under Configure in the left navigation.
Click the IP tab. Some of the settings displayed on the IP Settings page are configured during initial installation of the CTMS software. The following fields can be configured on this page:
•
Domain Name
•
Primary DNS
•
Secondary DNS
•
IP Address
•
Subnet Mark
•
Default Gateway
Step 2
Edit settings as described in Table 3-6.
Table 3-6 IP Settings
Field or Button
|
Setting
|
MAC Address
|
View only. MAC address of the MCS server on which the Cisco TelePresence Multipoint Switch is located.
|
Hostname
|
View only. Hostname configured for the MCS server on which the Cisco TelePresence Multipoint Switch is located.
|
Domain Name
|
Domain name in which the MCS server on which the Cisco TelePresence Multipoint Switch is located.
|
Primary DNS
|
IP address of the primary Domain Name System (DNS) server for the MCS server on which the Cisco TelePresence Multipoint Switch is located.
|
Secondary DNS
|
IP address of the secondary Domain Name System (DNS) server for the MCS server on which the Cisco TelePresence Multipoint Switch is located.
|
Ethernet Card
|
View only. Ethernet card being used on the MCU server to connect to the network.
|
IP Address
|
IP address of the Cisco TelePresence Multipoint Switch.
Note After changing the IP address, close your browser window, then log into CTMS again using your new IP address.
|
Subnet Mask
|
Subnet mask of the Cisco TelePresence Multipoint Switch.
|
Default Gateway
|
Default gateway IP address for the Cisco TelePresence Multipoint Switch.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
NTP
Network Time Protocol (NTP) servers allow CTMS to synchronize system time with CTS and CTS-Man. Synchronization is a critical component for scheduled meetings.
Figure 3-11 shows the NTP Settings page.
Figure 3-11 NTP Settings
To edit NTP settings:
Step 1
Click System Settings under Configure in the left navigation.
Click the NTP tab to list the configured IP address of the NTP servers.
Step 2
Edit settings as described in Table 3-7.
Table 3-7 NTP Settings
Field or Button
|
Setting
|
NTP Server 1-5
|
IP address of the NTP server. To add an NTP server to the configuration, type the IP address in an NTP Server field. To change an NTP server in the configuration, highlight and delete the IP address in the NTP Server field and type in the new address.
Note You must configure at least two NTP servers.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
Route Pattern
Route pattern settings define route patterns—a string of digits that can be assigned to direct calls for specific devices and access numbers associated with this CTMS.
Note
All of the settings in the Route Pattern page are derived from settings you previously configured in Cisco Unified Communications Manager (Cisco Unified CM).
Figure 3-12 shows the Route Pattern page.
Figure 3-12 Route Pattern
To edit route pattern settings:
Step 1
Click System Settings under Configure in the left navigation.
Step 2
Click the Route Pattern tab.
Step 3
Enter the settings as described in Table 3-8.
Table 3-8 Access Settings
Field or Button
|
Setting
|
Route Pattern Start
|
Defines the first number in your defined route pattern as configured in Cisco Unified CM.
|
Route Pattern End
|
Defines the last number in your defined route pattern as configured in Cisco Unified CM.
|
Access Number
|
Displays the first number in the route pattern as defined in Cisco Unified CM. The CTMS automatically chooses the first number in the range.
This number is used as the dial-in number for all scheduled meetings. This number is also used as the caller ID when the CTMS dials out for ad hoc meetings.
Note The access number cannot be used for static meetings.
|
Access Name
|
Descriptive name for the access number as defined in Cisco Unified CM. Maximum number of characters is 20.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
QoS
Differentiated Services Code Point (DSCP) markings are used by the network to classify traffic priority so that a queuing strategy can be applied. QoS settings define the DSCP markings that CTMS applies to its media traffic as that traffic goes to CTS, CUVC, and Cisco Unified CM for SIP signaling.
These settings should be consistent with Cisco Unified CM settings for the Cisco TelePresence endpoints and should also align with your enterprise-wide queuing strategy. Work with network administrators to identify DSCP markings for CTMS traffic.
Figure 3-13 shows the QoS Settings page.
Figure 3-13 QoS Settings
To configure or edit QoS settings:
Step 1
Click System Settings under Configure in the left navigation.
Step 2
Click the QoS tab.
Step 3
Enter or edit settings as described in Table 3-9.
Table 3-9 QoS Settings
Field or Button
|
Setting
|
DSCP for CTS Media
|
Traffic marking values for Cisco TelePresence System (CTS) voice and video traffic used for network queuing. Available settings are:
• AF11 DSCP (001010)
• AF12 DSCP (001100)
• AF13 DSCP (001110)
• AF21 DSCP (010010)
• AF22 DSCP (010100)
• AF23 DSCP (010110)
• AF31 DSCP (011010)
• AF32 DSCP (011100)
• AF33 DSCP (011110)
• AF41 DSCP (100010)
• AF42 DSCP (100100)
• AF43 DSCP (100110)
• CS1 (precedence 1) DSCP (001000)
• CS2 (precedence 2) DSCP (010000)
• CS3 (precedence 3) DSCP (011000)
• CS4 (precedence 4) DSCP (100000)
• CS5 (precedence 5) DSCP (101000)
• CS6 (precedence 6) DSCP (110000)
• CS7 (precedence 7) DSCP (111000)
• Default DSCP (000000)
• EF DSCP (101110)
The default value for this field is CS4 (precedence 4) (100000) based on Cisco TelePresence SRND recommendations. Choose this value to align with your network-wide QoS strategy.
|
DSCP for CUVC Media
|
Traffic marking values for Cisco Unified Videoconferencing 5230 (CUVC) voice and video traffic used for network queuing. Available settings are:
• AF11 DSCP (001010)
• AF12 DSCP (001100)
• AF13 DSCP (001110)
• AF21 DSCP (010010)
• AF22 DSCP (010100)
• AF23 DSCP (010110)
• AF31 DSCP (011010)
• AF32 DSCP (011100)
• AF33 DSCP (011110)
• AF41 DSCP (100010)
• AF42 DSCP (100100)
• AF43 DSCP (100110)
• CS1 (precedence 1) DSCP (001000)
• CS2 (precedence 2) DSCP (010000)
• CS3 (precedence 3) DSCP (011000)
• CS4 (precedence 4) DSCP (100000)
• CS5 (precedence 5) DSCP (101000)
• CS6 (precedence 6) DSCP (110000)
• CS7 (precedence 7) DSCP (111000)
• Default DSCP (000000)
• EF DSCP (101110)
The default value for this field is AF41 DSCP (100010) based on Cisco TelePresence SRND recommendations. Choose this value to align with your network-wide QoS strategy.
|
DSCP for Signaling
|
Traffic queuing techniques that define per-hop behavior based on the Differentiated Services Code Point (DSCP) value in the IP header of a packet. control stream
Available settings are:
• AF11 DSCP (001010)
• AF12 DSCP (001100)
• AF13 DSCP (001110)
• AF21 DSCP (010010)
• AF22 DSCP (010100)
• AF23 DSCP (010110)
• AF31 DSCP (011010)
• AF32 DSCP (011100)
• AF33 DSCP (011110)
• AF41 DSCP (100010)
• AF42 DSCP (100100)
• AF43 DSCP (100110)
• CS1 (precedence 1) DSCP (001000)
• CS2 (precedence 2) DSCP (010000)
• CS3 (precedence 3) DSCP (011000)
• CS4 (precedence 4) DSCP (100000)
• CS5 (precedence 5) DSCP (101000)
• CS6 (precedence 6) DSCP (110000)
• CS7 (precedence 7) DSCP (111000)
• Default DSCP (000000)
• EF DSCP (101110)
The default value for this field is CS3 (precedence 3) (011000) based on Cisco TelePresence SRND recommendations. Choose this value to align with your network-wide QoS strategy.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
Note
QoS settings are a system-wide policy and should be consistent across the TelePresence domain. Unless network administrators have specific reasons to change these values, QoS settings should match Cisco Unified CM settings.
Resources
Resource Management settings enable you to specify the number of ad hoc segments and segments that can be scheduled for use.
Figure 3-14 shows the Resource Management page.
Figure 3-14 Resource Management
To configure or edit Resource Management settings:
Step 1
Click System Settings under Configure in the left navigation.
Step 2
Click the Resources tab.
Step 3
Enter or edit settings as described in Table 3-10.
Table 3-10 Resource Management Settings
Field or Button
|
Setting
|
Maximum Segments
|
View only. The total number of segments (individual video displays) this CTMS handles. The maximum number is 48.
|
Adhoc Segments
|
Defines the maximum number of segments available for impromptu meetings. By defining the number of table segments available for ad hoc meetings, you ensure that there will be sufficient segments available for scheduled meetings. Maximum number is 48.
Note Combined total for Schedulable Segments and Ad hoc Segments cannot exceed 48.
Note Interop calls consume one additional CTMS segment per interop meeting to accommodate the cascade link between the CTMS and the Cisco Unified Videoconferencing (CUVC) MCU. An interop call is defined as any meeting that contains both a CTS and legacy videoconferencing systems.
Note When you configure scheduled meetings, you should also configure ad hoc segments so that you can add CTS endpoints to the meeting from the CTMS user interface if necessary.
|
Schedulable Segments
|
This field displays the number of segments available at any one time for scheduled meetings. CTMS automatically derives this value by subtracting the defined number of Ad Hoc Segments from the defined number of Maximum Segments.
|

Note
If you do not have Cisco TelePresence Manager installed, all segments must be ad hoc.
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
SNMP
The Simple Network Management Protocol (SNMP) is an application layer protocol that facilitates the exchange of management information between network devices. It enables network administrators to manage network performance, find and solve network problems, and plan for network growth by analyzing information gathered using MIBs. You configure all SNMP settings through the CTMS command line interface (CLI) commands.
SNMP is enabled by default, and it monitors the CTMS system status (go to Troubleshoot > System Resources for system status details). You can designate a particular server where SNMP trap messages are gathered and stored. Configuration requires username and password authentication.
By default, SNMP service is enabled. The following default SNMP settings are also enabled:
•
SNMPv3 username set to "mrtg." This name is for internal use of the system and should not be deleted.
•
SNMPv2c username set to "public." This name is for internal use of the system and should not be deleted.
•
No trap receiver is configured. Use CTMS CLI commands to configure SNMP trap receiver information.
Figure 3-15 shows the SNMP Settings page. All information on this page is view only.
Figure 3-15 SNMP Settings
Table 3-11 describes the SNMP fields.
Table 3-11 SNMP Settings
Field or Button
|
Setting
|
Engine ID
|
View only. The engine ID for the SNMP agent on this Cisco TelePresence Multipoint Switch. This number is usually based on the CTMS MAC address.
If you configure the trap receiver, this engine ID is used to create a trap user on the trap receiver system and to compute the security digest for authenticating and encrypting packets sent to a user on the remote host.
|
SNMP
|
View only. Shows whether SNMP is enabled or disabled.
|
System Location
|
View only. Physical location of the SNMP system associated with CTMS.
|
System Contact
|
View only. Name of the SNMP system contact associated with CTMS.
|
SNMP Access Configuration
|
|
Version
|
View only. Lists the configured SMNP version, either 3 or 2C.
|
User Name/ Community String
|
View only. SNMP server username.
|
Access
|
View only. Indicates whether the access is read, writer or read/write.
|
Password
|
View only. SNMP server password. The password must be 8 characters long. Enter it twice for verification.
|
Security Level
|
View only. Level of security supported by the SNMP server.
|
Authorization Algorithm
|
View only. Authentication algorithm supported by the SNMP server. Currently only MD5 algorithm is supported.
|
Encryption
|
View only. Encryption used for SNMP requests.
|
Trap Receiver Configuration
|
|
IP Address
|
View only. IP address or hostname of the SNMP trap receiver (the remote SNMP system) where SNMP traps will be sent.
|
Version
|
View only. Lists the configured SNMP version, either 3 or 2C.
|
User Name
|
View only. Username used to access the system where SNMP traps are received.
Note SNMP trap user names can be from 1 to 32 characters.
|
Password
|
View only. Password used to access the system where SNMP traps are received.
|
Engine ID
|
View only. Engine ID to use for trap; default is system engine ID.
|
Security Level
|
View only. Level of security supported by the SNMP Trap Receiver.
|
Authentication Algorithm
|
View only. Authentication algorithm supported by the SNMP Trap Receiver. Currently only MD5 algorithm is supported.
|
Encryption
|
View only. Encryption used for SNMP requests.
|
To view all CTMS MIBs, go to the following location:
ftp://ftp.cisco.com/pub/mibs/supportlists/ctms/ctms-supportlist.html
Restart CTMS
Figure 3-16 shows the Restart CTMS page.
Figure 3-16 Restart CTMS
To restart CTMS or to shutdown CTMS:
Step 1
Click System Settings under Configure in the left navigation.
Step 2
Click the Restart CTMS tab.
Step 3
Click Restart to restart—meaning shutdown and then reboot—CTMS.
Step 4
Click Shutdown to completely shutdown CTMS.
Unified CM
The following sections describe how to make changes to the Cisco Unified Communications Manager (Cisco Unified CM) settings:
•
Unified CM Settings
•
SIP Profile Settings
Unified CM Settings
Figure 3-17 shows the Cisco Unified CM page.
Figure 3-17 Unified CM
To configure or edit Cisco Unified CM settings:
Step 1
Click Cisco Unified CM Settings under Configure in the left navigation.
Step 2
Click the Unified CM Settings tab.
Step 3
Enter settings as described in Table 3-12.
Table 3-12 Cisco Unified CM Settings
Field or Button
|
Setting
|
Unified CM 1 through 5
|
Hostnames or IP address(es) of the Cisco Unified CM server.
Note It is important to add all Cisco Unified CM servers in the cluster.
|
SIP Port
|
Port number for Cisco Unified SIP IP Phones that are using UDP to listen for SIP messages from Cisco Unified CM. The default setting equals 5060.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
SIP Profile Settings
Figure 3-18 shows the SIP Profile Settings page.
Figure 3-18 SIP Profile Settings
To configure or edit SIP Profile settings:
Step 1
Click Unified CM under Configure in the left navigation.
Step 2
Click the SIP Profile Settings tab.
Step 3
Enter or edit settings as described in Table 3-13.
Table 3-13 SIP Profile Settings
Field or Button
|
Setting
|
Retry Count for SIP Invite
|
Specifies the number of times that Cisco Unified Communications Manager (Cisco Unified CM) will resend the INVITE message. This is a required field. Minimum is 1. Maximum is 10 Default is 6.
|
Retry Count for SIP non-Invite Request
|
Specifies the number of times that Cisco Unified CM will resend the non-INVITE message. This is a required field. Minimum is 1. Maximum is 10 Default is 6.
|
SIP Expires Timer
|
Specifies the maximum time that an INVITE message remains valid. If Cisco Unified CM has not received an answer before this timer expires, Cisco Unified CM tears down the call. This is a required field. Minimum is 60000 (msec). Maximum is 300000 (msec). Default is 180000 (msec).
|
SIP Timer T1
|
Specifies the lowest value, in milliseconds, of the retransmission timer for SIP messages. Valid values include any positive number. Default specifies 500.
|
SIP Timer T2
|
Specifies the highest value, in milliseconds, of the retransmission timer for SIP messages. Valid values include any positive number. Default specifies 4000.
|
Start Media Port
|
Designates the start real-time protocol (RTP) port for media. Media port ranges from 16384 to 32766. Default specifies 16384.
|
Stop Media Port
|
Designates the stop real-time protocol (RTP) port for media. Media port ranges from 16384 to 32766. Default specifies 32766.
|
Device Security
|
Specifies the type of security applied to this CTMS. Available choices are:
• Non-Secure (Trusted Trunk with media encryption if the Media Encryption checkbox is checked)
• Authenticated
• Encrypted with SDP Keys (recommended if using Cisco Unified CM version 7.0 or later)
For more information about Device Security, see Security.
|
Media Encryption
|
Click this checkbox if you want to have non-secure SIP signaling mode but with encrypted media.
Note This field is displayed only when the meeting security policy is secure.
|
Transport Layer Protocol
|
Defines the transport protocol used. Available choices are:
• TCP
• UDP
Transport Layer Security (TLS) is automatically selected or filled in when "Authenticated" or "Encrypted with SDP Keys" is chosen for Device Security.
Note Whenever the transport type is modified in CTMS, the corresponding transport type for the Cisco Unified CM trunk setting must be changed to match the CTMS transport type.
|
•
To register new or modified settings, click Apply.
•
To restore the original settings, click Cancel.
WebEx
The WebEx page, which is shown in Figure 3-19, enables you to configure the Cisco TelePresence WebEx OneTouch feature to work with the CTMS.
Note
After you finish your configuration, you must click Apply to save your changes. After clicking Apply, you will be prompted to restart the CTMS processes, which will cause all active TelePresence meetings to end immediately. Therefore, you must plan your Cisco WebEx configuration accordingly. If you do not want to restart the processes, you can click Cancel, in which case, your Cisco WebEx configuration will not be saved.
Note
To set up a Cisco WebEx proxy server, the CTMS must be running release 1.7.2 or later.
Figure 3-19 WebEx
For complete information on performing this configuration, see the Cisco TelePresence WebEx OneTouch Configuration Guide for the Cisco TelePresence System, which is available at this location:
http://www.cisco.com/en/US/products/ps8332/products_installation_and_configuration_guides_list.html