V4.3.2 UUCP (cu) Problem

V4.3.2 UUCP (cu) Problem

Post by Jeff Shirle » Thu, 28 Oct 1999 04:00:00



Greetings.

I just did a migration upgrade of a few systems from AIX V3.2.5 to V4.3.2,
and am having a problem with the cu command.  The format used is:

cu -l<tty> -s<baud-rate> <phone-number>

A specific example:

cu -ltty0 -s2400 5551212

This worked fine under V3.2.5, and would cause the modem connected to the port
to dial and establish a connection to a remote modem.  The same command in
V4.3.2 always returns:

cu: 0835-028 The connection failed. CALLER SCRIPT FAILED.

Using the same command with debugging turned on (-d) yields:

altconn called
Device Type ACU is wanted
ttylock tty0 succeeded
Attempting to open /dev/tty0
clear O_NDELAY
filelock: ok
fixline(8, gdial(hayes) called
expect: ("")
got it
Sendthem (DELAY
A)
expect: (OK)
timed out
set interface UNIX
ttylock ttyx1 succeeded
Attempting to open /dev/ttyx1
generic open failed, errno = 2
set interface UNIX
ttylock tty0 succeeded
Attempting to open /dev/tty0
clear O_NDELAY
filelock: ok
fixline(8, gdial(hayes) called
expect: ("")
got it
Sendthem (DELAY
A)
expect: (OK)
timed out
set interface UNIX
getto ret -1
cu: 0835-028 The connection failed. CALLER SCRIPT FAILED.
call cleanup(1)
call _mode(0)

The "A)" line sometimes appears as "?)" or "???)".  I never see anything I
recognize from the Dialers file.  I hooked up a serial data analyzer between
the port and the modem, and see no data transfered whatsoever.  The symptom
persists with my setup files (/etc/uucp/*) from V3.2.5 (which work fine under
V3.2.5), and fresh files from the V4.3.2 CDROM.  The command:

cu -m -l<tty> -s<baud-rate>

works fine, and I am able to send commands to the modem and get a response.
Anybody else out there seen this?  Any hints would be appreciated.

Jeff.
--
NOTICE TO BULK EMAILERS:  I am really getting tired of your junk email.  It
costs me both time and money.  Send spam to me, and I WILL GET YOUR OPERATION
SHUT DOWN.  So far, 46 web sites deleted.  Who's next?


          Remove the "x" characters from my email address when replying
         ** UNSOLICITED COMMERCIAL/PROMOTIONAL EMAIL IS NOT ACCEPTED **

 
 
 

V4.3.2 UUCP (cu) Problem

Post by John Jaszcza » Fri, 29 Oct 1999 04:00:00


  I don't have V3 manpages, so I can't confirm that a change was made
between V3 and V4, but I also had to supply the "-m" option to the "cu"
command to get it to connect to a modem. The V4 manpage says that the "-m"
instructs the cu command to ignore DCD from the modem.
  I just upgraded a box from V3 to V4 that had a modem attached and I did
have to change parameters for the tty from the defaults. The tty port
settings don't get converted.
  If you have a breakout box, you could see what the current state of DCD
is, alter the state of DCD to be opposite of what it currently is and then
try the "cu" command without the "-m" and see if it works. My guess is that
CU wants to see the DCD signal HIGH before it will connect. In other words,
the cu command may work just fine for incoming calls, where the modem
answers and raises DCD, but not for outgoing calls, unless you specify the
"-m".

Just for your reference, I had to configure my tty as follows. This is the
output of
stty -a < /dev/tty1
speed 9600 baud; 0 rows; 0 columns;
   eucw 1:1:0:0, scrw 1:1:0:0:
   intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^A; eol = ^A
   eol2 = ^?; start = ^Q; stop = ^S; susp = ^Z; dsusp = ^Y; reprint = ^R
   discard = ^O; werase = ^W; lnext = ^V
   -parenb -parodd cs8 -cstopb hupcl cread clocal -parext
   ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -iuclc
   -ixon -ixany -ixoff -imaxbel rtsxoff ctsxon
   -isig -icanon -xcase -echo -echoe -echok -echonl -noflsh
   -tostop -echoctl -echoprt -e*-flusho -pending -iexten
   -opost -olcuc -onlcr -ocrnl -onocr -onlret -ofill -ofdel

-JAZZ
--
John Jaszczak
Romac International
Assigned to: Harmonic Systems, Inc.

612-321-4139


>Greetings.

>I just did a migration upgrade of a few systems from AIX V3.2.5 to V4.3.2,
>and am having a problem with the cu command.  The format used is:

>cu -l<tty> -s<baud-rate> <phone-number>

>A specific example:

>cu -ltty0 -s2400 5551212

>This worked fine under V3.2.5, and would cause the modem connected to the
port
>to dial and establish a connection to a remote modem.  The same command in
>V4.3.2 always returns:

>cu: 0835-028 The connection failed. CALLER SCRIPT FAILED.

>Using the same command with debugging turned on (-d) yields:

>altconn called
>Device Type ACU is wanted
>ttylock tty0 succeeded
>Attempting to open /dev/tty0
>clear O_NDELAY
>filelock: ok
>fixline(8, gdial(hayes) called
>expect: ("")
>got it
>Sendthem (DELAY
>A)
>expect: (OK)
>timed out
>set interface UNIX
>ttylock ttyx1 succeeded
>Attempting to open /dev/ttyx1
>generic open failed, errno = 2
>set interface UNIX
>ttylock tty0 succeeded
>Attempting to open /dev/tty0
>clear O_NDELAY
>filelock: ok
>fixline(8, gdial(hayes) called
>expect: ("")
>got it
>Sendthem (DELAY
>A)
>expect: (OK)
>timed out
>set interface UNIX
>getto ret -1
>cu: 0835-028 The connection failed. CALLER SCRIPT FAILED.
>call cleanup(1)
>call _mode(0)

>The "A)" line sometimes appears as "?)" or "???)".  I never see anything I
>recognize from the Dialers file.  I hooked up a serial data analyzer
between
>the port and the modem, and see no data transfered whatsoever.  The symptom
>persists with my setup files (/etc/uucp/*) from V3.2.5 (which work fine
under
>V3.2.5), and fresh files from the V4.3.2 CDROM.  The command:

>cu -m -l<tty> -s<baud-rate>

>works fine, and I am able to send commands to the modem and get a response.
>Anybody else out there seen this?  Any hints would be appreciated.

>Jeff.
>--
>NOTICE TO BULK EMAILERS:  I am really getting tired of your junk email.  It
>costs me both time and money.  Send spam to me, and I WILL GET YOUR
OPERATION
>SHUT DOWN.  So far, 46 web sites deleted.  Who's next?


>          Remove the "x" characters from my email address when replying
>         ** UNSOLICITED COMMERCIAL/PROMOTIONAL EMAIL IS NOT ACCEPTED **