Guest

Cisco TelePresence Multipoint Switch

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.7

  • Viewing Options

  • PDF (513.7 KB)
  • Feedback
Release Notes for Cisco TelePresence Multipoint Switch, Release 1.7

Table Of Contents

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.7

Contents

Introduction

Cisco TelePresence Software Compatibility Matrix

Software Releases and Component Firmware Versions

CTMS Software Upgrade Path

New and Changed Information for CTMS Release 1.7.4

Fixed Caveats in CTMS Release 1.7.4

New and Changed Information for CTMS Release 1.7.3

Fixed Caveats in CTMS Release 1.7.3

New and Changed Information for CTMS Release 1.7.2

Video Quality for Scheduled Meetings

Quality Value Displayed in Active Meetings Page

Cisco WebEx User Password Expiration or Reset

Cisco WebEx Via Proxy Server

Fixed Caveats

Cisco TelePresence WebEx OneTouch Enhanced with Cisco Media Experience Engine Interoperability (Available in an Upcoming Release)

Documentation Errata in Release 1.7.2

Caveats for CTMS Release 1.7.3

CTMS Release 1.7.3 Caveat Reference

Caveats for CTMS Release 1.7.3

Caveats for CTMS Release 1.7.2

CTMS Release 1.7.2 Caveat Reference

Caveats for CTMS Release 1.7.2

New and Changed Information for CTMS Release 1.7.1

Documentation Errata in Release 1.7.1

Caveats for CTMS Release 1.7.1

CTMS Release 1.7.1 Caveat Reference

Caveats for CTMS Release 1.7.1

New and Changed Information for CTMS Release 1.7.0.1

Documentation Errata in Release 1.7.0.x

Caveats for CTMS Release 1.7.0.x

CTMS Release 1.7.0.x Caveat Reference

Caveats for CTMS Release 1.7.0.x

New and Changed Information for CTMS Release 1.7.0

Cisco TelePresence WebEx OneTouch

Cisco Media Experience Engine Interoperability

Cisco Unified Videoconferencing 7.1 and Cisco Unified Videoconferencing Manager Interoperability

Director Controls in the CTMS Web UI

Dual-Presentation Streams

Conference Control Protocol for Web Services

Reverse Message Polarity (Smart Media)

Meeting Termination and Extension Policy and CTMS Resources

Manageability Improvements

TIP Support

Cisco TelePresence Commercial Express Version of CTMS Release 1.7

Interoperability Issues

Upgrading to Future Releases from Release 1.7.0(505)

Fixed Caveats

Documentation Errata in Release 1.7.0

Caveats for CTMS Release 1.7.0

CTMS Release 1.7.0 Caveat Reference

Caveats for CTMS Release 1.7.0

New and Changed Information for CTMS Release 1.6.4

Support for Non-CABAC Endpoints

Caveats

New and Changed Information for CTMS Release 1.6.3

Caveats

New and Changed Information for CTMS Release 1.6.2

Caveats

New and Changed Information for CTMS Release 1.6.1

Caveats

New and Changed Information for CTMS Release 1.6.0

Upgrading to CTMS Release 1.6.0

Standard Event Controls: VIP Mode, Auto Lecture Mode, and Boardroom Mode

Professional Event Controls: Director Controls Through the CTMS Administrative CLI

High Definition Interoperability

Extended Reach

Caveats

Software Releases and Component Firmware Versions

Caveats for CTMS Release 1.6.x

CTMS Release 1.6 Caveat Reference

Caveats for CTMS Release 1.6.0

New and Changed Information for CTMS Release 1.5.6

Software Upgrade Caveat

New and Changed Information for CTMS Release 1.5.4

New and Changed Information for CTMS Release 1.5.3

New and Changed Information for CTMS Release 1.5.2

CTMS Hardware MIB Support

New and Changed Information for CTMS Release 1.5.1

New and Changed Information for CTMS Release 1.5.0

Upgrading to CTMS Release 1.5.0

Cisco TelePresence Manager (CTS-MAN) Intercompany Communication

CTMS Security Features

HTTP Proxy for CTMS

NTP Server Configuration

Software Releases and Component Firmware Versions

Caveats for CTMS Release 1.5.x

CTMS Release 1.5 Caveat Reference

Caveats for CTMS Release 1.5.4

Caveats for CTMS Release 1.5.3

Caveats for CTMS Release 1.5.2

Caveats for CTMS Release 1.5.1

Caveats for CTMS Release 1.5.0

Supplemental End User License Agreement

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TelePresence Multipoint Switch, Release 1.7


Created: September 2010
Revised: August 2012, OL-23452-04

Contents

Introduction

Cisco TelePresence Software Compatibility Matrix

Software Releases and Component Firmware Versions

CTMS Software Upgrade Path

New and Changed Information for CTMS Release 1.7.4

New and Changed Information for CTMS Release 1.7.3

New and Changed Information for CTMS Release 1.7.2

Documentation Errata in Release 1.7.2

Caveats for CTMS Release 1.7.2

New and Changed Information for CTMS Release 1.7.1

Documentation Errata in Release 1.7.1

Caveats for CTMS Release 1.7.1

New and Changed Information for CTMS Release 1.7.0.1

Caveats for CTMS Release 1.7.0.x

New and Changed Information for CTMS Release 1.7.0

Documentation Errata in Release 1.7.0

Caveats for CTMS Release 1.7.0

New and Changed Information for CTMS Release 1.6.4

New and Changed Information for CTMS Release 1.6.3

New and Changed Information for CTMS Release 1.6.2

New and Changed Information for CTMS Release 1.6.1

New and Changed Information for CTMS Release 1.6.0

Software Releases and Component Firmware Versions

Caveats for CTMS Release 1.6.x

New and Changed Information for CTMS Release 1.5.6

New and Changed Information for CTMS Release 1.5.4

New and Changed Information for CTMS Release 1.5.3

New and Changed Information for CTMS Release 1.5.2

New and Changed Information for CTMS Release 1.5.1

New and Changed Information for CTMS Release 1.5.0

Software Releases and Component Firmware Versions

Caveats for CTMS Release 1.5.x

Supplemental End User License Agreement

Obtaining Documentation and Submitting a Service Request

Introduction

These release notes describe the new features and open caveats for all software releases that are associated with the Cisco TelePresence Multipoint Switch (CTMS).

Cisco TelePresence Software Compatibility Matrix

For Cisco TelePresence software compatibility information, see the information located at the following URL:

http://www.cisco.com/en/US/products/ps8332/products_device_support_tables_list.html

Software Releases and Component Firmware Versions

For the current recommended set of software releases and component firmware versions for the Cisco TelePresence solution, see the information located at the following URL:

http://www.cisco.com/en/US/partner/docs/telepresence/cts_admin/1_7/release/notes/cts_1_7_release_notes.html#wp42142

CTMS Software Upgrade Path

For each CTMS software release, we support an upgrade path from the previous two releases. For example, for CTMS 1.7.x, we support an upgrade path from these releases:

1.6.x

1.5.x

New and Changed Information for CTMS Release 1.7.4

CTMS 1.7.4 contains a fix for CSCua83891.

Fixed Caveats in CTMS Release 1.7.4

CSCua83891: When a CTS endpoint with 2048-bit security certificates tries to join a secure CTMS conference, it will be dropped. If it tries to join a scheduled (best-effort) meeting, the meeting and the endpoint will be downgraded to non-secure.

New and Changed Information for CTMS Release 1.7.3

CTMS 1.7.3 contains a fix for CSCty49750.

Fixed Caveats in CTMS Release 1.7.3

CSCty49750: CTMS switches without a refresh picture. Video switches before IDR frames are received.

New and Changed Information for CTMS Release 1.7.2

Video Quality for Scheduled Meetings

In CTMS releases before 1.7.2, the video quality of a scheduled multipoint meeting was determined by the endpoint with the lowest video quality.

Release 1.7.2 introduces an enhanced approach to determining the video quality of a scheduled meeting. From the list of scheduled participating endpoints, CTMS now determines the endpoint with the highest video quality and sets the meeting to that quality.

The video quality of a scheduled meeting is also affected by the setting of the Allow Downspeed attribute, which can be accessed in the Default Meeting Settings page of the CTMS Administrative UI. By default, this attribute is set to Yes, which means that if an endpoint with lower video quality joins a higher quality meeting, CTMS adjusts the quality of all endpoints to match the lower quality endpoint. If the parameter is set to No, an endpoint with a lower video quality is not allowed to join the meeting because of the quality mismatch.

Quality Value Displayed in Active Meetings Page

As a result of the video quality enhancements described in the "Video Quality for Scheduled Meetings" section, the value of the Quality attribute displayed in the Manage > Active Meetings page has been updated in CTMS 1.7.2. This attribute now displays the current meeting quality, factoring in the dynamic changes made by the CTMS as endpoints join and leave the meeting, and per the setting of the Allow Downspeed attribute.

Cisco WebEx User Password Expiration or Reset

A user's Cisco WebEx password can expire, or the Cisco WebEx administrator might reset their password but they never use the new password. If either of these events occurred and the user tries to start a scheduled multipoint meeting with Cisco WebEx, the phone UI displays this message:

WebEx account issue, please check your WebEx account

After receiving this message, the user must specify a new Cisco WebEx password as follows:

If the user's password expired, they should log into their Cisco WebEx website with the expired password. They will then be prompted to set a new password.

If the user's password was reset, they should find the reset notification email sent by the Cisco WebEx administrator. This email should include a URL from which they can log in and set a new password. If they cannot find the email, they can contact the Cisco WebEx administrator.

After specifying a new password, the user should be aware of the following points:

They do not need to re-authenticate with the WebEx server because the Cisco WebEx account itself did not undergo any changes.

They will be able to join Cisco Webex meetings scheduled after they specify their new password, but they will not be able to join any Cisco Webex meetings scheduled before they specify their new password.

Cisco WebEx Via Proxy Server


Note To successfully use this feature, both CTMS and CTS-Manager must be running software version 1.7.2.


To maintain the Cisco WebEx server's anonymity, a precaution that provides an additional layer of security, you can set up a proxy server through which the CTMS and Cisco WebEx TelePresence gateway communicate.

Fixed Caveats

The following caveats were fixed in CTMS release 1.7.2:

CSCti53470: Scheduled meeting fails if Subject field not specified in email client

CSCti62824: Meeting ended at scheduled time but sys msg says it was extended

CSCti89282: Participant list displays multiple grayed-out VC endpoints

CSCtk58352: Can't access CTMS webserver after software upgrade and security change

CSCtl91785: After Auto Lecture Mode is disabled, scrolling view continues

CSCtl84403: CTMS is not registered with CTS-Manager after power outage

CSCtn79160: WebEx OneTouch audio fails

Cisco TelePresence WebEx OneTouch Enhanced with Cisco Media Experience Engine Interoperability (Available in an Upcoming Release)

Media Experience Engine (MXE) integration with Cisco TelePresence WebEx OneTouch requires a new version of MXE software that will be qualified with the CTMS and CTS-Manager in an upcoming release.

