Start your digital
journey with us—reach out now.
We are happy that we are taking another step to provide better transparency to our customers. As of today as DLT template scrubbing is LIVE so for better clarity to our SMS customers we will be providing detailed SMS error codes to every outbound SMS text message that fails due to DLT scrubbing. These detailed error codes will help you to understand reasons for failure and troubleshoot issues right away with your outbound SMS deliverability.
These error codes are related to only DLT scrubbing. Our application will be displaying error code instantly once received from telecom operators in real time.
Sr. No. | ERROR CODE | STATUS | DESCRIPTION |
---|---|---|---|
1. | 600 | ENTITY_NOT_FOUND | No record found with EID as primary key |
2. | 601 | ENTITY_NOT_REGISTERED | No entry of entity on the platform. |
3. | 602 | ENTITY_INACTIVE | Entity is inactive on the platform, ex: {VI:I} |
4. | 603 | ENTITY_BLACKLISTED | Entity is blacklisted on all platforms |
5. | 604 | INVALID_ENTITY_ID | Received wrong entity id format or no entity id tag. |
6. | 605 | ENTITY_ID_NOT_ALLOWED_FOR_TM | Principal entity is not allowed for the TM |
7. | 606 – 609 | ENTITY_RESERVED | Reserved for Entity |
8. | 610 | TELEMARKETER_NOT_REGISTERED | No entry of TMID on the platform. |
9. | 611 | TELEMARKETER_INACTIVE | Telemarketer is inactive on the platform, ex: {VI:I} |
10. | 612 | TELEMARKETER_BLACKLISTED | Telemarketer is blacklisted on all platforms |
11. | 613 | TELEMARKETER_NOT_ALLOWED_FOR_ENTITY | Telemarketer is not allowed the Entity |
12. | 614 | PE_TM_HASH_NOT_RECEIVED | PE-TM Hash not Received |
13. | 615 | PE_TM_HASH_NOT_REGISTERED | PE-TM Hash not Registered |
14. | 616 | PE_TM_HASH_INACTIVE | PE-TM Hash Inactive |
15. | 617 | PE_TM_HASH_BLACKLISTED | PE-TM Hash Blacklisted |
16. | 618 | PE_TM_HASH_SUSPENDED | PE-TM Hash Suspended |
17. | 619 | TELEMARKETER_RESERVED | Reserved for Telemarketer |
18. | 620 | HEADER_NOT_FOUND | No record found with header (case sensitive) as primary key |
19. | 621 | HEADER_INACTIVE | Header is inactive on the platform, ex: {VI:I} |
20. | 622 | HEADER_BLACKLISTED | Header is blacklisted on all platforms |
21. | 623 | PEID_NOT_MATCHED_WITH_HEADER | Principle Entity Id is not matched with Header Id |
22. | 624 | HEADER_SUSPENDED_DUE_TO_VALIDITY | Header is Suspended after the validity period |
23. | 625 | HEADER_SUSPENDED_DUE_TO_USAGE | Header is Suspended due to non-usage |
24. | 626 | HEADER_SUSPENDED_DUE_TO_CUSTOMER | Header is Suspended due to PE action |
25. | 627 | HEADER_MISUSED_FOR_INVALID_CONTENT | Invalid/Spam content is failed. |
26. | 628 | HEADER_RESERVED | Reserved for Header |
27. | 629 | HEADER_MISUSED_FOR_INVALID_CONTENT | Spam content detected against Header |
28. | 630 | TEMPLATE_NOT_FOUND | No record found with Template Id as primary key/no template found |
29. | 631 | TEMPLATE_INACTIVE | Template is inactive on the platform, ex: {VI:I} |
30. | 632 | TEMPLATE_BLACKLISTED | Template is blacklisted on all platforms |
31. | 633 | TEMPLATE_NOT_MATCHED | Template not matched for given Template ID |
32. | 634 | HEADER_NOT_REGISTERED_FOR_TEMPLATE | Header is not registered for the template |
33. | 635 | TEMPLATE_VARIABLE_EXCEEDED_MAX_LENGTH | Variable length exceeded the max configured length |
34. | 636 | ERROR_IDENTIFYING_TEMPLATE | Error in identifying the template |
35. | 637 | INVALID_TEMPLATE_ID | Received wrong Template id format or no Template id tag. |
36. | 638 | ENTITY_NOT_REGISTERED_FOR_TEMPLATE | Entity not registered for the submitted Template |
37. | 639 | TEMPLATE_SUSPENDED_DUE_TO_VALIDITY | Template is Suspended after the validity period |
38. | 640 | TEMPLATE_SUSPENDED_DUE_TO_USAGE | Template is Suspended due to non-usage |
39. | 641 | TEMPLATE_SUSPENDED_DUE_TO_CUSTOMER | Template is Suspended due to PE action |
40. | 642 | CTA_NOT_WHITELISTED | Template scrubbing failed due to non-whitelisted CTA |
41. | 643-649 | TEMPLATE_RESERVED | Reserved for Template |
42. | 650 | PREFERENCE_NOT_MATCHED | Blocked in preferences with MSISDN as PK. |
43. | 651 | INVALID_PROMO_TIME | Block promo hours (9PM to 10AM) |
44. | 652 | SE_CATEGORY_BLOCK | SE category blocking on fully DND, if consent not available |
45. | 653-659 | PREFERENCE_RESERVED | Reserved for Preference |
46. | 660 | CONSENT_FAILED | General error code for Consent |
47. | 661-669 | CONSENT_RESERVED | Reserved for Consents |
48. | 670 | SCRUBBING_FAILED | SCRUBBING_FAILED |
49. | 671-699 | SCRUBBING_RESERVED | Reserved for Scrubbing |
50 | 7001 | Entity is inactive | |
51 | 7002 | Entity is blacklist | |
52 | 7003 | Entity not in DB | |
53 | 7004 | Entity ID Blank | |
53 | 7005 | ENTITY_OP_INACTIVE | |
54 | 812 | Missing PETM Hash in Aerospike | Scrubbing will fail with response code 812. Logger mode message: "NOT FOUND". |
55 | 813 | PE ID Mismatch | If the PE ID in the request does not match the PE ID in the PETMHash object in Aerospike, scrubbing will fail with response code 813. Logger mode message: "NOT MATCHED". |
Template Rejection? Avoid delays.
Delivery Failures? Get your messages through.
Billing Discrepancies? Understand your charges.
Compliance Confusion? Stay compliant, effortlessly.
Diagnose. Fix. Deliver. Simple.
DLT (Distributed Ledger Technology) is a blockchain-based registration system mandated by TRAI to prevent SMS fraud. It ensures every SMS campaign is verified before delivery.
DLT errors usually occur due to invalid sender IDs, unapproved templates, missing headers, or unregistered content. Each error has a specific code to identify the issue.
Review the specific DLT error code and ensure your sender ID, template, and message content are approved by the DLT platform. Contact your SMS provider if errors persist.
Common DLT error codes include:
1001 - Header not registered,
1002 - Template mismatch,
2001 - Consent missing,
3001 - Invalid entity ID.
View the full list on our DLT Error Codes page.
Yes, TRAI mandates DLT registration for all businesses using SMS for communication. Both promotional and transactional SMS require approved headers and templates on the DLT portal.
SMS messages with unregistered content or headers will be rejected by telecom operators, and you may receive DLT error codes explaining the cause.
Absolutely! Smart5Solutions provides end-to-end support for DLT registration, header and template approvals, ensuring your bulk SMS campaigns run smoothly without errors.
Check the error code, verify your DLT configurations, and confirm your message matches an approved template. You can also contact Smart5Solutions support for detailed assistance.
Typically, DLT registration and template approval can take anywhere from a few hours to 2 working days depending on operator queues and documentation.
A DLT Template ID is a unique identifier assigned to each approved message template by the DLT platform. This ID must match exactly when sending SMS through any operator.
This error occurs when the message body you are sending does not match the template body approved on DLT. Make sure there's no extra space, character, or dynamic value missing.
The Header ID (Sender ID) is the name/number used to send SMS to recipients. It must be pre-approved under your DLT entity. Unregistered headers will trigger a DLT error.
No, as per TRAI regulations, SMS without valid DLT registration, headers, and template approval will not be delivered by operators in India.
There is no fixed limit. You can register multiple templates under a single approved header, as long as each template serves a valid communication purpose and follows DLT guidelines.
Yes. Transactional templates are used for service-related communication like OTPs, while promotional templates are for marketing purposes. Both must be registered separately with correct categories.
Most SMS platforms provide a delivery report (DLR) that includes the failure reason. If it's a DLT issue, the report will mention the corresponding DLT error code.
Yes, Smart5Solutions supports integration with leading DLT operators such as Videocon, VIL (Vodafone Idea), Jio, and Airtel. We help clients choose and configure the right one.
Promotional SMS are used for marketing, offers, and advertisements, and can only be sent between 9 AM and 9 PM to non-DND users. Transactional SMS are sent 24/7 and contain important info like OTPs, order updates, etc.
This error appears when the SMS content you're trying to send hasn't been approved under your DLT account. You need to submit the template and wait for approval before sending messages.
Yes, DLT allows dynamic content using variables like {#var#}. You must use the exact same structure in your live SMS as approved in the template.
Login to your registered DLT operator portal (like Jio DLT, Airtel DLT, VIL Power), go to the dashboard, and check your approved headers and templates status under the relevant sections.
This error means the sender ID (header) you are using is not mapped with your entity on the DLT platform. You must link the header with your DLT entity before sending messages.
Yes, Smart5Solutions provides complete DLT onboarding support including entity registration, header setup, template submission, and compliance management.
You typically need:
- PAN card and GST certificate of the company
- Letter of Authorization
- Header format approval request
- Proof of business identity (e.g., website or incorporation certificate)
OTPs may fail due to invalid template mapping, expired DLT credentials, or unregistered headers. Ensure your template is marked as Transactional and approved by the DLT platform.
No, DLT platforms do not allow editing of approved templates. You must submit a new template for approval if any changes are required in the message content.
If your DLT entity or template expires or is inactive, your SMS campaigns will fail. It's important to keep your DLT account active and renew as per operator guidelines.