mgetty(rpm) on a Zoltrix (33,600)

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

I have a Zoltrix (Rockwell based) 33,600 modem.

According to the modem manual, this gives all the info one needs
about the modem

	ati3
	V2.061 US001-V34_ACF_DP1
	
	OK
	at+fclass=?
	0,1

	OK
 
I installed the modem both at home (Redhat 2.1) and on my office
(Redhat 4.1) Linux boxes. Then I installed mgetty-1.0.0.rpm on both
boxes. Remarks and questions:

1) The mgetty.rpm does not work out of the box with the stock redhat
stuff because the lockfile is put in /var/log/uucp/ while minicom puts
it in /var/log/ (and this latter is according to FSSTND).

2) So I changed this and recompiled mgetty. The modem is class 1, but
I ('d like to) use it only for datatransfer. First I had this in
/etc/mgetty.config in my home box

port ttyS1
speed 115200
data-only y
init-chat "" AT&FX4&C1&D2W2 OK ATE1Q0S0=0 OK
ringback y 


The modem manual recommends 

	AT&F&C1&D2

as the first part of any customized init string. In order to make the
modem to attempt a V.42bis connection, the manual recommends

	AT&F&C1&D2W2

3) I now dial (using minicom) my home from the office. Hangup, dial
again. After 20 seconds my answering machine picks up --- not the
modem. Here is the the relevant portion of /var/log/mgetty.ttyS1 from
my home box (debug level 4)

--
04/20 11:43:24 yS1 mgetty: official release 1.0.0
04/20 11:43:24 yS1 check for lockfiles
04/20 11:43:24 yS1 locking the line
04/20 11:43:25 yS1 lowering DTR to reset Modem
04/20 11:43:25 yS1 send: AT&FX4&C1&D2E1Q0[0d]
04/20 11:43:25 yS1 waiting for ``OK'' ** found **
04/20 11:43:26 yS1 send: ATS0=0[0d]
04/20 11:43:26 yS1 waiting for ``OK'' ** found **
04/20 11:43:26 yS1 waiting...
04/20 12:43:26 yS1 checking if modem is still alive
04/20 12:43:26 yS1 mdm_send: 'AT' -> OK
04/20 12:43:26 yS1 waiting...
04/20 13:43:26 yS1 checking if modem is still alive
04/20 13:43:27 yS1 mdm_send: 'AT' -> OK
04/20 13:43:27 yS1 waiting...
04/20 14:43:27 yS1 checking if modem is still alive
04/20 14:43:27 yS1 mdm_send: 'AT' -> OK
04/20 14:43:27 yS1 waiting...
04/20 15:14:15 yS1 waiting for ``RING'' ** found **
04/20 15:14:15 yS1 waiting for ``RING'' ** found **
04/20 15:14:20 yS1 waiting for ``RING'' ** found **
04/20 15:14:36 yS1 waiting for ``RING'' ** found **
04/20 15:14:42 yS1 waiting for ``RING'' ** found **
04/20 15:14:48 yS1 waiting for ``RING''
04/20 15:15:05 yS1 timeout in chat script, waiting for `RING'
04/20 15:15:05 yS1 ringback: phone stopped after 5 RINGs, waiting for re-ring
04/20 15:15:05 yS1 waiting for ``RING''
04/20 15:15:35 yS1 timeout in chat script, waiting for `RING'
04/20 15:15:35 ##### missed ringback!

So somehow the modem does not receive the second call (the phone
answers instead).

4) I now change the mgetty conf file so ringback is not enabled. Then
I get the modems connected. On the other hand, even when I call home by
telephone, the modem answers! Here is again the mgetty logfile from
the home box:

04/21 08:40:34 yS1 mgetty: official release 1.0.0
04/21 08:40:34 yS1 check for lockfiles
04/21 08:40:34 yS1 locking the line
04/21 08:40:34 yS1 lowering DTR to reset Modem
04/21 08:40:35 yS1 send: AT&F&C1&D2W1[0d]
04/21 08:40:35 yS1 waiting for ``OK'' ** found **
04/21 08:40:35 yS1 send: ATE1Q0S0=0[0d]
04/21 08:40:35 yS1 waiting for ``OK'' ** found **
04/21 08:40:35 yS1 waiting...
04/21 09:02:07 yS1 waiting for ``RING'' ** found **
04/21 09:02:07 yS1 send: ATA[0d]
04/21 09:02:07 yS1 waiting for ``CONNECT'' ** found **
04/21 09:02:20 yS1 send:
04/21 09:02:20 yS1 waiting for ``
'' ** found **
04/21 09:02:25 ##### data dev=ttyS1, pid=22408, caller=none, conn='115200/26400'
 
Could anybody advice me what to do? 


Thanks

Mate

Mate Wierdl 
mw@moni.msci.memphis.edu 
University of Memphis
.