[prev in list] [next in list] [prev in thread] [next in thread] 

List:       novalug
Subject:    Re: [novalug] inbound modem connection to Linux box.. modem will
From:       Bruce Hill <whizkid () ricochet ! net>
Date:       1999-09-29 14:40:12
[Download RAW message or body]

Miles - The following string is where the modem is setup to answer and such
this is the place to look with your modem book.
# format: <expect> <send> ... (chat sequence)
INIT="" AT\r OK\r\n
#INIT="" ATE1Q0V1S0=1&C1&S0\r OK\r\n
WAITFOR=RING
CONNECT="" ATA\r CONNECT\s\A

I would check the #Init part for turning on auto answer. I do not see it in
any of these strings and I don't know the exact wording for yours.

Hope that helps,

Bruce Hill




> Got a strange problem here on my linux box.
>
> Modem answers and gives carrier 'screech' when I am monitoring com2 with
>minicom. I see the ring, and then the carrier sound follows.
>
> When I get in and edit my inittab and uncomment the uugetty statement and
>try to dialin again, the modem answers but NEVER gives a carrier sound, it
>just waits and eventually hangs up.
>
> It is a USR sportster modem using the system defaults as far as DIP switch
>settings and config settings except for setting ATS0=1 for hardcoding into
>it to answer on the first ring. below is my /etc/conf.uugetty/ttyS1 config
>file.
>
># sample uugetty configuration file for a Hayes compatible modem to allow
># incoming modem connections
>#
># alternate lock file to check... if this lock file exists, then uugetty is
># restarted so that the modem is re-initialized
>ALTLOCK=ttyS1
>ALTLINE=ttyS1
># line to initialize
>INITLINE=ttyS1
># timeout to disconnect if idle...
>TIMEOUT=60
># modem initialization string...
># format: <expect> <send> ... (chat sequence)
>INIT="" AT\r OK\r\n
>#INIT="" ATE1Q0V1S0=1&C1&S0\r OK\r\n
>WAITFOR=RING
>CONNECT="" ATA\r CONNECT\s\A
># this line sets the time to delay before sending the login banner
>DELAY=1
>DEBUG=010
>
> Im pulling my hair out over this one. I've tried turning on debugging but
>it doesnt give me any input.  I cannot figure it out.
>
> It could be that minicom is passing a string to the modem that is allowing
>it to answer but so far I am at a loss. This is very strange.
>
> Anyone else see anything like this??
>
>
>To unsubscribe, send a message to esquire@tux.org with
>	unsubscribe novalug
>as the BODY of the message.  The SUBJECT is ignored.




To unsubscribe, send a message to esquire@tux.org with
	unsubscribe novalug
as the BODY of the message.  The SUBJECT is ignored.

[prev in list] [next in list] [prev in thread] [next in thread]