Guest

Cisco TelePresence Multipoint Switch

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.6

  • Viewing Options

  • PDF (441.6 KB)
  • Feedback
Release Notes for Cisco TelePresence Multipoint Switch, Release 1.6

Table Of Contents

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.6

Contents

Introduction

Cisco TelePresence Software Compatibility Matrix

Software Releases and Component Firmware Versions

Important Information for CTMS 1.6.x Releases

Interoperability Issues

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

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

Caveats from CTMS Release 1.1.x

CTMS Release 1.1 Caveat Reference

Caveats from CTMS Release 1.1.2 (6)

Caveats from CTMS Release 1.1.1

Caveats from CTMS Release 1.1.0

Caveats from CTMS Release 1.0.x

Caveats from CTMS Release 1.0.3(15)

Caveats from CTMS Release 1.0.3(8)

Caveats from CTMS Release 1.0.2

Caveats from CTMS Release 1.0

Supplemental End User License Agreement

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TelePresence Multipoint Switch, Release 1.6


Revised: April 4, 2011
OL-21541-05

Contents

Introduction

Cisco TelePresence Software Compatibility Matrix

Software Releases and Component Firmware Versions

Important Information for CTMS 1.6.x Releases

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

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

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

Caveats from CTMS Release 1.1.x

CTMS Release 1.1 Caveat Reference

Caveats from CTMS Release 1.1.2 (6)

Caveats from CTMS Release 1.1.1

Caveats from CTMS Release 1.1.0

Caveats from CTMS Release 1.0.x

Caveats from CTMS Release 1.0.3(15)

Caveats from CTMS Release 1.0.3(8)

Caveats from CTMS Release 1.0.2

Caveats from CTMS Release 1.0

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_6/release/Notes/cts_1_6_release_notes.html#wp42142

Important Information for CTMS 1.6.x Releases

Interoperability Issues

When endpoints that use a Cisco/Tandberg VCS system as a proxy dial in to a CUVC running version 7.0 or 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.

The Movi client is not supported on CUVC.

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.

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

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

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 3 summarizes caveats found in CTMS Release 1.6.x.

Table 1 CTMS Release Caveats and Caveats Corrected Reference 

 

Software Release

 

1.6.0

CDETS Number

Found in Release

Corrected in Release

CSCsw50200

1.6.0

None

CSCta38768

1.6.0

None

CSCta57505

1.6.0

None

CSCtc20725

1.6.0

None

CSCtc23584

1.6.0

None

CSCtc43708

1.6.0

None

CSCtc57680

1.6.0

None

CSCtc57727

1.6.0

None

CSCtc66419

1.6.0

None

CSCtc68768

1.6.0

None

CSCtc70726

1.6.0

None

CSCtc71031

1.6.0

None

CSCtc85023

1.6.0

None

CSCtc88319

1.6.0

None

CSCtd11725

1.6.0

None

CSCtd29406

1.6.0

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.

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.

CSCta57505

Symptom: The administrator might observe an exception from Java from the WebUI log.

Condition: During upgrade of CTMS, the administrator might see an exception if some process is not active before the Web UI process comes up after upgrade.

Workaround: None.

CSCtc20725

Symptom: On resume of a receiving endpoint, the presentation is sent before notifying the endpoint to start receiving the presentation. The result is a system error message.

Condition: During a meeting with a presentation, when an endpoint on hold resumes, the presentation is sent from the source before the endpoint is notified to start receiving presentation. This results in a CTMS_ALARM_MEDIA_RXOFF_STREAMSENT system error WARN message.

Workaround: This message does not impact the presentation or the meeting.

CSCtc23584

Symptom: Endpoint drop with error code = NO_RESUME during overnight testing

Condition: When a meeting is active for over six hours with active switching, holding and resuming, and adding and dropping participants, an endpoint can drop with error code = NO_RESUME when Unified CM does not respond to a resume request.

Workaround: The Endpoint can dial back in to meeting, or CTMS can redial the endpoint.

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.

CSCtc57680

Symptom: Uploading an invalid certificate on the Security Settings page gives 'null' and 'Go Back' page

Conditions: On Security Setting, click Upload, input an incorrect certificate and click Upload. A 'Null' and 'Go Back' page will be seen.

Workaround: User must Close the page and input a correct certificate file name for Upload.

CSCtc57727

Symptom: An endpoint drops from a meeting. Then a "not responding" system error message appears.

Condition: This symptom is seen during network congestion on this endpoint in the meeting. The endpoint has already left the meeting, but this system error message information is produced because of synchronization issue between two threads.

Workaround: None.

CSCtc66419

Symptom: CTS 1.4.7 will drop from a meeting after multiple other CTS go on Hold and then one of them resumes.

Condition: During a meeting, if more than one of other CTS endpoints go on hold, upon resume of one of them, a CTS 1.4.7 was dropped from that meeting.

