AppManager for Call Data Analysis 7.5.0.2 Release Notes

Date Published: December 2018

AppManager for Call Data Analysis lets you to collect call detail records (CDRs) in a centralized repository. You then use Knowledge Scripts to create and schedule reports that analyze the telephony traffic represented by the gathered data. AppManager for Call Data Analysis supports CDRs produced by Cisco H.323 gateways, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express routers.

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 website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click Click to comment on this content to the right of each section 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 website.

1.0 What’s New?

This release of AppManager for Call Data Analysis provides the following enhancements:

  • Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Call Data Analysis provides support for TLS 1.2.

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. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.

This release of AppManager for Call Data Analysis replaces all Previous Releases.

2.0 System Requirements

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 Call Data Analysis has the following system requirements:

Software/Hardware

Version

NetIQ AppManager installed on the AppManager repository (QDB) computers, on the computers you want to monitor (agents), and on all console computers

8.0.3, 8.2, 9.1, 9.2, 9.5, or later

One of the following AppManager agents are required:

  • AppManager agent 7.0.4 with hotfix 72616 or later

  • AppManager agent 8.0.3, 8.2, 9.1, 9.2, 9.5, or later

Microsoft Windows operating system on the agent computers

One of the following:

  • Windows 10 (32-bit or 64-bit)

  • Windows Server 2016

  • Windows Server 2012 R2

  • Windows Server 2012

  • Windows Server 2008 R2

  • Windows Server 2008 (32-bit or 64-bit)

  • Windows 7 (32-bit or 64-bit)

Microsoft SQL Server installed on the Data Warehouse and Data Mart computers

One of the following:

  • SQL Server 2016, with Microsoft SQL Server Integration Services.

  • SQL Server 2014, with Microsoft SQL Server Integration Services.

  • SQL Server 2012, with Microsoft SQL Server Integration Services.

  • SQL Server 2008 R2, with Microsoft SQL Server Integration Services

NOTE:

  • The Extraction, Transformation, and Loading (ETL) process requires a minimum disk space of 1 GB on the drive where the Data Mart is located.

  • This module supports named instances of SQL Server as well as cluster nodes.

NetIQ AppManager for Cisco Unified Communications Manager

Required for monitoring CDRs produced by Cisco Unified Communications Manager version 5.x through 8.6

Microsoft .NET Framework installed on the agent computers

4.0 or later

SQL Client Tools SDK on the agent computers

The version of SQL Client Tools SDK on the agent computers must be same as the corresponding SQL Servers that host the Data Mart databases.

NOTE:You can install Client Tools SDK from the Microsoft SQL Server iso file by running the Setup wizard.

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 hardware requirements and supported operating systems and browsers, see the NetIQ AppManager for Call Data Analysis 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.

3.0 Contents of the Download Package

AppManager for Call Data Analysis includes a managed object, qCallDataa4.dll, and Knowledge Scripts to discover and monitor Call Data Analysis resources. The download package includes this release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

  • AM70-CallDataAnalysis-7.5.114.0.msi, the module installer.

  • AM70-CallDataAnalysis-7.5.114.0.ini, a configuration file used with the AppManager setup program.

  • AM70-CallDataAnalysis-7.5.114.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-CallDataAnalysis-7.5.114.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.

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

4.0 Installing This Module

IMPORTANT: If you are upgrading from version 7.4, you need to perform additional steps to ensure that the Data Warehouse is properly configured for this version of the module. For more information, see the “Upgrading from Version 7.4 of the Module” section in the management guide.

Run the module installer to install the module components in the following locations:

  • On the 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 these components 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 NetIQ AppManager for Call Data Analysis Management Guide, included in the download package.

5.0 Known Issues

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.

6.0 Previous Releases

This release of Call Data Analysis includes enhancements added in previous releases.

6.1 Release 7.5.0.1, January 2018

This release provided the following enhancements:

  • This release of AppManager for Call Data Analysis supports SQL Servers with TLS 1.2 enabled.

6.2 Release 7.5, November 2017

This release provided the following enhancements:

  • Support for Microsoft Windows 10, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012: This release supports Windows 10, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012. For more information, see the System Requirements.

  • Support for Microsoft SQL Server 2016, SQL Server 2014, and SQL Server 2012: This release supports SQL Server 2016, SQL Server 2014, and SQL Server 2012. For more information, see the System Requirements.

This release of AppManager for Call Data Analysis resolved the following issue:

  • No check is performed to determine the validity of a CDA Warehouse database: When a database name was specified for Call Data Analysis in the Discovery_CallDataAnalysis Knowledge Script, there was no check mechanism involved to determine whether the specified database was a valid CDA Data Warehouse. In this release, a check is performed to determine whether the specified database is a valid CDA Data Warehouse and an event is raised if the check fails. (ENG343622)

6.3 Release 7.4.55.0, June 2012

