Guest

Cisco TelePresence Multipoint Switch

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.8

  • Viewing Options

  • PDF (549.8 KB)
  • Feedback

Table Of Contents

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.8

Contents

Introduction

Supported Servers For CTMS Release 1.8

CTMS 1.8 Requirements for Server Configuration, CPU, Memory, and Storage

Specification-based Hardware Support

Cisco TelePresence Software Compatibility Matrix

CTMS Open-Source Software Licenses

Software Releases and Component Firmware Versions

CTMS Software Upgrade Path

New and Changed Information for CTMS Release 1.8.7

Fixed Caveats

New and Changed Information for CTMS Release 1.8.6

Fixed Caveats

New and Changed Information for CTMS Release 1.8.5

Fixed Caveats

Caveats for CTMS Release 1.8.5

New and Changed Information for CTMS Release 1.8.4

Fixed Caveats

New and Changed Information for CTMS Release 1.8.3

Fixed Caveats

Caveats for CTMS Release 1.8.3

New and Changed Information for CTMS Release 1.8.2

Fixed Caveats

Caveats for CTMS Release 1.8.2

CTMS Release 1.8.2 Caveat Reference

Caveats for CTMS Release 1.8.2

New and Changed Information for CTMS Release 1.8.1

Alert Management

Email Server

New Process for Printing SDP Keys

Other Notes

Fixed Caveats

Caveats for CTMS Release 1.8.1

CTMS Release 1.8.1 Caveat Reference

Caveats for CTMS Release 1.8.1

New and Changed Information for CTMS Release 1.8

Supported Endpoint Types

TelePresence Call-in Number

UCS Server

Network Multipoint

Event Recording

Browser Security

MXE Support Discontinued

Interface Failover

Fixed Caveats

Documentation Errata in Release 1.8

Caveats for CTMS Release 1.8

CTMS Release 1.8 Caveat Reference

Caveats for CTMS Release 1.8

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

Documentation Errata in Release 1.7.2

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

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 Release Versions

Caveats for CTMS Release 1.5.x

CTMS Release 1.5 Caveat Reference

Caveats for CTMS Release 1.5.3

Supplemental End User License Agreement

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TelePresence Multipoint Switch, Release 1.8


Revised: December 2013

Contents

Introduction

Supported Servers For CTMS Release 1.8

CTMS 1.8 Requirements for Server Configuration, CPU, Memory, and Storage

Specification-based Hardware Support

Cisco TelePresence Software Compatibility Matrix

CTMS Open-Source Software Licenses

Software Releases and Component Firmware Versions

CTMS Software Upgrade Path

New and Changed Information for CTMS Release 1.8.7

New and Changed Information for CTMS Release 1.8.6

New and Changed Information for CTMS Release 1.8.5

Caveats for CTMS Release 1.8.5

New and Changed Information for CTMS Release 1.8.4

New and Changed Information for CTMS Release 1.8.3

Caveats for CTMS Release 1.8.3

New and Changed Information for CTMS Release 1.8.2

Caveats for CTMS Release 1.8.2

New and Changed Information for CTMS Release 1.8.1

Caveats for CTMS Release 1.8.1

New and Changed Information for CTMS Release 1.8

Documentation Errata in Release 1.8

Caveats for CTMS Release 1.8

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

Supported Servers For CTMS Release 1.8

Table 1 Server Support for CTMS 

Server
1.8 New Install
1.8 Upgrade

MCS

MCS-7845-I3-CTS1

MCS-7845-I3

MCS-7845-I2

MCS-7845-H2

UCS

UCS C210 M2

UCS C220 M3

NA

NA


CTMS 1.8 Requirements for Server Configuration, CPU, Memory, and Storage


Note CTMS version 1.8 requires a minimum of 4 GB of RAM for non-Commercial Express solutions. Therefore, you must upgrade an MCS-7845-I2 server with 2 GB of RAM to at least 4 GB. To order additional RAM, use the product ID MEM-7845-I3-2GB=.


Table 2 MCS Server Configuration for CTMS (Non-Commercial Express) 

Server
Configuration
CPU
Memory
Storage

MCS-7845-I3

MCS-7845-I3-CTS1 (IPC1)

1 x Intel Xeon 5540 Quad Core (2.53 GHz, last level cache 8 MB)

6 GB (three 2 GB DIMM) PC3-10600 1333 MHz, fully buffered double data rate 3 (DDR-3) RDIMM

4 x 146 GB SAS 2.5 inch hot-swap

MCS-7845-I2

MCS-7845-I2-IPC2

Dual Intel 5140 2.33 GHz 4M L2

4 GB (four 1 GB) PC2-5300R

4 x 146 GB SAS 2.5 inch hot-swap

MCS-7845-I2

MCS-7845-I2-IPC1

Dual Intel 5140 2.33 GHz 4M L2

2 GB (two 1 GB) PC2-5300R

4 x 72 GB SAS 2.5 inch hot-swap



Note CTMS version 1.8 requires a minimum of 8 GB of RAM for Commercial Express solutions. Therefore, you must upgrade an MCS-7835-I3 server with 4 GB of RAM to at least 8 GB. To order additional RAM, use the product ID MEM-7835-I3-2GB=.


Table 3 MCS Server Configuration for CTMS (Commercial Express) 

Server
Configuration
CPU
Memory
Storage

MCS-7835-I3

MCS-7835-I3-CTS1 for Commercial Express before 11/15/2011

1 x Intel 5504 Quad Core 2.00 GHz; last level cache 8 MB

4 GB (two 2 GB DIMM) PC3-10600 1333 MHz, fully buffered double-data-rate 3 (DDR-3) RDIMM

2 x 300 GB SAS

MCS-7835-I3

MCS-7835-I3-CTS1 for Commercial Express after 11/15/2011

1 x Intel 5504 Quad Core 2.00 GHz; last level cache 8 MB

8 GB (four 2 GB DIMM) PC3-10600 1333 MHz, fully buffered double-data-rate 3 (DDR-3) RDIMM

