Use this Action Knowledge Script to trigger NetIQ Vivinet Diagnostics to run a Diagnosis of voice quality between two phones or two endpoints. A Diagnosis is performed when a threshold is exceeded when you run any of the following Knowledge Scripts:
AvayaCM_CallQuality. Vivinet Diagnostics can diagnose the problem when average MOS, average R-Value, average jitter, average latency, and average packet loss fall below or exceed their thresholds.
AvayaCM_PhoneQuality. Vivinet Diagnostics can diagnose the problem when MOS, R-Value, jitter, latency, and packet loss fall below or exceed their thresholds during the data collection interval.
CiscoCallMgr_CallQuality. Vivinet Diagnostics can diagnose the problem when jitter, latency, and percentage of lost data exceed their thresholds.
CiscoCallMgr_CallFailures. Vivinet Diagnostics can diagnose the problem when the number of failed calls exceeds its threshold.
NortelCS2x_CallQuality. Vivinet Diagnostics can diagnose the problem when end-of-call values for MOS and R-value fall below their thresholds, and when end-of-call values for jitter, latency, and packet loss exceed their thresholds.
NortelCS2x_PhoneQuality. Vivinet Diagnostics can diagnose the problem when mid-call values for MOS and R-value fall below their thresholds, and when mid-call values for jitter, latency, and packet loss exceed their thresholds.
PhoneQuality_CiscoPhoneQuality. Vivinet Diagnostics can diagnose the problem when the values for listening MOS and listening R-value fall below their thresholds, and when the values for average jitter, maximum jitter, and packet loss exceed their thresholds.
VoIPQuality_CallPerf_<name of script>. Vivinet Diagnostics can diagnose the problem when MOS, R-factor, delay, jitter buffer loss, and percentage of lost data exceed their thresholds.
NOTE:This script is supported only when Vivinet Diagnostics 1.1 or later is installed. In addition, this script does not work when triggered by Knowledge Scripts other than those listed above.
When launched, Action_DiagnoseVoIPQuality performs the following steps:
Verifies that Vivinet Diagnostics 1.1 or later is installed. If Vivinet Diagnostics 1.1 or later is not installed, this script raises an event indicating that Vivinet Diagnostics 1.1 is required.
Verifies that you have elected to run this Action Knowledge Script based on an event raised by the running of an applicable script. If you choose to initiate this script based on some other Knowledge Script, this Action script raises an event indicating that the Action script cannot invoke Vivinet Diagnostics from the <script name> Knowledge Script.
Determines the number of Diagnoses that need to be performed based on the parameters that you set in the above-mentioned scripts, as well as the thresholds that were reached or exceeded.
Invokes Vivinet Diagnostics to perform the Diagnosis and generate an .html diagnostic report.
If Use Report Agent settings? is disabled, generates a default.rptIndex.xml file and a small default.htm file that contains hyperlinks to the .dgv file and the Vivinet Diagnostic report.
Upon completion of the Diagnosis, raises an event that contains the results of the Diagnosis. An event for a successful Diagnosis contains either a URL to the default.htm file (if Use Report Agent settings? is enabled) or the name of the computer and full directory path to the output files. An event for an unsuccessful Diagnosis contains an error message explaining why the Diagnosis was unsuccessful.
For a more in-depth discussion of the integration of Vivinet Diagnostics and AppManager, see the User Guide for Vivinet Diagnostics.
NOTE:Before running this script, you must first configure Vivinet Diagnostic with information about your VoIP setup. AppManager passes phone data, such as the calling party or the called party, to Vivinet Diagnostics, and then Vivinet Diagnostics starts the diagnosis using the phone data from AppManager and the VoIP setup information you configured in Vivinet Diagnostics. Be aware that AppManager will not raise an alert if the information about your VoIP setup is missing from Vivinet Diagnostics.
The following list covers what you must configure for Vivinet Diagnostics, based on your VoIP setup:
Nortel Call Server Signaling Server (for Nortel phones)
Cisco Call Manager (for Cisco phones)
SNMP information (for all VoIP phones)
For more information, see the User Guide for Vivinet Diagnostics.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Event severity when error |
Set the severity level, between 1 and 40, to indicate the importance of an event in which a diagnosis does not complete successfully. The default is 15. |
|
Event severity when successful |
Set the severity level, between 1 and 40, to indicate the importance of an event in which a diagnosis completes successfully. The default is 35. |
|
Output folder prefix |
Enter a prefix for the output folder that is created by the Diagnosis. The output folder then uses this prefix in its naming convention as follows: Prefix_JobID_ComputerName_DateTime. NOTE:The ComputerName is the name of the CallManager computer or talker/listener computer. If a single event triggers multiple Diagnoses, a sequence number (0, 1, 2, 3, 4) is appended to the output folder name. The output folder contains the .dgv file, the diagnostic .html report file, and, if integrated with the report-enabled agent, a default.rptIndex.xml file, and a default.htm file that contains hyperlinks to both the .dgv file and the diagnostic .html report. |
|
Use Report Agent settings? |
Set to y to integrate the Diagnostics results into the AppManager Web management server (the Report Binder). The default is y. |
|
Full path to root of output folders |
Provide the full path to the root of where the output folders will be created. NOTE:Ignore this parameter if Use Report Agent settings? is set to Yes. |
|
Maximum diagnoses |
Specify a number between 1 and 5 to indicate the maximum number of Diagnoses that can be triggered by a single event. NOTE:This parameter is applicable only for events generated by the CiscoCallMgr_CallQuality and CiscoCallMgr_CallFailures scripts, where one event may identify multiple pairs of phones that indicate a problem. |