Avaya S6200 Administration And Maintenance page 249

The format of REQUEST_CDR_FILE is:
struct request_cdr_file
{
char cmd[2];// "01"
char month[3];// MMM (e.g. "Jan")
char day[2];// DD
char seqnum[5];// NNNNN (e.g. "00012")
char mode[1];// Y or N
};
The format of REQUEST_CODR_FILE is:
struct request_codr_file
{
char cmd[2];// "02"
char month[3];// MMM (e.g. "Jan")
char day[2];// DD
char seqnum[5];// NNNNN (e.g. "00012")
char mode[1];// Y or N
};
The format of REQUEST_CDR_CODR_FILE is:
struct request_cdr_codr_file
{
char cmd[2];// "03"
char cdrMonth[3];// MMM (e.g. "Jan")
char cdrDay[2];// DD
char cdrSeqnum[5];// NNNNN (e.g. "00012")
char mode[1];// Y or N
char codrMonth[3];// MMM (e.g. "Jan")
char codrDay[2];// DD
char codrSeqnum[5];// NNNNN (e.g. "00012")
};
These commands cause the server to send records for the specified day's file, beginning with
sequence # NNNNN. When the request's Mode flag is set to N, the server sends a blank record
upon reaching end-of-file (EOF). This blank record includes the requested file's date and a
sequence number of 99999, with N as the Data Valid flag in the header. However, if the
request's Mode flag is set to Y, no end of file blank record is sent. Instead, the process
continues sending records as they become available until the connection is lost or broken.
(e.g. "01")
(e.g. "01")
(e.g. "01")
(e.g. "01")
Real-time CDRs and CODRs
Issue 1 August 2007 249