The Autocdr Process - Avaya CS700 Administration And Maintenance

Managing Reports

The autocdr Process

When the Automatic CDR Print parameter (see
LAN, the Auto CDR server begins the autocdr process after each reboot (re-initialization or
shutdown). Once begun, this process finds the listen port number in the /etc/services file and
listens for remote client (host) requests on that port.
Subsequent connection requests trigger a connection to the remote client, and the process
looks up the host address in the /etc/hosts file. If no match is found, the server disconnects from
the remote host and waits for other connection requests. However, if the server locates the host
address, the process waits indefinitely for a socket command. When command data begins to
arrive, the process waits up to 15 seconds between command bytes before timing out. If the
server does time out waiting for command data, it maintains the connection and waits for a new
command from the client.
Each request from the client includes a command number, the starting date(s), the starting
record number(s) and the autocdr mode. The process opens the file, seeks the starting
sequence number, then sends the data across the established connection to the remote host.
Replies to commands are CDRs and/or CODRs, starting from the requested record in the file of
the specified date, including all records in all files written after this date. Note that no records
from files with earlier dates are sent. If a client requests both CDRs and CODRs, CDRs for the
earliest day are sent first, then CODRs for the same day, then CDRs for the next day, and so
forth.
Command processing from this point depends on the Mode flag in the request string:
If Mode flag = N, the server processes each command synchronously: the server
l
completes each request, then returns to listening for another command.
If Mode flag = Y, the server processes the request as above, then stops listening for
l
commands and sends records to its client asynchronously, as they are generated, until the
client closes the connection. If the requested sequence number is invalid, the process
waits and sends the next record the system generates.
If the connection breaks, any subsequent records are not sent. To transfer these files,
re-establish connection and issue a request, specifying the date, starting sequence number,
and mode.
Note:
It takes up to 45 seconds to re-establish a lost or broken connection.
Note:
294 Administration and Maintenance of the CS700/CS780 Audio Conferencing Server
System Configuration on page 45) is set for