Documentation Errata in Release 1.7.2

The most current source of CTMS administration information is the Cisco TelePresence Multipoint Switch Administration Guide, which you can access at the following location:

http://www.cisco.com/en/US/products/ps7315/prod_maintenance_guides_list.html

In the CTMS online help for the Manage > Default Meeting Settings page/Allow Downspeed parameter, the term "QoS" is erroneously used multiple times. Instead of "QoS," the term "quality" should be used when describing the video quality of the endpoint.

In the CTMS online help for Director Control, an incorrect command is used. Instead of the set eventconrol webui directorcntrl enable command, use the set eventcontrol webgui directorctrl enable command to enable Director Control in the CTMS administrative UI.

Caveats for CTMS Release 1.7.3

This section includes the following information:

CTMS Release 1.7.3 Caveat Reference

Caveats for CTMS Release 1.7.3

CTMS Release 1.7.3 Caveat Reference

Table 2 summarizes caveats found in CTMS Release 1.7.3.

Table 1 CTMS Release 1.7.3 Caveats and Caveats Corrected Reference 

 

Software Release

 
 

1.7.3

 

CDETS Number

Found in Release

Corrected in Release

Note

CSCua83891

1.7.3

1.7.4

-


Caveats for CTMS Release 1.7.3

CSCua83891

Symptom: When a CTS endpoint with 2048-bit security certificates tries to join a secure CTMS conference, it will be dropped. If it tries to join a scheduled (best-effort) meeting, the meeting and the endpoint will be downgraded to non-secure.

Condition: This affects the newer CTS which comes with manufacturer installed 2048-bit security certificates.

Workaround: Use best-effort or non-secure meetings.

Caveats for CTMS Release 1.7.2

This section includes the following information:

CTMS Release 1.7.2 Caveat Reference

Caveats for CTMS Release 1.7.2

CTMS Release 1.7.2 Caveat Reference

Table 2 summarizes caveats found in CTMS Release 1.7.2.

Table 2 CTMS Release 1.7.2 Caveats and Caveats Corrected Reference 

 

Software Release

 
 

1.7.2

 

CDETS Number

Found in Release

Corrected in Release

Note

CSCtn01277

1.7.2

None

-

CSCtn06831

1.1

None

This CDET is not a CTMS caveat. It is a caveat for the MXE release 1.1.

CSCtn23550

1.7.2

None

-

CSCto59894

1.7.2

None

-


Caveats for CTMS Release 1.7.2

CSCtn01277

Symptom: The CTMS receives multiple instances of this system message:

Media Processor Feedback was not received from all the destinations for the source endpoint

Condition: The CTMS might receive multiple instances of this warning message during a scheduled meeting that includes these elements:

Multiple video conferencing (VC) endpoints, which are supported by a Cisco Media Experience Engine (MXE).

Participants who join the meeting using Cisco WebEx.

Workaround: None. This system message is benign and does not require any action nor affect the quality of the meeting.

CSCtn06831

Symptom: During a meeting that includes CTS endpoints and video conferencing (VC) endpoints supported by the Cisco Media Experience Engine (MXE), a VC endpoint drops out of the meeting then tries to dial back into the meeting but cannot rejoin.

Condition: During the meeting, the following events occurred successfully:

VC endpoints joined then dropped out of the meeting.

One or more VC endpoints put the meeting on hold then resumed it multiple times.

This issue can occur if the MXE is running software version 1.1.

Workaround: The MXE must be restarted.

CSCtn23550

Symptom: An endpoint dials into a multipoint meeting after the first participant places the call on hold, then resumes the call multiple times. The endpoint receives this message:

Remote user is on hold

The endpoint then receives this message:

Please end the call if your meeting has ended

Condition: See Symptom above.

Workaround: No workaround exists.

CSCto59894

Symptom: An ad hoc meeting with multiple participants and no activity for several hours is dropped.

Condition: See Symptom.

Workaround: Restart the meeting.

New and Changed Information for CTMS Release 1.7.1


Note CTMS Release 1.7.1 replaces releases 1.7.0 and 1.7.0.1, which are no longer available on Cisco.com.


The following caveats were fixed in CTMS release 1.7.1:

CSCtj92963: holdresume command set to false causes static mtg to not start

CSCtk81749: Multiple scheduled mtg pushes w/ large mtgs could cause process failure

CSCtk82095: Duplicate core dump files cause full disk space

CSCtl20589: CTMS unresponsive under demanding conditions

Documentation Errata in Release 1.7.1

The most current source of CTMS administration information is the Cisco TelePresence Multipoint Switch Administration Guide, which you can access at the following location:

http://www.cisco.com/en/US/products/ps7315/prod_maintenance_guides_list.html

Caveats for CTMS Release 1.7.1

This section includes the following information:

CTMS Release 1.7.1 Caveat Reference

Caveats for CTMS Release 1.7.1

CTMS Release 1.7.1 Caveat Reference

Table 3 summarizes caveats found in CTMS Release 1.7.1.

Table 3 CTMS Release 1.7.1 Caveats and Caveats Corrected Reference 

 

Software Release

 

1.7.1

CDETS Number

Found in Release

Corrected in Release

CSCtl06578

1.7.1

None

CSCtl47516

1.7.1

None

CSCtn89016

1.7.1

None

CSCto57796

1.7.1

None


Caveats for CTMS Release 1.7.1

CSCtl06578

Symptom: The System Status in the left navigation of the CTMS Administration UI displays a segment count greater than 48 segments.

Condition: Under these conditions, the described Symptom might occur:

1. Back-to-back scheduled meetings are running.

2. CTMS is functioning at full capacity.

3. For a meeting scheduled at the top of the hour, an endpoint attempts to join the meeting a few minutes early, and it is put on hold.

Workaround: None. This issue does not affect the meeting itself.

CSCtl47516

Symptom: In the Active Meetings page of the CTMS Administrative UI, the Segments column displays an incorrect segment count for ad hoc and static meetings.

Condition: This issue can occur if an endpoint dials in early to join a scheduled meeting.

Workaround: None. This issue does not affect the meeting itself.

CSCtn79160

Symptom: The audio portion of a Cisco TelePresence WebEx OneTouch meeting does not work. Also, when a meeting participant dials into a CTMS Direct Inward Dial (DID) number, they don't hear multiple beeps, which indicate a good connection.

Condition: See Symptom above.

Workaround: Restart the CTMS processes using the Troubleshoot > Process Status page.

CSCtn89016

Symptom: Unable to successfully issue utils service snmp commands in the CTMS command line interface (CLI). After entering any of the SNMP commands, the CLI prompts you for a password. After entering a single character, the SSH session hangs.

Condition: This situation can occur if the CTMS administrative username is other than "admin."

Workaround: Contact the Cisco Technical Assistance Center (TAC). To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

CSCto57796

Symptom: The CTMS Administrative UI Director Controls that map sources to destinations, and lock the video switching do not work. However, the Media Controls work.

Condition: This issue can occur if the "Alerting Name" or "ASCII alerting name" in the Cisco Unified CM Directory Number configuration for an endpoint includes an underscore (_).

Workaround: You can work around this issue using one of these options:

Use the CTMS command-line interface (CLI) to map sources and destinations, and lock the video switching.

Substitute the underscore in the "Alerting Name" and the "ASCII alerting name" with a hyphen (-).

New and Changed Information for CTMS Release 1.7.0.1


Note CTMS Release 1.7.0.x replaces release 1.7.0, which is no longer available on Cisco.com.


The following caveats were fixed in CTMS release 1.7.0.1:

CSCtj57730: Security policy changed to Non-Secure from Best-Effort after upgrade if trusted trunk

CSCtj82894: With UCM 8.0.3, first endpoint in secure multipoint meeting from another UCM cluster disconnected if intercluster trunk is non-secure

CSCtj97946: Time Zone in CTS-Man page changes to UTC after CTMS upgrade

CSCtj98077: CTS-Manager 1.6.x fails to push scheduled multipoint meetings to CTMS if meeting is intercompany

CSCtk09141: Adding 3rd endpoint to intercompany call causes one endpoint to drop

Documentation Errata in Release 1.7.0.x

The most current source of CTMS administration information is the Cisco TelePresence Multipoint Switch Administration Guide, which you can access at the following location:

http://www.cisco.com/en/US/products/ps7315/prod_maintenance_guides_list.html

Caveats for CTMS Release 1.7.0.x

This section includes the following information:

CTMS Release 1.7.0.x Caveat Reference

Caveats for CTMS Release 1.7.0.x

CTMS Release 1.7.0.x Caveat Reference

Table 4 summarizes caveats found in CTMS Release 1.7.0.x.

Table 4 CTMS Release 1.7.0.x Caveats and Caveats Corrected Reference 

 

Software Release

 

1.7.0.x

CDETS Number

Found in Release

Corrected in Release

CSCtf51649

1.7.0

None

CSCti08961

1.7.0

None

CSCti31875

1.7.0

1.7.2

CSCtj92963

1.7.0

1.7.1

CSCtk53578

1.6.3

1.7.2


Caveats for CTMS Release 1.7.0.x

CSCtf51649

Symptom: In the Troubleshoot > Log Files page of the CTMS Administrative UI or under the /var/log/active/core directory, you notice one or more core files such as "core.10118.8.cimlistener.1289229932."

Condition: You might notice these core files after upgrading the CTMS software from version 1.6.x to version 1.7.x or 1.7.0.x.

Workaround: The cimlistener process might generate core files if SNMP traps are configured. These files are benign and do not affect any operations. Therefore, no action is required.

CSCti08961

Symptom: In the Configure > CTS Manager page of the CTMS Administrative UI, you enter a name for the User attribute that includes a blank space(s) before or after. In the Configure > Bridges and Servers page of the CTS-Manager Administrative UI, you add the same name, including the blank space(s). After refreshing the Configure > CTS Manager page in the CTMS Administrative UI, you notice that the Registration Status field says "Fail to register," while in the Configure > Bridges and Servers page of the CTS-Manager Administrative UI, the Status for the CTMS is "Error."

Condition: See Symptom above. Additionally, the CTMS is running build 1.7.0.1 and CTS-Manager is running build 1.7.0.2.

Workaround: Remove the blank space(s) from the username in the CTMS and CTS-Manager configurations.

CSCti31875

Symptom: In a multipoint meeting with 1.5.x or 1.6.x CTS endpoints trying to present, users may see a black presentation window or screen when the call is resumed after it was on hold.

Condition: This issue can occur when CTS endpoints running different software versions (1.5.x or 1.6.x) are in a meeting and the active presenter role changes from one endpoint to another. If a presentation stream is active and a 1.5.x or 1.6.x CTS endpoint connects its presentation cable, the active stream will change. If the newly active presenter places the call on hold, the previous presenter will resume its presentation stream. When the 1.5.x or 1.6.x endpoint resumes the call, a black presentation window or screen could appear.

Workaround: Disconnect then reconnect the presentation cable on the endpoint that resumed the call to retry the role of active presenter.

CSCtj92963

Symptom: A static multipoint meeting cannot be started.

