Including Bsnl Error code 44
Bulk SMS Plans is introducing BSNL ERROR CODES for bulk SMS which helps to better clarity of sms failed that to be delivered. These BSNL ERROR CODES will help you to understand the reason for failure and troubleshoot issues.
| Error Code | Description |
| -1 | This reason is captured when MAP Abort Error Type is not set in the response. |
| 0 | This reason is captured when SMS is delivered to specified destination successfully. |
| 1 | This reason is captured when Encoding error received from SS7/Sigtran-GW server |
| 2 | This reason is captured when SMSC local encoding error or local error due to MAX SMS length exceeded is occurred. |
| 5 | SMSC is configured to receive message of 160 chars without segmentation. If it receives large message (more than 160 chars and if the segmentation support in SMSC is set to 0) then SMSC will drop the message with LFR as SMSC_PR_LC_SMSC_LargeMessage. |
| 6 | This reason is captured when Source Address is Invalid (Cases like NID not matching with any rules (or) Address Translation rule is not defined in any of the rules) |
| 7 | This reason is captured when Destination Address is Invalid (Cases like NID not matching with any rules (or) Address Translation rule is not defined in any of the rules) |
| 8 | This reason is captured when Originator (Source Address) is barred by the operator. |
| 9 | This reason is captured when Destination Address is barred by the operator. |
| 10 | This reason is captured when Destination ESME is blocked. |
| 11 | This reason is captured when SMS Originating MSC Address is barred. |
| 12 | This reason is captured when SMS Destined MSC Address is barred. |
| 13 | This reason is captured when Service centre address is not packed or encoding of send routing request failed for MT. |
| 15 | This reason is captured when SMSC does not receive response from ESME for the request within a specified time. |
| 16 | If the SRI/MT request is timed out and the message state in MsgInfo buffer is NULL then the default last failure reason is written as SMSC_TM_LC_TimeoutError. |
| 18 | This reason is captured when the delivery receipt for the international message is not received by SMSC from ESMEGw within the specified time. |
| 19 | This reason is captured when no response is received from Prepay server within the specified time interval for the request sent by SMSC. |
| 20 | This reason is captured when Originator is Not Having Enough Balance. |
| 21 | This reason is captured when Destination Number is not having enough Balance. |
| 22 | This reason is captured when there is an error in packing charging request. |
| 23 | This reason is captured when subscriber is unknown or no such Subscription exists error is received as part of SRI response. |
| 24 | This reason is captured when the Call is being barred. i.e the PLMN rejects the short message TPDU due to barring of MS. This error is received as part of SRI response. |
| 25 | This reason is captured when the facility requested by the Mobile station is not supported by the PLMN. This error is received as part of SRI response. |
| 26 | This error is returned only if not even a subset of the requested teleservice group has been subscribed to. This error is received as part of SRI response. |
| 27 | This reason is captured when Subscriber is not reachable or when the MS is switched OFF at the Time of SRI. |
| 28 | This reason is captured when Subscriber is not reachable or when the MS is switched OFF at the Time of SRI for SRI request with map version as 3. |
| 29 | This reason is captured when requested task cannot be performed because of problem in network resource or other entity at the time of SRI. |
| 30 | This reason is captured when an optional parameter required by the context is missing during SRI. |
| 31 | This reason is captured when the data type is formally correct but its value or presence is unexpected in the current context at the time of SRI. |
| 32 | This reason is captured when illegality of the access has been established by use of authentication procedure. |
| 33 | This reason is captured when the IMEI check procedure has shown that the IMEI is blacklisted or not white-listed. |
| 34 | This reason is captured when the requested facility is not supported by the PLMN. This error is received as part of MT response. |
| 35 | This reason is captured when Subscriber is not reachable or when the MS is switched OFF at the Time of MT. |
| 36 | This reason is captured when Subscriber is not reachable or when the MS is switched OFF at the Time of MT for MT request with map version as 3. |
| 37 | This reason is captured when the subscriber is not contained in the database and it has not or cannot be established whether or not a subscription exists. This error is received as part of MT response. |
| 38 | This reason is captured when a SMS is about to be delivered but the channel is busy as the subscriber is receiving another message. i.e Mobile terminated short message transfer cannot be completed because another mobile terminated short message transfer is going on. This error is received as part of MT response. |
| 39 | This reason is captured when requested task cannot be performed because of problem in network resource or other entity at the time of MT. |
| 40 | This reason is captured when an optional parameter required by the context is missing during MT. |
| 41 | This reason is captured when the data type is formally correct but its value or presence is unexpected in the current context at the time of MT. |
| 42 | This reason is captured when the mobile memory capacity exceeded or MS protocol error or MS not equipped or subscriber is not a SC subscriber. (MAP) |
| 43 | This reason is captured when failure cause code is not received as part of the response. |
| bsnl error code 44 | This reason is captured when the Telematic Interworking is not supported by SMSC |
| 45 | This reason is captured when the message type is not supported by SMSC or Mobile. |
| 46 | This reason is captured when short message cannot be replaced by SMSC or Mobile. |
| 47 | This reason is captured when PID error is unspecified by SMSC or mobile. |
| 48 | This reason is captured when Data Coding Scheme(alphabet) is not supported. |
| 49 | This reason is captured when Message class is not supported. |
| 50 | This reason is captured when Data Coding Scheme Error is not specified by SMSC or Mobile. |
| 51 | This reason is captured when action cannot be taken for a command by SMSC. |
| 52 | This reason is captured when Command is not supported by SMSC. |
| 53 | This reason is captured when command error is not specified by SMSC. |
| 54 | This reason is captured when TPDU is not supported by SMSC or mobile. |
| 55 | This reason is captured when SMSC is busy. |
| 57 | This reason is captured when requested task cannot be performed because of problem in network resource or other entity at service centre. |
| 58 | This reason is captured when the destination address is invalid. |
| 59 | This reason is captured when destination number is barred. |
| 60 | This reason is captured when receive the duplicated message. |
| 61 | This reason is captured when Validity Period Format is not supported |
| 62 | This reason is captured when Validity Period is not supported. Ex |
| 63 | This reason is captured when SIM short message Storage Capacity is full. |
| 64 | This reason is captured when there is no SMS storage capability in SIM. |
| 65 | This reason is captured when (there is an error in MS.) the PLMN rejects the short Message TPDU due to an error occurring within the MS at reception of short Message. Ex |
| 66 | This reason is captured when MS is busy with some application. |
| 67 | This reason is captured when there is an error while downloading data by SIM. |
| 69 | This reason is captured when error cause received in the response is not specified or unknown. |
| 70 | This reason is captured when mobile memory capacity is exceeded. |
| 71 | This reason is captured when the component type is not recognized. |
| 72 | This reason is captured when the elemental structure of a component does not conform to the structure of that component as defined. |
| 73 | This reason is captured when a fundamental encoding problem is occurred in component portion. (e.g bad length). |
| 74 | This reason is captured when the operation code is not one of those agreed by the two TC-User. |
| 75 | This reason is captured when an unidentified parameter is received in invoke component. |
| 76 | This reason is captured when the requested operation cannot be invoked because the dialogue is about to be released. |
| 77 | This reason is captured when the received linked ID does not correspond to an active invoke operation. |
| 78 | This reason is captured when the operation referred to by the linked ID is not an operation for which linked invokes are allowed. |
| 79 | This reason is captured when the operation referred to by the linked ID does not allow this linked operation. |
| 80 | This reason is captured when the invoke ID is that of a previously invoked operation which has not been completed. |
| 81 | This reason is captured when Sufficient resources are not available to perform the requested operation. |
| 82 | This reason is captured when no operation with the specified invoke ID is in progress. |
| 83 | This reason is captured when the invoke operation does not report success. |
| 84 | This reason is captured when an unidentified parameter is received in return result component. |
| 85 | This reason is captured when the received invoke ID does not reflect an operation that is currently progress in return error component. |
| 86 | This reason is captured when the return error component did not report failure of the invoked operation. |
| 87 | This reason is captured when the reported error has not been defined by the application. |
| 88 | This reason is captured when the reported error is not applicable to the invoked operation. |
| 89 | This reason is captured when an unidentified parameter is received in return error component. |
| 90 | This reason is captured when the message type is not defined. |
| 91 | This reason is captured when a transaction ID has been received for which a transaction does not exist at the receiving node. |
| 92 | This reason is captured when badly formatted transaction portion is received in TC-P-ABORT. |
| 93 | This reason is captured when incorrect transaction portion is received in TC-P-ABORT). |
| 94 | This reason is captured when there is a congestion towards MAP peer service user or resource limitation received in TCP- ABORT. |
| 95 | This reason is captured when the Abort is received from service user level. |
| 96 | This reason is captured when the Abort is received from service provider level. |
| 177 | This reason is captured when there is system error and is indicated by command status field of an SMPP message Response. |
| 178 | This reason is captured for ESME Receiver temporary application error code and is indicated by command status field of an SMPP message Response. |
| 179 | This reason is captured when an invalid Message length received as part of bind request or SubmitSM / DataSM Request originated by ESME. |
| 180 | This reason is captured when an invalid Command length received as part of bind request or SubmitSM / DataSM Request originated by ESME. |
| 181 | This reason is captured when Command ID received as part of bind request or SubmitSM / DataSM Request originated by ESME. |
| 182 | This reason is captured for incorrect Bind Status requested in bind request from an ESME. |
| 183 | This reason is captured when an ESME bind request is received and if the ESME is already in bound state. |
| 184 | This reason is captured for Invalid Priority Flag as part of SubmitSM / DataSM Request originated by ESME. |
| 185 | This reason is captured for Invalid Registered Delivery Flag received as part of SubmitSM / DataSM Request originated by ESME. |
| 186 | This reason is captured for Invalid Source Address received as part of SubmitSM / DataSM Request originated by ESME. |
| 187 | This reason is captured for Invalid Destination Address received as part of SubmitSM / DataSM Request originated by ESME. |
| 188 | This reason is captured when Message ID is Invalid as part of SubmitSM / DataSM Request originated by ESME. |
| 189 | This reason is captured when received ESME bind information is incorrect and then the response is indicated by command status field of an SMPP message Response. |
| 190 | This reason is captured when an Invalid Password is received as part of ESME bind request. |
| 191 | This reason is captured when an Invalid System ID is received as part of ESME bind request. |
| 192 | This reason is captured when a cancel SM request is received from ESME and SMSC is unable to cancel the short message. |
| 193 | This reason is captured when a replace SM request is received from ESME and SMSC is unable to replace the SMS. |
| 194 | This reason is captured when Message Queue is full on SMSC to handle the ESME originated requests. |
| 195 | This reason is captured for Invalid Service Type received as part of SubmitSM / DataSM Request originated by ESME. |
| 196 | This reason is captured for Parameter Retrieval failure and is indicated by command status field of an SMPP message Response. |
| 197 | This reason is captured for Invalid Parameter and is indicated by command status field of an SMPP message Response. |
| 198 | This reason is captured for Invalid Number of Destinations and is indicated by command status field of an SMPP message Response. |
| 199 | This reason is captured for Invalid Distribution List Name and is indicated by command status field of an SMPP message Response. |
| 200 | This reason is captured for Invalid Submit with Replace Request and is indicated by command status field of an SMPP message Response. |
| 201 | This reason is captured for Invalid esm_class field Data received as part of SubmitSM / DataSM Request originated by ESME. |
| 202 | This reason is captured when message submission to distribution List is not allowed and is indicated by command status field of an SMPP message Response. |
| 203 | This reason is captured when submit_sm or submit_multi request from ESME is failed on SMSC and is indicated by command status field of an SMPP message Response. |
| 204 | This reason is captured for Invalid Source Address TON received as part of SubmitSM / DataSM Request originated by ESME. |
| 205 | This reason is captured for Invalid Destination Address NPI received as part of SubmitSM / DataSM Request originated by ESME. |
| 206 | This reason is captured for Invalid Destination Address TON received as part of SubmitSM / DataSM Request originated by ESME. |
| 207 | This reason is captured for Invalid Destination Address NPI received as part of SubmitSM / DataSM Request originated by ESME. |
| 208 | This reason is captured for Invalid system_type received as part of SubmitSM / DataSM Request originated by ESME. |
| 209 | This reason is captured for Invalid replace_if_present flag received as part of SubmitSM / DataSM Request originated by ESME. |
| 210 | This reason is captured for Invalid Number of Messages value received as part of SubmitSM / DataSM Request originated by ESME. |
| 211 | This reason is captured when ESME has Exceeded allowed Message Limits (Throttling error) of SubmitSM / DataSM messages. |
| 212 | This reason is captured for Scheduled Delivery Time of message is invalid received as part of SubmitSM / DataSM Request originated by ESME. |
| 213 | This reason is captured for Invalid Message Validity period (Expiry Time) received as part of SubmitSM / DataSM Request originated by ESME. |
| 214 | This reason is captured when default Message ID value received as part of SubmitSM / DataSM Request originated by ESME. |
| 215 | This reason is captured for ESME Receiver Temporary Application Error Code and is indicated by command status field of an SMPP message Response. |
| 216 | This reason is captured for ESME Receiver Permanent Application Error Code and is indicated by command status field of an SMPP message Response. |
| 217 | This reason is captured when ESME sent the Query message, unable to process by SMSC. i.e. query_sm request failed and is indicated by command status field of an SMPP message Response. |
| 218 | This reason is captured for Delivery failure used for data_sm_resp if the message delivery is failure on SMSC. |
| 219 | This reason is captured for unknown error and is indicated by command status field of an SMPP message Response. |
| 220 | This reason is captured when Message licensing exceeded. |
| 221 | This reason is captured when Source address is a Closed User Group member whereas Destination Address is not a Closed User Group member. |
| 222 | This reason is captured when Originator Address is Black Listed. |
| 223 | This reason is captured when Destination Address is Black Listed. |
| 224 | This reason is captured when all SS7Linksets are down in SMSC. |
| 225 | This reason is captured when SRI response not received within configured time. |
| 226 | This reason is captured when MT response is not received within configured time. |
| 227 | This reason is captured when subscriber doesn’t have enough Balance. |
| 228 | This reason is captured when accounting response is not received from DIAMETER within configured interval of time. |
| 229 | This reason is captured when Subscriber is not prepaid subscriber. |
| 230 | This reason is catured when there is no response from the subscriber database. |
| 231 | This reason is catured when the Mobile orginating licensing is exceeded. |
| 232 | This reason is captured when the Originator's NID range is barred. |
| 233 | This reason is captured when the Destination's NID range is barred. |
| 234 | This reason is captured in provisioned mode when the originator's address is not provisioned in the DB. |
| 235 | This reason is captured when the Destination's NID range is barred. |
| 236 | This reason is captured in provisioned mode when the originator's address is not provisioned in the DB. |
| 237 | This reason is captured in provisioned mode when the destination address is not provisioned in the DB. |
| 238 | This reason is captured when a message is sent to a destination address whose nid rule is not matched. |
| 239 | This reason is captured when the international rule is not matched. |
| 240 | This reason is captured when the Landline range doesn’t match |
| 241 | This reason is captured when the ESME rule is not matched. |
| 242 | This reason is captured when the national NID range is not defined for the destination. |
| 243 | This reason is captured when the International NID Range is not defined. |
| 244 | This reason is captured when the landline number does not belong to any landline range defined. |
| 245 | This reason is captured when the destination has barred the originator address. |
| 246 | This reason is captured when all SS7 Links are down with the STP while sending SRI Request. |
| 247 | This reason is captured when the Originators' prepaid type is not configured. |
| 248 | This reason is captured when the Destination prepaid type is not configured. |
| 249 | This reason is captured when there is no responserecieved from the SMPPLUS IN after a specified interval of time. |
| 250 | This reason is captured when Prepaid Subscriber doesn’t have sufficient balance. |
| 251 | This reason is captured when SMPP Subscriber is Invalid. |
| 252 | This reason is captured when the Message validity has expired. |
| 253 | This reason is captured when there is no connectivity with Diameter server. |
| 254 | This reason is captured when other than No Balance, Service denied, Invalid Subscriber, Diameter-Server Unavailable and connect failed. |
| 255 | This reason is captured when service is Denied to the user by IN. |
| 256 | This reason is captured when SMPP other Error is encountered. |
| 257 | This reason is captured when service is Denied to the user by the IN. |
| 258 | This reason is captured when there is no connectivity with the SMPP PLUS IN Server |
| 259 | This reason is captured when the TCAP Abort is received with unknown cause. |
| 260 | The reason is captured when SM Delivery Failure with equipment Protocol Error is received as part of Mobile terminate response. |
| 261 | The reason is captured when the ESME’s validity period is expired in the SMSC. |
| 262 | The reason is captured when the MO for the ESME is blocked by the operator. |
| 263 | This reason is captured when SMSC is unable to insert the message in the retry pending table. |
| 269 | System failure (unknown error code) |
BULK SMS PLANS CONNECTING YOU TO THE WORLD.
These figures don't tell the whole story,We add value to your business in more than one way
25+ Billions
SMS Processes Annually
500+
Direct Mobile Operator Connections
50000+
Customers & Resellers Accessible Worldwide
200+
Countries Coverd