Workaround: This is not reproducible with CTS 1.5 or greater. Only the older mux version has been seen to drop.

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.

CSCtc70726

Symptom: "Feedback not received" system error displays for meetings with presentation from the same source on for approximately 100 minutes.

Condition: During a meeting that has a 5 FPS presentation on from the same source for a long time (more than 100 minutes), the following warning message eventually is displayed: CTMS_ALARM_MEDIA_FB_NOT_RECVD

Workaround: Switch the presentation source, or unplug and plug in again the presentation from that source.

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.

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, update 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 2 provides the current recommended set of software releases and component firmware versions for the Cisco TelePresence solution.

Table 2 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 3 summarizes caveats found in CTMS Release 1.5.x.

Table 3 CTMS Release 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

None

CSCta33668

1.5.3

1.6.0

CSCta38768

1.5.3

None

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

CSCsz17951

1.5.2

Unreproducible

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

CSCsw77667

1.5.0

None

CSCsw46206

1.5.0

1.5.2

CSCsw46355

1.5.0

None

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

CSCsz17951

Symptom: A call may drop during a security downgrade.

Condition: In a best-effort static conference, if a non-secure endpoint joins the call, the security downgrade for the secure endpoint causes the secure endpoint to drop from the conference call.

Workaround: None.

Further Problem Description: This is observed during a stress test for a best-effort conference call. It happens after 24 hours of stress testing.

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

CSCsw77667

Symptom: While uploading a Unified CM root certificate, you get a screen with a Error Message saying "null."

Condition: In the CTMS WebUI (Security Settings), while uploading a Unified CM root certificate (.PEM file), you get a screen with a Error Message saying "null."

Workaround: Do not upload .PEM files; upload only .DER files.

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

CSCsw46355

Symptom: A Scheduler role doesn't have access to Security Settings page.

Condition: On the CTMS WebUI, any credential with a Scheduler Role will not have access to Security Settings page.

Workaround: While it is true that the Scheduler role can't see the current CTMS security settings and the current installed security certificates, for security reasons, the Security Settings page should be visible only to Administrator Role. The Scheduler can still create meetings of Secured, Non-Secured or Best-Effort configurations.

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.

Caveats from CTMS Release 1.1.x

Caveats were recorded in the following CTMS Release 1.1 interim releases:

CTMS Release 1.1 Caveat Reference

Caveats from CTMS Release 1.1.2 (6)

Caveats from CTMS Release 1.1.1

Caveats from CTMS Release 1.1.0

CTMS Release 1.1 Caveat Reference

Table 3 summarizes caveats found in CTMS Release 1.1.x.

Table 4 CTMS Release Caveats and Caveats Corrected Reference 

 

Introduced in Software Release

1.1.2(6)


DDTS Number

Corrected in Release

Caveat

CSCsu22084

1.1.2(6)

Need to increase default bad source detection threshold.

CSCsu66562

1.1.2(6)

Support early UPDATE.

 

Introduced in Software Release

1.1.1(17)


DDTS Number

Corrected in Release

Caveat

None

   
 

Introduced in Software Release

1.1.1(7)


DDTS Number

Corrected in Release

Caveat

None

   
DDTS Number
Introduced in Software Release
1.1.1
Corrected in Release
Caveat

CSCsq37498

1.1.2

Blank presentation on CTS 500 on rare timing corner case under stress situation.

CSCsr07887

1.1.2

Time zone selected in "Preference" doesn't take effect.

CSCsr25631

1.5.0

Default Settings do not persist after upgrade.

CSCsr56370

1.5.0

Active conference without endpoints is not deleted from Conference Manager.

CSCsy55513

1.5.2

The legacy video isn't being shown in spite of the endpoint sending Refresh Requests and NAKs.

DDTS Number
Introduced in Software Release
1.1.0
Corrected in Release
Caveat

CSCsl69290

1.1.1 (6)

Need more specific error generated with SNMP Trap username/password.

CSCsm65258

1.1.2

Unable to launch schedules CTMS meeting after upgrading from CTMS Release 1.0 to CTMS Release 1.1

CSCsm93296

1.5.0

Web User Interface need to maintain system error and warnings.

CSCso98637

1.5.0

New QoS Settings are not saved after system restart.

CSCso61170

1.5.0

Administrator account is overwritten when saved configuration files are imported.

CSCso16467

1.1.1(17)

CTMS allows time zone preference to be set to "Select Timezone."

CSCso53449

1.1.1(17)

Changing "quality" and "downspeed" fields generate error page displayed.

CSCso61729

1.5.0

If you are re-installing CTMS using DVD media and importing CTMS configuration files from previous installation, CTMS users are not migrated.

CSCso70405

1.1.1

Scheduled conference video announce is not working.

