Skip to content

facing challenges getting a US phone number verified for AWS End User Messaging in sandbox

2

I have set up an AWS End User Messaging account, created phone pool and a default configuration set. I ensured that a test message sent using default pool and default configuration set (logging to CloudWatch enabled) works properly. However, I have not been able to receive verification messages for a custom destination phone number(s), and I tried two, both US numbers, both following the mandated format. Verification status for both indicates "Pending" and there is no additional info logged into the associated log in CloudWatch. I've followed all the recommendations I've found online, like ensuring that two-way SMS messaging is enabled on the destination phone, but nothing so far has worked. Any guidance and/or assistance as to what steps to take to resolve this would be greatly appreciated.

asked 2 years ago1.2K views

3 Answers
1

I think I was able to figure this out on my own - origination iD was not created for my sandbox account. Process of registering brand and getting 10DLC registered and available for use under way. I'll provide additional updates as soon as they become available, perhaps others facing the same issue can benefit as well.

answered 2 years ago

EXPERT

reviewed 2 years ago

  • Can you elaborate? I am having the same problem, and I don't see origination ID when I am using simulator number as originator. I thought that you need to request 10DLC when you are moving from sandbox to production environment; and I am long way from that point. UPDATE: When I click on OriginationIDs in SNS -> SMS dashboard, I see simulator number (as I expect) that is active and is associated with phone pool.

  • this is in reply to virshu's post - you need to go through the process of registering brand first, once that concludes successfully you should be able to validate own numbers (as opposed to those available in the simulated pool)

  • OK so here's the final update on this topic. Here are the steps that need to be taken for a US number to be fully validated for testing in the sandbox environment:

    • register brand (takes less than a day)
    • register campaign (takes less than a day)
    • request originating ID, using the registered brand and campaign (this step may take a few days)
    • try to send test message, choose the option to verify a new number This will finally get the verification code delivered to the phone being validated, once you clear the challenge you will then be able to use the originating ID to send test messages to the verified number(s)

    Hope this helps as this was a challenging puzzle to solve and the documentation on this topic is rather scarce

1

I understand you're facing challenges verifying a US phone number for AWS End User Messaging while in the sandbox environment. This is a common issue, and there are a few things to consider:

  1. Sandbox Restrictions: When your account is in the sandbox, you can only send SMS messages to phone numbers that have gone through the verification process. This is a security measure implemented by AWS.

  2. Verification Process: The verification process involves sending an SMS with a verification code to the destination phone number. This code must then be entered into the console to complete the process.

  3. US Number Verification: Some users have reported difficulties specifically with verifying US numbers in the sandbox environment. This could be due to various factors, including regional restrictions or temporary issues with the service.

  4. Origination Identity: Ensure that you have set up an origination identity for SMS messages. This is crucial for sending SMS, especially in regions where Amazon Pinpoint is not supported.

  5. Alternative Testing: While in the sandbox, you might consider using simulator phone numbers for testing. These behave as both origination and verified destination phone numbers without requiring registration.

  6. Support Request: If you've followed all the recommendations and are still unable to verify your US number, it may be worth contacting AWS Support for further assistance. They can provide more specific guidance based on your account and use case.

  7. Production Access: Keep in mind that to move from the sandbox to production, you'll need to submit a support request with details about your use case and the number of messages you plan to send. You'll also need to send at least one voice message before requesting production access.

If the issue persists, double-check all your settings, ensure your phone can receive international calls, and consider trying a different phone number if possible. If none of these steps resolve the issue, reaching out to AWS Support would be the next best step.

Sources
AWS Account Activation - Troubleshooting Phone Verification Issues | AWS re:Post
Add a destination phone number while in the AWS End User Messaging SMS sandbox - AWS End User Messaging SMS
SMS/MMS and Voice sandbox in AWS End User Messaging SMS - AWS End User Messaging SMS
SNS Sandbox SMS delivery to US numbers | AWS re:Post
AWS End User Messaging SMS concepts - AWS End User Messaging SMS

answered 2 years ago

EXPERT

reviewed 2 years ago

0

OK so here's the final update on this topic. Here are the steps that need to be taken for a US number to be fully validated for testing in the sandbox environment:

  • register brand (takes less than a day)
  • register campaign (takes less than a day)
  • request originating ID, using the registered brand and campaign (this step may take a few days)
  • try to send test message, choose the option to verify a new number, and this will finally get the verification code delivered to the phone being validated, once you clear the challenge you will then be able to use the originating ID to send test messages to the verified number(s)

Hope this helps as this was a challenging puzzle to solve and the documentation on this topic is rather scarce

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.