Path: utzoo!attcan!uunet!tektronix!percival!qiclab!sopwith!snoopy
From: snoopy@sopwith.UUCP (Snoopy)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit result codes
Message-ID: <85@sopwith.UUCP>
Date: 15 Jan 89 01:12:46 GMT
References: <275@ssbn.WLK.COM>
Reply-To: snoopy@sopwith.UUCP (Snoopy)
Distribution: na
Organization: The Daisy Hill Puppy Farm
Lines: 32

In article <275@ssbn.WLK.COM> bill@ssbn.WLK.COM (Bill Kennedy) writes:
| I have X3 set but I don't get any of the extended result codes
| unless I have S50 set to 255 for PEP.  Also, the modem doesn't
| give up right away on a BUSY.  I've nearly destroyed the binding
| on TFM but have not been able to find anything that says I should
| only get RRING and BUSY when I'm in PEP mode.  Could some kind
| could set me straight?  Thanks,

I get extended result codes with or without s50=255.  Sometimes my telebit
doesn't recognise a busy, other times it does.  Sometimes the busy switches
from a normal busy to a fast 'trunk' busy, (!?) and then the telebit
recognises it.

However, I never ever get NO ANSWER.  It returns NO CARRIER instead.
Has anyone else noticed this?  Not a big deal, but something isn't
quite right.

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.

Has anyone else seen this?  It seems that if it were a timer going off, it
would be the same amount of time each time.  Again, this isn't a serious
problem, uucp just keeps trying until it gets through.
    _____     
   /_____\    Snoopy
  /_______\   
    |___|     tektronix!tekecs!sopwith!snoopy
    |___|     sun!nosun!illian!sopwith!snoopy