2 x 300 GB SAS


Table 4 UCS Server Configuration for CTMS 

Server
Configuration
CPU
Memory
Storage

UCS C210 M2

UCS-C210M2-VCD2

2x E5640 Quad Core 2.66 GHz

48 GB (12 x 4 GB)

10 x 146 GB SAS

UCS C220 M3

UCS-SP5-C220E

Add:

UCS-HDD300GI2F105
(4 drive RAID 5 Hard drive)

VMW-VS5-STD-1A (VMware vSphere 5 Standard for 1 Processor, 1 Year Support Required)

2x E5-2650 2.00 GHz

64 GB (8 x 8 GB)

 

Specification-based Hardware Support

Beginning with release 1.8, CTMS now supports specification-based hardware using VMware.

For more information on supported hardware, refer to the following links:

http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications#TelePresence_Applications

http://docwiki.cisco.com/wiki/UC_Virtualization_Storage_System_Design_Requirements#TelePresence_Applications

For more information on VMware support, refer to the following links:

http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements#VMware_Feature_Support_for_TelePresence_Applications

http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines#TelePresence_Applications

http://docwiki.cisco.com/w/index.php?title=Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29#TelePresence_Applications

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


Note CTS release 1.6.x software does not support CTMS release 1.8.x. To use CTMS 1.8.x, CTS software must be upgraded to release 1.7.x or a later supported release.


CTMS Open-Source Software Licenses

License agreements for the open-source software used in CTMS are available at the following URL:

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

Software Releases and Component Firmware Versions

For the current recommended set of software releases and component firmware versions for the Cisco TelePresence System solution, see the Release Notes for Cisco TelePresence System Software Release 1.8, which is located at the following URL:

http://www.cisco.com/en/US/docs/telepresence/cts_admin/1_8/release/notes/cts_1_8_release_notes.html

CTMS Software Upgrade Path

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

1.7.x

1.6.x

New and Changed Information for CTMS Release 1.8.7

Fixed Caveats

The following caveats were fixed in CTMS release 1.8.7:

CSCuh69368: Crackling audio due to CTMS not sending media options G722 with CUVC.

CSCty48966: MediaProcessor Core crashes during network multipoint meeting.

CSCtz86895: MediaProcessor goes into deadlock on leaf CTMS.

New and Changed Information for CTMS Release 1.8.6

Fixed Caveats

The following caveats were fixed in CTMS release 1.8.6:

CSCub16619: Calls dropped due to ConfMgr trying to send REINVITE to endpoint while CCS processes REINVITE from endpoint.

CSCud84688: CTMS displays the error "Audio Only Media Received. Call Terminated."

CSCud22647: CTS audio addin not heard by CUVC endpoints.

CSCue73357: Incorrect copyright year information displayed in CTMS.

CSCua02750: Packet capture created from command-line interface (CLI) not included in log set.

New and Changed Information for CTMS Release 1.8.5

Fixed Caveats

The following caveat was fixed in CTMS release 1.8.5:

CSCuc05549: CTMS crashes after receiving a large UDP packet.

Caveats for CTMS Release 1.8.5

CSCtz86895

Symptom: Call fails with ERROR ALARM_CCS_OPEN_PORT_FAILURE error message during a network multipoint meeting.

Condition: During network multipoint meeting where there are more than 20 CTS endpoints.

Workaround: None.

CSCty48966

Symptom: MediaProcessor process crashes during network multipoint meeting.

Condition: During network multipoint meeting where there are more than 20 CTS endpoints.

Workaround: None.

CSCue73357

Symptom: Incorrect copyright information (2006 - 2012) is displayed in CTMS.

Condition: Displayed in the About and Help windows, and Home and Login pages.

Workaround: None.

CSCuh69368

Symptom: Crackling audio on CTS endpoints.

Condition: CTMS not sending media options G.722 with CUVC calls. Scheduled interop meeting.

Workaround: None.

Further Problem Description: When condition exists with a static interop meeting, the issue does not occur.

New and Changed Information for CTMS Release 1.8.4

Fixed Caveats

The following caveats were fixed in CTMS release 1.8.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.

CSCua92152: Participants in a TelePresence call hear reverberation in the audio coming from another participating endpoint.

CSCtt20160: Active speaker video switching from Movi (now called Jabber) taking more than 20 seconds in a multipoint call.

CSCts99571: System capacity is down to 34 ports with Cisco MXE Media Processing Modules.


Note In release 1.8, CTMS only supported recording of both high definition (HD) and low definition (LD) streams from endpoints. For calls using endpoints connecting through MXE, this resulted in reduced call capacity. In release 1.8.4, CTMS now provides global configuration to enable/disable LD recording for meetings with MXE. The configuration value determines whether CTMS offers HD only or both HD+LD quality to MXE in MUX. This new feature is not available in the 1.9.0 release of CTMS, but will be available in the 1.9.1 release. For more information, see the CTMS 1.8 Administration Guide.


New and Changed Information for CTMS Release 1.8.3

Fixed Caveats

The following caveats were fixed in CTMS release 1.8.3:

CSCty47078: Multipoint calls between CTS endpoints and CTMS version 1.8.x can drop within 15 minutes.

CSCtx77647: CTMS intermittent authentication failures.

CSCtx90451: CCP connection failure, SOAP socket read error on TC5 endpoints.

CSCty49750: CTMS switches without a refresh picture.

CSCty64667: After sending a text message, CTMS dialed out to a dialing endpoint.

CSCty80747: With CTMS, CUVC interop number cannot be longer than 10 digits.

CSCty84213: CTMS receive loss counter does not reset.

CSCty99311: CTMS is not dialing out to the right host for dial-out requests.

CSCtz01565: JBoss vulnerability—able to remotely download server class files.

CSCtz32834: Unable to change CUVC dial repeat time value from CTMS.

