Modem not answering

Hello,

I have a new P4 server with a modem in it. I am using QNX 4.25D. The modem is a
US Robotics PCI version. I can use show_pci -vvv to get the port and irq for the
modem just fine. I start “Dev32.ser port,irq” in the sysinit file. I can talk to
the modem and dial out with qtalk just fine. With qtalk running, I can call the
machine and qtalk prints “RING” to the screen.

My problem is with the “modem” utility. In the past we have started modem from
a tinit line in the sysinit file. Modem does not want to answer the phone.
I have tried taking modem out of the sysinit and starting on the command line, using
the example given in the docs, “on -t /dev/ser1 modem -b 57600 -L…”. This just
locks the /dev/ser1 from being used by qtalk (“modem in use”) and when modem is
slain, qtalk stops talking to the modem (ATZ does not return OK).

What would be causing this?

Kevin Hammond
PACE Control Systems.

FWIW, I have had similar experience in getting modems to answer. I have always managed
it though. Usually my problem has been that the number of rings is unrelated to the
settings I request. I haven’t spent too much time investigating because it is not that
critical to me. My command line is
tinit -c “modem -B 115200 -b 115200 -r 3 -L -iATZX0M0” -t /dev/ser1 &

Pace Control Systems wrote:

Hello,

I have a new P4 server with a modem in it. I am using QNX 4.25D. The modem is a
US Robotics PCI version. I can use show_pci -vvv to get the port and irq for the
modem just fine. I start “Dev32.ser port,irq” in the sysinit file. I can talk to
the modem and dial out with qtalk just fine. With qtalk running, I can call the
machine and qtalk prints “RING” to the screen.

My problem is with the “modem” utility. In the past we have started modem from
a tinit line in the sysinit file. Modem does not want to answer the phone.
I have tried taking modem out of the sysinit and starting on the command line, using
the example given in the docs, “on -t /dev/ser1 modem -b 57600 -L…”. This just
locks the /dev/ser1 from being used by qtalk (“modem in use”) and when modem is
slain, qtalk stops talking to the modem (ATZ does not return OK).

What would be causing this?

Kevin Hammond
PACE Control Systems.

Thank you for the information. It helps, but I still can’t get the modem to
answer.

I have the serial port set properly, (I can talk to the modem via qtalk and
ATZ returns OK)
I can get a dialtone and dial out. If I leave qtalk running and call the
number, qtalk responds
with a “RING” message.

My command line is
tinit -c “modem -B 115200 -b 115200 -r 3 -L -iATZX0M0” -t /dev/ser1 &

and is the last line of the sysinit file.

What am I doing wrong?

Kevin Hammond


“Donald Backstrom” <donaldb@cstgroup.com.au> wrote in message
news:3AAFF14F.3914D118@cstgroup.com.au

FWIW, I have had similar experience in getting modems to answer. I have
always managed
it though. Usually my problem has been that the number of rings is
unrelated to the
settings I request. I haven’t spent too much time investigating because it
is not that
critical to me. My command line is
tinit -c “modem -B 115200 -b 115200 -r 3 -L -iATZX0M0” -t /dev/ser1 &

Pace Control Systems wrote:

Hello,

I have a new P4 server with a modem in it. I am using QNX 4.25D. The
modem is a
US Robotics PCI version. I can use show_pci -vvv to get the port and
irq for the
modem just fine. I start “Dev32.ser port,irq” in the sysinit file. I
can talk to
the modem and dial out with qtalk just fine. With qtalk running, I can
call the
machine and qtalk prints “RING” to the screen.

My problem is with the “modem” utility. In the past we have started
modem from
a tinit line in the sysinit file. Modem does not want to answer the
phone.
I have tried taking modem out of the sysinit and starting on the command
line, using
the example given in the docs, “on -t /dev/ser1 modem -b 57600 -L…”.
This just
locks the /dev/ser1 from being used by qtalk (“modem in use”) and when
modem is
slain, qtalk stops talking to the modem (ATZ does not return OK).

What would be causing this?

Kevin Hammond
PACE Control Systems.

try running modem on its own first with debug mode…

e.g.
modem -D/dev/con6 -Lb115200 -s1

this way you will see output from modem on con6 (or wherever else you want
to see it). and a locked baud rate is best so no auto negotiate to modem
from the uart. and put a delay in (-s) so that you don’t start login too
soon.
that’s what we do here and it works well. a tricky science though…

