Guest

Cisco TelePresence Multipoint Switch

Release Notes for Cisco TelePresence Multipoint Switch Release 1.1

Table Of Contents

Release Notes for Cisco TelePresence Multipoint Switch, Release 1.1

Introduction

New Information for CTMS Release 1.1

Increase in the Number of Supported Segments

Cisco TelePresence Interoperability With Legacy Video Conferencing Devices

Software Releases and Component Firmware Versions

TelePresence Software Compatibility Matrix

Open Caveats from CTMS Release 1.1.1

Open Caveats from CTMS Release 1.1

Closed and Resolved Caveats from CTMS Release 1.1

Open Caveats from CTMS Release 1.0.3(15)

Closed and Resolved Caveats from CTMS Release 1.0.3(15)

Open Caveats from CTMS Release 1.0.3(8)

Closed and Resolved Caveats from CTMS Release 1.0.3(8)

Open Caveats from CTMS Release 1.0.2(250)

Closed and Resolved Caveats from CTMS Release 1.0.2(250)

Open Caveats from CTMS Release 1.0

Closed and Resolved Caveats from CTMS Release 1.0

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco TelePresence Multipoint Switch, Release 1.1


Created: May 5, 2008, OL-13015-05
Last Updated: August 7, 2008

Introduction

These release notes describe the open caveats and additional information for the Cisco TelePresence Multipoint Switch (CTMS), Release 1.1.

New Information for CTMS Release 1.1

Increase in the Number of Supported Segments

CTMS Release 1.1 now supports up to 48 table segments (48 single-screen systems, 16 triple-screen systems, or a mix of both) in a single Cisco TelePresence conference.

Cisco TelePresence Interoperability With Legacy Video Conferencing Devices

Cisco TelePresence is based on open standards, including SIP, H.264. AAC-LD and G.711. With Cisco TelePresence System (CTS) Release 1.3 and CTMS Release 1.1, Cisco TelePresence now supports interoperability between Cisco TelePresence systems and traditional video conferencing/video telephony endpoints using the Cisco Unified Video Conferencing 3500 series MCU (CUVC).

Software Releases and Component Firmware Versions

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


Note CTS Release 1.4 software provides support for Cisco Unified Communications Manager Version 5.1.x. To enable this support, enter the set downrev-cucm enable command for the Cisco TelePresence System software in command-line interface (CLI) mode.


Table 1 Software Releases and Component Firmware Versions  

Product/Component
Recommended Version
Release Date

Cisco TelePresence System (CTS)

1.4.0

7/28/2008

CTS component firmware: Display AppCode for Gen1 Displays

1.05

8/15/2007

CTS component firmware: Display BootCode for Gen1 Displays

1.01

8/15/2007

CTS component firmware: Display App_Code for Gen2 Displays

11.01

8/15/2007

CTS component firmware: Display BootCode for Gen2 Displays

11.05

8/15/2007

CTS component firmware: Camera firmware version

390

2/7/2008

Cisco TelePresence Manager (CTS-Man)

1.3.2

6/28/2008

Cisco TelePresence Multipoint Switch (CTMS)

1.1.1

8/4/2008

Cisco Unified Communications Manager (Unified CM)

6.x1

10/22/2007

Cisco Unified IP Phone 7970G

8.3(2)

8/10/2007

Cisco Unified IP Phone 7975G

8.3(2)

8/10/2007

1 Enter the set downrev-cucm enable CLI command for the CTS software to enable your Cisco TelePresence system to work with Cisco Unified Communications Manager version 5.1.x.


TelePresence Software Compatibility Matrix

Table 2 provides information about TelePresence software compatibility.

Table 2 TelePresence Software Compatibility Matrix  

Software
CTS 1.0
CTS 1.1.1
CTS 1.2.0/1
CTS 1.2.2/3
CTS 1.3
CTS 1.4
CTMS 1.0.2 or earlier
CTMS 1.0.3 or 1.0.4
CTMS 1.1
CTMS 1.1.1
CTS-Man 1.0
CTS-Man 1.1
CTS-Man 1.2
CTS-Man 1.3
CTS-Man 1.4
CTS 1.0

Yes

Yes

No

No

No

No

Yes

No

No

No

Yes

No

No

No

No

CTS 1.1.1

Yes

Yes

Yes

Yes

No

No

Yes

Yes

No

No

Yes

Yes

No

No

No

CTS 1.2.0/1

