Xref: utzoo comp.sys.att:7576 unix-pc.general:3731 unix-pc.uucp:146
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!usc!ucsd!ames!vsi1!zorch!galaxia!cals01!cals
From: cals@cals01.NEWPORT.RI.US (Charles A. Sefranek)
Newsgroups: comp.sys.att,unix-pc.general,unix-pc.uucp
Subject: Re: How do you check if ph0 is set to DATA?
Message-ID: <512@cals01.NEWPORT.RI.US>
Date: 14 Sep 89 02:01:37 GMT
References: <2938@puff.cs.wisc.edu> <4185@ditka.UUCP>
Reply-To: cals@cals01.Newport.RI.US (Charles A. Sefranek)
Distribution: usa
Organization: My Very Own Castle, Portsmouth RI
Lines: 26

In article <4185@ditka.UUCP> kls@ditka.UUCP (Karl Swartz) writes:
>...
>I was under the (possibly misguided) impression that due to
>software bugs ph0 didn't work very well as a data line. 

Yup, you're misguided. I *only* use ph0, mostly as a DATA line.
It works great, has been for 2 yrs now.  Took some tuning up
though to find all the error possibilities and take care of them.

Use phtoggle to switch ph0 between DATA and VOICE.  Phtoggle comes
with the ua.  Use a program called phstat to check whether the line 
is currently set up as DATA or VOICE (or VOICE-ACTIVE, or RINGING, etc). 
Phstat was posted to the net a while back.  I suppose I could repost my
hacked up version of it if there's enough interest...

As I said above, an IMPORTANT part of this is the shell script needed
to coordinate the activity of phstat, phtoggle, and uucp (I don't have
HDB).  There are a number of obscure and subtle conditions that will cause
errors if you don't check for them and handle them properly.  Email me
for more info, I can post if there's enough interest...
-- 

--
 Charlie Sefranek	cals@cals01.NEWPORT.RI.US
UUCP: {rayssd,xanth,lazlo,mirror}!galaxia!cals01!cals
Alt.: c4s@rayssdb.ray.com {sun,decuac,gatech,necntc,ukma}!rayssd!rayssdb!c4s