CSCso73123

Not reproducible

Adding DNS erases Unified CM settings.

CSCso76744

1.5.0

Under default settings, "Idle Meeting Termination Time" sets to 10 during an upgrade. It should not reset. The value that was configured before the upgrade should be retained.

CSCso77232

No

On a triple-screen system, legacy endpoints will be seen in the center, as well as a CTS, even though the legacy should be seen on the left.

CSCso87663

1.1.1(7)

Admin CLI "set lateendmins" can accept any positive number as the value.

CSCso95895

1.1.1(17)

Script error after clicking Site/Segment radio button.

CSCsq06085

1.1.1(17)

Scheduled conference cannot launch from phone.


Caveats from CTMS Release 1.1.2 (6)

CSCsu22084

Condition: Need to increase default bad source detection threshold.

Summary: Default Bad Source Detection threshold increased from 0.15% to 0.2% over 40 seconds

Fixed: CTMS Release 1.1.2 (6)

CSCsu66562

Condition: Support early UPDATE

Summary: Cisco Unified Communication Manager (Unified CM) 6.1.2 sends early UPDATE after sending the "to-tag." When CTMS responds to UPDATE, it does not send the "from-tag."

Fixed: CTMS Release 1.1.2 (6)

Caveats from CTMS Release 1.1.1

CSCsq37498

Condition: Blank presentation on CTS 500 on rare timing corner case under stress situation.

Summary: When using a CTS 500, if the user presses the Resume key in a multipoint meeting with a remote presenter, the remote presentation fails to reappear.

Workaround: The presentation will reappear under the following circumstances:

When another endpoint dials into the meeting.

When you press Hold/Resume on a third CTS endpoint.

When you remove and then add the presentation back on the current source.

Fixed: CTMS Release 1.1.2

CSCsr07887

Condition: Time zone selected in "Preference" doesn't take effect

Summary: On the web user interface, users have an option to list scheduled conferences based on a selected time zone in Preferences tab. The times show up as the time zone selected but in the column header, you still see GMT offset.

Workaround: Ignore the column header; it is a cosmetic issue.

Fixed: CTMS Release 1.1.2

CSCsr25631

Condition: Default Settings do not persist after upgrade.

Summary: Default Settings do not persist after software upgrade. The following settings change:

Switching policy will change to Speaker if originally Room

Quality: If Q2, it changed to Q0; if Q5, it persists

Allow downspeed will change to Yes if originally set to No

Idle Meeting Termination will change to Yes, if originally set to No

Idle Meeting Termination Time will change to 10 if originally set to 5

Values that persist:

Max rooms

Video Announce

Workaround: Manually change Default Settings back to desired values after upgrade.

Fixed: CTMS Release 1.5

CSCsr56370

Condition: Active conference without endpoints is not deleted from Conference Manager

Summary: This occurs when Administrator dials a number that is a configured static meeting number to any active meeting and then cancels the dial out and removes all other endpoints from the meeting.

Workaround: Do not dial out to any number that is a configured as a static meeting number.

Fixed: CTMS Release 1.5

CSCsy55513

Symptom: The legacy video isn't being shown in spite of the endpoint sending Refresh Requests and NAKs.

Condition: Hold-Resume on the CTS is not receiving video signal.

Workaround: None.

Fixed: CTMS Release 1.5.2

Caveats from CTMS Release 1.1.0

CSCsl69290

Condition: Need more specific error generated with SNMP Trap username/password.

Summary: When inputting an invalid SNMP trap receiver username, an incorrect error (invalid password length) is given instead of "invalid username error."

Fixed: CTMS Release 1.1.1(6)

CSCsm65258

Condition: Unable to launch schedules CTMS meeting after upgrading from CTMS Release 1.0 to CTMS Release 1.1

Summary: Unable to launch scheduled multipoint meeting due to missing access number after an upgrade.

Workaround: Reapply the access number.

Fixed: CTMS Release 1.1.2

CSCsm93296

Condition: Web User Interface need to maintain system error and warnings

Summary: System Errors are of different "type." If users click on the Warning Messages link from the Status pane and delete some of the messages, they are presented a full list of system errors that includes both warning and error messages. This issue does not compromise security or impact the normal operation of CTMS.

Workaround: When you decide to clear alarms, always go from the System Errors link rather than the link from Status pane.

Fixed: CTMS Release 1.5

CSCso98637

Condition: New QoS Settings are not saved after system restart

Summary: If QoS configuration settings are changed and the system is restarted, the QoS settings are not saved. This happens after users change DSCP for CUVC Media to (0000000) and restart the system.

Workaround: Set or leave the default value for DSCP for CUVC Media: AF41 DSCP (100010).

Fixed: CTMS Release 1.5

CSCso61170

Condition: Administrator account is overwritten when saved configuration files are imported.

