Path: utzoo!attcan!uunet!tektronix!ozvax!tekcsc!jeff
From: jeff@tekcsc.MKT.TEK.COM (Jeff Beadles)
Newsgroups: comp.dcom.modems
Subject: Re: Need tty000 modem help
Message-ID: <114@tekcsc.MKT.TEK.COM>
Date: 18 Nov 88 03:58:39 GMT
References: <4242@pitt.UUCP> <417@uncle.UUCP> <392@limbic.UUCP>
Reply-To: jeff@tekcsc.UUCP (Jeff Beadles)
Distribution: na
Organization: Tektronix, Inc.  Wilsonville, Or.
Lines: 80

In article <392@limbic.UUCP> gil@limbic.UUCP (Gil Kloepfer Jr.) writes:
 In article <4242@pitt.UUCP> anthony@pitt.UUCP (M. Anthony Kapolka 3) writes:
 [describes modem setup]
 >When I set it up (via /etc/inittab) with a getty, everything seems fine.
 >When someone calls in, however, the modem picks up the phone and then
 >promptly hangs up on the caller.
 
 [John Milton gives one explanation]
 
 Another reason why this can happen is that when a Hayes compatible modem
 is in verbose mode, and a caller calls in, the CONNECT xxx message is
 sent to the 3B1 and is subsequently echoed back to the modem.  If this
 happens fast enough on some modems (ie. the "C" in "CONNECT" gets sent back
 to the modem before the whole CONNECT xxx message is displayed), the modem
 will think you are aborting the call.  I wouldn't have even mentioned this
 except that it happened to me!

Well, here's how I have worked around this.  First, set the modem so it
does not return result codes, nor echo.  (ATE0Q1)  This will allow it to
answer (dial-in) calls ok.  In your chat script for calling, use something
like this:   ATE1Q0 OK ATDTxxxxxx NNECT ...  
This will turn the echo on, so you can tell if it's connected or not.
Then, set the modem so it will reset on DTR toggle.  (For a 2400 hayes, I
believe that it's &D?  (not sure)  On a 'Blazer, it's ATS52=2

Hope this helps,

		-Jeff Beadles


-- 
Jeff Beadles  IDG Customer Support Center  Tektronix, Inc.
jeff@tekcsc.mkt.tek.com -or-               POB 1000
 ..!tektronix!tekcsc.mkt.tek.com!jeff      Wilsonville, OR. 97070 MS 63-171
Newsgroups: unix-pc.general,comp.dcom.modems
Subject: Re: Need tty000 modem help
Summary: 
Expires: 
References: <4242@pitt.UUCP> <417@uncle.UUCP> <392@limbic.UUCP>
Sender: 
Reply-To: jeff@tekcsc.UUCP (Jeff Beadles)
Followup-To: 
Distribution: na
Organization: Tektronix, Inc.  Wilsonville, Or.
Keywords: 

In article <392@limbic.UUCP> gil@limbic.UUCP (Gil Kloepfer Jr.) writes:
 In article <4242@pitt.UUCP> anthony@pitt.UUCP (M. Anthony Kapolka 3) writes:
 [describes modem setup]
 >When I set it up (via /etc/inittab) with a getty, everything seems fine.
 >When someone calls in, however, the modem picks up the phone and then
 >promptly hangs up on the caller.
 
 [John Milton gives one explanation]
 
 Another reason why this can happen is that when a Hayes compatible modem
 is in verbose mode, and a caller calls in, the CONNECT xxx message is
 sent to the 3B1 and is subsequently echoed back to the modem.  If this
 happens fast enough on some modems (ie. the "C" in "CONNECT" gets sent back
 to the modem before the whole CONNECT xxx message is displayed), the modem
 will think you are aborting the call.  I wouldn't have even mentioned this
 except that it happened to me!

Well, here's how I have worked around this.  First, set the modem so it
does not return result codes, nor echo.  (ATE0Q1)  This will allow it to
answer (dial-in) calls ok.  In your chat script for calling, use something
like this:   ATE1Q0 OK ATDTxxxxxx NNECT ...  
This will turn the echo on, so you can tell if it's connected or not.
Then, set the modem so it will reset on DTR toggle.  (For a 2400 hayes, I
believe that it's &D?  (not sure)  On a 'Blazer, it's ATS52=2

Hope this helps,

		-Jeff Beadles


-- 
Jeff Beadles  IDG Customer Support Center  Tektronix, Inc.
jeff@tekcsc.mkt.tek.com -or-               POB 1000
 ..!tektronix!tekcsc.mkt.tek.com!jeff      Wilsonville, OR. 97070 MS 63-171