Configuring CTS-Manager

Table Of Contents

Configuring Cisco TelePresence Manager

Contents

Introduction

Security Settings

Database

Settings

Backup

Restore

Restoring Backup Data

Calendar Server

IBM Domino

Re-sync Operations

Microsoft Exchange

Re-sync Operations

LDAP Server

Settings

Field Mappings

Microsoft Exchange Deployments

IBM Domino Deployments

Discovery Service

MCU Devices

Cisco TelePresence Multipoint Switch (CTMS)

Cisco Unified Video Conferencing (CUVC)

Concierges

Access Management

Policy Management

System Settings

IP Setting

NTP Setting

SNMP Setting

Remote Account

Password

System

Application Settings

Software Upgrade

Upgrading to Cisco TelePresence Manager 1.5

Switch Version

Upgrade Software

CTS-Manager Redundancy Failover Procedure

Cold Standby

Warm Standby

Configuring Cisco TelePresence Manager

---

Revised: February 25, 2009, OL-13673-04
First Published: November 27, 2006

Contents

•Introduction

•Security Settings

–Generating Security Certificate Reports

–Viewing Security Certificates

–Deleting Security Certificates

–Uploading Security Certificates

•Database

–Settings

–Changing the Backup Schedule

–Backing Up Database Files

–Viewing Backup History

–To restore data from a backup:

•IBM Domino

–Re-sync Operations

•Microsoft Exchange

–Re-sync Operations

•LDAP Server

–Settings

–Microsoft Exchange Deployments

–IBM Domino Deployments

•Discovery Service

•MCU Devices

–Cisco TelePresence Multipoint Switch (CTMS)

–Cisco Unified Video Conferencing (CUVC)

•Concierges

•Access Management

–Assigning Roles to Groups Using Domino Directory Assistance

•Policy Management

•System Settings

–IP Setting

–NTP Setting

–SNMP Setting

–Remote Account

–Password

–System

•Application Settings

•Software Upgrade

Introduction

The administrator makes use of the System Configuration window to perform such tasks as upgrading system software, synchronizing system databases, managing security, and reconfiguring system settings.

Figure 3-1 shows the system configuration tasks.

Figure 3-1 Cisco Telepresence Manager System Configuration Window

Security Settings

The Security Settings window assists with managing system security certificates and web services security.

Figure 3-2 System Configuration Security Settings Window

Web Services Security

You can turn on web services security by choosing Secure mode. For more information refer to the Cisco TelePresence Security Solution documentation on Cisco.com.

---

Caution Unified CM and any CTMS registered with CTS-Manager must be configured and set to secure mode before downloading CAPF certs, LSCs, and setting CTS-Manager to secure mode. If secure mode is not established in this order, you may need to restart the CTI manager in Unified CM and restart CTS-Manager in order for secure mode to work properly.

---

Digital Security Certificates

CTS-Manager supports the following security certificates:

•Tomcat—Security Keystore to store self-generated Apache Tomcat certificates.

---

Note CTS-Manager does not support replacing the default Tomcat certificate with any other certificate.

---

•CTM-trust—CTS-Manager Security Keystore to store digital certificates for Microsoft Exchange or IBM Domino, Directory Server, and Cisco Unified CM.

Generating Security Certificate Reports

You can generate a list of certificates containing a specific category and unit by supplying the following criteria:

•Choose All, Own, or Trust from the Category drop-down list.

•Choose All, CTM-trust, or Tomcat from the Unit menu.

•Click Filter to generate the list of certificates that match the search criteria.

Viewing Security Certificates

To view the contents of a security certificate click the radio button next to the certificate unit name and click View.

The contents of the certificate can be copied and pasted in a text file.

Deleting Security Certificates

To delete a CTM-trust type security certificate, click the radio button next to the certificate unit name and click Delete.

---

Note CAPF-LSCs and CAPF-trust certificates and tomcat cannot be deleted. To remove them, set Web Security to "Unsecure." Setting Web Security to unsecure triggers the deletion process.

---

Uploading Security Certificates

To display the Certificate Upload window, from which you can copy a security certificate to Cisco TelePresence Manager, click Upload.

---

Caution You cannot upload a certificate of the same name. You should delete the existing certificate before uploading a new one.

---

---

Step 1 In the Certificate Upload window, choose the category and unit for the certificate.

Step 2 Click Browse to choose a location where a certificate file is located, and add it to the Certificate field.

Step 3 Click Upload to copy the file.

Step 4 Click Close to close the Certificate Upload window.

---

Database

CTS-Manager uses an Informix database server to store information. The Database window allows the Administrator to view the database status and run backup and restore operations. Open the Database window to see the following choices:

•Settings

•Backup

•Restore

Settings

The Settings window allows you to manage the size and age of meeting information in the Informix database. To register new settings, click Apply. To return to the original settings, click Reset.

Figure 3-3 Database Window Settings Tab

Table 3-1 describes the information and settings that are accessible from the Database window Settings tab.

Table 3-1 Database Settings 

Field	Description or Settings
Service Status	Display-only status report of the Informix database server.
Current Database Size	Display-only report showing the size of the database as a percentage of the amount of total space available for a Cisco TelePresence Manager account in Directory Server. The number displayed should not exceed 75%.
Automatically purge data older than (months)	Sets the number of months of storage for the information in the database. Data older than the specified number of months is purged. The purge cutoff date for this setting should be selected by balancing the number of months of data retention against the size of the database required to store the data created during that period. The default setting of 1 month is considered a reasonable midpoint. Note Database utilization cannot exceed 75% of the allocated disk space, and takes precedence. If the number of months you have specified exceeds this percentage, older data is purged so as not to exceed 75%.

Backup

Choose the Backup tab to display fields and settings that will assist you in scheduling backups of the database. It is important to keep the backup current in case you need to activate the backup CTS-MAN system.

Figure 3-4 System Configuration - Database Window Backup Tab

Changing the Backup Schedule

The backup schedule currently set is displayed in the Backup window.

To change the backup schedule:

---

Step 1 Click Change.

Step 2 Choose the starting time from the Start Time drop-down list. This sets the backup time in your local timezone.

Step 3 Choose the frequency of the backups by clicking the Daily or Weekly radio button.

---

Note If you click Weekly, check the box for the day of the week on which the backup should occur.

---

Step 4 Click OK to register your settings, or Cancel to restore the original settings

---

To register new or modified settings, click Apply. To restore the original settings, click Reset.

---

Note Backup schedules are now displayed in your local timezone.

---

Backing Up Database Files

Data backups are performed on the Active partition. If you switch partitions after performing a backup you'll need to perform another backup for the new Active partition. See Switch Version for more information.

To back up files in the database:

---

Step 1 From the drop-down list, choose the number of backup files to keep. If you choose 3, the last three backup files will be kept, but earlier backup files will be purged.

---

Note If you are creating remote backups the number of backup files is not affected. CTS-Manager only keeps track of the number of backups made locally.

---

Step 2 Choose the type of backup by clicking the Local or Remote radio button.

Step 3 Test your connection to a remote host by clicking Verify Remote Host.

Step 4 Click backup Now to begin the operation.

---

Remote Storage Host Fields

A remote backup uses Secure FTP (SFTP) or FTP to store files remotely. If you choose to backup or restore using FTP, you do not need to supply a port number.

---

Note FTP scripts for Upgrade, Backup and Restore use Expect scripts and perform on a best-effort basis, due to potential variations in the responses sent by the FTP server. Only username/password-based login is supported. Anonymous login is not supported.
Secure FTP (SFTP) is the recommended mode of transferring files over the network.

---

You must fill in the following fields to gain access permissions to a remote host:

Table 3-2 Remote Storage Host Fields 

Field	Description
Remote Storage Host	Pathname of the remote host.
Port	Port to access the remote host. The default is port 22 for SFTP.
Username	Login name for the remote server.
Password	Password to access the remote server.
Storage Path	The full pathname where you want to store the backup files.

Viewing Backup History

The Database window Backup tab provides a history of database backups.

Table 3-3 describes the Backup History and Restore History fields.

Table 3-3 Backup History and Restore History Fields 

Field	Description
Timestamp	Date and time of backup. Click the arrow in the header of the Timestamp column to sort the list in ascending or descending order.
Status	Status of the backup.
Type	Type of backup, either local or remote.
Hostname	Name of host for the backup files.
Location	Pathname where the files are stored.

Restore

The Restore tab displays the history of the database restore operations. See Table 3-3 for a description of the fields.

Figure 3-5 Database Window Restore Tab

Restoring Backup Data

When you restore data from a backup file, all changes made to the database since the backup will be lost. These changes must be added by the Exchange Sync Up and Discovery functions of the Cisco TelePresence Manager server. The database Restore function should be run only as a last resort; for example, when the database is corrupted or the disk fails and has to be replaced.

The restore operation will stop the Informix database server, so some CTS-Manager operations might be impacted during the operation. While the restore operation is in progress, all other processes are stopped. The user interface will only display progress of the restore operation. When the restore operation is complete, the Cisco Telepresence Manager is automatically restarted and the login page is displayed. You will have to login to resume use of the Cisco Telepresence Manager application.

---

Note You cannot restore the database from previous versions of CTS-Manager.

---

To restore data from a backup:

Clicking Restore Now displays a window listing all the backups stored locally and remotely. If you want to restore from a backup stored remotely you must first click the Network Restore Type radio button. Then choose either the SFTP or FTP Restore Mode and enter required information to access the remote host. See Table 3-2 for a description of the Remote Storage Host fields.

---

Step 1 Click the Refresh button to view the list of backups.

Step 2 Click the radio button next to the backup filename that is to be used for the restore operation.

Step 3 Click Restore Now. This action initiates a full restore of the database from the backup file.

---

Calendar Server

If you did not specify a Calendar server (either Microsoft Exchange or IBM Domino) during the initial installation, the Calendar Server window displays the Calendar Server wizard.

The Calendar Server wizard leads you through a four-step process to register a Calendar server with CTS-Manager.

---

Note The LDAP server you specified during initial installation determines if you will be able to sync any Cisco TelePresence endpoints with the Calendar server you are registering. The LDAP server you are using must match the Calendar server you are registering.

---

The No Calendar Server window displays the Configure Now button to initiate the Calendar Server wizard.

Figure 3-6 Configure Calendar Server

---

Step 1 The first step in registering a Calendar server with CTS-Manager is to choose either IBM Domino or Microsoft Exchange.

Figure 3-7 Cisco TelePresence Manager - Calendar Server Selection Screen

Step 2 In the second step you need to specify the service logon information. The example below displays the information needed to use the Microsoft Exchange service.

Figure 3-8 Cisco TelePresence Manager - Calendar Server MicroSoft Exchange Screen

Step 3 Click Apply to save the new Calendar server settings.

Figure 3-9 Cisco TelePresence Manager - Calendar Confirmation Screen

Step 4 Then click OK to restart the CTS-Manager server.

Figure 3-10 Apply Changes Screen

Step 5 Once the server has restarted, click Continue to re-launch the CTS-Manager server and log in.

Figure 3-11 System Restart Notification Screen

---

Caution If the Calendar service you are registering with does not match the LDAP server you specified during initial installation the wizard will display all the Cisco TelePresence endpoints that will not sync with the new Calendar service. You can proceed with the Calendar service you have chosen, but meeting organizers will not be able to use the endpoints to schedule meetings.

---

---

IBM Domino

The IBM Domino window helps you manage the database that stores TelePresence meeting information.

To test the connection between this system and the Domino server, as shown in IBM Domino Calendar Service Window:

---

Step 1 Click Test Connection.

Step 2 To register new or modified settings, click Apply.

Step 3 To restore the original settings, click Reset.

---

Figure 3-12 IBM Domino Calendar Service Window

Table 3-4 describes the information and operations accessible from this window.

Table 3-4 IBM Domino Server 

Field or Button	Description or Settings
Service status	Display-only status report of system service.
Mailbox Usage	Meeting information is mailed to users. This display-only field reports the amount of storage space taken up by the emails as a percentage of total space available.
Host	Hostname provided for the Domino server account, which can be modified.
Bind Method	Choose the Secure or Normal radio button to select the binding method, as follows: •Secure—CTS-Manager communicates with the Domino server in secure mode using HTTPS. This method requires enabling Secure Socket Layer (SSL). on the Domino server. •Normal—CTS-Manager communicates with the Domino server in cleartext using HTTP.
Port	Communication port number.
Organization Name	Domain name provided for the Domino server account, which can be changed.
Username	This is the account name used to log on to the Domino server.
Password	Password used to access the Domino server account, which can be changed. Note Make sure the Internet password is used in the Password fields in the System Configuration> IBM Domino window and the LDAP Server window.
Polling Interval (minutes)	Specifies the time interval, in minutes, to poll the Domino server for meeting information.
Certificate	Use the field to provide an IBM Domino trust certificate class file. Note A certificate is required in secure mode only.

Re-sync Operations

The Re-sync Operations area tells you when information in the Domino server database was last updated with meetings scheduled for a particular room.

When mismatched information in the databases causes meeting conflicts or there are other problems that prevent a meeting from being launched successfully, this area of the IBM Domino window allows you to synchronize information between Domino and the CTS-Manager database. Synchronization takes time and system resources to accomplish and should be done only when necessary.

To synchronize information between Domino and the CTS-Manager database:

---

Step 1 Click Re-sync to start the operation.

Once you've begun the Re-sync operation the Service Status field displays a Sync progress indicator showing the progress of the Re-sync operation by percentage.