This release provided the following enhancements:

  • Support for SQL Server named instances in the Data Warehouse and the Data Mart computers: This release now supports installation of the module when the SQL servers for the Data Warehouse and Data Mart are on separate computers. The Data Warehouse and Data Mart can be installed in named SQL server instances. SQL user logins to all databases are also supported.

  • Support for configurable names for the Data Mart and Data Warehouse databases: The Database name parameter in the CallData_AddDataSource_* Knowledge Scripts allow you to specify a name for the Data Mart database. You can also customize the Database name parameter for the Data Warehouse database. You can leave this parameter blank to use the default database name. In previous releases, the module would set these database names for you.

  • Running the Discovery_CallDataAnalysis Knowledge Script creates the Data Warehouse: The Discovery_CallDataAnalysis script creates the Data Warehouse if one does not exist, or it updates the Data Warehouse and associated security parameters if the warehouse has previously been created. In previous versions of this module, the Data Warehouse was created during the installation process.

  • Support for the installation of the Data Warehouse and Data Mart on additional SQL Server configurations: You can now install the Data Warehouse and Data Mart to a remote SQL Server or to a clustered SQL Server.

  • Updated SQL Server password support with Security Manager: This release retrieves SQL passwords from AppManager Security Manager when you run the Discovery_CallDataAnalysis and the CallData_AddDataSource_* scripts. As a result of this new functionality, the CallData_UpdateSecurity Knowledge Script was removed from this release, and the SQL password parameters were removed from the CallData_AddDataSource_* scripts.

  • Support for additional Windows operating systems: This release now supports 64-bit as well as 32-bit Windows operating systems, including Windows 7, Windows Server 2008 R2, and Windows Server 2003.

  • Support for SQL Server 2008 and SQL Server 2008 R2: This release supports Microsoft SQL Server 2008 and SQL Server R2 installed on the Data Warehouse and Data Mart computers. For both SQL Server 2008 and SQL Server 2008 R2, you need to install the Backward Compatibility pack. For more information, see the “SQL Server Dependencies” section in the management guide.

  • Support for Cisco Unified Communications Manager 8.5 and 8.6: This release now supports the monitoring of CDRs produced by Cisco Unified Communications Manager versions 8.5 and 8.6.

  • CallData_Report_CallDetail_CiscoCallMgr Knowledge Script includes a new custom filter parameter for SQL: The new Custom SQL filter parameter in this report script allows you to specify a SQL clause to filter the results in the report.

  • Improvements to the uninstallation procedure: If you uninstall this release of the module, the uninstallation procedure only disables the SQL ETL job that belongs to the Data Mart component. Other SQL elements, such as packages, jobs, logins, linked servers, and the Data Warehouse database, will remain after the module uninstallation is complete. In previous versions, these items were removed as part of the uninstallation.

  • Updates to the AppManager for Call Data Analysis Management Guide: This release includes the following updates to the “Installing AppManager for Call Data Analysis” chapter of the management guide:

    • How to address the dependencies for this module for SQL Server 2008 R2, SQL Server 2008, and SQL Server 2005.

    • How to upgrade an existing Call Data Analysis installation from SQL Server 2000.

    • How to configure Network Policy Server (NPS) to set up a Cisco router as a RADIUS client. NPS is a replacement for Internet Authentication Service (IAS), which was available in Windows Server 2003.

    • How to filter out-of-range data using the new Variables table in the Data Warehouse.

This release resolved the following issues:

  • ETL process fails if there is insufficient free space on the Data Mart computer: This release resolves an issue in which the Extraction, Transformation, and Loading (ETL) process failed if you had less than 1 GB of free space on any of the drives on the computer where you installed the Data Mart. In this situation, the ETL process failed on step 1. With this release, the ETL process only requires a minimum disk space of 1 GB on the drive where the Data Mart is located, and not on the other drives on the computer. (ENG239695)

  • ETL process fails after adding a new Data Source and creating a Data Mart: This release resolves an issue that occurred when you added a Cisco Unified Communications Manager as a Data Source and created the corresponding Data Mart, and then the ETL process failed on step 1 with an error message stating, “Cannot find either column 'dbo' or the user-defined function or aggregate 'dbo.fGetDataSourceID,' or the name is ambiguous.” The ETL process failed because the database for the Data Warehouse was not associated properly with the new Data Source. With this release, the ETL process runs as expected when you add a new Data Source and create a Data Mart. (ENG316959)

  • Call Data Analysis is unable to parse MOS data that contains invalid numeric values: This release resolves an issue in which the module was unable to use data that included Mean Opinion Score (MOS) with invalid numeric values. As a result, the Call Data Analysis reports did not contain accurate data. With this release, a change to the way in which the module handles invalid numeric values allows the CDR data to be processed correctly in the Call Data Analysis reports. (ENG286566)

