IBM R2E2 manual DataChannel host that requested them

Page 57

 

 

Chapter 4: Configuring the technology pack

 

 

 

 

Field

Description

 

 

 

 

 

 

 

resend_sent_files

If true, the CUCM server will re-send files that it has already successfully

 

 

sent. Since the CUCM can be configured to send data files to any host

 

 

specified by CUCM Web administration configuration settings, this field

 

 

must be set to true to ensure that data files are also sent to the

 

 

DataChannel host that requested them.

 

 

Use the false setting in the following situations:

 

 

• If you prefer to have the data files pushed back to the DataChannel host

 

 

according to a schedule specified by CUCM Web administration

 

 

configuration settings. Set the CUCM configuration to push the data

 

 

files back to the DataChannel server where the ProvisoCUCM instance

 

 

is running.

 

 

• If data files are being pushed back to the DataChannel host too slowly

 

 

for your needs.

 

 

If this field is false, the ProvisoCUCM instance will request the data files

 

 

from the CUCM server and receive none. It will then check for the data files

 

 

in the location specified by the CUCM Web administration configuration (at

 

 

time intervals specified by run_interval or perfmon_interval). If

 

 

the files are there, ProvisoCUCM retrieves the files and generates the CSV

 

 

output to cdr_output_dir (or perfmon_output_dir with Perfmon

 

 

data) on the DataChannel host that requested the data.

 

 

Example: resend_sent_files=true

 

run_interval

The interval, in milliseconds, at which ProvisoCUCM polls the CUCM

 

 

server for CDR and CMR data files, and checks cdr_output_dir for data

 

 

files pushed there by the CUCM server.

 

 

Example (15 minutes): run_interval=900000

Note: Before proceeding to the next step, be sure you have configured each cucm.properties file in the directories you created in Step 6.

9.CUCM environment only: Start all ProvisoCUCM applications by running the startcucm.sh file in each directory that you created in Step 6.

ProvisoCUCM writes a log file in the same directory where its ProvisoCUCM.jar file is located. Monitor the log file to make sure that ProvisoCUCM is successfully communicating with the CUCM server. Also, verify that CSV files are being generated to the output directories (cdr_output_dir and/or perfmon_output_dir).

Note: Be sure that all ProvisoCUCM instances are operating successfully before proceeding to the next step.

10.Define global variables.

Global variables are specific to each CCM or CUCM cluster. You assign values to global variables in either of the following files:

CCMConfig.js. with CCM clusters

CUCMConfig.js with CUCM clusters

The Cisco IP Telephony Technology Pack includes the configuration files CCMConfig.js and CUCMConfig.js. In Step 2-e,you copied these files to

DATA_CHANNEL_HOME/scripts/voip_cisco_ipt (typically, /opt/datachannel/scripts/voip_cisco_ipt).

IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.0 Technology Pack

53

