DLT Platform Error Codes and Solutions for SMS
Find common DLT SMS error codes, understand why a message may be rejected, and check practical steps to troubleshoot Entity ID (PEID), Telemarketer ID (TMID), Sender ID (Header), and content Template issues.
How to troubleshoot a DLT SMS error
DLT scrubbing checks message details against registered entities, headers, templates, consent and other applicable settings. An error code can help identify which item needs attention. The meaning of a code may vary by telecom operator, SMS platform, or error response format, so treat this table as a troubleshooting reference and confirm persistent or unclear errors with your SMS provider or the relevant DLT operator.
- Check that your Principal Entity ID (PEID) and Telemarketer ID (TMID) are correct and active.
- Confirm that the Sender ID (Header) is approved and mapped to the correct entity and message template.
- Compare the submitted SMS with the approved template, including static text, punctuation, spaces and variable lengths.
- Check the message category and any required recipient preference or consent records.
- If the details look correct, save the full error response and request your SMS provider to investigate.
Reference note: the codes and descriptions below are based on the existing reference list and are not represented as a complete or universally standardised list. Verify current meanings with your SMS platform or telecom operator. Reserved code ranges may not have a public, fixed meaning.
| Sr. No. | ERROR CODE | STATUS | DESCRIPTION | Recommended Solution |
|---|---|---|---|---|
| 1. | 195 | Expected TLV missing | Template not enabled in application. Contact support | Enable the approved template in your SMS application or contact your SMS provider for assistance. |
| 2. | 600 | ENTITY_NOT_FOUND | No record found with EID as primary key | Verify that the Principal Entity ID (PEID) is correct and registered on the DLT platform. |
| 3. | 601 | ENTITY_NOT_REGISTERED | No entry of entity on the platform | Complete DLT Entity registration before sending messages. |
| 4. | 602 | ENTITY_INACTIVE | Entity is inactive on the platform, ex: {VI:I} | Activate the Entity ID on the respective operator's DLT portal. |
| 5. | 603 | ENTITY_BLACKLISTED | Entity is blacklisted on all Platforms | Contact the DLT operator to resolve the Entity blacklist status. |
| 6. | 604 | INVALID_ENTITY_ID | Received wrong Entity ID format or no entity ID tag | Check the Entity ID format and ensure it is correctly configured. |
| 7. | 605-609 | ENTITY_RESERVED | Reserved for Entity | Reserved code. Contact your SMS provider if this error persists. |
| 8. | 610 | TELEMARKETER_NOT_REGISTERED | No entry of TMID on the Platform | Verify that the Telemarketer ID (TMID) is registered and active. |
| 9. | 611 611 |
TELEMARKETER_INACTIVE / Invalid entity id/Header ID |
Telemarketer is inactive on the platform, ex: {VI:I} / Invalid entity id provided/Invalid Header id for this Entity |
Ensure the TMID, Entity ID and Header ID are valid and active. |
| 10. | 612 612 |
TELEMARKETER_BLACKLISTED / Invalid CLI |
Telemarketer is blacklisted on all Platforms / Invalid CLI |
Verify the CLI and check whether the TMID has been blacklisted. |
| 11. | 613-619 613 |
TELEMARKETER_RESERVED / Invalid Template id |
Reserved for Telemarketer / Invalid Template id |
Verify the Template ID. Reserved codes should be referred to the SMS provider. |
| 12. | 614 | CLI Mismatch with Template | Template does not match with CLI | Use the correct Sender ID (Header) associated with the approved template. |
| 13. | 615 | Template or header Invalid | Template or header Invalid | Verify both the Header ID and Template ID on the DLT portal. |
| 14. | 616 | Invalid category provided | Invalid category provided | Select the correct SMS category (Promotional, Service, Transactional, etc.). |
| 15. | 620 | HEADER_NOT_FOUND | No record found with header (case sensitive) as primary key | Confirm that the Header ID exists and matches the exact case registered on DLT. |
| 16. | 621 | HEADER_INACTIVE | Entity is inactive on the platform, ex: {VI:I} | Activate the Header ID through the DLT portal. |
| 17. | 622 | HEADER_BLACKLISTED | Header is blacklisted on all Platforms | Contact the operator to remove the Header blacklist if applicable. |
| 18. | 623 | PEID_NOT_MATCHED_WITH_HEADER | Principle Entity ID is not matched with Header ID | Ensure the Header is mapped to the correct Principal Entity ID (PEID). |
| 19. | 624-629 | HEADER_RESERVED | Reserved for header | Reserved code. Contact your SMS gateway provider. |
| 20. | 630 | TEMPLATE_NOT_FOUND | No record found with template ID as primary key/no template found | Verify the Template ID and ensure it exists on the DLT platform. |
| 21. | 631 | TEMPLATE_INACTIVE | Template is inactive on the platform, ex: {VI:I} | Activate the template before sending SMS. |
| 22. | 632 | TEMPLATE_BLACKLISTED | Template is blacklisted on all Platforms | Contact the DLT operator regarding the template blacklist. |
| 23. | 633 | TEMPLATE_NOT_MATCHED | Template not matched for given Template ID | Ensure the SMS content exactly matches the approved DLT template, including spaces, punctuation and variables. |
| 24. | 634 | HEADER_NOT_REGISTERED_FOR_TEMPLATE | Header is not registered for the template | Register or map the Header ID with the approved Template on the DLT portal. |
| 25. | 635 | TEMPLATE_VARIABLE_EXCEEDED_MAX_LENGTH | Variable length exceeded the max configured length | Reduce the variable length within the maximum limit defined in the template. |
| 26. | 636 | ERROR_IDENTIFYING_TEMPLATE | Error in Identifying the Template | Verify the Template ID and SMS format before retrying. |
| 27. | 637 | INVALID_TEMPLATE_ID | Received wrong template ID format or no Template ID tag | Check the Template ID format and configure the correct ID. |
| 28. | 638-649 | TEMPLATE_RESERVED | Reserved for Template | Reserved code. Contact your SMS service provider. |
| 29. | 650 | PREFERENCE_NOT_MATCHED | Blocked in preferences with MSISDN as PK | Verify recipient preferences and ensure the number is eligible to receive messages. |
| 30. | 651-659 | PREFERENCE_RESERVED | Reserved for Preference | Reserved code. Contact your SMS gateway provider. |
| 31. | 660 | CONSENT_FAILED | General error code for Consent | Verify that the recipient has provided the required consent. |
| 32. | 661_669 | CONSENT_RESERVED | Reserved for Consent | Reserved code. Contact your SMS provider. |
| 33. | 666 | SMS Content mis-match | SMS Content mis-match | Ensure the SMS content exactly matches the approved template. Do not modify static text, spaces or punctuation. |
| 34. | 670 | SCRUBBING_FAILED | General error code in case of any exceptions | Retry the request. If the issue persists, contact technical support. |
| 35. | 671-699 | SCRUBBING_RESERVED | Reserved for Scrubbing | Reserved code. Contact your SMS gateway provider. |
| 36. | 677 | Invalid TM_ID | Invalid Telemarketer ID | Verify that the Telemarketer ID (TMID) is correct, registered and active. |
| 37. | 678 | Telemarketer ID does not exist / Inactive | Telemarketer ID does not exist/Inactive | Ensure the TMID exists and has not been deactivated. |
| 38. | 680 | Telemarketer ID blacklisted | Telemarketer ID blacklisted | Contact the DLT operator to resolve the Telemarketer blacklist status. |
| 39. | 683 | SMS Type of header is not match Template | SMS Type of header is not match Template | Verify that the Header SMS type matches the approved Template SMS type. |
| 40. | 687 | SMS Type is not match with header / Template SMS Type | SMS Type is not match with header / Template SMS Type | Ensure the SMS type (Promotional, Service, Transactional, etc.) matches both the Header and Template. |
| 41. | 801 | Entity is blacklisted | Entity is blacklisted | Contact the operator to remove the Entity blacklist before retrying. |
| 42. | 802 | EntityID Inactive / Not registered with Airtel | EntityID Inactive / Not registered with Airtel | Register or activate the Entity ID with Airtel DLT. |
| 43. | 803 | Header is blacklisted | Header is blacklisted | Contact the operator to resolve the Header blacklist issue. |
| 44. | 804 | Header Inactive / Not registered with Airtel | Header Inactive / Not registered with Airtel | Register or activate the Header with Airtel DLT. |
| 45. | 823 | Entity not matched | Entity not matched | Ensure the Entity ID used matches the approved Header and Template. |
| 46. | 834 | Header not registered for template | Header not registered for template | Register the Header against the selected Template before sending SMS. |
| 47. | 1026 | Check Template | Template mismatch at application | Verify that the correct Template ID is configured and the SMS content matches the approved template exactly. |
| 48. | 4106/5101/5102/ 5103/5104/5105/ 5106/5107/5108 |
BLOCKED_BY_DLT | Message blocked by DLT Scrubbing | Review your Entity, Header, Template and SMS content to ensure they pass DLT scrubbing. |
| 49. | 4107/4001/ 5000/5001 |
DLT_SCRUBBING_TIMEOUT | Timeout while performing DLT Scrubbing | Retry after a short interval. If the issue continues, contact your SMS gateway provider. |
| 50. | 4108/5201/5202/ 5203/5204/5205 |
SENDER_BLOCKED_BY_DLT | Blocked by DLT because Sender didn't pass Scrubbing | Verify that the Sender ID (Header) is correctly registered and mapped on DLT. |
| 51. | 5301/5302/5303/ 5304/5305/5306/ 5307/5401/5402/ 5403/5404/5405/ 5406/5407 |
TEMPLATE_ERROR | Content Template is not Matching/Register | Ensure the Template ID is correct and the SMS content exactly matches the approved DLT template. |
| 52. | 7001/7002/7003 | ENTITY_ID_ERROR | Entity not Matching | Verify that the Principal Entity ID (PEID) is correct and mapped with the appropriate Header and Template. |
Frequently asked questions about DLT SMS errors
Why is an SMS blocked by DLT?
An SMS may be blocked when the Entity ID, Header, Template ID, message content, message category, or applicable consent and preference checks do not match the required records. Check the returned error code and validate each item before retrying.
What should I check when a template mismatch error appears?
Confirm that the Template ID is correct and compare the message against the approved template. Static text, spacing, punctuation and variable values or lengths can affect matching.
What if the DLT error code is not listed here?
Keep the complete error response, approximate send time and relevant message reference, then contact your SMS service provider. Some codes are operator- or platform-specific and may require provider-side investigation.
For help with SMS delivery and account configuration, visit our Contact page or explore our SMS Sender ID guide.