Ref: 08040002
Title: Interfacing 3+Remote with Rolm Phone System
Date: 07/12/88

Copyright 3Com Corporation, 1991.  All rights reserved.

We have been able to interface our 3+Remote User with a Rolm
phone system at a customer site.  The customer site is a large
complex of buildings where they have a requirement for several
people thoughout the complex to communicate through their PBX
system to a 3+ Server.

Configuration:  The Rolm phone system is used thoughout the campus
for communications, both voice and digital.  The PC would connect
to a phone set which also contains a modem.  The goal was to have
the user run a communication package (CrossTalk, SmartCom etc.)
and also be able to run 3+Remote User without rebooting the PC
or reconfiguring the modem setup.  The problem was trying to
interface with the Rolm because the phone system was set up to
be interactive with the user.  Rolm needs a character to sense baud rate
then expects a 1 letter command (when using the 240D handset).

Equipment:  We worked with the Rolm CBX-II 9004.1.50.  The Rolm rep
said we would also be compatible with models CBX-II 8003 and the
CBX-II 8004.  The handset was a 240D, which implies compatibility
with handsets 120D and 400D.  A new handset has been released by Rolm,
model 244pc; this handset is the key to our interoperability.  The 244pc
handset must be used at the workstation.  The 240D handset worked fine at
the server side.

The hand sets were configured as an Originate and Answer terminal at
19.2K.

The server was a 3S/401 with n/f/p/route and maybe mail. The
workstation was an IBM XT clone then an IBM AT clone running 3+
1.3. The remote user S/W was 1.1.1.

We were able to have the workstation log in and link from 1200
baud to 19.2.  However, the server and workstation need to be at
the same baud rate. If the server is at 19.2 the workstation must
also be defined for 19.2.  No autosensing or stepdown occurs at
the server side.  In the user's profile either null or other modem
worked and line1 was defined as "atdt 67062" (67062 was the
extension).  The server was defined as either null or other modem
also.  We also tested the compatibility between 3+Remote and
Crosstalk and were we able to switch between packages.  It was
possible to run Crosstalk then leave Crosstalk to log in to the
server without booting the PC.  You cannot have a Crosstalk
connection then establish a 3+Remote connection than switch back
to the original Crosstalk connection.  Only one commumication package has
complete control at a time.

SIDE NOTE:  It is not possible for Crosstalk to establish the connection
and exit to DOS and have Remote know the connection is already
established.  3+Remote must establish connection before 3+ software can work.

It is possible to make the 240D handset work at the workstation for
3+remote communication only, but it is not a very practical solution.
