1. Overview of Hash Generation
This document outlines the hash generation process at Karix Mobile, ensuring compliance with DLT Chain Hashing. SMS delivery requests are processed through different chains, approved via Telemarketer Aggregator Functions (TM-AF) or Delivery Functions (TM-DF) as needed.
2. Hash Generation for Different Chains
Sample Data for Illustration:
•
PE ID: 1101172974420810001
•
TM AF1 ID: 1101172974420820002
•
TM AF2 ID: 1101172974420820003
•
TM DF1 ID: 1101172974420830004 (Karix DF ID: 110200001000)
•
Chain 1 (PE to TMDF1): SHA256(PEID, TMDF1ID)
•
Chain 2 (PE to TMAF1 to TMDF1): SHA256(PEID, TMAF1ID, TMDF1ID)
•
Chain 3 (PE to TMAF1 to TMAF2 to TMDF1): SHA256(PEID, TMAF1ID, TMAF2ID, TMDF1ID)
Hash Generation Logic:
3. Implementation Approach at Karix Mobile end
3.1 Principal Entities (PE) Sending SMS Traffic Directly to Karix (Chain 1)
•
No Changes for PEs Using Karix DLT AI Feature: Karix will generate the hash SHA256(PEID, TMDF1ID) automatically.
3.2 Aggregators (TM_AF) Using Karix DLT AI Feature (Reverse Lookup)
Aggregators not including DLT Entity ID and Template ID in SMS requests can use the Karix DLT AI feature, where content templates are preloaded on the Karix portal for reverse lookup.
•
Configuration Requirement:
o
Single Chain (Chain 2): Map Entity ID to TM_AF ID in Karix DLT Configuration module in GUI.
o
Multiple Chains (Chain 3): Map Entity ID with TM_AF1 and TM_AF2 IDs as comma-separated values.
3.3 Aggregators (TM_AF) Sending DLT Entity ID and Template ID in SMS Requests
For aggregators sending DLT Entity and Template IDs directly:
•
Karix HTTPs Send SMS API: Include dlt_tm_id in the API payload.
Sample QueryString API:
https://japi.instaalerts.zone/httpapi/QueryStringReceiver?ver=1.0&key=XXXXXXXXXXXXX&dest=919000000001&send=KARIXM&text=This is a test message - KARIX&dlt_entity_id=1001492930000010179&dlt_template_id=1107161951486743588&dlt_tm_id=1101172974420820002
•
Karix SMPP Interface: Add dlt_tm_id in the Submit_SM packet (TLV format):
o
Decimal: 5122
o
Hex: 1402
Multiple Chains (Chain 3): Send IDs as comma-separated values in TLV, e.g., 1101172974420820002,1101172974420820003.
4. Error Codes for Hash Generation Issues
•
PE_TM_HASH_NOT_RECEIVED = 614
•
PE_TM_HASH_NOT_REGISTERED = 615
•
PE_TM_HASH_INACTIVE = 616
•
PE_TM_HASH_BLACKLISTED = 617
•
PE_TM_HASH_SUSPENDED = 618
5. Reporting Updates
•
DLT TM ID Logging: Karix will capture DLT TM IDs in billing and SMS GUI reports.