mgetty and Sierra SQ3465

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

Hi,

On Tue, Nov 10, 1998 at 04:45:17AM +0100, trovero@my-dejanews.com wrote:
> apologies if you received this message twice. I tried to send it few days ago,
> but, apparently, it didn't make it through.

It did.  Obviously, nobody had anything to say in response to it...

> Has anyone had success in using mgetty with a Sierra SQ3465 internal
> data/fax/voice modem? 

Not me personally, but most modem issues are similar (and as such,
mentioned in the "common problems" section of mgetty.info/mgetty.html).

[..]
> First, it cannot distinguish between different kind of calls. If I
> set modem-type to auto, it believes that all calls are voice. If I set it
> to c2.0, it believes all calls are fax.  If I set it to data, of course,
> it believes all calls are data.

Well, not surprising.  El-cheapo modems do that, occasionally.

[..]
> The real problem is that I cannot login. Eventually I would like to
> use AutoPPP, but right now I'd be happy enough if I could login "the old
> way".
> 
> Well, that is not completely true: I logged in once, but could never
> do it again, and I haven't changed anything since then. The log
> of that one session comes later.

Let's look into the mgetty log file...

> All other times, the program prints the login banner and then it seems to
> hang up there and reads nothing from the modem. I tried using, among other
> things, different lines (some are listed later on) in init-chat with
> different combinations of &C# &D# (my modem seems not to understand what
> &K# means) and ingore-carrier, but no success.

Sounds like a carrier detection problem - if the serial port doesn't see
a DCD signal (because it's poorly emulated on the internal modem card, or
because it's not asserted), "login" will hang.

[..]
> 10/30 01:26:01 yS1    CND: ATA[0d][0a]CONNECT ** found **
> 10/30 01:26:13 yS1  send:
> 10/30 01:26:13 yS1  waiting for ``_''
> 10/30 01:26:13 yS1   got:  57600/REL[0d]
> 10/30 01:26:13 yS1    CND: CONNECT 57600/REL
> 10/30 01:26:13 yS1    CND: found: 57600/REL[0a] ** found **

Connection established: good.

> 10/30 01:26:13 yS1   waiting for line to clear (VTIME), read:
> 10/30 01:26:13 yS1  warning: carrier signal is ignored
> 10/30 01:26:13 yS1    looking for utmp entry... (my PID: 788)
> 10/30 01:26:13 yS1   utmp + wtmp entry made
> 10/30 01:26:14 yS1   tio_set_flow_control( HARD )
> 10/30 01:26:14 yS1   print welcome banner (/etc/issue)
> 10/30 01:26:14 yS1   getlogname (AUTO_PPP), read:[0d]
> 10/30 01:26:52 yS1   input finished with '\r', setting ICRNL ONLCR

A single "carriage return" character is received here, in response to the
/etc/issue welcome banner.

> 10/30 01:26:52 yS1   tio_set_flow_control( HARD )
> 10/30 01:26:52 yS1   input finished with '\r', setting ICRNL ONLCR
> 10/30 01:26:52 yS1   tio_set_flow_control( HARD )
> 10/30 01:26:52 yS1   print welcome banner (/etc/issue)
> 10/30 01:26:52 yS1   getlogname (AUTO_PPP), read:[0a]
> 10/30 01:26:52 yS1   tio_set_flow_control( HARD )
> 10/30 01:26:52 yS1   print welcome banner (/etc/issue)
> 10/30 01:26:52 yS1   getlogname (AUTO_PPP), read:NO CARRIER[0d]

... but that one seems to have been the first character of the NO CARRIER
message.

This log looks like the modem did not receive ANYTHING from the caller's
side.  Did you try with a different modem/program on the calling end?

> 10/30 00:41:53 yS1   print welcome banner (/etc/issue)
> 10/30 00:41:53 yS1   getlogname (AUTO_PPP), read:trovero[0d]
> 10/30 00:42:01 yS1   input finished with '\r', setting ICRNL ONLCR
> 10/30 00:42:01 yS1   tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
> 10/30 00:42:01 yS1    login: use login config file
> /etc/mgetty+sendfax/login.config

Looks fine.  So it's not a "ignore-carrier" issue (DCD is there), but
more likely a calling modem or modem-modem issue.

I'd say "not a case for the mgetty list, but a case for the modem vendor.
If he went out of business, bad luck".

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de