3Com VCX V7000, Maintenance Manual

Page: 29 / 344

Call Records Service Overview 29
cdrworking4). A cdrworking file remains open until one of the following
threshold events occurs:
■
500 CDRs have accumulated
■
1 hour has elapsed
When one of these events occurs, the Accounting service closes the
cdrworking file and writes CDRs to an XML file that uses the following
filename format:
cdr<Year Month Date Hour Minutes Seconds n >_c.xml
The value for n is 1, 2, 3, or 4 depending on which cdrworking file was
the source of the collected CDRs, for example:
cdr200609210806362_c.xml
This XML file was generated on September 21, 2006 at 08:06:36 and
contains the CDRs collected by cdrworking2.
When the CDRs have been written to an XML file, the file is available for
upload to the Call Records service.
Note that, while the Call Records service checks each Accounting service
every 10 minutes, there may be no XML file available for upload (because
neither threshold event has occurred since the last upload).
You cannot adjust the cdrworking threshold limits (500 CDRs or 1 hour)
but you can change 10 minute timer used by the Call Records service to
check the Accounting services for available XML files.
You may want to adjust the timer according to the volume of CDRs your
system generates. For example, if the Accounting service never reaches
the 500 CDR threshold, a new XML file will be created every hour. In this
case, you can increase the timer from its 10-minute default to prevent the
Call Records service from needlessly checking for a new XML file.
To adjust the Call Records service timer:
1 Access the server hosting the Call Records service using the root account.
2 Enter the following command:
cd /opt/3com/VCX/bssxml/conf
3 Open the file
bssxmlconfig.xml
and find the following entry:
frequency=”600”