cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SMPP Statuses

 

If your SMPP SMS messages were not delivered as expected, you can use the Message Search tool under the SMS tab on the Sinch Customer Dashboard to view a report of messages you have sent using the SMS API. The entries in this report will include any messages that have been processed (or, in some cases, are in process).

 

Additionally, the Status column in the report will provide you with information on the current state your message is in:

 

Rejected

 

Message was rejected by Sinch. Sinch does not charge for rejected messages.

 

Troubleshooting Steps:

If you receive the Rejected status for any of your SMPP SMS messages, we recommend you take the following Troubleshooting steps:

  1. Verify Number Format: Ensure the recipient's phone number is correctly formatted and valid. Incorrect formats often lead to rejection.
  2. Check Content Compliance: Review the message content for adherence to carrier and destination regulations. Non-compliance can result in rejection.
  3. Examine Sender ID: Confirm that the Sender ID used is approved and not causing the rejection, as some carriers have specific Sender ID policies.

No Delivery Receipt

 

The operator did not provide a delivery receipt for this message.

 

Troubleshooting Steps:

If you receive the No Delivery Receipt status for any of your SMPP SMS messages, we recommend you take the following Troubleshooting steps:

  1. Verify Number Format: Ensure the recipient's phone number is correctly formatted and valid. Incorrect formats often lead to rejection.
  2. Carrier and Network Check: Investigate any known issues with the recipient's mobile carrier or network delays that could prevent delivery.

Pending Delivery Receipt

 

Awaiting delivery receipt for this message from the operator.

 

Troubleshooting Steps:

If you receive the Pending Delivery Receipt status for any of your SMPP SMS messages, we recommend you take the following Troubleshooting steps:

  1. Check Network Conditions: Verify any known network issues that might be delaying message delivery, such as congestion or outages.
  2. Message Queue Status: Investigate if there's a high traffic backlog in Sinch causing delays.
  3. Content and Format Compliance: Ensure message content and format meet carrier and destination regulations to avoid pending status due to filtering or format issues.
  4. Recipient Device Status: Confirm if the recipient's device is on and within service range, as its status can impact delivery.

Failed

Messages which show a status of Failed will have an associated Error Code. Please refer to the SMPP Error Codes section for details of how to understand and troubleshoot common SMPP Error Codes.

 

 

SMPP Error Codes

 

If any of your SMPP SMS message search results have a Failed status, they will include an error code. These error codes are detailed in our developer documentation, and can be divided into Temporary and Permanent errors. Temporary errors indicate a state that may be resolved without changing the corresponding send message request. In these cases, retrying the same send message request may result in success as circumstances change. Permanent errors indicate a state in which the corresponding request must be updated in order to resolve the issue. For example, including a non-existent MSISDN in a send message request would result in a Permanent error; the MSISDN would need to be updated in order to resolve the issue.

 

The most common codes are listed below:

 

Error Code

Treated as

Description

Comment/Action

Troubleshooting Tips

61

Permanent

Destination blocked.

Account not permitted to reach the destination MSISDN

  1. Use the Right Account or Service: Make sure you are using the appropriate account or service for the destination you're trying to reach.
  2. Number Format Check: Ensure the phone number is in the correct E-164 format. It should start with the country code and be followed by the phone number, like “11234567890”, without including the '+' sign. Learn more
    Note: If the person has chosen not to receive messages (opted out), try reaching them in an alternative manner or avoid texting this number again.

62

Permanent

Keyword blocked.

A phrase or word in the body of the message has been caught in the anti-spam filter

  1. Review and Compliance: Carefully examine your message for any high-risk phrases, links, or keywords and make sure it adheres to the specific rules and regulations in your area. Learn more about content review and local compliance
  2. Test Message: After reviewing and adjusting your message, send a test version to ensure it successfully goes through without any issues.

150

Permanent

Unknown
subscriber

The MSISDN is not active with the carrier

  1. Number Format Check: Ensure the phone number is in the correct E-164 format. It should start with the country code and be followed by the phone number, like “11234567890”, without including the '+' sign.
    Learn more for iOS
    Learn more for Android.
  2. Confirm Phone Number Validity: Ensure that the phone number you are trying to message is valid and currently active. Check that it is not blocked or restricted in any way on your account.
  3. Restart the Phone: Message Recipient may need to turn the phone off and then on again to refresh its connection.
  4. Test Another Number: Try sending a message to a different number on the same network to pinpoint the issue.
  5. Wait and Retry: If the issue persists, give it some time and then try sending the message again later.

151

Permanent

Call barred.

Message rejected due to active barring by the end-user.

The person receiving the message needs to call their mobile service provider to fix any blocks on their account. It might be best to stop sending messages to this number for now.

153

Temporary

Absent subscriber.

Subscriber handset not connected to the network. Likely turned off or outside the area of coverage.

  1. Check the Phone Number: Make sure the number is correct and working with the mobile service provider.
  2. Check the Phone: Message recipient may need to confirm the phone is on and has a strong signal.
  3. Restart the Phone:    Message recipient may need to turn the phone off and on again to refresh its connection.
  4. Wait and Retry: If the issue persists, give it some time and then try sending the message again later.

158

Temporary

Memory capacity exceeded.

The handset does not have sufficient free memory to accept the SMS

Message recipient may need to make sure the phone has enough space for new messages. Delete old texts if necessary.

212

Temporary

Device not short message equipped.

The number cannot receive text messages, for example Data-SIMs

Check Number Type:  Message Recipient may need to ensure the number can receive texts. It shouldn't be a data-only SIM card, landline, VoIP, or any special service number that can't get text messages.

255

Permanent

Personal service barring, MT Personal.
Determined Barring Black List.

The end-user has opted out from receiving messages. Either all A2P messages or sender ID specific

  1. Check for Blocks: Ensure no filters or bars are preventing the number from receiving messages.
  2. Contact Support: If you're unsure, reach out to your service provider’s help team.
  3. Test Message: Send a test message to ensure the issue is resolved.

300

Permanent

Invalid destination address

The MSISDN does not exist

  1. Number Format Check: Ensure the phone number is in the correct E-164 format. It should start with the country code and be followed by the phone number, like “11234567890”, without including the '+' sign. Learn more
  2. Confirm Phone Number Validity: Ensure that the phone number you are trying to message is valid and currently active. Check that it is not blocked or restricted in any way on your account.
  3. Follow the Rules: Ensure your message meets all the local laws. Check the rules.
  4. For Developers: If using SMPP, set TON/NPI values to 1/1.

310

 Permanent

Invalid source address

The source address is not permitted. Refer to Country Information and local regulations

  1. Check Sender Name/Number: Make sure the sender ID is set up properly.
  2. Follow the Rules: Ensure your message meets all the local laws. Check the rules.

 

Note: Refer to the Sinch SMS SMPP Developer Documentation for a complete list of all the SMPP error codes.

Featured Article
Version history
Last update:
‎02-27-2024 04:00 AM
Updated by: