Hi, we get one of these errors for prepaid short codes. Here are some description from our provider:
"For prepay, successful delivery of a message can only occur when the end user has sufficient credit available to pay for the requested message. If the end user has insufficient credit, then the message will not be delivered and you will not receive an ACK. You will however receive the Message_Queue_Full error (command_status = 0x00000014). This SMPP error code actually indicates that a message has failed for one of three reasons: (i) A customer has insufficient credit to receive the message. (ii) There is an outstanding premium rate message for that customer already. (iii) Congestion exists on the prepay system preventing billing of this message. " 0x00000058 is a throttling error ganerated by SMSC when queue exceeded configured limit. In our case if i get this error i shall to wait min 15 sec before to send next MT message. Anyway these errors generate SMSC and you may ask them for help with their logs and configuration parameters to clear situation. cheers, Dima Milentiev m-Wise Mobile Solutions [EMAIL PROTECTED] Mobile: +972 (55) 679229 Tel: +972 (9) 9581711 (ext: 120) -----Original Message----- From: Rajesh [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 01, 2002 6:51 AM To: [EMAIL PROTECTED] Subject: SMPP failure : error code 0x00000014 Can anyone help on this? This has been going on for quite long and we dont seem to have any clue.. When we are trying to send the messages to the SMSC, either we are getting 0x00000058 or 0x00000014. The descriptions for both the errors are more or less related to message limit and queue limit. We are using SMPP protocol with Kannel 1.0.3 Version and CMG SMSC. Earlier we use to face the error 0x00000014 error for binary messages. When a binary message is long, then our application will fragment it into appropriate fragments. We use to get this 0x00000014 error for the 2nd fragment out of 3 fragments. Our application used to make independent MT requests for that many number of fragments. For example if the binary message is somewhere around 180 bytes, then our application used to fragment it into 3 fragments and make 3 independent MT requests to the sendsms port of the smsbox. The strangest thing is, Wapit Kannel is running on the same service-code successfully whereas our's is not. When we are asking the assistance from the SMSC people, they simply say that our queue limits should be increased. As far as i know, i don't see any such queue limits on our gateway. Does anyone has any ideas on this. Rgds -- ---------------------- Rajesh Venkateshvaralu Senior Developer OpenMobile Asia Pacific Pte Ltd 200, Cantonement Rd #14-01, Southpoint Singapore - 089763 Ph: 63247791 ----------------------
