User guide

August 2001 85
Troubleshooting
BAD_STATE_ERROR
A BAD_STATE_ERROR indicates that the function could not
execute because the line was in the wrong state for that
function. For example, ‘TermType’ would report a bad state
error if the application tries to wait for a call or send a wink
when the line is not idle. In a bad state error, the CO's
interpretation of the previous signal on the line probably didn't
match your application's interpretation.
A bad state error could also occur if the application expects a
certain event that does not occur, such as a wink after seizing
the line in some protocols. Sometimes the signal is not sent
because the CO and the application are in different states. This
could happen if the application sends a signal that does not
meet a minimum time requirement, so the CO does not
recognize the signal. The application would be in one state,
having sent the signal, but since the CO did not recognize the
signal it would not change states. Guard times generally
prevent this situation.
The field ‘RawPattern’ contains the signaling bits being sent
and received on the line. This information can help determine
why a bad state error occurred, but doesn’t explain why the
situation arose.