Cabletron Systems CSX1200, CSX1000 manual Call Detail Recording

PROBLEM DIAGNOSIS

Call Detail Recording

If there are no problems with actions 1 and 2, proceed to action 3.

3.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.

CALL DETAIL RECORDING

Problem:

The cdr verify command fails for an off-node server.

Action:

1.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.)

2.Using the dr command, check the CyberSWITCH Report log for error messages.

3.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.

4.Syslogd can be run in debug mode with the “-d”option. See your UNIX system documentation for more information on your syslogd daemon process.

5.If syslogd is running but does not receive any log messages, make sure CDR is configured for the UDP port that syslogd is using. The typical port is 514, but some versions of syslogd may use a different port.

6.Check that the priority value that you assigned in the CFGEDIT Call Detail Recording menu (default of 38) matches the priority setting on your syslog server (default of auth.info).

Workgroup Remote Access Switch 411