hmm, this is the snip from the mgetty log for the modem that works. 05/23 08:50:13 yS1 send: \dATQ0V1H0[0d] 05/23 08:50:14 yS1 waiting for ``OK'' 05/23 08:50:14 yS1 got: ATQ0V1H0[0d] 05/23 08:50:14 yS1 CND: ATQ0V1H0[0d][0a]OK ** found ** 05/23 08:50:14 yS1 send: ATS0=0Q0&D3&C1[0d] 05/23 08:50:14 yS1 waiting for ``OK'' 05/23 08:50:14 yS1 got: [0d] 05/23 08:50:14 yS1 CND: OK[0a]ATS0=0Q0&D3&C1[0d] 05/23 08:50:14 yS1 CND: ATS0=0Q0&D3&C1[0d][0a]OK ** found ** ... notes below... Florin Iucha wrote: > On Wed, May 23, 2001 at 12:54:19PM -0500, John Hawley wrote: > > Anyone else have problems getting mgetty to work with an internal USR > > 56K PCI (non-win) modem (on ttyS2)? The mgetty / AUTOppp dial-in > > services I've been playing with works fine on an external modem on > > ttyS1. > > > > Minicom connects to ttyS2 fine (when not locked by mgetty) and I'm > > seeing the verbose result codes. I can intercept an incoming call by > > doing an ATA so I believe I believe the hardware is set up right. > > > > The mgetty.ttyS2 log shows loops containing this: > > > > 05/23 11:26:04 yS2 send: \dATQ0V1H0[0d] > > 05/23 11:26:04 yS2 waiting for ``OK'' > > 05/23 11:26:04 yS2 got: ATQ0V1H0[0d] > > this tells me two things: > > 1. You have echo on. I guess you don't need that. its the same init-chat string as on the modem that works (the default). I've tried various combinations for a custom init-chat, turning echo on and off, etc. same results. > > 2. Maybe the timeout is too short. You can play with modem's registers what timeout? This is a dialin test. There is no dial string for the comma. When in minicom I instantly get the 'OK' after an AT command. > > > And the third thing: when I was in Phoenix,AZ (serviced by [US|Q]West as well) > it happened at times for the dialtone to come after 3-5 seconds after I opened > the line : it happened both in modem and the phone. Some "," in the dialout > string helped. "," is "wait two seconds". > > Weird enough the PPP dialer on FreeBSD didn't choke as the one from Linux. > > > 05/23 11:26:04 yS2 CND: ATQ0V1H0 > > 05/23 11:26:24 yS2 timeout in chat script, waiting for `OK' > > 05/23 11:26:24 yS2 init chat timed out, trying force-init-chat > > 05/23 11:26:24 yS2 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d] > > 05/23 11:26:28 yS2 waiting for ``OK'' > > 05/23 11:26:28 yS2 got: [10][03]+++[0d] > > 05/23 11:26:28 yS2 CND: __+++ATQ0V1H0[0d] > > 05/23 11:26:28 yS2 CND: ATQ0V1H0 > > ... and I do see [RING]'s coming in when I put through a test call. > > > > Any clues? > > -John > > > > Oh, this is on a Debian Woody with kernel 2.4.2 and mgetty1.1.26-Apr16 > > compiled from source. > > Used to be 2.2.xx back then, but I don't think it matters much. > > florin > -- > > "you have moved your mouse, please reboot to make this change take effect" > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list -- John Hawley BGEA/ITS <=> Network Admin 612.335.1334 jhawley at bgea.org