CSCtz95285: CTMS 1.8 switches standard definition video to CTS 1.9.x when TC5 or TC6 endpoint joins as first participant.

Caveats for CTMS Release 1.8.3

CSCua02750

Symptom: Packet capture created via the command-line interface (CLI) command utils network capture cannot be retrieved via the administrative web UI and is not included in the log set.

Condition: CTMS CLI used to create the packet capture.

Workaround: Use the CLI command file get activelog /platform/cli to upload the file to an SFTP server.

CSCud84688

Symptom: When user dials the wrong number, CTMS displays the error "Audio Only Media Received. Call Terminated."

Condition: CTMS 1.8.3. CTMS connects to the subscriber Unified CM with MOH enabled. User dials unknown number.

Workaround: None.

CSCub16619

Symptom: Calls sometime gets dropped because CTMS (ConfMgr) is trying to send a REINVITE to an endpoint while CTMS (CCS) is still processing a REINVITE from the endpoint. The SIP stack drops the REINVITE from ConfMgr because it is still processing the REINVITE from the endpoint.

Condition: This happens mostly due to REFRESH REINVITE from Unified CM which is normally handled at the SIP stack level, but sometimes these REINVITEs are handed over to the CCS application by the SIP stack.

Workaround: None.

CSCtz86641

Symptom: WebEx UI does not allow admin to apply changes.

Condition: After uploading TPGW certificate, click Upload button. The Apply button is dimmed, so changes cannot be applied.

Workaround: Click Apply without clicking Upload. The changes are saved.

CSCtz86945

Symptom: CTMS Call-in Number endpoints cannot extend the meeting. Only One Button to Push endpoints can extend the meeting.

Condition: A scheduled meeting with WebEx is started. Call-in Number endpoints then join the meeting.

Workaround: None.

CSCtz87144

Symptom: In the Media Control dialog box, after clicking Reset All Rooms to Default, video does not switch in.

Condition: After manipulating a meeting with both triple-screen and single-screen endpoints through the Director Control interface, the administrator clicks the Reset All Rooms to Default button. After reset, the single-screen endpoints do not see active video from the triple.

Workaround: In Media Control dialog box, after clicking Reset All Rooms to Default, click and unclick any transmit or receive icon and click Apply. Normal video switching should resume.

CSCtz87376

Symptom: After video is downgraded for a meeting, endpoints that join the meeting late are not downgraded.

Condition: Video has been downgraded for the whole meeting because one endpoint received downgraded video.

Workaround: None.

CSCtz86593

Symptom: Enabling CTMS browser security does not work after upgrade

Condition: If browser security was installed and then disabled before upgrading, browser security cannot be enabled after upgrade to CTMS 1.8.3.

Workaround: Enable browser security on current CTMS release before upgrading to CTMS 1.8.3.

CSCtz76468

Symptom: Call-in Number voice prompts are not played when a TC5 (version 5.0) endpoint that is registered to VCS dials in.

Condition: The TC5 endpoint is registered to VCS. There is a trunk from VCS to CUCM.

Workaround: With VCS 7.1X, the voice prompts do not play completely. If the user still enters the meeting number, the endpoint is added to the meeting.

New and Changed Information for CTMS Release 1.8.2

Fixed Caveats

The following caveats were fixed in CTMS release 1.8.2:

CSCtw78534: Extend Multipoint Meetings and Start Meetings Early features do not work at the same time, so meetings cannot be started early or ended late.

CSCty26982: Using TelePresence Call-In number to dial into meeting that started early, participant receives message "please wait for the meeting to start."

CSCtx90451: CCP connection failure and SOAP socket read error on endpoint running TC5.0 software.

CSCtx69314: Logs cannot be downloaded from the CTMS Administrative UI and remote_account creation fails.

Caveats for CTMS Release 1.8.2

This section includes the following information:

CTMS Release 1.8.2 Caveat Reference

Caveats for CTMS Release 1.8.2

CTMS Release 1.8.2 Caveat Reference

Table 6 summarizes caveats found in CTMS Release 1.8.1.

Table 5 CTMS Release 1.8.2 Caveats and Caveats Corrected Reference 

 

Software Release

 
 

1.8.2

 

CDETS Number

Found in Release

Corrected in Release

Note

CSCua92152

1.8.2

1.8.4

 

Caveats for CTMS Release 1.8.2

CSCua92152

Symptom: Participants in a TelePresence call hear reverberation in the audio coming from another participating endpoint.

Condition: The meeting is secure and the participant is receiving audio from a triple-screen endpoint.

Workaround: Upgrade CTMS to software release 1.8.4.

New and Changed Information for CTMS Release 1.8.1

Alert Management

When disk usage is close to or exceeds a user-configurable threshold, an alert email is sent. The disk threshold, and email addresses for recipient and sender are configured on the Configure > Alert Management page.

CTMS sends alert emails under the following circumstances:

When the disk usage reaches 5% below the configured disk threshold percentage, CTMS sends an email indicating the disk usage is approaching the threshold.

When the disk usage exceeds the configured disk threshold percentage, CTMS sends an email indicating the disk usage has exceeded the threshold.

When the disk usage exceeds 90%, CTMS sends an email indicating the disk usage has exceeded the critical level.

CTMS resends the alert email every 24 hours as long as the condition remains the same. If the condition changes to one of the other circumstances that triggers an alert, the new alert email is sent within an hour of the change.


Note For alert emails to be sent, an email server must be configured on the Configure > Email Server page.


Email Server

On the Configure > Email Server page, an email server can be configured. CTMS uses this email server to send out the alert emails described in the Alert Management section.

New Process for Printing SDP Keys

SDP keys are not printed in logs for security reasons. Contact the Cisco Technical Assistance Center (TAC) if you need to print them.

Other Notes

When configuring VMware on the UCS server, the same OVF template used with CTMS release 1.8 can be used with release 1.8.1.

Fixed Caveats

The following caveats were fixed in CTMS release 1.8.1:

