User guide

August 2001 69
Handling Incoming and Outgoing Calls
Only Wink Start and Double Wink Start protocols require a
wink to acknowledge the line seizure. A wink is on hook/off
hook/on hook sequence where the duration of the off hook must
be within a range defined by RDG_REMOTE_MIN_WINK and
RDG_REMOTE_MAX_WINK. This wink must be sent within a
time specified by RDG_REMOTE_ACK_TIMEOUT after the
seizure.
If RHT_SEIZE_LINE does not receive an appropriate wink, it
abandons the call, sends an idle pattern, and returns an error.
If RHT_SEIZE_LINE repeatedly returns an error indicating
that the wink received was out of specification, the wink
parameters are probably not set correctly.
In Immediate, Loop and Ground Start protocols, no
acknowledgment is necessary.
Glare Resolution
If the line is not idle when the application calls
RHT_SEIZE_LINE, BrktGetLastError( ) returns
BRKT_ERROR_CODE(IO_DEVICE). See Troubleshooting on page 81
for more information on how to handle the error.
It is possible for the application to try to seize the line as the CO
tries to send a call. In this situation, called a glare,
RHT_SEIZE_LINE returns an error but does not set the line
back to idle. In order to accept the incoming call, the application
calls RHT_OFF_HOOK. If it does not accept the call, it calls
RHT_DISCONNECT to set the line back to idle. Check with
your carrier to see how they want applications to handle glare
situations (also called glare resolution).