User`s guide

Small Office Remote Access Switch 323
C ONFIGURING O THER A DVANCED O PTIONS
Log Options
.2, and so on up to .10. The file extension cycles through the values 1 through 10 with each write
command, similar to the current report log file and status log file, so that the ten most recent
versions of the CDR log are available on the system disk.
There are five ISDN CDR events that are logged: connect, disconnect, reject, system up, and verify.
For each type of event that is logged, related CDR information is provided.
A report always refers to the particular device at the other end of the WAN connection. There is an
important distinction between CDR on an interconnect device and CDR on a terminal server. The
remote device for an interconnect device is the device on the other end of the WAN connection, not
the human user or the client PC. For example, in the diagram below, it is Bridge that is the system’s
remote device, not Client1 (the machine) or Client2, and not the user, who is using Client1.
A CDR report contains a variety of data items related to an associated CDR event. Some reports
consist of more than one record.
Call Detail Recording Events
This section describes CDR events for switched ISDN services. There are five ISDN CDR events:
connect, disconnect, reject, system up, and verify.
A connect event occurs when the system authenticates the remote device of an ISDN connection.
The time stamp for the connect event marks the time the ISDN connection was established.
A disconnect event occurs when the system disconnects a connected device. The disconnect
timestamp marks the time that the decision to disconnect was made.
A reject event occurs when the system disconnects an ISDN connection for which no device was
authenticated. The reject timestamp marks the time that the decision to disconnect was made.
A system up event occurs when the system is loaded. The system up event provides a visible
divider in the log file between two instances of loading the system. Since the connection ID value
is a counter that begins at zero when the system is loaded, it is necessary that the log file contain an
indication of when the system is loaded.
A verify event is generated by issuing the
cdr verify console command. This command verifies
the configuration of the CDR feature. It causes a message to be sent to all configured CDR log
servers. The proper logging of the message can then be inspected to verify that CDR configuration
is as desired.
ISDN
Client 1
Client 2
Bridge
Server
Remote Device
CSX150