Source-Specific Statuses & Errors

Carrier 10DLC Status & Error Codes

AT&T and T-Mobile provide SMPP status codes for failed 10DLC transactions, available with an HTTP endpoint setup.

When a ten-digit long code number attempts to send a message toward AT&T or T-Mobile but fails, the DLR details will not provide the carrier-level status details needed to determine why a submit was unsuccessful. AT&T and T-Mobile will instead forward their carrier-level SMPP response status codes to Convey, and we will forward these codes to a customer-provided HTTP endpoint for consumption and processing.

Status information will help you self-serve the troubleshooting of failed message submits without having to open a ticket with Convey support. For instance, the following scenarios would reflect a status error code:

• Brand exceeds daily outbound message limit per T-Mobile send cap
• Campaign exceeds allowed throughput rate
• Message rejected by carrier anti-spam filter
• Long code not properly registered to approved campaignID
• Mobile end-user opted out

Setup

Aerialink

These status codes are delivered via an HTTP endpoint for both SMPP and HTTP-connected accounts. You may submit a request for setup through the Aerialink Help Desk Portal. In the summary description field, please include “Request for 10DLC Error Code Endpoint,” and provide your webhook endpoint URL for each applicable account. Aerialink will configure the routing to forward any SMPP status code that isn’t a success to the endpoint in a JSON schema and we will provide you wit ha list of error codes and their description.

Example JSON for an MT toward T-Mobile wherein the Brand has exceeded their daily outbound transactions:

Error code 9802 - “Quota Error Exception”

{
connectionGUID: 'xxx03e74-f3dc-11e3-94de-02f2d79344c4',
  eventGUID: 'xxx791cb-de11-4602-8ef0-7bf698d40dde',
  eventType: 'smppStatusCode',
  eventDateTime: '2022-10-12T14:50:02.411Z',
  eventMessage: {
   transactionGUID:  'xxx791cb-de11-4602-8ef0-7bf698d40dde',
    smppStatusCode: 9802,
    detail: 'Received an SMPP Status Code that was not a success.'
  }
}

Short Code De-Duplication Policy

When a duplicate MT (outbound message) is sent from the same short code to the same destination within 20 seconds of the first MT, it will be blocked and no DLR will be provided. Note that there will be two separate transaction GUIDs with different statuses for otherwise identical message content. Note that only one of the two messages will arrive to the destination handset.