When utilizing Tatango, it's crucial to be familiar with the status and error codes you may come across in reporting. These codes serve as indicators of the carrier's response to Tatango and can provide valuable insights into potential issues. To make your troubleshooting process more efficient, we have organized a complete list of these codes on this page.
To view the response codes that Tatango receives for a specific message, you'll need to download that sent message's report.
Message Status Codes:
0: Message sent successfully.
1: Processing request.
2: Message received.
3: Message buffered with carrier, awaiting a response.
4: Message delivered to the end user.
3-Digit Carrier-Specific Codes:
815: Message submitted but not acknowledged by the carrier.
1020: Temporary carrier system error, likely to resolve shortly.
1030: Non-retryable carrier system error; avoid message retries.
341: Transaction failed; Carrier ID does not exist.
345: Unable to determine Carrier ID from destination address.
349: Destination address contains non-numeric characters.
350: A destination address is required.
351: Transaction failed: Invalid destination address value.
352: Invalid destination address country code.
353: Message text or data is required.
354: Message text is not long enough.
355: Message text is too long.
358: Message from is too long.
365: Strict international addressing is enforced; use a country code + national number.
366: Invalid message length control option.
367: Invalid source TON value.
368: Invalid source address value.
369: Account not permitted to use an alphanumeric source address.
370: Account not permitted to use a short code source address.
373: Invalid destination TON value.
374: Preview lookup request failed.
375: Source address denied.
376: Account not permitted to use premium billing options.
377: Invalid premium SMS charge type.
378: Invalid premium billing charge amount.
379: Invalid user data header.
380: Invalid data coding scheme.
381: Invalid characters used with the selected data coding scheme.
382: Invalid source or destination port.
383: Message data and text attributes cannot be used at the same time.
384: Invalid message data.
388: Binary messaging is not supported for this carrier.
390: Must provide a numeric country and network code.
394: Invalid option type for the phone specified.
396: Smart messages cannot use more than 3 messages to transfer.
397: WAP Pushes require the optional URL parameter to be included.
398: WAP Pushes not supported for this type of carrier.
399: Binary data with a User Data Header is not allowed for your account.
400: General error occurred while delivering the message to the carrier.
401: General error occurred while delivering the message to the carrier.
410: Message recipient not found on the carrier.
411: Message recipient not found on the carrier.
420: Invalid account ID or account password.
430: Demo or commercial access is required.
431: Invalid Subscriber ID.
432: Account access permanently blocked.
433: Account access denied.
461: Must include source address if premium billing requested.
462: Currency not supported by carrier.
508: Carrier absent subscriber.
509: Carrier delivery failed.
510: Carrier protocol error.
511: Carrier MS not equipped.
512: Carrier unknown SC.
513: Carrier illegal MS.
514: Carrier MS not a subscriber.
525: Carrier system failure.
540: Invalid Request.
560: Message recipient not authorized by carrier to receive the message.
561: Content blocked by carrier.
562: Short code not active.
563: Short code expired.
564: Short code blocked.
565: Reseller address blocked by carrier.
566: Destination address blocked by carrier.
568: Destination address not provisioned for SMS.
569: Destination address suspended by carrier.
570: Invalid charge amount: charge amount not allowed for charge type.
571: List rejected by carrier.
572: List information is not provisioned for this carrier or is not active.
573: Short code blocked by subscriber.
574: Subscribers are not allowed to receive or send messages on this short code.
575: Account not permitted to submit preview requests.
576: List blocked.
577: US SMS Demo Product required for this short code.
578: Demo product expired.
579: Destination address not provisioned for this demo product.
580: Demo product transaction limit exceeded.
581: Prepaid subscriber out of credits.
582: Managed consent not supported on this carrier.
583: Another premium transaction is pending confirmation on the same short code and destination address.
584: PIN expired.
585: PIN verification temporarily blocked for the list and phone number.
586: PIN invalid.
587: Conflicting values for managed consent and charge type.
588: Invalid T-Mobile subscriber. Possible causes: out of credits, suspended, content blocked, or not a T-Mobile subscriber.
589: Premium MT expired waiting for confirmation MO from subscriber.
590: Invalid purpose for India SMS.
591: Monthly MT limit exceeded.
592: Your account is not provisioned for international SMS.
628: Temporary handset failure. Communication to the end user failed, despite the end user's account being provisioned for SMS and the handset SMS-capable. This is typically a temporary failure -- for instance, the handset might be turned off or without coverage.
630: Destination overloaded. The destination mobile operator currently is unable to deliver SMS messages due to high traffic.
E202: Error occurred. SMS Delivery was not successful.
BADCOUNTRY: Area code cannot be reconciled as it does not belong to US or CA, or a CA client is trying to send to a US recipient, or a US client is trying to send to a CA recipient.
UNSENT: We understand this is an error, but we rarely get these so we have no mechanism for handling these; therefore, we will mark them as UNSENT and is_delivered: false but we will not increase bounce count.
Detailed Error Codes:
301: Only one top-level request element is permitted.
303: The required version attribute of the request element was not found in the request.
304: The required protocol attribute of the request element was not found in the request.
306: The XML POST parameter cannot be empty.
307: The request was an ill-formed XML document.
321: Invalid request version.
322: Invalid request protocol.
323: Invalid request type.
337: Invalid carrier ID value.
339: Invalid destination carrier ID value.
340: Invalid source carrier ID value.
341: Transaction failed; Carrier ID does not exist.
345: Unable to determine Carrier ID from destination address.
349: Destination address contains non-numeric characters.
350: A destination address is required.
351: Transaction failed: Invalid destination address value.
352: Invalid destination address country code.
353: Message text or data is required.
Message Status Codes:
0: Message sent successfully.
1: Processing request.
2: Message received.
3: Message buffered with carrier, awaiting a response.
4: Message delivered to the end user.
3-Digit Carrier-Specific Codes:
815: Message submitted but not acknowledged by the carrier.
1020: Temporary carrier system error, likely to resolve shortly.
1030: Non-retryable carrier system error; avoid message retries.
341: Transaction failed; Carrier ID does not exist.
345: Unable to determine Carrier ID from destination address.
351: Transaction failed: Invalid destination address value.
4-Digit Infobip-Specific Codes:
E651: MMS Operator ID not found in our system.
E201: SMS Fallback Message Failed on submission to the supplier.
E101: MMS Message Failed on submission to the supplier.
E102: MMS Message Sent/Failed, potentially rejected by the carrier or device.
Success Response Codes:
N201: SMS Fallback Message Sent successfully to the carrier.
N202: SMS Fallback Message Sent/Delivered to the handset.
N101: MMS Message Sent successfully to the carrier.
N102: MMS Message Sent/Delivered to the handset.
We hope this guide clarifies the meaning and actions associated with each code. For any further assistance or queries, please feel free to reach out to our dedicated support team. Happy messaging!