CSCtt20570: During a Cisco TelePresence WebEx meeting, the Cisco WebEx Video View window sometimes displays an inaccurate active speaker on the top left corner of the Video display.

CSCtt28939: When installing the CAPF root certificate on the CTMS, an error message appears saying that the file is the CTM-trust file.

CSCtu07635: In a CTMS 1.8 multipoint meeting, the video sent by a third-party TelePresence Interoperability Protocol Version 7 (TIPv7) unrestricted endpoint might not be seen on a CTS 1.8 endpoint.

CSCts99446: The Director Control set eventcontrol entry source CLI command does not work as expected.

CSCts35244: Adding a recording server results in a null pointer exception error in the CTMS web UI.

CSCtt70572: An endpoint is allowed to join a meeting and the meeting is downgraded to a lower quality, even though Allow Downspeed is set to No on the Manage > Default Meeting Settings page.

CSCtw57027: MCS 7845 H2 server fails due to 100% full disk space.

CSCtu22309: TelePresence Call-In Number prompts become squeaky.

CSCtu03710: Newly configured and upgraded secure CTS 1.8.x cannot join secure CTMS meeting.

Caveats for CTMS Release 1.8.1

This section includes the following information:

CTMS Release 1.8.1 Caveat Reference

Caveats for CTMS Release 1.8.1

CTMS Release 1.8.1 Caveat Reference

Table 6 summarizes caveats found in CTMS Release 1.8.1.

Table 6 CTMS Release 1.8.1 Caveats and Caveats Corrected Reference 

 

Software Release

 
 

1.8.1

 

CDETS Number

Found in Release

Corrected in Release

Note

CSCud22647

1.8.1

1.8.6

 

CSCty47078

1.8.1

None

 

CSCty26982

1.8.1

1.8.2

 

CSCtx90451

1.8.1

1.8.2

 

CSCtw84975

1.8.1

None

 

CSCtw70506

1.8.1

None

 

CSCtx06115

1.8.1

None

 

Caveats for CTMS Release 1.8.1

CSCud22647

Symptom: Devices connecting to a CTMS 1.8 conference through CUVC cannot hear an audio addin caller added in from the CTMS side of the call.

Condition: CTMS 1.8. addin caller on the CTMS side of call.

Workaround: Downgrade to CTMS 1.7. Add caller from the CUVC side of the call. Host conference entirely on CUVC or other MCU.

CSCty47078

Symptom: Multipoint calls between CTS endpoints and CTMS version 1.8.x can drop within 15 minutes.

Condition:

1. Multipoint calls include a CTS endpoint (any version).

2. CTMS version 1.8.x.

3. Default Unified CM SIP Session Expires Timer is set to 1800.

Workaround:

Change Unified CM SIP Session Expires Timer to 86400:

1. Log in to Unified CM.

2. Go to System > Service Parameters.

3. For Server, select the current server.

4. For Service, select Cisco CallManager (active).

5. In the Clusterwide Parameters (Device - SIP) section, find the SIP Session Expires Timer and change its value to 86400.

6. Click Save.

CSCty26982

Symptom: Meeting participant receives message "Please wait for the meeting to start."

Condition: Meeting participant uses TelePresence Call-In number to dial into meeting that started early.

Workaround: None

CSCtx90451

Symptom: CCP connection failure and SOAP socket read error.

Condition: Endpoint running TC 5.0 software registers to Unified CM and then joins meeting through CTMS.

Workaround: None

CSCtw84975

Symptom: When a 1080p-capable endpoint enters meeting, a message appears indicating it has been downgraded to 720p resolution.

Condition: Endpoint is running TC5 software.

Workaround: None

CSCtw70506

Symptom: Changing Adhoc Segments to 48 on the Configure > System Settings > Resources tab and Apply causes the error: "Unexpected Error Occurred while processing your request. Please contact the Diagnostic Technician to diagnose this problem."

Condition: IP address for CTS-Manager in the Configure > CTS Manager page is incorrect.

Workaround: Click Go Back and the resources are changed correctly.

CSCtx06115

Symptom: Endpoints that support 1080p resolution are dropped from the meeting.

Condition: Set Allow Downspeed setting to No on the Manage > Default Meeting Settings page and start an active static meeting.

Workaround: None.

Further Problem Description: This issue occurs with schedule and ad hoc meetings also.

New and Changed Information for CTMS Release 1.8

Supported Endpoint Types

In CTMS release 1.8, Supported Endpoint Types in the Manage > Default Meeting Settings page is introduced. With Supported Endpoint Types, you can control the endpoint types that are supported in Cisco TelePresence multipoint and network multipoint meetings managed by a particular CTMS. By default, only these endpoints are supported:

CTS 1.6.x, 1.7.x and 1.8 endpoints, where x is the latest maintenance release

For information about the latest maintenance releases, see the Cisco TelePresence System Software Compatibility Matrix, which you can access at this location:

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

Optionally, you can select "Cisco TelePresence TC 5.0 (and later) and CTS 1.8 (and later) endpoints," which supports the following endpoints:

Cisco TelePresence EX Series, C Series, and MX200 endpoints running TC software version 5.0 (and later)

CTS 1.8 (and later) endpoints


Note To interoperate with Cisco TelePresence endpoints running version TC 5.0 (and later) in multipoint and network multipoint meetings, CTS 1.8 is the minimum required endpoint version. CTS 1.7.x and older endpoints are not supported in this scenario and must be upgraded to CTS 1.8 or later.


While interoperating with Cisco TelePresence TC 5.0 (and later) endpoints in multipoint and network multipoint meetings, all supported endpoint types have full audio and video capabilities.

For information on Supported Endpoint Types, see 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

TelePresence Call-in Number

