使用AWS Pinpoint印度专用长码发送SMS时Sender显示为NOTICE的问题

Let’s walk through the most likely issues and fixes for your scenario—since you’ve already got the dedicated long code, two-way SMS enabled, and are seeing the wrong sender ID despite specifying the origination number:

Key Troubleshooting Steps #

1. Check TRAI Sender ID Registration Compliance #

India’s telecom regulator (TRAI) has strict rules for SMS sender IDs. Even with a dedicated long code, if you haven’t registered and had your sender ID approved specifically for that long code, AWS Pinpoint will fall back to using "NOTICE" as a default. Head to your Pinpoint console:

• Navigate to the SMS & voice channel settings
• Locate your dedicated long code and verify if a verified sender ID is linked to it
• Confirm the sender ID registration status shows "Approved" (this can take a few business days after submission)

2. Verify Request Parameter Behavior #

While you tried adding SenderId to your request, note these critical points:

• For Indian dedicated long codes, the OriginationNumber should take precedence over SenderId if configured correctly
• If your sender ID isn’t approved or linked to the long code, Pinpoint will ignore the SenderId parameter entirely. Try removing the SenderId field from your request and test again—if it still shows "NOTICE", the issue isn’t with the request payload.

3. Validate Two-Way SMS Configuration Details #

Double-check your two-way SMS setup for the long code:

• Confirm the long code is marked as "Enabled" in Pinpoint
• Ensure the two-way SMS endpoint (SNS topic/Lambda function) is correctly configured—misconfigurations here can sometimes trigger unexpected sender ID behavior
• Make sure there are no overlapping SMS rules or campaigns that might be overriding your direct API request settings

4. Test with a Minimal Request #

Simplify your API request to eliminate potential parameter conflicts:

{
  "ApplicationId": "6b07b70b18714cf6ba60fb5446123456",
  "MessageRequest": {
    "Addresses": {
      "+914321321321": {
        "ChannelType": "SMS"
      }
    },
    "MessageConfiguration": {
      "SMSMessage": {
        "Body": "Test reply from your dedicated long code",
        "MessageType": "TRANSACTIONAL",
        "OriginationNumber": "+911234123123"
      }
    }
  }
}

If the sender ID is still "NOTICE" after this, the problem is definitely in your account/long code configuration, not the request.

5. Reach Out to AWS Support #

If all the above checks pass and you’re still seeing the issue, it’s likely a backend sync problem between Pinpoint and TRAI’s systems, or a service-side configuration glitch. Submit a support ticket with:

• Your dedicated long code (+911234123123)
• Application ID (6b07b70b18714cf6ba60fb5446123456)
• Screenshots of your long code’s configuration in Pinpoint
• Details of your test requests and their outcomes

As per AWS’s documentation, this use case is supported, so it’s almost certainly a missing configuration step rather than a feature bug.

内容的提问来源于stack exchange，提问作者Rohit Manokaran