Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!hsdndev!wuarchive!cs.utexas.edu!uunet!beartrk!cjp
From: cjp@beartrk.beartrack.com (CJ Pilzer)
Newsgroups: comp.dcom.modems
Subject: Re: Problem getting Hayes V-Series Smartmodem 9600 to connect to T2500
Summary: Set up S9 and S10 to avoid premature disconnect
Message-ID: <449@beartrk.beartrack.com>
Date: 6 Jan 91 06:41:08 GMT
References: <567@fciva.FRANKLIN.COM> <SALC.91Jan3133905@aristotle.shearson.com>
Distribution: na
Organization: Bear Track Computer Co., Takoma Park, MD.
Lines: 16

In article <SALC.91Jan3133905@aristotle.shearson.com>, salc@aristotle.shearson.com (Sal Cataudella) writes:
> I seem to be having the same problem too with my Hayes Ultra 9600 modem.
> When I dial up to my unix host, (which has a Telebit TrailBlazer) a connection
> is made, but is quickly lost; the message 'NO CARRIER' is displayed.
> My modem is connected to a NeXT cube. Is there anyone out there that has a 
> simple answer to this problem?
I had a simular problem with a Hayes Smartmodem 2400.  I think the problem is
that by the time the T2500 gets through the PEP tones and the answer tone, the
Hayes has timed out.  I solved the problem by setting S9=30 and S10=50.  
Something less might be OK, but this works.  Make sure that S7 is not less
than 30.  S10 must be greater than S9 because the actual loss of carrier
that can be tolerated is the difference between S10 and S9.  

Since I have done this I get 100% connection.

-- cjp@beartrk.beartrack.com