Image 57
Contents IBM Copyright IBM Corp Contents Contents Organization AudienceTivoli Netcool/Proviso documentation Tivoli Netcool/Proviso product suiteSummary of Device Technology OverviewCategories of Service Reporting Source of Collected Data Collection Type Sources of Collected DataPort for SQL Access Troubleshooting Note for SQL RequestsDevices and Services Prerequisites Snmp AccessBulk input file formats Supported MIBsBulk input file name Bulk input file schemaBulk adaptor design files Devices and Services Reporter sets Supported Reports and KPIsReporter set summary Reporter set tree Reporter set contents Cluster Quality Resource Cluster Call Distribution ResourceCluster Call Distribution Group Top 10 Cluster Call Completion Cluster Quality GroupCluster Utilization Group Top 10 Cluster Number of Calls Top 10 Cluster Number of ErrorsCluster VoiceMail Usage Resource Cluster IP vs Legacy ResourceCluster Erlang-B Group Cluster Utilization MLH ResourceExtension CDR Utilization Resource CDR Quality ResourceTop 10 CDR Number of Errors CDR Call Distribution ResourceTop 10 CDR Number of Calls Top 10 CDR Call Completion CDR VoiceMail Usage ResourceTop 10 CDR Call Duration CDR Quality GroupCDR Call Distribution Group Factor Factor ResourceFactor Group Top 10 CDR K-Factor Codec Errors on Cluster by CodecCallManager Server CCM Server Quality Resource CCM Sql Server ResourceCCM Sql Server Group Pstn Gateway E1/T1Availability Resource Pstn Gateway Interface Top 10 E1/T1 Utilization ResourcePstn Gateway E1/T1 Interface Utilization Resource Device Pstn Gateway Device Quality ResourceDSP Card Pstn Gateway DSP Card Resource Pstn Gateway Availability ResourceMedia Devices Media Device Resource Media Device GroupGatekeeper Device Quality Resource Gatekeeper Availability Resource Gatekeeper Availability Resource Detail ChartGatekeeper Interface Availability Resource Gatekeeper Interface Utilization Resource Detail ChartGatekeeper Interface Utilization Resource Perfmon Perfmon Active Calls ResourcePerfmon Active Calls Group Perfmon Security GroupPerfmon Security Resource Perfmon Pstn Group Perfmon Pstn ResourcePerfmon MOH Resource Perfmon MOH GroupKey performance indicators Key performance indicatorsCCR Supported Reports and KPIs Key performance indicators ClusterLocalCall Key performance indicators ICR Unknown or unsupported protocol Mlqk MOS SCS Key performance indicators Before you begin Configuring the technology packCd /opt/datamart Configure the technology packOpt/datamart/dataMart.env Pvm YourDataSource1 Driver=PVmsss20.so Generates output from a CDR file and its associated CMR file If true, ProvisoCUCM requests CDR and CMR data from the Cucm Request DataChannel host that requested them Report navigation by customer Name you pass to the object Tivoli Netcool/Proviso v4.4.3 and later Where Datachannelhome Specifies the channel number for example, 1 that you Success message Meaning Syntax item Verifying resources Device.instance.schema.parametername Description InstancesComponent ValueVoipciscoipt Instances VOIPCISCOIPT.CCMINPUT.DELETEONACQUIRE VOIPCISCOIPT.CCMINPUT.URI VOIPCISCOIPT.CDRINPUT.DELETEONACQUIRE VOIPCISCOIPT.CDRINPUT.URI VOIPCISCOIPT.DESIGNFILE VOIPCISCOIPT.DESIGNFILE VOIPCISCOIPT.INPUTDIRECTORY VOIPCISCOIPT.INPUTDIRECTORY VOIPCISCOIPT.INPUTFTPPASSWORD VOIPCISCOIPT.INPUTFTPUSERNAME VOIPCISCOIPT.INPUTHOST VOIPCISCOIPT.INPUTHOST VOIPCISCOIPT.INPUTUSESECUREFTP VOIPCISCOIPT.INPUTUSESECUREFTP VOIPCISCOIPTPERFMON.DESIGNFILE VOIPCISCOIPTPERFMON.INPUTDIRECTORY VOIPCISCOIPTPERFMON.INPUTFTPPASSWORD VOIPCISCOIPTPERFMON.INPUTFTPUSERNAME VOIPCISCOIPTPERFMON.INPUTHOST VOIPCISCOIPTPERFMON.INPUTUSESECUREFTP VOIPCISCOIPTPERFMON.PERFMON.DELETEONACQUIRE VOIPCISCOIPTPERFMON.PERFMON.URI Pack-specific UBA parameters Template file name and locationUBA Parameter Value Meaning Additional information about UBA parametersDbusername URIExample UBA.1.101.VOIPCISCOIPT.CCMINPUT.DELETEONACQUIRE=false Page Page Trademarks Copyright IBM Corp Page Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK Additional Copyright InformationAdditional Copyright information Scotty 2.8, incrTCL 3.0, incr TCL BLT 2.4uUCD Snmp Regex 1.1a JdomXwpick Page IBM