Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cu not dialing 9600 baud systems

Status
Not open for further replies.

aseidas

MIS
Jan 10, 2002
73
US
Hello,
We use cu heavily to support customers and have been for years about two weeks ago we started having major problems with our call scripts that use cu to dialout, very flaky some customers worked other didn't. We called the phone company to check the lines, they said they were clean. We swapped out half of the 10 modems we have connected to a stallion serial concentrator , no difference.

I installed a brand new stallion card and panel still the same. I then moved all of the modems to another sco server replaced all cables & connecters, copied /usr/lib/uucp/Systems,Devices & Dialers & problems still persist. I believe I have narrowed it down to systems set to 9600 baud in Systems, 19200 systems seem to be fine. I am pulling my hair out !!! Any suggestions would be greatly appreciated. Please see examples from dialers, systems, and devices below:


Devices:
ACU tty0A00 - 19200 usrobT19.2 \D
ACU tty0A00 - 9600 usrobT9600 \D
ACU tty0A00 - 2400 usrobT2400 \D
ACU tty0A00 - 1200 usrobT1200 \D

Systems:
weil Any ACU 9600 15555555555 -\r\d-ogin:-\K\d-ogin:-\K\d-ogin: nuucp word: ****

tpc Any ACU 19200 15555555555 -\r\d-ogin:-\K\d-ogin:-\K\d-ogin: nuucp word: ****

Dialers:

usrobT9600 =,-, "" ATQ0E0&D2&C1&B1&M4&N6S0=0X4S2=043\r\c OK\r ATDT8,\T\r\c CONNECT
&usrobT9600 =,-, "" +++\dATZ0Q0H OK\r ATE0&D3&C1&N6X4S2=128 OK\r ATS0=1Q1\r


usrobT19.2 =,-, "" ATF1Q0E0&D2&A0&B1&C1S0=0X4S2=043\r\c OK\r ATDT8,\T\r\c CONNECT
usrobT19.2=,-, "" ATF1Q0E0T&D3&C1S0=0X4S2=043\r\c OK\r ATDT8,\T\r\c Speed



PLEASE HELP !!!

-Aseidas






 
ATZQ0...

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244
 
To create an automatic reset,

1) Determine the proper AT command to restore factory defaults.

2) Create a dialer in the "/usr/lib/uucp/Dialers" file called "reset". Here is an example below:
Code:
reset        =,-, "" \r\p\r\pAT&F1\r\pAT&W0\r
&reset       =,-, "" \r\p\r\pAT&F1\r\pAT&W0\r

"AT&F1" is typically the command for Hardware Flow Control factory defaults. The "\r\p" sends a carriage return to the modem and pauses for it to react. It is possible to add several AT strings in the reset if you want to make changes after the return to factory. "AT&W0" is typically the cammand that saves the settings to memory, making them permanent. Your modems may require different commands than these.

3) Create a device in the "/usr/lib/uucp/Devices" file called "RESET" for each of your ttys. Here is an example below:

Code:
RESET tty0A00 - 38400 reset
ACU tty0A00 - 19200 usrobT19.2 \D
ACU96 tty0A00 - 9600 usrobT9600 \D
ACU24 tty0A00 - 2400 usrobT2400 \D
ACU12 tty0A00 - 1200 usrobT1200 \D
Direct tty0A00 - 38400 direct

The "RESET" device must be the first listing for the given tty or it will not work. Unix always uses the first device listing for a tty as the reset for when a port is enabled on bootup or with an enable command. Place ACUs or any other devices between the "RESET" and the "Direct" devices. If you don't have a "RESET" device set up this way, the reset string of the first device found is used for reset (typically the "ACU" device).

A "RESET" device is the preferred setup because it allows restoring factory defaults on port initialization, yet accommodates simpler and faster reset strings (like "ATZ") between modem connections so that the devices are ready to use more quickly after disconnect.
 
Well we have pretty much just given up on this, we have tried every suggestion here as well as other things we have thought of and nothing seems to work other than a reboot of the machine. After the reboot all the modems work perfectly for a while then start failing again. I would like to try to simulate what the reboot is doing to the serial ports without a reboot but I fear it is at the kernel level. Anyone know how I might simulate a reboot for the serial devices or is this just wishful thinking.

-Aseidas
 
Have you tried the sequence: disable, init q, sleep, enable, init q ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top