Step 2 Once the synchronization operation completes, click Refresh to update the display.

---

Table 3-5 describes the information displayed in this area of the IBM Domino window.

Table 3-5 IBM Domino Server Synchronization Report

Field	Description
Domino Databases	Name of the meeting room. Click the arrow in the header of the Room Name column to sort the list in ascending or descending alphabetical order.
Last Synchronization Time	Time the synchronization operation was started.
Resynchronization Status	Status of the synchronization operation.
Associated Rooms	Name of the Cisco TelePresence meeting rooms associated with the Domino database. Note The room name displayed is the name of the room in the Domino database. In order for CTS-Manager to successfully sync the room's meeting calendar, the room name must exactly match the room name in the Cisco TelePresence System profile registered in Unified CM.

Microsoft Exchange

The Microsoft Exchange window helps you manage the database that stores meeting information.

To test the connection between this system and the Microsoft Exchange server as shown inMicrosoft Exchange Calendar Service Window:

---

Step 1 Click Test Connection.

Step 2 To register new or modified settings, click Apply.

Step 3 To restore the original settings, click Reset.

---

---

Note CTS-Manager only supports Microsoft Windows Server 2003, Enterprise Edition.

---

Figure 3-13 Microsoft Exchange Calendar Service Window

Table 3-6 describes the information and operations accessible from this window.

Table 3-6 Microsoft Exchange Server 

Field	Description or Settings
Service status	Display-only status report of system service.
Mailbox Usage	Meeting information is mailed to users. This display-only field reports the amount of storage space taken up by the e-mails as a percentage of total space available.
Host	Hostname provided for the Microsoft Exchange server account, which can be modified.
Bind Method	Choose the Secure or Normal radio button to select the binding method, as follows: •Secure—CTS-Manager communicates with the Microsoft Exchange server in secure mode using HTTPS. This method requires enabling Secure Socket Layer (SSL). on the Microsoft Exchange server. •Normal—CTS-Manager communicates with the Microsoft Exchange server in cleartext using HTTP.
Port	Communication port number.
Domain Name	Domain name provided for the Microsoft Exchange server account, which can be changed.
Logon Name	This is the account name used to log on to the Microsoft Exchange server. The value is dependent on the AD/Exchange configuration. For example, it is either ctsappaccount@mycompany.com or ctsappaccount.
SMTP LHS	This is the left hand side (LHS) of the SMTP address for the account specified by the Logon Name. If the full SMTP address is ctsappsmtp@mycompany.com enter ctsappsmtp in this field.
Password	Password used to access the Microsoft Exchange server account, which can be changed.
Certificate	Use the field to provide a trust certificate for new Microsoft Exchange server.
Number of Meetings Per Query	The maximum number of meetings that Cisco TelePresence Manager can retrieve from the Exchange server for each query.

Re-sync Operations

The Re-sync Operations area tells you when information in the Microsoft Exchange server database was last updated with meetings scheduled for a particular room.

When mismatched information in the databases causes meeting conflicts or there are other problems that prevent a meeting from being launched successfully, this area of the Microsoft Exchange window allows you to synchronize information between Microsoft Exchange and the CTS-Manager database. Synchronization takes time and system resources to accomplish and should be done only when necessary.

To synchronize information between Microsoft Exchange and the CTS-Manager database:

---

Step 1 Check the boxes next to the rooms to select them. To synchronize information for all meeting rooms, check the box next to Room Name in the display header.

Step 2 Click Re-sync to start the operation.

Once you've begun the Re-sync operation the Service Status field displays a Sync progress indicator showing the progress of the Re-sync operation by percentage.

Step 3 Once the synchronization operation completes, click Refresh to update the display.

Step 4 Once the synchronization operation completes, click Refresh to update the display.

---

Table 3-7 describes the information displayed in this area of the Microsoft Exchange window.

---

Note A maximum of 100 rooms are displayed per page. If you have more than 100 rooms registered with Cisco TelePresence Manager you can click the Next button to display the additional rooms.

---

Table 3-7 Microsoft Exchange Server Synchronization Report

Field	Description
Room Name	Name of the meeting room. Click the arrow in the header of the Room Name column to sort the list in ascending or descending alphabetical order.
Last Synchronization Time	Time the synchronization operation was started.
Subscription Status	Status of the synchronization operation. Click the arrow in the header of the Room Name column to sort the list in ascending or descending alphabetical order.

LDAP Server

CTS-Manager uses Lightweight Directory Access Protocol (LDAP) to retrieve information related to users and conference rooms from Directory Server deployments. Enterprises typically use specialized databases called directories to store information related to users, meeting rooms, and so on. LDAP is a protocol for accessing directories.

---

Note CTS-Manager only supports English language-based Active Directory installations.

---

This window specifies LDAP Directory Server server settings that are used by CTS-Manager to access the directory information. Open the LDAP Server window to see the following choices:

•Settings

•Field Mappings

Settings

The Settings window is where you make changes to the LDAP server after first-time installation.

Figure 3-14 LDAP Window Settings Tab

Multiple LDAP Peer Domains

If you have a LDAP peer domain configured you'll need to specify the additional user containers and context. You can do this with one of the User Container fields.
For example, cn=users,dc=domain2,dc=com
When specifying the container and context information for your peer domain, DO NOT check the Append default context box.

---

Note LDAP containers configured for use with CTS-Manager should not be specified in such a way where one container is the child of the other. This requirement includes specifying the default context.

---

Table 3-8 describes the settings for this window.

Table 3-8 LDAP Server Settings 

Field or Button	Description or Settings
Service Status	Display-only status of the service.
Host	LDAP server host name.
Bind Method	Click the Secure or Normal radio button to select the binding method: •Secure—Secure SSL connection requires the Distinguished Encoding Rules (DER) Certificate for the LDAP server. •Normal—CTS-Manager communicates with the Microsoft Exchange or IBM Domino server in cleartext using HTTP.
Port	The default port for secure connection is 636. The default port for normal connection in a single LDAP server deployment is 389. In cases where deployments consist of multiple LDAP Directory Servers, this port should be configured with 3268, which is the Global Catalog port.
Default Context	The default context from which the LDAP queries are performed. To change the context string: •Click the Fetch DNs button and choose the context from the Fetch DNs drop-down list adjacent to this field.
Username	The username used to authenticate to the LDAP server. This must be in the LDAP fully qualified domain name (FQDN) format. Example: cn=administrator,cn=users,dc=<mydomain>,dc=com)
Password	Password to access the LDAP server.
Certificate	The name of the LDAP certificate. This is only needed if you have chosen the Secure Bind Method.
Connection pool size	The number of concurrent connections used by the Cisco TelePresence Manager server to retrieve data from the LDAP server. This is primarily used for optimizing the server's access to the LDAP server.
User containers	The containers from which queries are performed to retrieve user objects. More than one user container or user object can be specified. The Cisco Telepresence server uses the values entered to search through the containers in sequence to retrieve user and meeting room information from the Directory Server. Additionally, these containers are used to retrieve user information for authentication. •To append the default context, check the Append default context box next to the user container field. Note If you have a LDAP peer domain configured you'll need to specify any user containers and context. For example, "cn=users,dc=domain2,dc=com". When specifying the container and context information for your peer domain, DO NOT check the Append default context box.

