OPEN FAILED /dev/cul0p7, errno = 16

[alexander bellia_1]

I'm trying to use the internal modem to dial outside. I did test the phone line with a regular phone and the line is O.K however when running the follwing command I have an error:
cu -l/dev/cul0p7 -s2400 -d1 94163292746 for autodialling

Autodialing - please wait
call dial(2139031584)
baud=2400, speed=2400, line=/dev/cul0p7, telno=94163292746
call find_dev(17737604040)
baud=2400, speed=2400, line=/dev/cul0p7, telno=94163292746
nomodem is 0
OPEN FAILED /dev/cul0p7, errno = 16
call undial(-6)
Connect failed: line problem

Any suggestions ?
Regards,
alexander bellia

[Paula J Frazer-Campbell · Accepted solution]

Hi
Test it with kermit:-

kermit
set line /dev/tty0p7
set modem (usr or whatever)
set speed 2400
c

then :-
at - this should reply OK - this is a reply from the modem

adt 94163292746 to dial number

Paula

[Bill Douglass]

errno means device busy. Do you have a hung process accessing the modem port? If not, make sure it is not configured in /etc/inittab to be running a getty.

[alexandre MARIE]

did you check the permissions on /dev/cul0p7 (rw) and look at the dev configuration (stty -a
Regards,

[Darren Prior]

Hi,

use fuser /dev/*0p7 to see if any other process is using the port. The * is important as it will check the other device files that use the same physical port (ie ttyd0p7, cua0p7.)

regards,

Darren.

[A. Clay Stephenson]

Becuase uucp/cu is so difficult to get exactly right and you may have hardware/cabling/modem configurations problemsd as well, I suggest that you use the much simpler kermit first. It's then easy to distinguish the hardware problems from the software ones.


My first step would be to edit /etc/inittab and set the newly configured port to off and then do an init -q to force a read of gettydefs. Now make sure using fuser or lsof that no other processes are using the port.

I suggest that you first try to talk to the modem using kermit.
Something like:
kermit
set line /dev/ttyd0p1 (or whatever your port is)
set speed 19200
set modem hayes
connect

If you can issue AT commands and get responses
you are in great shape. If not,
from another terminal session, I would now try to assert/ignore some of the status lines
via stty -crts rtsxoff ctsxon < /dev/ttyd0p1.
See if kermit will now talk to the modem. If it works after the stty, then you need to assert those bits on the modem either via AT commands, DIP switch settings, or hardwiring the cable.

One you get kermit working then you can configure uucp secure in the knowledge that the hardware portion is out of the picture.

[Darren Prior]

Hi,

I've just re-read the question...

You don't mention what type of server this is, I suspect either a D or K class; judging from the device file for the internal modem. It sounds likely to me that the system is configured for remote console access, in which case the device files will have no effect on the modem as it is bypassing them.

You have 2 choices, either disable remote console access or use an alternative, external modem.

The internal modem is not supported for customer usage; in addition if you hang the modem the only way to fix it is to power cycle the box.

regards,

Darren

[Paula J Frazer-Campbell]

Well spotted Darren


I should have seen that as most of my servers a Ks.

and "I'm trying to use the "internal" modem to dial outside".


Alexander as Darren has said this is not supported.

Invest in a good stand moden US robotics is fine.

Paula