Guest

Cisco TelePresence Manager

Release Notes for Cisco TelePresence Manager 1.6

  • Viewing Options

  • PDF (420.1 KB)
  • Feedback
Release Notes for Cisco TelePresence Manager Release 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5

Table Of Contents

Release Notes for Cisco TelePresence Manager Release 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5

Contents

Introduction

Software Releases and Component Firmware Versions

Hardware Support and Upgrade Path

Cisco TelePresence Software Compatibility Matrix

What New in this Release

New in Release 1.6.5:

New in Release 1.6.3:

New in release 1.6.x

CTS-Manager Release 1.6.x Caveat Reference

Caveats for CTS-Manager Release 1.6.5

Caveats for CTS-Manager Release 1.6.4

Caveats for CTS-Manager Release 1.6.3

Caveats for CTS-Manager Release 1.6.2

Caveats for CTS-Manager Release 1.6.1

Caveats for CTS-Manager Release 1.6

Caveats for CTS-Manager Release 1.5.1

Caveats for CTS-Manager Release 1.5

Caveats for CTS-Manager Release 1.4

Supplemental End User License Agreement

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco TelePresence Manager Release 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5


Created: Feb. 24, 2010, OL-13672-07

Contents

Introduction

Software Releases and Component Firmware Versions

Hardware Support and Upgrade Path

Cisco TelePresence Software Compatibility Matrix

What New in this Release

CTS-Manager Release 1.6.x Caveat Reference

Caveats for CTS-Manager Release 1.6.5

Caveats for CTS-Manager Release 1.6.4

Caveats for CTS-Manager Release 1.6.3

Caveats for CTS-Manager Release 1.6.2

Caveats for CTS-Manager Release 1.6.1

Caveats for CTS-Manager Release 1.6

Caveats for CTS-Manager Release 1.5.1

Caveats for CTS-Manager Release 1.5

Caveats for CTS-Manager Release 1.4

Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

This Release Note describes the open caveats and additional information for all releases associated with Cisco TelePresence Manager (CTS-Manager), Release 1.6.x.


Note CTS-Manager is supported only in an enterprise intranet environment. NAT deployment is not supported.


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.

Table 1 Software Releases and Component Firmware Versions  

Product/Component
Recommended Version
Release Date

Cisco TelePresence Manager (CTS-Manager)

1.6.4

4/2010

Display Firmware

Gen 1 Displays:

CTS component firmware: Display AppCode for Gen 1 Displays

1.05

8/15/2007

CTS component firmware: Display BootCode for Gen 1 Displays

1.01

8/15/2008

Gen 2 Displays:

CTS component firmware: Display App_Code for Gen 2 Displays

11.0D

8/21/2009

CTS component firmware: Display BootCode for Gen 2 Displays

11.05

8/15/2007

Gen 3 Displays:

CTS component firmware: Display App_Code for Gen 3 Displays

21.05

8/29/2009

CTS component firmware: Display BootCode for Gen 3 Displays

21.00

8/29/2009

Camera Firmware

CTS component firmware: Camera firmware version

462

2/7/2008

Cisco Unified CM Components

Cisco Unified Communications Manager (Cisco Unified CM)

7.0.2, 7.1.2, 7.1.3

Note You must be running a minimum of Release 7.0.2 to use MIDlets.

Release 8.0.1 is not supported by CTS-Manager 1.6.x and earlier releases.

2/2009; 11/2009

Cisco TelePresence System MIDlet

TSPM.1-6-0-1S

10/2009

Cisco Unified IP Phone 7970G

8.4(3)

08/2009

Cisco Unified IP Phone 7975G

8.4(3)

02/2009

Additional Software

Cisco TelePresence Multipoint Switch (CTMS)

1.6.3

2/2010

Cisco TelePresence System (CTS) software

1.6.2

1/2010


Hardware Support and Upgrade Path

Table 2 Hardware Support and Upgrade Path  

Cisco TelePresence Manager Version
Shipping
Supported
May be Upgraded to CTS-Manager Versions:

1.1

MCS-7835-H2-CTS1

MCS-7835-H1-CTS1

MCS-7835-H2-CTS1

1.2, 1.3

1.2

MCS-7835-I2-CTS1

MCS-7835-H2-CTS1

MCS-7835-H1-CTS1

MCS-7835-H2-CTS1

MCS-7835-I2-CTS1

1.3

1.3

MCS-7835-I2-CTS1

MCS-7835-H2-CTS1

MCS-7835-H1-CTS1

MCS-7835-H2-CTS1

MCS-7835-I2-CTS1

1.4

1.4

MCS-7835-H2-CTS1MCS-7835-I2-CTS1

MCS-7835-H2-CTS1

MCS-7835-I2-CTS1

1.5, 1.6.0, 1.6.x

1.5, 1.5.x

MCS-7845-H2-CTS2MCS-7845-I2-CTS2

MCS-7835-H2-CTS1

MCS-7835-I2-CTS1

MCS-7845-H2-CTS2

MCS-7845-I2-CTS2

1.6.0, 1.6.x


Table 2 shows the servers supported for each version of Cisco TelePresence Manager.

Cisco TelePresence Software Compatibility Matrix

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

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


Note Cisco Unified CM 8.0.1 is not supported with release CTS-Manager 1.6.x and earlier releases.


What New in this Release

This section describes new and changed information in Cisco TelePresence Manager beginning with Release 1.6.0. No new features has been introduced in releases 1.6.1 to 1.6.5.

New in Release 1.6.5:

Fixes for the following bugs:

CSCtf46535

CSCtf60552

CSCtg76975

CSCtf15500

CSCte79769

CSCtg90896

CSCtg90910

CSCtg90932

CSCsz44470

CSCtg38615

CSCtg31293

CSCtg66265

New in Release 1.6.3:

Support for NTLMv2 authentication policy for Exchange 2007 EWS is now available in this release.

Support for unlimited LDAP servers with Microsoft Exchange WebDAV and EWS environments.

New in release 1.6.x

Studio mode recording - allows an administrator to turn on global studio mode recording if all managed CTS endpoints are upgraded to the supported version. CTS is configured using the CTS UI, with a preferred recording server which would dial out to meetings, allowing the one button to push recording for the meeting

Concierge changed to Live Desk

Tentative Room Reservations - CTS-Manager now processes room reservations which are in tentative state. A tentative state implies meeting invite has been viewed by room/CTS-500 owner but not accepted yet. CTS-Manager would treat a tentative reservation as an accepted reservation

Support for MS Exchange 2003/2007 deployments using Windows 2008 platform

Enhancement Email Management - more support to email notifications on a global basis, admin can turn off or on email notifications

Hardware MIB- new hardware MIBs are supported in 1.6 release

Support for MS Exchange 2007 Web Services using FBA (Form Based Authentication)

SD Interop supported with CIF; HD Interop with CUVC 7.0 supports 720p

Support for multiple CUCM Clusters - supports One Button To Push in CUCM multi-cluster deployment. The ens user does not need to dial any special number to dial across the clusters in that CTS-Manager will formulate the numbers dialed by CTS end points to go across clusters based on CUCM configurations.

Support for multiple LDAP Domains/Forests in MS Exchange Deployments - CTS-Manager supports interacting with a maximum of 5 LDAP servers per deployment

Optional First Time Setup using the Pre-Qualifier tool

CTS-Manager Release 1.6.x Caveat Reference

Table 3 summarizes caveats found in CTS-Manager Release 1.4 to 1.6.5.

Table 3 Release Caveats and Caveats Corrected Reference 

