DLT Registration in India (Mandatory for SMS/OTP)

TRAI requires every company to register on a DLT portal of an Indian telecom operator. Common operators:

• Jio (Reliance) → https://trueconnect.jio.com
• Vodafone Idea (Vi) → https://www.vilpower.in
• Airtel → https://dltconnect.airtel.in
• BSNL → https://www.ucc-bsnl.co.in

You can register on any one, and it propagates to all operators.

✅ Step-by-step DLT Process

1. Entity Registration
   • Sign up on a DLT portal with company details, PAN, GST, CIN, and KYC docs.
   • Get an Entity ID after approval.
2. Header Registration (Sender ID)
   • For OTP/Transactional SMS: choose a 6-character alphabetic ID (e.g., WIZBRD).
   • Each operator must approve it.
3. Template Registration
   • Register your OTP and service templates. Example: Your OTP for Wizbrand login is {#var#}. Do not share it with anyone.
   • {#var#} is a variable placeholder.
4. Scrubbing & Approval
   • Once approved, you’ll get a Template ID.
   • SMS providers (including AWS) must use this ID in their requests.
5. Integration
   • Provide Entity ID, Header (Sender ID), and Template IDs to AWS or your aggregator.
   • Without this, SMS in India will be dropped by operators.

Excellent and very practical question 👌 Let me clear it up:

🌍 1. Can SNS Send Worldwide After DLT?

✅ Yes — Amazon SNS can send SMS to any country worldwide once your AWS account is out of SMS sandbox mode and has the proper spend limit approved.

• For India: delivery will only succeed if the SMS matches your DLT Entity + Header (Sender ID) + Template ID.
• For outside India (e.g., Germany, US): DLT is not required — SMS will route normally.

So, one integration → global delivery.
But the Sender ID (the “FROM” field) is what changes depending on the country.

📲 2. What Will the Receiver See in the “FROM” Field?

This depends on region + telecom rules + what you configure:

✅ India (DLT Mandatory)

• The “FROM” = your DLT-registered Header (Sender ID), e.g.,
  • If you register WIZBRD, the recipient sees:
    WIZBRD
• Random numbers or unregistered headers will be blocked by Indian operators.

✅ Other Countries

• US & Canada:
  • The FROM will be a long code (regular phone number) or short code (5–6 digit number) that AWS provides.
  • Sender IDs (like WIZBRD) are not supported by US carriers.
  • Example: SMS might come from +1 206 555 1234.
• Europe (Germany, UK, etc.):
  • Many carriers support alphanumeric Sender IDs (up to 11 characters).
  • If you set WIZBRD in SNS attributes, the recipient in Germany will likely see:
    WIZBRD.
  • If not supported, it falls back to a random long code.
• Middle East (UAE, Saudi, etc.):
  • Strict — often require pre-registration of Sender IDs.
  • Without approval, FROM will show a random number.

🔧 3. How to Control “FROM” in SNS

When publishing SMS via SNS, you can set the AWS.SNS.SMS.SenderID attribute:

aws sns publish \
  --phone-number "+919812345678" \
  --message "Your OTP is 123456" \
  --message-attributes '{
     "AWS.SNS.SMS.SenderID":{"DataType":"String","StringValue":"WIZBRD"},
     "AWS.SNS.SMS.SMSType":{"DataType":"String","StringValue":"Transactional"}
   }'

• For India: SenderID must match your DLT-approved header.
• For Europe: Works fine as alphanumeric ID (if carrier supports).
• For US/Canada: Ignored → replaced with AWS-assigned long/short code.

⚖️ Summary

• Yes, SNS works worldwide after DLT.
• In India: FROM = your DLT Header (Sender ID).
• In Germany/Europe: FROM = your custom Sender ID (if carrier supports).
• In US/Canada: FROM = AWS-assigned long/short code (numbers).

👉 Do you want me to create a mapping table (India, US, EU, Middle East, etc.) showing what the recipient sees in the FROM field when you send via SNS/Pinpoint? That way your team knows exactly how the SMS looks in each market.

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I am working at Cotocus. I blog tech insights at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at I reviewed , and SEO strategies at Wizbrand. 

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at PINTEREST
Rajesh Kumar at QUORA
Rajesh Kumar at WIZBRAND