Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!ihlpf!mhw
From: mhw@ihlpf.ATT.COM (Marc Weinstein)
Newsgroups: comp.sys.att
Subject: Re: PC 7300: Phone Manager vs. uucp
Message-ID: <1982@ihlpf.ATT.COM>
Date: Mon, 17-Aug-87 18:36:53 EDT
Article-I.D.: ihlpf.1982
Posted: Mon Aug 17 18:36:53 1987
Date-Received: Wed, 19-Aug-87 01:29:53 EDT
References: <2772@hcr.UUCP>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 47

in article <2772@hcr.UUCP>, tom@hcr.UUCP (Tom Kelly) says:
> 
> I too have been looking for a way to switch the phone line from
> VOICE 1: IDLE to DATA 1 without human intervention.  I have discovered
> that killing the Phone Manager process (ph) and removing the LCK..ph0
> file does the trick, in that uucp will now use the line on demand.
> Furthermore, the line is no longer automatically answered.
> 
> I would prefer a more elegant way, partly because cu(1) doesn't seem
> to work, and I like using the phone manager for terminal emulation
> because you can swap between the remote session and a local unix session.
> 

If you get the latest version of the phone manager (3.5.1), it comes with
a program called phtoggle, which toggles the line from VOICE to DATA.  I
have set up cron jobs to do this at certain times of the day and all the
systems which talk to mine have Systems entries which correspond to these
times.  Uucp will basically wait until the line has been set to DATA, which
isn't all bad.  If you really want something to go out, I typically queue
up a bunch of stuff and then do a Uutry to the system I'm interested in
(after toggling the phone line).  You can also set up a job (perhaps in
cron) or a shell which you can execute at will to first toggle the
line, then do a uucico (or cu), then toggle the line back.

> The basic problem is that sometimes the modem seems to get into a strange
> state.  A symptoms of this state are that when uucp is dialing, I can hear
> the dial tone and ringing (as I can when ph is dialing for me).
> 
> Sometimes I can clear the condition by toggling between VOICE and DATA
> mode.  Sometimes that doesn't work, but I can do it by killing ph and
> restarting it.  Sometimes nothing seems to work short of a reboot (which
> so far has always worked).
> 

Several of us have seen this problem (or a similar problem).  The most
bothersome effect is that the modem refuses to answer, even in DATA mode.
I think it might involve a situation where the OBM is attempting to call
another system when a call comes in.  I think it gets confused and the modem
and/or the getty do not get reset correctly.  I've noticed the same thing with
toggling VOICE to DATA and back - it seems to clear the problem most of
the time.

Have you called the hotline?? There may be a fix available...

Marc Weinstein
Bell Labs - Indian Hill, Naperville, IL
ihnp4!ihlpf!mhw