CDETS Number
Software Release
1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5
Found in Release
Corrected in Release

CSCtj55176

1.6.5

1.7

CSCtj37423

1.6.5

 

CSCth75847

1.6.5

1.7

CSCti01542

1.6.5

 

CSCte44271

1.6.1

None

CSCth55904

1.6.5

1.7

CSCth29806

1.6.5

None

CSCtg17709

1.6.5

None

CSCth38766

1.6.5

None

CSCth41514

1.6.5

None

CSCtg66265

1.6.5

1.6.5

CSCth40762

1.6.4

None

CSCtf46535

1.6.2

1.6.5

CSCtf60552

1.6.2

1.6.5

CSCtg76975

1.6.3

1.6.5

CSCtf15500

1.6

1.6.5

CSCte79769

1.6.1

1.6.5

CSCtg90896

1.6.4

1.6.5

CSCtg90910

1.6.4

1.6.5

CSCtg90932

1.6.4

1.6.5

CSCsz44470

1.6

1.6.5

CSCtg38615

1.6.4

1.6.5

CSCtg31293

1.6.4

1.6.5

CSCtf96934

1.6

1.6.4

CSCtf63273

1.6

1.6.4

CSCtf70527

1.6.4

1.6.4

CSCtf63205

1.6.1

1.6.4

CSCtf23830

1.6

1.6.4

CSCtf34465

1.6.3

1.6.4

CSCtc74101

1.6

1.6.4

CSCtf55004

1.6.2

1.6.4

CSCtf70611

1.6.4

None

CSCte98832

1.6.3

None

CSCtf06189

1.6.3

None

CSCtf06584

1.6.3

None

CSCtf09279

1.6.3

None

CSCtf18642

1.6.3

None

CSCtf28688

1.6.3

None

CSCtd57073

1.6.1

None

CSCtd72972

1.6.1

1.6.2

CSCtd76058

1.6.1

None

CSCtd79345

1.6.1

None

CSCtd99840

1.6.1

None

CSCte25973

1.6.1

None

CSCte07818

1.6.2

None

CSCte64866

1.6.x

None

CSCtg31979

1.6.x

1.6.3

CDETS Number
Software Release
1.6
Found in Release
Corrected in Release

CSCte15533

1.6.1

None

CSCsz60047

1.6.0

1.6.0

CSCsz80533

1.6.0

None

CSCta97404

1.6.0

1.6.0

CSCtb37936

1.6.0

1.6.0

CSCtb45402

1.6.0

None

CSCtb74377

1.6.0

1.6.0

CSCtc04031

1.6.0

1.6.0

CSCtc26855

1.6.0

1.6.0

CSCtc33539

1.6.0

1.6.0

CSCtc39950

1.6.0

None

CSCtc42007

1.6.0

1.6.1

CSCtc44339

1.6.0

None

CSCtc49952

1.6.0

None

CSCtc52790

1.6.0

None

CSCtc57772

1.6.0

None

CSCtc57776

1.6.0

None

CSCtc59787

1.6.0

None

CSCtc62358

1.6.0

None

CSCtc67046

1.6.0

None

CSCtc68154

1.6.0

None

CSCtc71652

1.6.0

None

CSCtc71672

1.6.0

None

CSCtc72044

1.6.0

None

CSCtc74099

1.6.0

None

CSCtc77284

1.6.0

1.6.1

CSCtc77297

1.6.0

1.6.1

CSCtc77494

1.6.0

1.6.1

CSCtc77744

1.6.0

None

CSCtc80656

1.6.0

1.6.1

CSCtc83234

1.6.0

1.6.1

CSCtc85636

1.6.0

1.6.1

CSCtc96559

1.6.0

None

CSCtd11066

1.6.0

1.6.0

CSCtd14526

1.6.0

None

CSCtd57073

1.5, 1.6

1.6.1

CSCte64866

1.6.x

None

CDETS Number
Software Release
1.5.1
Found in Release
Corrected in Release

CSCtf34917

1.5.1

1.6.4

CSCsy30732

1.5.1

1.6

CSCsy91066

1.5.1

1.6

CSCtc80248

1.5.1

1.6

CSCtd57073

1.5

1.6.1

CSCsz33199

1.5, 1.5.1

1.6

CSCsz59287

1.5.1

1.6

CDETS Number
Software Release
1.5.0
Found in Release
Corrected in Release

CSCtf06584

1.5.x

None

CSCtb30112

1.5, 1.5.1

1.5.2, 1.6

CSCsr78238

1.4

1.5.1

CSCsu71389

1.4

1.5.1

CSCsv02902

1.4

None

CSCsv77664

1.4

1.5.1

CSCsw15356

1.5

1.5.1

CSCsw98468

1.5

None

CSCsx18364

1.4

1.5.1

CSCsy24454

1.5

1.5.1

CSCsy41859

1.5

1.6

CSCsy88040

1.5

1.5.1

CSCsy91600

1.4

1.5.1

CSCsz12941

1.5

1.6

 

Software Release

1.4.0

CDETS Number

Found in Release

Corrected in Release

CSCte19489

1.4

1.7


Caveats for CTS-Manager Release 1.6.5

CSCtj55176

Symptom: CTS-Manager fails to authenticate with Unified CM.

Conditions: CTI Service is not running on the publisher node of the Unified CM cluster.

Workaround: Start the CTI Service on the publisher nodeof the Unified CM cluster.

CSCtj37423

Symptom: When CTS-Manager has been configured in Microsoft Exchange Web Services mode, modifying the time of an individual occurrence of a recurring meeting could create a duplicate occurrence in CTS Manager.

Conditions: An individual occurrence of a recurring meeting is modified in the Exchange server to have a different start time.

Workaround: None.

CSCth75847

Symptom: Question mark shows as status for some future scheduled meetings.

Conditions: Occurs when some future meetings are scheduled.

Workaround: None.

Fixed: 1.7.

CSCti01542

Symptom: Prequalification test for Microsoft Exchange EWS fails mailbox quota test.

Conditions: If the CTS-Manager user logon name is different from the LHS of the email ID and there is no matching email ID for the user.

Workaround: Add a secondary email ID that uses the CTS-Manager logon name as the LHS of the email ID append with the SMTP domain.

CSCti01542

Symptom: Prequalification test for Microsoft Exchange EWS fails mailbox quota test.

Conditions: If the CTS-Manager user logon name is different from the LHS of the email ID and there is no matching email ID for the user.

Workaround: Add a secondary email ID that uses the CTS-Manager logon name as the LHS of the email ID append with the SMTP domain.

CSCth55904

Symptom: CTS-Manager shows room synchronization failure in Microsoft Exchange WebDAV mode. System log files show it is unable to perform room synchronization due to an unexpected meeting returned back from the Microsoft Exchange Server. This could manifest to another system where a meeting deleted from the room calendar does not get deleted from CTS-Manager.

Conditions: This occurs if the room calendar does not contain any scheduled meeting during a specific time period.

Workaround: Create a monthly recurring meeting that starts in the past and ends 6 or more months in the future.

CSCth41514

Symptom: Verifying the connection to the LDAP server fails.

Conditions: Domino Calndar server is using secure bind method and the port is changed from one to another.

Workaround: Close and reopen the PreQualification tool.

CSCth29806

Symptom: One or more recurring meeting instances, deleted from calendar are not deleted from the CTS-Manager database.

Conditions: This issue occurs if the recurring meeting has one or more instances modified (subject, room and/or time) and the whole recurring meeting series is deleted.

