no login via modem

[chris5234]

Hi,

we are running a SCO Unix 5.0.7 machine which has a modem connected to COM1 for another support-company to dial in.
Despite of the need to reset the modem from time to time it worked perfectly. But now the support company says, that they can't log-in anymore. So I checked everything on our side, restarted the server, tried COM2, etc... Without success.
As I have no clue, what I could else do, I'd like to ask if someone of you has an idea.

Some more detail:
- modem is a Sportster_28800_External connected to COM1

- inittab: Se1a:234:respawn:/etc/getty -x1 tty1a m

- gettydefs: m # B9600 HUPCL # B9600 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\nlogin: # m

- ps shows getty as only proc on tty1a

- /usr/lib/uucp/Devices:
ACU tty1a - 9600 Sportster_28800_External

- /usr/lib/uucp/default/Sportster_28800_External:
MDM_SETUP=AT &F1 E0 V1 &C1 &D2 Q0 S0=0 &B1 &A3&H1&R2&I0&M4
MDM_SPEAKER=ATM0
MDM_DIALCMD=ATDT
MDM_HANGUP=ATH

as I turned debugging on in getty, I receice this in the syslog:
Jan 21 11:42:33 stxserv getty[8246]: Getty started on tty1a
Jan 21 11:42:33 stxserv getty[8246]: Obtaining connection on tty1a
Jan 21 11:42:33 stxserv getty[8246]: Checking if uucp handling is required for line
Jan 21 11:42:33 stxserv getty[8246]: Dialer is specified for tty1a
Jan 21 11:42:34 stxserv getty[8246]: Line modes reset & line dropped.
Jan 21 11:42:34 stxserv getty[8246]: Have tty lock.
Jan 21 11:42:34 stxserv getty[8247]: Run /usr/lib/uucp/Sportster_28800_External -hx0 tty1a 9600
Jan 21 11:42:41 stxserv getty[8246]: Caught SIGCLD (dialer completed).
Jan 21 11:42:42 stxserv getty[8246]: Wait for connection on line : tty1a
Jan 21 11:42:42 stxserv getty[8246]: Connected.
Jan 21 11:42:42 stxserv getty[8246]: Connected at 9600 baud.
Jan 21 11:42:42 stxserv getty[8246]: Required speed is 9600 baud.
Jan 21 11:42:42 stxserv getty[8246]: Incoming DATA.
Jan 21 11:42:42 stxserv getty[8246]: Login sequence.

These entries are followed by " Timed out. Exit(1)" after one minute and then it starts over again.

I did a 'cat /dev/tty1a' and it returns OK everytime the getty-initialization is done. When the support tries to dial in, cat showed me RING RING RING and then I was kicked out.


Support told me that they had checked everything and averything would be set up correctly (i.e. speed = 9600 baud).
But they always get these lines:
---------------------------------------------------
Attempting to dial :- <phone number>
Connected

x
Lost Carrier

Disconnected
Not connected.

The line is either busy or will not answer.
---------------------------------------------------

At the point, where the x is, they usually get the 'login:' prompt, but it is missing.


Does anyone know how to proceed with this problem? Or if at least it looks like everything is OK on our side?

Best regards,
Chris

 

[PHV]

Replace this:
S0=0
With this:
S0=2

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[chris5234]

Thanks for you reply.

well, afaik this only sets the ammount of rings until it answers, but I tried it anyway. Regretfully, it didn't change anything.

 

[PHV]

The modem line is tty1A (not tty1a) ...

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[edfair]

In addition to PHV's 1A comment switch 5 s/b up for auto answer and I normally make the gettydefs entry 2 , modify the entries for 1, 2, and 3 to point back to themselves rather than rotating, and change 2 to be 9600 on both lines involved.

In 5.0.5 the gettydefs lines involved were 55 to 62 IIRC, part of the modem stuff.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[motoslide]

If you are just using the modem for dial-in support (no UUCP, PPP, SLIP, etc.), I wouldn't tell UUCP about the modem. Take it out of the Devices file, set the inittab to a fixed BAUD rate (which you aready have), and set the modem to a fixed speed on it's serial port. On the modem, disable command echo and result codes.

But, that's just me.

Also, using the tty1A line should cause it to hang up on logout.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[chris5234]

Ok, I now disabled tt1a and only left tt1A in the inittab.
But I left it to gettydefs entry 3 and 2400 baud, as it did work some time ago, these settings should work...

/etc/inittab:
Se1a:234ff:/etc/getty tty1a m
Se1A:234:respawn:/etc/getty -x1 -t60 tty1A 3


/etc/gettydefs:
3 # B2400 HUPCL OPOST CR1 ECHOE NL1 # B2400 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\nlogin: # 3

However my syslog now looks like this:

Jan 24 10:24:19 stxserv getty[8895]: Getty started on tty1A
Jan 24 10:24:19 stxserv getty[8895]: Obtaining connection on tty1A
Jan 24 10:24:19 stxserv getty[8895]: Checking if uucp handling is required for line
Jan 24 10:24:19 stxserv getty[8895]: Dialer is not specified for tty1A
Jan 24 10:24:19 stxserv getty[8895]: Line modes reset & line dropped.
Jan 24 10:24:19 stxserv getty[8895]: Wait for connection on line : tty1A

and stays there. When the modem was resetted, I got:

Jan 24 10:39:44 stxserv getty[8895]: Connected.
Jan 24 10:39:44 stxserv getty[8895]: Connected at 2400 baud.
Jan 24 10:39:44 stxserv getty[8895]: Required speed is 2400 baud.

immedeately followed by the first part. Now it's waiting for connection again. It does not restart after 60 secs as tty1a did.

Maybe someone could tell me, if this is the expected output? Or does anything indicate an error on our system?

Best regards,
Chris

 

[edfair]

Don't have a system to check with but seem to recall that you need the dialer entry to reset the modem when the line goes down.

There are 2 ways to identify it to the system, one with a specific file name and the other with an entry that points into the middle of a list of possible dialers. I've always used the one that is part of the generic set.

I also recall some issues with terminal emulators having problems with low speed rates with 33K rated modems. Lowest I could ever get reliably was 9600. But that may have been emulator issues.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[chris5234]

Thanks for all your help.

Finally it works. The main issue really was the speed.
It looks like previous connections were somehow established using tty1a at 9600 baud. When I triedd to handle the connection with tty1A, it used the defined 2400 baud and this was definitely too slow for the terminal, resulting in a single 'x' on the dial-in prompt.

I set up the connection completely new from scratch with tty1a disabled and tty1A using a new gettydefs speed in the way motospeed mentioned: copied entry 3, changed to 9600 baud and loop back to itself.
In usr/lib/uucp/Devices I set up the Sportster device on tty1A with 9600 baud. I added additionally a direct device for tty1a in order to debug the MDM_SETUP string (according to SCO manual). Finally I used the Sportster entry in /usr/lib/uucp/default/Sportster_28800_External as dialer in order to reset the modem to the default afer any connection.

Once again, thanks to you all!
Chris

 

[motoslide]

Actually, the gettydefs change was Ed's suggestion. Kudo's to him for his UUCP expertise, and to you for passing along the final solution.

"Proof that there is intelligent life in Oregon. Well, Life anyway.