I upgraded from Openserver 5.0.0 to 5.0.6, Now my Modems don't Dialin.

[apeasecpc]

I upgraded from Openserver 5.0.0 to 5.0.6. Now my Modems don't work for Dialin. They connect and then immediately disconnect like the line is not holding DTR.

My Serial Device is a Comtrol Rocketport which is currently configured with 32 ports, ttyr0A - ttyr0H, ttyr1A - ttyr1H, ttyr2A - ttyr2H, ttyr3A - ttyr3H. My 6 modems I am are connected to ttyr2A - ttyr2F.

My modems are all External US Robotics Sportster 56k Fax.

I am using the same Dialers, Devices, and Systems, gettydefs, and inittabs that worked in 5.0.0.

Here is the gettydef I am using:

p # B38400 HUPCL # B38400 CS8 SANE HUPCL TAB3 -ORTSFLOW RTSFLOW CTSFLOW #\r\nlogin: # p

For most of my dialouts I am not using a compiled dialer, instead the dialer is defined in the Dialers file as the typical series of modem commands. These all seem to work fine for dialout, and the man pages imply this is still supported in 5.0.6.

reset =,-, "" \r\pATE0F1Q1V0M1X4AT&A3&B1&C1&D2&H1&I0&K1&M4&R2&S1ATS0=1S2=128&U0&N0Y0AT&W0\r
&reset =,-, "" \r\pATE0F1Q1V0M1X4AT&A3&B1&C1&D2&H1&I0&K1&M4&R2&S1ATS0=1S2=128&U0&N0Y0AT&W0\r
normal =,-, "" \r\pATE1Q0V1M0S0=0S2=128&U0&N0 OK\r \dATDT\T CONNECT
&normal =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
normal2400 =,-, "" \r\pATE1Q0V1M0S0=0S2=128&U0&N3 OK\r \dATDT\T CONNECT
&normal2400 =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
normal9600 =,-, "" \r\pATE1Q0V1M0S0=0S2=128&U0&N6 OK\r \dATDT\T CONNECT
&normal9600 =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
normal192 =,-, "" \r\pATE1Q0V1M0S0=0S2=128&U0&N10 OK\r \dATDT\T CONNECT
&normal192 =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
debug =,-, "" \r\pATE1Q0V1M1S0=0S2=128&U0&N0 OK\r \dATDT\T CONNECT
&debug =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
debug2400 =,-, "" \r\pATE1Q0V1M1S0=0S2=128&U0&N3 OK\r \dATDT\T CONNECT
&debug2400 =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
debug9600 =,-, "" \r\pATE1Q0V1M1S0=0S2=128&U0&N6 OK\r \dATDT\T CONNECT
&debug9600 =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r
debug192 =,-, "" \r\pATE1Q0V1M1S0=0S2=128&U0&N10 OK\r \dATDT\T CONNECT
&debug192 =,-, "" \r\pATE0Q1V0M1S0=1S2=128&U0&N0Y0&W0\r

My Devices file actually contains several lines in addition to the typical ACU and Direct lines:

RESET ttyr2A - 38400 reset
USRM ttyr2A - 38400 USRModem
USRMT ttyr2A - 38400 USRModemT
CMHCA ttyr2A - 9600 cmhc9600a
NORM ttyr2A - 38400 normal
NOR24 ttyr2A - 2400 normal2400
NOR96 ttyr2A - 9600 normal9600
NOR19 ttyr2A - 19200 normal192
DEBUG ttyr2A - 38400 debug
DEB24 ttyr2A - 2400 debug2400
DEB96 ttyr2A - 9600 debug9600
DEB19 ttyr2A - 19200 debug192
ACU ttyr2A - 38400 normal
Direct ttyr2A - 38400 direct

In the days of 5.0.0. it used to be that when a modem port was first enabled, it sent the the initialization string defined by that ports first line in the Devices file. When I reset the modem by disabling and re-enabling the port, I would physically see the indicator lights flash on the modem. This no longer happens and I suspect that the modem is no longer being initialized, which explains the DTR hangup.

Question:
How do get my system to reset and send a fresh initialization string in 5.0.6? How do I make this a part of the normal configuration?

 

[apeasecpc]

I notice in the man page for atdialer that the MDM_RESET parameter says "This parameter is no longer supported and is ignored". I am very suspicious that for some reason SCO dropped the program that sends the reset string to the modem when it is first enabled or the line is disconnected. That appears to be the behavior I am seeing. Does anyone have any information on this?

My experience is that leaving the reset up to the modem's nv-ram is not entirely reliable (point of fact, my problem described above, which wouldn't be happening if the modems were resetting themselves correctly). I prefer to force a reset after each disconnect, which SCO Openserver 5.0.0 supported, but I guess 5.0.6 does not. What can I do?