Workaround: The workaround is to create a future recurring meeting with the same set of rooms as the original meeting that was not deleted from the CTS-Manager database.

CSCtg17709

Symptom: CTS-Manager fails to communicate with Cisco Unified Communications Manager (CUCM) displaying the following error message: "Failed to initialize the Trust Manager for CCM Adapter:java.io.IOException: stream does not represent a PKCS12 key store java.io.IOException: stream does not represent a PKCS12 key store".

Conditions: CTS-Manager upgrade from release 1.5 to release 1.6.

Workaround: None.

CSCth38766

Symptom: When the system is loaded with a very large number of meetings, TelePresence Engine may fail to save the resource reservation records for some meetings in the database during first-time startup.

Conditions: This may happen when CTS-Manager is syncing a large number of meetings for the first time along with meeting deletions and modification at the same time.

Workaround: Maintenance cycle will fix this issue. Meeting modification specific meeting will fix this issue.

CSCtg66265

Symptom: The Intercompany Access Number in the confirmation email for an intercompany meeting has a period following the country code. This is not an E164 format.

Conditions: In order for CTS-Manager to evaluate the country code of origin separately from the E164 dial number, the user must provide the E164 number beginning with the country code followed by a "." and the local phone number. Example:123.123455555

Workaround: None.

Caveats for CTS-Manager Release 1.6.4

CSCth40762

Symptom: CTS-Manager PreQualification Assistant doesn't work due to unsupported domain version.

Conditions: Using LDAP with CTS-Manager in an environment where the domain controller is running Windows 2008 R2 OS

Workaround: None.

CSCtg31293

Symptom: Clicking Scheduled Meeting Details opens a very small web browser window.

Conditions: When using the IP address of the CTS-Manager to launch the web UI.
e.g. https://<server ip address>

Workaround: Use the DNS name of CTS-Manager to launch the web UI.
e.g. https://<server name>

Fixed: 1.6.5

CSCtg38615

Symptom: Attempts to log in to CTS-Manager causes a SocketTimeoutException error. Out of memory is noticed in TE logs.

Conditions: Unknown.

Workaround: Restart CTS-Manager.

Fixed: 1.6.5

CSCtg90932

Symptom: Microsoft Exchange calendar sync with more than 850 rooms, takes too long and needs to be optimized.

Conditions: Large database.

Workaround: None.

Fixed: 1.6.5

CSCtg90910

Symptom: Restarting CTS-Manager with more than 850 rooms crashes CTS-Manager.

Conditions: Large database.

Workaround: None.

Fixed: 1.6.5

CSCtg90896

Symptom: Discovery of more than 850 rooms takes more than 2.5 hours which is significantly more than the typical 30 minutes for this load.

Conditions: Codec devices version 1.6.4, 1.6.3, and possibly all 1.6.x.

Workaround: None.

Fixed: 1.6.5

CSCtf70611

Symptom: Adding rooms to and deleting rooms from a meeting in the calendar are incorrectly displayed in the Cisco TelePresence Manager UI.

Conditions: Modifying rooms in the calendar for a TelePresence meeting that is in progress.

Workaround: None.

CSCtf70611

Symptom: Adding rooms to and deleting rooms from a meeting in the calendar are incorrectly displayed in the Cisco TelePresence Manager UI.

Conditions: Modifying rooms in the calendar for a TelePresence meeting that is in progress.

Workaround: None.

Caveats for CTS-Manager Release 1.6.3

CSCtg76975

Symptom: In Microsoft Exchange EWS deployment, meeting deleted from room calendar is still showing in CTS-Manager.

Conditions: Unknown.

Workaround: None.

Fixed: 1.6.5

CSCtf55004

Symptom: Scheduled multi-point meeting gets rejected due to insufficient MP resource.

Conditions: The scheduled meeting time overlaps with other existing meeting.

Workaround: None.

Fixed: 1.6.4

CSCte98832

Symptom: Meeting is not downloaded to phone.

Conditions: Room is added to a meeting while in progress.

Workaround: None.

CSCtf06189

Symptom: Time zone information is shown with null value on Scheduled Meeting page.

Conditions: N/A.

Workaround: None.

CSCtf06584

Symptom: CTS-Manager throws error while uploading CAPF certificate.

Conditions: This problem happens when CTS-Manager was downgraded from 1.6.x version to 1.5.x version.

Workaround: None.

CSCtf09279

Symptom: Live Desk user cannot login to CTS-Manager.

Conditions: Live Desk user is part of a group in a peer domain or additional domain.

Workaround: Move the Live Desk user to local domain.

CSCtf18642

Symptom: Switch version fails after upgrade.

Conditions: Special characters like single quotes are entered in text to be displayed in the email field.

Workaround: Remove the special characters and upgrade again.

CSCtf28688

Symptom: Test connection works fine for Pre-Qualification Assistant tool but failing on CTS-Manager.

Conditions: This problem happens when CUCM is running in secure (mixed) mode and "CTI Secure Connection" role is added to the application user profile.

Workaround: Remove "CTI Secure Connection" role from the application user profile.

CSCtf34465

Symptom: Discovery remains in starting state.

Conditions: Add Cisco Unified Call Manager 8.0.x.

Workaround: None.

Fixed: 1.6.4

Caveats for CTS-Manager Release 1.6.2

CSCtf46535

Symptom: No meeting information in CTS-Manager after upgrading from 15.x to 1.6.x.

Conditions: Domino super user has LDAP DN format name.

Workaround: None.

Fixed: 1.6.5

CSCtf60552

Symptom: Whenever a meeting is created after March 28th (the day when the UK changes from GMT to BST and applies DST), the email notification sent from CTS-Manager displays the wrong time (one hour earlier).

The meeting in the OWA calendar as well as the meeting details of the CTS-Manager web UI (Support > Scheduled Meetings) both have the correct time.

It's only a cosmetic issue with the meeting notification received by the user. This, however, may confuse them.

Conditions: - Microsoft Outlook 2007 SP1, version: 08.01.0240.006

- CTS-Manager 1.6.2.0 (64)

- User scheduling the meeting is in EU/London time (GMT) timezone.

- Scheduled meeting time is during UK Daylight Saving Time (DST) (British Summer Time).

For GMT DST starts on Sunday, March 28, 2010 at 1:00 AM local standard time and ends on Sunday, October 31, 2010 at 2:00 AM local daylight time.

Workaround: None.

Fixed: 1.6.5

CSCte07818

Symptom: DB restore to a different server can cause login failed with, "System is being maintained. Try again later," and never recover.

Conditions: DB didn't initialize successfully.

Workaround: Restart DB and restart server.

CSCte64866

Symptom: Test connection fails for Exchange installed using EWS.

Conditions: Super user's AD domain and SMTP email domain are different. Only windows authentication is enabled in IIS for EWS.

Workaround: Use AD domain without the .com in the domain name field on Exchange page. Mailbox quota will say unable to get info though.

CSCtg31979

Symptom: Multi-forest LDAP support needs to be expanded.

Conditions: Can't add more than one LDAP server for Microsoft Exchange WebDAV and EWS.

Workaround: None.

Caveats for CTS-Manager Release 1.6.1

CSCtd78813

Symptom: Adding a Cisco Unified CM server with a secure profile cause the Test Connection command to fail, displaying the following message: 'Unable to create provider null'.

Conditions: Unified CM server has no ceritificate.

Workaround: When adding a Cisco Unified CM server with a secure profile in CTS-Manager add a certificate for that Unified CM server.

CSCte15533