Summary: Administrator account overwritten during import can be deleted and leaves no access to GUI.

Fixed: CTMS Release 1.5

CSCso16467

Condition: CTMS allows time zone preference to be set to "Select Timezone."

Summary: Because this is a required field, users should not be allowed to set this field to "Select Timezone."

Fixed: CTMS Release 1.1.1(17)

CSCso53449

Condition: Changing "quality" and "downspeed" fields generate error page displayed.

Summary: From the Defaults settings page, if you change the "quality" and "downspeed" fields and then click "Apply," CTMS displays "Please contact diagnostic technician" error page but applies the changes.

Fixed: CTMS Release 1.1.1(17)

CSCso61170

Condition: Administrator account is overwritten when saved configuration files are imported.

Summary: Administrator account overwritten during import can be deleted and leaves no access to GUI.

Fixed: CTMS Release 1.5

CSCso61729

Condition: If you are re-installing CTMS using DVD media and importing CTMS configuration files from previous installation, CTMS users are not migrated.

Summary: After a fresh installation of the administration software, a previously exported configuration file was imported. The administrator logged out, and then logged in using the new password, and then logged into the command line interface (CLI). Only the password created during the fresh installation worked; the password for GUI and the CLI were out of sync.

Fixed: CTMS Release 1.5

CSCso70405

Condition: Scheduled conference video announce is not working.

Summary: If video announce is enabled from CTMS, then scheduled conference will not have video announce.

Fixed: CTMS Release 1.1.1

CSCso73123

Condition: Adding DNS erases Unified CM settings.

Summary: After adding DNS and rebooting CTMS, unable to launch Ad Hoc meeting. Unified CM settings were erased. This is a very rare case.

Workaround: Manually reconfigure Unified CM settings.

Status: Unreproducable

CSCso76744

Condition: Under default settings, "Idle Meeting Termination Time" sets to 10 during an upgrade. It should not reset. The value that was configured before the upgrade should be retained.

Summary: Upgrade from any version of 1.0 to any other version.

Workaround: Reconfigure the "Idle termination time" after upgrading.

Fixed: CTMS Release 1.5

CSCso77232

Condition: On a triple-screen system, legacy endpoints will be seen in the center, as well as a CTS, even though the legacy should be seen on the left.

Summary: Highly unlikely in a non-scripted scenario, the issue is a result of a race condition where a CTS endpoint joins faster than the CUVC can be automatically added.

Workaround: The issue will be fixed when the next CTS joins.

CSCso87663

Condition: Admin CLI "set lateendmins" can accept any positive number as the value.

Summary: For the Admin CLI command, "set lateendmins..." you can input any value.

Fixed: CTMS Release 1.1.1(7)

CSCso95895

Condition: Script error after clicking Site/Segment radio button.

Summary: Open any scheduled meeting and click on the Site/Segment (Room/Speaker) radio button. Script error window will pop up. However, the error doesn't seem to have any adverse affect.

Fixed: CTMS Release 1.1.1(17)

CSCsq06085

Condition: Scheduled conference cannot launch from phone.

Summary: Scheduled conference "early start minutes" is set to a value greater than the default value (10) or other value set since last CTMS restart. User tries to join the meeting ahead of scheduled start time for a time that is between the new early start minutes and the old early start minutes.

Fixed: CTMS Release 1.1.1(17)

Caveats from CTMS Release 1.0.x

Caveats were recorded in the following CTMS Release 1.0 interim releases:

Caveats from CTMS Release 1.0.3(15)

Caveats from CTMS Release 1.0.3(8)

Caveats from CTMS Release 1.0.2

Caveats from CTMS Release 1.0

Caveats from CTMS Release 1.0.3(15)

CSCsh68518

Condition: Cisco Unified Communications Manager SIP trunk offline does not trigger CTMS alarm.

Summary: CTMS needs to trigger an alarm when somebody creates an Immediate AdHoc meeting and the Cisco Unified Communications Managers STP trunk is offline.

Fixed: CTMS Release 1.1.0(205)

CSCsi46414

Condition: Cannot delete template.

Summary: Cannot delete a template from the Ad Hoc Meeting/Template tab. The page refreshes but the template is not deleted.

Fixed; CTMS Release 1.0.3(11)

CSCsj40959

Condition: Duplicate word in system error message.

Summary: System error message included a duplicate word (because because).

Fixed: CTMS Release 1.0.3(7)

CSCsj51843:

Condition: CTMS log files shows password.

Summary: CTMS logs show password in clear text.

Fixed: CTMS Release 1.0.3

CSCsk95166

Condition: Template disappears after it has been edited.

Summary: For example, if you add a new extension number to an existing meeting template, then shut down the server or upgrade the software to a later releases, the edited template no longer appears in the web UI but it still remains in the web_configure file.

