Enterasys Networks CSX6000 - Manual (Page 461)

Central Site Remote Access Switch 461
V ERIFYING S YSTEM O PTIONS
Call Detail Recording
• If there are no problems, check for the following system messages:
For BRI resource:
In - proceeding <#,#>
In - disconnect <#,#> - <disconnect cause>
For PRI resource:
In - accept <#,#>
In - disconnect <#,#> - <disconnect cause>
If the system reports these messages, then the network disconnected the call attempt. For
the disconnect cause meaning, refer to the
Cause Code table. If help is necessary to resolve
the reported disconnect cause, write down the “disconnect cause” and call your phone
company (carrier) to report the problem.
C ALL D ETAIL R ECORDING
The cdr verify console command is used to verify that the Call Detail Recording (CDR) feature
is operational. This command will send a sample message to all servers that have been configured
for CDR. Check the log file of each server to verify that the message was logged. The message will
be similar to the example below; additional data items may be added in future releases.
<System Name> CDR VERIFY 1 of 1
In order for the cdr verify console command to be useful, an Ethernet LAN must be operational
and an IP route to all off-node servers must be defined and operational. The command can be
performed before all the WAN equipment is in place and configured.
Additional verification can be performed by forcing the logged events to occur and checking that
they are indeed logged. This would require that all WAN equipment and configuration is in
operational order.
The Connect and Disconnect events require a successful connection; a Reject event can be forced by
supplying a bad PAP password, for example.
1. Issue the cdr verify console command.
2. If the verify fails for an off-node server, try the following:
a. Ping the syslog server to check the IP route from the CyberSWITCH to the server. (Note
that an IP route to the server must be established.) If RIP is needed to establish the route,
the route may not be available until the CyberSWITCH has been running for a minute or
two.)
b. Using the dr command, check the CyberSWITCH Report log for error messages.
c. Check that the syslogd daemon is running on the syslog server. This can be done with your
UNIX system’s process status (ps) command. This command should result in a display of
the syslogd process. If none is displayed, syslogd is not running.
d. Syslogd can be run in debug mode with the “-d” option. See your UNIX system
documentation for more information on your syslogd daemon process.