Symptom: Changing the IP address of a secure Cisco Unified CM requires CTS-Manager to be resecured.

Conditions: Enivironment contains multiple Unified CM servers.

Workaround: IP address must be used as the identifier for each Unified CM server in environments which have multiple Unified CM servers. Hostname cannot be used because CTS-Manager must also support non-DNS enviroments.

CSCte15533

Symptom: Cisco Unified CM publisher goes into error mode.

Conditions: Subscriber is deleted from the Cisco Unified CM and discovery is triggered on the publisher with CTI running on both publisher and subscriber.

Workaround: When removing one node from cluster, it's suggested to restart RisDC and AMC services on all nodes.

CSCte79769

Symptom: After deleting a room some meetings in that room are not removed from the CTS-Manager database.

Conditions: CTS-Manager was down or had network connectivity problems when the room deletion occurred and lost its connection to the Microsoft Exchange server.

Workaround: None.

Fixed: 1.6.5

CSCtf63205

Symptom: CTS-Manager web UI login by Live Desk group members or the Admin group members unsuccessful.

Conditions: Unknown.

Workaround: Unknown. System may recover by itself after some time.

Fixed: 1.6.4

CSCtd57073

Symptom: Test Connection with complex password will pass for a secure CUCM, but will fail in the runtime of Discovery. Once the password is changed and if Discovery is kicked off, Discovery will be OK showing all the rooms, but the CUCM server will show error status in UI.

Conditions: Secure CUCM profile with complex password.

Workaround: Change the password to avoid complex characters do a Test Connection, save and restart CTS-Manager.

CSCtd72972

Symptom: When a user tries to convert an intercompany recurrent meeting from one type of intercompany to another type of intercompany, i.e., hosted type to hosting type (type maps on UI to ->Another company option to Our company option) or vice versa. The dialog to apply the settings provide user with both the options, i.e., apply to all the future instances and apply to this instance.

Conditions: Both of the options of intercompany, our company type and another company type are enabled globally in the enterprise and user is trying to convert the recurrent meeting from one type of intercompany to another.

Workaround: User must always choose in this type of conversion the option to apply all and not the option to apply to this instance.

Fixed: CTS-Manager Release 1.6.2

CSCtd76058

Symptom: Pre-Qualification Assistant tool and CTS-Manager Retrieve mailbox quota information failed even with the quota set as recommended.

Conditions: This occurs if the userID and display name are the same for a user in Domino.

Workaround: None, other than ignoring this particular failure message

CSCtd79345

Symptom: Discovery status is shown "OK" but the Test Connection is failing.

Conditions: This happens with a secure CUCM which was added to CTS-Manager using an application user profile which did not have "CTI secure connection" role and later this role was added to the application user profile.

Workaround: Restarting CTS-Manager will fix this problem.

CSCtd99840

Symptom: Test connection in discovery page is ok but syslog shows CTI adapter error.

Conditions: A complex password is used for the appuser in CUCM for ex: starting with a special character

Workaround: Change the password to not start with a special character. Restart CTS-Manager.

CSCte25973

Symptom: Pre-Qualification Passes Unified CM test but CTS-Manager fails.

Conditions: A complex password is used for Cisco Unified CM appuser

Workaround: Change the Unified CM password to a simple one. Restart the Pre-Qualification Assistant tool.

Caveats for CTS-Manager Release 1.6

CSCsz44470

Symptom: Manual version switch fails after upgrade.

Conditions: Upgrade is done with "automatically switch version after upgrade" set to No. After upgrade is done, CTS-Manager is restarted before the version is switched.

Workaround: Upgrade again but do not restart before switching the version.

Fixed: 1.6.5

CSCtf15500

Symptom: Establishing secure IBM Domino connection does not work when a secure HTTP port is provided.

Conditions: Fresh installation.

Workaround:

- In the CTS-Manager Administration UI, select IBM Domino in the left navigation pane.

- Select secure bind method.

- Specify the port value to the normal DIIOP port configured in IBM Domino Server.

- This workaround requires normal DIIOP port to be enabled.

Fixed: 1.6.5

CSCtf96934

Symptom: Admin user not able to login... System reports that it is in maintenance mode.

Conditions: This occurs after db restore and if db did not recover.

Workaround: * It is fixed - It should not occur any more.

* In rare circumstances - if it occurs again, there is no work around.

Fixed: 1.6.4

CSCtf63273

Symptom: When looking at restore script log, it is observed that it is trying to delete a row from db matching a filename "07.23.10.tar.gz" or "CTSMan_db_backup....03-27-". For both of them, it is throwing errors.

Conditions: The reason is, db output is wrapping long filenames into two lines and hence, they are broken in any single line. They need to be concatenated to form valid filenames and only then, operation should be attempted.

Workaround: None.

Fixed: 1.6.4

CSCsz60047

Symptom: CTS-Manager/CTMS/CTRS won't create a default snmp "admin" user for fresh installation.

Conditions: All the customer created, modified snmp users and trap destinations will still be migrated. However, system created default "admin" user with default password, "snmppassword", unchanged won't be migrated to 1.6 or later releases.

Workaround: None.

Fixed: 1.6.0

CSCsz80533

Symptom: When a Scheduled Studio mode recording call is launched and ended, the meeting doesn't show in-progress/completed on CTS-Manager web UI. CTS-Manager currently doesn't support transitioning meeting states based on Inbound call notifications. CTS gets a inbound call notification from CTRS when a studio mode recording is launched.

Conditions: Happens with studio mode scheduled recording meetings only.

Workaround: None.

CSCta97404

Symptom: A modified Single room recurring meeting instance does not show in CTS-Manager.

Conditions: This might happen if the changes are done within a few minutes of creating the meeting. Sometimes the Exchange doesn't send out event when an instance date is changed.

Workaround: Users can update the meeting instance to reflect the correct request.

Fixed: 1.6.0

CSCtb37936

Symptom: When use MS Exchange 2007 FBA (Form Based Authentication) and connect to CTS-Manager version 1.4, the MS Exchange status on CTS-Manager still shows status as OK.

Conditions: CTS-Manager version 1.4 does not support the Exchange 2007 FBA. It should show the exchange status in Error, not OK status.

Workaround: None

Fixed: 1.6.0

CSCtb45402

Symptom: When pull out redundant power cord from PS2, a trap isn't generated for 7835I2 server.

Conditions: When the redundant power cord is pulled from PS2.

Workaround: None

CSCtb74377

Symptom: Meeting does not show up in CTS-Manager Web UI nor is it pushed to the phone UI.

Conditions: Room mailbox attending the meeting has been switched between auto-accept mode and manual mode.

Workaround: Manually re-accept the meeting again.

Fixed: 1.6.0

CSCtc04031

Symptom: Upgrade from 1.4 to 1.6 with Exchange secure bind failed - certificate not found.

Conditions:

1. Ex2007 connected to CTS-Manager with secure bind method

2. Re-install Ex2007 server

3. Get the new certificate from Ex2007, and connect with CTS-Manager 1.4 status OK.

4. Upgrade CTS-Manager to 1.6, the secure connection between Exchange and CTS-Manager is in Error state.

Workaround: Delete the certificate and re-load it. The user needs to delete the old certificate and upload the new certificate. Tests the connection and Apply. The connection is now OK.

Fixed: 1.6.0

CSCtc26855

Symptom: In rare cases, CTS-Manager upgrades might take up to 5 hours or more - when this happens, do not think the system is frozen during the upgrade and do not reboot during this process.

