On Thu, Mar 05, 2009 at 10:50:13PM +0100, Didier Wiroth wrote: > Thanks a lot for the help!!! > > The logging help now returns the following error: > Mar 5 22:42:54 406334G chat[14042]: SIGTERM > Mar 5 22:43:01 406334G chat[9395]: abort on (BUSY) > Mar 5 22:43:01 406334G chat[9395]: abort on (NO CARRIER) > Mar 5 22:43:01 406334G chat[9395]: abort on (VOICE) > Mar 5 22:43:01 406334G chat[9395]: abort on (NO DIALTONE) > Mar 5 22:43:01 406334G chat[9395]: send (ATZ^M) > Mar 5 22:43:01 406334G chat[9395]: expect (OK) > Mar 5 22:43:01 406334G chat[9395]: TZ^M^M > Mar 5 22:43:01 406334G chat[9395]: ERROR^M > Mar 5 22:43:46 406334G chat[9395]: alarm > Mar 5 22:43:46 406334G chat[9395]: Failed > > Unfortunately these AT commands are chinese to me,
I don't understand much of it either. You can search the web for "at command set" to get information on them. To understand what chat does, read the chat(8) man page. It has a section called CHAT SCRIPT which explains things quite well. > I can see the error but, > what's wrong in the chat file: > ABORT BUSY > ABORT "NO CARRIER" > ABORT VOICE > ABORT "NO DIALTONE" > "" ATZ > OK AT+CPIN="9907" > OK AT+CGDCONT=1,"IP","web.pt.lu" > OK ATDT*99***1# > 'CONNECT' '\c' > 'TIMEOUT' '5' The script looks good to me, but I'm certainly not an expert. I used a similar script once with a umts modem and it worked. I had "" AT instead of "" ATZ though, and I didn't need the PIN, else pretty much the same. Stefan
