This topic provides information on performing a Call Detail Recording
(CDR) file transfer. You can use CDR to create a data file that
can be downloaded, using the FTP process, from the Message Networking
server on to another system for analyzing and reporting purposes.
For more information on FTP, see Message
Networking FTP Support.
The Message Networking CDR feature writes a call detail record
for each of the following:
- Successful delivery of a message from one subscriber to another,
including digital, AMIS Analog, and Octel Analog Networking message
transfers
- Failed delivery of a message from one subscriber to another,
including digital, AMIS Analog, and Octel Analog Networking message
transfers
One week's worth of data, on average, is stored on the Message
Networking system. The exact length of time for which this data
is to be stored is determined by the value entered in the CDR Retention
field on the General Parameters page.
For a detailed list of the CDR records in format, you can generate
a CDR Subscriber Detail report.
Message Networking provides an interface that allows a system
to copy CDR data from a CDR file on the Message Networking system
to another system. CDR file transfer is done by using FTP.
Complete the following steps to create a CDR file to be used for
transferring:
- Start at the Administration menu, and select Message Networking
Administration > Call Detail Recording > Unload
CDR Data.
The system displays the Unload CDR Data page.
- Complete the fields on the page.
For information on completing the fields, click the field names
or Help on the Web-based administration page.
- Click Display.
If you previously unloaded the CDR data, a message asks if you
want to overwrite the existing CDR data:
- Click Yes to overwrite the data and display the Unload
CDR Data page.
- Click No if you do not want to continue.
Once a CDR file has been transferred from Message Networking to
your machine, to verify that the transfer has taken place, run
a cdr directory list on your machine and compare the file (for
example, file size) to the cdr subdirectory under the ICFTP_DIR
(iclog/icftp/cdr) directory list on the Message Networking system.
- Click Return to Main.
CDR file fields
The following table provides a description of the fields contained
in the CDR file.
Field
|
Length
|
Description
|
Record
Length |
3 |
Length
of the call detail record in bytes, including this field (leading zeroes),
but not including line feed. This field provides information about the record itself and is not actually stored in the database
(193). |
Record
Type |
2 |
Message
delivery detail. This field provides information about the record itself and is not actually stored in the database (04). |
Record
Version |
2 |
Version
of this record. This field provides information about the record itself and is not actually stored in the database (04).
|
Message
Networking Name |
14 |
Name of
the Message Networking machine generating this record; not actually
stored in the database. |
Message
ID |
10 |
Unique
number assigned to every message sent within a Message Networking
system; a combination of message ID, sending date/time, and
sending mailbox ID guarantees uniqueness; numbered in chunks
of 256 (511-256, etc.).
This ID remains unique across Message Networking
reboots and server updates. Numbering is recycled after 10
billion.
|
Delivery
Result |
2 |
Indicates
the delivery status. See the Delivery
Status Codes table for a list of delivery status codes.
|
Number
of Delivery Retries |
2 |
Number
of retries to deliver a message (right justified; leading zeroes).
|
Received
Date |
8 |
Date when
message was received by Message Networking (in the format yyyymmdd).
|
Received
Time |
6 |
Time when
message was received by Message Networking (in the format hhmmss).
|
Sending
Date |
8 |
Date when
successful delivery or failure occurs (in the format yyyymmdd).
|
Sending
Time |
6 |
Time when
successful delivery or failure occurs (in the format hhmmss).
|
Sending
Network Address |
30 |
Network
address of the sending machine. |
Receiving
Network Address |
30 |
Network
address of the receiving machine. |
Sending
Machine Name |
24 |
Name of
the sending machine. |
Receiving
Machine Name |
24 |
Name of
the receiving machine. |
Voice
Size |
5 |
Voice
component size in seconds (leading zeroes). |
Fax Size
|
3 |
Fax component
size in pages (leading zeroes). |
Text Size
|
5 |
Text component
size in KB (leading zeroes). |
Binary
Size |
5 |
Binary
component size in KB (leading zeroes). |
Annotation
Size |
1 |
Annotation
component size in KB (leading zeroes); the Subject line. |
Priority
|
1 |
Indicates
whether the message was sent as a priority message:
|
Private
|
1 |
Indicates
whether the message was sent as a private message: |
Line Feed
|
1 |
Line feed
for record. This is field is not actually
stored in the database. |
Delivery status codes
The following table lists the delivery status codes for the CDR
report.
Delivery
code |
Description
|
Successful
delivery |
|
00 |
Successful
delivery |
60 |
Extended
absence greeting warning |
61 |
Reply
to previous message (reserved) |
62 |
Forwarded
message (reserved) |
Failed delivery |
01 |
Connection
failure |
02 |
Mailbox
is full |
03 |
Nonexistent
subscriber |
04 |
Invalid
message attributes (message header corrupted, and so on.) |
05 |
Permissions
failure (recipient is call-answer only) |
06 |
Sending
restrictions |
07 |
Miscellaneous
delivery failure |
08 |
Multimedia
delivery failure |
09 |
Unsupported
media type |
11 |
AMIS message
length is too long |
15 |
Extended
absence greeting block |
16 |
Message
size is too large |
17 |
Future
delivery failure |
18 |
Future
expire |
19 |
Message
component delivery failure |
20 |
Message
Networking error |
21 |
Insufficient
disk capacity |
22 |
Destination
is not accepting calls |
23 |
Duplicate
subscriber |
Top of page
|