3.3 AddDataSource_H323RADIUS

This script creates the Data Mart, which is the container for all configuration and CDR information it gathers from the Data Source according to a schedule you determine.

The H.323 RADIUS Data Source is the log (flat) files written by the IAS/RADIUS server when it receives call detail records generated by Cisco H.323 gateways and Communications Manager Express routers.

Cisco Communications Manager Express views the IP phones connected to it as virtual voice ports (EFXS) and generates telephony call legs to and from these phones. Therefore, call quality information is not available for a call from Communications Manager Express phones for which the call remains on Communications Manager Express or goes directly to the PSTN.

This script raises an event if a Data Source is added successfully, if the Data Mart server is inaccessible, if warnings are raised during an attempt to add a Data Source, and if a Data Source is not added.

You can re-run this Knowledge Script to change parameter settings, such as log file archiving. If you do so, you need to complete all parameters, not just those you are changing.

NOTE:After you run AddDataSource_H323RADIUS, press F5 to refresh AppManager and display the other Knowledge Scripts available in the Call Data Analysis module.

3.3.1 Changing RADIUS Log Folder or Archive Settings

When you add a Data Source, you specify whether to archive RADIUS logs after processing. In addition, you indicate the location of the RADIUS logs and the location of the archive folder.

To change any of these settings for a Data Source you already added, rerun AddDataSource_H323RADIUS and complete all parameters, including those for which the setting is not changing:

  • Folder containing IAS RADIUS logs. Use this parameter to specify the location on the Data Mart of the folder that houses the IAS RADIUS logs. This location is the one you set up when you configured IAS.

  • Archive RADIUS logs after processing? Set this parameter to Yes if you want to archive the RADIUS logs after their data has been processed. If you set this parameter to Yes, you must use the Archive folder parameter to specify the location of the archive folder.

  • Archive folder. Use this parameter to specify the location on the Data Mart of the folder in which you want to archive the processed RADIUS logs.

NOTE:If you rerun AddDataSource_H323RADIUS, all parameters are updated, not only the three discussed above. Therefore, if you originally added your Data Source with any non-default parameter values, ensure you set those parameters correctly when you run the script to change archive or log information.

3.3.2 Reviewing Call Quality Metrics for Gateways and Routers

Cisco H.323 gateways provide call quality information for the VoIP legs of a call. Using this information, AppManager calculates additional quality metrics.

MOS

The Mean Opinion Score is an overall score representing the quality of a call. The MOS is a number between 1 and 5. A MOS of 5 is excellent; a MOS of 1 is unacceptably bad. The MOS is calculated based on measured items plus jitter buffer size.

R-value

Can be mapped to an estimated MOS. R-values range from 100 (excellent) to 0 (poor).

Jitter loss

Calculated from the number of received and discarded packets. Discarded packets are those that arrive too early or too late to be stored in the jitter buffer.

Packet loss

Calculated from the number of received and lost packets.

Delay

One-way delay approximated by dividing the round-trip delay value (from the RADIUS record) by two.

Voice quality

The Cisco IOS software (which is installed on the router on which the H.323 gateway resides) measures call quality based on ITU G.113, which defines the term Calculated Planning Impairment Factor (ICPIF), a calculation based on network delay and packet loss. ICPIF yields a single value that can be used to gauge network impairment. ITU G.113 provides the following interpretations of specific ICPIF values:

  • 5 - Very good

  • 10 - Good

  • 20 - Adequate

  • 30 - Limiting case

  • 45 - Exceptional limiting case

  • 55 - Customers likely to react strongly

NOTE:Use the Report_CallDetail_H323Gateway script to see the ICPIF values for individual calls.

3.3.3 Resource Object

Call Data server

3.3.4 Default Schedule

By default, this script runs once.

3.3.5 Setting Parameter Values

Set the following parameters as needed:

Parameter

How to Set It

Configure Data Source

Folder containing IAS RADIUS logs

Specify the location on the Data Mart of the folder that houses the IAS RADIUS logs. This location is the one you set up when you configured IAS.

Configure Data Source Schedule

Data source schedule type

Select the frequency with which you want the Data Mart to collect data from the Data Source: Daily or Hourly. The default is Daily.

Daily start time - Run daily at

If you selected Daily above, select the time of day at which you want data collected. Select from a list of hours based on a 24-hour clock. For instance, select 0100 for 1:00 A.M. or select 1300 for 1:00 P.M. The default is 0400.

NOTE:If you have multiple Data Sources, you may want to stagger your data collection times in order to balance the load on the Data Warehouse.

Hourly time interval - Run every n hours

If you selected Hourly above, select the interval at which you want data collected, such as every 2 hours or every 8 hours. The default is 12 hours.

NOTE:If you have multiple Data Sources, you may want to stagger your data collection times in order to balance the load on the Data Warehouse.

Data Collection

Archive RADIUS logs after processing?

Select Yes to archive the RADIUS logs after their data has been processed. The default is unselected.

If you set this parameter to Yes, specify the location of the archive folder in the Archive folder parameter.

Archive folder

Specify the location on the Data Mart of the folder in which you want to archive the processed RADIUS logs.

Start data collection job immediately?

Select Yes if you want the Data Mart to collect data immediately, rather than waiting for the first scheduled collection. The default is unselected.

Start SQL Server Agent if it is stopped? (Supported on local Data Mart server only)

Select Yes to start SQL Server Agent. SQL Server Agent must be running in order for data collection tasks to be performed. The default is unselected.

NOTE:This feature is supported only when the Call Data Analysis agent and the SQL Server that hosts the Data Mart are on the same computer.

Keep data for n months

Specify the number of months’ worth of collected data you want to keep in the database on the Data Mart. The data for the current month is always kept in the database. Therefore, if you choose to keep 1 month’s worth of data, and it is December, the database will retain the data for December and November.

Customize SQL Server Access Configuration For Data Mart?

Select Yes to customize the SQL Server access configuration for the Data Mart. You will then need to specify the name of the Data Mart server in the Server name parameter below.

If you do not select Yes, the Data Mart database will be created on the same SQL Server instance as the Data Warehouse.

Server name

Specify the name of the server on which the Data Mart database will be created.

SQL username

Specify the SQL username required to access the Data Mart server. Leave this field blank to use Windows authentication.

Database name (blank for default)

Specify a name for the Data Mart database. Leave this field blank to use the default Data Mart database name.

Customize SQL Server Access Configuration for Data Warehouse?

Select Yes if you want to customize the SQL username.

SQL username

Specify the username required to access the SQL Server running on the Data Warehouse FROM the local NetIQ agent (netiqmc service) AND the SQL Server agent service running on the Data Mart computer. Leave this field blank to use Windows authentication.

NOTE:If you leave this field blank, and the Data Mart is not located on the Data Warehouse computer, verify the SQLSERVERAGENT service on the Data Mart computer is running as a user that has access to the Data Warehouse database.

Event Notification

Raise event if job succeeds?

Select Yes to raise an informational event when the AddDataSource job is successful. The default is Yes.

Event severity when job succeeds

Set the severity level, from 1 to 40, to reflect the importance of an event in which the AddDataSource job is successful. The default is 25.

Event severity when data mart server inaccessible

Set the event severity level, from 1 to 40, to reflect the importance of an event in which the Data Mart server is inaccessible. The default is 10.

Event severity for warnings

Set the event severity level, from 1 to 40, to reflect the importance of warnings raised during an attempt to add a Data Source. The default is 20.

Event severity when job fails

Set the event severity level, from 1 to 40, to reflect the importance of an event in which the AddDataSource job fails. The default is 5.