Key Takeaways
- Gateway-server localization is finished text you POST. The Android SIM transmits bytes. Recipients see your number.
- Bangla, Arabic, Hindi, and emoji flip GSM-7 (160) to UCS-2 (70). Concatenation is extra operator segments.
- Keep locale in your product. Confirm body/encoding fields in Developer Center — this page is ops, not OpenAPI.
- OTP templates stay ASCII when you can. Marketing copy is where long scripts belong, on a different device.
- You bring the Android and carrier credit. Platform pricing is devices plus SMS send volume.
android sms gateway server how to localize message language is not “set Accept-Language on the modem.” Recipients see your SIM. The string your server POSTs is what leaves the radio. Hub: Server guide. API sibling: localize on the API. Handset copy: localize on the app. Live fields: Developer Center.
You bring phones and operator credit. Devices and send volume. REST samples are HTTPS/JSON — not a Complete SDK.
Your locale · GSM-7 / UCS-2
OTP 4821/কোড ৪৮২১
Same job. Different encoding. Different operator parts.
The server does not pick a language pack
Locale lives in your product. Render Bangla or English before HTTPS. Pair the APK: Downloads, setup. Number formats: multi-country MSISDNs.
A “smart quote” from a CMS is enough to flip UCS-2. Proof the rendered bytes on a staff SIM before a festival blast.
Encoding table
| Script | Typical encoding | Single-part budget | Server check |
|---|---|---|---|
| English OTP | GSM-7 | 160 | No emoji, no curly quotes |
| Bangla / Hindi / Arabic | UCS-2 | 70 | Count parts before send |
| Mixed Latin + Bangla | UCS-2 | 70 | Do not mix in OTP |
| Concatenated promo | Either | Multiplies | Other SIM than OTP |
Parts bill the operator
Each concatenated segment can bill the carrier. Platform volume counts sends too. Retries multiply both. Concatenated SMS. Geo example: Bangladesh, India.
OTP stays short
Brand + code + expiry. No STOP line on login. OTP templates, OTP product. Promo wording: messaging practices.
Hub F vs API vs app
Server how-tos own ops: who renders, who pays parts, which device_id. They do not rewrite the API catalog. How it works. DLR still proves delivery: DLR.
Next steps
Render one GSM-7 OTP and one UCS-2 canary to staff numbers. Spend 300 lifetime SMS proving parts — then a funded SIM. Version the template, not the radio: version integrations.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- download the Android gateway appGet the APK
