Filter
Top Products
Optimizing the Server
44 Avaya IP Telephone File Server Application Reference Guide
Figure 7: Sample .ini File Settings for CDR/BCMS
Sending end ini settings needed:
#==============================================
[HTTPS]
RunHTTPS=1
HTTPSPort=411
TLSV1=1
[BACKUP_SERVERS]
#==============================================
CDRBackup=1
BCMSBackup=1
RetainDays=7.0
UpdateInterval=2
UsePrimarySvr=1
PrimaryIP=192.168.0.13
UseSecondarySvr=0
SecondaryIP=192.168.0.11
Note: At the receiving end, the Avaya IP Telephone File Server Application must be set as a
fileserver to receive the incoming requests.
Receiving end ini settings needed:
#==============================================
[HTTPS]
RunHTTPS=1
HTTPSPort=411
TLSV1=1
[BACKUP_SERVERS]
#==============================================
FileServer=1
CDRBackup=1
BCMSBackup=1
RetainDays=7.0
UpdateInterval=2
The Avaya IP Telephone File Server Application performs most of the data relay function. With
the options sets as shown in Figure 7
, the Avaya IP Telephone File Server Application scans the
two CDRBackup or BCMSBackup directories. The Avaya IP Telephone File Server Application
creates a list of the files to be transferred. The storing end requests the list of files to be relayed
on a periodic basis. The files in the list are uploaded to an equivalent CDRBackup or
BCMSBackup directory on the file server. The receiving end then copies the data to the
MV_CDR and/or MV_BCMS application as if the data was collected locally.
Using this mechanism and the redundant database options of MV_CXDR or MV_BCMS, you
can perform highly secure and distributed management data collection.