Condition: On the CTMS, the set holdresume CLI command is set to false.

Workaround: Set the holdresume command to true, which is the default setting.

CSCtk58352

Symptom: After entering the URL of a CTMS in a supported browser, the Login page of the CTMS administrative GUI does not appear.

Condition: This issue can occur after upgrading a secure CTMS from software version 1.6.x to 1.7.x and deleting all security certificates.

Workaround: Perform the following steps:

1. Using the utils system switch-version CLI command, switch the running software version from 1.7.x back to 1.6.x.

2. Configure the 1.6.x system as Non-Secure.

3. Upgrade the CTMS software to 1.7.x.

CSCtk53578

Symptom: During a secure multipoint meeting, a CTS endpoint does not display video nor receive audio.

Condition: The DTLS key exchange fails, and as a result, secure calls fall back to SDP mode.

Workaround: Reboot the CTS endpoint.

New and Changed Information for CTMS Release 1.7.0

Cisco TelePresence WebEx OneTouch

The Cisco TelePresence WebEx OneTouch bridging solution integrates the Cisco WebEx conferencing server with Cisco TelePresence multipoint meetings. When the first CTS endpoint connects to a meeting, the CTMS automatically connects with the Cisco WebEx conferencing server. The presentation and audio are automatically shared.

Cisco Media Experience Engine Interoperability

CTMS release 1.7 supports the Cisco Media Experience Engine (MXE), which provides interoperability between video conferencing (VC) endpoints. The MXE acts as a transcoder for the VC endpoints that want to join a TelePresence multipoint meeting or dial directly to a CTS endpoint.

All scheduled MXE meetings that include one or more CTS endpoints are multipoint and therefore involve the CTMS.

The following are caveats for interoperability with the MXE in CTMS release 1.7:

A meeting with only VC endpoints is considered to be a non-TelePresence meeting and is in error state in CTS-Manager.

VC endpoints dial into scheduled meetings and do not have One-Button-to-Push (OBTP) functionality.

CTS endpoints in the multipoint meeting must be running CTS release 1.5, 1.6, or 1.7. If the CTS endpoint is running release 1.5, the meeting does not support HD.

The MXE currently supports the presentation audio stream only. As a result, the VC endpoints receive only the audio stream from a CTS presentation with audio. The endpoints currently do not receive the video stream.

If a multipoint meeting includes an MXE VC room, Cisco TelePresence WebEx OneTouch is not supported.

CTS-Manager allows the scheduling of a meeting with an MXE or a Cisco Unified Videoconferencing (CUVC) device. It does not allow the scheduling of a meeting that includes both devices.

Cisco Unified Videoconferencing 7.1 and Cisco Unified Videoconferencing Manager Interoperability

CTMS release 1.7 supports interoperability with Cisco Unified Videoconferencing (CUVC) 7.1 and CUVC Manager (CUVC-M).

The following are caveats to interoperability with a CUVC when a Cisco Tandberg Video Communication Server (VCS) is used to dial in to the CUVC:

Using a VCS as a proxy to dial in to a CUVC is not a supported configuration. If endpoints use a VCS as a proxy, the CUVC audio mixer might terminate, which results in audio failure. CTS endpoints in an Interop meeting with CUVC 7.x might not see or hear video conference callers. These callers might not connect to CUVC or might be connected without audio. SIP calls are rejected with SIP return code "603 declined." This conditions occurs with or without CUVC-M in the call path.

If this condition occurs, you must reboot the CUVC to restore service and place calls directly from Cisco Tandberg endpoints to the CUVC.

The Movi client is not supported on CUVC.

Director Controls in the CTMS Web UI

Director Controls, one of several ways to set what rooms and room segments in active meetings see and hear, was available only through the CLI in CTMS release 1.6. In CTMS release 1.7, Director Controls functionality is also accessible through the Web user interface after the feature is enabled through the CLI.

Dual-Presentation Streams

CTMS release 1.7 introduces additional quality when a Presentation Codec (CTS-HFR-COLLAB) is used. If an endpoint that is presenting includes this optional codec, two presentation streams are sent. Depending on the capability of the participating endpoints, both streams are sent at 5 frames per second (FPS) and 30 FPS, or at 1 FPS and 30 FPS. This feature adds approximately 500 kbps bandwidth to a call.

Conference Control Protocol for Web 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. 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.

Reverse Message Polarity (Smart Media)

Reverse Message Polarity (RMP), also known as Smart Media, provides CTMS with a way to classify the quality of video streams. These streams can then be targeted for quality adjustments.

Meeting Termination and Extension Policy and CTMS Resources

A meeting organizer or participant might want to extend a scheduled meeting beyond its scheduled end time. CTMS has a limited number of audio and video resources, so the CTS-Manager (CTS-Man) administrator must create a policy that determines how the CTMS handles termination and extension. This policy indicates who can extend and for how many minutes.

The CTMS administrator does not have to configure anything for meeting termination and extension to work. The CTMS accepts the configured policy from the CTS-Man and handles CTMS resources according to that policy.

Manageability Improvements

Troubleshoot > System Messages in the CTMS web interface provides a list of messages about CTMS events or conditions that might affect the performance of endpoints in a multipoint meeting. In CTMS release 1.7, a column called "Recommendation" has been added to this list page. When appropriate, a message includes a recommendation for troubleshooting the cause of the event or condition.

TIP Support

CTMS release 1.7 supports Telepresence Interoperability Protocol (TIP) version 6.0 and version 7.0.

Cisco TelePresence Commercial Express Version of CTMS Release 1.7

The Cisco TelePresence Commercial Express product bundle is delivered as a single Cisco MCS server with one or more Cisco TelePresence application DVDs, license keys, and instructions to install the product, including the recommended VMware configuration. During installation, the common infrastructure component within the Cisco applications detects the VMware and identifies it as supported hardware.

Once you have VMware installed on your system, the basic procedure to install CTS-Manager, CTMS, and CTRS are the same. You can install the CTMS and CTRS in any order once you have installed, configured, and set up licensing for CTS-Manager.

For Commercial Express versions of CTMS, the number of schedulable segments and the number of ad hoc and static segments is determined by the Commercial Express license, which is loaded in CTS-Manager. After you have set up licensing in CTS-Manager, the CTMS administrator can reconfigure the number of ad hoc and static segments to any number less than the total number of permitted segments.

Interoperability Issues

When endpoints that use a Cisco/Tandberg VCS system as a proxy dial into a CUVC running version 7.1, the CUVC audio mixer might terminate, which results in audio failure. CTS endpoints in an Interop meeting with CUVC 7.x might not see or hear video conference callers. These callers might not connect to CUVC or might be connected without audio. SIP calls are rejected with SIP return code "603 declined." This conditions occurs with or without CUVC-M in the call path.

If this condition occurs, you must reboot the CUVC to restore service and place calls directly from Cisco Tandberg endpoints to the CUVC.

This condition is noted in CSCth61621: CUVC rejects new calls when VCS is used as a proxy.

Upgrading to Future Releases from Release 1.7.0(505)

CTMS version 1.7.0(505) should be upgraded either to 1.7.2(75) or 1.8.0(1026) before upgrading to other future releases.

Fixed Caveats

The following caveats, which were opened in CTMS releases 1.5.3 and 1.6.0, were fixed in CTMS release 1.7.0:

CSCso13993: Sysop log reports packet loss percentage call from center (e.g., 25% or 100%) while no audio issue is noticed

CSCta38768: Import kept Best-Effort and Secure settings for static meetings

CSCtc71031: Call drops. And CTMS alarm page shows SPIMAP timeout

CSCtc88319: 1080p quality selection is not available after changing Interop selection to No in the Static Meetings detail screen

CSCtd11725: Change Security Policy back to Non-Secured will also change all static meetings to Non-Secured

CSCtd29406: Upgrade does not populate Dial Suffix for HD Interoperability

Documentation Errata in Release 1.7.0

In the CTMS administrative interface, buttons with the label Reset now use the label Cancel. Screen captures in the CTMS administration guide might not reflect the label change.

In the CTMS CLI, the term conference is now meeting. Command entries in the CTMS command reference might not reflect the change in terms.

Caveats for CTMS Release 1.7.0

This section includes the following information:

CTMS Release 1.7.0 Caveat Reference

Caveats for CTMS Release 1.7.0

CTMS Release 1.7.0 Caveat Reference

Table 5 summarizes caveats found in CTMS Release 1.7.0.

Table 5 CTMS Release 1.7.0 Caveats and Caveats Corrected Reference 

 

Software Release

 

1.7.0

CDETS Number

Found in Release

Corrected in Release

CSCtb64811

1.7.0

None

CSCtc68768

1.7.0

1.7.2

CSCtf73377

1.7.0

None

CSCtf82182

1.7.0

None

CSCtg07495

1.7.0

None

CSCtg50877

Duplicate of CSCti94915, which was corrected in Release 1.7.2

1.7.0

1.7.2

CSCth44072

1.7.0

1.7.2

CSCth51888

1.7.0

None

CSCth93803

1.7.0

1.7.2

CSCti14371

1.7.0

1.7.2

CSCti16462

1.7.0

None

CSCti21782

1.7.0

1.7.2

CSCti21821

1.7.0

1.7.2

CSCti26725

1.7.0

None

CSCti31875

1.7.0

1.7.2

CSCti38768

1.7.0

1.7.2

CSCti53470

1.7.0

1.7.2

CSCti58167

Duplicate of CSCti14371

1.7.0

1.7.2

CSCti62790

Duplicate of CSCti38768

1.7.0

1.7.2

CSCti89282

1.7.0

1.7.2

CSCti91916

1.7.0

1.7.2

CSCti96592

1.7.0

1.7.2


Caveats for CTMS Release 1.7.0

CSCtb64811

Symptom: The graphs in the Troubleshoot > System Resource page do not display any data.

Condition: This issue can occur after a network interface card (NIC) failover.

Workaround: Approximately 10 hours after the NIC failover, the System Resource page will start to work properly and display data again.

CSCtc68768

Symptom: Deleting the DNS and Domain Name values causes an error message to appear.

Condition: In the System Settings > IP page, if you remove the values for the DNS and Domain Name fields and click Apply, the following error message displays: Domain Name "is not a valid value."

Workaround:

To remove the DNS, perform these steps:

Retain the Domain Name value.

Remove the DNS entries.

Click Apply.

The DNS is removed after the CTMS is restarted.

CSCtf73377

Symptom: The CTS endpoint displays a blank presentation screen.

Condition: This issue can occur under the following conditions:

In this example, there are three CTS endpoints (A, B, and C).

Endpoints A and B are running any software version, and endpoint C is running version 1.7.

Endpoint A is presenting at 5 FPS presentation.

In the meantime, endpoint B places the call on hold.

At the same time that endpoint B resumes the call, endpoint C plugs in at 30 FPS presentation.

Workaround: On CTS endpoint C, unplug the presentation cable, then plug it back in.