Conditions: Occasionally this happens when performing a CTS-Manager upgrade 1.5.x to 1.6.

Workaround: None.

Fixed: 1.6.0

CSCtc33539

Symptom: If the AD domain controller is null due to some configuration issue on the AD server, CTS-Manager will not work.

Conditions: CTS-Manager requires the Active Directory domain level be set to at least 2.

Workaround: AD domain level be set to at least 2.

Fixed: 1.6.0

CSCtc39950

Symptom: When Ctrl-A and Ctrl-X is used in the system settings page for any filed apply button is not enabled.

Conditions: Keyboard shortcut to select and cut is used.

Workaround: Click in the field and remove the content by backspace or delete buttons.

CSCtc42007

Symptom: In CTS-Manager Web UI, the room subscription appears in error.

Conditions:

1. In CTS-Manager Web UI under Exchange configuration settings, Admin specified an account that does not have valid permissions on the room that is in question.

2. Admin changed the account specified in Exchange configuration settings to an account that has valid permissions on the room that is in question.

Workaround: Using CTS-Manager Web UI, resynchronize the room in question.

Fixed: 1.6.1

CSCtc44339

Symptom: One of the TelePresence room goes into subscription error and sync error when email IDs of 2 CTS-rooms are inter-changed and re-discovered.

Conditions: This happens when email IDs of 2 CTS-rooms are inter-changed and then a Discovery is performed.

Workaround: Perform a manual re-sync on the TelePresence room.

CSCtc49952

Symptom: When Pre-Qualification Assistant is uninstalled, it is not removed from the start menu.

Conditions: Pre-Qual uninstall.

Workaround: The start menu item needs to be manually deleted.

CSCtc52790

Symptom: Moving CTS from one call Manager to other causes custom data from that meetings to be lost and triggers emails associated with meetings belonging to that room.

Conditions: This happens when CTS device is moved from one device to the other and running Discovery on clusters.

Workaround: It is recommended to move the room from one cluster (C1) to another cluster (C2) and run Discovery on both clusters back to back. If the operation is not performed back to back, whenever they resume, it is recommended to run Discovery on the clusters again. First on C2 as it belongs first and then on C1, remove the device from profile and Discover again. Otherwise the custom data is lost.

CSCtc57772

Symptom: When the CTS-Manager is configured in Microsoft Exchange Web Service (EWS) mode, if there is any room shown with subscription error, performing manual synchronization on that room does not fix the subscription error.

Conditions:

1. CTS-Manager is configured with Microsoft Exchange Web Service (EWS) mode.

2. CTS-Manager fails to establish a subscription to a room mailbox.

Workaround: Wait for 20 minutes. The CTS-Manager EWS Adapter has a built in logic to detect subscription error and will re-established room subscription every 20 minutes.

CSCtc57776

Symptom: When Pre-Qualification Assistant is uninstalled, it is not removed from the start menu.

Conditions: Pre-Qual uninstall.

Workaround: The start menu item needs to be manually deleted.

CSCtc59787

Symptom: The MCU>CUCM status does not refresh by itself. To see the latest updated status, clicking on the Refresh button is required

Conditions: On MCU and CUCM views if any change is made such that status for the devices change from ok-error etc, the change is not displayed unless user clicks Refresh, i.e., status change is not detected automatically.

Workaround: Clicking on the Refresh button updates the status to display the correct status of the devices.

CSCtc62358

Symptom: Sometimes an unsubscribed room is still shown with a meeting in the meeting view

Conditions: On a studio mode enabled CTS-Manager server, down grade one of the CTS devices to 1.5 version. Then initiate a discovery process on CTS-Manager.

Workaround: None.

CSCtc67046

Symptom: Pre-Qualification dat. file default option does not become the default during optional FTS.

Conditions: If any server other than the first LDAP configured in Pre-Qual is setup as default, using the radio button option.

Workaround: Setup Pre-Qualification with the default LDAP that needs to be used as the first one in Pre-Qualification Assistant tool.

CSCtc68154

Symptom: CTS-Manager Pre-Qualification tool allows adding of multiple LDAP servers for testing connectivity and authenticating scheduler email ID. It doesn't allow the tests to be run until all the servers have details on the scheduler username and password.

Conditions: This occurs when multiple LDAP servers are specified for testing (in Exchange deployment).

Workaround: The scheduler details need to be specified in all the LDAP servers. The LDAP UI interface allows adding of LDAP server details. This includes the scheduler username and password. The scheduler username is valid for all the LDAP servers, however, there is only one scheduler username which needs to be authenticated.

CSCtc71652

Symptom: While a meeting is in progress across 2 call manager clusters, from one of the TelePresence rooms launch Live Desk. If Admin of CTS-Manager has been logged in already and if the UI times out after certain time due to inactivity and admin logs back in notice that starting from current inprogress meeting all the other future meetings have "?" icon displayed.

Conditions: Intermittent problem.

Workaround: Refresh browser and logon again.

CSCtc71672

Symptom: Meeting which is in progress state does not appear when Need-help filter is selected on Scheduled Meeting view.

Conditions: If a meeting is in progress state, the meeting is not displayed when filter to display meetings on scheduled meetings view is set to mode: Need-help. The Need-help filter is a room associated criteria and not meeting associated. The meeting displayed are for all current scheduled and future. Hence, the meeting which is already started is not filtered in meeting view.

Workaround: To see the meeting, set the filter to mode All and use room name in room filter to see the meeting.

CSCtc72044

Symptom: During Optional FTS using Pre-Qualification Assistant dat. file shows no LDAP data.

Conditions: On Pre-Qual data for MS Exchange connection, logon name value is not added.

Workaround: Enter the logon name for MS Exchange connection in Pre-Qual and regenerate the dat. file and use this when performing the optional FTS.

CSCtc74099

Symptom: The algorithm to select CTMS based on affinity is broken. Normally, resources needed for meetings are allocated on the CTMS that is closest to scheduled rooms. But now they are all allocated on a fixed CTMS which is not closest to the scheduled rooms. When that CTMS runs out of available resources, then the algorithm picks the next CTMS which is also not the closest to scheduled rooms. When a CTS endpoint with 30fps capacity is part of a scheduled MP meeting CTS-Manager will calculate the segment count based on 30fps resource usage which is 4 segments for that CTS when it joins a meeting. CTS-Manager doesn't downgrade the 30fps resource capability to 5fps if the other participants are at 5fps. If there are no resources available for 30fps participants, CTS-Manager marks the meeting in error.

Conditions: Whenever CTMS resources are needed (e.g. multipoint meetings, WebEx enabled meetings), this problem would occur. A 30fps presentation capability Codec present in MP call

Workaround: Critical meetings can be manually migrated from the chosen CTMS to another CTMS that is closer to scheduled rooms. Have enough segments on CTMS to allocate resources.

CSCtc77284

Symptom: Room filter shows all rooms for error filter even if they are not in error.

Conditions: Filter error rooms.

Workaround: None.

Fixed: 1.6.1

CSCtc77297

Symptom: CTS-Manager Administration UI reports Exchange Server 2007 version 8.2.176.2 as not supported in System Log page.

Conditions: Exchange Server 2007 is patched with SP2.

Workaround: None.

Fixed: 1.6.1

CSCtc77494

Symptom: An initial user is displayed from CLI "show snmp user" command after upgrading from 1.5.1 to 1.6.

Conditions: The migration process migrate the initial user from 1.5.1 to 1.6.

Workaround: Use CLI "set snmp del user" command to delete the initial user.

Fixed: 1.6.1

CSCtc77744

