SNS : Publish Text Message is success, but no message received at the mobile

Question

I have recently moved out of sandbox, now when i m trying to test the SNS SMS capabilities, I clicked on "Publish Text Message" button and entered required information.

I can see below response in the cloud watch for the corresponding event, but actual message is not received at my phone number. I have edited the response to remove my phone number for the destination and phonCarrier fields.

{
    "notification": {
        "messageId": "e06c2101-8edf-53de-bbb4-7ee7a0e0461e",
        "timestamp": "2024-12-25 15:59:59.646"
    },
    "delivery": {
        "phoneCarrier": "Reliance Telecom - ",
        "mnc": 1,
        "numberOfMessageParts": 1,
        "destination": "",
        "priceInUSD": 0.069,
        "smsType": "Transactional",
        "mcc": 405,
        "providerResponse": "Message has been accepted by phone",
        "dwellTimeMs": 36,
        "dwellTimeMsUntilDeviceAck": 644
    },
    "status": "SUCCESS"
}

Can some one please help me in fixing this? Thanks in advance.

re:Post Agent · Answer

The situation you're experiencing is not uncommon with SMS delivery through Amazon SNS. Even though the CloudWatch logs indicate a successful delivery with the status "SUCCESS" and the provider response "Message has been accepted by phone," this doesn't always guarantee that the message has been received on the mobile device.

There are several reasons why this might occur:

1. Carrier issues: Even when SNS marks the message as delivered, the final delivery depends on the phone carrier. Carriers may sometimes temporarily block messages if they detect unusual traffic patterns.

2. Sender ID registration: For some countries, including India (which seems to be the case here given the mention of Reliance Telecom), the sender ID needs to be properly registered with the carrier. If the sender ID doesn't match the registered phone number used to send SMS, carriers may intermittently accept messages without actually delivering them.

3. Downstream provider or aggregator issues: There could be problems with the providers that route traffic between SNS and carriers, causing intermittent failures.

4. Delayed delivery: Sometimes, SMS messages may experience delays due to network congestion or other factors. The message might eventually be delivered, but it could be significantly delayed.

To troubleshoot this issue:

1. Check your CloudWatch logs for any specific failure reasons like "PhoneNumberOptedOut" or "ThrottlingLimitExceeded".

2. Ensure that your sender ID is properly set up and registered, especially if you're sending to Indian phone numbers.

3. Monitor your SMS usage to make sure you're not hitting any service quotas that might force your messages into a low priority queue.

4. If the problem persists, it's recommended to contact AWS Support. Provide them with recent message logs (ensure they're not older than 72 hours). AWS Support can work with the providers and carriers to identify and resolve any underlying issues.

5. Verify that the destination phone number is correct and hasn't opted out of receiving SMS messages from your sender ID.

Remember, while SNS provides delivery status information, the final step of message delivery is handled by mobile carriers, which can introduce variables outside of AWS's direct control.  
**Sources**  
[AWS SNS - SMS not receive to mobile at some times | AWS re:Post](https://repost.aws/questions/QUREkykH-7RTOlnVbr8uXHZA/aws-sns-sms-not-receive-to-mobile-at-some-times)  
[SMS not being received by user even after a successful 'Message has been accepted by phone' | AWS re:Post](https://repost.aws/questions/QUdzAz7xdcT5WSEDLlFWfq2w/sms-not-being-received-by-user-even-after-a-successful-message-has-been-accepted-by-phone)  
[Adding and verifying phone numbers in the Amazon SNS SMS sandbox - Amazon Simple Notification Service](https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox-verifying-phone-numbers.html)

SNS : Publish Text Message is success, but no message received at the mobile

Add your answer

Relevant content