No

Yes

Yes

Yes

No

No

Yes

Yes

No

No

No

No

Yes

No

No

CTS 1.2.2/3

No

Yes

Yes

Yes

Yes

No

No

Yes

Yes

Yes

No

No

Yes

Yes

Yes

CTS 1.3

No

No

No

Yes

Yes

Yes

No

Yes

Yes

Yes

No

No

No

Yes

Yes

CTS 1.4

No

No

No

No

Yes

Yes

No

No

No

Yes

No

No

No

Yes

Yes

CTMS 1.0.2 or earlier

Yes

Yes

Yes

No

No

No

NA

NA

NA

NA

No

Yes

Yes

No

No

CTMS 1.0.3 or 1.0.4

No

Yes

Yes

Yes

No

No

NA

NA

NA

NA

No

Yes

Yes

Yes

Yes

CTMS 1.1

No

No

No

Yes

Yes

No

NA

NA

NA

NA

No

No

Yes

Yes

Yes

CTMS 1.1.1

No

No

No

Yes

Yes

Yes

NA

NA

NA

NA

No

No

No

Yes

Yes

CTS-Man 1.0

Yes

Yes

No

No

No

No

No

No

No

No

NA

NA

NA

NA

NA

CTS-Man 1.1

No

Yes

No

No

No

No

Yes

Yes

No

No

NA

NA

NA

NA

NA

CTS-Man 1.2

No

No

Yes

Yes

No

No

Yes

Yes

No

No

NA

NA

NA

NA

NA

CTS-Man 1.3

No

No

No

Yes

Yes

Yes

No

Yes

Yes

Yes

NA

NA

NA

NA

NA

CTS-Man 1.4

No

No

No

Yes

Yes

Yes

No

Yes

Yes

Yes

NA

NA

NA

NA

NA

CTS500

No

No

No

No

No

Yes

No

No

No

Yes

No

No

No

No

Yes

CTS3200

No

No

No

No

No

Yes

No

No

No

Yes

No

No

No

No

Yes

CUCM 5.1.3

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

CUCM 6.0/6.1

No

Yes

Yes

Yes

Yes

Yes

No

Yes

Yes

Yes

No

Yes

Yes

Yes

Yes

SBC 3.7

No

No

Yes

Yes

Yes

Yes

No

No

No

Yes

NA

NA

NA

NA

NA

SIP
70.8-3-3
SR2S

No

Yes

Yes

Yes

Yes

Yes

NA

NA

NA

Yes

No

Yes

Yes

Yes

Yes

SIP
70.8-2-2

Yes

Yes

Yes

Yes

No

No

NA

NA

NA

Yes

Yes

Yes

No

No

No


Open Caveats from CTMS Release 1.1.1

CSCsm93296

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

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

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

CSCso98637

Condition: New QoS Settings are not saved after system restart

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

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

CSCsq37498

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

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

Workaround: The presentation will reappear under the following circumstances:

When another endpoint dials into the meeting.

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

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

CSCsr07887

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

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

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

CSCsr25631

Condition: Default Settings do not persist after upgrade.

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

Switching policy will change to Speaker if originally Room

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

Allow downspeed will change to Yes if originally set to No

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

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

Values that persist:

Max rooms

Video Announce

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

CSCsr56370

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

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

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

Open Caveats from CTMS Release 1.1

CSCso13993

Condition: Erroneously reports audio packet loss while there is no actual packet loss. There was a gap in the audio stream which was perceived as "loss."

Summary: During a CTS MP call, no audio issue is notice, call isn't dropped. When Site B overrides Site A's presentation, and Site A's presentation becomes active again, it is possible that the meeting will report a large packet loss. This is because when Site A's presentation is originally overridden, another audio stream will not necessarily be sent automatically. So, if Site A's presentation becomes active again, it is possible it may send to the same decoder as it did before, and look like a large gap in packets, causing the call to report loss.

Workaround: Hang up and call again.

CSCso76744

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

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

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

CSCso77232

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

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

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

Closed and Resolved Caveats from CTMS Release 1.1

CSCsl69290

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

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

CSCso16467

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

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

CSCso53449

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

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

CSCso61170

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

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

CSCso61729

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

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

CSCso62784

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

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

CSCso70405

Condition: Scheduled conference video announce is not working.

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

CSCso73123

Condition: Adding DNS erases Unified CM settings.

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

