Product Document. SMS Delivery Guide

Transcription

1 Product Document SMS Delivery Guide Document Version: 2.0 Last Revised: March 21, 2014.

2 SMS Delivery Flow: The delivery of an SMS depends on many factors which could be Handset driven or Network driven. An attempt to deliver SMS may result in following 3 conditions: SMS Success Permanent Fail Temporary Fail Handset Error Network Error I. Success: Message is successfully delivered to mobile handset II. Permanent Fail: Message could not be delivered to the mobile handset for permanent errors such as Call Barred, Unknown Subscriber, UnidentifiedSubscriber etc. The message for these errors can not be delivered to end user s handset even after making multiple attempts hence the message is purged after the first delivery attempt. III. Temporary Fail: In this case the SMSC fails to deliver the message in its first attempt for the following error:: a) Handset Errors: SMSC flags Temp Fails in to Handset errors, when there is one of the following errors is reported by network: SIM Memory Full Not Reachable/Switched Off b) Network Errors: There are many switching and radio level errors reported by GSM networks. All of them categorized in to one SystemFailure for ease in handling. 2

3 MSC Timeout: When SMSC makes a delivery attempt for a message, it normally received either a success or error acknowledgment for that message. However, for some reason if there is no response from the network for 30 seconds, that particular message is marked as Time0ut. A timed out message has 50% probability of delivery, and in normal scenario, is not retried at all. Retry Interval and logic Network Failures and Timeout: All message that do not get delivered due to reason such as Network error or Timeout on first attempted through primary SMSC are immediately routed to our secondary SMSC. Even if the second attempt gets failed for Network error or Timeout then we route SMS via third SMSC, if it fails on the third attempt we send a status report of the messages received from the operator. Handset Error: If message is not delivered due handset based error, SMSC flags Home Location Register (HLR) of the destined mobile number indicating that there is a Message Waiting for that number. At any point of time when handset comes out of reported error, HLR sends an alert (SC Alert) back to SMSC triggering the delivery attempt of all the pending messages for that number. Message for handset errors are purged and marked as expired if no SC alert is received for 6 hours (from the time of first attempt) Operators Your message will be routed via one of the below operators, based on the best availability for the respective series or performance at the point of broadcast. Airtel, Maharastra Loop, Maharastra Aricel, Maharastra BSNL, PAN India 3

4 Status Codes: CODE REASON DESCRIPTION I ) FINAL STATUS -01 New Error Code 000 Sub-SMSC 001 DELIVRD Successfully delivered. This status displays when the error code provided by the subscribers terminating operator is not mapped with the existing status. The message is on SMSC queue i.e. the message has been inserted into the SMSC database but the status of the message is yet to be received. 002 FAILED The message is permanently failed due to CallBarred, Error in Destination Number, Error in TeleService Provider etc. 004 NDNC_Failed Failed Due to DND Registration 044 Promo_Blocked 005 Blacklist 006 Whitelist 007 Invalid Series 008 Prepaid Reject 009 Night_Expiry 099 Night_Purge 031 EXP-AbsSubs This error is displayed when IUC charges are not active for your account. Black-listed number. This list of numbers is provided by the customer and includes numbers of CEO etc. A message will never go to a number in the black-list. This error is received when a Opt-In account sends messages to a non white listed number This error is shown when a number series in the correct number format is invalide. This error is shown when the messages are rejected due to insufficient credits. These messages have not been processed because of legal restrictions of sending messages late hours. These are promotional messages submitted between 9PM and 12AM which are not processed on request. The message is rejected because there was no paging response, the IMSI record is marked detached, or the MS is subject to roaming restrictions. 032 EXP-MEM-EXCD Message rejected because the MS doesn't have enough memory. 033 EXP-NW-FAIL Message rejected due to network failure. 034 EXP-NW-TMOUT Message rejected due to network or protocol failure. 035 EXP-SMS-TMOUT Message rejected due to network or protocol failure. 4

5 036 EXP-HDST-BUSY 037 EXP-MSG-Q-EXD II ) INTERMEDIATE DELIVERY REPORT 110 PENDG-ABS-SUB 120 PENDG-MEM- EXCD The message is rejected because of congestion encountered at the visited MSC. Message queue exceeded when there are too many messages for one number. SMSC can deliver only a particular number of messages to a mobile number. If there are more messages, they get this error code till the queue clears. The message is rejected because there was no paging response, the IMSI record is marked detached, or the MS is subject to roaming restrictions at the first attempt. Message rejected because the MS doesn't have enough memory when at the first attempt PENDG-NW- FAILR PENDG-NW- TMOUT PENDG-SMS- TMOUT PENDG-HDST- BUSY REMOTE NODE NOT REACHABLE Message rejected due to network failure at the first attempt. Message rejected due to network or protocol failure at the first attempt. Message rejected due to network or protocol failure at the first attempt. The message is rejected because of congestion encountered at the visited MSC at first attempt. Remote HLR or VLR route is not defined on adjacent node 210/190 User Abort TCAP Protocol abort received from one of the node on the network 5