Further Problem Description: This issue can occur if a CTS endpoint plugs in at 30 FPS presentation at the same time that another endpoint, which initially received the call at 5 FPS presentation, resumes the call. After this sequence of events, the CTMS and CTS can become unsynchronized as to the correct framerate of the presentation. Unplugging then replugging the presentation cable causes the CTMS and CTS to reestablish synchronization.

CSCtf82182

Symptom: The CTMS administrative GUI displays two identical warning messages for the MXE.

Condition: These messages can display if the MXE is rejected while trying to join a locked meeting.

Workaround: None.

CSCtg07495

Symptom: For a 1.6.x CTS endpoint, the MXE call statistics indicate more bandwidth than the CTS call statistics.

Condition: This discrepancy can occur for calls between a CTS 1.6.x and VC endpoint through the MXE.

Workaround: None.

CSCtg50877

(Duplicate of CSCti94915)

Symptom: Occasionally, at the beginning of a best-effort ad hoc meeting, a secure CTS endpoint may display a black screen with a secured call icon and no video.

Condition: This issue can occur under the following conditions:

The best-effort ad hoc meeting is created using the CTMS Administration UI.

The meeting includes secure and non-secure endpoints.

Workaround: Redial that endpoint into the meeting.

CSCth44072

Symptom: A Meet-Me meeting participant, who is on hold, is dropped from the meeting.

Condition: In a Meet-Me meeting, if the caller is the only participant in the meeting and places the meeting on hold, the caller is dropped by the CTMS with the cause code 34.

Workaround: The participant must call back into the meeting.

CSCth51888

Symptom: A bulk event control request for a large meeting may generate errors. As a result, multiple alarms with the message "Failed to send msg: errno=11, errorstr=Resource temporarily unavailable" are logged into the CTMS administrative GUI.

Condition: If an event control administrator tries to modify all endpoints in a large event (using all 48 segments) in CTMS version 1.7, the alarm messages described in "Symptom" may be observed.

Workaround: Modify a small subset of endpoints at a time (<25) instead of updating all endpoints at the same time.

CSCth93803

Symptom: WebEx meetings do not start properly.

Condition: This issue can occur under the following conditions:

An incorrect address is entered in the WebEx TelePresence Gateway URL field in the Configure > WebEx page of the CTMS administrative UI.

Subsequently the correct address is entered in this field.

Workaround: After entering the correct address in the WebEx TelePresence Gateway URL field, restart the CTMS processes to force the system to accept the correct address.

CSCti14371

Symptom: In the CTMS administrative GUI, a single-segment endpoint, which was originally set as a presenter, is still shown as the presenter in a meeting that has no boardroom.

Condition: This issue can occur under the following circumstances:

At least two triple-segment endpoints are in a boardroom with other endpoints.

One of the triple-segment endpoints is set as the boardroom.

A single-segment endpoint is set as the presenter.

The triple-segment endpoint set as the boardroom leaves the meeting.

The original presenter is still shown as the presenter in the meeting that now has no boardroom.

Workaround: Manually remove the role of presenter from the single-segment endpoint, or select a new boardroom then select a new presenter.

CSCti16462

Symptom: Due to a misconfiguration, the CTMS is unable to place a call.

Condition: This issue can occur if the Unified CM1, Unified CM2, and Unified CM3 fields in the Configure > Unified CM page specify invalid or non-working Unified CMs. Under this condition, the CTMS uses the Unified CMs specified in the Unified CM4 and Unified CM5 fields, which are not supported.

Workaround: Specify valid and working Unified CMs in the Unified CM1, Unified CM2, and Unified CM3 fields.

CSCti21782

Symptom: In the Configure > Security page, the administrator clicks the Delete All or Download LSC button, and the following occurs:

Delete All: the System Restart screen should appear but does not. Instead, the Security page continues to display.

Download LSC: the pop-up screen does not close, and the Security page does not refresh with the latest updates.

Condition: These issues can occur if accessing the Configure > Security page when using a Mozilla Firefox browser.

Workaround:

Delete All: reaccess the Security page by clicking the Security link in navigation pane.

Download LSC: close the pop-up screen, and reaccess the Security page by clicking the Security link in navigation pane.

CSCti21821

Symptom: After the system finishes downloading all log files, you change one or more log levels and the system unexpectedly prompts you to download all log files again.

Condition: This issue can occur under the following conditions:

In the Troubleshoot > Log Files page, you clicked "Download All," and the system finished downloading all log files.

Back in the Troubleshoot > Log Files page, you change one or more log levels, then click "Apply."

The system unexpectedly prompts you to download all log files again.

Workaround: To complete the task of changing the log levels, re-access the Log Files page by clicking "Log Files" in the left navigation pane, change the log levels, then click "Apply."

CSCti26725

Symptom: In the Manage > Active Meetings page, a user deletes a large meeting with 20 or more rooms but notices that a few of the rooms are not yet deleted.

Condition: The issue can occur if the user is accessing the Manage > Active Meetings page with a Mozilla Firefox browser.

Workaround: Refresh the Firefox browser.

CSCti31875

Symptom: In a multipoint meeting with 1.5.x or 1.6.x CTS endpoints trying to present, users may see a black presentation window or screen when the call is resumed after it was on hold.

Condition: This issue can occur when CTS endpoints running different software versions (1.5.x or 1.6.x) are in a meeting and the active presenter role changes from one endpoint to another. If a presentation stream is active and a 1.5.x or 1.6.x CTS endpoint connects its presentation cable, the active stream will change. If the newly active presenter places the call on hold, the previous presenter will resume its presentation stream. When the 1.5.x or 1.6.x endpoint resumes the call, a black presentation window or screen could appear.

Workaround: Disconnect then reconnect the presentation cable on the endpoint that resumed the call to retry the role of active presenter.

CSCti38768

Symptom: The video on a WebEx Common Intermediate Format (CIF) video screen freezes momentarily.

Condition: This issue can occur when a new CIF video source is switched to WebEx.

Workaround: This issue resolves itself within a few seconds. No action is required.

CSCti53470

Symptom: A scheduled meeting using one-button-to-push dialing may cause the following CTMS error:

Call can't connect, no active meeting error

Condition: This error can occur if the meeting organizer left the Subject field blank while setting up the meeting in the email client.

Workaround: The meeting organizer should update the meeting with a subject.

Further Problem Description: CTMS does not allow a meeting with a blank Subject field. Although the meeting is scheduled successfully in the email client and CTS-Manager, the conference cannot be started from CTMS, which results in the error message.

CSCti58167

(Duplicate of CSCti14371)

Symptom: Presenter remains set even though it left and rejoined a boardroom meeting.

Condition: An endpoint that was originally set as the presenter in a boardroom leaves then rejoins the meeting. However, the CTMS Administration UI still shows this endpoint as the presenter.

Workaround: Unset that specific presenter if the presenter is in the boardroom, or select a different presenter.

CSCti62790

(Duplicate of CSCti38768)

Symptom: The System Messages page displays several instances of the following INFO-level message: ALARM_MEDIA_SSRCSWITCH_NOTIDR

Condition: This issue can occur in Interop and WebEx meetings when stream switches are frequent. Despite the frequent messages, this condition is benign, and there will be no impact to the audio or video quality of a meeting.

Workaround: Currently, there is no workaround for this issue. To remove the messages from the System Message page, the administrator can select each instance of the message, then click "Clear" at the bottom of the page. Alternatively, they can click "Clear All" to hasten the process; however, this method is not advised as other messages may inadvertently be removed from the page. Neither of these methods will affect the log files in any way.

CSCti62824

Symptom: A meeting ended at its scheduled time, but according to a system message that appeared in the CTMS administrative UI, the meeting was extended past its scheduled end time.

Condition: This issue can occur if a meeting could be extended, but was not.

Workaround: The scenario described in Symptom is benign, and no action is required.

CSCti89282

Symptom: The participant list displays multiple grayed-out VC endpoints.

Condition: When there is more than one active VC Room in a scheduled meeting, this condition can occur.

Workaround: None.

CSCti91916

Symptom: After downloading the Locally Significant Certificate (LSC), reloading the CTMS does not restart the processes.

Condition: Processes are STOPPED after you download the LSC and the CTMS is automatically reloaded.

Workaround: Either manually restart the processes, or select one of the encrypted device security settings from the Unified CM > SIP Profile Settings tab.

CSCti94915

Symptom: An endpoint is dropped from a meeting.

Condition: The CTMS' conference manager may have sent RMP EFC messages when the endpoint was in a state other than the connected state, for example, the hold state. If the conference manager sends these messages while the endpoint is in, for example, the hold state, the endpoint could be dropped from the meeting.

Workaround: Meeting participants should redial that endpoint back into the meeting.

CSCti96592

Symptom: Although a space is an invalid character for an Access Management password, the system currently accepts one or more spaces in these passwords.

Condition: The system currently accepts spaces in Access Management passwords that are being created or updated.

Workaround: In future releases, the system will not accept a space in new and updated Access Management passwords. To accommodate the future enforcement of this invalid character, we recommend that you not use a space in Access Management passwords even though the system currently accepts it.

CSCtj57730

Symptom: After upgrading the CTMS from 1.6.1 to 1.7.0, static meetings with a security policy of Best Effort change to a security policy of Non-Secure.

Condition: In the 1.6.1 CTMS Administrative UI/Unified CM page/SIP Profile Settings tab, Device Security is set to Non-Secure, and Media Encryption is selected.

Workaround:

1. Before upgrading from 1.6.1 to 1.7.0, change the Device Security value to Encrypted with SDP Keys for 7.0 Cisco Unified CM. Apply the changes.

2. Upgrade the CTMS software to 1.7.0.

3. After the upgrade, verify that the static meetings retained their security policy of Best Effort.

4. Change the Device Security value back to Non-Secure with Media Encryption checked.

CSCtj82894

Symptom: The first participant dials across a non-secure intercluster Cisco Unified CM trunk into a secure or best effort meeting on a CTMS that is hosted by Unified CM version 8.0.3 or above. The CTMS is configured with "Encrypted with SDP Keys." When a second participant dials in (could be from anywhere), the first participant is dropped from the meeting and the second participant is put into remote hold by CTMS.

Condition: See Symptom.

Also, the CTMS is secured with Unified CM and uses the "Encrypted with SDP Keys for 8.0.3 Cisco Unified CM" setting for the Device Security attribute in the Unified CM page/SIP Profile Settings tab.

Workaround: On the CTMS, choose the "Encrypted without SDP Keys" setting for the Device Security attribute in the Unified CM page/SIP Profile Settings tab.

CSCtj97946

Symptom: After the CTMS software is upgraded, the setting of the Time Zone attribute in the CTS-Manager page of the CTMS Administrative UI changes from its configured setting to "UTC - Coordinated Universal Time." CTS-Manager uses the Time Zone value to select this closest CTMS for the scheduled meetings. The inadvertent changing of this attribute to "UTC" can in turn cause CTS-Manager to select a CTMS that is not the closest.

Condition: This issue can occur under the following conditions:

The CTMS software is upgraded from release 1.6 to 1.7.

Before the upgrade occurs, Time Zone is set to a value that includes "Etc," for example, "Etc/GMT+8."

Workaround:

Pre-upgrade: Change Time Zone to an applicable value that does not include "Etc."

Post-upgrade: Change Time Zone to an applicable value.

CSCtj98077

Symptom: CTS-Manager fails to push all scheduled multipoint meetings to CTMS.

Condition: This issue can occur under the following conditions:

CTS-Manager release 1.6.5.

CTMS release 1.7.

Intercompany meetings are scheduled. These meetings can cause the push of all scheduled multipoint meetings to fail.

Workaround: None.

CSCtk09141

Symptom: When adding a third endpoint to an intercompany multipoint call, one of the endpoints is dropped.

Condition: The CTMS is running release 1.7.0 software, and the Cisco GSR router is running release 3.7.1 software.

Workaround: When the third endpoint attempts to join the call, place the call on hold then resume it within 5 seconds if possible.

CSCtl91785

Symptom: During a multipoint meeting with Auto Lecture Mode enabled, endpoint A is the active speaker and receives a scrolling view of all participants. After Auto Lecture Mode is disabled, endpoint A continues to receive the scrolling view of all participants.

Condition: See Symptom. This issue can occur if the CTMS is running release 1.7 software.

Workaround: On endpoint A, place the call on hold, then resume it. This action should disable the scrolling view.

CSCtl91785

Symptom: During a multipoint meeting with Auto Lecture Mode enabled, endpoint A is the active speaker and receives a scrolling view of all participants. After Auto Lecture Mode is disabled, endpoint A continues to receive the scrolling view of all participants.

Condition: See Symptom. This issue can occur if the CTMS is running release 1.7 software.

Workaround: On endpoint A, place the call on hold, then resume it. This action should disable the scrolling view.

New and Changed Information for CTMS Release 1.6.4

Support for Non-CABAC Endpoints

CTMS 1.6.4 supports endpoints that do not use the context-adaptive binary arithmetic coding (CABAC) mechanism when encoding video. Those endpoints must indicate through Media Options signaling in the Telepresence Interoperability Protocol (TIP) that they are not using CABAC.

CTS endpoints must run software version 1.6.5 or later to support endpoints that do not use CABAC in meetings with CTMS.

Caveats

The following caveats were fixed in CTMS Release 1.6.4:

CSCte91304: Call dropped because of CTMS process restart.

CSCtf26422: Conference manager does not resume participants on hold in a One-Button-to-Push meeting.

CSCth02270: Call dropped because of an internal timeout.

CSCth14515: When a meeting is started, CTMS processes restarted with this error message:

Execution Manager detected a process(confmgr signal=11) dead, will try restarting CTMS processes shortly

New and Changed Information for CTMS Release 1.6.3

Caveats

The following caveats were fixed in CTMS Release 1.6.3:

CSCsz50977: CLI printStatistics showing incorrect mux version for the endpoint.

CSCtc77674: LTRP enabled when CUVC 7.0 connection was restored.

CSCtc85023: LTRP_REPAIR_MISMATCH message is false alarm.

CSCtd68603: Jitter in top portion of CTS screen.

CSCte63487: Scheduled multipoint call failed because a config manager process was terminated.

New and Changed Information for CTMS Release 1.6.2

Caveats

The following caveat was fixed in CTMS Release 1.6.2:

CSCta57597: CTMS Adhoc call fails to dial out. The number dialed is an access number.

New and Changed Information for CTMS Release 1.6.1

Caveats

The following caveats were fixed in CTMS Release 1.6.1:

CSCtd60678: Pixilation during secure multipoint call with auth failure packets. The Rx Pkts AuthFail counter increases.

CSCtd60840: Pixilation during multipoint call with out-of-order packets.

CSCtd68551: When CTMS is on 7845I2 or 7835I2 platform, admin CLI access is denied with lines of java exceptions. Most GUI features are not available.

CSCtd68559: Random screen flickering sometimes seen.

New and Changed Information for CTMS Release 1.6.0

Upgrading to CTMS Release 1.6.0

When upgrading to CTMS Release 1.6.0, you must be running CTMS Release 1.1.2 or later. If you are running a version earlier than CTMS Release 1.1.2, update to CTMS Release 1.1.2 before upgrading to CTMS Release 1.6.0.

Standard Event Controls: VIP Mode, Auto Lecture Mode, and Boardroom Mode

In addition to VIP Mode, which was supported in previous releases, CTMS Release 1.6.0 supports Auto Lecture Mode and Boardroom Mode. All modes enable the CTMS administrator to manage the audio and video for specific events.

Auto Lecture Mode

With CTMS Release 1.6.0, CTMS supports Auto Lecture Mode. When Auto Lecture Mode is enabled for a particular multipoint meeting (using the CTMS administrative GUI), the first speaker or room speaking uninterrupted for 60 seconds (60 seconds is the default) becomes the "lecturer." In Auto Lecture Mode, all sites see the "lecturing" speaker or room based on the switching policy (room or speaker). The lecturing site sees a scrolling view of all rooms in the meeting; a new room is displayed every 10 seconds (10 seconds is the default). During the meeting, if someone other than the lecturer speaks for approximately 2 seconds (approximately 2 seconds is the default), the lecturer is reset and the meeting returns to its standard switching policy. A lecturer is set again as soon as someone speaks uninterrupted for 60 seconds.

You can customize the Auto Lecture Mode default times by entering the set damping command in the CTMS admin CLI. See the CTMS release 1.6 command reference for information about this command:

http://www.cisco.com/en/US/products/ps7315/prod_command_reference_list.html

Boardroom

With CTMS Release 1.6.0, CTMS supports Boardroom Mode through the CTMS administrative GUI. Boardroom Mode allows for a highly customized boardroom configuration. When Boardroom Mode is enabled for a particular multipoint meeting, the administrator must first set a room as the boardroom. Then the administrator can specify presenters. The boardroom must use a CTS 3x00. Boardroom Mode must be enabled through the CTMS administrative CLI in order to use this feature from the CTMS administrative GUI.

Professional Event Controls: Director Controls Through the CTMS Administrative CLI

With CTMS Release 1.6.0, CTMS supports Director Controls. Director Controls allow an administrator to control any or all of the media options available for any multipoint meeting. Large events or scripted meetings often require manual mapping and locking of video and mapping or muting of video on a per-segment basis. With Director Controls, an advanced administrator can script and control large multipoint meetings. CTMS release 1.6 provides Director Controls through the CTMS admin CLI. See the CTMS release 1.6 command reference for a complete list of commands:

http://www.cisco.com/en/US/products/ps7315/prod_command_reference_list.html


Note To use the CLI commands for Director Controls, the CTMS and CTS must run software release 1.6 or a later release.


High Definition Interoperability

With CTMS Release 1.6.0, Cisco TelePresence supports high definition interoperability between Cisco TelePresence systems and other video conferencing/video telephony endpoints using the Cisco Unified Videoconferencing 5230 MCU using CUVC Release 7.0 software (CUVC 7.0).


Note HD Interop calls with T1/Extended Reach endpoints might experience video quality issues if any endpoint in the meeting has high packet loss.



Note CUVC 5xxx platforms running 7.01 or higher are not compatible with CTMS 1.5 and prior. CUVC 5xxx platforms require CTMS Release 1.6.


Extended Reach

With CTMS Release 1.6.0, you can enable or disable Extended Reach (the default is enabled). With Extended Reach enabled, if a T1 endpoint joins a meeting, Conference Manager downgrades the meeting quality to 720p Lite. T1 endpoints are kept in the meeting, but pre-1.6 endpoints are dropped. If you disable Extended Reach, Conference Manager rejects incoming T1 endpoints. Pre-1.6 endpoints are kept in the meeting.

The CTMS admin CLI to enable or disable Extended Reach is set t1mode {true | false}, where true mean enable and false means disable.

Caveats

The following caveats from previous releases were fixed in CTMS Release 1.6.0:

CSCso21301: When SNMP user is deleted through admin CLI, only the username or community string is checked; password, access, or authentication level was not checked.

CSCsx10991: KeyExchange process doesn't count towards dead process and status is incorrectly shown as green instead of red.

CSCsx27088: Endpoint drops in Secure/Best Effort multipoint meetings. The CTMS reports "Media Timeout" system errors in the CTMS WebUI.

CSCsx74508: CTS screen in black and there is no audio.

CSCta33668: MTRG empty files should be removed from Log Files.

CSCta40704: Unprotect errors; possibility of MediaProcessor crash during secure meetings.

CSCta45951: When upgrading CTMS from Release 1.1.2(6) to Release 1.5.3(11), SNMP user will have a user name "cros" added.

CSCta45967: After upgrading CTMS, trap host may not receive any trap notify from CTMS.

CSCta47547: When upgrading to CTMS Release 1.5.3(11), admin may experience a exception when accessing the SNMP Setting from Web UI.

CSCta74500: Calls drop because of DTLS timeout and security mismatch.

CSCta74466: SNMPD trap notify may not be received after SNMPD stopped.

CSCta92390: Endpoints registered to three Unified CM devices during a static meeting will result in call drop.

CSCtc62620: Screens do not switch after endpoint does hold/resume in multipoint meeting.

The following caveats were identified in CTMS Release 1.6.0:

CSCsw50200: The host cannot join meeting after a user locks the meeting while it is active.

CSCta57505: Found nested exception is: java.net. ConnectException: Connection refused.

CSCtc20725: Presentation causing RXOFF statements.

CSCtc23584: Endpoint drop with error code = NO_RESUME during overnight testing.

CSCtc43708: CTMS does not drop CUVC leg while legacy stream has huge packet loss.

CSCtc57680: Uploading invalid certificate gives 'null' and 'Go Back' page

CSCtc57727: MEDIA_EP_NOTRESPOND alarm after CloseEndPoint().

CSCtc66419: 1.4.7 CTS got dropped from CTMS 1.6.0 best effort when other CTSs resume

CSCtc68768: Delete Domain and DNS from web-ui gives error message

CSCtc70726: "Feedback not received" system error displays for meetings with presentation.

CSCtc71031: 1.6.0 LTRP SPIMAP TIMEOUT drop call

CSCtc85023: False Alarm of LTRP_REPAIR_MISMATCH.

CSCtc88319: Quality drop list does not show all 6 values when Interop Yes > No

CSCtd11725: Meeting Security Policy to non-secure should not affect static meetings

CSCtd29406: Upgrade does not populate Dial Suffix for HD Interoperability

Software Releases and Component Firmware Versions

For the current recommended set of software releases and component firmware versions for the Cisco TelePresence solution, see the information located at the following URL:

http://www.cisco.com/en/US/partner/docs/telepresence/cts_admin/1_6/release/Notes/cts_1_6_release_notes.html#wp42142

Caveats for CTMS Release 1.6.x

Caveats were recorded in the following CTMS Release 1.6.x. releases:

CTMS Release 1.6 Caveat Reference

Caveats for CTMS Release 1.6.0

CTMS Release 1.6 Caveat Reference

Table 6 summarizes caveats found in CTMS Release 1.6.x.

Table 6 CTMS Release 1.6 Caveats and Caveats Corrected Reference 

 

