Filter
Top Products
Chapter 4: Configuring the technology pack
50 IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.0 Technology Pack
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:
[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.
Field Description
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