Q: mgetty/DIAL-IN problem

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

Thomas Mandl wrote:

> I have to setup a remote *dial-in* connection using a SupraFAX Modem
> V.32bis on /dev/ttyS1 (COM2). I use an Intel PC running Linux RedHat 

These are normally good modems... if they are older. The one I tried
since supra got sold to Dimond has unreliable CID support, but seems to
be all right besides that. The one I use is older than that and
everything works just fine. I normally start with at&f2 for init and go
from there. Do not use at&f or atz. at&f2 sets a known state, atz does
not. at&f(0) turns off too much stuff :-) Here is my initchat in
mgetty.config:

# supra
  init-chat "" \d\d\d+++\d\d\dAT&F2w0s7=60s95=6MH#CID=1 OK 


> Q1: do i need an init-chat sequence (in /etc/mgetty.config) for
> *dial-in*, or is this done only by using the answer-chat?

See above...

> Q2: where can i specify any additional modem AT commands which mgetty
> should use to initialize the modem? (e.g. L[123], X[1234], ...)?

See above ;-)

> Q4: Has anyone got working /etc/mgetty.config files for *dial-in*
> support?

I run a BBS with the above line.

> Q5: Does anyone have a suggestion for my problem. Is my modem broken
> (old BIOS???)

My old bios works better than the new one. 

> Well i've to say i'm not a modem expert, hence i want to appologize if
> my questions are too stupid.

Your questions are not stupid, my opinion is that if you are doing
serious dial in support, you need to become a modem expert... or at
least know what makes a good connection. It is best to start with a
terminal on both ends and try differnt settings on both ends till you
make it work. (use at&v to see where things are at any time) Supra used
to have a number you could dial in and download a file with all their
modem commands. (often ones not mentioned in the book) I found this
useful as the commands are not rockwell standard commands even though it
uses rockwell chips.


> # access the modem(s) with 19200 bps
> speed 19200

This is a 14400 modem then? Even still this should be able to be higher.

> 02/04 14:50:19 yS1   tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
> 02/04 14:50:19 yS1  WARNING: DCD line still active, check modem settings
> (AT&Dx)

Fix this... at&f2 should work... but make sure.

> 02/04 14:54:38 yS1    CND: OK[0a]RING ** found **
> 02/04 14:54:38 yS1    CND: check no: 'none'
> 02/04 14:54:38 yS1    CND: check vs: all
> 02/04 14:54:38 yS1  send: ATA[0d]
> 02/04 14:54:38 yS1  waiting for ``CONNECT''
> 02/04 14:54:38 yS1   got: [0d]
> 02/04 14:54:38 yS1    CND: RING[0a]ATA[0d]
> 02/04 14:54:38 yS1    CND: ATA[0d][0a]CONNECT ** found **
> 02/04 14:54:52 yS1  send:
> 02/04 14:54:52 yS1   waiting for line to clear (VTIME), read:

Got connect ok.

> 02/04 14:54:55 yS1  clean_line: only 500 of 612 bytes logged
> 02/04 14:54:55 yS1    looking for utmp entry... (my PID: 487)
> 02/04 14:54:55 yS1   utmp + wtmp entry made
> 02/04 14:54:55 yS1   tio_set_flow_control( HARD )
> 02/04 14:54:55 yS1   print welcome banner (/etc/issue.modem)
> 02/04 14:54:55 yS1   getlogname (AUTO_PPP),

Assuming this is you trying to login from a terminal... mgetty seems to
think you are trying to start up a ppp connection. Hyper term shouldn't
do that. Network connection would... (you shouldn't be using that) May
be worth while compiling mgetty without DAUTOPPP and trying that. At
least to see where things are. Try the initchat solution first though.
Maybe, mgetty is seeing garbage and thinking autoppp, I don't know the
code well enough.
 

-- 
Len Ovens
len@studio.cbbs.org