Problems with dialing out when dial-ins are enabled

Problems with dialing out when dial-ins are enabled

Post by Eric Dittm » Sat, 26 Jun 1993 01:36:59



I'm having trouble getting dial-outs to work when dial-ins are
enabled.  I can dial out on /dev/cua1 when getty isn't running
on /dev/ttyS1, but when getty is running I get a message that
the port I'm trying to dial-out on (/dev/cua1) is in use.  I
read the FAQs and everything seems to be set up right.  What
am I doing wrong?  

[I'm running SLS 1.02 (0.99pl9).]
--
Eric Dittman                  Texas Instruments - Component Test Facility

Disclaimer:  Not even my opinions.  I found them by the side of the road.

 
 
 

Problems with dialing out when dial-ins are enabled

Post by Ian Murdo » Sat, 26 Jun 1993 09:39:19



Quote:>I'm having trouble getting dial-outs to work when dial-ins are
>enabled.  I can dial out on /dev/cua1 when getty isn't running
>on /dev/ttyS1, but when getty is running I get a message that
>the port I'm trying to dial-out on (/dev/cua1) is in use.  I
>read the FAQs and everything seems to be set up right.  What
>am I doing wrong?  

>[I'm running SLS 1.02 (0.99pl9).]
>--

If you're using the getty that comes with SLS, you're using the old version.
You can't dialin/dialout on the same line with that version.  Get the new
version, getty_ps2.0.7b if I remember correctly, and you should be able
to do the above.  You can find it on tsx.mit.edu somewhere; check the index.

I say should because I can't.  Whenever I invoke kermit I get the message
'can't initialize modem'.  If I restart init with a different runlevel
(one which does not spawn getty on the line) then I can dial out just fine.

Also, the new RINGBACK feature doesn't seem to work quite right for me.  It
picks up after three rings all of the time.  But logging in, etc. works just
fine.

Anyone else having the above problems?
--


 
 
 

Problems with dialing out when dial-ins are enabled

Post by John Comy » Sun, 27 Jun 1993 10:54:45



>If you're using the getty that comes with SLS, you're using the old version.
>You can't dialin/dialout on the same line with that version.  Get the new
>version, getty_ps2.0.7b if I remember correctly, and you should be able
>to do the above.  You can find it on tsx.mit.edu somewhere; check the index.

>I say should because I can't.  Whenever I invoke kermit I get the message
>'can't initialize modem'.  If I restart init with a different runlevel
>(one which does not spawn getty on the line) then I can dial out just fine.

>Also, the new RINGBACK feature doesn't seem to work quite right for me.  It
>picks up after three rings all of the time.  But logging in, etc. works just
>fine.

>Anyone else having the above problems?

        I'm having both of those problems. I thought I was doing something
wrong but maybe not. I don't know much about c programming but I'll try
reading the source code to see what's happening.

        John

 
 
 

Problems with dialing out when dial-ins are enabled

Post by Rafal Kust » Sun, 27 Jun 1993 12:31:05




>>Also, the new RINGBACK feature doesn't seem to work quite right for me.  It
>>picks up after three rings all of the time.  But logging in, etc. works just
>>fine.

>>Anyone else having the above problems?

>    I'm having both of those problems. I thought I was doing something
>wrong but maybe not. I don't know much about c programming but I'll try
>reading the source code to see what's happening.

>    John

Play with INTERRING, MINRBTIME and MAXRBTIME.
It solved a problem for me.
Here is mine uugetty.ttyS2:

#DEBUG=777
RINGBACK=YES

INTERRING=10
MINRBTIME=10
MAXRBTIME=45

INITLINE=cua2

TIMEOUT=45

INIT="" \r+++\dAT\r OK\r\n-\r+++\dAT\r-OK\r\n
ATM1L3S0=0\r OK\r\n

WAITFOR=RING
CONNECT="" \d\dATA\r CONNECT\s\A
DELAY=1

                        Rafal

--
/|| " Numbers exist only in our minds. There is no physical entity that
 ||  that _is_ number 1. If there were, 1 would be in a place of honor
 ||  in some great museum of science, and past it would file a
==== steady stream of mathematicians gazing at 1 in wonder and awe. "

 
 
 

1. supraexpress modems (28.8) problems w/dial-ins

Hello,

        I've configured my linux box to receive calls from two 28.8
SupraExpress modems (both support v.34).  Everything works fine, the
connection, everything.  However, when the user logs off, the modems
literally go bezerks and make the LED display shows pure garbage and
the SD/RD leds blinks relentlessly.  After that, the modem no longer
answer to commands issued by my system or to incoming calls, and I get
this kind of messages inside /var/adm/messages:

Feb 24 14:05:02 zeus kernel: ttyS0: 13 input overrun(s)

        for both ports.  The only solution is to power off the modem
and restart it.  Then, uugetty regains controls and accepts answers.

        Here's a copy of my /etc/default/uugetty.ttyS0 file:

CLEAR = NO
HANGUP=YES
#DEBUG=777
DEBUG=010
INIT="" AT&F2S0=1\r OK
ALTLOCK=cua0
ALTLINE=cua0
#WAITFOR=RING
#CONNECT="" ATs0=1\r CONNECT \s\A
TIMEOUT=60

        Help!

        ...David

--

// Socom technologies, Inc.        Tel: 514/939-0480 Fax: 514/939-0834
   " There are lies, damned lies, and statistics. " -- Mark Twain

2. Migrate With Confidence From Microsoft Windows Servers to UNIX/Linux

3. PPP dial-ins refused, OSR-5 with net100

4. Linux Commercial HOWTO (part 1/3)

5. Setting up firewall for dial-ins: How?

6. unable to send e-mail attachments

7. Can't get dial-ins, anyone?

8. Kingston and Linksys nic problems

9. Linux and Dial-ins (?)

10. Need Help on setting up getty for dial-ins

11. concurrent ppp dial-ins

12. Remote unix (RS/6000) servers with dial-ins

13. Can ISP detect when dial-ins are 'overloaded' ?