To test the connection between this system and the LDAP server, click Test Connection.

To register new or modified settings, click Apply.

To restore the original settings, click Reset

Field Mappings

The CTS-Manager server uses application objects and attributes that are internally mapped to the objects and attributes in the LDAP Directory Server. Most of these mappings are predefined and fixed. However, some of the information required for the Cisco TelePresence system may be stored in different attributes of the LDAP Directory Server, based on the enterprise deployment. The Field Mapping window provides a mechanism to map such objects and attributes used by the CTS-Manager server to the object and attributes defined in the LDAP Directory Server schema.

Microsoft Exchange Deployments

The attributes are used by the Exchange server to store the user's e-mail and display name information. For most of the Exchange deployments, this information should not be changed.

CTS-Manager supports connection to multiple LDAP domains/servers that belong to a single Active Directory forest. Some of the setups with which CTS-Manager can work are peer-peer LDAP domain setup, and Parent-Child LDAP domain setup.

---

Caution The object and attribute mappings for Exchange/Directory Server deployments are listed in Table 3-9 and cannot be changed after installing and configuring Cisco TelePresence Manager. Cisco TelePresence Manager may not functions properly if the Object Class fields are changed.

---

Figure 3-15 LDAP Window Field Mappings Tab

Table 3-9 LDAP Objects and Attributes 

Application Object	Application Attribute	LDAP Object Class	LDAP Attribute
Person
	SchedulerName	Person	proxyaddresses Note Do not change this value. If this value is changed incorrectly, meetings will not have the correct information.
	EmailID	Person	proxyAddresses
	DisplayName	Person	displayname
EnterpriseConfRoom
	EmailID	Person	proxyAddresses
	DisplayName	Person	displayname

Verifying Field Mapping Data

Verify that the data retrieved is as you expected. If data is incorrect, the application will not operate correctly.

Click View Sample Data to retrieve objects based on the mappings specified.

---

Caution Setting the LDAP objects and attributes used by the Exchange server requires experience using Directory Server and Exchange software. Do not change the proxyAddresses value in the LDAP SchedulerName Attribute field.
The majority of deployments do not require any changes to these attributes. Incorrectly changing these fields will result in Cisco TelePresence Manager not being able to function.
Consult the Cisco TelePresence Manager support team and the LDAP and Exchange server administrator for your deployment before changing the default mappings in these screens.

---

IBM Domino Deployments

These attributes are used by the Domino LDAP server to retrieve the user's e-mail and display name information. For most of the Domino deployments, this information should not be changed.

CTS-Manager supports a Domino deployment with a single domain. CTS Manager can be configured against one Domino server only. In a cluster environment, all resource reservation databases that contain a Cisco TelePresence room's reservations must be replicated to the Domino server that CTS-Manager is configured against. Users in Directory Assistance database configured with external LDAP servers are not supported.

---

Caution The object and attribute mappings for Domino/Directory Server deployments are listed in Table 3-10 and cannot be changed after installing and configuring CTS-Manager.

---

Figure 3-16 LDAP Window Field Mappings Tab

Table 3-10 LDAP Objects and Attributes 

Application Object	Application Attribute	LDAP Object Class	LDAP Attribute
Person
	SchedulerName	Person	cn Note Do not change this value. If this value is changed incorrectly, meetings will not have the correct information.
	EmailID	Person	cn
	DisplayName	Person	cn

Verifying Field Mapping Data

Verify that the data retrieved is as you expected. If data is incorrect, the application will not operate correctly.

Click View Sample Data to retrieve objects based on the mappings specified.

---

Caution The Object Class field and the LDAP Attribute field do not need to be changed. Cisco TelePresence Manager may not function properly if the Object Class fields and LDAP Attribute fields are changed.

---

---

Caution Setting the LDAP objects and attributes used by the Domino server requires experience using Directory Server and Domino software. Do not change the cn value in the LDAP SchedulerName Attribute field.
The majority of deployments do not require any changes to these attributes. Incorrectly changing these fields will result in Cisco TelePresence Manager not being able to function.
Consult the Cisco TelePresence Manager support team and the LDAP and Domino server administrator for your deployment before changing the default mappings in these screens.

---

Discovery Service

To display and modify settings that associate CTS-Manager with Unified CM, choose Discovery Service in System Configuration.

To test the connection between Cisco TelePresence Manager and Cisco Unified Communications Manager, click Test Connection.

To manually start the process that is periodically performed to discover new rooms added to Unified CM, click Discover Rooms.

---

Note This process consumes a large amount of system processor time. System operation will be noticeably slower from the time that the Discover Rooms button has been clicked until the process is completed.

---

To register new or modified settings, click Apply. To restore the original settings, click Reset.

Figure 3-17 Discovery Service Window

Table 3-11 describes fields, buttons, and settings.

Table 3-11 Cisco Unified Communications Manager Settings 

Field	Description or Settings
Service Status	Display-only status report of system services. Note You may see a progress indicator in the status field, especially if many Cisco TelePresence meeting rooms are being managed by CTS-Manager. Each time this page is accessed, the status is updated, and the progress indicator will be seen while the system is discovering meeting rooms.
Host	Name of the Cisco Unified CM server host.
Username	Username for login to the Cisco Unified CM server.
Password	Password to access the Cisco Unified CM server.
Certificate	Use the field to provide a trust certificate for new Cisco Unified CM server.

MCU Devices

The MCU Devices window provides the ability to add and delete MCU devices. There are two MCU devices supported by CTS-Manager—Cisco TelePresence Multipoint Switch (CTMS) and Cisco Unified Video Conference device (CUVC).

The MCU Devices support screen displays several attributes for each MCU device registered with Cisco TelePresence Manager.

---

Caution If the MCU devices has a reinstall the device must be registered through Cisco TelePresence Manager. There are no errors generated by the MCU device software change. The Cisco TelePresence Multipoint Switch Administrator must inform you of the change.

---

Figure 3-18 MCU Devices Window

Table 3-12 describes the MCU Device fields.

Table 3-12 MCU Devices

Field	Description or Settings
Hostname	The hostname or IP address of the MCU. Clicking the hostname hyperlink opens a new browser window, with the CTMS login page.
Type	The MCU Type is either CTMS or CUVC.
Control state	The Control state is either Scheduled or Non-Scheduled
Description	The Description field displays the MCU device description, added when the MCU device was added.
IP Address	The IP address of MCU.