Kevin Hammond <kevinh@paceolm.com> wrote:

Thank you for the information. It helps, but I still can’t get the modem to
answer.

I have the serial port set properly, (I can talk to the modem via qtalk and
ATZ returns OK)
I can get a dialtone and dial out. If I leave qtalk running and call the
number, qtalk responds
with a “RING” message.

My command line is
tinit -c “modem -B 115200 -b 115200 -r 3 -L -iATZX0M0” -t /dev/ser1 &

and is the last line of the sysinit file.

What am I doing wrong?

Kevin Hammond



“Donald Backstrom” <> donaldb@cstgroup.com.au> > wrote in message
news:> 3AAFF14F.3914D118@cstgroup.com.au> …
FWIW, I have had similar experience in getting modems to answer. I have
always managed
it though. Usually my problem has been that the number of rings is
unrelated to the
settings I request. I haven’t spent too much time investigating because it
is not that
critical to me. My command line is
tinit -c “modem -B 115200 -b 115200 -r 3 -L -iATZX0M0” -t /dev/ser1 &

Pace Control Systems wrote:

Hello,

I have a new P4 server with a modem in it. I am using QNX 4.25D. The
modem is a
US Robotics PCI version. I can use show_pci -vvv to get the port and
irq for the
modem just fine. I start “Dev32.ser port,irq” in the sysinit file. I
can talk to
the modem and dial out with qtalk just fine. With qtalk running, I can
call the
machine and qtalk prints “RING” to the screen.

My problem is with the “modem” utility. In the past we have started
modem from
a tinit line in the sysinit file. Modem does not want to answer the
phone.
I have tried taking modem out of the sysinit and starting on the command
line, using
the example given in the docs, “on -t /dev/ser1 modem -b 57600 -L…”.
This just
locks the /dev/ser1 from being used by qtalk (“modem in use”) and when
modem is
slain, qtalk stops talking to the modem (ATZ does not return OK).

What would be causing this?

Kevin Hammond
PACE Control Systems.


Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579

Hello,

Previously, Randy Martin wrote in qdn.public.qnx4:

try running modem on its own first with debug mode…

e.g.
modem -D/dev/con6 -Lb115200 -s1

I tried “modem -D /tmp/modem.out” and got the following output
3ACDE856 STATUS: Restart
3ACDE859 STATUS: No CTS
3ACDE85A STATUS: No CTS
3ACDE85B STATUS: No CTS
3ACDE85C STATUS: No CTS
3ACDE85D STATUS: No CTS
3ACDE85E STATUS: No CTS
3ACDE85F STATUS: No CTS
3ACDE860 STATUS: No CTS
3ACDE861 STATUS: No CTS

I tried “modem -D /tmp/modem.out -C” and got the following output
3ACDE86D STATUS: Restart
3ACDE872 INPUT: “” 4
3ACDE877 INPUT: “” 4
3ACDE87B INPUT: “” 4
3ACDE880 INPUT: “” 4
3ACDE884 INPUT: “” 4
3ACDE884 STATUS: Did not get OK response from modem
3ACDE884 EMIT: “ATZ|~AT”
3ACDE88A INPUT: “” 1
3ACDE88C INPUT: “” 1

I tried “modem -m /dev/ser1 -D /tmp/modem.out -C” and got the following output
3ACDE8A7 STATUS: Restart
3ACDE8A8 INPUT: “at” 0
3ACDE8A9 INPUT: “at” 0
3ACDE8A9 INPUT: “at” 0
3ACDE8AA INPUT: “at” 0
3ACDE8AA INPUT: “ok” 0
3ACDE8AA EMIT: “ATZ|~AT”
3ACDE8AD INPUT: “ok” 0
3ACDE8AF INPUT: “” 1

but the modem still does not answer.

This is a brand new system installed from the June 2000 CD. (Dev.ser, 4.23I, June 27, 1997)
and modem is july 17, 1998.

qtalk -m /dev/ser1 can talk to the modem and I can dial out. The modem is a 3Com pci internal
modem.


What would be causing this?

Kevin Hammond
PACE Control Systems.

After various combinations of hair pulling and “on -t /dev/ser1” commands, we are able to
get the modem to answer. Initially we were putting the “open consoles AND start modem” in the
same tinit line. Moving to two separate tinit lines has fixed the problem.

Kevin Hammond