The Telecom Regulatory Authority of India (TRAI) mandated the implementation of the Distributed Ledger Technology (DLT) platform for all telecom operators in India. This platform aims to curb unsolicited commercial communications (UCC) and ensure transparency in transactional messages.
While the Airtel DLT platform is designed to streamline communication processes, users may encounter error codes during registration, template submissions, or message sending. Understanding these error codes is crucial for troubleshooting and ensuring smooth communication.
When using the Airtel DLT platform, it is important to be aware of the various error codes that may be encountered during the registration or submission process. These error codes are designed to help users identify and resolve any issues that may arise while using the platform. Understanding these error codes is crucial in order to ensure a smooth and efficient registration process. By familiarizing yourself with the DLT error codes on the Airtel platform, you can quickly address any issues that may arise and avoid delays in the registration process. Stay informed and proactive to make the most of your experience with the Airtel DLT platform.
| 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. | 812 | Missing PETM Hash in Aerospike | |
| 51. | 813 | PE ID Mismatch | |
| 52 | 9014 | ESME_RINVPASWD | Invalid TM Password |
| 53 | 9015 | ESME_RINVSYSID | Invalid TM Username |
| 54 | 9008 | ESME_RSYSERR | Connection timeout from DLT |
| 55 | 9016 | JMS_QUEUE_ERROR_CODE | Error from JMS queue |
| 56 | 9028 | ESME_RELAY_NB_JMS_ERROR | Relay NB JMS error |
| 57 | 9029 | ESME_DLR_RETRY_JMS_ERROR | DLR retry JMS error |
| 58 | 9031 | RETRY_REACHED_MAX_LIMIT | Retry profile max limit reached |
| 58 | 9027 | ESME_MULTI_MISSING_PART | ESME_MULTI_MISSING_PART is missing |
| 59 | 9032 | MP_VECTORIZATION_ERROR | Multipart Vectorisation Error |
| 60 | 9033 | MP_NORMALIZATION_ERROR | Multipart Normalisation Error |
| 60 | 9034 | GENERATE_SCRUB_ZERO_ERROR | Component Scrub Zero Error |
| 61 | 9009 | ESME_RSYSERR_ABMS | Connection timeout from ABMS |
| 62 | 88 | ESME_RTHROTTLED | SKV_THROTTLE_ERROR |
| 63 | 9003 | SME_RINVCMDID | Invalid command ID - like Query_sm or data_sm |
| 64 | 9010 | ESME_RINVSRCADR | Invalid CLI (If CLI is blank) |
| 65 | 9011 | ESME_RINVDSTADR | |
| 66 | 9018 | GOV_HEADER_ERROR_CODE | |
| 67 | 9019 | GOV HEADER INVALID ACCOUNT TYPE ERROR CODE |
Tags:
DLT Error Codes airtel DLT Platform, Bulk SMS, airtel DLT Error Codes, Bulk sms service, operator error codes, sms api, sms error codes, bulk SMS API, DLT Platfrom Error Codes India, DLT Platfrom Error Codes, BSNL DLT error codes, DLT information, DLT Platfrom Error Codes India, DLT ERROR CODES FOR BULK SMS, DLT Template Registration Complete Guide, DLT Template Registration, DLT Template Registration guide, DLT Registration, Bulk Sms DLT Registration, dlt content template registration, add Content Template in Jio DLT, Content Template Guideline on DLT, DLT Bulk Sms, DLT Registration Process & Guidelines, DLT Registration Process, DLT Registration price, DLT verified entity approved by TRAI, DLT platform, DLT, dlt registration trai, Dlt registration trai fees, Dlt registration process, Dlt registration online, Dlt registration india, DLT Registration Mandatory, smsgatewayhub