Deleting a MCU

A Multipoint Conference Unit cannot be deleted if there are any associated scheduled meetings. If the MCU is a CUVC, with associated scheduled meetings, you must first Deallocate the CUVC resources before you can delete the device.

To delete a MCU Device, click the radio button next to the device and click Delete.

Refreshing the list of MCUs

Click the Refresh button to refresh the list of MCU devices.

---

Note Once Interop has been enabled (see Application Settings), a CTMS device can only be added to CTS-Manager if it is interop-ready. An interop-ready device is defined as running a certain level of software release. Refer to the software compatibility matrix in your CTS-Manager Release Note.

---

Cisco TelePresence Multipoint Switch (CTMS)

A CTMS communicates with the Cisco TelePresence Manager. CTMSs provide the functionality for three or more Cisco TelePresence rooms to attend a conference call. Cisco TelePresence Manager provides the scheduling information to the different CTMSs and each CTMS provides the multipoint switching capabilities for the conference.

Adding a CTMS

To register additional CTMS devices with Cisco TelePresence Manager, click New to display the Registration dialog box, and choose CTMS from the Type drop-down field.

Figure 3-19 Adding New CTMS - MCU Devices Window

Table 3-13 Registering a CTMS with Cisco TelePresence Manager 

Field	Description or Settings
Type	CTMS or CUVC are the only MCU types. If only CTMS appears in the drop-down list, Interop has not been enabled. Use the Application Settings window to enable Interop.
MCU Host Name	The hostname or IP address of the CTMS. This is the LHS of the complete Host name.
Username	This is the account name used to log into the CTMS.
Password	This is the account password used to log into the CTMS.
Control State	Specify whether the CTMS is available (scheduled) for meetings. The resources of a scheduled CTMS can be used when meetings are scheduled. Specifying a CTMS as Non-Scheduled means the CTMS will not be used when a meeting is scheduled. Note CTMSs in a Scheduled state cannot be used to migrate meetings from other CTMSs.

Editing CTMS Settings

To edit CTMS registration information, click the radio button next to the device and click Edit. The following table describes the CTMS settings that may be changed.

Table 3-14 Editing Registered CTMS Configuration Settings

Field	Description or Settings
Username	This is the account name used to log into the MCU.
Password	This is the account password used to log into the MCU.
Control State	Specify whether the MCU is available for meetings. The resources of a scheduled MCU can be used when meetings are scheduled. Specifying a MCU as Non-Scheduled means the MCU will not be used when a meeting is scheduled. Note CTMSs in a Scheduled state cannot be used to migrate meetings from other CTMSs.

Cisco Unified Video Conferencing (CUVC)

CTS-Manager support of CUVC enables video conferencing devices to join a scheduled Cisco TelePresence meeting. A CUVC is notified by and joins a Cisco TelePresence meeting through a CTMS. A CTMS device must be used to enable video conferencing devices to join, even if it is a point-to-point call.

---

Note Only one CUVC can be registered with CTS-Manager.

---

Adding a CUVC

To a CUVC device with Cisco TelePresence Manager, click New to display the Registration dialog box, and choose CUVC from the Type drop-down field.

Table 3-15 Registering a CUVC with Cisco TelePresence Manager 

Field	Description or Settings
Type	CTMS or CUVC are the only MCU types. If only CTMS appears in the drop-down list, Interop has not been enabled. Use the Application Settings window to enable Interop. Note Only one CUVC may be registered with CTS-Manager.
MCU Host Name	This is the LHS of the complete Host name.
Control State	Specify whether the CUVC is available (scheduled) for meetings. The resources of a scheduled CUVC can be used when meetings are scheduled. Specifying a CUVC as Non-Scheduled means the CUVC will not be used when a meeting is scheduled.
Access Number Prefix for CTMS	The access number prefix for your CTMS is based on your enterprise dialing plan.
Access Number Prefix for Video Conferencing Participants	This access number prefix is based on your enterprise dialing plan.
Conference ID Length	The Conference ID can be 1-8 digits in length. The system-generated Conference ID is used to create an Interop Access Number used by the CTMS to establish the conference call. It is also used to create the Interop Access Number sent in an email to meeting participants, as the dial-in phone number. The Conference ID length is based on your enterprise dialing plan.
Multiple EMP Cards Support	Enabling EMP card support provides additional resources to support a greater number of video calls using the CUVC. CTS-Manager with EMP card support enabled allows up to 48 video calls per EMP card. Note If you are using a CUVC 3515 MCU this option is disabled.
Number of EMP Cards	Specify the number of EMP cards installed in the CUVC device.
Maximum Participants per Conference	Enter a numeric value for the maximum number of meeting participants that may dial into the conference call.
Minimum Participants per Conference	The minimum value for this field is 2. This value cannot exceed the Maximum Participants per Conference value.
Total Resources	This value should be greater than the Maximum Participants per Conference. Note If you have enabled EMP card support the values in the Total Resources field and the Minimum Participants per Conference field are calculated for you. The calculation is Number of EMP Cards x Maximum Participants per Conference.

Editing CUVC Settings

To edit CUVC registration information, click the radio button next to the device and click Edit. The following table describes the CUVC settings that may be changed.

Table 3-16 Editing Registered CUVC Configuration Settings 

Field	Description or Settings
Control State	Specify whether the CUVC is available for meetings. The resources of a scheduled CUVC can be used when meetings are scheduled. Specifying a CUVC as Non-Scheduled means the CUVC will not be used when a meeting is scheduled. Note If there are scheduled interop meetings you can't change a CUVC state to non-scheduled.
Access Number Prefix for CTMS	The access number prefix for your CTMS is based on your enterprise dialing plan.
Access Number Prefix for Video Conferencing Participants	This access number prefix is based on your enterprise dialing plan.
Number of EMP Cards	This value in this field can be changed if Multiple EMP Card support is enabled.
Maximum Participants per Conference	Enter a numeric value for the maximum number of meeting participants that may dial into the conference call. Note The value in this field affects the number of CTMS resources reserved for a specific conference call.
Minimum Participants per Conference	The minimum value for this field is 2. This value cannot exceed the Maximum Participants per Conference value.
Total Resources	This value should be greater than the Maximum Participants per Conference.

Concierges

The Concierges window has two areas, a list of concierges and a list of rooms that need a concierge assigned to them. Use the areas in this window to assign a concierge to a meeting room.

A phone number is associated with the concierge, which is displayed on the Cisco TelePresence meeting room phone user interface when the Concierge soft key is pressed. Meeting participants can dial the concierge and ask for help when problems occur with the Cisco TelePresence system.

Figure 3-20 System Configuration - Concierge Window

Creating Concierges

•Click New to display the New Concierges window.

