AppManager for Avaya Communication Manager Release Notes 8.0.0.1

Support for Avaya Communication Manager 7.1.3 and 8.0: This hotfix release of AppManager, provides support for Avaya Communication Manager 7.1.3 and Avaya Communication Manager 8.0.

AvayaCM module causing agent crash: This hotfix release of AppManager for Avaya Communication Manager resolves AvayaCM module agent crash when using multiple TrunkGroups.(ENG347110)

No data for Active Calls - Close/Shutdown RTCP Socket Correctly an issue occurs when multiple call data jobs are running at the same time when an agent restarts for any reason, access to the RTCP port can then become blocked resulting in an ERROR AvayaCM - The RTCPListener's "bind" call failed with error code 10048 log and 0 value for the call data collection stream. With this release, the socket management code was updated and a mutual exclusion region was applied to prevent these errors from occurring. (ENG340966).

Packages new Aura MIBs. With this release the new AVAYA-AURA-CM-MIB and AVAYA-AURA-CMALARM-MIB installs in the appmanager/bin directory. These MIBs are necessary to discover Aura call managers, and to fully decode traps received with the corresponding MIBs in SNMPTraps. (ENG340609).

Allows Discovery of call managers using AVAYA-AURA-CM-MIB SNMP MIB. With this release, Avaya allows discovery of call managers using the AVAYA-AURA-CM-MIB (Avaya releases 6.3 and later). Upon discovery, Avaya creates treeview objects that are necessary for the call managers to support call data collection functionality. Avaya also creates treeview objects that enable jobs requiring additional SNMP queries. (ENG340608)

Allows discovery of non-SNMP Avaya. With this release Avaya allows the discovery of Avaya call managers for which SNMP access is not available. Upon discovery, Avaya creates treeview objects necessary for call managers to support call data collection functionality. Avaya does not create treeview objects which allow jobs that require additional SNMP queries for these servers. (ENG340611)

Discovers station folder and allows station-based Knowledge Scripts for Aura and non-SNMP systems. With this release, Avaya the discovery of Avaya call managers that do not have access to SNMP. Upon discovery, Avaya creates treeview objects necessary for the call managers to support call data collection functionality. Avaya does not create treeview objects for enabling jobs that require additional SNMP queries for the servers. (ENG340911)

Updates licensing count for non-SNMP Avaya. This release updates the treeview details for Avaya call servers discovered without SNMP to include an estimated “subscriber count” from the CDR database. For call servers discovered using Avaya SNMP MIBs, the “subscriber count” used for licensing is the registered stations count in the Avaya SNMP MIB. (ENG340906)

Renaming Avaya trunks cause AppManager to stop monitoring the trunks. This release resolves the issue in which the datapoints for the trunks were reported with the “old” object name until discovery. With this release, the name in the datastream will match the name by which the object is known in the treeview. The exception is for objects identified by an index number in the name, following the device discovery, when the Add Avaya Index to Discovered Names parameter is selected, datastreams for these objects will match the index number in the treeview, regardless of whether the name matches.(ENG339487) For additional information about the Add Avaya Index to Discovered Names parameter, see the “Discovering Avaya Communication Manager Resources” in the Management Guide.

AvayaCM always reports LSP Status against 1 LSP after ENG337359 PF. This release resolves the issue that occurred after ENG337359 when the agent managed object, which was running a job against multiple objects, reports all error events against only the first object in the list. With this release, when the agent managed object runs a job against multiple objects, any errors detected against those objects will be reported.(ENG338876)

Trunk Groups with duplicate names are not displayed. This release resolves an issue in which any trunk group that had a name which was not unique was identified with a numeric suffix. With this release, a new parameter Add Avaya Index to discovered names was added to discovery. When you select this parameter, all discovered Avaya objects for collected indices are placed in the treeview with a treeview name formed by suffixing the index of the object to the Avaya name for the object. Fax test 1 at index 14 becomes Fax test 1[14]and Fax test 2 at index 15 becomes Fax test 2[15].(ENG334424) For more information about the Add Avaya Index to discovered names parameter, see the “Discovering Avaya Communication Manager Resources” section in the Management Guide.

AvayaCM_HuntGroupUsage and other Knowledge Scripts not collecting data, and AvayaCM is sharply limited in the number of simultaneous “get requests” that can be processed. This release resolves a set of issues where AvayaCM was unable to provide SMNP data for requests because the request rate and volume exceeded its internal performance limits. We reduced the number of requests and the limited request rate to reduce the load on AvayaCM to better allow it to keep up with the requests.(ENG338854, ENG336716, ENG337359, ENG336037)

AvayaCM_CallActivity Knowledge Script generates multiple data streams for a single metric. This release resolves an issue in which the AvayaCM_CallActivity script created multiple data streams and did not correctly associate data points with those data streams, instead of creating a single data stream and associating all data points with that data stream. With this release, an update to the AvayaCM_CallActivity script allows the script to create data streams and data points correctly (ENG330096)

AvayaCM_SecurityViolations Knowledge Script does not return security violation data. This release resolves an issue in which the AvayaCM_SecurityViolations script did not report security violation data when the login port name you wanted to monitor was blank. With this release, the AvayaCM_SecurityViolations script accurately reports security violations in this situation. (ENG330474)

