Managing Log and CDR Files 49
■Additional IP Messaging files you should periodically examine include:
■/usr/app/gen/app.out
■/usr/app/gen/eml_client.out
■/usr/app/gen/cpy4.out
Each of these files resets after a restart of IP Messaging. Consequently,
these files will not grow too large unless the system is extremely busy
or the system runs without a restart for a long period of time
(months).
CDR File Maintenance Storage of CDRs is not an issue if your VCX system includes a dedicated
server running the Call Records service. In this case, the Call Records
service off loads CDRs from each configured Accounting service (see Call
Records Service Overview). If, however, your VCX system does not include
a Call Records service, CDRs continually accumulate on each server
running the Accounting service.
If your VCX system does not include a Call Records service, you can
configure the Accounting service to be self-cleaning by editing the
Accounting service configuration file or modifying the appropriate SNMP
MIB variables.
To modify the Accounting service configuration file:
1Log in to the server running the Accounting service using the root
account.
2Enter the following command:
cd /opt/3com/VCX/acctxml/conf/
3Use an editor to open the following file:
acctxmlconfig.xml
4In the <CONFIGURATION_INFO> section, locate the
<BES_CDRFILE_CONFIG> subsection and find the following variables:
AUTO_CLEAN_IF_NO_LATEST_UPDATE="N"
AUTO_CLEAN_IF_NO_LATEST_UPDATE_INTERVAL="96"
The first variable determines whether or not CDRs are purged if the
Accounting service has not received notification from the Call Records
service within the time period (96 hours) specified by the second variable.
By default, the variable AUTO_CLEAN_IF_NO_LATEST_UPDATE is set to N. If
you have Call Records service configured to collect CDRs from the