You must enter an identifier for the concierge in the ID field and a phone number in the Phone Number field.

Figure 3-21 Adding a Concierge Window

You can choose to supply other information identifying the concierge in the Description field.

When putting information in the Concierge Description Field do not use a Carriage Return or line feed, sometimes referred to as <CR> between words (do not hit return key).

All Cisco TelePresence rooms must be assigned to a Concierge. If you haven't specified a Concierge for a room, the System installed <Unassigned> Concierge is the default Concierge for all rooms discovered in CTS-Manager. You can change the default Concierge to a specific Concierge by checking the Set as Default checkbox in the Concierge details window. Any Cisco TelePresence room discovered by CTS-Manager will be assigned to the new default Concierge. Each time you specify a different Concierge as the default, all future rooms discovered by CTS-Manager will be assigned to the new default.

Assigning a Room to a Specific Concierge

Once concierges have been registered, assign them meeting rooms as follows:

---

Step 1 Check the box next to a room that has not been assigned.

Step 2 Select a concierge from the Assign Selected Rooms drop-down list.

Step 3 Click Apply.

To edit the concierge assignment:

Step 4 Select the radio button next to the concierge ID and click Edit.

Step 5 In the Edit Concierges window, you can change the phone number and other information identifying the concierge.

Step 6 To delete a concierge, select the radio button next to the concierge ID and click Delete.

---

---

Note CTS-Manager 1.5 supports a default concierge that is assigned to endpoints that have no specific concierge assignment. Earlier versions of CTS-Manager allowed more than one concierge to have the same phone number. If you are upgrading to version 1.5 from an earlier version that allows a concierge to share a phone number with another concierge, during the upgrade CTS-Manager 1.5 changes the phone number of one of the concierges and assigns that concierge to the endpoint.

---

Access Management

From the Directory Server, it is possible to create groups, such as a Concierge group and an Admin group. Use this window to view and create roles for these groups. CTS-Manager supports two roles—a concierge and an administrator.

The two roles have different levels of privilege and access when using CTS-Manager. Members in the group mapped to the Concierge role have limited privileges that allow them to view the meetings, rooms, and system error and log files. Members in the group mapped to the Administrator role have the privileges of the Concierge role plus additional privileges that allow them to make configuration changes.

Figure 3-22 Access Management Window

Assigning Roles to Groups Using Domino Directory Assistance

If your Cisco TelePresence Manager deployment is working with an IBM Domino Server and Domino Directory Assistance, it is possible for the group to contain a user from an external directory. That type of external user cannot be granted the CTS-Manager Administrator role. Only members of groups local to the IBM Domino Directory may be granted the Administrator role.

You can generate a report about specific LDAP Group mappings, as follows:

•Choose the role—All, Administrator, or Concierge—from the Role drop-down list.

•Click Filter.

---

Caution When assigning different Directory Server groups to a role, the Add window may not list the group or groups you want to add. This is an Directory Server limitation when the number of groups returned by the query exceeds 500. If this occurs, click the Manual radio button in the Add window, specify the Group FQDN you are searching for and assign either the Concierge or Administrator role.

---

Policy Management

The Policy Management window lists the three default policies to support scheduling and conference termination:

Figure 3-23 System Configuration - Policy Management Window

•CTMS policy—describes the switching policy for multipoint meetings. The switching mode can be set to either Speaker or Room switching. You also use the policy management window to set the number of scheduled meetings pushed to CTMS devices. The default is to push 14 days of meetings.

Figure 3-24 CTMS Policy Window

•CTS endpoint policy—determines the number of days of scheduled meetings pushed to each endpoint. The default is 14 days.

Figure 3-25 CTS Endpoint Policy Window

•Conference Manager policy—specifies the following:

–Force Meeting Termination—Setting this to "Yes" allows the endpoints and any MCU device to automatically terminate a conference call according to the scheduled meeting time. The default is "No", so that meeting participants can continue a call past the scheduled end time of the meeting.

–Early Meeting Start in minutes—Determines how many minutes before a meeting's scheduled start time a participant can press the One-Button-to-Push to initiate a meeting.

–Late Meeting End in minutes—Determines how many minutes a meeting may continue before the call is forced to terminate. This field is grayed out if Force Meeting Termination is set to No.

---

Note "Early Meeting Start in minutes" affects both point-to-point meetings and multipoint meetings. All other settings affect only multipoint meetings.

---

Figure 3-26 Conference Manager Policy Window

System Settings

If you are the system administrator and know the superuser password, you can open the System Settings window to see the following choices:

•IP Setting

•NTP Setting

•SNMP Setting

•Remote Account

•Password

•System

Use the tabs in this window to modify IP settings, configure a Network Time Protocol (NTP) server, enable or disable Simple Network Management Protocol (SNMP), set up a temporary account for access, change the system password, and restart the system.

IP Setting

The IP Setting window lists information that is provided to CTS-Manager during first-time installation and configuration. Although it is typically not necessary to change IP settings, this window offers a place to modify some of them. Figure 3-27 describes the fields and buttons.

Figure 3-27 System Settings Window IP Settings Tab

Table 3-17 IP Settings 

Field or Button	Description or Settings
MAC Address	Display-only MAC address number supplied for this Cisco TelePresence Manager.
Hostname	Display-only hostname configured for this Cisco TelePresence Manager.
Domain Name	Domain name for this Cisco TelePresence Manager.
Primary DNS	Primary DNS server IP address supplied for this Cisco TelePresence Manager.
Secondary DNS	Secondary DNS server IP address supplied for this Cisco TelePresence Manager.
Ethernet Card	Name supplied for the system Ethernet card.
DHCP	Enable and Disable radio buttons determine whether DHCP is enabled or disabled. When the Enable radio button is chosen, information in the IP address fields cannot be modified. •To modify the IP settings for this Cisco TelePresence Manager, click the Disable radio button.
IP Address	IP address supplied for this Cisco TelePresence Manager.
Subnet Mask	Subnet mask used on the IP address.
Default Gateway	Default gateway IP address supplied for this Cisco TelePresence Manager.

To add new information, type it in the fields provided.

To change information, highlight and delete existing information and type in the new information.

To register new or modified settings, click Apply.

To restore the original settings, click Reset.

NTP Setting

Click the NTP Setting tab in the System Settings window to list the configured IP address of the Network Time Protocol (NTP) servers.

NTP is used to synchronize the clocks on Cisco IP telephony servers with an external network time server that uses NTP.

Figure 3-28 System Settings Window NTP Settings Tab

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.

To register new or modified settings, click Apply.

To restore the original settings, click Reset.

SNMP Setting

SNMP is an industry-standard interface used by network management systems to capture system status and error information, including information provided by Unified CM. Use this window to enable and disable SNMP service and change the default configuration.

By default, SNMP service is disabled. Once SNMP is enabled, the following default SNMP settings are also enabled:

---

Caution Editing SNMP settings from the CTS-Manager UI may cause some discrepancies. Please use the CLI commands to change these settings.

---

•One SNMP username set to "admin". This name cannot be changed.

•SNMP service password set to "snmppassword." The password should be changed.

•No trap receiver configured. Use the Trap Receiver Configuration fields in this window to configure a trap receiver. The fields collect trap receiver username, password, authentication algorithm, hostname or IP address, and port.

Figure 3-29 System Settings Window SNMP Settings Tab

To configure SNMP, click the SNMP Setting tab in the System Settings window. Table 3-18 describes the fields and buttons.

Table 3-18 SNMP Settings 

Field or Button	Description or Settings
Engine ID	The engine ID for the SNMP agent on this CTS-Manager. 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	To enable or disable SNMP, click the Enable or Disable radio button, as appropriate. When SNMP is enabled, supply a password for the SNMP server in the Configuration area.
Configuration
Username	SNMP server username.
Current Password	SNMP server password. The password must be 8 characters long. Enter it twice for verification.
Trap Receiver Configuration	To select whether to use an SNMP trap receiver, click the Yes or No radio button, as appropriate. When a trap receiver is used, supply login information for the trap receiver in the following fields.
Username	Trap receiver username.
Current Password	Trap receiver password. The password must be 8 characters long. Enter it twice for verification.
Authentication Algorithm	Choose Message Digest 5 (MD5) or Secure Hash Algorithm (SHA) for authentication.
Host	Trap receiver IP address or hostname.
Port	Trap receiver port number.

To register new or modified settings, click Apply.

To restore the original settings, click Reset.

Technical Notes

CTS-Manager supports SNMP v3 and v2c. Together it supports ten SNMP users and five trap destination/receivers. A string of trap receiver settings is added to the /etc/snmp/snmpd.conf file to configure the trap receiver on the Cisco TelePresence Manager server. The string must include the following information, which is collected in the fields described in Table 3-18 or is set by default:

•IP address and port number of the trap receiver

•Trap receiver username

•Trap receiver user password

•Trap sender engine ID

•Authentication method, either MD5 for Message Digest 5 or SHA for Secure Hash Algorithm

•Security model, which by default is authNoPriv

•SNMP version, which by default is version 3

•Included MIBs, which by default is ALL.

The following is an example trap receiver entry:

trapsess -e 0x80001f880474657374 -v 3 -m ALL -l authNoPriv -u traper -a MD5 -A changeme 
171.71.232.113:162

These fields can be viewed and configured using get and set commands on the /usr/sbin/snmpconfig script. To test your configuration, run snmptrapd come with net-snmp on the trap receiver system. You can create the user in /etc/snmp/snmptrapd.conf on the trap receiver system before starting snmptrapd.

Remote Account

Use this window to set up limited access for remote users of this CTS-Manager. The remote account is intended for use by Cisco technical support personnel so they can access the system remotely to troubleshoot problems. Secure Shell (SSH) is used to access the system. The remote account is typically enabled for a brief period. Disabling the account will cause whoever is logged onto the system to be logged off. Only one remote account can be set up at a time, but more than one remote account can be active at the same time.

Login to the remote account is done using the account name and a pass phrase generated by software in this CTS-Manager. The remote user uses the account name, the pass phrase, and a utility available at an internal Cisco web site to generate a login name and password that allow access to this Cisco TelePresence Manager.

Figure 3-30 System Settings Window Remote Account Tab

To start the remote login account process:

---

Step 1 Type a name for the remote login account in the Account Name field.

This name can be anything you choose, using English characters.

Step 2 Type in the number of days that the account should be active.

Step 3 Click Add.

This step generates a pass phrase.

To complete this process, the account name and pass phrase are entered into a utility at the following Cisco Internal web site:
https://remotesupporttool.cisco.com/logon.php

For security reasons, if remote users fail to log off, they will be logged off automatically at the time listed in the Expires field.

---

Password

Use the System Settings window to change the password for the Cisco TelePresence Manager. You must know the current password. Input the new password the second time for verification.Do not use anything other than English, as International words or characters are not supported in this release.

Figure 3-31 System Configuration - System Settings Window Password Tab

---

Step 1 To display the password fields, click on the tab, Password.

Step 2 Type in your current password.

Step 3 Then, to change password, go to New Password field and type your new password, using only English characters.

Step 4 In the New Password (verify) field, repeat your new password to verify it.

Step 5 To register the new password, click Apply.

Step 6 To restore to the original password, click Reset.

---

Note Make sure you keep your password secure and that it follows standard password guidelines, minimum 6 letters.

---

It is not possible to change the username for this CTS-Manager.

---

System

Use the System Configuration, System Settings window to restart CTS-Manager.

Figure 3-32 System Settings Window System Tab

---

Step 1 To restart the system, click on the System tab.

•The username cannot be changed.

Step 2 Enter your password.

Step 3 Click on Restart.

This will restart the CTS-Manager system.

---

Application Settings

The System Configuration Applications Settings window is used to set three different options: Interoperability with Video Conferencing, Intercompany, and Meeting Notification Email.

Figure 3-33 Application Settings Window

Interoperability with Video Conferencing Settings

The default setting for inter operability with video conferencing is "Disable." If the setting is grayed out and cannot be changed to "Enable," there is at least one CTS endpoint or MCU device that is not interop-ready. All endpoints and CTMS MCUs must support interop before you can enable Interop settings. Make sure all devices discovered by CTS-Manager are running interop-enabled software releases.

If Interoperability with Video Conferencing has been set to "Enable" and is grayed out so that you can't disable it, the CUVC, added through the MCU devices window, is included in at least one scheduled meeting. In order to disable interop services, you must first Deallocate the CUVC, and then Delete it from the MCU Devices window.

Intercompany Setting

Enabling Intercompany allows you to schedule multipoint meetings between two different organizations. Once you enable the Intercompany feature it cannot be disabled.

Meeting Notification Email Settings

The default setting for Meeting Notification Email is 'Yes'. If you change this setting to 'No' you disable email notifications, and Confirmation emails and Action Required emails are not sent to meeting organizers.

You can also specify an additional email address. All emails generated by Cisco TelePresence Manager will also be sent to this address.

A secondary email address specified for IBM Domino installations is included in the BCC field when emails are generated.

A secondary email address specified for Microsoft Exchange installations is included in the CC field when emails are generated.

Software Upgrade

If you are the system administrator and know the superuser password, you can access the Software Upgrade window to monitor and maintain system software. This window reports the version number of the system software. There are also two buttons to assist you in version maintenance between primary and backup and upgrading the system software, as follows:

Figure 3-34 System Configuration - Software Upgrade Window

•Switch Version—The hard drive on the server on which this CTS-Manager is installed is partitioned into two areas. Each area can contain a system image. The Switch Version button allows you to switch between the Active and Inactive versions of the system software.

