Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Outdated Documentation Regarding Telemarketer Chains for SMS Messaging (India)

0

We are encountering issues while setting up PE-TM chain binding for our registered sender ID on the DLT platform (https://www.vilpower.in/) as per the AWS documentation https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-sms-senderid-india-register.html

Out of the five PE-TM chains mentioned in the guide, only Karix Mobile Pvt Ltd has been approved. On contacting Route Ledger Technologies Pvt Ltd they informed us that AWS documentation is outdated and uses a different set of TMs.

Sender ID has been registered with AWS and the necessary resource policies have also been set up on AWS End User Messaging.

Could someone please confirm the latest and accurate list of telemarketer chains required for sending SMS messages through local routes?

Topics
Application IntegrationFront-End Web & MobileBusiness Applications
Tags
Amazon PinpointAWS End User MessagingAmazon Simple Notification Service (SNS)
Language
English
asked a year ago319 views
2 Answers
0

I apologize for the confusion caused by outdated information. You're correct that the documentation regarding telemarketer chains for SMS messaging in India needs to be updated. The situation with telemarketer chains for AWS End User Messaging SMS in India has indeed changed.

Currently, the process for sending SMS messages to India through local routes involves registering your company and use case with the Telecom Regulatory Authority of India (TRAI) through a Distributed Ledger Technology (DLT) portal. After registration, you need to create a case with AWS Support to specify the Entity ID and Template ID values for sending messages to India.

While I don't have the most up-to-date list of telemarketer chains, it's important to note that this information can change. The best course of action would be to create a case with AWS Support directly. They will have the most current information on the required telemarketer chains and can guide you through the process specific to your account and use case.

When creating the support case, be sure to include:

  1. The AWS Region you're using
  2. Your company name (as registered with TRAI)
  3. Your Principal Entity ID (PEID)
  4. Estimated monthly message volume
  5. A description of your use case
  6. How recipients opt in to receive messages
  7. Confirmation that you manage opt-ins and opt-outs

AWS Support will then be able to provide you with the most accurate and current information regarding the telemarketer chains required for your specific situation.
Sources
India sender ID registration process in AWS End User Messaging SMS - AWS End User Messaging SMS
Create a case with AWS Support - AWS End User Messaging SMS

answered a year ago
0

You are correct, out of 5 Infobip India Private Limited ROUTE LEDGER TECHNOLOGIES PRIVATE LIMITED

Is not approved and we contacted but no use they are refusing. After have a continuous email with route ledger technology they given another TM details to add. I will share here TM Name: SEND CLEAN PRIVATE LIMITED

• TM ID: 1202168836913126411

For infobip still i have no idea, if anyone have share here

answered a year 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.

Relevant content