AWS sms-voice documentation change
Summary
Updated India sender ID registration requirements and added parallel processing tip
Security assessment
Clarifies registration workflow without introducing security features or addressing vulnerabilities
Diff
diff --git a/sms-voice/latest/userguide/registrations-sms-senderid-india-register.md b/sms-voice/latest/userguide/registrations-sms-senderid-india-register.md index 582874602..f90a857c8 100644 --- a//sms-voice/latest/userguide/registrations-sms-senderid-india-register.md +++ b//sms-voice/latest/userguide/registrations-sms-senderid-india-register.md @@ -34 +34 @@ Infobip India Private Limited | 110200001152 -As of 2/6/2025, ACL MOBILE PRIVATE LIMITED telemarketer ID is no longer required and is managed through the Sinch Cloud Communication Services India Private Limited telemarketer. +To complete your India sender ID registration in AWS End User Messaging SMS, only the **Karix Mobile Pvt Ltd** and **Sinch Cloud Communication Services India Private Limited** chain approvals are required. We recommend submitting chain requests for all telemarketers listed above, but you can proceed with your AWS End User Messaging SMS registration while awaiting approval from the remaining telemarketers. @@ -51,0 +52,4 @@ If the TM is not found in the **Chain** tab of the DLT portal, your DLT provider +###### Tip + +DLT platforms typically return template IDs before chain approval is complete. You can use these template IDs to begin your AWS End User Messaging SMS registration in parallel while your chain requests are being processed. +