Symptom: A prequal.dat file used for optional FTS (First Time Setup) has LDAP in normal mode. However, if the user tries to manually upload the certificate to enable secure mode for LDAP, the Test Connection fails.

Conditions: This will only happen in case a user using a prequal.dat file has normal bind mode and user tries to move to secure mode in case the user is attempting to configure CTS-Manager in optional FTS mode.

Workaround: The user can continue to proceed FTS using the same mode as exported in Pre-Qualification file i.e., configure LDAP in normal mode itself. After FTS, user can change the configuration to secure mode in configuration >edit LDAP view to change it to secure connection for LDAP.

CSCtc80248

Symptom: No email sent if meeting has "..." (3 dots) in the subject.

Conditions: Happens all the time

Workaround: remove the "..." from the meeting subject and send update from Outlook.

Fixed: 1.6

CSCtc80656

Symptom: If multiple CUCM clusters are added to CTS-Manager, System errors reporting failure in discover timezone info may be logged during discovering these multiple clusters after first time setup (FTS) when the clusters are added first time to the CTS-Manager.

Conditions: Condition can occur during FTS when multiple CUCM clusters are added or whenever multiple CUCM multiple clusters are added back to back within a short period time span.

Workaround: Avoid adding more than one CUCM cluster at a time. Add a cluster run discovery on that cluster before adding another CUCM cluster to CTS-Manager.

Fixed: 1.6.1

CSCtc83234

Symptom: Tentative room meetings are not processed or tentative rooms do not show up in meetings on EWS setup.

Conditions: EWS is configured on CTS-Manager.

Workaround: Daily maintenance will fix the issue for any meetings created after this, for old meetings proxy has to take action manually. A restart also fixes this issue.

Fixed: 1.6.1

CSCtc85636

Symptom: CTS-Manager Administration UI EWS Conversion Wizard confirmation page display valid room as error.

Conditions:

1. CTS-Manager is configured in Microsoft Exchange (WebDAV) mode.

2. An administrator goes to Microsoft Exchange page and click on "Configure EWS."

3. In the confirmation page of the wizard, rooms are marked as error.

Workaround: None. Simply complete the conversion wizard.

Fixed: 1.6.1

CSCtc96559

Symptom: Exchange rooms in error.

Conditions: LDAP is in starting status when CTS-Manager started after upgrade or restart.

Workaround: Restart CTS-Manager, making sure LDAP is in OK status before restarting or upgrading.

CSCtd11066

Symptom: Recurring meeting does not show up in CTS-Manager.

Conditions: Scheduler is using Entourage as client for scheduling meetings. Cisco TelePresence room may be auto-accept enabled.

Workaround: Use Microsoft Outlook for scheduling your Cisco TelePresence meetings. Entourage is not a supported client for Cisco TelePresence meetings.

Fixed: 1.6.0

CSCtd14526

Symptom: A user with full mailbox access cannot login to email link.

Conditions: A meeting is created by a user on a local disabled account mailbox, but this user does not have associated account permission.

Workaround: Login using the associated account credentials.

CSCtd57073

Symptom: The CTS-Manager is never able to discover any rooms even though it made it through the initial set up screens. The problem has been linked to a bad password which was found in the discovery.log file. The error is also seen in the discovery rooms area of CTS-Manager. Under the CUCM section for support in CTS-Manager, the message "CTI error" appears.

Conditions: The password for the CTS-Manager account is created on the CUCM. The password is 8 characters long and started with a special character, i.e., "=".

Workaround: Don't use a special character as the first entry for a password.

Caveats for CTS-Manager Release 1.5.1

CSCtf34917

Symptom: CTS-Manager email showing Etc/UTC time zone instead of scheduler's time zone. The workaround by scheduling a recurring meeting for CTS-Manager to cache the scheduler's time zone didn't work.

Workaround: Use user preference when login to CTS-Manager email link.

No workaround if URL link in email is removed, unless the scheduler happens to be in the live desk group or admin group in Access Management.

Fixed: 1.6.2

CSCsy30732

Symptom: SNMP trap will be delayed by 40 seconds if a power cord is removed from an HP server.

Conditions: Always - if you remove and plug power cord back in within less than 30 seconds, you may not receive a trap to indicate there was a power change.

Workaround: None

Fixed: 1.6

CSCsy91066

Symptom: After applying changes on Discovery or Exchange page, system never comes up.

Conditions: Unknown.

Workaround: The server manager needs to be started from Admin CLI or system needs to be physically power cycled.

Fixed: 1.6

CSCsz33199

Symptom: The upgrade from 1.5 to 1.5.1 will fail if the subnet mask is changed to use 000 instead of 0 in the field.

Conditions: On CTS-Manager 1.5 UI, the admin changes the subnet mask to use 000 instead of 0 in the field, for example, from 255.255.252.0 to 255.255.252.000. The upgrade to 1.5.1 will fail.

Workaround: The admin changes the subnet mask back to have 0 instead of 000 in the field. The upgrade will be successful after that change.

Fixed: 1.6

CSCsz59287

Symptom: Field Mapping data is blank either partially or completely.

Conditions: This is possibly a timing issue, as it is an intermittent problem.

Workaround: Go back to previous pages, change any value and proceed with FTS.

Fixed: 1.6

Caveats for CTS-Manager Release 1.5

CSCtb30112

Symptom: Certain IBM RAID driver versions can cause instability in the RAID environment and lead to hard drives being marked as Read-Only.Since Write access to the RAID array is required with TelePresence Applications, this problem can prevent critical files from being written to the array and eventually can cause a service outage.

Conditions: Affected servers using one of the affected versions may suddenly experience a loss of service. User may get denied access to admin CLI or web UI. System performance may suddenly become sluggish and service will be interrupted. Servers affected are MCS-7835-I2-xxx, MCS-7845-I2-xxx.

Workaround: None. Must perform a software upgrade to version 1.5.2 or 1.6.0

Fixed: 1.5.2, 1.6

CSCsr78238

Symptom: Authentication fails from CTS-Manager to Cisco Unified CM after upgrading Cisco Unified CM version.

Conditions: After Cisco Unified CM is upgraded to a new version, the new version certificate needs to be uploaded to CTS-Manager. This is due to storing the certificate in Java keystore.

Workaround: If the certificate already exists, the only other option in uploading a valid certificate is to delete the existing certificate with the same name and then reload the certificate.

Fixed: 1.5.1

CSCsu71389

Symptom: CTS-Manager reports an error for one or more CTS endpoints. The error may report that this system has a duplicate directory number assigned to it. Cisco Unified Communications Manager does not report a corresponding configuration error for the same Cisco TelePresence System.

Conditions: The directory number used for the stated CTS endpoint was previously used for a different endpoint. Everything else with respect to the Cisco Unified Communication Manager profile and configuration for this system is correct.

Workaround:
1. Log into Cisco Unified Communications Manager as an administrator. Navigate to the page where the application (appuser) user credentials for Cisco Unified CM used by Cisco TelePresence Manager are specified. Take the CTS endpoint (codec) and the associated IP phone out of this profile.

2. Replace the IP phone model 7975 with that of model 7970 in the room.

3. Navigate back to Unified CM and create a new device profile for the new 7970 IP phone.

4. Allocate a new, previously unused, directory number for the CTS endpoint and the new phone, and modify the respective configuration pages in Unified CM with the new information.

5. Add the new IP phone and the CTS endpoint back to the application user (appuser) used by CTS-Manager.

6. Wait for 15 minutes to allow the new configuration to be set.

