|
|
RoutoMessaging account clients can select to receive real-time delivery receipts for the messages they send. Know within seconds that the message has been delivered to the handset providing critical return information on the success of SMS and MMS campaigns and communications.
Receiving Delivery Reports differs per connection protocol, method used to send SMS or MMS:
- HTTP
- SMPP
- Manually Download on our Command Centre
- Using Desktop SMS Application to Send Messages and then Receive Delivery Reports.
Delivery reports over HTTP
When connected to our SMS gateway via HTTP protocol, we provide an option for you to automatically receive delivery reports to your Server by sending reports via a CGI script on your web server. For this you only need to provide us with an absolute path (URL) pointing to the CGI script on your web interface.
This URL must be entered in the ‘Account Info’ section of the Command Centre:
https://www.routomessaging.com/cust/index.php?do=account, (URL for reports).
Please note that the URL must be inserted without leading "http://". For example, if URL to your script is http://mywebserver.com/delivery.php, you would need to insert only "mywebserver.com/delivery.php".
More information regarding delivery report scripts and message statuses can be found in our online documentation. Specifically in Appendix C of document entitled "RoutoMessaging HTTP specification".
Please see: RoutoMessaging HTTP Specification.
Delivery reports over SMPP
Exchange of messages via SMPP protocol can be categorized under 3 types of connection - Connect as transmitter, receiver or transceiver.
To receive delivery reports from our servers you need to be connected as receiver or transceiver. This is because, according to the SMPP 3.4 communication model, you need to have bind_receiver or bind_tranceiver session in order to receive deliver_sm PDU.
Please Note: If you are not connected (or connected as transmitter), delivery reports for your account will be stored and pending on our side, waiting for you to collect them. When receiver connection is established again you will be able to receive reports for all messages you have sent through our gateway.
Upon receiving a final status of the previously submitted message (using submit_sm command) and in case you have requested a delivery receipt via the registered_delivery parameter, deliver_sm is issued by the SMSC. The delivery receipt data will be included in the short message field of the deliver_sm. After receiving this, your software should respond with deliver_sm_resp command, stating successful accept of delivery receipt.
Below is a list of statuses supported by the SMPP protocol:
DELIVRD (0) - message has been successfully delivered to subscriber
EXPIRED (3,253) - message not successfully delivered for certain amount of time, subscriber absent for a long time, (usually more than 24 – 72 hours)
DELETED (4,252)
UNDELIV (5,9,251) - message undeliverable, mostly because of invalid destination number (unknown subscriber) or message was sent to non-GSM number
ACCEPTD (6) - message accepted for further processing
REJECTD (1,8,10,11,49,69,72,73,80,249) - messages rejected, mostly because of improper message settings
UNKNOWN (any other value)
More information regarding SMPP 3.4 protocol can be found in our online documentation, available at SMPP 3.4.pdf
Command Centre delivery reports
Delivery reports can be easily accessed through the Command Centre web page by clicking on "Tools" > "Reports" on the left side of the screen, or more easily by following this link: https://www.routomessaging.com/cust/index.php?do=reports
Please note:
There is a report filter that enables you to view reports based on specific criteria, such as:
- A chosen time period
- Specific mobile numbers
- Specific message IDs
- Sender IDs
For reports older than 4 days please follow link: "to search older messages, click here".
Reports can also be downloaded in CSV format.
RoutoMessaging Desktop SMS Sender delivery reports
When sending messages using Desktop SMS Sender (PC to SMS, PC to MMS), delivery reports for messages sent are located in Delivery reports folder. Delivery reports are downloaded by clicking Receive Delivery Reports button in the upper menu of the application. This folder enables you to clearly review all relevant information for each message you have sent such as; sender, number, message, date and time of receiving, status of the message (delivered, no status, rejected etc.).
When sending group SMS or MMS, a new window will open up showing the list of contacts from the group you selected, message text and other important data. When messages to the contact group are sent, you will be able to click on a "Get Delivery" button, thus downloading all delivery reports for them. By clicking on the "Export" button, you will be provided with an option to save your delivery reports in CSV format and this report will contain information about message ID, destination number and status of the message.
Bellow you will find some example Screen Shots:
PC SMS Delivery Message Folder
Option to Export the Reports in CSV file.
Example Delivery Report Code:
| Status can be: | |
| 1 | Delivered |
| 2 | Subscriber absent |
| 3 | Device memory capacity exceeded |
| 4 | Equipment protocol error |
| 5 | Equipment not supported |
| 6 | Equipment not SM equipped |
| 7 | Unknown service centre |
| 8 | Service centre congestion |
| 9 | Invalid SME address |
| 10 | Not SC subscriber |
| 11 | Unknown subscriber |
| 12 | Illegal subscriber |
| 13 | Teleservice not provisioned |
| 14 | Illegal equipment |
| 15 | Call barred |
| 16 | Facility not supported |
| 17 | Subscriber busy for SM |
| 18 | System failure |
| 19 | Message waiting, list full |
| 20 | Data missing |
| 21 | Unexpected data value |
| 22 | Resource limitation |
| 23 | Initiating release |
| 24 | Unknown alphabet |
| 25 | USSD busy |
| 26 | Duplicated invoke ID |
| 27 | No supported service |
| 28 | Mistyped parameter |
| 29 | Unexpected response from peer |
| 30 | Service completion failure |
| 31 | No response from peer |
| 32 | Invalid response received |
| 69 | Rejected by SMSC |
| 248 | Sent |
| 249 | Rejected |
| 250 | Accepted |
| 251 | Undeliverable |
| 252 | Deleted |
| 253 | Expired |
| 254 | Roaming level not supported |
| 255 | Unknown error |