Introduced in version 1.8 of Cisco TelePresence Multipoint Switch (CTMS) and Cisco TelePresence Manager (CTS-Manager), the Cisco TelePresence Call-in Number feature enables a Meeting Organizer to allow users to join the meeting from Cisco TelePresence endpoints that are not scheduled in the meeting invitation. With this feature enabled in the Configure > Applications Settings page, Bridges and Servers tab, in the CTS-Manager Administrative UI, the CTS-Manager communicates with the CTMS to obtain the CTMS multipoint call-in number and the meeting number, which is a unique identifier for the meeting. The meeting organizer then provides the participants with the call-in number to join the meeting from their endpoints. After calling in, the participants hear a voice prompt and enter the meeting number. The CTMS permits participants to join after they enter the meeting number successfully.

For complete information on this feature, see the "Cisco TelePresence Call-In Number," which you can access at this location:

http://www.cisco.com/en/US/products/ps7074/products_installation_and_configuration_guides_list.html


Note Security with the TelePresence Call-In Number feature is not supported using CTMS. Any endpoint that joins a secure meeting using the TelePresence Call-In Number through CTMS will downgrade the meeting to non-secure.


UCS Server

CTMS release 1.8 can be installed and run on Cisco's new UCS server platform, the Cisco UCS C210 M2 server. Before installing CTMS software on a UCS C210 M2 server, you must configure the server and install VMWare.


Note Only one instance of CTMS can be installed on a UCS server at one time. Except for the required VMware software, no other software should be installed on the UCS server. The "no other software" caveat includes Cisco TelePresence Manager (CTS-Manager) and Cisco TelePresence Recording Server (CTRS).


For UCS C210 M2 server specifications, see Table 4.

For information about setting up the server and installing the CTMS software, see 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

For information about migrating from a Cisco MCS server to another MCS server or a UCS server, see the Hardware Migration Guide for CTS-Manager, CTMS, and CTRS - Release 1.8, which you can access at the following location:

http://www.cisco.com/en/US/docs/telepresence/hw_migration/1_8/ct_hw_mig.html

Network Multipoint

Multiple CTMS devices can be deployed in a Cisco TelePresence topology. Starting with CTMS release 1.8, the network multipoint feature allows two CTMS devices to support endpoints during a static meeting.

The support of two CTMS devices during a network multipoint meeting provides these benefits:

The number of endpoints that can potentially join the meeting increases.

The workload and amount of required bandwidth is distributed from one to two CTMS devices.

The strategic deployment of CTMS devices to support frequently used endpoints in key geographical areas reduces the number of expensive WAN links.

The transition of a static meeting to a network multipoint meeting is made dynamically as the meeting begins. From the perspective of the meeting participants, the experience of attending a network multipoint meeting is the same as attending a non-network multipoint meeting.

For information on network multipoint, see the Network Multipoint Design Guide, which you can access at this location:

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

Event Recording

Event Recording lets you create recordings of meetings with multiple video and audio streams. You can choose which streams to record. This is useful for recording scripted corporate events, such as company meetings. The recording is initiated from the CTMS where you can control what is being recorded. After the recording is completed, you can find and download the recording from the CTRS.

Because the special events to be recorded are director-controlled and generally scripted, you can manage an Event Recording session from the Director Control UI in the CTMS Administrative UI only. The CTMS Administrative UI enables you to select the video and audio streams to record, start, pause/resume, and stop the recording of the event.


Note Neither the CTMS nor the recording server issues a recording notification to meeting participants. Therefore, we recommend that you or the event speaker tell the participants that the meeting will be recorded before the recording begins.


After you finish recording an event, the recording is available for playback, sharing, downloading, and other tasks.


Note CTMS records both the high definition and low definition streams from endpoints.


For information on Event Recording, see 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

Browser Security

This new feature secures communication between the CTMS web server and the browser through which you access the CTMS Administrative UI. Browser security eliminates website security certificate warnings, which you receive if your web server is not secure.


Note On a CTMS, you can set up either inter-device security, which is an existing feature, or browser security, which is introduced in CTMS release 1.8. We do not support the deployment of both security features at the same time.


To implement browser security, you must buy a Secure Sockets Layer (SSL) certificate from a certificate authority (CA), then install it on the CTMS.

For more information on browser security, see the Securing Cisco TelePresence Products, Release 1.8:

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

MXE Support Discontinued

In earlier versions of the CTMS release notes, CTMS 1.8 and MXE 5600 with limited interoperability was supported.

Based on recent testing, it has been determined that MXE 5600 interop with CTMS 1.8 or higher is a solution Cisco can no longer recommend to customers. As a result, support for Media Experience Exchange (MXE) 5600 is discontinued with CTMS and CTS-Manager 1.8 and 1.9.

Existing customers are encouraged to migrate to TelePresence Server for interop.

For options regarding MXE 5600, contact your Cisco account team or send an inquiry to Ravi Bansal via email: ravbansa@cisco.com.

Interface Failover

Interface failover is no longer supported using the CTMS Web UI. To configure interface failover, use the set network failover command in the CTMS command line interface. For more information, refer to the CTMS 1.8 Command Reference.

Fixed Caveats

The following caveats were fixed in CTMS release 1.8:

CSCtf51649: Core files from cimlistener observed while checking CTMS log files

CSCti08961: CTMS & CTS-Man connection fails with blank spaces before/after username

CSCto57796: Underscore in EP alerting name causes GUI Director Controls issue

CSCts32789: CTMS scheduled active meeting segments exceed configured value

Documentation Errata in Release 1.8

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

This section includes the following information:

CTMS Release 1.7.2 Caveat Reference

Caveats for CTMS Release 1.7.2

CTMS Release 1.8 Caveat Reference

Table 7 summarizes caveats found in CTMS Release 1.8.

Table 7 CTMS Release 1.8 Caveats and Caveats Corrected Reference 

 

Software Release

 
 

1.8

 

CDETS Number

Found in Release

Corrected in Release

Note

CSCts96815

1.8

   

CSCtt44841

1.8

None

 

CSCuc05549

1.8

1.8.5

 

CSCua83891

1.8

1.8.4

 

CSCts99571

1.8

1.8.4

 

