[comp.dcom.modems] getting through to a PEP last site

snoopy@sopwith.UUCP (Snoopy) (01/25/89)

In article <446@eda.com> jim@eda.com (Jim Budler) writes:
| In article <85@sopwith.UUCP> snoopy@sopwith.UUCP (Snoopy) writes:

|# One site I dial into has a TB+ setup to present PEP last.  Many times
|# it will hang up the connection before getting through all the various
|# carriers.  My TB+ waits around a bit and then returns NO CARRIER.  If
|# I manually have my system call again right away, the remote TB+ gets
|# a little further through the sequence of carriers each time, and after
|# 3-5 tries finally stays on the line long enough to connect.
|
| My manual, under the S92 instructions says that the originating modem
| must have S50=255 to call a site answering PEP last (and connect at
| PEP), AND have S7 >= 60. 

I missed the part in the manual about having s7>=60, thanks.  I had increased
it from 40 to 50 which didn't help.  After reading your article, I increased
it to 70, then 100, but all that happened was that I then got "You have
waited too long to dial, if you want to make a call, hang up and try again."
So I moved it back to 60.  Calls that succeed turn the FST (PEP) LED on
about 20-25 seconds after dialing.  On calls that fail, the other end hangs
up sooner than this.

| The length of time to successfully connect is a function of the line
| quality.

I haven't seen this, but these are local calls, so the quality should be
pretty good.  (knock on wood)
    _____     
   /_____\    Snoopy
  /_______\   
    |___|     tektronix!tekecs!sopwith!snoopy
    |___|     sun!nosun!illian!sopwith!snoopy