Fixed: CTMS Release 1.1.0(149)

CSCsj90340

Condition: CTMS doesn't show scheduled meeting.

Summary: CTMS doesn't show scheduled meeting due to double quote in meeting subject line.

Fixed: CTMS Release 1.0.3(4)

CSCsj90347

Condition: Media Processor needs to provide a CLI to flush statistics to log file.

Summary: Backend processes need invoke media processor CLI (FlushLogStatistics) to flush statistics into rtp.log so that it can captures latest media statistics information in log file.

Fixed: CTMS Release 1.1.0(205)

CSCsj92542

Condition: Unable to use zero octet IP in Cisco Unified Communications Manager (CUCM) configuration.

Summary: Zero octet is legal IP address on the network; however, it gets invalid IP error when used to configure the CUCM IP address in CTMS.

Fixed: CTMS Release 1.1.0(31)

CSCsj94543

Condition: MediaProperties performance optimization.

Summary: The class need to be optimized to cache those values used by RTP processing window to reduce hash map lookup and improve media performance

Fixed: CTMS Release 1.0.3

CSCsj96270

Condition: Flush media statistics to log file when user click download log from web GUI.

Summary: Media process periodically logs statistics into log file. In order to capture latest media statistics, media should provide CLI to flush media statistics into log file, when user clicks download log from web GUI. This functionality should help trace customer issue.

Fixed: CTMS Release 1.0.3

CSCsk05875

Condition: Upgrading with sFTP and no DNS creates unusable multipoint switch.

Summary: Upgrading with sFTP and no DNS creates unusable multipoint switch.

Fixed: CTMS Release 1.0.3(5)

CSCsk05968

Condition: Static meeting subject does not display.

Summary: Static meeting subject does not display when special characters are entered in the meeting description

Fixed: CTMS Release 1.0.3(4)

CSCsk06046

Condition: The system should not allow the same endpoint to dial same number twice.

Summary: During an AdHoc meeting, the endpoint should not be allowed to dial the same meeting number more than once.

Fixed: CTMS Release 1.0.3(7)

CSCsk10737

Condition: Cannot delete static meetings.

Summary: Intermittently, user cannot delete static meetings.

Fixed: CTMS Release 1.0.3(4)

CSCsk29972

Condition: CTMS is unable to register with Cisco TelePresence Manager.

Summary: When CTMS is located where the latency is greater than 200 ms, it is not able to register with Cisco TelePresence Manager if the timeout is set for 100 ms.

Fixed: CTMS Release 1.1.0(31)

CSCsk52342

Condition: Statistics did not refresh.

Summary: All the statistics (PrintJitter) for audio and video did not get refreshed. The statistics are shown as 0 for audio field and some for the video file.

Fixed: CTMS Release 1.0.3(10)

CSCsk57054

Condition: Media layer not forwarding SRs to endpoints.

Summary: CTS logs indicated that SRs weren't being forwarded to the CTS endpoints.

Fixed: CTMS Release 1.0.3(10)

CSCsk60800

Condition: Display more detailed error information when Scheduled Meetings cannot launch.

Summary: Conference Manager needs to send a more detailed error and log information when Scheduled Meetings cannot be launched due to resource allocation.

Fixed: CTMS Release 1.0.3(7)

CSCsk68251

Condition: CTMS needs to wait longer for MUX negotiation with CTS Release 1.2 endpoints.

Summary: CTMS needs to wait longer for MUX negotiation with CTS Release 1.2 endpoints.

Fixed: CTMS Release 1.0.3

CSCsk81167

Condition: Cisco TelePresence Manager detected a process (switching signal=11) dead.

Summary: Cisco TelePresence Manager detected a process (switching signal=11) dead.

Fixed: CTMS Release 1.0.3(15)

CSCsk87203

Condition: CTMS high CPU causes call drop.

Summary: Call dropped by CTMS because of high CPU spike.

Fixed: CTMS Release 1.0.3(12)

CSCsk91728

Condition: Installation error.

Summary: During installation, the following message was displayed: "The installation has encountered a serious internal error. The system will be halted."

Fixed: CTMS Release 1.0.3(15)

CSCso71518

Condition: Presentation switching in a multipoint call does not mirror that of a point-to-point call, specifically during calls where endpoints with presentations plugged in go on hold.

Summary: If an endpoint with a presentation plugged in but who is not the active presenter goes on hold and resumes, they will become the active presenter.

Fixed: CTMS Release 1.0.3

Caveats from CTMS Release 1.0.3(8)

CSCsi16039

Condition: Log Files: Change the name of the "Download All" button.

Summary: In Log Files window, after using the filter button, the only choice that the user has is he button labeled "Download All." "Download All" implies that all of the log files will be downloaded, not the files that are the result of the filtering. The recommendation is to change "Download All" to "Download File(s) Listed."

