The system uses database DIPs to communicate with databases (one DIP per database). These DIPs need to be supplied with information regarding where and how to access the databases. The DIP configuration is managed entirely from the Web Administration interface.
You can have call information alternatively stored in a Call Data Handler (CDH) flat file where it can either be read directly or uploaded into a database. The upload to a database can be done at a convenient (low traffic) time using a cron job.
Configuring a database DIP
The browser displays the JDBC Administration - Main screen.
The browser displays the JDBC Administration - Edit screen for the DIP you chose.
The browser displays the DIP Start Status screen, which shows whether or not the DIP has started.
The browser displays the DIP Stop Status screen, which shows whether or not the DIP has stopped.
Configuring CDH
If a flat file is always used, the flat file needs to be configured:
The browser displays the JDBC Administration - Edit screen.
If you enable File CDH, the information saved in the flat file is always stored in the database accessed by the database DIP you chose.
Note:
Since enabling File CDH results in heavy LAN traffic, Avaya does not recommend doing this in most cases.
To enable File CDH:
The browser displays the DIP Start Status screen, which notifies you if the DIP has successfully started.
To disable File CDH:
The browser displays the DIP Stop Status screen, which notifies you if the DIP has successfully stopped.
In some cases, you may want to create your own customized database DIP to run with a database. This DIP would use the CDH flat file as its source of call data.
To configure the DIP:
The browser displays the Database DIP Configuration - Edit screen.
To activate the DIP:
The browser displays the DIP Start Status screen, which notifies you if the DIP has successfully started.
To deactivate a DIP:
The browser displays the DIP Stop Status screen, which notifies you if the DIP has successfully stopped.