AppManager for Cisco Unified Communications Manager (CiscoCM) allows you to monitor clusters and resources for Cisco Unified Communications Manager environments.
This hotfix resolves specific previous issues. This document outlines why you should install this hotfix.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials Web site.
This release of AppManager for Cisco Unified Communications Manager provides the following enhancement:
Support for Cisco Unified Communications Manager 12.5: This release of AppManager for Cisco Unified Communications Manager provides support for Cisco Unified Communications Manager 12.5.
This release of AppManager for Cisco Unified Communications Manager resolves the following issues:
CiscoCM supplemental DB grooming errors that prevent deletion of old CDR and CMR: Supplemental DB continued growth of the database size without proper grooming. With this release, a parameter called PruningComplete is added to the variables table, which resolved the issue. (ENG349188)
Hanging of random CiscoCM jobs: CiscoCM module fetches credentials for every object resulting in hanging of jobs. With this release, this issue is resolved, and all CiscoCM jobs run without any hang issues. (ENG350057)
CiscoCM discovery fails: Due to invalid host FQDN usage, CiscoCM discovery fails. With this release, this issue is resolved and CiscoCM discovery is restored in Cisco Communication Manager 12.5. (ENG349526)
VoIP module uses KS instead of NQACUtil: To improve performance, with this release XML is generated using Knowledge Scripts instead of NQACUtil to improve performance. (ENG348610)
CiscoCM_CDR_CallQuality KS does not generate dynamic legend XML: With this release, this issue is resolved, and CiscoCM_CDR_CallQuality, CiscoCM_CDR_CallFailures, and CiscoCM_CDR_Query KS now generate the dynamic legend XML. (ENG348875)
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts.
This release of AppManager for Cisco Unified Communications Manager replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Cisco Unified Communications Manager has the following system requirements:
This hotfix requires the following product versions:
This service pack requires the following product versions:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computer, on all proxy agent computers, and on all console computers |
9.1, 9.2, 9.5, or later Support for Windows Server 2008 R2 on AppManager 7.x requires AppManager Windows Agent hotfix 71704 or later. For more information, see the AppManager Suite Hotfixes page. |
|
Microsoft operating system installed on all proxy agent computers |
One of the following:
|
|
AppManager for Microsoft Windows module installed on repository, agent, and console computers |
Latest agent version of 9.x. For more information, see the AppManager Module Upgrades & Trials page. |
|
Microsoft SQL Server installed on the proxy agent computer |
All listed versions enable you to create and use the Cisco CM supplemental database.
|
|
Cisco Unified Communications Manager on the computers you want to monitor |
12.5, 11.5, 10.5, 10.0, 9.1, 9.0, 8.6, 8.5, 8.0, 7.1(2), 7.0, 6.1, 6.0, 5.1, or 5.0 |
|
Microsoft .NET Framework |
4.0 or above. |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
For more information on configuration, hardware requirements, and supported operating systems and browsers, see the AppManager for Cisco Unified Communications Manager Management Guide, included in the download package.
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for Cisco Unified Communications Manager includes a managed object, qNQCiscoCM.dll, and Knowledge Scripts to discover and monitor Unified Communications Manager resources. The download package includes these release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-CiscoCM-7.6.80.0.msi, the module installer.
AM70-CiscoCM-7.6.80.0.ini, a configuration file used with the AppManager setup program.
AM70-CiscoCM-7.6.80.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-CiscoCM-7.6.80.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckCiscoCM.exe, the pre-installation check used with the AppManager setup program.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On all proxy agent computers to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install the Knowledge Scripts into local or remote QDBs. When installing to each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
Important This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for Cisco Unified Communications Manager Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
CiscoCM_PhoneInventory Knowledge Script might create unexpected entries in the inventory .csv file. When you run the CiscoCM_PhoneInventory script on a Cisco Unified Communications Manager version 10 computer, the inventory .csv file incorrectly lists device templates as phones. There is no workaround for this issue, but if you are already using the various parameters in this script to filter the inventory .csv file, you might not encounter these templates. (ENG334544)
CiscoCM_Locations Knowledge Script does not monitor Shadow or Phantom locations. This module discovers two new standard locations recently added by Cisco, Shadow and Phantom locations, and adds objects for those discovered locations to the TreeView in the Operator Console or the Navigation pane in the Control Center console. However, because neither of these new locations uses the Cisco counters that the CiscoCM_Locations script monitors, the script does not collect data or raise events for either of these new objects. (ENG330073)
Cisco Unified Communications Manager 9.x license usage is not reported correctly. Starting with Cisco Unified Communications Manager 9.0, the Cisco Enterprise License Manager tracks license usage for Cisco Unified Communications Manager, but the AppManager for CiscoCM module does not interact with this new component. As a result, the CiscoCM_LicenseUsage Knowledge Script does not accurately measure license usage in a Cisco Unified Communications Manager 9.x cluster. Also, after Discovery, Cisco Unified Communications Manager 9.x objects display "0:0" in their Cisco Node Licenses and Cisco Phone Licenses detail columns. At this time, the AppManager for CiscoCM module does not provide another means to measure Cisco Unified Communications Manager 9.x license usage, but NetIQ Corporation might add this functionality in a future release. (ENG329934, ENG330323)
The NetIQ prerequisite checker does not detect SQL named instances on 64-bit Windows operating systems. Due to a difference in the 64-bit registry hive from the 32-bit registry hive, the prerequisite checker does not detect SQL named instances on 64-bit systems. Despite this issue with the prerequisite checker, the module works as expected with these 64-bit systems. (ENG310987)
The event message after discovery fails lacks sufficient information about Security Manager credentials. If you type an incorrect name or password in Security Manager and run Discovery_CiscoCM, discovery fails. However, the event message does not mention that incorrect credentials may cause discovery to fail. Similarly, discovery fails if you do not select Extended application support in Security Manager, but the event message does not mention that leaving this option unselected in Security Manager may cause discovery to fail. (ENG309281, ENG309325)
The CiscoCM_CCM_RegisteredResources Knowledge Script also counts some registered softphones as registered resources. When X-Lite or Cisco IP Communicator softphones get registered into the Cisco Unified CallManager, the RegisteredHardwarePhones performance counter increments. As a result, the number of hardware phones monitored with the CiscoCM_CCM_RegisteredResources script also includes these softphones. (DOC311220)
The CiscoCM_SystemUpTime Knowledge Script might return an incorrect value if the monitored system has been running for over a year. The Cisco Unified Communications Manager Total CPU Time performance counter cannot monitor a system that has been running for longer than 500 days, which causes the incorrect value to occur in this module. As a workaround, you can measure uptime for a system that has been running for over 500 days by using the NetworkDevice_Device_Uptime Knowledge Script. For more information about the Network Devices module, see the AppManager for Network Devices Management Guide on the AppManager Documentation page. (ENG305411)
This release of AppManager for Cisco Unified Communications Manager includes enhancements added in previous releases.
This release provided the following enhancement:
Support for Transport Layer Security 1.2 (TLS): This release provides support for TLS 1.2 enabled environment.
IMPORTANT:Use TLS 1.2 supported version of AppManager.
Support for Microsoft SQL Server: This release supports Microsoft SQL Server 2012, Microsoft SQL Server 2014, Microsoft SQL Server 2016 and Microsoft SQL Server 2016 SP1 Express edition. For more information, see the System Requirements.
Support for Microsoft Windows Server 2016: This release supports Microsoft Windows Server 2016.
This release resolved the following issues:
MS Fails to Insert CiscoCM Discovery XML to QDB in 9.2: AM 9.2 MS is having a problem handling the CiscoCM discovery XML containing the Call Manager objects to be inserted into the QDB being sent from an agent. With this release, XML special characters are handled to generate valid discovery XML. (ENG348177)
CiscoCM_CDR_RetrieveCallRecords fails to process CMR files: CiscoCM server generates the call data records with different schema based on the CiscoCM server configuration. Since the call data record file schema is not constant,CiscoCM_CDR_RetrieveCallRecords fails to load CDR/CMR files. With this release, CiscoCM_CDR_RetrieveCallRecords loads the CDR/CMR files properly to supplement database. (ENG348421)
AXL Communication Error: With this release the CiscoCM jobs stop generating an AXL communication error event when a name is used to connect instead of the IP address. (ENG344311)
CiscoCM_HealthCheck cannot handle more than 64 services: When CiscoCM_HealthCheck is configured to monitor more than 64 services, the Cisco Call Manager only returns the first 64 services and the KS does not handle the remaining services. The remaining services raise a service not started event. With this release CiscoCM_HealthCheck handles more than 64 services by processing multiple batches of 64 services per batch. (ENG345346)
CDR_RetrieveConfigData KS not finding kbits column: When the Cisco Call Manager is behind a NAT segment or is in a split DNS configuration then CiscoCM_CDR_RetrieveConfigData KS fails with communication error (exception message: kbits column not found in any table in the query). With this release CiscoCM_CDR_RetrieveConfigData KS does not fail irrespective of Cisco Call Manager configuration. (ENG343640)
CiscoCM jobs hangs when Cisco Call Manager is unavailable: With this release the default timeout values are modified to avoid CiscoCM jobs to hang or slow down. (ENG345319)
This release provided the following enhancement:
Added CiscoCM Scalability Improvements. This release provides a performance enhancement to allow the retrieval of a configurable number of instances of a counter object within a single AXL session, as specified using a registry entry. For additional information about adding the registry entry, see Installing AppManager for CiscoCM in the AppManager for CiscoUCM Management Guide. (ENG341209,ENG343751)
CiscoCM_CDR_CallQuality generated SQL Server timeouts. The CDR table in the CiscoCM supplemental database, used by the CiscoCM_CDR_CallQuality Knowledge Script, did not have indices optimized for querying the table efficiently, which could result in timeouts. With this release, the SQL run by the CiscoCM_SetupSupplementalDb applies optimized indices to this table when run, improving the performance of CiscoCM_CDR_CallQuality. (ENG334658)
CiscoCM_SystemPerformance Knowledge Script does not create expected events. The yellow alarm condition, monitored by the CiscoCM SystemPerformance Knowledge Script, did not reflect whether a server both entered and exited a yellow alarm condition in the same interval. With this release, the datastream and event looks at the yellow alarm state at the end of the interval, and at whether the total number of yellow alarm entries increased from the previous interval. This allows very short yellow alarm conditions to be reported accurately. (ENG338759)
Unable to collect inter-location bandwidth usage. The CiscoCM_Locations Knowledge Script dropped on a specific location in the treeview and monitored bandwidth usage within that location, but not bandwidth usage to other locations (inter-location bandwidth), which left the customer without a way to monitor inter-location bandwidth. With this release, a new Knowledge Script, CiscoCM_LocationsList, allows monitoring of drops on the server object and all combinations of location bandwidth counters, including inter-location pairs. (ENG339183)
Added CiscoCM Scalability Improvements. This release provides a performance enhancement that allows the retrieval of a configurable number of instances for a counter object within a single AXL session, as specified using a registry entry. For additional information about adding the registry entry, see “Installing AppManager for Cisco Unified Communications Manager,” in the AppManager for CiscoCM Management Guide. (ENG341209)
GeneralCounter unexpectedly stopped the NetIQmc service, if run on a system with a large string of objects. With this release, the CiscoCM_GeneralCounter Knowledge Script increases the maximum size of its target object list, which monitors more objects from a single job. (ENG343060)
60-second AXL throttle timer back-off activated for non-throttling errors. This release resolves an issue in which non-throttling errors caused the timer backoff to engage, which delayed all CiscoCM messaging. With this release, when a non-throttling error occurs, an event is raised that the errors occurred while messaging to the device continues without delay. (ENG341208)
Improved handling of AXL throttling errors for scalability. When Cisco servers received more than 50 SOAP/AXL requests/second, the servers might have responded with an AXL throttling exception. This might have occurred on systems when monitoring a large number of counter entries. In this release, the retry method for SOAP/AXL errors adds an additional delay when AXL throttling is detected, which slows down the overall request rate to allow monitoring of larger systems without error. (ENG341209, ENG341210)
Removed truncation from CiscoUCM AXL communication logs. The AXL communication logs were truncated, limiting debugging for large systems. These logs no longer truncate. (ENG341207)
GeneralCounter datastreams with brackets [ ] in counter names were truncated. Counters containing square brackets in the name were not correctly displayed as datastreams. These counters now display correctly. (ENG341211)
Discovery did not resolve servers when a host file nickname (a non-domain name as second entry) was used. When using the hosts file on Microsoft Windows to include alternate names for specific IP addresses, if a host file entry contained multiple names and the second entry was a non-domain name, discovery did not resolve the matching server instance correctly and it created two copies of the server in the TreeView pane. With this release, correction of the host name lookup allows creation of only one server regardless of the number of names in the host file. (ENG343061)
CallsActive of CiscoCM_MGCP_PRI_CallActivity returns a delta value. The CallsActive datastream incorrectly returned a delta value. This was changed to an absolute (non-delta) value to better match Cisco usage of the counter. (ENG336618)
Management Group treeview items were relayed through the publisher, which could result in the AXL messaging limit being exceeded unnecessarily. With this release, messaging for objects located on subscriber servers is sent directly to those servers. (ENG341200)
AM only shows call information for SIP trunks nodes that are on CM group device pool. When SIP Trunks were monitored, only call information for nodes on the CM group device pool was queried. SIP trunks are unique in that Cisco introduced a configuration option to allow these trunks to exist outside of the CM group device pool. SIP monitoring jobs now query all devices in a given cluster when monitoring SIP trunks, including those outside of the CM group. (ENG336470)
This release provided the following enhancement:
Support for Cisco Unified Communications Manager 10.0. You can use this release of AppManager for Cisco Unity Connection to monitor Cisco Unified Communications Manager version 10.0. For more information, see the System Requirements.
This release resolved the following issue:
Discovery_CiscoCM Knowledge Script does not complete the discovery process. This release resolves an issue in which the Discovery_CiscoCM script failed to discover the complete set of associated gateways when you ran it on a cluster with a large number of MGCP or H.323 gateways. With this release, the discovery script correctly includes the complete set of gateways. (ENG330711)
Discovery_CiscoCM Knowledge Script incorrectly discovers Call Manager Group details. This release resolves an issue in which the Discovery_CiscoCM script listed incorrect values for external IP addresses of Call Manager Groups, and listed the secondary address information in the tertiary position. With this release, Discovery_CiscoCM properly displays the Call Manager Group external addresses, and lists the primary, secondary, and tertiary details in the correct positions.(ENG330929)
Data streams do not display correctly in Control Center. This release resolves an issue in which the data collected by the CiscoCM_CDR_CallFailures, CiscoCM_CDR_CallQuality, and CiscoCM_CDR_Query scripts did not display in the Control Center console. With this release, AppManager properly associates the data collected by these Knowledge Scripts with the relevant TreeView object, which enables the data to be displayed in the Control Center console. (ENG330774)
This release resolved the following issue:
CiscoCM_Locations Knowledge Script fails to generate events or create data streams. This release resolves an issue in which the CiscoCM_Locations script failed to generate events and data streams for Location objects associated with Cisco Unified Communications Manager servers version 9.0 or later. With this release, the script properly generates events and data streams for servers running version 9.0 or later. (ENG329912)
This release also added the following support:
Support for Cisco Unified Communications Manager version 9.1.
This release added the following support:
Support for Microsoft Windows Server 2012 and Windows 8. This release supports Windows Server 2012 and Windows 8 installed on the agent computers.
Support for Cisco Unified Communications Manager version 9.0.
This release also resolved the following issues:
CiscoCM_HealthCheck Knowledge Script generates an "Exceeded allowed rate for real time information" error message. This release resolves an issue in which the CiscoCM_HealthCheck script generated this error message when the monitored Unified Communications Manager reached the throttling limit set by Cisco for real-time service state queries. The script retried the failed queries twice before returning an error to the user, with no delay between retries. With this release, if the server reaches the throttling limit, the script delays retrying the queries to lessen the chance of generating the error message. (ENG326409)
CiscoCM_MGCP Knowledge Script jobs stop working when a registered server fails over. This release resolves an issue in which a registered server failed over to a different server, and the monitoring jobs for the CiscoCM_MGCP scripts running on the Registered Server object stopped working. With this release, this module dynamically determines the new registered server and prevents the jobs from failing. (ENG321652)
CiscoCM_RoleStatus Knowledge Script causes a throttling error. This release resolves an issue in which the CiscoCM_RoleStatus script caused a throttling error when multiple CallManager Groups were configured for the same primary and secondary servers. The CiscoCM_RoleStatus script also caused other CiscoCM scripts that were running at the same time to experience the same throttling errors. With this release, an update to the CiscoCM_RoleStatus script prevents these issues from occurring. (ENG324923)
Discovery_CiscoCM Knowledge Script lists the server name instead of the IP address. This release resolves an issue in which the Discovery_CiscoCM script failed when you ran it using the Comma-separated list of CallManager IP address pairs in a single NAT cluster parameter, and the specified servers were registered by server name instead of by IP address. With this release, the Discovery_CiscoCM script can discover servers using NAT translation that are registered both by name and by IP address. (ENG283421)
Some Knowledge Scripts that track call detail records do not collect data for each cluster when deployed on multiple clusters. This release resolves an issue in which the CiscoCM_CDR_CallFailures, CiscoCM_CDR_CallQuality, and CiscoCM_CDR_Query scripts did not properly collect data for each cluster when you ran one of these scripts on multiple clusters. With this release, these scripts have new data streams that properly collect data for multiple clusters. Because these new data streams do not match the data streams from previous releases, any data streams you created before this release will not match up with the data streams created with this release, even if the job remains the same. (ENG325484, DOC326227)
This release resolved the following issues:
The object details for a discovered object in the TreeView now include the internal IP address for that object. This release renames the existing Local IP Address detail of the TreeView objects to UCM Local IP Address. In addition, some objects now have an additional Device IP Address detail that refers to the internal IP address of the individual object. After you install this release, you must rerun the Discovery_CiscoCM Knowledge Script to observe the updates to the TreeView details. (ENG316859)
CiscoCM Knowledge Scripts generate an unclear error message when run on too many objects. This release resolves an issue in which CiscoCM Knowledge Scripts might fail with an Internal Failure error message if the scripts are run on too many objects for AppManager to create the complete list of object names. With this release, changes to the managed object allow the CiscoCM scripts to return more descriptive error messages in this situation, including an estimate of the maximum number of objects that can be selected. (ENG317486)
This release of included the following enhancements:
Support for Cisco Unified Communications Manager version 8.6. This release now supports Cisco UCM version 8.6.
Supplemental database support for SQL 2008 and SQL 2008 R2. This release now includes supplemental database support for SQL 2008 and SQL 2008 R2.
New sort options for the CiscoCM_CDR_CallQuality Knowledge Script. This release includes two new parameters in the CiscoCM_CDR_CallQuality script that allow you to specify how to sort the event details table. The first parameter, Sort call details table by this value, lets you sort the call details table by just one of the call details instead of all call details. The second parameter, Sort type for call details table, lets you choose an ascending or a descending sort. (ENG299133)
New filtering options for the CiscoCM_CDR_CallQuality Knowledge Script. This release lets you filter for more than one range of directory numbers with the Directory Number parameter in the CiscoCM_CDR_CallQuality script. You can now specify multiple expressions separated by commas, including an asterisk (*) as a wildcard, such as 123*,2345,234*. (ENG281200)
New filters for the CiscoCM_CDR_Query Knowledge Script. This release includes two new parameters for the CiscoCM_CDR_Query script that you can use to filter your query for call data records (CDRs). The first parameter, Called directory number type, lets you filter the CDRs by the originally called directory number, the most recently called directory number, or by either directory number. The second parameter, Call time range type allows you to filter by the type of call time range you want to use when troubleshooting. (ENG304079)
SNMP trap event message customization. This release allows you to use the CiscoCM_SNMPTrap_Async Knowledge Script to add or edit trap event message definitions, based on a .csv file you created. (ENG299843)
New CiscoCM_LicenseUsage Knowledge Script. You can use this script to monitor authorized, used, and remaining phone and node licenses on a Cisco Unified Communications Manager cluster. This script raises an event if the number of remaining licenses falls below a threshold, or if the percentage of licenses used exceeds a threshold you set. (ENG299849)
This release also resolved the following issues:
An exception occurs when you stop the NetIQmc service while CiscoCM jobs are running. This release resolves an issue that occurs when you stop the NetIQ AppManager Client Resource Monitor (netiqmc.exe) agent service when you are running any CiscoCM jobs that query performance counters. Because the module installer stops the netiqmc.exe service as part of the installation process, you may experience this behavior when you install this release. After installation is complete, an update to the CiscoCM managed object, qNQCiscoCM.dll, prevents the netiqmc.exe service from crashing in this situation. (ENG313442)
Unclear error message text when video bandwidth settings are not fixed for the CiscoCM_Locations Knowledge Script. This release resolves an issue in which a video bandwidth setting of None or Unlimited in Cisco Unified Communications Manager caused the CiscoCM_Locations script to raise an event about unlimited video bandwidth, and the event message was not clear about the cause of the event. With this release, an update to the event message describes the cause of the event when the location does not have a fixed video bandwidth. (ENG300530)
An internal failure prevents the CiscoCM_MTP_Device job from completing. This release resolves an issue in which the CiscoCM_MTP_Device job failed with the following event message: "An internal failure occurred that prevented the current iteration of the job from completing." With this release, an update to the Knowledge Script code prevents this failure. (ENG301677)
The CiscoCM_MGCP_PRI_CallActivity Knowledge Script continually raises alerts. This release resolves an issue in which the CiscoCM_MGCP_PRI_CallActivity script constantly raised alerts when the object instance name in the TreeView was the same as another object instance name in the TreeView. With this release, an update to the Knowledge Script code enables the job to use the full name for the object instead of just the instance name, which prevents the constant raising of alerts when two or more TreeView instance names are the same. (ENG307030)
MOS values returned by the CiscoCM_CDR_CallQuality Knowledge Script are inaccurate. This release resolves an issue in which the Mean Option Score (MOS) values for Cisco Unified Communications Manager clusters were lower than expected due to erroneous data. With this release, updates to the script filtered out all MOS values of zero, so that the script no longer includes zero MOS values in the data point calculations or the detail result tables. (ENG303862)
Error when trying to query call records with the CiscoCM_CDR_CallQuality Knowledge Script. This release resolves an issue in which running the CiscoCM_CDR_CallQuality script raises a Database operation failed event message when the packet count in the Cisco call data record (CDR) has an invalid value. With this release, an update to the code of the CiscoCM_CDR_CallQuality prevents the error from occurring. (ENG313071, ENG278857)
This initial release provided the following enhancements:
Support for Cisco Unified Communications Manager 8.5. This release now supports Cisco Unified Communications Manager version 8.5.
Support for Microsoft Windows 7. This release provides support for proxy agent computers running 32-bit or 64-bit Windows 7.
This release also resolved the following issues:
After discovery, the fully qualified domain name does not display in the TreeView. This release addresses an issue in which the fully qualified domain name (FQDN) for a Cisco Unified Communications Manager server does not display in the TreeView of the AppManager Operator Console after you run the Discovery_CiscoCM Knowledge Script. With this release, you can set a parameter in the Discovery script to display CiscoCM servers in the TreeView using FQDNs instead of the host name after you run discovery. (ENG301579)
The CDR_CallQuality Knowledge Script generates events based on invalid call records. This release addresses an issue in which the CDR_CallQuality script generated a "Database operation failed" event when it encountered certain types of invalid call records from the Cisco Unified Communications Manager server. With this release, the module more accurately screens for invalid records and ignores them, which keeps the "Database operation failed" event from occurring. (ENG300528)
The AppManager for Cisco Unified Communications Manager product and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).
The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.
Xerces. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Boost License.
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the “Software”) to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:
The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Net-SNMP. Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001. An additional copyright section has been added as Part 4 below also under a BSD license for the work contributed by Sun Microsystems, Inc. to the project since 2003.
Code has been contributed to this project by many people over the years it has been in development, and a full list of contributors can be found in the README file under the THANKS section.
---- Part 1: CMU/UCD copyright notice: (BSD like) -----
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----
Copyright (c) 2001-2003, Networks Associates Technology, Inc
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
Portions of this code are Copyright (c) 2001-2003, Cambridge Broadband Ltd.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) ----- Copyright (c) 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Use is subject to license terms below. This distribution may include materials developed by third parties. Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ---- Part 5: Sparta, Inc copyright notice (BSD) -----
Copyright (c) 2003-2006, Sparta, Inc
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----
Copyright (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) -----
Copyright (c) Fabasoft R&D Software GmbH & Co KG, 2003
oss@fabasoft.com
Author: Bernhard Penz
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
OpenSSL License. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)."
The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)."
THIS SOFTWARE IS PROVIDED BY THE OPENSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
SSLeay License. Copyright (c) 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscape's SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-)."
If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)."
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license (including the GNU Public License).
Last Modified October 2011
AppManager for Cisco Unified Communications Manager 7.5
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see http://www.netiq.com/company/legal/.
Copyright © 2019 NetIQ Corporation. All Rights Reserved..