SMS Status Codes (Operator Level)

On submission of a message to any operator, we associate one of the following status codes to every SMS to track the status. The common status codes received while using any API are as follows:



StatusDescription
ABSENT-SUBTelecom services not providing service for the particular number. / Mobile Subscriber not reachable.
BARREDEnd user has enabled message barring system. / Subscriber only accepts messages from Closed User Group [CUG].
DELIVRDSMS successfully delivered.
EXPIREDSMS expired after multiple re-try.
FAILEDSMS expired due to roaming limitation. / Failed to process the message at operator level.
HANDSET-BUSYSubscriber is in busy condition.
HANDSET-ERRProblem with Handset or handset failed to get the complete message. / Handset doesn’t support the incoming messages.
HEADER NOT REGISTERED FOR TEMPLATEThe Sender ID used along with the template ID do not match as per the registration in DLT portal
INVALID_TEMPLATE_ID / TL-ID-INVLDThe Template id received is in the wrong format or there is no Template id tag.
INVALID-SUBNumber does not exist. / Failed to locate the number in HLR database.
MEMEXECHandset memory full.
MOB-OFFMobile handset in switched off mode.
NET-ERRSubscriber’s operator not supported. / Gateway mobile switching error.
NO-DLR-OPTRIn case the operator has not acknowledged on the status report of the SMS.
OUTPUT-REJUnsubscribed from the group.
REJECTEDSMS Rejected as the number is blacklisted by operator.
REJECTED-MULTIPARTValidation fail [SMS over 160 characters]
SERIES-BLKSeries blocked by the operator.
TEMPLATE BLACKLISTEDThe message template pushed has been blacklisted at the DLT platform level.
TEMPLATE INACTIVEThe message template sent is in an inactive status at the DLT platform level.
TEMPLATE NOT MATCHEDThe template does not match the template registered on the DLT platform
TEMPLATE VARIABLE EXCEEDED MAX LENGTHThe variable content sent exceeds the allowed limit (30 characters)
UNDELIVFailed due to network errors.


SMS Status Codes (Platform Level)

The following are error codes at the application level.

 

StatusDescription
AWAITED-DLRMobile number has been accepted and submitted to the operator. Awaiting delivery report from the operator
BLACKLISTBlacklisted number
DNDNUMBDND registered number.
INV-NUMBERInvalid number.
INV-TEMPLATE- MATCHIn case the message given in any one of the nodes does not match the template approved for the sender ID in the same node
MAX-LENGTHIn case the message given in any one of the nodes exceeds the maximum of 1000 characters
NO-CREDITSInsufficient credits.
NOT-OPTINNot subscribed for opt-in group.
SENDER-ID-NOT-FOUNDSender ID not found.
SERIES-BLOCKMobile number series blocked.
SERVER-ERRServer error
SNDRID-NOT-ALLOTEDSender ID not allocated.
SPAMSpam SMS
TEMPLATE NOT FOUND / TEMPLATE-NOT-FOUNDThe message content sent was not found in the DLT platform as a registered template. Template not mapped.
TIME-OUT-PROMTime out for promotional SMS.


SMS Status Codes- HTTP API (On Submission)

When we receive an API call for sending SMS one of the following status code is attached at the application level.

The common status codes received while using the API are:

StatusDescription
AWAITED-DLR


Mobile number has been accepted and submitted to the operator. Awaiting delivery report from the operator
INVALID-NUM


In case any invalid number present along with the valid numbers.


SMS Status Codes-XML/JSON API (On Submission)

There could be one or more nodes in an XML API, each of those nodes can have a different status code on submission. The common status codes received while using the API are:


Status

Description

AWAITED-DLR

Mobile number has been accepted and submitted to the operator.Awaiting delivery report from the operator

DNDNUMB

Mobile number is DND.

OPTOUT-REJ

Opt out from subscription.

INVALID-NUM

In case any invalid number present along with the valid numbers.

SENDER-ID-NOT-FOUND

In case the sender ID given in any one of the nodes is not available

INV-TEMPLATE- MATCH

In case the message given in any one of the nodes does not match the template approved for the sender ID in the same node

MAX-LENGTH

In case the message given in any one of the nodes exceeds the maximum of 1000 characters