Software Release

 

1.6.0

CDETS Number

Found in Release

Corrected in Release

CSCsw50200

1.6.0

Closed, software works per design

CSCtc43708

1.6.0

Closed, software works per design

CSCtc68768

1.6.0

1.7.2

CSCtc71031

1.6.0

1.7.0

CSCtc85023

1.6.0

1.6.3

CSCtc88319

1.6.0

1.7.0

CSCtd11725

1.6.0

1.7.0

CSCtd29406

1.6.0

1.7.0

CSCtn27679

1.6.3

None


Caveats for CTMS Release 1.6.0

CSCsw50200

Symptom: A lock can be placed on a hosted meeting and not allow the host to join.

Condition: For a hosted meeting, a participant can 'lock' the meeting from the phone UI and prevent the host from joining the meeting. When the host tries to join the meeting, the host gets a message stating the meeting is locked. The host cannot join.

Workaround: The administrator or meeting participant must first unlock the meeting so that the host can join.

CSCtc43708

Symptom: Call drops during interop MP meeting.

Conditions: 1. Packet loss introduced from legacy stream. 2. Large NTP time updates (this is a rare occurrence).

Workaround: None.

CSCtc68768

Symptom: Deleting DNS and Domain Name will give an error message

Conditions: On System Settings -> IP Settings page, if you remove the DNS and Domain Name fields and click Apply, an error message box shows with: Domain Name '' is not a valid value.

Workaround: To remove DNS altogether, leave the Domain Name field and just remove the DNS entries and Apply. When the CTMS restarts, there will be no DNS.

CSCtc71031

Symptom: Call drops. And CTMS alarm page shows SPIMAP timeout

Conditions: It only happens when at the time of the call join, another meeting which has lots of room joins and leaves activity, which is not likely to happen in real world, is ending.

Workaround: Redial the meeting.

CSCtc85023

Symptom: A false alarm is raised during a meeting when adding an older endpoint and afterward that same endpoint drops from the meeting.

Condition: During a meeting with one active speaker, when an older endpoint joins or is added (LTRP is turned off) and that same older endpoint is then dropped or drops from the meeting (LTRP is turned back on), this false system error WARN alarm is displayed: CTMS_ALARM_MEDIA_LTRP_REPAIR_MISMATCH.

Workaround: This alarm does not impact the meeting.

CSCtc88319

Symptom: 1080p quality selection is not available after changing Interop selection to No in the Static Meetings detail screen.

Conditions: User wants to change an existing Interop (1080p or 720p) static meeting to non-Interop 1080p meeting. In the Static Meetings popup window, after selecting No for Interop, the Quality droplist only shows 720p.

Workaround: Select the 720p quality (even though 1080p is desired) and click Save. Then select the same static meeting again and change the quality to 1080p.

CSCtd11725

Symptom: Change Security Policy back to Non-Secured will also change all static meetings to Non-Secured.

Conditions: After securing a CTMS, the Security Settings Meeting Security Policy can be changed. If this is changed from Non-Secure, and static meetings with Best-Effort and Secured Policies are created, if this the Security Settings Meeting Security Policy is changed back to Non-Secure, the static meetings will also be changed to Non-Secure.

Workaround: Edit each static meeting to set Meeting Security Policy to Best-Effort and Secured.

CSCtd29406

Symptom: Upgrade does not populate Dial Suffix for HD Interoperability

Conditions: Dial Suffix for HD Interoperability is a required field for the Default Settings page, but after an upgrade from a pre-1.6 CTMS version, this field is left blank.

Workaround: Manually input #*#000 in the Dial Suffix for HD Interoperability field.

CSCtl84403

Symptom: In the Configure > CTS-Manager page of the CTMS administrative UI, the Registration Status is "Not yet registered" even though scheduled multipoint meetings can be pushed to CTMS.

Conditions: This issue can arise if the CTMS sustained a loss of power. As a result, Trigger Registration from CTS-Manager fails to register.

Workaround: To force the registration, you can make a minor modification in the Configure > CTS-Manager page, and click Apply.

CSCtn27679

Symptom: The snmpwalk application queries the SNMP OID 10.3.3.17 1.3.6.1.4.1.9.1.587 on the CTMS, which in turn causes the CTMS SNMP service to become disabled.

Conditions: This issue might occur in rare through currently unknown conditions if the CTMS is running software version 1.6.3.

Workaround: Restart the CTMS SNMP service using the utils service snmp start command in the CTMS command-line interface (CLI).

New and Changed Information for CTMS Release 1.5.6

Software Upgrade Caveat

When upgrading the CTMS software from build 1.5.6(1) to 1.7.0, keep in mind that build 1.5.6(1) does not support the downloading of 1.7.0 software from your network using FTP.

New and Changed Information for CTMS Release 1.5.4

The following caveats from previous releases were fixed in CTMS Release 1.5.4:

CSCta57580: When SNMPD stopped from admin CLI, Web UI still shows SNMP is ENABLED.

CSCta57797: After upgrading to CTMS Release 1.5.3, the default admin user for SNMP may get removed.

CSCtb63708: The endpoint cannot join multipoint calls. All static meetings failed on the CTMS server, and the call was disconnected within seconds.

CSCtb63738: CTMS conference controls do not work when an HTTP proxy server is used between the CTS endpoint and CTMS.

CSCtb63770: When an external URL with additional appended data is configured in the CTMS, CTMS conference controls do not work. The CTMS returns a 404 error to the CTS endpoint.

New and Changed Information for CTMS Release 1.5.3

The following caveats from previous releases were fixed in CTMS Release 1.5.3:

CSCsz66410: A SNMPWALK will fail on CTMS server.

CSCta07212: Legacy endpoint off CUVC can't hear one specific Cisco TelePresence participant, but can see video.

CSCta57597: CTMS Adhoc call fails to dial out. The number dialed is an access number.

CSCta79047: Multiple call drops from random rooms.

The following caveats were identified in CTMS Release 1.5.3.

CSCso13993: Sysop log reports packet loss percentage call from center (e.g., 25% or 100%) while no audio issue is noticed.

CSCta33668: MTRG empty files should be removed from Log Files.

CSCta38768: Import kept Best-Effort and Secure settings for static meetings.

CSCta40704: Unprotect errors; possibility of MediaProcessor crash during secure meetings.

CSCta45951: When upgrading CTMS from Release 1.1.2(6) to Release 1.5.3(11), SNMP user will have a user name "cros" added.

CSCta45967: After upgrading CTMS, trap host may not receive any trap notify from CTMS.

CSCta47547: When upgrading to CTMS Release 1.5.3(11), admin may experience a exception when accessing the SNMP Setting from Web UI.

CSCta57580: When SNMPD stopped from admin CLI, Web UI still shows SNMP is ENABLED.

CSCta57797: After upgrading to CTMS Release 1.5.3, the default admin user for SNMP may get removed.

CSCta74252: Static CUVC meeting can barge in on the scheduled meeting.

CSCta74466: SNMPD trap notify may not be received after SNMPD stopped.

CSCta92390: Endpoints registered to three Unified CM devices during a static meeting will result in call drop.

CSCtc62620: Screens do not switch after endpoint does hold/resume in multipoint meeting.

For a list of the caveats associated with CTMS Release 1.5.3, see Caveats for CTMS Release 1.5.3

New and Changed Information for CTMS Release 1.5.2

CTMS Hardware MIB Support

CTMS hardware MIB support was added for the Hewlett Packard/IBM 7985 platform.

New and Changed Information for CTMS Release 1.5.1

CSCsv99142 was resolved in CTMS Release 1.5.1. For a list of the caveats associated with CTMS Release 1.5.1, see Caveats for CTMS Release 1.5.1.

New and Changed Information for CTMS Release 1.5.0

Upgrading to CTMS Release 1.5.0

When upgrading to CTMS Release 1.5.0, you must be running CTMS Release 1.1.2 or later. If you are running a version earlier than CTMS Release 1.1.2, upgrade to CTMS Release 1.1.2 before upgrading to CTMS Release 1.5.0.

Cisco TelePresence Manager (CTS-MAN) Intercompany Communication

CTMS Release 1.5 now includes additional CTS-MAN configuration fields to define the dialing system CTMS and CTS-MAN use to establish intercompany TelePresence meetings.

CTMS Security Features

Starting with CTMS Release 1.5, CTMS supports the following security features:

Multipoint Encryption (MPE)

Media Encryption in the absence of Secured SIP Signalling

Secured Web-Services communication between CTMS and CTS-MAN

HTTP Proxy for CTMS

CTMS Release 1.5 supports an inbound HTTP Proxy for CTMS. The external URL provides CTMS web services for external third-party web service clients in an intercompany communication environment.

NTP Server Configuration

CTMS Release 1.5 supports Network Time Protocol (NTP); NTP is used to synchronize the clocks on Cisco IP telephony servers with an external network time server that uses NTP.

Software Releases and Component Firmware Versions

Table 7 provides the current recommended set of software releases and component firmware versions for the Cisco TelePresence solution.

Table 7 Software Releases and Component Firmware Versions  

Product/Component
Recommended Version
Release Date

Cisco TelePresence System (CTS)

1.5.3(10)

7/22/2009

CTS component firmware: Display AppCode for Gen1 Displays

1.05

8/15/2007

CTS component firmware: Display BootCode for Gen1 Displays

1.01

8/15/2007

CTS component firmware: Display App_Code for Gen2 Displays

11.0A

9/11/2008

CTS component firmware: Display BootCode for Gen2 Displays

11.05

8/15/2007

CTS component firmware: Camera firmware version

390

2/7/2008

Cisco TelePresence Manager (CTS-MAN)

1.5.1

6/2/2009

Cisco TelePresence Multipoint Switch (CTMS)

1.5.3

7/22/2009

Cisco Unified Communications Manager (Unified CM)

6.1.3 or 7.0.2 or greater

12/2008; 2/2009

Cisco Unified IP Phone 7970G

8.4(3)

2/2009

Cisco Unified IP Phone 7975G

8.4(3)

2/2009


Caveats for CTMS Release 1.5.x

Caveats were recorded in the following CTMS Release 1.5.x releases:

CTMS Release 1.5 Caveat Reference

Caveats for CTMS Release 1.5.4

Caveats for CTMS Release 1.5.3

Caveats for CTMS Release 1.5.2

Caveats for CTMS Release 1.5.1

Caveats for CTMS Release 1.5.0

CTMS Release 1.5 Caveat Reference

Table 8 summarizes caveats found in CTMS Release 1.5.x.

Table 8 CTMS Release 1.5 Caveats and Caveats Corrected Reference 

 

Software Release

 

1.5.4

CDETS Number

Found in Release

Corrected in Release

 

No new caveats found in release 1.5.4

 
 
 

1.5.3

CDETS Number

Found in Release

Corrected in Release

CSCso13993

1.5.3

1.7.0

CSCta33668

1.5.3

1.6.0

CSCta38768

1.5.3

1.7.0

CSCta40704

1.5.3

1.6.0

CSCta45951

1.5.3

1.6.0