7. Log into CTS-Manager and trigger a room discovery again. Alternatively, wait for 24 hours and the system will discover the new device automatically.

Further Description: This error is due to incorrect handling of data when the Unified CM administrator deletes a device or reassigns different DNs to existing devices.

Fixed: 1.5.1

CSCsv02902

Symptom: The status for a completed Cisco TelePresence meeting is incorrectly shown as "in progress" or "no-show" in CTS-Manager.

Conditions: CTS-Manager loses IP connectivity with one or more CTS endpoints just before or after a meeting starts. The meeting has ended before it regains this IP connectivity back.

Workaround: Wait for up to 24 hours after the meeting ends and IP connectivity is again regained with all devices in the meeting. Check the status for the meetings again. The meeting status is automatically updated by the Cisco TelePresence Manager.

Further Description: CTS-Manager determines and displays the status of meetings using "meeting start" and "meeting end" notifications generated by a CTS endpoint, Cisco TelePresence Multipoint Switch and/or other Cisco TelePresence component. If any device participating in, or scheduled to participate in, a call either loses connectivity with CTS-Manager or is restarted, one or more such notifications may be missed resulting in this erroneous state. CTS-Manager resynchronizes status for each meeting with each device once a day which should reconcile any such status errors.

If a meeting is displayed as a "no-show," it might not be auto corrected.

CSCsv42242

Symptom: Customer tried to schedule meetings for 24 months in advance. Scheduling failed.

Conditions: Cannot schedule meeting beyond 12 months time frame. This is the design limitation in Cisco CTS-Manager.

Workaround: None

Fixed: 1.5.1

CSCsv77664

Symptom: CTS-Manager pop up is missing the radio button to click Yes/No when a meeting organizer logs into CTS-Manager from a Confirmation email and modifies a recurring meeting.

Conditions: When the browser computer's Display settings has the DPI setting set to "Custom settings" with a larger font size.

Workaround: Select "Normal size (96 DPI)" for Control Panel->Display->Settings->Advanced->General->DPI settings. Your computer will restart after changing the settings.

Fixed: 1.5.1

CSCsw15356

Symptom: Meetings with errors are not displayed when the Scheduled Meetings report is filtered by the Error status.

Conditions: Upgrading from CTS-Manager 1.4 to 1.5.

Workaround: A meeting organizer or CTS-Manager Administrator can trigger an update for the missing meetings to correct meeting state. Alternatively, use "All" option to view meetings with errors.

Fixed: 1.5.1

CSCsw98468

Symptom: CTS-Manager is configured with Lightweight Directory Access Protocol (LDAP) port 389 against Active Directory. When the port is modified to 3268, the CTS endpoints in a second domain do not sync up and users in the second domain are not authenticated.

Conditions: This occurs when CTS endpoints exist in a second domain.

Workaround: Restart CTS-Manager.

Further Description: This issue occurs when LDAP port 389 resolves objects local to the Active Directory domain. Changing to the global catalog port resolves objects in other domains. However, since the current connections are already generated with port 389, the objects are not retrieved until CTS-Manager is restarted.

CSCsx18364

Symptom: The ampersand character "&" is not accepted by the LDAP User Container fields in the first time set-up.

Workaround: Move the necessary user container(s) up to a level in the LDAP tree where no special character is used in the CN or OU name, or do not specify a user container and click Append Default Context.

Further Description: In addition to the ampersand, there can be other characters (such as, . + < > etc) which can potentially cause similar authentication failures.

In order to prevent this for any DN string that is entered either in Admin UI or pre-qualifier tool, the DN must be entered as it is actually stored in the directory. Consider the following scenario:

A directory admin creates a container name Sales, Marketing under acme.com domain with an AD admin console. On the admin console the string will look like Sales, Marketing. However, LDAP uses the comma character as a tree delimiter. LDAP stores the DN of that container as cn=Sales\, Marketing,dc=acme,dc=com. This is the string that must be entered in CTS-Manager and pre-qualifier tool.

There are many more LDAP reserved characters. As a general rule, it is typically recommended to avoid having to specify objects containing special characters which can be interpreted incorrectly by either the browser or LDAP. If it is absolutely required, look at how the data is represented in LDAP and enter the value as is.

Fixed: 1.5.1

CSCsx97469

Symptom: After system restart, the database does not come up when the hostname and IP address are changed for CTS-Manager using admin CLI commands set network hostname and set network ip. The system becomes unusable.

Conditions: When the hostname and IP address are changed for CTS-Manager using admin CLI commands set network hostname and set network ip.

Workaround: None

Fixed: 1.6

CSCsx97676

Symptom: When security certificate is uploaded, and an error is encountered, currently CTS Manager shows only a single error message from the resource bundle. However, this may not be verbose enough for the administrator.

Conditions: This happens when there is a failure in loading LSC.

Workaround: Try to upload LSC with different name after duly deleting the existing certificate (if required) Expected Resolution:

Fixed: 1.5.1

CSCsy24454

Symptom: CTS Manager performs short name to user/resource document resolution. The name to document resolution is done by performing a full text search against Domino. Once a document is obtained, CTS Manager will fetch some necessary attributes and cache that information. Subsequent name resolution will consult the value of this cache.

Conditions: A full text search operation might fail with an error, "NotesException: Notes error: Maximum allowable documents exceeded for a temporary full text index" on an unindexed Domino directory database. If you encounter this issue, there are several workarounds.

Workaround:

1. Indexed the Domino Directory (names.nsf)

2. Increase the parameter Temp_Index_Max_Doc that limits the number of records to search. This value needs to be set to a value higher than the number of user or resource whichever is higher. For more information on this parameter and other related parameters, check the link:

http://www.ibm.com/developerworks/lotus/documentation/notes-ini/ptot.html

3. If option 2 is not practical since it might impact other applications, it is recommended to install a new instance of Domino server for CTS Manager and set this parameter on that particular server.

Fixed: 1.5.1

CSCsy41859

Symptom: Upgrade from any previous version to 1.5 failed, - will not switch to 1.5 when the upgrade process completed.

Conditions: This is caused by a sentence in Concierge Description Field broken by a Carriage Return or line feed, sometimes referred to as <CR>.

Workaround: 1. Proactive Action: Before starting the upgrade, change the description into one line sentence without breaking it by <CR> between words (do not hit return key). 2. If already upgraded and having the issue, do the same workaround as above and then do a manual switch version to 1.5.

Fixed: 1.6

CSCsy49615

Symptom: CTS-Manager would not generate confirmation or action required emails for a meeting scheduled via Microsoft Outlook.

Conditions: If a meeting subject contains special characters, i.e., Chinese fonts.

Workaround: None

Fixed: 1.6

CSCsy88040

Symptom: CTS-Manager is unable to connect with LDAP secure configured in secure mode.

Conditions: Always

Workaround: None. Use non-secure mode if acceptable.

Fixed: 1.5.1

CSCsy91600

Symptom: CTS-Manager is unable to communicate with MS-Exchange 2003/2007. Error is reported as "Certificate contains unsupported critical extensions: [2.5.29.17]."

Conditions:
1. In CTS Manager Web UI, under "System Configuration > Microsoft Exchange" page, "Bind Method" is selected as "Secure".

2. A digital certificate with security extensions viz. SubjectAltName is used.

Workaround: None. Use non-secure mode if acceptable.

Fixed: 1.5.1

CSCsz12941

Symptom: LSC generation failed.

Conditions:

CAPF User does not have the correct privileges

Incorrect Certificate Operation mode in CUCM

