Insights & Updates

We've shipped native 5G Standalone core support, four new protocol engines (SS7, Diameter, SCTP, Proto-Hub), and a redesigned admin dashboard. This release marks a major milestone in our carrier-grade platform evolution, delivering production-ready interconnect infrastructure in a single deployable stack.

A look at how RFC 8224/8225 call authentication works at the carrier level, and how MOBITELSMS implements full A/B/C attestation across all outbound voice traffic. We examine the JSON Web Token structure, PASSporT claims, and the certificate chain verification process carriers rely on to assess call legitimacy.

Registering brands and campaigns via The Campaign Registry (TCR) is now mandatory for all US A2P SMS traffic. We walk through the brand vetting process, campaign use case categories, message sample requirements, and what to expect from carrier review — so your traffic keeps flowing without interruption.

Misunderstanding UCS-2 encoding costs carriers real money. We explain how character encoding affects SMS segment billing — why UCS-2 uses 67 characters per concatenated segment instead of 153, and how a single byte-vs-character confusion in your billing engine can result in systematically overcharging customers on international messages.

A new HTTP API gateway adapter lets you push messages to any external SMS provider via REST, with live health monitoring and balance tracking. The adapter supports custom authentication headers, configurable retry logic, per-gateway TPS limits, and real-time status reporting via the admin dashboard and real-time health checks.

As carriers accelerate their 5G rollouts, MVNOs face critical decisions about core network infrastructure and interconnect strategy. We explore the difference between 5G NSA and 5G SA deployments, what the migration means for roaming agreements, and how MVNOs can use open-source EPC and 5GC implementations to control their own destiny.