SMS 365, Operator Service SMS Messaging Error Codes

SMS 365, operator serviceSMS Messaging Error CodesVersion 2 – Jan 2021

SMS 365, operator service SMS Messaging Error CodesRevision dated and rebrandedTable of Contents1 Introduction .22 SMS Error Codes .32.1 SPAM Control Error Codes.82.2 SS7 Originated Error Codes .91Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error Codes1 IntroductionWhile SMS messages are, for the most part, delivered to their destination subscriberover 99% of the time, there are times when the message is interrupted during itstransit. This can be caused by a variety of reasons – from issues in the radio linkbetween the handset or originating device and the operator, between the originatingoperator and an inter-carrier messaging hub, with the content or format of themessage, between the inter-carrier messaging hub and the destination operator, andso forth.This is a complex ecosystem, so errors do occur. The purpose of this document is tooutline frequent and not so frequent errors that are commonly seen for SMS andfrom the point of view of the Digital Interconnect’s Inter-Carrier Messaging Hubs.Error messages are visualized in the various reporting and analytics products thatDigital Interconnect provides to its customers. Messages that are rejected by DigitalInterconnect will also have various error codes as part of the rejection response.2Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error Codes2 SMS Error CodesDigital Interconnect’s SMS interoperability solution, SMS 365 provides a widevariety of error codes to cover almost any conceivable situation. In many cases,error codes are passed from the destination SMSC or SMS gateway back to theoriginator, as many of these occur on the far-end destination.Some error codes are transient or temporary. SMS 365 identifies these as such andwill usually attempt to retry delivery of the message.Using the SMS 365 reporting tools, such as Report Manager, error codes for acustomer or even individual routes can be summarized.In this sample, a list of common error codes that may appear for any carrier areshown. This is a live example of the number of errors that occurred whendelivering several million messages over a period of time.At first glance, several of these look to be quite self-explanatory. Messages such asMessage Queue Full, Invalid Source Address (for SMPP), Content Invalid orBlank Message, while not common, are rather self- explanatory.Each message received by SMS 365 is queried in our NRS database, which is fedby a variety of authoritative sources from around the world.3Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error CodesAs you can see the errors are categorized. Delivery Errors are common, so let’sreview what they mean in more detail: 1100 NPA/NXX not found -- Typically occurs when a subscriber tries to send amessage to the USA or Canada. NPA Area Code and NXX Exchange. So inthe North American Numbering plan, we have 1 NPA NXX YYYY. NPA NXX sequences are very specific. If a subscribermistypes the destination number -- especially the NPA NXX, the message willfail. Additionally, this may occur if our hub thinks an invalid country code is partof a 1 NPA. 1106 No Route to Carrier -- This would occur when we can resolve thenumber to a particular operator, but we have no way of reaching that operator.For example, we looked up a route to 503 77 123456. 503 is El Salvador andmobile carrier was identified in our NRS database as Millicom/Tigo. In this case,we can reach Millicom/Tigo El Salvador, but NOT for traffic from the originatingcarrier country -- only the specific carriers or countries could reach thisdestination. These types of exceptions are always noted in our Global OperatorList. 1101 Destination address invalid -- This means that the destination phonenumber was incomplete or probably had a bad or unrecognized country code.Again, this is typically the result of a subscriber mistyping the destination address.As you can see from the table, these are generally rare. 1103 Content Invalid –SMS 365 typically limits P2P SMS traffic to non-binarymessages -- meaning we filter out and reject these messages. This is usuallybuilt into our contracts with a variety of mobile operators for us to provide this.It may be noted as the types of character encoding that a particular operator willaccept.In the table above, if you look at Protocol column and note the "SMPP" entries.These generally occur at the far end SMSC, when we try to deliver the message.This is the standard SMPP response codes that we passed back to the originatingoperator.Here's another selection of errors:As you can see the biggest was an Invalid esm class field data. The error wasgenerated by the destination carrier’s SMSC. The esm class is an SMPP parameterthat is used to indicate special messaging attributes.4Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error CodesNormally, this is set to "default SMSC mode [Store & Forward], normal message. Butthere are ways that handsets or originating entities could specify other messagingoptions - such as reply path and such. In this case, the far-end SMSC will rejectsome of these constructs -- usually as a matter of policy.Message Queue Full and System Error are also noted, but in much smallernumbers -- System Error usually relating to some problem with the destinationSMSC in general. Generally, the System Error message either follows or precedessome “outage” event; otherwise, it would be transient in nature.5Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error CodesThe next image contains a more comprehensive list of errors that may occur:6Error CodeMessageCategory00000001SMPPCAT Delivery Error - Message Length is invalid00000008SMPPCAT Other Error - System Error0000000ASMPPCAT Delivery Error - Invalid Source Address0000000BSMPPCAT Delivery Error - Invalid Destination Address00000014SMPPCAT Delivery Error - Message Queue Full Invalid00000015SMPPCAT Delivery Error – Service type00000043SMPPCAT Delivery Error - Invalid esm class field data00000045SMPPCAT Delivery Error - submit sm or submit multi failed00000058SMPPCAT Other Error - Throttling error (ESME has exceeded allowedmessage limits)00000064SMPPCAT Other Error - ESME Receiver Temporary App Error Code00000065SMPPCAT Other Error - - ESME Receiver Permanent App Error Code000000FESMPPCAT Other Error - Delivery Failure (used for data sm resp)000000FFSMPPCAT Delivery Error - Unknown Error00000447SMPPCAT Other Error - Reserved for SMSC vendor specific errors002InternalCAT Other Error - Delivery Failed02UCPCAT Other Error - Syntax Error Operation04UCPCAT Other Error - not allowed Call05UCPCAT Other Error - barring active1002InternalCAT Other Error- Unknown error1060UnknownCAT Other Error - Unknown1100InternalCAT Other Error - NPA/NXX not foundError Message & DescriptionCopyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error Codes1101InternalCAT Other Error - Destination address invalid1103InternalCAT Other Error - Content invalid1105InternalCAT Other Error - Validity period expired1106InternalCAT Other Error - No route to carrier1108InternalCAT Other Error - Loop1130InternalCAT Delivery Error - Blank Message1300InternalCAT Other Error - NACK1711InternalNetwork Errors – No ACCK Received1713InternalCAT Other Error - Socket Timeout24UCPCAT Other Error - Message too long302WCTPProtocol Violation Error Codes - XML validation error9UCPUCP - GA not validAs you can see, messages are categorized by SMPP, Internal (within SMS 365messaging hubs) as well as other specific protocols such as UCP and WCTP. Ingeneral, these would come from the far end destination and be returned back to SMS365.7Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error Codes2.1 SPAM Control Error CodesSMS 365 provides a number of capabilities to scrutinize SMS messages for spamand/or unacceptable traffic as they traverse the hubbing environment. The errorcodes are designed to provide some views as to why a particular message wasblocked.Error CodeDescription for Reporting1120Blocked SPAM – Originating Address (OA) Statistical1121Blocked SPAM – Keyword1122Blocked SPAM – Content or Keyword1123Blocked SPAM – Alphanumeric Originating Address (OA)1124Blocked SPAM – Repeated Content1125Blocked SPAM – Cloudmark Mobile PlatformMessages cited by the Cloudmark Mobile Platform can further be researched byDigital Interconnect personnel to further determine why particular messages mayhave been blocked (within 30 days of the blocked message).This will be the most common error in terms of spam blocking.8Copyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error Codes2.2 SS7 Originated Error CodesIn an effort to provide additional transparency and visibility, in 2013, we added anumber of new error codes that will further diagnose conditions at the far end. In thepast, we used a catch-all error code (1300) that covered a variety of GSM SS7specific conditions. The new codes will detail the individual conditions that causedthe 1300 code and provide further details into an SMS’s final disposition.Additionally, where possible, some conditions were moved from Error Code 1002(Unknown Error) to one or more of the new codes to provide further visibility.The following table outlines the new error codes that are deployed within SMS 365.The Retry column indicates if the original occurrence of that error would havetriggered a retry process. If, after the retries have been exhausted and the conditionpersists, then the final disposition will the code indicated.Error CodeDescriptionRetry3300Unknown User ErrorYes3301Destination Handset Number does not exist in the Numbering Plan.No3302Reception status of SMS is unknown and no acknowledgement ofNodelivery.3303External Operator specific error code.No3305The Origin Number does not exist in the Numbering Plan OR On aNoFWD SM MT, the subscriber (identified by the IMSI) is not in thevisited MSC.3306Absent SubscriberYes3308The delivering node has not received a response. The HLR may notNobe reachable or the subscriber may be roaming in a country wherethe delivering node does not have a roaming agreement.33099Invalid subscriber.NoCopyright 2021 Sinch. All rights reserved. NDA Confidential.

SMS 365, operator service SMS Messaging Error CodesError CodeDescriptionRetry3311No SMS Service for this reachable Operator or this HandsetNo3312Invalid TerminalNo3313Invalid Terminal.No3314No routing exists to destination.No3315Destination is not reachable and SMS service is not available.No3316No roaming route.No3317The destination handset is roaming on a network that Sybase 365Nohas no reach.3318The requesting ISP is not registered for the localization featureNoservice.3319The requesting ISP is not registered for the localization featureNoservice.103320Origin address is not recognizedNo3321No response.No3322External Operator specific error code.No3327The subscriber has turned off his handset.Yes3328The destination is unreachable or barred.No3331The GSM subscriber is busy for MT-SMS.Yes3332SIM card is full.Yes3333Voicemail is full.No3335MSC CongestionYes3336Unacceptable data value.NoCopyright 2021 Sinch. All rights reserved. NDA Confidential.