Davy, Thank you very much for your response. We're on post-paid and i found out that our GSM provider had cut us off cause we couldn't even call out. We normally use this number for only SMSes, that's why it was difficult to figure out.
Thanks one again, Allan On Mon, 28 Feb 2005 16:19:59 +0800, Davy Chan <[EMAIL PROTECTED]> wrote: > That's an "ME failure" error. Make sure the mobile device (phone, > standalone modem) can still be used to manually send an SMS. > > One major possibility is that the operator has deactivated the > SIM you are using in the modem. If it is a prepaid SIM, then > it could be because the SIM was not recharged before the expiration > of the current activation period. If it's a postpaid (term-subscription) > this the operator might have disabled the SIM because it noticed > a large amount of SMS traffic without a corresponding amount of > Voice traffic. > > Try the following steps: > Check the mobile device first: > - Check that the mobile device can send an SMS manually (e.g. if > it's a phone, then manually enter an SMS on the keypad and send > it). [fails here, then the device might have hardware problems > if the next step fails] > - Check if a different SIM in the questionable mobile device > can manually send an SMS [fails here, it might be a hardware > problem] > Check the SIM installed in the mobile device: > - Check if the SIM can be used in another phone to manually > send an SMS. [fails here, then the operator might have > deactivated the SIM] > - Check if the SIM in another device can send an SMS if in > a different location. [succeeds here, then you need to move > the mobile device to a location with better signal strength] > > See ya... > > d.c. > > **>Date: Mon, 28 Feb 2005 10:27:10 +0300 > **>From: Allan hank <[EMAIL PROTECTED]> > **>To: [email protected] > **>Subject: Can't send SMS > **>In-Reply-To: <[EMAIL PROTECTED]> > **> > **>Hello Kannel Users, > **> > **>I've been using kannel for some time ( 1 month) but of recent it has > **>turned to be a bizarre for me. I start it and it appeard to have > **>started well but it can't send an sms. Below is a dump of what i see > **>in kannel.log > **>There's nothing in bearerbox.* and smsbox.* > **> > **>I appreciate all the help, > **>Thank you > **>----- > **>Allan > **> > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: <-- OK > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: --> AT+CMGF=0^M > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: <-- OK > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: --> AT+CSMS=?^M > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: <-- +CSMS: (0) > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: <-- OK > **>2005-02-28 10:24:40 [5] DEBUG: AT2[/dev/cuaa1]: --> AT+CNMI=1,2,0,1,0^M > **>2005-02-28 10:24:41 [5] DEBUG: AT2[/dev/cuaa1]: <-- OK > **>2005-02-28 10:24:41 [5] INFO: AT2[/dev/cuaa1]: AT SMSC successfully opened. > **>2005-02-28 10:24:54 [4] DEBUG: Started thread 7 (gw/bb_boxc.c:function) > **>2005-02-28 10:24:54 [7] INFO: Client connected from <127.0.0.1> > **>2005-02-28 10:24:54 [7] DEBUG: Started thread 8 (gw/bb_boxc.c:boxc_sender) > **>2005-02-28 10:27:33 [7] DEBUG: boxc_receiver: sms received > **>2005-02-28 10:27:35 [5] DEBUG: AT2[/dev/cuaa1]: TP-Validity-Period: 24.0 > hours > **>2005-02-28 10:27:35 [5] DEBUG: AT2[/dev/cuaa1]: --> AT+CMGS=49^M > **>2005-02-28 10:27:35 [5] DEBUG: AT2[/dev/cuaa1]: <-- > > **>2005-02-28 10:27:35 [5] DEBUG: AT2[/dev/cuaa1]: send command status: 1 > **>2005-02-28 10:27:35 [5] DEBUG: AT2[/dev/cuaa1]: --> > **>11000B915276818899F10000A7276171FA1C168741D7347BFE7683D27310BD3CA7A7DD6785 > **>51FE6EEB40F7347BFE768300 > **>2005-02-28 10:27:35 [5] DEBUG: AT2[/dev/cuaa1]: --> ^Z > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: <-- > > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: <-- +CMS ERROR: 130 > **>2005-02-28 10:27:39 [5] ERROR: AT2[/dev/cuaa1]: CMS ERROR: +CMS ERROR: 130 > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: send command status: 1 > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: --> AT+CMGS=49^M > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: <-- > > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: send command status: 1 > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: --> > **>11000B915276818899F10000A7276171FA1C168741D7347BFE7683D27310BD3CA7A7DD6785 > **>51FE6EEB40F7347BFE768300 > **>2005-02-28 10:27:39 [5] DEBUG: AT2[/dev/cuaa1]: --> ^Z > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: <-- > > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: <-- +CMS ERROR: 130 > **>2005-02-28 10:27:42 [5] ERROR: AT2[/dev/cuaa1]: CMS ERROR: +CMS ERROR: 130 > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: send command status: 1 > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: --> AT+CMGS=49^M > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: <-- > > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: send command status: 1 > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: --> > **>11000B915276818899F10000A7276171FA1C168741D7347BFE7683D27310BD3CA7A7DD6785 > **>51FE6EEB40F7347BFE768300 > **>2005-02-28 10:27:42 [5] DEBUG: AT2[/dev/cuaa1]: --> ^Z > **>2005-02-28 10:27:44 [5] DEBUG: AT2[/dev/cuaa1]: <-- > > **>2005-02-28 10:27:44 [5] DEBUG: AT2[/dev/cuaa1]: <-- +CMS ERROR: 130 > **>2005-02-28 10:27:44 [5] ERROR: AT2[/dev/cuaa1]: CMS ERROR: +CMS ERROR: 130 > **>2005-02-28 10:27:44 [5] DEBUG: AT2[/dev/cuaa1]: send command status: 1 > **> >