Discovery_AvayaCM Knowledge Script does not fully discover an Avaya device although it reports a successful discovery. This release resolves an issue in which the Discovery_AvayaCM script reported a successful discovery for an Avaya Communication Manager cluster, but due to an SNMP message or a task timeout error, the job did not actually discover all the resources for that cluster. With this release, an update to the Discovery_AvayaCM script prevents the script from discovering resources and instead generates an event message stating that discovery failed when an SNMP message or task timeout error occurs on an Avaya CM cluster. (ENG330086)

Support for Windows 8 and Windows Server 2012. This release supports Windows 8 and Windows Server 2012 on proxy agent computers. For more information, see the System Requirements.

Support for Avaya Communication Manager 6.3, 6.2, and 6.1. You can use this release of AppManager for Avaya Communication Manager to monitor Avaya Communication Manager version 6.3, 6.2, and 6.1.

Some AvayaCM Knowledge Scripts assign events to the wrong object in a folder containing the same type of objects. This release resolves an issue that occurred when you ran an AvayaCM script on a TreeView folder that contained more than one object of the same type, and the script assigned events only to the first object in the folder. With this release, when you run an AvayaCM script on a folder object, the script assigns an event to the correct object in that folder. (ENG325279)

Some AvayaCM Knowledge Scripts generate an “Internal Failure” error message when the device object has a comma in its name. This release resolves an issue in which an AvayaCM script failed when you ran the script on an object folder in the TreeView and an object in that folder had a comma in its name. In this situation, the script incorrectly identified the comma as a delimiter, creating a mismatch between the object names and the details for those objects. With this release, the AvayaCM scripts run without failing on objects that contain a comma in their names. (ENG324772)

AvayaCM_AddPhone Knowledge Script cannot add a phone with an extension of more than ten digits. This release resolves an issue in which the AvayaCM_AddPhone script raised an error message stating that an extension was not found, when the extension actually existed, but contained more than ten digits. With this release, the AvayaCM_AddPhone script now supports extensions of up to 15 digits. (ENG321315)

AvayaCM_PhoneQuality Knowledge Script incorrectly labels zero delay measurements at the start of a call. This release resolves an issue in which the AvayaCM_PhoneQuality script reports a zero round-trip delay at the start of a call, even though the true delay is at that time unknown. This error resulted from an invalid metrics report received from the 96x1 Avaya station firmware. With this release, the AvayaCM_PhoneQuality script identifies and excludes invalid zero round trip time metrics reports at the start of the call. (ENG322414)

The AvayaCM_SystemUptime job fails due to a negative uptime value. This release resolves an issue in which the AvayaCM_SystemUptime Knowledge job failed because AppManager incorrectly reported the system uptime value as a negative number, which caused the script to fail. With this release, AppManager no longer reports the negative value. (ENG312274)

Invalid data from an AvayaCM_PhoneQuality job causes a negative datastream value. This release resolves an issue in which the AvayaCM_PhoneQuality job encountered invalid packet loss data that resulted in a data point of -1. With this release, the AvayaCM_PhoneQuality job ignores the invalid packet count if no valid data is available, which keeps the job from generating a negative data stream value. (ENG312807)

Type 1 call data records are not generated when trace level is set to Error. This release resolves an issue in which type 1 call data records (CDRs) did not get generated with the default trace level setting of Error, as well as the Info setting. This release ensures that Type 1 CDRs get generated regardless of the trace level settings. (ENG313291)

A discovered object with a comma in its name causes AvayaCM Knowledge Scripts to fail. This release resolves an issue in which AvayaCM Knowledge Scripts failed when run on an object containing a comma in its name. This release allows you to run scripts on the following objects, even if they contain commas in their names: LSS, ESS, trunk group, hunt group, announcement, and gateway objects. However, because the name of the cluster is used as the name of the SQL database, and a comma is a special character to SQL, the cluster object name cannot contain a comma. With this release, you can successfully run all AvayaCM scripts on objects that have commas in their names, so long as the cluster name itself does not contain a comma. (ENG311613)

Support for Avaya Communication Manager 6.0. You can use this release of AppManager for Avaya Communication Manager to monitor Avaya Communication Manager version 6.0. For more information, see the System Requirements.

Support for retrieving configuration data when running the AddPhone Knowledge Script. You can use the AvayaCM_AddPhone script to retrieve SNMP configuration data for your phones, leading to a faster setup for phone quality monitoring. (ENG308004)

Support for filtering by Facilities Restriction Level (FRL) codes. You can use the AvayaCM_CallFailures Knowledge Script to filter by some or all FRL codes. (ENG287372)

The AvayaCM_PhoneQuality Knowledge Script fails due to negative datastream values. This release resolves an issue in which the AvayaCM_PhoneQuality script generated “internal failure” errors because of negative values in the PctPacketLoss datastream. With this release, an update to the code of the AvayaCM_PhoneQuality script prevents the errors. (ENG309871)

Improve information provided by AvayaCM_SNMPTrap Knowledge Script for unmapped traps. This release resolves an issue in which the event message for the AvayaCM_SNMPTrap script provided a default message for unmapped traps which did not contain enough data to describe the cause of the event. With this release, the AvayaCM_SNMPTrap script includes more information in the default event message for unmapped traps. (ENG276822)

Allow user-selectable filters for call completion codes in the AvayaCM_CallFailures Knowledge Script. This release allows you to specify specific Avaya Communication Manager failure codes to be considered in counting failed calls for the AvayaCM_CallFailures script. With this release, a new Knowledge Script parameter lets you filter by failure code, including calls with a duration of zero. (ENG294041)