Connection summaries, Originating calls (dsptotaloriginatingcalls), Answering calls (dsptotalansweringcalls) – Patton electronic 29XX User Manual

Page 148: Successful connects (dsptotalsuccessfulconnects), Failed connect prev8 (dsptotalfailedconnectprev8), Remote retrains (dsptotalremoteretrains), Remote renegotiates (dsptotalremoterenegotiates), Local retrains (dsptotallocalretrains), Local renegotiates (dsptotallocalrenegotiates)

Advertising
background image

DSP Connection Performance

148

Access Server Administrators’ Reference Guide

11 • Digital Signal Processing (DSP)

Connection Summaries

This part of the window shows DSP statistics as a whole.

Originating Calls (dspTotalOriginatingCalls)
The number of calls the DSP initiates for outbound calls.

Answering Calls (dspTotalAnsweringCalls)
The number of calls answered regardless if the call was successfully completed.

Successful Connects (dspTotalSuccessfulConnects)
The number of calls that successfully connected.

Failed Connect PreV8 (dspTotalFailedConnectPreV8)
The number of calls that failed before modulation V8 was completed.

Failed Connect PostV8 (dspTotalFailedConnectPostV8)
The number of calls that failed to connect after V8 modulation was completed.

Remote Retrains (dspTotalRemoteRetrains)
The number of times the remote modem has asked for a retrain to be done.

Remote Renegotiates (dspTotalRemoteRenegotiates)
The number of times the remote modem has asked for a renegotiation to be done.

Local Retrains (dspTotalLocalRetrains)
The number of times the local DSP has requested a retrain to be done.

Local Renegotiates (dspTotalLocalRenegotiates)
The number of times the local DSP has requested a renegotiation to be done.

Suspect—A) Transitions into suspect state (dspTotalWentSuspect)
The number of times an instance went into the suspect state. An instance will go into the suspect state when it
fails to complete several calls in succession.

Suspect—B) Recoveries from suspect state (dspTotalSavedFromSuspect)
An instance in the suspect state will recover from the suspect state as soon as it successfully takes an incoming
call.

Reboot—A) Reboots due to consecutive fails (dspTotalRebootDueToFails)
The number of times a DSP has been rebooted because it was in the suspect state and then took additional
calls which also did not connect successfully.

Reboot—B) Reboots due to error detection (dspTotalRebootDueToError)
The number of times a DSP has been rebooted because it was not responding properly to the main CPU driver
code.

Advertising