Lost Login: prompt from Modem Dial In

[Jon Jenkins_1]

I'm trying to resolve a problem of our modem (Multitech MT2834BLIe on L-Class 11.0)dropping an inactive session too quickly. I've got the User Manual and I'm working my way getting to know all the AT commands. Having reset the modem to factory defaults, I'm reasonably happy that the settings are correct. However when I dial in, the connection appears to go smoothly but I get no Login: prompt, and keystrokes appear to have no affect. These are the current settings;

atl5l6l7
B0 E1 M1 Q0 R0 V1 X0 &E1 &E4 &E7 &E8 &E10 &E12 &E15 %C0 #C1 &C1
$MB33600 $SB19200 $BA0 &W0

S0 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11 S13 S18 S19 S24 S25
001 130 013 010 008 004 055 004 006 001 080 000 030 001 020 000

S30
000

$A0 #A0 &B0 &BS1 $D0 &D3 #DB0 %DL0 $EB0 %E1 %E5 #F2 $F0 &G2 #L0 $LL0 $MI0
&M0 &P1 #P0 &Q0 $R0 &R1 &RF1 &S1 $SP0 &SF0 &T4 $T1 $V0 $V6 $VD0 &X0 Y0
$MB33600 $SB19200 $BA0 &W0

Any ideas?

[Bill Hassell]

HP-UX will do nothing with a modem. There must be a getty posted on that port in order to answer the phone. If the modem answer the phone without a getty running, you probably have the modem ignoring the terminal-ready line. When properly configured, the modem must only answer the phone when the getty is running, otherwise, the modem will never hangup.

To test this, setup the getty in /etc/inittab and pick an appropriate entry in gettydefs. Then change the inittab entry to :respawn: and tell init to reread inittab. You should see the terminal ready light come on. If you then kill the getty, you should see the light go out, then a few seconds later, it should come back on again as a new getty is respawned by init.

At that point, you should get a login prompt from a remote terminal.

[Ron Kinner]

If I read your post correctly everything was working before you played with the AT commands so we don't have to worry about your HP setup.

Don't know about HP but on my SCO boxes we always used s0=0. The modem would detect an incoming call and send RING to the computer which would then send a command to answer the call (with an ATA I think). This kept the modem from answering calls if the process was not running so we didn't have to pay for calls. IF yours is set up this way you may also need to change &Q0 to &Q1.

You have &D3 which will return the modem to factory default after DTR falls. I'd change this to &D1.

If you set up a kermit session can you talk to your modem? You might have a speed/parity/stop bit mismatch.

You can turn on logging for the gettys which might give you a clue. Someone else will have to tell you how tho.
You can also look at the expect/respond setup which the hp uses for incoming calls.

That might give you a clue as to how to set up the modem. I don't have a dialup on my HP so I can't tell you what the file is called.


On your original problem there were two S registers which control hanging up too early. S30 which you now have at 0 (meaning no hang up on inactivity this can cost you some big phone bills) and the S10 which you have set to only 1 meaning a 100 msec drop in carrier is enough to drop the call. This seems way too low. You can get a lot of noise on an analog line which is more than that in length. The default is supposed to be 7 meaning 700 msec which is enough to bridge over most noise on the line and even ignore call waiting.

Ron