CSCtw78534

1.8

1.8.2

 

CSCtx69314

1.8

1.8.2

 

CSCtu33601

1.8

None

 

CSCtu03710

1.8

1.8.1

 

CSCts99446

1.8

1.8.1

 

CSCts35244

1.8

1.8.1

 

CSCtt70572

1.8

1.8.1

 

CSCtu22309

1.8

1.8.1

 

CSCtt20160

1.8

1.8.4

 

CSCtl56527

1.8

None

 

CSCtl80292

1.8

None

 

CSCto12827

1.8

None

 

CSCtq40875

1.8

None

 

CSCtr29759

1.8

None

 

CSCtr88752

1.8

None

 

CSCtr92930

1.8

None

 

CSCts58516

1.8

None

 

CSCts73135

1.8

None

 

CSCtt02782

1.8

None

 

CSCtt15171

1.8

None

 

CSCtt20570

1.8

None

 

CSCtt22558

1.8

None

 

CSCtt28939

1.8

None

 

CSCtt42155

1.8

None

 

CSCtt44841

1.8

None

 

CSCtu07635

1.8

None

 

Caveats for CTMS Release 1.8

CSCts96815

Symptom: CTMS accessible on revoked browser security certificate.

Condition: Install and apply browser security successfully. From CA, make the applied certificate revoked. Access CTMS administrative web UI from Internet Explorer browser.

Workaround: Access CTMS administrative web UI from a different browser.

CSCtt44841

Symptom: When a CTS 1.6.x endpoint tries to join a Cisco WebEx-enabled scheduled meeting supported by a CTMS 1.8, the endpoint is dropped with the following alarm:

ALARM_INTEROP_NOT_SUPPORTED. Call not connected. The endpoint is unable to join the meeting because it does not support interoperability.

Condition: See Symptom.

Workaround: None.

Further Problem Description: The system message that displays does not specify the type of interoperability that is not supported. The call was dropped because the CTS 1.6.x endpoint does not support Cisco WebEx interoperability.

CSCuc05549

Symptom: CTMS crashes and is unable to process calls.

Condition: CTMS version 1.8.x. UDP is configured between Unified CM and CTMS.

Workaround: Change SIP trunk configuration between Unified CM and CTMS to TCP.

Further Problem Description: If UDP is set on the SIP trunk between Unified CM and CTMS, calls may not get processed.

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.

CSCts99571

Symptom: System capacity is down to 34 ports with Cisco MXE Media Processing Modules.

Condition: Place 45 ports via MXE to a CTMS running software release 1.8.

Workaround: Use a CTMS running software release 1.7.x or earlier.

CSCtw78534

Symptom: Extend Multipoint Meetings and Start Meetings Early features do not work at the same time, so meetings cannot be started early or ended late.

Condition: Both Extend Multipoint Meetings and Start Meetings Early are enabled at the same time.

Workaround: None.

CSCtx69314

Symptom: Logs cannot be downloaded from the CTMS Administrative UI, and remote_account creation fails.

Condition: CTMS /common file system is set to read only. CTMS 1.8.0(1026) on MCS 7845-I2 that has been upgraded.

Workaround: None.

CSCtu33601

