SYNXWEB NETWORKS
> INITIALIZING CONNECTION SECURE...
> SYNCHRONIZING SMTP RELAY CORE...
> CONNECTING GEOSPATIAL MAPS...
> ESTABLISHING HANDSHAKE PROTOCOL...
00%
BOOT SEQUENCE ACTIVE
POWER

Developer & Logistics Tools

Free browser utilities designed for IT coordinators, developers, and operations managers. Test, configure, and visual systems instantly.

1. SMS Text & Variables

Volume Cost Calculator

Total Budget Required ₹1,600.00
Total Credits Used 10,000

SMS Engine Metrics

GSM-7 (Standard)
Character Count 0
SMS Parts (Credits) 1 Part
Standard GSM-7 text allows up to 160 characters for the 1st part. Multi-part messages use 153 characters per part due to concatenation headers (UDH).
SYNWEB
Transactional SMS
Dear Customer, your order {#var#} has been shipped via {#var#}. Track it at {#var#}. Thanks, SynxWeb.
12:00 PM

PHP DLT-Compliant SMS Integration

PHP cURL

Understanding DLT Regulations & SMS Part Calculus

In India, the Telecom Regulatory Authority of India (TRAI) mandates that all commercial text messages are verified against Distributed Ledger Technology (DLT) blockchain databases prior to transmission. A single character discrepancy between your API payload and your approved DLT template will trigger a delivery failure. Additionally, message length calculations change depending on your character encoding.

GSM-7 vs. Unicode Encoding

GSM-7 is the standard alphabet for SMS, containing English letters, digits, and basic punctuation. Standard English text uses GSM-7. However, if your message includes a single Unicode character (such as Hindi, Arabic, or emojis), the entire message encoding switches to UCS-2 (Unicode).

  • GSM-7 Limits: 160 characters for a single SMS. Multi-part messages allow 153 characters per part.
  • Unicode Limits: 70 characters for a single SMS. Multi-part messages allow 67 characters per part.

DLT Template Binding Guidelines

When sending SMS via the API, you must explicitly pass your approved Entity ID (Principal Entity ID) and Template ID. Dynamic placeholders must be formatted exactly as {#var#} in your templates. When calling the API, you populate those variables with actual values (e.g. order numbers or names) while ensuring the rest of the text matches the approved template layout exactly.

All Channels Operational