This is to inform you about the recent implementation of TRAI direction regarding Principal Entities (PE) and Telemarketer (TM) Chain Binding for traceability of SMS delivery.
The "812 error code" typically indicates that there is a problem with the message parameters, settings, or the recipient's information when sending bulk SMS through a specific SMS gateway or provider. However, the specific meaning of the error code may vary depending on the service you are using. Here are some general steps you can take to troubleshoot and resolve the issue:
As per TRAI's direction, all Principal Entities (PEs) are required to disclose the complete chain through which their SMS communication is sent. This includes all involved Registered Telemarketers (RTMs). With effect from 11st December 2024, messages will not be allowed if the chain of Telemarketers are not defined.
PE-TM Chain Binding Workflow
Principal Entity (PE) → Telemarketer-Aggregation Function (AF) (If there is any aggregator is the chain) → Telemarketer-Delivery Function (DF) (Here SMSGATEWAYHUB is TM DF) → OAP (Operator)
Action Required – For PE customers
- Log in to your respective DLT portal.
- Click on the "Chain" option available on the dashboard. Every operator will have similar options to define the chain process “Create new request”
- Enter SMSGATEWAYHUB TECHNOLOGIES PVT LTD as the Telemarketer or can enter the TM ID (1302157243747322354) and submit the request.
- SMSGATEWAYHUB as the Telemarketer (TM-DF) will approve the request on DLT.
- After TM-DF approval, the request goes back to the PE for final confirmation. The PE must log in to their PE account and approve the PE-TM chain. Once approved, the chain is finally completed!
DLT PLATFORM ERROR CODES
| 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". |
if any kind of support plese drop mail us at : support@smsgatewayhub.com