AltiGen MAXCS 7.0 CDR - Manual (Page 14)

Configuration Areas Affecting CDR Information
10 CDR Manual
Migration.
If you are upgrading from OE 4.5 or earlier, you will not be
provided with any conversion tool for CDR records stored under OE 4.5 or
prior releases.
Extension-to-Extension Call Reporting.
CDR Search includes
records for internal calls between extensions, and from internal extensions
to workgroups. This is in addition to information on incoming and outgoing
trunk calls.
SMDR Cautions.
SMDR is a Mitel-defined data schema for delivering
basic call information out the RS232 serial port to external recording and
reporting applications. While AltiGen has provided an SMDR interface, it
has had many problems in terms of accuracy and consistency of
information delivery. SMDR is not CDR. CDR is historical, and is a
database containing call records. SMDR is a real time delivery of a subset
of this information. We recommend that you use the new CDR, not the
SMDR, for reporting and billing applications. No improvements or
corrections have been made to SMDR.
Configuration Areas Affecting CDR Information
How calls are routed in outcall routing is reflected in the CDR record. The
route names configured in MaxAdmin will appear in the route table name
area of the records.
Multi-Project Naming
Each extension table entry in MaxAdmin has a field to identify the
extension owner. If a name is placed in this field, that name will be used in
the CDR record to represent the project or department associated with the
particular extension.
Wrapup
Setting the wrapup time or supporting AltiX ActiveX controls can affect
the level of CDR information. For example, using ActiveX for
AltiLinkPlus, a client application can place wrapup data into the User
Defined data field of the CDR record. This is useful if the user wants to
correlate business information with call handling information; revenue
achieved versus talktime by agent. A system integrator is required to use
AltiGen’s AltiX ActiveX control.