Knowledge
Knowledge: Useful Information about Delivery Notifications and Reasoncodes
Subsequently useful information that we were able to collect from our daily experience with sending SMS.
Many requests reaching our Support Team regard the interpretation of Delivery Notification.
What are Delivery Notifications?
A Delivery Notification informs you if a specific SMS has been delivered or not.
The ASPSMS Delivery Notifications are so called «Handset Notifications». A positive Notification does not only mean the Message has been sent, but also it reached the according mobile device.
If an SMS can't be delivered successfully, a Reasoncode indicates the cause of the failure.
Basically there are three different types of Delivery Notification:
Status 0: Delivered
If a Delivery Notification has Status 0, the SMS has been delivered successfully. There is no need for further analysis of the Reasoncode.
Status 1: Buffered
If a Delivery Notification has Status 1, the SMS could not be delivered immediately. In such a case the network will try to deliver the message for maximum 24 hours. To find out more about the reason of this failure the reasoncodes are very helpful.
In any case the SMS will get a final status code: 0 / Delivered or 2 / Failed.
Status 2: Failed
The delivery of the message definitely failed. There won't be any further delivery efforts. The Reasoncodes are useful to find out more about the cause of such a failure.
In the following you will find explanations of reasoncodes that appear the most in our daily work.
Recipient that does not or not anymore exist. Please check, if the number has been entered correctly.
This number has been barred by the provider. This Reasoncode has also occurred in context with empty prepaid cards which were barred for receiving SMS. Often it is still possible to call such a number.
107 is the most common Reasoncode. The mobile device is turned off or has no reception for some reason. As soon as the device is reachable again, most likely the reception of SMS will work again.
This Reasoncode often occurs when the memory of a mobile device is full. If the recipient deletes one or more stored messages, most likely the message will be delivered.
The validity of a message has expired. That means the system has tried to deliver the message for 24 hours unsuccessfully. The delivery has failed definitely.
In the past this error often occurred with certain mobile devices which were not able to handle alphanumeric originators correctly. Now the error occurres mostly when sending overlength messages (more than 160 chars). The concatenation is handled incorrectly within the mobile device and the message will not be displayed.
This code has often been sighted with roaming combinations in non European networks. Typically networks in North- and Southamerica are affected of this error.
This code has often been sighted with roaming combinations in non European networks. Typically networks in North- and Southamerica are affected of this error.
It was tried to send a message, but a failure, which could not be specified any further, occurred in the network. This error has been viewed in context with not reachable, barred or overloaded networks and warlike events.
This code has appeared several times when there was more than one SIM card with the same number signed on in the network. Often code 119 appears together with the use of communication systems which are not able to receive SMS (e.g. UMTS cards).
This code has appeared several times when there was more than one SIM card with the same number signed on in the network. Often code 119 appears together with the use of communication systems which are not able to receive SMS (e.g. UMTS cards).
Home Location Register - Indicates serious problems within the network of the recipient. This code occurs mostly when the recipients network is not reachable. In this case the chance is very little for the SMS to be sent later on. Most likely a delivery failure will be displayed after the validity of the message has expired.
Visiting Location Register Failure - Indicates problems within the network of the recipient. This reasoncode has already occured in combination with roaming problems, e.g. if the recipient was abroad and the foreign network has not negociated an SMS roamingagreement with his home network.
Click here for the ASPSMS new user registration.
Have you already registered? Log in with your user e-mail address and password.
Factsheets | |
---|---|
Purpose and business examples |
SMS tools for End Users | |
---|---|
Name | Pricing |
SMS Blaster Winlog | free |
Microsoft Office Outlook 2013-2016: Email to SMS | free |
Microsoft Office Outlook 2010 Mobile Service | free |
SMSBLASTER web edition | free |
SMS Blaster Windows Edition | free |
SMS touch for iPhone and iPod touch | Shareware |
ECO-SMS - Ökologische SMS! | Shareware |
Cybersystems mscrmSMS | see price list for details |
Jabber-Client Chatopus for Palm OS | small one-time payment |
delight Software GmbH | see price list for details |
ASPSMS Widget for Mac | free |
SMS scripts and interfaces for developers | |
---|---|
Name | Pricing |
ASPSMS Dot Net Assembly on NuGet | free |
ASPSMS JSON API (REST) | free |
C# Microsoft ASP.NET Identity MVC (for SOAP) | free |
Node.js interface for ASPSMS | free |
PHP Class for ASPSMS SOAP web service | free |
aspsms.dll (Active-X) | free |
SOAP Web Service | free |
XML-Interface | free |
ASPSMS SMTP Interface | free |
VBscript Class (ASP) | free |
HTTP | free |
PHP - Python - C# - Java | free |
Jabber to SMS for Server Admins | free (open source) |
SMS Blaster Visual Basic Source Code | free |
ASPTOKEN | free |
Network coverage | |
---|---|
Supported networks around the world |
Latest News
Finland
Supported operators in your country:
Alcom
DNA
Elisa Corporation
Telia Finland