Workaround: Manually reconfigure Unified CM settings.

CSCso79483

Condition: Admin WebUI shows ALARM_DUPLICATE_CALL alarm.

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

CSCso87663

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

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

CSCso95895

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

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

CSCsq06085

Condition: Scheduled conference cannot launch from phone.

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

Open Caveats from CTMS Release 1.0.3(15)

CSCso71518

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

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

Workaround: The endpoint that wishes to present should unplug and plug back in the presentation at any time to become active.

Closed and Resolved Caveats from CTMS Release 1.0.3(15)

CSCsh68518

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

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

CSCsi46414

Condition: Cannot delete template.

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

CSCsj40959

Condition: Duplicate word in system error message.

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

CSCsj51843:

Condition: CTMS log files shows password.

Summary: CTMS logs show password in clear text.

CSCsk95166

Condition: Template disappears after it has been edited.

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

CSCsj90340

Condition: CTMS doesn't show scheduled meeting.

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

CSCsj90347

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

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

CSCsj92542

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

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

CSCsj94543

Condition: MediaProperties performance optimization.

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

CSCsj96270

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

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

CSCsk05875

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

Summary: Verified

CSCsk05968

Condition: Static meeting subject does not display.

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

CSCsk06046

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

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

CSCsk10737

Condition: Cannot delete static meetings.

Summary: Intermittently, user cannot delete static meetings.

CSCsk29972

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

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

CSCsk52342

Condition: Statistics did not refresh.

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

CSCsk57054

Condition: Media layer not forwarding SRs to endpoints.

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

CSCsk60800

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

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

CSCsk68251

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

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

CSCsk81167

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

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

CSCsk87203

Condition: CTMS high CPU causes call drop.

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

CSCsk91728

Condition: Installation error.

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

Open Caveats from CTMS Release 1.0.3(8)

There are no open caveats from CTMS Release 1.0.3(8) (severity level 1, 2, or 3) as of May 5, 2008.

Closed and Resolved Caveats from CTMS Release 1.0.3(8)

CSCsi16039

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

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

CSCsi24160

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

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

CSCsi45541

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

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

CSCsi49322

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

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

CSCsi51051

Condition: Pages take a long time to refresh.

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

CSCsi51283

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

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

CSCsi84648

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

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

CSCsi95884

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

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

CSCsj02267

Condition: CTMS host name change not allowed.

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

CSCsj05237

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

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

CSCsj15373

Condition: GUI "hangs" after being idle.

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

CSCsj24360

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

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

CSCsj29837

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

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

CSCsj31510

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

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

CSCsj35537

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

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

CSCsj44260

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

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

CSCsj48010

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

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

CSCsj87499

Condition: Dual image on CTS 1000.

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

CSCsj90876

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

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

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

CSCsj92140

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

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

CSCsj92146

Condition: Media statistics enhancement.

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

Mean jitter standard deviation

Mean video frame duration standard deviation

Max ssrc switch count per 4 seconds

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

Total packets received and transmitted

CSCsj92637

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

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

CSCsj92688

Condition: Inconsistent switch and IDR packet lost.

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

CSCsk43793

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

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

Open Caveats from CTMS Release 1.0.2(250)

There are no open caveats from CTMS Release 1.0.2(250) (severity level 1, 2, or 3) as of May 5, 2008.

Closed and Resolved Caveats from CTMS Release 1.0.2(250)

CSCsj31519

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

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

CSCsj51298

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

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

CSCsj35537

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

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

CSCsj38998

Condition: Log files contain extraneous files.

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

Open Caveats from CTMS Release 1.0

There are no open caveats from CTMS Release 1.0 (severity level 1, 2, or 3) as of May 5, 2008.

Closed and Resolved Caveats from CTMS Release 1.0

CSCsh81490

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

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

CSCsi26863

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

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

CSCsi44352

Condition: Time zone is not configurable during installation.

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

CSCsi45541

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

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

CSCsi48875

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

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

CSCsi48916

Condition: Cannot delete user.

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

CSCsi52075

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

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

CSCsi53840

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

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

CSCsi54335

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

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

CSCsi55871

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

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

CSCsi58667

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

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

CSCsi69494

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

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

CSCsi67495

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

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

CSCsi70080

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

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

CSCsi71121

Condition: No indication given when switching versions.

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

CSCsi71444

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

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

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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

Printed in the USA on recycled paper containing 10% postconsumer waste.