SNS Send SMS to Sandbox Phone Numbers (NO ORIGINATION ENTITIES AVAILABLE)

0

Hello,

I am trying to send a SMS to a sandbox phone number that needs to be defined first. When I try to register this new number the system complains that "No origination entities are available to send". I see the option to define that in "Pinpoint" but it wants me to register an organization and because I do not have an organization when I enter dummy data the verification process fails. How to get past this? what's the best way to make this work?

Thanks!

2 Answers
0

To send SMS in AWS Pinpoint's sandbox:

  1. Verify Phone Number in SNS Sandbox:
  2. Use SNS for SMS Sending:

Here's a sample AWS CLI command to send an SMS using SNS:

aws sns publish --phone-number "+1234567890" --message "Your message here"

Replace +1234567890 with the verified phone number.

profile picture
EXPERT
answered 4 months ago
0

Hi Alex,

I am assuming you are trying to test sending SMS to a US destination number and you tried a register a Toll Free number.

Please note that starting September 30, 2022, the United States mobile carriers require toll-free numbers to be registered. The goal is to protect consumers from spam, hence, the US carriers are mandating these requirements for all A2P SMS senders. It will also allow for higher messaging volume with better quality of service and more affordability. We’re committed to helping you comply with these changing carrier requirements. Hence, in order to help you to seamlessly register the TFN number, AWS has introduced the TFN registration form within the Pinpoint console through which the required information can be provided.
[+] https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-tfn-register.html.

Kindly note that the registrations is being regulated by the US phone carriers and based on the information they require, the registration form within the Pinpoint service has included only those fields which are being expected by the carrier to validate the use-case of the TFN number. Further, the approval needs to come from the carriers end and this is not in AWS's control.

I will recommend to reach out to our dedicated team regarding your use case by following the link below.
[+] https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-tfn.html#tfn-registration-issues

AWS
answered 4 months 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.

Guidelines for Answering Questions