IBM R2E2 manual Generates output from a CDR file and its associated CMR file

Page 54

Chapter 4: Configuring the technology pack

Field

Description

 

 

 

 

[Data Source Name]

The configuration of the specified data source.

 

[Data Source Name]: for example, [SANFRANCISCO]

 

Address: the remote IP address and TCP port of the CallManager Publisher

 

Database (for example, 192.168.1.1,1433). To verify the remote connection

 

configuration, establish the connection manually from a shell window: telnet

 

xx.xx.xx.xx 1433 or telnet xx.xx.xx.xx 1370. The remote TCP

 

port can be 1433 or 1370 according to the SQL Server configuration.

 

 

[ODBC]

A global section that defines the global environment for the bridge.

 

 

Important: If you do not have a CUCM environment, skip Step 6 through Step 9, and continue with Step 10.

6.CUCM environment only: On the DataChannel host, create a directory for each CUCM server from which CDR, CMR, and Perfmon data files will be requested. For example, if you will be requesting data files from two CUCM servers, you might create the following directories:

/opt/datachannel/cucm1

/opt/datachannel/cucm2

These directories will contain the ProvisoCUCM application and other files needed to send SOAP requests to each CUCM server.

Note: If you will be requesting CDR and CMR data files through a master CUCM server, you need to create just one directory for those requests. However, if you will be requesting Perfmon data, you must create a separate directory for each CUCM server from which you will request Perfmon data.

7.CUCM environment only: Copy the following files into each one of the directories you just created in Step 6:

ProvisoCUCM.jar

cucm.properties

startcucm.sh

stopcucm.sh

These files were included in the technology-specific files you copied to

DATA_CHANNEL_HOME/scripts/voip_cisco_ipt in step 2-e on page 47.

8.CUCM environment only: Configure each of the cucm.properties files you copied in Step 7.

Each cucm.properties file is associated with an instance of the ProvisoCUCM application that is located in the same directory as the file. The ProvisoCUCM instance reads the cucm.properties file to find the address and login credentials of the associated CUCM server, the address and login credentials of the DataChannel host for the CUCM server to use when pushing the requested files via FTP back to the DataChannel host, and other required configuration details.

The following table describes the fields in the cucm.properties files:

Field

Description

cdr_output_dir

The location on the DataChannel host where the ProvisoCUCM instance

 

generates output from a CDR file and its associated CMR file.

 

The output is a single CSV file that contains correlated data from the CDR

 

file and CMR file.

 

Example: cdr_output_dir=/opt/uba/cdrcmr

50

IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.0 Technology Pack

Image 54
Contents IBM Copyright IBM Corp Contents Contents Audience OrganizationTivoli Netcool/Proviso product suite Tivoli Netcool/Proviso documentationOverview Summary of Device TechnologyCategories of Service Reporting Sources of Collected Data Source of Collected Data Collection TypeTroubleshooting Note for SQL Requests Port for SQL AccessDevices and Services Snmp Access PrerequisitesSupported MIBs Bulk input file formatsBulk input file schema Bulk input file nameBulk adaptor design files Devices and Services Supported Reports and KPIs Reporter setsReporter 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 Cluster VoiceMail Usage Resource Top 10 Cluster Number of ErrorsTop 10 Cluster Number of Calls Cluster IP vs Legacy ResourceExtension CDR Utilization Resource Cluster Utilization MLH ResourceCluster Erlang-B Group CDR Quality ResourceTop 10 CDR Number of Errors CDR Call Distribution ResourceTop 10 CDR Number of Calls Top 10 CDR Call Duration CDR VoiceMail Usage ResourceTop 10 CDR Call Completion CDR Quality GroupCDR Call Distribution Group Factor Factor ResourceFactor Group Codec Errors on Cluster by Codec Top 10 CDR K-FactorCallManager Server CCM Server Quality Resource CCM Sql Server ResourceCCM Sql Server Group Pstn Gateway E1/T1 Interface Utilization Resource Pstn Gateway Interface Top 10 E1/T1 Utilization ResourcePstn Gateway E1/T1Availability Resource Device Pstn Gateway Device Quality ResourceMedia Devices Media Device Resource Pstn Gateway Availability ResourceDSP Card Pstn Gateway DSP Card Resource Media Device GroupGatekeeper Device Quality Resource Gatekeeper Availability Resource Detail Chart Gatekeeper Availability ResourceGatekeeper Interface Utilization Resource Gatekeeper Interface Utilization Resource Detail ChartGatekeeper Interface Availability Resource Perfmon Perfmon Active Calls ResourcePerfmon Active Calls Group Perfmon Security GroupPerfmon Security Resource Perfmon MOH Resource Perfmon Pstn ResourcePerfmon Pstn Group 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 Configuring the technology pack Before you beginConfigure the technology pack Cd /opt/datamartOpt/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 Component InstancesDescription 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 Template file name and location Pack-specific UBA parametersAdditional information about UBA parameters UBA Parameter Value MeaningURI DbusernameExample UBA.1.101.VOIPCISCOIPT.CCMINPUT.DELETEONACQUIRE=false Page Page Trademarks Copyright IBM Corp Page Additional Copyright Information Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TKAdditional Copyright information BLT 2.4u Scotty 2.8, incrTCL 3.0, incr TCLUCD Snmp Jdom Regex 1.1aXwpick Page IBM