Filter
Top Products
Multiserver 5000
126
or
Initiated by Multiserver (or remote end):
1. Calling device disconnects.
2. Multiserver drops CTS, DSR, and CD.
3. Port is marked out-of-service until device
acknowledges disconnect by dropping
then raising DTR.
AUTO (ANSWER) PROTOCOL
Call Request (Calling port attached to a dialup
modem)
Idle State: Ring (Busy at the Multiserver) is
low. Other control signal levels are
ignored. Multiserver holds CTS,
DSR, and CD off.
1. Device sends ring/no-ring cycle (RI 1
second on, 2 seconds low).
2. Multiserver raises DSR (DTR at modem)
and CTS (RTS at modem) when RI goes
low.
3. Modem raises DSR (DTR at Multiserver)
and CTS (RTS at Multiserver) within 60
seconds.
4. If ABR is enabled, <cr> should now be
typed (see Section 9.3, Asychronous
Channels).
Call Completion (Receiving port)
1. Multiserver sends ring cycles (RI 2
seconds on, 4 seconds off).
2. Device must raise DTR within 2 ring
cycles or it will be made inoperable until
it does.
3. Multiserver has 2 seconds to raise DSR
and CTS.
Disconnect Sequence
Initiated by device:
1. Device drops DTR.
2. Multiserver drops DSR and CTS.
Initiated by Multiserver (or remote end):
1. Multiserver drops DSR and CTS.
2. If Call Inhibit is on, the channel will be
marked out-of-service until device drops
DTR.
10.10 Port Contention/Queueing
Port contention allows multiple users access to a
limited number of resources.
If no resource is idle, the user will be placed in
queue for the busy ports in the primary or
secondary class.
Once in the queue, the user may receive the
current queue message (Waiting Q = your place
in the queue) by typing in any printable ASCII
character or a <cr>. The user may also exit the
queue (and return to the resource prompt) by
pressing the <break> key.