Status: Closed

CSCsi24160

Condition: Clicking "Filter" applies changes to Log Levels.

Summary: From the Log Files window, if you select "New Log Level" for one process and then click "Filter,' the result is that the Log Level is automatically applied and the Apply and Reset buttons are grayed out. The Log Level should not be applied until the user clicks "Apply."

Fixed: CTMS Release 1.1.0(136)

CSCsi45541

Condition: Inconsistent use of rooms vs. segment in CTMS Administration software.

Summary: In System Configuration, under System Settings, on the Resource Management window, parameters refer to "segments." In Meeting Management, on the Default Settings page, parameters refer to "rooms," "sites," and "segments." The recommendation is to standardize on "segments."

Status: Closed

CSCsi49322

Condition: Active Meeting Status window should move to the front of CTMS WebUI.

Summary: If you create an AdHoc meeting with maximum rooms, and then add another room, the Active Meeting Status window is displayed, showing the error. If you click on the CTMS WebUI screen without closing the Active Meeting Status window, the Active Meeting Status window moves to the background. If you try to add another room, the Active Meeting Status window updates but stays in the background.

Status: Unreproducable

CSCsi51051

Condition: Pages take a long time to refresh.

Summary: The WebUI is now taking a very long time—1 to 2 minutes—to refresh. Only the web status bar at the bottom of the screen shows that the page is refreshing.

Status: Closed

CSCsi51283

Condition: Logs and System Error displays incorrectly when choosing "Rows per Page."

Summary: System Errors and Log files list 10 errors or files per page. If you have more than 10 errors or files, when you click "Last," those beyond the initial 10 errors or files are displayed on another (last) page. If you click "Rows per Page" and choose anything greater than 10, the system does not increase the number of line items displayed. The last view remains. No scroll bar is available to see previous entries.

Status: Unreproducable

CSCsi84648

Condition: Reset button does not reset Log Levels, but acts as Apply button.

Summary: From Log Files, if you change the Log Level for CCS process to DEBUG (the default is INFO) and then click Reset, the field is not reset but applied and the Apply button is grayed out.

Fixed: CTMS Release 1.1.0(136)

CSCsi95884

Condition: If the SFTP port number is changed during CTMS software upgrade, the wizard does not retain the changes.

Summary: If the SFTP port number is changed during CTMS software upgrade, the wizard does not retain the changes.

Fixed: CTMS Release 1.1.0(192)

CSCsj02267

Condition: CTMS host name change not allowed.

Summary: Users cannot change host name from CLI. Web UI has no option to change hostname.

Status: Closed

CSCsj05237

Condition: No status shown if the user relaunches the web page during software upgrade.

Summary: If a user closes the web pages after initiating the upgrade process (the auto switch version), and later re-launches the same upgrade page to check the progress, there is no status given; instead, it shows "Preparing upgrade patch," which was already done.

Status: Postponed

CSCsj15373

Condition: GUI "hangs" after being idle.

Summary: After idle time, GUI hangs; user cannot access anything or log out. When this happens, user must close web browser, open a new browser, and log in again.

Status: Closed

CSCsj24360

Condition: Log files shown on the GUI does not match downloaded number of log files.

Summary: From Log Files, if you select "Download All" and the click "Okay," and then open the zipped file for the log files, the number of log files listed on the GUI does not match the number of files in the zipped file.

Status: Closed

CSCsj29837

Condition: CTMS scheduled meeting information should include switch and quality policies.

Summary: Because the switch policy can be configured and modified on Cisco TelePresence Manager for scheduled meeting, the CTMS display for scheduled meetings should have the switch policy information and quality of conference used information on the detail page.

Fixed: CTMS Release 1.1.0(171)

CSCsj31510

Condition: Schedulable segments value blank out when Reset button is clicked.

Summary: In System Configuration, under System Settings, on the Resource Management window, when user changes the AdHoc segment value and clicks the Reset button, Schedulable segments value blanks out and the Apply and Reset buttons are grayed out.

Fixed: CTMS Release 1.1.0(136)

CSCsj35537

Condition: Cannot open files directly listed in Log Files when "All" is selected.

Summary: From Log Files, if you click "License,properties," the system opens a new web browser without any contents. There is no option to Open, Save or Cancel.

Fixed: CTMS Release 1.1.0(136)

CSCsj44260

Condition: Software upgrade/downgrade wording needs to be changed.

Summary: Customers can select to upgrade or downgrade versions of CTMS software. When users are switching to a lower version of the software, the message should say "downgrade" instead of "upgrade."

Fixed: CTMS Release 1.1.0(157)

CSCsj48010

Condition: Very long description in template shows up as "Null."

Summary: From AdHoc Meeting, if you select Templates and then add a long meeting description, when you launch an Ad Hoc meeting using that template, the Meeting Description shows up as "null."

