3Com V7000 The file naming convention uses this format:

40 CHAPTER 2: CONFIGURING THE CALL RECORDS SERVICE
Viewing CDRs CDRs are stored on the server hosting the Accounting service. In a
multi-site VCX system, the CDRs gathered by multiple Accounting
services and stored on multiple servers can be sent to a single Call
Records service.
To view a CDR stored on a server hosting the Accounting service:
1Log on to server hosting the Accounting service as cworks.
2The CDRs are stored in the /opt/3com/VCX/acctxml/db/export directory.
The newest CDR is listed last and looks similar to the following:
cdr200504111533531_c.xml
The file naming convention uses this format:
o5 OUTBOUNDENDPOINTTYPE Indicates the type of outbound end
point.
2 – Gateway
6 – Terminal
9 – Call processor
10 – Others
11 – Unknown
12 – Redirect call processor
13 – IP Messaging server
2
o6 TRANSFEREDTOURI URI that a call was transferred to. 74000002
o7 TRANSFERINGPARTYURI URI of the transferring Transferring
Party URI
74000003
o8 REFERENCECALLID This is the reference text call ID for
when silent monitor and barge in is
used.
Not supported in this release.
N/A
o9 FORWARDINGPARTYURI Forwarding party URI.
Not supported in this release.
N/A
p1 GROUPNAME The name of a hunt group that was
defined when it was created.
1stShift
p2 CALLQUEUEEXITTIME The call queue exit time in a hunt
group - the time stamp filed.
Not supported in this release.
N/A
p3 MEMBEREXTENSION The member extension used in a
hunt group.
21113
Tabl e 7 CDR Field Descriptions and Values (continued)
Tag Variable Description and Values Example