On 13/06/11 23:45, Brian wrote: > On Mon 13 Jun 2011 at 22:02:17 +1000, Scott Ferguson wrote: > >> On 13/06/11 20:37, Brian wrote: >>> >>> I'd be inclined to have >>> >>> OK ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> >> What is that supposed to do? > > Not a lot, apparently. I cut it out and there was still a connection.
Oh - I was hoping you knew the proprietary AT commands used by this particular modem. > >>> OK AT+CGDCONT=1,"IP","inet.bell.ca" >> >> The form is correct for INIT2. The OK line is not used in ppp. >> (it's a response from the modem) eg. INIT2 would be just:- AT+CGDCONT=1,"IP","inet.bell.ca" > > So I got rid of this too. And the username/password lines. Without the > ABORT lines the chatscript is down to > > '' ATZ > OK "ATDT*99#" You *can* connect with just a single CLI instruction... eg. # pppd ttyUSB0 460800 nodetach defaultroute noipdefault noauth lock usepeerdns connect 'chat "" "at" "" "at" "OK" "at&f" "OK" "atz" "OK" "atdt*99***1#" CONNECT' But it's not a useful form for testing purposes.... > > So much for searching out the files on the dongle aimed at Apple Mac > users and taking note of advice given to Windows users of the same ISP, > all of which referred to an APN and username/password! It's the first place I'd look if I couldn't get access to the manual - it just needs to be adjusted to suit the dialer. It was probably not meant for pon scripting - ppp dialer like wvdial and kppp use a (slightly) different form. Treat the following with caution as I can't verify this:- I "believe" the reasoning behind supplying the APN every connection is that some ISPs have different APNs for mobile, fixed line, and prepaid accounts. (Telstra for instance, has half a dozen) So a user might use the same modem to connect using different accounts to the same ISP - just picking the best rate plan for the particular area. > > It's a PAYG dongle, if that makes any difference. It often does. If I knew your ISP I could be more specific. eg. Vodaphone in the UK uses one APN for prepaid and another for post-paid. > I expect a first-time > connection have taken place with the chatscript as it stands now as the > SIM would have been recognised. > > You can test that by using the single line CLI connection commands I've posted above - just modify the connection port and speed to suit your requirements. If it connects then you'll have "proven" that the APN is supplied by the modem. I don't know the *nix equivalent, but on Windoof I've used a USB bus sniffer to see the communication between the modem and the OS - so I know the APN is retained on the device. I don't know if it (sic) is stored on the SIM or on the modem it self. If I sound unsure of myself it's because I am. Each case is different - even from the same manufacturer. Additionally modems are often customized for particular ISPs (eg. ZTE MF-627 with hidden ports for 3Mobile). Additionally there isn't a standard in the AT commands used - though many of them originate from the Rockwell chipset. Christian's modem from Bell for instance is about 80% standard AT commands and 20% proprietary. Proprietary (in this case) == closed. But I digress, and I note that Christian has already spent 6 months trying to connect with his modem, so I'll try not to add more non-essential information to his reading list. Cheers -- We all pay for life with death, so everything in between should be free. ~ Bill Hicks -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