Fixed: CTMS Release 1.0.3(15)

CSCsj87499

Condition: Dual image on CTS 1000.

Summary: When CTMS media received an IDR, it will have its destination cache invalidated. CTMS has a problem in RTP processing logic. It may result in IDR packet from new segment (active speaker) dropped, and send streams from another segment wrongly to the destination.

Fixed: CTMS Release 1.0.3

CSCsj90876

Condition: Media destination cache optimization to reduce RTP processing window.

Summary: One of the major overheads in media process is the time spent on EPO lookup for each packet in user space. There was transmission destination cache implemented. The cache is invalidated for each RTP processing window.

The enhancement is to cache transmission destination for all segments for all endpoints including both video and audio. The performance of media is expected to be significantly improved further.

Fixed: CTMS Release 1.1.0(218)

CSCsj92140

Condition: Incorrect audio packet handling causes switch to sometimes be unresponsive.

Summary: Under rare condition, when MediaProcessor may buffer more than one audio packet in a UDP channel, only the first packet has its confidence level updated into rank table. All other packets buffered do not get the chance to update their confidence level into rank table. This error can cause switching to be unresponsive when two segments from same endpoint compete.

Fixed: CTMS Release 1.0.3

CSCsj92146

Condition: Media statistics enhancement.

Summary: Media need enhance statistics for troubleshooting. The following statistics need to be added.

Mean jitter standard deviation

Mean video frame duration standard deviation

Max ssrc switch count per 4 seconds

Calculate video jitter based on mux version with either first packet of a video frame or last packet of video frame.

Total packets received and transmitted

Fixed: CTMS Release 1.0.3

CSCsj92637

Condition: Unable to add or modify DNS entries via CTMS web page.

Summary: The CTMS web page does not allow users to add or modify the DNS entries. Only IP, Subnet Mask and Default Gateway values can be modified.

Status: Duplicate

CSCsj92688

Condition: Inconsistent switch and IDR packet lost.

Summary: When a top active speaker is detected and IDR is received by media, Media use source SSRC derives segment information to calculate index to transmission destination cache. The cache gets updated when the media layer goes through the EPO table to find a list of destinations to transmit a packet. Whenever a destination is found, it gets added to destination cache based on index calculated from rtp packet ssrc. Since media manipulate ssrc in the same packet for each iteration finding destination, the source ssrc used for cache index calculation keeps changing. It may result in the wrong cache index if the ssrc is the same before or after manipulation.

Fixed: CTMS Release 1.0.3

CSCsk43793

Condition: Web should not restart CTMS processes when updating resources.

Summary: When some parameters like resources are updated from web, web should not restart CTMS processes; it should delete all active conferences and then reset the parameters.

Fixed: CTMS Release 1.1.0(136)

Caveats from CTMS Release 1.0.2

CSCsj31519

Condition: Switching policy cannot be configured after upgrade from Cisco TelePresence Manager (CTS-MAN) Release 1.1 to CTS-MAN Release 1.2.

Summary: After completing upgrade from CTS-MAN 1.1 to CTS-MAN 1.2, the MCU field value is "N/A" and the field from which a user can select a new policy is disabled.

Fixed: CTMS Release 1.1.0(94)

CSCsj51298

Condition: Calls cannot be cancelled if the dialed-out number is preceded with "0."

Summary: In releases prior to CTMS Release 1.0.2(250), dialed-out numbers preceded by "0" trigger a JavaScript validation error that forces the calls to fail. In CTMS Release 1.0.2(250), users cannot cancel a call before the call is answered if the dial-out number is preceded by "0."

Fixed: CTMS Release 1.0.3(4)

CSCsj35537

Condition: Cannot open Log files directly when "All" is selected.

Summary: When you click "Log Files" in CTMS Administration Software, and then select "Licence Properties," a new web browser window opens with no content.

Fixed: CTMS Release 1.1.0(136)

CSCsj38998

Condition: Log files contain extraneous files.

Summary: Log files contain extra files that are not useful for debugging.

Fixed: CTMS Release 1.1.0(136)

CSCso62784

Condition: The web pages still mention "site/segment" instead of "room/speaker."

Summary: In all customer facing GUIs, "site" has been changed to "room" and "segment" to "speaker."

Fixed: CTMS Release 1.1.1(7)