6.4 Release 7.3.65.0, January 2012

This release provided the following enhancement:

  • Ability to import information from backup call records: With this release, you can import data from backup call records into the Call Data Analysis Data Mart. For more information about this manual process, see the “Importing Data from Backup Call Records” section in the AppManager for Call Data Analysis Management Guide.

This release resolved the following issues:

  • Entries in the Data Mart database contain inaccurate values for call quality data: This release resolves an issue in which the supplemental database contains data about call quality, such as packet loss, but the corresponding entries in the Data Mart database contain a value of Null in all Quality columns. With this release, the entries in the Data Mart display properly. (ENG308612)

  • ETL jobs fails on step 5: This release resolves an issue in which the Extraction, Transformation, and Loading (ETL) process fails on step 5 (Prepare CMRs) with this error message: Null value is eliminated by an aggregate or other SET operation, when the data received from the Cisco server contains out-of-range values, such as 2147483647, for one or more quality metrics. With this release, an update to the process filters out invalid data values from calculations used in the ETL process and keeps ETL jobs from failing. (ENG309288)

6.5 Release 7.3.41.0, November 2010

This release added support for Cisco Unified Communications Manager 8.0.

6.6 Release 7.3.37.0, March 2010

This release resolved the following issue:

  • ETL job fails in step 6: This release resolved an issue in which the Extract, Transform, Load (ETL) process, which moves call data into the Data Mart, fails in step 6 with the following error message: Cannot insert duplicate key in object 'dbo.Data_<date>'. The error is caused by a failed attempt to write multiple instances of a single call record into the Data Mart. After you install this release, a code change filters out potential duplicate records from intermediate tables before new records are inserted into dbo.Data_<date> tables. (ENG278880)

6.7 Release 7.3.34.0, October 2009

This release resolved the following issues:

  • New reporting option in CallVolume report: The CallData_Report_CallVolume Knowledge Script offers a new parameter that allows you to select how call time details are grouped in the report: Group time details based on. Select Start time to group calls by the periods in which the calls start. Select Call duration to split calls into multiple groups based on the duration of the calls. For more information, see the online Help for the Knowledge Script. (ENG272777)

  • ETL jobs remain in step 3: Before you install this release, the Extract, Transform, Load (ETL) process, which moves call data into the Data Mart, remains in step 3. New jobs cannot start because the old job is still running. After you install this release, a code change corrected all Data Transformation Service (DTS) steps in the ETL process, which allows the ETL job to finish. (ENG273009)

6.8 Release 7.3.28.0, April 2009

This release provided the following enhancement:

  • Support for Windows Server 2008: With this release, AppManager for Call Data Analysis adds support for Microsoft Windows Server 2008 and removes support for Microsoft SQL Server 2000.

This release resolved the following issues:

  • Report scripts fail when executing the stored procedures: Before you install this release, jobs involving the Report Knowledge Scripts fail when attempting to run the associated stored procedures. The error message in the log files indicates that the maximum number of tables in the query has been exceeded. After you install this release, the Report scripts successfully execute the stored procedures, regardless of the number of tables in the query. (ENG253483)

  • Adding multiple data sources causes failure in Report scripts: Before you install this release, Report Knowledge Script jobs fail after you add multiple data sources (approximately 20) using the AddDataSource Knowledge Script. The stored procedures that support the addition or removal of data sources create one large tsql statement that exceeds the character limit imposed by SQL Server, which causes the failure of subsequent attempts to query SQL Server. After you install this release, SQL Server views are updated using a method that is not limited by the number of data sources. (ENG253483)

6.9 Hotfix 71235, September 2008

This release resolved the following issues:

  • CallData_Report_Jitter report contains no data: Before you install this release, an arithmetic exception error can cause the Jitter report to contain no data, if call detail records (CDRs) contain invalid jitter values equal to the maximum allowed integer value. After you install this release, the average jitter calculation ignores jitter values equal to the maximum integer value in the calculation, which prevents the arithmetic exception error. (ENG248307)

  • Error in associating call record locations: Before you install this release, the data extraction and transformation (ETL) process can be interrupted due to an error in associating a given call with its location. After you install this release, an updated stored procedure correctly associates the call record with its location information, preventing interruptions in the ETL process. (ENG247005)

  • CallData_Report_TrunkGroupByHour fails to create report: Before you install this release, the TrunkGroupByHour report fails in environments that have a large number of monthly data tables across all Data Marts. The report initially attempts to select data from all data tables in every Data Mart, before filtering the data according to the source and time range selected. After you install this release, the TrunkGroupByHour report more efficiently queries only the data sources selected for the report. (ENG250539)

6.10 Release 7.3, January 2008

This release provided support for Microsoft SQL Server 2005 and support for AppManager licensing.

7.0 Contact Information

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

For general corporate and product information, see the NetIQ Corporate website.

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.