CSCta45967

Duplicate of
CSCta74466

1.5.3

1.6.0

CSCta47547

1.5.3

1.6.0

CSCta57580

1.5.3

1.5.4

CSCta57797

1.5.3

1.5.4

CSCta74252

1.5.3

None

CSCta74466

Duplicate of
CSCta45967

1.5.3

1.6.0

CSCta92390

1.5.3

1.6.0

CSCtc62620

1.5.3

1.6.0

 
 

1.5.2

CDETS Number

Found in Release

Corrected in Release

CSCsz66410

1.5.2

1.5.3

CSCta57597

1.5.2

1.5.3

CSCta79047

1.5.2

1.5.3

CSCtb63708

1.5.2

1.5.4

 
CDETS Number
1.5.1
Found in Release
Corrected in Release

None

   
CDETS Number
1.5.0
Found in Release
Corrected in Release

CSCso21301

1.5.0

1.6.0

CSCsu61389

1.5.0

1.5.2

CSCsv71090

1.5.0

1.5.0

CSCsv30700

1.5.0

1.5.0

CSCsv30853

1.5.0

1.5.0

CSCsv84170

1.5.0

1.5.1

CSCsv99059

1.5.0

1.6.0

CSCsv99142

1.5.0

1.5.1

CSCsw18834

1.5.0

1.5.2

CSCsw63631

1.5.0

1.5.1

CSCsw68069

1.5.0

1.5.2

CSCsw46206

1.5.0

1.5.2

CSCsw46476

1.5.0

1.5.2

CSCsw47840

1.5.0

1.5.1

CSCsw63631

1.5.0

1.5.2

CSCsx10991

1.5.0

1.6.0

CSCsx11395

1.5.0

1.5.2

CSCsx27088

1.5.0

1.6.0

CSCsx29728

1.5.0

1.5.2

CSCsx67502

1.5.0

1.5.2

CSCsx74508

1.5.0

1.6.0

CSCsx83681

1.5.0

1.5.2

CSCsx98212

1.5.0

1.5.2

CSCsy59071

1.5.0

1.5.2

CSCta07212

1.5.0

1.5.0

CSCta74500

1.5.0

1.6.0


Caveats for CTMS Release 1.5.4

No new open caveats in CTMS release 1.5.4.

Caveats for CTMS Release 1.5.3

CSCso13993

Symptom: Sysop log reports packet loss percentage call from center (e.g., 25% or 100%) while no audio issue is noticed.

Condition: During a CTS multipoint call, packet loss is reported, but no audio issue is notice and call isn't dropped.

1. When Site B overrides Site A's presentation, and Site A's presentation becomes active again, it is possible that the meeting will report a large packet loss. This is because when A's presentation is originally overridden, another audio stream will not necessarily be sent automatically (only if someone talks). So, if site A's presentation becomes active again, it is possible it may send to the same decoder as it did before, and look like a large gap in packets, causing the call to report loss.

2. A triple CTS display with two single CTS displays where one of the single CTSs ends the call or goes on hold.

If a CTS has been receiving multiple audio streams from CTMS and, if CTMS stops sending audio streams, CTS will show packet loss in its statistics and sysop logs. CTMS may not have additional streams to forward to CTS.

Workaround: Hang up and call again or add another CTS.

CSCta33668

Symptom: MTRG empty files are found in Log Files for fresh install or upgrade to 1.5.3(2).

Condition: After fresh install or upgrade to CTMS 1.5.3(2), mrtg.cfg_l_# files in the Log Files section are 0.0 size and are not necessary.

Workaround: A root-enabled or remote-account needs to be created to remove these empty and benign files from the CTMS server log directory if these are bothersome.

CSCta38768

Symptom: Import kept Best-Effort and Secure settings for static meetings.

Condition: When a previous export is completed on a secure CTMS, the best-effort and secure static meetings configured will be exported with the security policy setting.

If a fresh install is done, the CTMS is non-secure. Before making the CTMS secure, if that export file is imported, the best-effort and secure static meeting security policy flag remains. If a customer attempts to call those static meetings numbers, the meeting will fail.

Workaround: Make the CTMS secure or change individual static meetings to non-secure to be used with non-secure CTMS.

CSCta40704

Symptom: Unprotect Errors; possibility of MediaProcessor crash during secure meetings.

Condition: When legacy video packets from the CTS are received in a secure meeting, during authenticating, the packet will result in UnProtect Errors/MediaProcessor crash because the packet size is too small.

Workaround: Use non-secure meetings.

CSCta45951

Symptom: When upgrading CTMS from Release 1.1.2(6) to Release 1.5.3(11), SNMP user will have a user name "cros" added.

Condition: Upgrading from CTMS Release 1.1.2(6) to Release 1.5.3(11).

Workaround: None.

CSCta45967

Symptom: After upgrading CTMS, trap host may not receive any trap notify from CTMS.

Condition: After upgrading CTMS to a new release.

Workaround: Stop and restart SNMP daemon on trap host.

CSCta47547

Symptom: When upgrading to CTMS Release 1.5.3(11), admin may experience a exception when accessing the SNMP Setting from Web UI.

Condition: Upgrading to CTMS Release 1.5.3(11) and then accessing SNMP Setting from Web UI.

Workaround: After the upgrade, wait for 3 to 5 minutes before accessing the SNMP setting from Web UI.

Further Problem Description: After upgrading, SNMPD is not up before the WebUI is available to CTMS admin; when accessing SNMP Setting, query to SNMPD will fail.

CSCta57580

Symptom: When SNMPD stopped from admin CLI, Web UI still shows SNMP is ENABLED.

Condition: SNMPD stopped from Admin CLI, or any condition that stops SNMPD.

Workaround: None

Further Problem Description: The SNMPD status was not sync'ed up on Web UI.

CSCta57797

Symptom: After upgrading to CTMS Release 1.5.3, the default admin user for SNMP may get removed.

Condition: Upgrading to CTMS Release 1.5.3.

Workaround: 1. Modify admin user before the upgrade;

2. Add admin user back after the upgrade.

CSCta74252

Symptom: Static CUVC meeting can barge in on the scheduled meeting.

Condition: Static CUVC meeting, created using the same CUVC access number as a scheduled CUVC meeting, can sometime barge in on the scheduled meeting.

Workaround: Make sure that static CUVC meetings and scheduled CUVC meetings are configured with different CUVC access numbers.

CSCta74466

Symptom: SNMPD trap notify may not be received after SNMPD stopped.

Condition: When using SNMP version 3 trapdest, when performing an SNMP operation (add user, del user, stop and start/restart SNMPD), SNMP trap host may stop receiving the trap notify from CTMS SNMP agent.

Workaround: Stop trap host SNMP daemon, and restart trap host daemon.

CSCta92390

Symptom: When CTMS receives signaling from three Unified CM devices, endpoint will drop with Error code=ERROR.

Condition: With three Unified CM devices configured for endpoints or across an ICT SIP trunk, the CTMS will keep track of two at a time, so the third endpoint is dropped with Error Code=ERROR.

Workaround: Only have endpoints loads shared across two Unified CM devices in a cluster.

CSCtc62620

Symptom: Screen or screens are not switched during a multipoint meeting.

Condition: After one endpoint goes on hold and then resumes.

Workaround: Another endpoint in the meeting (not the one that first went on hold and then resumed) goes on hold and then resumes. Screen switching should function properly after this second hold/resume.

Caveats for CTMS Release 1.5.2

CSCsz66410

Symptom: A SNMPWALK will fail on CTMS server.

Condition: When SNMPWALK is performed.

Workaround: There is no user workaround, please contact Cisco TAC for assistant.

Further Problem Description: The SNMP configuration is corrupted due to a conflict between SNMP cron job start up and hardware MIB accessing SNMP configuration. As long as SNMP is not restarted by cron job, SNMP works fine. Cron job runs every 5 minutes so SNMP need to be stopped and started again in-between this intervals.

Fixed: CTMS Release 1.5.3

CSCta57597

Symptom: CTMS Adhoc call fails to dial out. The number dialed is an access number.

Condition: CTMS access number range overlaps with CTS domain name configuration. Static meetings are configured on CTMS, which includes configured access numbers. The last eight digits match that of the dialed DN of endpoint with which CTMS is trying to establish an adhoc call.

Workaround: Delete the conflicting static meeting on CTMS, configure access number for static meeting so that last eight digits of access number are not associated with CTS DN.

Additional workaround is to modify route pattern and CTMS access numbers so that they do not overlap that of CTS DN range configured in enterprise.

Fixed: CTMS Release 1.5.3

CSCta79047

Symptom: Multiple call drops from random rooms.

Condition: 200 OK sip message for session refresh is delayed on CTMS.

Workaround: None

CSCtb63708

Symptom: The endpoint cannot join multipoint calls. All static meetings failed on the CTMS server, and the call was disconnected within seconds.

Conditions: From CTMS SIP logs, CTMS did not get a response from Cisco Unified CM for the Reinvites that the CTMS sent. The SIP responses from the Cisco Unified CM that arrived on the CTMS were not honored by CTMS.

Workaround: There is no workaround.

Caveats for CTMS Release 1.5.1

There are no listed caveats for CTMS 1.5.1.

Caveats for CTMS Release 1.5.0

CSCso21301

Symptom: When SNMP user is deleted through admin CLI, only the username or community string is checked; password, access, or authentication level was not checked.

Condition: When SNMP user is deleted through admin CLI.

Workaround: None

CSCsu61389

Symptom: DNS change is not reflected in Web-UI.

Condition: When making DNS changes through Admin CLI, it is not reflected on the Web-UI until the CTMS is rebooted.

Workaround: Restart the CTMS.

CSCsv71090

Symptom: User sees this alarm "Error checking own private key" in CTMS alarm log, maybe multiple times.

Condition: File corruption or some failure in CAPF certificate downloading.

Workaround: Perform the following:

Change Device Security to "Non-Secured."

Delete all certificates.

Install all certificates again.

Change to the desired security level.

Fixed: CTMS Release 1.5

CSCsv30700

Symptom: Thirty frames per second (30FPS) is not supported on satellite endpoints.

Condition: 30FPS configured on endpoints without additional 30FPS codec support. Typically, 30FPS presentations take up additional bandwidth that satellite endpoints are unable to handle.

Workaround: None

Fixed: CTMS Release 1.5

CSCsv30853

Symptom: Secure to Non-Secure meeting has 50% chance to recover correct presentation.

Condition: When a secure meeting is downgraded to non-secure with two endpoints plugged in for displaying presentation, the presentation seen before the downgrade has a 50% chance of recovering.

The downgrade performs a hold on the endpoints, so the last endpoint with presentation that resumes will take over showing presentation, which may not be the one presenting before the security downgrade.

Workaround: Endpoint with presentation to display must restart their presentation (unplug/plug in) again.

Fixed: CTMS Release 1.5

CSCsv84170

Symptom: Call fails when congestion was detected on source endpoint; no SNMP trap was generated.

Condition: Receiving loss rate:100.00 percent. Any condition that causes call failure results in an alarm logged in the Syslog (/var/log/active/syslog/messages ).