CSCso79483 (1.0.2(245)

Condition: Admin WebUI shows ALARM_DUPLICATE_CALL alarm.

Summary: This alarm will appear for scheduled Interop meetings. If at least one room joins and then leaves the meeting before the scheduled start time (within the CUVC dial repeat interval from the scheduled start time), and at the scheduled start time the meeting is active again, this alarm will show and the CUVC will be disconnected from the meeting.

Fixed: CTMS Release 1.1.1(21)

Caveats from CTMS Release 1.0

CSCsh81490

Condition: If you enter data and then move to another tab without selecting "Apply," no warning message is displayed.

Summary: In System Settings, if you enter data in Access Management and then select another tab (QoS tab, for example), no warning message is displayed, telling you that the data you entered will be lost.

Fixed: CTMS Release 1.0(218)

CSCsi26863

Condition: A call exceeding maximum streams should return a "fast busy."

Summary: A call exceeding maximum streams should return a "fast busy." Currently, the caller is dropped without any indication. Maximum streams is configured in the CTMS Administration software. If it is set to 20, a caller attempting to allocated the 21st stream should be sent a busy signal.

Fixed: CTMS Release 1.1.0(205)

CSCsi44352

Condition: Time zone is not configurable during installation.

Summary: CTMS server is defaulting GMT and not offering an option to select the right time zone during installation or through CLI post install.

Fixed: CTMS Release 1.1.0(192)

CSCsi45541

Condition: In the CTMS Administration software, there is an inconsistent use of terms: rooms versus segment.

Summary: In CTMS Administration software, parameters under System Settings and Resource Management use the term "segments." Default Settings under Meeting Management uses the term "rooms." Default settings also includes site/segment switching parameter. Recommendation: use "segments" consistently throughout.

Status: Closed

CSCsi48875

Condition: CTMS should reject audio calls if it receives an audio only SDP.

Summary: If CTMS receives an audio only SDP, it should reject this call immediately. Today, it proceeds as normal: it opens its media ports and waits for AppMux packet. When the AppMux packet doesn't come, it does a media timeout and raises a warning alarm.

Fixed: CTMS Release 1.0(221)

CSCsi48916

Condition: Cannot delete user.

Summary: After a user is created, it cannot be deleted.

Fixed: CTMS Release 1.0.3(7)

CSCsi52075

Condition: The Ad hoc Meeting Status page displays inconsistent state.

Summary: After creating an ad hoc conference with three attendees, the conference was cancelled from the Ad Hoc meeting status page. The status displays that the meeting was terminated by end user, then calling state, then media timeout occurred.

Status: Duplicate

CSCsi53840

Condition: When a CTS-1000 exits a conference, another CTS-1000 active speaker may be displayed briefly.

Summary: There is a corner case where if a specific CTS-1000 is the active speaker and a different CTS-1000 leaves the conference, the first CTS-1000 can show up on 2 displays for a few seconds.

Fixed: CTMS Release 1.0.2(250)

CSCsi54335

Condition: The Static Conference dialed number changed after hold/resume.

Summary: The phone user interface displayed a different dialed number after a static conference call was put on hold and then resumed.

Fixed: CTMS Release 1.0.3(7)

CSCsi55871

Condition: Media Processor log level change above INFO causes jitter.

Summary: The Media Processor log level default value is INFO; this is different from all other processes. If it is changed above INFO that Jitter could/will result.

Fixed: CTMS Release 1.0(236)

CSCsi58667

Condition: Two video picture overlaps—one actual and one transparent.

Summary: Occasionally during conferences, two video pictures overlap: one of the active speaker, and a transparent image of another speaker. This artifact clears up when someone else switches in the segment.

Fixed: CTMS Release 1.0.2(250)

CSCsi69494

Condition: After Hold/Resume with hosted meeting, participants can join.

Summary: If the host does not join the conference, pressing hold/resume on the two other CTS-1000 devices causes them to join the hosted meeting.

Fixed: CTMS Release 1.0(237)

CSCsi67495

Condition: When first conference participant is put on hold, video does not resume when second participant joins conference.

Description: When the first participant joins a meeting, they are put on hold by the CTMS over a SIP trunk. This creates an icon on the screen (hourglass) that alerts the user that they are the first participant. When a second participant joins, they are resumed. On the resume, the call information is being sent by Cisco Unified Communications Manager with a video port set to zero. This causes no video is sent to the endpoint. To recover, they must drop from the meeting and re-enter.

Status: Duplicate

CSCsi70080

Condition: Timeout only displays voice mail dialed number instead of going to voice mail.

Summary: After starting an ad hoc meeting, created a second ad hoc meeting with the same dialed number; only displays voice mail dialed number instead of going to voice mail.

Fixed: CTMS Release 1.1.0(149)

CSCsi71121

Condition: No indication given when switching versions.

Summary: When switching versions, the web page refreshed back to the platform login page. It should give the status of shutting down until the link is out.

Fixed: CTMS Release 1.0.1

CSCsi71444

Condition: No hourglass icon on second try to join hosted meeting.

Summary: On first call into a hosted meeting from non hosted endpoints, an hourglass icon is displayed. On second call into the hosted meeting, no icon is displayed.

Fixed: CTMS Release 1.1.1

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.