|
Avaya |
|
|
|
|
|
||
|
Avaya |
|
|
|
|
|
|
Avaya
|
Avaya |
|
|
|
|
|
||
|
Avaya |
|
|
|
|
|
|
Overview
Before installing CallData, you will have to configure the settings on your Avaya system to work with CallData.
Supported Interfaces
The CallData service connects to the Avaya system using the following interfaces:
|
TCP/IP |
Serial |
|---|---|---|
Streaming |
|
|
ODBC - Internal Database |
|
|
FTP - Flat file |
|
|
HTTP - Flat file |
|
|
Configuration Instructions
Follow these step-by-step instructions to properly configure your Avaya Communication Manager version 5.x:
| 1. | Set up your destination server node (the CallData server) with the change node-names ip command. In this example, our destination is aco54sql on 192.168.131.47. |
In this example, our destination is "aco54sql" on 192.168.131.47 |
| 2. | Setup your IP service with the change ip-services command. Create a name for the IP service (e.g. CDR2). Then specify the source (e.g. procr). This is the name of the Avaya system. Then enter the destination node from step 1 (e.g. aco54sql). This is the computer name where the CallData service is installed and set the remote port to match the port number you will have CallData configured to connect to (e.g. 8090). |
This service is called "CDR2" & the source is called "procr". Also, the Remote Node is set to match the name of the CallData server (aco54sql) & the port is set to 8090 - the port we have CallData configured to connect to. |
| 3. | Set up your CDR with the change system-parameters cdr command. On the first page, set your output type to customized and then the name of the IP service created in step 2 (e.g. CDR2). Make sure the rest of the settings match the screenshot below. |
In this example, we're calling our service "CDR2" & the Avaya server is called "procr". We also have |
On the second page, of this screen configure your CDR output. The Avaya system supports having more than one CDR output and if there is already one set for the “primary output format” (e.g. a line printer), configure the secondary output to CallData. Make sure the settings match the screenshot below.
In this example, we're calling our service "CDR2" & the Avaya server is called "procr". We also have |
Some reports may display missing or no data at all, depending on the phone system CallData is collecting data from. This is a result of non-standardized data formats being used across the wide spectrum of supported phone systems.
However, with the Avaya, there are no report compatibility issues. All reports will function properly.
See Also:
