🚀 go-pugleaf

In article <1993Jan25.121940.341@rlgsc.com>, gezelter@rlgsc.com writes:
> In article <1993Jan23.110940.1270@cmkrnl.com>, jeh@cmkrnl.com writes:
>> They also put out some release note on, I believe, DS200 3.1 code, talking
>> about the server "asserting RI [ring indicator]", when RI is of course not
>> sourced by the terminal server! 
> Are you sure that the reference to RI was not concerning the case 
> of the server providing Reverse-LAT services. On some systems, 
> the host must see RI on a dialup connection before it will 
> "answer the phone". 
>  
> In that case, the server needs to assert RI, since the server is 
> behaving as a modem, not as a host.

It may "need to", but it can't, not unless it's working (as Terry Kennedy
suggested) through a "null modem" cable.  (In which case the server asserts
some *other* signal, which is "wired through" to RI, pin 22, at the far end of
the cable.) 

Otherwise... 

A DEC terminal server can absolutely *not* assert RI, because that pin is not
wired to a line driver -- it's wired to a line receiver.  The electronics
simply aren't in the box that would allow it to provide a signal on that pin. 
This is because a terminal server is, in EIA-232 parlance, a DTE.  (You can
tell that from the fact that it has a male DB-25 connector; DCEs have female
connectors.) 

Asking it to source RI (or, for that matter, RD, CTS, or CD) is like asking a
telephone to generate ring and battery voltages.  (Very much like that, in
fact!)

	--- Jamie Hanrahan, Kernel Mode Systems, San Diego CA
drivers, internals, networks, applications, and training for VMS and Windows NT
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and 
Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIG 
Internet:  jeh@cmkrnl.com, or hanrahan@eisner.decus.org  Uucp: uunet!cmkrnl!jeh