Checking A Connection - Avaya CS700 Administration And Maintenance

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.

Checking a Connection

The ping feature on the AutoCDR server allows a client to determine actively if a connection is
open and the server running. This message is called REQUEST_PING (cmd=04), and is
padded to the same size as a REQUEST_CDR_FILE message. The server's response to this
message is to send the same message back to the client. Specifically, the server will copy the
request's rfu bytes into the response, so the client will receive whatever it sent. No further action
is taken by the server. Note that the server uses no timeout on this connection and it is not
necessary for a client to send these messages in order to maintain the connection; the ping
feature is provided merely as a means of verifying it.
The format of REQUEST_PING is:
struct request_ping
{
char cmd[2];// "04"
char rfu[11];
};
(e.g. "01")
(e.g. "01")
Real-time CDRs and CODRs
Issue 1 August 2007 297