Modems hanging up

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Thank you for responding Mirek, I really appreciate it.


>Allways try recent (1.1.18) version of mgetty (because 1.1.xx are
>development versions).

I have been chasing the version monster for the last year and a half.
I will try 1.1.18 if you really think it is necessary.

>Send your modem configuration (start minicom and write: atl5l6l7)

Is this really a lower case L as in ATL5L6L7? The string^^^^^^^^
didn't work just reported an error with atl5l6l7 and atl5 atl6 atl6.

or is it ati5, ati6, ati7?

I'm sorry I am not well versed in minicom.  I am much more comfortable
with cu.  Here is a session from cu with ati.

Connected.
atz
OK
ati5i6i7
1.01,0,19

OK
ati5
1.01,0,19

OK
ati6
OK
ati7
OK

Is there something that I am missing?  I can't seem to find anyway
to get to the configuration on these MultiTechs.  The USRs will report 
all the info by using ati5 ati6 ati7.


>Maybe line is noisy or serial line speed is wrong (I don't know what the
$SB
>parameter is for but I had problems with it some time ago), and ...

The serial line speed is set at 57600 as per MultiTech.
If I change this to 38400 will this decrease the throughput?
Or should I go higher, 115200?  The cables that go to these modems
are the flat cables that were supplied cyclades.  Could these be the 
culprit?


I noticed that my mgetty.config file has this at line 20:

# access the modem(s) with 38400 bps
speed 38400

This should probably be 57600?  Since my mgetty lines in inittab have
-s 57600

Excuse me for being slow, what $SB?

>and modem doesn't reset because wrong &D setting.
>Use minicom and write:
>  atz
>  at&d3
>  at&w0

This is what I have done to all the modems for the last year and a half.

cu -l ttyCxx
atz
atm0
at&d3
atx1
at&w0
atz
~.

>May current init chat string is:
>
>  init-chat "" \d\d\d+++\d\d\dATZ OK AT OK ATB0L0M0&C1&D3&E4X4 OK


Is this in the policy.h?  The line #309:

#define MODEM_INIT_STRING       "ATS0=0Q0&D3&C1"




-greg