•Upgrade Software—This button loads 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.
In addition to SFTP, FTP is also supported on a best-effort basis due to variations of behavior between different FTP servers. Only username/password-based login is supported. Anonymous login is not supported.
Secure FTP (SFTP) is the recommended mode for downloading the upgrade software over the network.

Upgrading to Cisco TelePresence Manager 1.5

Switching calendar application type, e.g. changing from Exchange to Domino, during Cisco TelePresence Manager upgrade is not supported. A fresh install is required to install Cisco TelePresence Manager for Domino deployment.

•Software upgrade is only supported from CTS-Manager 1.3 or 1.4 to 1.5.

• Data are automatically migrated during software upgrade, with the exceptions of:

– custom settings, such as custom email templates or custom flags.

– log or debug settings

– log files

• Perform a backup before performing a CTS-Manager upgrade and another backup after upgrade is completed and verified.

• If for any reason you must revert to a previous release after the upgrade is completed, you can switch to the old partition from CTS-Manager.

Switch Version

The hard drive on the CTS-MAN server is divided into two partitions. CTS-MAN is always using the Active partition and contains the Active software version. The software image versions are identified in the System Configuration> Software Upgrade window.

You may find it necessary to switch the version of the CTS-Manager software.

•To switch between the two software versions stored in the partitions, click the Switch Version button.

The system will swap the software versions and reboot. Screens will describe activity.

Upgrade Software

This task upgrades the CTS-Manager software by loading and applying a patch file from either a CD-ROM or an SFTP/FTP host network. Before starting this task, determine the source of the patch file.

•To start the software upgrade process, click the Upgrade Software button.
The Source Selection dialog box appears.

---

Note Once you have launched the Upgrade Wizard the upgrade process cannot be started by any other user logged into the same Cisco TelePresence Manager server.

---

•Click the CD-ROM or Network radio button to choose the location of the patch file.

If you chose CD-ROM, click Next to go to the File Selection window.

If you chose Network, provide the following information, and then click Next to go to the File Selection window.

•Host—The hostname of the network server.

•Port—The port. By default, port 22 is used to access the server; supply the correct port number, if required.

---

Note If you choose to perform the software upgrade using FTP you do not need to supply a port number.

---

•Username and Password—The user account and password needed to log into the server.

•Storage Path—The file path to the patch file, e.g. /localview/ctm_patch

---

Caution FTP scripts for Upgrade, Backup and Restore use Expect scripts and perform on a best-effort basis, due to potential variations in the responses sent by the FTP server. Only username/password-based login is supported. Anonymous login is not supported.
Secure FTP (SFTP) is the recommended mode of transferring files over the network.

---

Figure 3-35 Software Upgrade - Source Selection Window

•At the File Selection window, choose the file to load by clicking its radio button. Then click Next.

Figure 3-36 Software Upgrade - File Selection window

•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.

Figure 3-37 Software Upgrade - Patch File Preparation Window

•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.

•Click Yes or No to make your choice. Then click Next to finish the software upgrade task.

---

Caution Once you click Next to confirm you cannot cancel the upgrade.

---

Figure 3-38 Software Upgrade - Confirmation Window

•The install wizard displays a dialog window that logs the progress of the update.

Figure 3-39 Software Upgrade - Progress Window

•When the log indicates that the files have been switched, click Finish to complete this task.

---

Note If you selected to automatically switch to the new version, a message is displayed letting you know there is no connectivity to the server during the switch.

---

Figure 3-40 Software Upgrade - CTM Upgrade Completed Window

CTS-Manager Redundancy Failover Procedure

The Cisco TelePresence Manager configuration for a redundant system is to have a primary and a backup CTR-MAN system with a mirror configuration.

---

Note If a redundant system is configured, make sure database backups are performed regularly.

---

Cold Standby

In a redundant system, the primary CTS-MAN is active and the backup is powered off.

When a CTS-MAN primary system stops working, meetings scheduled during this down-time will not be pushed to the phone. Meetings can still be scheduled in the Exchange of Notes during a the downtime and all meetings "one button to push" on the phone will not be affected. Once the backup CTS-MAN is online, meetings scheduled during the primary down-time will be processed and pushed to the phones.

---

Note It is recommended to use the same hostname and the same IP address for CTS-MAN replacement server.

---

CTS-MAN Failover Procedure

When the primary CTS-MAN fails, perform the following procedure:

•To start the failover procedure, power off the primary CTS-MAN system.

•Power on the backup CTS-MAN system.

•Restore the last CTS-MAN database to the backup CTS-MAN, click Available Backups to complete this task

Figure 3-41 System Configuration Database Restore Backup Window

•Next, perform a re-sync with Microsoft Exchange or IBM Domino database from the backup CTS-MAN.

Figure 3-42 System Configuration - Microsoft Exchange Re-sync Window

•After ensuring the information is correct, click Re-sync to complete the re-sync.

---

Note This Re-sync in Exchange must be verified in an Exchange environment, not CTS-MAN.

---

Warm Standby

CTMS Warm Standby for Scheduled Meetings

Both the primary and backup CTMS systems are configured independently with different access numbers, etc.

Each CTMS is configured in the CTS-MAN. Both primary and backup CTMS are powered on and connected to the network at all times. The meetings will only be scheduled on and serviced by the primary CTMS.

CTS-MAN Redundancy Failover Procedure

With a redundant CTS-MAN system, make sure to configure two CTS-MAN and register the primary with CTS-MAN in "Scheduled" mode and the backup in "Non-Scheduled" mode.

---

Note Both CTMS are active, but meetings are to be scheduled on the primary "Scheduled" CTMS

---

When the primary CTR-MAN fails, perform the following procedure:

•To start the failover procedure process, power off the primary CTS-Man.

•Power on the backup CTS-Man.

•Restore the last CTS-MAN database to the backup CTMS, click Available Backups to complete this task

---

Note During a primary CTMS failure, all multipoint meetings in progress will be disconnected and no new meetings will be allowed to start. Migrating all meetings is only allowed to a non-scheduled CTMS.

---

Figure 3-43 System Configuration Database Restore Backup Window

CTMS Redundancy Failover Procedure

•When the primary CTMS fails, log into CTS-MAN and migrate all scheduled meeting to the backup "non-scheduled" CTMS.

Figure 3-44 System Configuration MCU Devices - Details Window

•Change the Control State of primary CTMS to Non-scheduled

•Change the Control State of the backup CTMS to Scheduled.

Figure 3-45 System Configuration MCU Devices - Edit Window

All scheduled multipoint meetings are moved to the backup CTS-MAN and "One Button to Push" entries are updated with the new CTMS access number and conference ID. The time it takes to update all meeting entries and update all phones will vary depending on the number of meetings and CTS endpoints.

.