Article View: comp.dcom.sys.cisco
Article #388Using a high-speed modem on an ASM terminal server.
From: Ray Piworunas
Date: Wed, 02 Sep 1992 20:39
Date: Wed, 02 Sep 1992 20:39
73 lines
2921 bytes
2921 bytes
I have an ASM-32 that I am trying to get a "FaxModem" made by ZOOM Telephonics, Inc. to work on. I can't seem to establish a connection above 9600-baud. I would appreciate any help readers of this group could give. I'm not trying to do FAX transfers, just ordinary data connections. The serial line of the ASM the modem is on is setup as follows. # # Fast modem. # line 40 access-class 1 out no private exec-timeout 2 session-timeout 45 modem ri-is-cd flowcontrol hardware autobaud databits 8 parity none stopbits 1 length 24 width 80 terminal-type dialup location TCC 2B - 14400-baud (MNP) dialup. I have wired the serial connection as shown below. ASM-32 Modem --------------------- SG (7) SG (7) TD (2) RD (2) RD (3) TD (3) RI (22) CD (8) DTR (20) DTR (20) CTS (5) CTS (5) The modem has the following settings (other than the factory defaults): &C1 Have CD follow condition of modem carrier. &D3 Reset modem after DTR drops. S0=1 Set for auto-answer. S36=5 Attempt an MNP connection, if it fails attempt an asynchronous (direct mode -- don't buffer data) connection. These settings were saved as configuration zero. I have been able to establish connections to the ASM at: 2400-baud, using a 2400-baud modem (Practical Peripherals PM2400SA), 4800-baud, using a Prometheus ProModem 9600-EC, 9600-baud, using a Prometheus ProModem 9600-EC. Once at the ASM prompt things work as they should. I can't establish a connection to the ASM at 19200-baud, nor at 38400-baud. From looking at the ASM port (using sh li 40) at various times during the connection attempt it appears the ASM is in its autobauding mode. It can't seem to lock on to the right speed. Occasionally it will show that the line has received a BREAK. I have tried setting the ASM line to a speed of 38400 instead of autobauding but that didn't help any with the attempt to connect at 38400. (I didn't try a slower speed connection with the ASM port at 38400 since the 38400 connection didn't work). I'm not sure if the error correction, or compression, at the higher speeds might be messing things up since I've never worked with these features before. It seems that that shouldn't be a problem in just getting to the terminal server prompt though. Well that's as far as I've gotten with it. I'm pretty well stuck right now. If you need more information please ask (I know I do!). Thank you, Ray Piworunas (ray@nmt.edu).
Technical Details
Message-ID:
<1992Sep2.203948.25107@nmt.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!usc!cs.utexas.edu!asuvax!ncar!mimbres.cs.unm.edu!nmt.edu!rayShow Full Headers
Complete Article Headers
Newsgroups: comp.dcom.sys.cisco Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!usc!cs.utexas.edu!asuvax!ncar!mimbres.cs.unm.edu!nmt.edu!ray From: ray@nmt.edu (Ray Piworunas) Subject: Using a high-speed modem on an ASM terminal server. Message-ID: <1992Sep2.203948.25107@nmt.edu> Organization: New Mexico Institute of Mining and Technology (NM Tech). Date: Wed, 2 Sep 1992 20:39:48 GMT Lines: 74