Workaround: Need to look in /var/log/active/syslog/messages file.

Fixed: Release 1.5.1

CSCsv99059

Symptom: From the Setting page, when the "Idle Meeting Termination Enabled" parameter is set to "No," an error message is displayed stating that the parameter cannot be left blank.

Condition: Whenever users change the stated parameter value, the error window is displayed.

Workaround: Click "OK" to close the window. The error doesn't have any adverse affect.

CSCsv99142

Symptom: NTP servers added through GUI do not show in GUI after upgrade.

Condition: Only affects the NTP server list as displayed in GUI.

Workaround: Users need to add NTP servers again after upgrade.

Fixed: Release 1.5.1

CSCsw18834

Symptom: Call drops in Secure/Best Effort multipoint meetings. The CTMS report "Media Timeout" errors/alarms in the CTMS WebUI.

Condition: The problem could occur between CTMS Release 1.5 and CTS Release 1.5 under the following conditions:

Cisco Unified Communications Manager (Unified CM) Release 6.1.X is present in the communication path between CTMS and CTS.

There is a failure in exchanging keys between CTMS and CTS for enabling secure calls.

Workaround: There is no workaround; dialing back from the CTS into the CTMS could work.

Fixed: CTMS Release 1.5.2

CSCsw63631

Symptom: Same interop extension was connected twice.

Condition: User dials out to interop meeting. Before the CUVC is added, user's call was disconnected. In this case, CUVC will not hang up.

Workaround: Delete the meeting from the WebUI and redial again.

Fixed: CTMS Release 1.5.1

CSCsw68069

Symptom: A CUVC caller can become the active speaker when a four-party meeting has a Telepresence caller hang up. Sometimes the CUVC caller may not switch into the meeting until another speaker switch occurs.

Condition: When four CTS callers are in a meeting and one hangs up, causing the CUVC session to become active speaker.

Workaround: Press hold/resume on one of the endpoints. Upon resume, the CUVC session should switch in when it becomes the active speaker again.

Fixed: CTMS Release 1.5.2

CSCsw46206

Symptom: Dialing status window for Adhoc calls shows congestion error.

Condition: Cisco Unified CM returns a "503: Service Unavailable" to CTMS for instances where the number may not be registered to Cisco Unified CM or it could be an internal Cisco Unified CM issue.

Workaround: None.

Fixed: CTMS Release 1.5.2

CSCsw46476

Symptom: CTMS will display error code = ERROR alarm from the Conference Manager.

Condition: Delays in the Cisco Unified CM or endpoint will cause Cisco Unified CM to drop the call, resulting in this error message.

Workaround: None.

Fixed: CTMS Release 1.5.2

CSCsw47840

Symptom: System Status graphs don't display CTMS traffic correctly.

Condition: When Interface Failover is enabled and network traffic has been redirected through Ethernet 1 (caused by a failure on Ethernet 0).

Workaround: There are no direct workarounds to graph the traffic flowing on Ethernet 1; however data on all network interfaces can be retrieved using SNMP. Follow the steps below for setup:

From the CTMS admin CLI, create a SNMP User:

set snmp user add 3 <userID> r <userPassword>

From a remote machine, retrieve all network interface-based data:

snmpwalk -v3 -m ALL -u <userID> -l authNoPriv -a MD5 -t 3 -A <userPassword>
<CTMS HostName> ifEntry

CSCsw63631

Symptom: Same interop extension was connected twice.

Condition: User dials out to interop meeting. Before the CUVC is added, user's call was disconnected. In this case, CUVC will not hang up.

Workaround: Delete the meeting from the CTMS Web GUI and redial again.

Fixed: CTMS Release 1.5.2

CSCsx10991

Symptom: KeyExchange process doesn't count towards dead process and status is incorrectly shown as green instead of red.

Condition: In CTMS WebUI, the Status pane in the lower left corner displays information about the state of the inner CTMS processes. If even one of the process is dead, this status should alert us in red. If the KeyExchange process is down and not running, the Status pane status is displayed as green. This happens only if the KeyExchange process is dead.

Workaround: This happens only during the time KeyExchange process is dead. The CTMS Execution Manager restarts all the processes immediately upon detecting a dead process.

CSCsx11395

Symptom: After upgrading CTMS, the QoS settings revert back to the default settings. The Media settings are not persisted across upgrades.

Condition: Following an upgrade

Workaround: If you've changed the QoS settings before an upgrade, you must change them again after the completion of the upgrade.

Fixed: CTMS Release 1.5.2

CSCsx27088

Symptom: Endpoint drops in Secure/Best Effort multipoint meetings. The CTMS reports "Media Timeout" system errors in the CTMS WebUI.

Condition: This happened only one time. If there is a delay synchronizing keys between various CTMS components, it will result in a Media Timeout error message shown on the WebUI and the endpoint dropping or not being able to join a meeting.

Workaround: None; the user will need to dial back into the meeting.

CSCsx29728

Symptom: Call control raises unknown alarm in System Errors page of Web GUI.

Condition: Service location between CTS and CTMS times out.

Workaround: None

Fixed: CTMS Release 1.5.2

CSCsx67502

Symptom: CTS black screen and DSP crash on non-secure endpoint.

Condition: Secure endpoint is in the process of SIP negotiation, which takes longer than normal processing time due to network delay.

Workaround: Wait for the endpoint to restart and dial in again.

Fixed: CTMS Release 1.5.2

CSCsx74508

Symptom: CTS screen in black and there is no audio.

Condition: Rapid, back to back, multiple hold/resumes from the phone without any pause in-between.

Workaround: None

CSCsx83681

Symptom: The calls in all meetings drop.

Condition: The problem could happen if there is network delay and SIP messages from Cisco Unified CM are delayed and CTMS hits a specific message timeout pattern.

Workaround: None

Fixed: CTMS Release 1.5.2

CSCsx98212

Symptom: After upgrade CTMS to 1.5.0(222), SNMP user and trapdest configuration is lost.

Condition: Upgrade CTMS to 1.5.0(222).

Workaround: Create new user and trapdest. Username "admin" can not be used so you need to add user other than "admin."

Example: To add SNMP user for v3 and v2c:

admin:set snmp user add 3 adminuser rw snmppassword
Successfully added user
 
   
admin:set snmp user add 2c testadmin
Successfully added user
 
   

Example: To add trapdests:

admin:set snmp trapdest add 3 v3trapdest <Traphost IP address>:162 v3password
Successfully added trap destination

CSCsy59071

Symptom: Endpoints sending bad video data can cause DSP failures on the receiving endpoints, causing the receiving endpoints to drop from the conference.

Condition: Multipoint conferences where one endpoint is sending faulty video data, causing DSP failures on the receiving endpoints.

Workaround: None.

Fixed: CTMS Release 1.5.2

CSCta07212

Symptom: Legacy endpoint off CUVC can't hear one specific Cisco TelePresence participant, but can see video.

Condition: Scheduled interop multipoint call with legacy end points involved.

Workaround: Use static interop call.

Fixed: CTMS Release 1.5.0

CSCta74500

Symptom: Calls drop because of DTLS timeout and security mismatch.

Fixed: CTMS Release 1.6.0.

Supplemental End User License Agreement

This Supplemental End User License Agreement ("SEULA") contains additional terms and conditions for the Software product that is used with Cisco's TelePresence product, including features, functionality and solutions enabled in such Software (collectively, "Software Product") licensed under the End User License Agreement ("EULA") between you and Cisco (collectively, the "Agreement"). Capitalized terms used in this SEULA but not defined will have the meanings assigned to them in the EULA. To the extent that there is a conflict between the terms and conditions of the EULA and this SEULA, the terms and conditions of this SEULA will take precedence.

In addition to the limitations set forth in the EULA on your access and use of the Software Product, you agree to comply at all times with the terms and conditions provided in this SEULA. DOWNLOADING, INSTALLING, OR USING THE SOFTWARE PRODUCT CONSTITUTES ACCEPTANCE OF THE AGREEMENT, AND YOU ARE BINDING YOURSELF AND THE BUSINESS ENTITY THAT YOU REPRESENT (COLLECTIVELY, "CUSTOMER") TO THE AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THE AGREEMENT, THEN CISCO IS UNWILLING TO LICENSE THE SOFTWARE PRODUCT TO YOU AND (A) YOU MAY NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE PRODUCT, AND (B) YOU MAY RETURN THE SOFTWARE PRODUCT (INCLUDING ANY UNOPENED CD PACKAGE AND ANY WRITTEN MATERIALS) FOR A FULL REFUND, OR, IF THE SOFTWARE PRODUCT AND WRITTEN MATERIALS ARE SUPPLIED AS PART OF ANOTHER PRODUCT, YOU MAY RETURN THE ENTIRE PRODUCT FOR A FULL REFUND. YOUR RIGHT TO RETURN AND REFUND EXPIRES 30 DAYS AFTER PURCHASE FROM CISCO OR AN AUTHORIZED CISCO RESELLER, AND APPLIES ONLY IF YOU ARE THE ORIGINAL END USER PURCHASER.

These SEULA terms will apply to the following Software Products:

Product Name Function

CTS-CTMS Cisco TelePresence Multipoint Switch

CUVC Cisco Unified Video Conferencing

CUVC-M Cisco Unified Video Conferencing Manager

For the purpose of this SEULA, we define the following terms:

"Authorized Service Provider" is a service provider that has an agreement with Cisco that explicitly authorizes support for the Restricted Features.

"Intra-company Use" is a use of the Software Product which occurs within the same company/entity and which traverses a service provider network for the purpose of interconnecting and communicating to endpoints within the same companies/entities.

"Inter-company Use" is a use of the Software Product which occurs between two or more companies/entities and which traverses a service provider network for the purpose of interconnecting and communicating to other companies/entities. A use may include functionality that is accessed before, during or after a Cisco TelePresence meeting. Inter-company Use also includes providing features of the Software Product in a commercially available service offering.

"Restricted Features" means one or more of the following features: (i) Inter-company Multipoint encryption; and (ii) Inter-company HD/SD Inter-Operability.

In addition to the Agreement, the following supplemental terms apply:

The Restricted Features are available or potentially enabled in this Software Product but may only be used for Intra-company Use. THE RESTRICTED FEATURES CANNOT BE USED FOR THE PURPOSES OF INTER-COMPANY USE UNLESS SUCH USE IS PERMITTED BY AN AUTHORIZED SERVICE PROVIDER. IF YOU WERE TO USE THE RESTRICTED FEATURES FOR INTER-COMPANY USE, YOUR USE OF THE RESTRICTED FEATURES PRIOR TO SUCH AUTHORIZATION WOULD CONSTITUTE A BREACH OF THE AGREEMENT. Unless your use is through an Authorized Service Provider, you are not authorized to use the Restricted Features for Inter-company Use until the Restricted Features have been noted as a generally available feature set in the updated release notes for the Software Product, as posted by Cisco on cisco.com. Notwithstanding the foregoing, your Intra-company Use of the Restricted Features shall not be restricted by this paragraph.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.