2 Aug
2005
2 Aug
'05
7:33 p.m.
On Tue, 2 Aug 2005 11:26:05 -0700 (PDT)
Vintage Computer Festival <vcf at siconic.com> wrote:
Still doesn't solve the multiplexing problem
(which a PBX does solve).
Unless you don't need multiplexing,
Why would you need automatic multiplexing?
With the described setup you get a maping:
TCP/IP port <=> modem <=> BBS port
I.e. each BBS port gets a different TCP/IP port. If user A is connected
to TCP/IP port 1 no other connections are accepted on that TCP/IP port.
If user B wants to connect he doesn't get a connection when telneting to
TCP/IP port 1. So he has to retry with TCP/IP port 2 etc. Not that nice
(manual multiplexing by the end user), but it is the simplest solution.
Alternative:
If you use a TCP/IP capable computer with multiserial card insted of the
terminal server you can write a custom application. It handles the
TCP/IP to serial port mapping and moving the bits back and forth of the
TCP/IP connection and serial port. It is easy to design this application
in a way that it accepts multiple TCP/IP connections to the _same_
TCP/IP port. The application keeps book on what serial lines / modems /
BBS ports are already in use so that it can connect a new TCP/IP
connection to the first free serial line == BBS port. This way you get
automatic multiplexing for the expense writing the multiplexing
application yourself.
in which case you should eat your foot for dinner.
Pardon?
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/