Incorrect Instance ID

Incorrect Authentication string

Incorrect Port or server details

Workaround: Correct the values and retry.

Fixed: 1.6

Caveats for CTS-Manager Release 1.4

CSCte19489

Symptom: PreQualification Assistant failed the connection test for the IBM Domino calendar server.

Conditions: DIIOP and HTTP ports were not set to allow anonymous access.

Workaround: Set both DIIOP and HTTP ports to allow anonymous access. In IBM Domino Administrator, go to Configuration > Ports > Internet Ports. Under the Web and DIIOP tabs in the Authentication Options section, make sure that Anonymous is selected.

Fixed: 1.7

CSCsr21292

Symptom: One or more of the following conditions are observed.

1. When a user schedules a new TelePresence meeting, the requester does not receive an email from Cisco TelePresence Manager for more than 20 minutes. CTS-Manager web UI displays (administrative privileges required) "Not available" in the email status corresponding to this meeting.

2. CTS-Manager web UI does not display one or more scheduled TelePresence meetings.

3. Cisco TelePresence Multipoint Switch's web UI does not display one or more scheduled TelePresence meetings involving three or more TelePresence rooms. Such meetings would have been created in the next 7 days.

Conditions: These symptoms have been observed very infrequently. These are typically observed when CTS-Manager manages more than 150 TelePresence rooms.

Workaround: Log in to CTS-Manager's web UI as a user with administrator's privileges. Navigate to the "System Settings->System" screen and restart the system. Wait for 30 minutes for the system to come back up (the administrative client would be logged out) and verify that the new meetings have been processed correctly.

Further Problem Description: This behavior is very infrequent. Multiple efforts to recreate this issue have not been successful. When CTS-Manager processes a significantly large amount of data in a short period of time, it results in some synchronization errors which cause these symptoms.

Fixed: 1.5

CSCsr40035

Symptom: A user creates a recurrent meeting with one or more rooms. This recurrent meeting is set without any end date.

CTS-Manager web UI displays that the last few instances of such a meeting are in error. It shows that it is awaiting more information from the calendar server (e.g. Microsoft Exchange).

Condition: These symptoms are typically observed for such recurrent meetings created with previous versions of CTS-Manager.

Workaround: The user should navigate to his/her calendar client (e.g. Microsoft Outlook) and delete all instances of such meetings. Wait for 5 minutes. Recreate the recurrent meeting with the same TelePresence rooms.

Further Problem Description: CTS-Manager does not store recurrent meetings without an end-date and certain other characteristics correctly in previous versions of this product. When the product software is upgraded to this version, this erroneous data is not auto-corrected. Deleting these previous meetings would delete such erroneous data and alleviate the issue.

Fixed: 1.5

CSCsr52514

Symptom: In CTS-Manager, under "Support > Multipoint Conference Unit", user selects MCU and clicks on "View Meetings." The "Control State" of the MCU device is "Non-Scheduled", but "Support > Scheduled Meetings" view shows one or more meetings associated with this MCU.

Conditions: 1. Cisco TelePresence Multipoint Switch's (CTMS) admin has reduced CTMS resources.

2. In CTS-Manager UI, under "Support > Multipoint Conference Unit" admin selects an MCU and clicks on "Migrate All Meetings To."

Step 2 is executed within 2 hours of step 1.

Workaround: Navigate to "Support > Scheduled Meetings" view and select the impacted meeting. Change the value for "MultiPoint Conference Unit" to another MCU and click on "Apply."

Further Problem Description: MCU resource reduction as well as migrate all operation should occur simultaneously for this problem to occur. This is a very rare condition.

Fixed: 1.5

CSCsr53939

Symptom: In CTS-Manager, under "Support > Multipoint Conference Unit," there is a MCU that is in a Non-Scheduled state; user selects the MCU and clicks on "View Meetings." Then, in "Support > Scheduled Meetings" view, one or more meetings are displayed within MCU with questions associated with them.

Conditions: 1. In CTS-Manager web UI, under "Support > Multipoint Conference Unit" there is a MCU in "Scheduled" state. User selects the MCU and clicks on "Details" and checks "Migrate All Meetings To" box and clicks on "Save."

2. There is one (or more) meeting hosted on source MCU that is selected, see the above step, such that the meeting start time is already in past but end time is in the future and the meeting is in a scheduled state (meeting is not launched yet).

Workaround: Before performing Migrate All operation, navigate to "Support > Scheduled Meetings" and make sure that for the source MCU there are no scheduled meetings whose start time is already in past but end time is in future. It is recommended to do migrate all operation in maintenance hours.

Further Problem Description: The Migrate All operation fetches only future meetings from database. It does not fetch current meetings, as a result current meetings are not migrated to target MCU.

Fixed: 1.5

CSCsr63982

Symptom: CTS-Manager restart results in resetting the Calendar window duration to default value.

Conditions: This happens when the default number of days for room and MCU calendar push is modified using the Policy Management screen. These modified numbers take effect. However upon restart of CTS-Manager, the default values are used for the calendar push.

Workaround: Triggering maintenance task, updating room schedule, or modifying the default values in CTS or Cisco TelePresence Multipoint Switch's (CTMS) policy results in pushing the calendar with the right number of days.

Further Problem Description: During CTS-Manager initialization, the default number of days for room and MCU calendar push is read from Configuration Entry instead of the Configuration policies. The Admin UI causes the Configuration policy values to be modified. When these values are modified, these are in effect until the next CTS Manager restart. However, after a restart, CTS- Manager picks these values again from Configuration Entry table instead of the Configuration Policy. The code needs to be fixed to read from the Configuration Policy table.

The remaining configuration parameters (Upcoming Alert, Early start time, etc) are properly read from Configuration Policy and are not impacted.

Fixed: 1.5

Supplemental End User License Agreement

This Supplemental End User License Agreement ("SEULA") contains additional terms and conditions for the 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, you agree to comply at all times with the terms and conditions provided in this SEULA. DOWNLOADING, INSTALLING, OR USING THE SOFTWARE 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 TO YOU AND (A) YOU MAY NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE, AND (B) YOU MAY RETURN THE SOFTWARE (INCLUDING ANY UNOPENED CD PACKAGE AND ANY WRITTEN MATERIALS)

FOR A FULL REFUND, OR, IF THE SOFTWARE 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.

Product Name

These SEULA terms will apply to the following products:

CTS-CODEC-PRIM- TelePresence Primary Codec

CTS-CODEC-PRI-G2-TelePresence Primary Codec for CTS-3200 and CTS-500

CTS-CTMS1.5-K9- Cisco TelePresence Multipoint Switch

CTS-MAN1.5-K9- Cisco TelePresence Manager

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

"Intracompany Features" are those features that are deployed within an enterprise and do not traverse a service provider network for the purpose of interconnecting and communicating to other enterprises. This does not include transport provided for communication within the enterprise allowing it to communicate to itself.

"Inter-company Features" are those features that provide support for communications between enterprises through a service provider network.

In addition to the Agreement, the following supplemental terms apply to Inter-company Features.

Multipoint encryption for Inter-company feature is available in the Software Product but you are not authorized to use it until you have been permitted to do so in the updated release notes for the Software Product, as posted by Cisco on cisco.com. Unless your use is through an authorized service provider's network, your use of such Inter-company feature prior to such authorization shall constitute a breach of the Agreement. Notwithstanding the foregoing, your use of Intracompany features shall not be restricted by these supplemental terms.

Obtaining Documentation, Obtaining Support, and Security Guidelines

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.