Symptom: "null" and `Go Back' are incorrectly displayed when changing device security to Non-Secure.

Condition: With CTMS in secure mode, go to Unified CM > SIP Profile Settings tab, change the Device Security from Secure to Non-Secure and click Apply.

Workaround: Click elsewhere in the CTMS Administrative Web UI and the setting is changed properly.

CSCtu03710

Symptom: Newly configured and upgraded secure CTS 1.8.x cannot join secure CTMS meeting.

Condition: In a rare situation with packet loss (such as in a bad network) the protocol of key exchange cannot finish between CTMS and CTS.

Workaround: Ensure the phone device configuration on Unified CM has Disable Speakerphone and Disable Speakerphone and Headset checked (enabled) and the PC Port option disabled, then retry joining the meeting from the endpoint.

CSCts99446

Symptom: The Director Control set eventcontrol entry source CLI command does not work as expected.

Condition:Director Controls are enabled, a meeting is started and the set eventcontrol entry source command is issued to lock new participants to seeing a specific existing participant. When a new participant joins, they do not see the existing participant as expected.

Workaround: None.

CSCts35244

Symptom: Adding a recording server results in a null pointer exception error in the CTMS web UI.

Condition: In the Configure > Recording Server page, click New and enter a value. Press Enter (instead clicking Save).

Workaround: Click Save instead of pressing Enter.

CSCtt70572

Symptom: An endpoint is allowed to join a meeting and the meeting is downgraded to a lower quality, even though Allow Downspeed is set to No on the Manage > Default Meeting Settings page.

Condition: Allow Downspeed is set to No on the Manage > Default Meeting Settings page of CTMS. An endpoint configured with quality of 1 MB joins a meeting with quality of 1.5 MB and the meeting downgrades to 1 MB.

Workaround: None.

CSCtu22309

Symptom: TelePresence Call-In Number prompts become squeaky.

Condition: If there are more than 5 endpoints, the prompts can become squeaky for new users joining the meeting via the TelePresence Call-In Number.

Workaround: None.

CSCtt20160

Symptom: Active speaker video switching from Movi (now called Jabber) taking more than 20 seconds in a multipoint call.

Condition: Establish the multipoint call using the CTS1000, EX90 and Movi keep switching the active speaker by speaking from each end point observe the video switch from Movi to other parties in the bridge.

Workaround: None.

CSCtl56527

Symptom: In a meeting with two single-segment endpoints and one triple-segment endpoint, the participants displayed by each single endpoint generally appear simultaneously in the center and left segments of the triple endpoint. However, in a network multipoint meeting, participants displayed by each single endpoint might compete to be displayed in the center segment of a triple endpoint, leaving the left and right segments blank.

Condition: This issue can occur if each single endpoint is supported by a different CTMS device in a network multipoint meeting. In this situation, each single endpoint is basically competing for the active speaker video in a triple endpoint, leaving the left and right segments blank.

Workaround: There is no workaround if no additional participants join the meeting. However, if more participants join, all segments of the triple endpoint will display participants.

Further Problem Description: This issue is a user experience issue in terms of optimally filling all segments of a triple endpoint. It does not affect any other functionality of the system.

CSCtl80292

Symptom: In a Commercial Express environment, after CTMS registers to CTS-Manager for the first time or after a new license application, the CTMS segment count is updated properly and shown on CTMS UI as expected. However, the updated CTMS segment count is not updated on CTS-Manager.

Condition: See Symptom.

Workaround: From the CTMS Administrative UI, register manually with CTS-Manager again. This action forces a segment update with CTS-Manager.

Further Problem Description:

1. CTMS sends registration request to CTS-Manager with 0 segment as it does not have license information.

2. CTS-Manager stores the segment count 0.

3. CTS-Manager sends the license information in response to CTMS.

4. CTMS gets the license information and sets the scheduled segments to 12 and ad-hoc to 3.

5. CTMS does not update CTS-Manager with new segment count.

CSCto12827

Symptom: If an endpoint tries to join a locked CTMS meeting, Cisco Unified Communications Manager (Unified CM) may respond with "400 Bad Request" instead of "480 Temporarily Unavailable" or "486 Busy Here."

Condition: The described symptoms could occur under the following conditions:

CTMS release is 1.7 or 1.8

Unified CM release is 8.6 or earlier

Workaround: None. This issue will be fixed in an upcoming CTMS release.

CSCtq40875

Symptom: After a CTMS is added in the Configure > Bridges and Servers page of the CTS-Manager Administrative UI, the status of the CTMS in the CTS-Manager Admin UI is OK. However, a few minutes later, the CTMS goes into a critical error state.

Condition: See Symptom. This issue can occur if the CTMS and CTS-Manager are both running release 1.8.

Workaround: Clear the critical system messages related to this issue in the CTMS Administrative UI, Troubleshoot > System Messages page. This action should enable the CTMS to return to an OK state in the CTS-Manager Administrative UI.

CSCtr29759

Symptom: After starting an ad hoc meeting using the Manage > Ad-Hoc Meeting page in the CTMS Administrative UI, you click Cancel. However, this action does not stop the CTMS from dialing the endpoints.

Condition: This issue can occur if one or more of the endpoints added to the ad hoc meeting are already in a meeting.

Workaround: After the meeting is started, you can cancel the meeting, thereby freeing up the endpoints, by manually deleting each endpoint from the Manage > Active Meetings page.

CSCtr88752

Symptom: The video quality of a CTMS multipoint meeting is downgraded to 720p even though all endpoints in the meeting are CTS and support 1080p.

Condition: These symptoms might occur under the following conditions:

Cisco Unified Communications Manager (Cisco Unified CM) release is 7.1

CTS release is 1.8

Workaround: Upgrade Cisco Unified CM release to 8.5.1 or later.

Further Problem Description: This issue applies only to Unified CM release 7.1 because this release does not handle multiple video PTs (Payload Types) in the SDP correctly. CTS sends two PTs in the order of 1080p and 720p in the SDP. Unified CM 7.1 always chooses the last one, in this case the PT of 720p and adds it to the SDP sent to CTMS. Unified CM release 7.1's method of handling multiple PTs causes CTMS to choose 720p resolution for the conference.

CSCtr92930

Symptom: An endpoint might suddenly be dropped from a meeting without record of the endpoint sending a SIP BYE message to the CTMS, although the CTMS received the SIP BYE message from the endpoint.

Condition: This issue is caused by Cisco Unified Communications Manager (Unified CM) sending the SIP BYE message on behalf of the endpoint. This behavior is the result of a Unified CM caveat, which affects the handling of the SIP SESSION TIMER expiry. This Cisco Unified CM issue is tracked by CSCts04421.

Workaround: The SIP SESSION TIMER is normally set to 1800 (seconds). To avoid this issue (until a fix is officially released for Unified CM), the SIP SESSION TIMER should be increased to the maximum value, which is 86400 (seconds) (or 1 day).

Further Problem Description: To set the Unified CM SIP SESSION TIMER to 86400 seconds:

1. Log in to Unified CM.

2. Go to System > Service Parameters.

3. Select Server = current server. For example, "<ip-address-or-hostname> (Active)".

4. Select Service = Cisco CallManager (Active).

5. Select SIP Session Expires Timer, and set it to 86400

CSCts58516

Symptom: You enter the set logging disable CLI command, but it does not disable logging.

Condition: This command does not work in CTMS releases 1.6, 1.7, and 1.8 for the user account.

Workaround: None. This command will be removed from an upcoming CTMS release.

CSCts73135

Symptom: The CTMS Administrative UI is no longer reachable, and the browser provides an error message, which says that the certificate has been revoked.

Condition: This situation can occur if the SSL certificate you bought from a Certificate Authority expires while the browser security feature is enabled on the CTMS.

Workaround: Log into the CTMS Administrative command-line interface (CLI) and use the set web-security command to generate a self-sign certificate that allows you to resume logging into the CTMS Administrative UI. For information on how to use this command, see the Cisco TelePresence Multipoint Switch Release 1.8 Command Reference at:

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

When you are able to log into the CTMS Administrative UI again, go to the Configure > Security page, set Browser Security to "Non-Secure," and click Apply.

After disabling browser security, you must decide whether to install a new SSL certificate or to keep browser security disabled. For information on installing a new SSL certificate, see the Cisco TelePresence Multipoint Switch Release 1.8 Administration Guide, which you can access at:

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

CSCtt02782

Symptom: After upgrading the CTMS from release 1.7 to 1.8, secure calls are not being completed.

Condition: This issue can occur if the following sequence of events occurs:

1. CTMS release 1.7 is upgraded to 1.8.

2. The Cisco Unified Communications Manager (Unified CM) certificates are regenerated.

3. In the CTMS Administrative UI, the old certificates are deleted and the regenerated ones are installed in the CTMS.

Workaround: To work around this issue, do the following:

1. In the CTMS Administrative UI, do the following:

Switch back to CTMS 1.7.

Delete the old certificates.

Install the regenerated certificates.

2. Verify that the secure calls are going through.

3. Upgrade the CTMS again to release 1.8.

CSCtt15171

Symptom: The time displayed in the Media Snapshot dialog box corresponds to the location of the CTMS server instead of the location of the CTMS administrator.

Condition: This issue occurs when accessing the Media Snapshot dialog box for an active meeting on a CTMS running any release.

Workaround: If the CTMS server and administrator are in different time zones, convert the time as appropriate.

CSCtt42155

Symptom: After launching a Cisco TelePresence WebEx meeting using One-Button-to-Push, the presenter in Room A passes the ball to a presenter in Room B. However, the Cisco WebEx Video View window continues to display "Viewing Room A's desktop" as well as the WebEx ball next to Room A.

Condition: The described symptom may occur if the presenter in each room still has the presentation cable connected to their laptop.

Workaround: The presenter in each room should disconnect the presentation cable from their laptop, then the next presenter should reconnect the cable to their laptop.

CSCtt22558

Symptom: Occasionally, the cimlistener process produces a core dump under /var/log/active/core.

Condition: The core dump can occur at any time.

Workaround: The core dump is benign, and the cimlistener process restarts itself afterward. To remove core dump(s) that may accumulate, you can set up a cron job that periodically removes them.

CSCtt28939

Symptom: When installing the CAPF root certificate on the CTMS, an error message appears saying that the file is the CTM-trust file.

Condition: This situation can occur under the following conditions:

The CTMS is running software version 1.8

The string "CUCM" appears in the path, such as a directory name, to the certificate. For example:

C:\Documents and Settings\Administrator\Desktop\CUCM\CAPF.der

Workaround: Remove or rename any path elements that contain the string "CUCM".

Fixed: 1.8.1

CSCtt20570

Symptom: During a Cisco TelePresence WebEx meeting, the Cisco WebEx Video View window sometimes displays an inaccurate active speaker on the top left corner of the Video display.

Condition: See Symptom.

Workaround: None.

Fixed: 1.8.1

CSCtt44841

Symptom: When a CTS 1.6.x endpoint tries to join a Cisco WebEx-enabled scheduled meeting supported by a CTMS 1.8, the endpoint is dropped with the following alarm:

ALARM_INTEROP_NOT_SUPPORTED. Call not connected. The endpoint is unable to join the meeting because it does not support interoperability.

Condition: See Symptom.

Workaround: None.

Further Problem Description: The system message that displays does not specify the type of interoperability that is not supported. The call was dropped because the CTS 1.6.x endpoint does not support Cisco WebEx interoperability.

CSCtu07635

Symptom: In a CTMS 1.8 multipoint meeting, the video sent by a third-party TelePresence Interoperability Protocol Version 7 (TIPv7) unrestricted endpoint might not be seen on a CTS 1.8 endpoint.

Condition: CTMS 1.8 does not properly support third-party TIPv7 devices indicating unrestricted media transmission in multipoint meetings with CTS 1.8 and earlier endpoints.

Workaround: None. This issue will be resolved in an upcoming maintenance release.

Fixed: 1.8.1

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

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 eventcontrol 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.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 8 summarizes caveats found in CTMS Release 1.7.1.

Table 8 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

Unreproducable in 1.8

-

CSCtn06831

1.1

1.2

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

CSCtn23550

1.7.2

Unreproducable in 1.8

-

CSCto59894

1.7.2

Unreproducable in 1.8

-

CSCto11614

1.7.2

-

 

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.

CSCto11614

Symptom: User can enter an invalid WebEx TelePresence Gateway URL on the Configure > WebEx page.

Condition: CTMS does not validate the URL for WebEx Telepresence Gateway.

Workaround: None.

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 9 summarizes caveats found in CTMS Release 1.7.1.

Table 9 CTMS Release 1.7.1 Caveats and Caveats Corrected Reference 

 

Software Release

 

1.7.1

CDETS Number

Found in Release

Corrected in Release

CSCtw57027

1.7.1

1.8.1

CSCtl06578

1.7.1

Duplicate of CSCts32789, which was corrected in Release 1.8

CSCtl47516, CSCts32789

1.7.1

Duplicate of CSCts32789, which was corrected in Release 1.8

CSCtn89016

1.7.1

1.7.2

CSCto57796

1.7.1

1.8


Caveats for CTMS Release 1.7.1

CSCtw57027

Symptom: MCS 7845 H2 server failed due to 100% full disk space.

Condition: A file became too big and used up all the disk space on root.

Workaround: None.

CSCtl06578

(Duplicate of CSCts32789)

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, CSCts32789

(CSCtl47516 is a duplicate of CSCts32789)

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

Table 10 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

1.8

CSCti08961

1.7.0

1.8

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.

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 11 summarizes caveats found in CTMS Release 1.7.0.

Table 11 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

Closed during 1.8

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

Unreproducable in 1.8

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

Table 12 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

1.7.2


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.

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 Release Versions

Table 13 provides the current recommended set of software release versions for the Cisco TelePresence solution.

Table 13 Software Release Versions  

Product/Component
Recommended Version
Release Date

Cisco TelePresence System (CTS)

1.5.3(10)

7/22/2009

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:

Caveats for CTMS Release 1.5.3

CTMS Release 1.5 Caveat Reference

Table 14 summarizes caveats still open in CTMS Release 1.5.x.

Table 14 CTMS Release 1.5 Caveats and Caveats Corrected Reference 

 

Software Release

 

1.5.3

CDETS Number

Found in Release

Corrected in Release

CSCta74252

1.5.3

None


Caveats for CTMS Release 1.5.3

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.

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.