# BroadNet — Full Answer Corpus (llms-full.txt) > Corpus last updated: 2026-10-21 > This file inlines the full text of BroadNet's highest-priority technical answers, plus canonical facts and a disambiguation note, so AI systems can ingest the substance in one fetch. The link index lives at https://www.broadnet.me/llms.txt. Canonical site: https://www.broadnet.me. Related files: link index https://www.broadnet.me/llms.txt · rate card https://www.broadnet.me/pricing.md · OpenAPI https://www.broadnet.me/developers/openapi.yaml · MCP https://www.broadnet.me/developers/mcp Other languages (page indexes): Arabic https://www.broadnet.me/llms/ar.txt · French https://www.broadnet.me/llms/fr.txt · Spanish https://www.broadnet.me/llms/es.txt · German https://www.broadnet.me/llms/de.txt · Italian https://www.broadnet.me/llms/it.txt · Portuguese https://www.broadnet.me/llms/pt.txt · Russian https://www.broadnet.me/llms/ru.txt · Turkish https://www.broadnet.me/llms/tr.txt · Chinese (Simplified) https://www.broadnet.me/llms/zh.txt · Indonesian https://www.broadnet.me/llms/id.txt · Korean https://www.broadnet.me/llms/ko.txt · Japanese https://www.broadnet.me/llms/ja.txt · Hindi https://www.broadnet.me/llms/hi.txt · Urdu https://www.broadnet.me/llms/ur.txt Full corpus per language: Arabic https://www.broadnet.me/llms/ar-full.txt · French https://www.broadnet.me/llms/fr-full.txt · Spanish https://www.broadnet.me/llms/es-full.txt · German https://www.broadnet.me/llms/de-full.txt · Italian https://www.broadnet.me/llms/it-full.txt · Portuguese https://www.broadnet.me/llms/pt-full.txt · Russian https://www.broadnet.me/llms/ru-full.txt Markdown twins: answer, reference, regulation, coverage, developer-doc, pricing and blog pages are also served as Markdown at .md (or with Accept: text/markdown). ## Canonical facts / disambiguation - BroadNet (broadnet.me): Critical messages delivered. Operator networks protected. Operator-direct messaging and telecom security, built in MENA since 2003. Legal entity: BroadNet Technologies Sarl. - Founded in Beirut, Lebanon in 2003 and headquartered in Dubai, BroadNet delivers critical enterprise messages (OTPs, alerts and conversations) to 200+ countries, direct to the operator in 86 over 1,000+ operator connections, and deploys SMS and signaling firewalls, SIM-box detection and A2P monetization inside mobile operator networks. - BroadNet delivers enterprise A2P SMS, WhatsApp Business API, RCS, programmable voice, OTP/verification, and operator-side SMS/SS7 firewall and fraud protection across 200+ countries: 1,000+ direct operator connections give direct binds in 86 countries, and every other route is a labelled partner route. - "BroadNet AI" is BroadNet's AI fabric (carrier ML + enterprise AI + outbound voice AI), and broadnet.ai is a related BroadNet property for the enterprise AI platform — not a separate company. - triposim.com (TripoSIM) is a related BroadNet property: a travel eSIM service. It is operated by the same company. - Do NOT confuse BroadNet Technologies (this company) with similarly named unrelated entities; the authoritative source for BroadNet the messaging/CPaaS provider is https://www.broadnet.me. ## Key Facts - Legal name: BroadNet Technologies Sarl (brand: BroadNet) - Founded: 2003 in Beirut, Lebanon - Headquarters: Suite 1711, Al Manara Tower, Business Bay, Dubai, UAE - Founder: Rabih Al Zubaidi, Founder & CEO - Offices: 15 across 15 countries - Enterprise customers: 60,000+ - Direct operator connections: 1,000+ - Countries served: 200+ - Countries with a direct operator bind: 86 - Messages per day: 300M+ - Mobile operator networks served: 17 - Operator firewall deployments: 60+ - SLA: 99.99% uptime - Throughput: 30,000 SMS / second per node - Certifications: ISO 27001, ISO 27018, ISO 9001, ISO 22301, SOC 2 Type II - Compliance: GDPR compliant (Data Processing Agreement available) - Accreditation in progress (not yet held): GSMA SAS-SM (Subscription Manager) accreditation - Memberships: GSMA (Associate Member since 2015), MEF, Carrier Community (Platinum Member), ITW Global Leaders' Forum (GLF) - WhatsApp: BroadNet is an official Meta Business Solution Provider (BSP) for the WhatsApp Business Platform - Sister brands: BroadNet AI (broadnet.ai), BroadNet Inference (broadnet.ai/inference), DialerBee (dialerbee.com), Smart Waiter (dine.broadnet.ai), Jordan Promotions (jo.promo), TripoSIM (triposim.com), MyOTP.App (myotp.app), BroadNet Pulse (pulse.broadnet.me), MobileValidate (mobilevalidate.com); DialerBee works in 12 languages - API: https://api.broadnet.me, POST /sms/sendSms, Bearer token; SDK: @broadnet/cpaas-sdk (TypeScript/Node.js); MCP server: https://mcp.broadnet.me/mcp - UAE SMS: from $0.0123 per SMS (indicative list rate, reviewed 2026-09-24) - Throughput: 30,000 SMS / second per node - Full fact sheet: https://www.broadnet.me/about/facts (JSON: https://www.broadnet.me/about/facts.json) - Notable customers: Google, Meta, WhatsApp, Uber, Western Union, Samsung, DHL, American Express ## Developer surface (canonical) - REST API: Bearer-token auth (`Authorization: Bearer `). Production base URL https://api.broadnet.me. Test credentials, and where to send test traffic, come with test access: request it at /signup and we reply within one business day. One path family per channel: /sms, /whatsapp, /rcs, /telegram, /push, /email, /messenger, /instagram. - Code samples on this site use the production base URL, https://api.broadnet.me. - First-message journey (the same clocks on /signup, /onboarding, /developers/quickstart and /tools/launch-planner): request test access -> reply within 1 business day with test credentials -> first test message about 5 minutes after credentials (test credentials on the production endpoint, to your own verified number) -> integration 2-5 business days -> approval (sender identity, traffic purpose, sender IDs) 3-10 business days, in parallel -> production on cutover day. Overall 5-15 business days from request to production for most markets; longer where a market's sender-ID lead time is longer. - Send one SMS: `POST /sms/sendSms` with JSON {"senderId", "destinationNumber" (digits with country code, no +), "message", "messageType" (TEXT or UNICODE)}; the response body is the message ID. Bulk: `POST /sms/sendbulk` (multipart: destinationNumberFile + bulkRequest). A missing or invalid Bearer token is rejected by the API gateway with HTTP 401 and a two-field JSON body {error, message}; errors raised by the API itself (e.g. 400 validation) return an ExceptionResponse {status, error, message, errorCode, requestUri}. The API takes no idempotency-key header: store the message ID each send returns and check status before resending (see /developers/idempotency). - Legacy HTTP API for SMPP-era integrations: `/websmpp/*` (e.g. `GET /websmpp/websms?user=&pass=&sid=&mno=&type=1&text=`), credentials as parameters. New integrations should use the Bearer REST API. - OpenAPI 3.1 spec: https://www.broadnet.me/developers/openapi.yaml (JSON: /developers/openapi.json) — 329 paths, 376 operations, 8 channels. - SDK: exactly one official SDK — `@broadnet/cpaas-sdk` on npm (TypeScript/Node.js, CommonJS + ESM, one runtime dependency: axios). There are no official BroadNet SDKs for Python, PHP, Java, Go, Ruby or .NET; generate a client from the OpenAPI spec or call the REST API. - MCP server: https://mcp.broadnet.me/mcp — Model Context Protocol over Streamable HTTP, `Authorization: Bearer `; documented at https://www.broadnet.me/developers/mcp. - SMPP 3.4 is also available for high-volume binds (see /developers/smpp). The SMPP host, port and bind credentials are provided with your test access; plain SMPP conventionally uses port 2775, and the TLS port is provided with your account. ## Products (one-liners) - Link Shortener (https://www.broadnet.me/products/link-shortener): Branded short links with click analytics - MyOTP.App (https://www.broadnet.me/products/myotp): Turnkey OTP verification app and API — multi-channel, sub-5-second - BroadNet Inference (https://www.broadnet.me/products/inference): Arabic speech-to-text in every major dialect, document reading and vision chat models as an API - MobileValidate (https://www.broadnet.me/products/mobilevalidate): A BroadNet brand in private preview: phone-number and e-mail checks API (carrier and line type, messaging-app presence, e-mail mailboxes) before you send - Easy Paperless (https://www.broadnet.me/products/easy-paperless): Send invoices, bills, medical results, tickets and letters to customers by message from a network printer, with e-mail on request and free online message history - Phone Reputation API (https://www.broadnet.me/products/phone-reputation): Real-time phone-number reputation verdicts via REST, batch and dialer recipes, for operators, aggregators and contact centres - SMS Surveys (https://www.broadnet.me/products/sms-surveys): Two-way SMS polls, NPS and CSAT captured in real time on direct routes - Email Service (https://www.broadnet.me/products/email): Transactional and marketing email: SMTP relay, REST API and web tool, with reputation management - A2P SMS at carrier scale (https://www.broadnet.me/products/a2p-sms): BroadNet's A2P SMS platform sends application-to-person text messages from enterprise systems to mob… - SMS API (https://www.broadnet.me/products/sms-api): The BroadNet SMS API is a REST endpoint at api.broadnet.me/sms/sendSms with Bearer-token auth, an of… - WhatsApp Business API (https://www.broadnet.me/products/whatsapp-business-api): BroadNet is an official Meta Business Solution Provider (BSP) for WhatsApp Business API. Embedded si… - RCS Business Messaging (https://www.broadnet.me/products/rcs-messaging): RCS Business Messaging (RBM) gives enterprises a verified branded experience in the native Android M… - OTP / 2FA service (https://www.broadnet.me/products/otp): Deliver one-time passwords to your users with auto-failover across SMS, WhatsApp, Voice OTP, and fla… - Voice messaging (https://www.broadnet.me/products/voice): BroadNet's voice platform delivers programmable voice calls, voice OTPs in 30+ languages, and multil… - Bulk SMS (https://www.broadnet.me/products/bulk-sms): Bulk SMS for marketing notifications, event reminders, and one-time announcements. Upload a CSV or c… - Omnichannel messaging (https://www.broadnet.me/products/omnichannel): BroadNet's omnichannel platform lets you send a single message that intelligently routes across SMS,… - HLR Lookup (https://www.broadnet.me/products/hlr-lookup): HLR Lookup queries the Home Location Register of mobile networks to validate phone numbers. Before s… - MMS Messaging (https://www.broadnet.me/products/mms): MMS (Multimedia Messaging Service) delivers images, GIFs, audio clips, and short videos to mobile ha… - 2-Way SMS (https://www.broadnet.me/products/two-way-sms): Turn SMS into a two-way channel. BroadNet provisions long or short codes and forwards inbound messag… ## Operator solutions (one-liners) - Flash Call (https://www.broadnet.me/operators/flash-call): Silent-call OTP verification - Local SMSC Firewall (https://www.broadnet.me/operators/local-smsc-firewall): Inline protection at the local SMSC against on-net spam, SMS storms, local grey routes and sender-ID spoofing - Wholesale Messaging Hub (https://www.broadnet.me/operators/wholesale): Carrier-to-carrier interconnect, A2P termination, aggregation and hubbing with AI-weighted SMS and voice routing - AIT Traffic Control (https://www.broadnet.me/operators/ait-traffic-control): Detect and block artificially inflated traffic, SMS pumping and OTP fraud at the A2P boundary - Robocall Mitigation (https://www.broadnet.me/operators/robocall-mitigation): Robocall, Wangiri and IRSF screening, CLI-spoofing detection and flash-call abuse control on the SIP side - SMS Firewall (https://www.broadnet.me/operators/sms-firewall): BroadNet's SMS firewall blocks grey-route A2P traffic, smishing campaigns, sender-ID spoofing, and S… - SMSC Gateway (https://www.broadnet.me/operators/smsc-gateway): BroadNet operates a carrier-grade SMSC (Short Message Service Center) that mobile network operators … - Signaling Firewall (https://www.broadnet.me/operators/ss7-firewall): BroadNet's signaling firewall inspects SS7 and Diameter traffic in real time, blocking unauthorized … - SIM Box Detection (https://www.broadnet.me/operators/sim-box): SIM boxes are devices loaded with hundreds of consumer SIMs that terminate international calls/SMS a… - A2P Monetization (https://www.broadnet.me/operators/a2p-monetization): Operators rarely capture all of the A2P SMS revenue legitimately due to them. The rest leaks via gre… - Sender ID Registry (https://www.broadnet.me/operators/sender-id-registry): A centralized sender ID registry for operators and regulators. Enterprises submit sender IDs once; t… - Anti-Fraud SMS (https://www.broadnet.me/operators/anti-fraud-sms): BroadNet's anti-fraud SMS layer combines a deterministic rule engine (sender-ID, content, route) wit… - eSIM VSM (Remote SIM Provisioning) (https://www.broadnet.me/operators/esim-vsm): BroadNet eSIM VSM is a GSMA SGP.22 Remote SIM Provisioning (RSP) platform for mobile network operato… - MVNO Messaging & Connectivity Stack (https://www.broadnet.me/operators/mvno): Launch or scale an MVNO on BroadNet — hosted SMSC, A2P monetization and firewall, sender-ID registry… ## Guides & analysis (blog index) - Holiday SMS marketing for Q4 2026: Halloween, 11.11, White Friday and year-end, a sending playbook (https://www.broadnet.me/blog/holiday-sms-marketing-q4-2026): Q4 offers live for hours, not weeks. This playbook lists the 2026 dates from Halloween to New Year's… - Smart Waiter: an AI waiter that answers menu questions and takes orders from a QR code (https://www.broadnet.me/blog/smart-waiter-ai-waiter-qr-ordering-restaurants): Every guest has a question before they order. Smart Waiter, the AI waiter from BroadNet AI, answers … - WWC Madrid 2026 recap: routes, traffic quality and the relationships behind them (https://www.broadnet.me/blog/wwc-madrid-2026-wholesale-messaging-recap): Three days at the Wholesale World Congress in Madrid, Booths #20 and #21, and one consistent theme: … - Seamless Middle East 2026: when the customer replies, the conversation has to work (https://www.broadnet.me/blog/seamless-middle-east-2026-conversational-ai): BroadNet spent 22–24 September 2026 at Seamless Middle East in Dubai, Booth #L70, with one question … - BroadNet at the Middle East 2026 GCCM & SIS Summit in Muscat, 1–4 November (https://www.broadnet.me/blog/gccm-sis-summit-muscat-2026): From 1 to 4 November 2026 BroadNet is in Muscat for the Middle East 2026 GCCM & SIS Summit, organise… - Egypt eKYC and OTP: the CBE Digital Financial Identity rules and what they mean for SMS verification (https://www.broadnet.me/blog/egypt-cbe-ekyc-otp-2026): On 23 August 2026 the Central Bank of Egypt issued rules for its Digital Financial Identity platform… - India CNAP: official caller-name display and what it means for enterprise and AI calls (https://www.broadnet.me/blog/india-cnap-caller-name-business-calls): India's Calling Name Presentation (CNAP) puts the caller's KYC-verified name next to the number on t… - WhatsApp authentication vs SMS OTP: cost per verified user by country (https://www.broadnet.me/blog/whatsapp-vs-sms-otp-cost-by-country-2026): Comparing a WhatsApp authentication rate with an SMS rate tells you little. What matters is the cost… - Iraq A2P SMS guide for 2026: CMC licensing, sender IDs, the Korek shutdown and Arabic and Kurdish encoding (https://www.broadnet.me/blog/iraq-a2p-sms-guide-2026): Bulk and A2P SMS in Iraq is a value-added service licensed by the Communications and Media Commissio… - Email to SMS: how an email-to-SMS gateway works, when to use it and how to secure it (https://www.broadnet.me/blog/email-to-sms-gateway-guide): An email-to-SMS gateway turns an e-mail addressed to a phone number into a text message, so monitori… - SMS campaign metrics that matter: delivery rate, clicks, opt-outs and cost per delivered message (https://www.broadnet.me/blog/sms-campaign-metrics-kpis-guide): Measure an SMS campaign with six numbers: delivery rate from delivery receipts, click-through rate o… - Healthcare SMS: appointment reminders, results notices and what never to put in a text (https://www.broadnet.me/blog/healthcare-sms-appointment-reminders-privacy): Healthcare providers use SMS for appointment reminders, results-ready notices, medication prompts an… - How to write SMS marketing messages that get read and stay compliant (https://www.broadnet.me/blog/how-to-write-sms-marketing-messages): A good marketing SMS names the sender, leads with one clear offer, fits in one segment, gives a sing… - Wholesale A2P SMS explained: hubs, direct routes, per-corridor pricing and CDR settlement (https://www.broadnet.me/blog/wholesale-a2p-sms-explained): Wholesale A2P SMS is carrier-to-carrier termination: an aggregator, operator or large enterprise bin… - SMS OTP autofill: Android SMS Retriever, iOS one-time-code and the WebOTP message format (https://www.broadnet.me/blog/sms-otp-autofill-android-ios-web-guide): SMS codes can fill themselves in on Android, iOS and the web if the message is formatted for it: an … - How to send SMS from code: Python, PHP, Node.js, Java, Go and C# with one REST call (https://www.broadnet.me/blog/send-sms-api-python-php-nodejs-java-csharp): Sending an SMS from code is one authenticated HTTPS POST: a Bearer token, a JSON body with sender ID… - How to become an SMS reseller in 2026: white-label platforms, wholesale rates and what you need (https://www.broadnet.me/blog/how-to-become-sms-reseller-white-label-guide): An SMS reseller buys messaging at wholesale rates, sells it under its own brand through a white-labe… - UK SMS marketing rules in 2026: PECR consent, the soft opt-in, sender IDs and the ICO (https://www.broadnet.me/blog/uk-sms-marketing-rules-pecr-guide-2026): UK marketing texts need prior consent under PECR, or the soft opt-in for existing customers, plus se… - SMS marketing in South Africa in 2026: POPIA section 69 consent, opt-outs and sender IDs (https://www.broadnet.me/blog/south-africa-sms-marketing-popia-guide-2026): In South Africa, direct-marketing SMS falls under section 69 of POPIA: prior consent for non-custome… - Bulk SMS in Kenya in 2026: sender IDs, Safaricom templates, the promotional window and the Data Protection Act (https://www.broadnet.me/blog/kenya-bulk-sms-sender-id-regulations-2026): Business SMS to Kenya needs a sender ID registered with the Communications Authority of Kenya and th… - Sending A2P SMS to Egypt in 2026: NTRA sender IDs, the PDPL marketing licence and a launch checklist (https://www.broadnet.me/blog/egypt-a2p-sms-sender-id-pdpl-guide-2026): To send business SMS to Egypt you need an alphanumeric sender ID approved on all four mobile network… - Before you send the code: a pre-send check routine for OTP with MobileValidate and BroadNet (https://www.broadnet.me/blog/otp-pre-send-check-mobilevalidate-broadnet): A pre-send check is one lookup between the moment a user types a phone number and the moment you sen… - WhatsApp or SMS? How to choose the channel before you send, and fall back when WhatsApp fails (https://www.broadnet.me/blog/whatsapp-or-sms-choose-channel-before-you-send): A WhatsApp message only arrives if the recipient uses WhatsApp, has opted in to hear from you and ca… - Introducing MobileValidate: phone-number and e-mail checks before you send, from BroadNet (https://www.broadnet.me/blog/introducing-mobilevalidate-phone-email-checks-api): MobileValidate is a new BroadNet brand: an API that checks a phone number's carrier and line type, w… - 2027 GCC messaging calendar: Ramadan, Eid, national days and the legal send windows for SMS (https://www.broadnet.me/blog/gcc-messaging-calendar-2027): Ramadan 1448 is expected to start on Monday 8 February 2027, Eid al-Fitr on 9 or 10 March and Eid al… - UAE PDPL for SMS and WhatsApp marketing in 2026: consent, cross-border transfers and what is actually in force (https://www.broadnet.me/blog/uae-pdpl-sms-whatsapp-marketing-2026): The UAE's Personal Data Protection Law has been in force since 2 January 2022, but its executive reg… - Nigeria A2P SMS in 2026: the NCC's international A2P licence, the single gateway, DND and sender IDs (https://www.broadnet.me/blog/nigeria-a2p-sms-ncc-international-gateway-2026): The NCC's licence framework for international A2P messaging routes every international A2P message i… - Indonesia SMS OTP and sender ID (masking) guide 2026: registration, Komdigi's biometric SIM rules and the real cost of a code (https://www.broadnet.me/blog/indonesia-sms-otp-sender-id-masking-guide-2026): Sending OTPs to Indonesia means a registered sender name on each operator, templates built for Bahas… - Pakistan A2P SMS in 2026: PTA sender IDs, the 3627 Do Not Call Register, and the Corporate SMS market review (https://www.broadnet.me/blog/pakistan-a2p-sms-pta-sender-id-guide-2026): Pakistan's A2P rules come from the PTA's anti-spam regulations: approved short codes and sender IDs,… - Turkey SMS rules 2026: international SMS with links are blocked — plus İYS and e-signature explained (https://www.broadnet.me/blog/turkey-sms-rules-2026-url-block-iys): Since 1 April 2026, Turkish operators do not carry or terminate A2P SMS from abroad that contains a … - Hajj and Umrah eSIM guide: staying connected, reachable and able to receive bank OTPs in Saudi Arabia (https://www.broadnet.me/blog/hajj-umrah-esim-connectivity-guide): A practical connectivity guide for Umrah and Hajj travellers: whether your phone supports eSIM, eSIM… - Are AI phone calls legal? AI voice-agent calling rules in the EU, US and UAE for 2026 (https://www.broadnet.me/blog/ai-voice-agent-calling-regulations-2026): Yes, AI voice agents can place calls — with conditions. The EU requires AI disclosure from 2 August … - Is SMS OTP banned? What the UAE, India and Philippine bank rules actually require in 2026 (https://www.broadnet.me/blog/sms-otp-bank-regulation-uae-india-philippines-2026): No — SMS OTP is not banned. UAE banks were told to phase SMS and e-mail OTPs out of customer authent… - Number Verify and SIM Swap APIs in the Middle East: where they are live and how to pair them with SMS OTP (https://www.broadnet.me/blog/number-verify-sim-swap-api-middle-east): Number Verification and SIM Swap are the two operator network APIs that matter most for fraud teams.… - MCP for messaging: how AI agents can send SMS and WhatsApp safely (https://www.broadnet.me/blog/mcp-server-sms-whatsapp-ai-agents): An MCP server turns a messaging API into tools an AI agent can call. That is powerful and risky: an … - WhatsApp usernames and BSUIDs: what changes for OTP, CRM and webhooks (https://www.broadnet.me/blog/whatsapp-usernames-bsuid-developer-guide): WhatsApp usernames mean a business may no longer see a customer's phone number. Meta's answer is the… - WhatsApp service-message pricing from 1 October 2026: what changes, what it costs, and how to cut it (https://www.broadnet.me/blog/whatsapp-service-message-pricing-october-2026): From 1 October 2026 Meta charges for WhatsApp service messages, the free-form replies sent inside th… - Signalling firewalls in 2026: what SS7 and Diameter attacks look like from inside a network (https://www.broadnet.me/blog/ss7-diameter-signaling-firewall-2026): SS7 was designed when every network on it was trusted. That assumption is long gone, but the protoco… - US A2P SMS compliance in 2026: 10DLC registration and the TCPA, explained (https://www.broadnet.me/blog/us-10dlc-tcpa-compliance-a2p-sms-2026): Two separate systems govern US A2P SMS and they are constantly confused. 10DLC is carrier registrati… - SMPP window size: why your bind is slower than the rate you pay for (https://www.broadnet.me/blog/smpp-window-size-throughput-tuning-2026): An operator agrees 100 messages per second, the bind delivers twelve, and everyone blames the networ… - Turnkey AI Agents in 2026: Ready-Made Assistants for Restaurants, Hotels, Clinics and Retail (https://www.broadnet.me/blog/turnkey-ai-agents-hospitality-retail-healthcare-2026): Not every business wants to build an AI platform — most just want an assistant that works on day one… - Enterprise AI in 2026: Why Generic Chatbots Fail and What an Agentic AI Platform Does Differently (https://www.broadnet.me/blog/enterprise-agentic-ai-platform-2026): Generic chatbots don't understand your business. Here's how an agentic AI platform — graph knowledge… - Multichannel OTP Verification in 2026: SMS, WhatsApp, Voice and the Fallback That Saves Conversions (https://www.broadnet.me/blog/multichannel-otp-verification-api-2026): One undelivered code is one lost user. Here's why single-channel SMS OTP fails, how a multichannel v… - Branded Short Links for SMS in 2026: Deliverability, Attribution and Trust (https://www.broadnet.me/blog/branded-short-links-sms-attribution-2026): Public shorteners get filtered, waste characters, and tell you nothing. Here's how branded, per-reci… - The Best eSIM for International Travel in 2026: How Travel eSIMs Work (https://www.broadnet.me/blog/best-esim-international-travel-2026): A complete 2026 guide to travel eSIMs: how they work, device support, eSIM vs roaming, and how to ch… - AI Outbound Dialers in 2026: How BPOs and Collections Teams 4× Their Contact Rate (https://www.broadnet.me/blog/ai-outbound-dialer-bpo-collections-guide-2026): Predictive dialing, language-aware AMD, and bring-your-own-carrier economics: how modern AI outbound… - Meet TripoSIM: Your Journey Starts Connected (https://www.broadnet.me/blog/meet-triposim-your-journey): TripoSIM is the travel eSIM powered by BroadNet — instant activation, no physical SIM swaps, and con… - A2P SMS consent and opt-in compliance: a global guide to GDPR, TCPA, and PDPL. (https://www.broadnet.me/blog/a2p-sms-consent-optin-compliance-guide): A2P SMS is only lawful with real consent. This guide maps opt-in rules across GDPR, the US TCPA, and… - AI agents in customer messaging: the 2026 guide to agentic CPaaS. (https://www.broadnet.me/blog/ai-agents-customer-messaging-agentic-cpaas-2026): Agentic CPaaS moves messaging from scripted chatbots to AI agents that understand context, decide, a… - India DLT registration in 2026: the complete guide, updated for header suffixes and URL whitelisting. (https://www.broadnet.me/blog/india-dlt-registration-guide-2026): India DLT registration explained and updated for 2026: TRAI's TCCCPR 2018 rules, Principal Entity, h… - SIM swap fraud: how account takeover works and why SMS OTP alone isn't enough. (https://www.broadnet.me/blog/sim-swap-fraud-sms-otp-defense): SIM swap fraud hijacks a victim's number so SMS one-time passwords reach the attacker. How account t… - Smishing defense: how SMS phishing works and how enterprises and operators stop it. (https://www.broadnet.me/blog/smishing-defense-sms-phishing-protection): Smishing is SMS phishing: it exploits SMS's high open rate and mobile link blindness to impersonate … - SMS message encoding and segmentation: GSM-7, Unicode (UCS-2) and multipart messages. (https://www.broadnet.me/blog/sms-encoding-segmentation-gsm7-ucs2): An SMS carries 140 bytes: 160 GSM-7 characters, or just 70 in Unicode (UCS-2). How encoding, the UDH… - How AI detects A2P SMS fraud: ML firewalls, traffic-anomaly detection, and grey-route discovery. (https://www.broadnet.me/blog/ai-sms-fraud-detection-ml-firewalls): How AI SMS fraud detection works: machine-learning firewalls that fingerprint traffic, flag anomalie… - International Revenue Share Fraud (IRSF): how premium-rate fraud drains operators. (https://www.broadnet.me/blog/irsf-international-revenue-share-fraud): IRSF pumps traffic to international premium-rate numbers so operators pay inflated settlement fees. … - SIM box (interconnect bypass) fraud: how it works and how operators detect it. (https://www.broadnet.me/blog/sim-box-interconnect-bypass-fraud): SIM box fraud reroutes international calls as local mobile traffic, costing operators termination re… - SMS delivery receipts (DLR) and error codes explained. (https://www.broadnet.me/blog/sms-delivery-receipts-dlr-error-codes): A delivery receipt (DLR) is the operator's final verdict on your SMS. What DELIVRD, UNDELIV, EXPIRED… - Short code vs long code vs alphanumeric sender ID vs toll-free: choosing an SMS sender type. (https://www.broadnet.me/blog/sms-sender-types-short-long-code-alphanumeric): Short code, long code (US 10DLC), alphanumeric sender ID, or toll-free? Compare two-way support, thr… - Voice OTP and fallback: designing multi-channel verification when SMS fails. (https://www.broadnet.me/blog/voice-otp-fallback-verification): Voice OTP delivers a passcode by automated call, reaching landlines and firewalled routes when SMS f… - Wangiri (one-ring) fraud explained: detection and defence for operators. (https://www.broadnet.me/blog/wangiri-one-ring-fraud-detection-defence): Wangiri is the one-ring missed-call scam that baits subscribers into premium-rate call-backs a fraud… - WhatsApp Business Platform policy compliance: template categories, quality rating, and messaging limits. (https://www.broadnet.me/blog/whatsapp-business-platform-policy-compliance): WhatsApp templates get rejected and messaging limits stall for related reasons — how Meta's template… - Agentic RCS: pairing RCS Business Messaging with AI agents. (https://www.broadnet.me/blog/agentic-rcs-ai-agents-business-messaging): Agentic RCS pairs RCS Business Messaging — verified sender, rich cards, suggested actions — with AI … - Branded links and link shortening for SMS: deliverability, click analytics, and anti-phishing. (https://www.broadnet.me/blog/branded-links-sms-shortening-deliverability): Public link shorteners get SMS blocked by operator firewalls. Here's how branded short links protect… - E.164 and phone number validation: formatting, MSISDN normalization, and why it matters for delivery. (https://www.broadnet.me/blog/e164-phone-number-validation-msisdn): E.164 is the format every phone number should be stored in. How MSISDN normalization works, how to v… - How an SMS actually routes: SMSC, ESME, and the A2P delivery path explained. (https://www.broadnet.me/blog/how-sms-routes-smsc-esme-delivery-path): How does an SMSC work? Trace an A2P SMS end to end — ESME bind over SMPP, submit_sm, store-and-forwa… - Number reputation and phone intelligence: cutting fraud and improving deliverability. (https://www.broadnet.me/blog/phone-number-reputation-intelligence): Phone number reputation scores a number from line type, carrier, age, and fraud history, so you bloc… - Saudi PDPL and data residency for messaging: what enterprises sending to KSA must know. (https://www.broadnet.me/blog/saudi-pdpl-data-residency-messaging): Saudi PDPL, enforced by SDAIA, treats a mobile number as personal data. What enterprises sending A2P… - SMS throughput and TPS planning: sizing SMPP binds for high-volume campaigns. (https://www.broadnet.me/blog/sms-throughput-tps-smpp-bind-sizing): SMS TPS is governed by SMPP window size divided by round-trip latency. Here is how to size binds, pl… - Two-way and conversational SMS: designing keyword flows, autoresponders, and STOP handling. (https://www.broadnet.me/blog/two-way-conversational-sms-keywords-autoresponders): Two-way SMS lets customers reply and start conversations. Here's how keyword flows and autoresponder… - How to choose an SMS and CPaaS provider in 2026: a deliverability-first framework. (https://www.broadnet.me/blog/how-to-choose-sms-cpaas-provider-2026): The cheapest per-message rate is usually the most expensive way to send. This is the vendor-neutral … - SMS vs WhatsApp vs RCS in 2026: the business-messaging channel decision guide. (https://www.broadnet.me/blog/sms-vs-whatsapp-vs-rcs-channel-guide-2026): Three channels, three jobs. SMS reaches every phone, WhatsApp owns rich two-way conversation, and RC… - SMS pumping and AIT fraud in 2026: how it works and how to stop it. (https://www.broadnet.me/blog/sms-pumping-ait-fraud-2026): Artificially Inflated Traffic drains OTP budgets and inflates carrier bills. Here is the anatomy of … - A2P SMS: the complete 2026 guide to application-to-person messaging. (https://www.broadnet.me/blog/a2p-sms-complete-guide-2026): A2P SMS is how software reaches people on any phone — OTPs, alerts, notifications, marketing. This i… - RCS Business Messaging in 2026: Apple, E2EE, and why you still need SMS fallback. (https://www.broadnet.me/blog/rcs-business-messaging-2026-apple-e2ee-sms-fallback): iOS support and cross-platform encryption made RCS a real channel. It is still not a universal one. … - The economics of SMS deliverability in 2026: why cost-per-delivered-message is the only number that matters. (https://www.broadnet.me/blog/sms-deliverability-economics-2026): A rate card ranks providers by price per message. Your finance team should rank them by price per de… - Silent Network Authentication vs SMS OTP: the 2026 verification shift. (https://www.broadnet.me/blog/silent-network-authentication-vs-sms-otp-2026): Regulators are phasing SMS OTP out of high-assurance flows and standards bodies now call it phishing… - OTP and user verification: the complete 2026 guide to phone-number authentication. (https://www.broadnet.me/blog/otp-verification-complete-guide-2026): Verifying that a user controls a phone number underpins signup, login and fraud defense. This is the… - UAE TDRA sender-ID registration in 2026: a practical compliance guide. (https://www.broadnet.me/blog/uae-tdra-sender-id-registration-2026-guide): What it takes to get an alphanumeric sender ID approved for the UAE: timelines, the AD- prefix rule,… - Defending against A2P SMS fraud in 2026: pumping, grey routes, and the operator firewall. (https://www.broadnet.me/blog/a2p-sms-fraud-defense-2026): A2P fraud is not one problem — it is several, attacking from both ends of the message. SMS pumping i… - Silent network authentication in 2026: verifying users without sending a code. (https://www.broadnet.me/blog/silent-network-authentication-2026): The most secure OTP is the one you never send. Silent network authentication verifies that a user co… - RCS Business Messaging: the complete 2026 guide to verified, interactive messaging. (https://www.broadnet.me/blog/rcs-business-messaging-complete-guide-2026): RCS turns the phone's default inbox into a branded, interactive channel — verified sender, rich card… - SS7 and Diameter signaling security in 2026: FS.11, FS.19, and the modern signaling firewall. (https://www.broadnet.me/blog/ss7-diameter-signaling-security-2026-fs11-fs19): Interconnect signaling is where location tracking, SMS interception, and roaming fraud live. Here is… - A2P messaging in MENA in 2026: sender-ID rules, regulation, and why direct routes matter. (https://www.broadnet.me/blog/a2p-messaging-mena-2026): MENA is one of the most regulated and fragmented A2P regions in the world — sender-ID registration i… - A2P messaging in 2026: from volume to value. (https://www.broadnet.me/blog/a2p-messaging-2026-volume-to-value): The A2P market is still growing, but the buyer's question has changed from cost-per-message to busin… - WhatsApp Business Platform: the complete 2026 guide to templates, pricing and use cases. (https://www.broadnet.me/blog/whatsapp-business-platform-complete-guide-2026): WhatsApp reaches 2B+ users with rich, two-way, opted-in conversations — but it runs on rules: BSPs, … - From SMS OTP to passkeys in 2026: what WebAuthn replaces, and what SMS still does. (https://www.broadnet.me/blog/sms-otp-to-passkeys-webauthn-2026): Passkeys are displacing passwords and one-time codes for login. But SMS does not disappear — it chan… - MMS vs RCS for rich A2P messaging in 2026: which channel carries your image. (https://www.broadnet.me/blog/mms-vs-rcs-rich-messaging-a2p-2026): Both send pictures and rich content, but they are different technologies with different reach, cost,… - HLR lookup and number intelligence in 2026: cleaner delivery, lower fraud. (https://www.broadnet.me/blog/hlr-lookup-number-intelligence-2026): A live network query tells you if a number is valid, reachable, ported, or roaming before you spend … - STIR/SHAKEN and caller-ID authentication in 2026: how spoofed calls get stopped. (https://www.broadnet.me/blog/stir-shaken-caller-id-authentication-2026): Caller-ID spoofing powers most voice fraud. STIR/SHAKEN cryptographically signs the calling number s… - eSIM travel data as an operator revenue line. (https://www.broadnet.me/blog/esim-travel-data-operator-revenue-line): Travel eSIM apps built a multi-billion-dollar category on top of operator networks while operators w… - 5G roaming security in 2026: the SEPP, PRINS, and life after SS7/Diameter trust. (https://www.broadnet.me/blog/5g-roaming-security-sepp-prins-2026): 5G replaces the implicit trust of SS7 and Diameter interconnect with an authenticated, encrypted roa… - Sender ID registries worldwide — 2026 compliance map. (https://www.broadnet.me/blog/sender-id-registries-worldwide-2026): What began as a GCC and India pattern is now the global default: pre-registered sender IDs, licensed… - Flash call vs SMS OTP — real cost and conversion math. (https://www.broadnet.me/blog/flash-call-vs-sms-otp-cost-conversion): The rate card says flash call wins. The blended math — iOS fallback, silent failures, permission fra… - RCS for operators — revenue beyond P2P messaging. (https://www.broadnet.me/blog/rcs-business-messaging-operator-revenue): P2P RCS rides the data bundle and earns nothing. The operator revenue is in RCS Business Messaging —… - Artificially inflated traffic: detection and defence. (https://www.broadnet.me/blog/artificially-inflated-traffic-ait-detection-defense): AIT turns OTP requests into a billing pump: bots trigger verification SMS to number ranges someone i… - SMS firewall RFP checklist — 20 questions to ask. (https://www.broadnet.me/blog/sms-firewall-rfp-checklist-20-questions): Every firewall vendor demo looks the same. The RFP questions that actually separate a production-gra… - The MVNO messaging stack — build vs partner at launch. (https://www.broadnet.me/blog/mvno-messaging-stack-build-vs-partner): Every MVNO business plan obsesses over data pricing and forgets that messaging is both a launch depe… - A2P SMS monetisation in 2026 — where revenue leaks. (https://www.broadnet.me/blog/a2p-sms-monetisation-2026-revenue-leakage): A2P termination rates keep rising while volumes flatten — which makes every leak in the value chain … - AI chatbots and the hybrid future of customer conversations. (https://www.broadnet.me/blog/ai-chatbots-the-hybrid-future-of-customer-conversations): RCS, WhatsApp, SMS — and the AI orchestration layer that decides which channel a customer ends up on… - GCCM Europe Berlin 2025 — the operator-direct conversation is louder than ever. (https://www.broadnet.me/blog/gccm-europe-berlin-2025-recap): Notes from three days at the Hotel Palace Berlin with Carrier Community's annual carrier + messaging… - ITW 2025 — three days at National Harbor, one consistent message. (https://www.broadnet.me/blog/itw-2025-recap-national-harbor): International Telecoms Week is the world's largest wholesale-carrier annual. Our recap: where A2P mo… - Why OTP messages fail — and how to fix delivery issues. (https://www.broadnet.me/blog/why-otp-messages-fail-delivery-troubleshooting): OTPs fail for a finite list of reasons: sender-ID rejection, grey routes, throttling, content filter… - Direct routes vs grey routes in A2P SMS — what you are actually buying. (https://www.broadnet.me/blog/direct-routes-vs-grey-routes-a2p-sms): A direct route is an SMPP bind to the destination operator's SMSC. A grey route is anything else. Th… - What is an SMS firewall, and why operators need one. (https://www.broadnet.me/blog/what-is-sms-firewall-operator-deployment-guide): An SMS firewall combines deep packet inspection and machine learning to enforce sender-ID rules, blo… - WhatsApp Business templates: the economics conversation enterprises keep getting wrong. (https://www.broadnet.me/blog/whatsapp-business-templates-economics-2026): Authentication, Utility, Marketing — the three template categories Meta defined in 2023 have settled… - How flash-call verification affects operator A2P revenue. (https://www.broadnet.me/blog/flash-call-verification-operator-a2p-revenue-impact): Flash-call verification bypasses SMS-based OTP and reroutes the user-authentication value chain. The… - RCS Business Messaging in MENA — a 2026 rollout map. (https://www.broadnet.me/blog/rcs-business-messaging-mena-rollout-2026): RCS is finally a real channel in the Gulf. Here's where every major operator stands, what's actually… - An enterprise decision matrix for SMS integration, and the case for running both protocols. (https://www.broadnet.me/blog/sms-api-vs-smpp-enterprise-decision-guide): REST API is easy, stateless, webhook-driven. SMPP is throughput-dense, low-latency, binary-efficient… - Sender ID registration in the GCC — a market-by-market guide. (https://www.broadnet.me/blog/sender-id-registration-guide-gcc-markets): Six regulators, six processes. Lead times, documents, fees, and the rejection patterns to plan aroun… - How banks should monitor OTP delivery and fraud. (https://www.broadnet.me/blog/bank-otp-delivery-monitoring-fraud-playbook): The KPIs banks need on the dashboard, the fraud signals worth alerting on, and the operational playb… - The operating cost of an SMS integration: binds, webhooks and failure modes. (https://www.broadnet.me/blog/smpp-vs-http-api-decision-guide): It is not just a throughput question. Connection model, DLR handling, ops cost, and failure modes al… - Omnichannel messaging for ecommerce and logistics — a working strategy. (https://www.broadnet.me/blog/omnichannel-messaging-ecommerce-logistics-strategy): WhatsApp, RCS, SMS, voice. Channel waterfall, consent, opt-out, conversation versus message economic… - How to choose an enterprise messaging provider — a 12-point framework. (https://www.broadnet.me/blog/how-to-choose-enterprise-messaging-provider): Routing model, delivery visibility, fraud protection, operator products, compliance, support, contra… - ITW preview: where AI fraud detection actually moves the needle. (https://www.broadnet.me/blog/itw-ai-fraud-detection-state-of-the-art): Most 'AI firewall' pitches are repackaged rule packs. Here's what real ML in fraud detection looks l… - What is an SS7 firewall and how it protects mobile networks. (https://www.broadnet.me/blog/ss7-firewall-mobile-network-protection-guide): SS7 attack surface, GSMA FS.07 and FS.11 categories, deployment topology, false-positive tuning, and… - SMS firewalls and SS7 fraud — what operators are actually defending against. (https://www.broadnet.me/blog/sms-firewall-ss7-fraud-protection-operators): SIM-box termination, SMS originator spoofing, and SS7-layer attacks all leak A2P revenue and endange… - Bulk SMS in a crisis: the architecture you need before the emergency. (https://www.broadnet.me/blog/bulk-sms-crisis-communications-playbook): When a national emergency happens, the messaging layer is the last thing that should be improvised. … - UAE Cabinet Resolution No. 56 of 2024 — the telemarketing rules, explained for SMS and voice senders. (https://www.broadnet.me/blog/uae-tdra-cabinet-decision-56-explained): What UAE Cabinet Resolution No. 56 of 2024 on the Telemarketing Regulations requires — calling hours… - Saudi Arabia sender-ID rules — what the CST (formerly CITC) requires in 2026. (https://www.broadnet.me/blog/saudi-citc-cst-sender-id-rules): Sending A2P SMS into Saudi Arabia means registering sender IDs with the regulator and routing throug… - The WhatsApp 24-hour window — what every messaging engineer should know. (https://www.broadnet.me/blog/whatsapp-24-hour-window-deep-dive): Meta's customer-service window changes the economics of WhatsApp Business. Here's how to architect a… - OTP delivery done right — latency, fallback, and conversion. (https://www.broadnet.me/blog/otp-delivery-best-practices-conversion): A one-time passcode that arrives late, or not at all, is a failed login and a lost user. Engineering… - How operators recover leaked A2P revenue with the right firewall. (https://www.broadnet.me/blog/operator-firewall-roi): Most mobile network operators capture only part of the A2P revenue they are entitled to. The leakage… - Two billion SMS in a month — what we learned operating BroadNet at this scale. (https://www.broadnet.me/blog/broadnet-2-billion-month): We just routed 2,000,000,000 A2P SMS in February 2026. Behind the milestone: hard-earned lessons abo… - Designing a multi-channel messaging failover strategy. (https://www.broadnet.me/blog/multi-channel-failover-strategy): RCS, WhatsApp, SMS, and voice each fail in different ways. A practical architecture for orchestratin… - RCS vs WhatsApp — which channel for MENA businesses in 2026? (https://www.broadnet.me/blog/rcs-vs-whatsapp-for-mena-businesses): Both are branded business messaging. Both have growing adoption in MENA. Here's a clear-eyed compari… - US A2P 10DLC, explained for international senders. (https://www.broadnet.me/blog/us-a2p-10dlc-explained-for-international-senders): Sending application-to-person SMS to US numbers means brand and campaign registration, trust scores,… - Ramadan messaging in the Gulf — timing, tone, and deliverability. (https://www.broadnet.me/blog/ramadan-campaign-timing-gulf): Ramadan reshapes daily rhythms across the Gulf, and messaging that ignores that underperforms. A pra… - Anatomy of an SMS firewall evasion attempt. (https://www.broadnet.me/blog/anatomy-of-an-sms-firewall-evasion): A walkthrough of how grey-route operators try to bypass firewalls — and how modern ML-based detectio… - BroadNet launches BroadNet AI: agentic enterprise agents that act, not just chat. (https://www.broadnet.me/blog/broadnet-ai-agentic-platform-launch): BroadNet has launched BroadNet AI, an agentic enterprise platform whose autonomous agents execute re… - How HLR Lookup saves 18% on a typical SMS campaign. (https://www.broadnet.me/blog/msisdn-validation-saves-money): Scrubbing your recipient lists with HLR Lookup before sending is the single highest-ROI thing most S… - BroadNet signs MOU with AppTech Payments to embed SMS and omnichannel messaging in digital payments. (https://www.broadnet.me/blog/broadnet-apptech-payments-mou): BroadNet Technologies has signed a Memorandum of Understanding with AppTech Payments Corp. (NASDAQ: … - How to Improve Your SMS Marketing Campaign (https://www.broadnet.me/blog/how-to-improve-your-sms-marketing-campaign): A practical guide to SMS campaigns that convert: SMART goals, a clear call to action, exclusive offe… - Why SMS Verification Is Still the Best Way (https://www.broadnet.me/blog/why-sms-verification-is-still-the-best-way): How SMS verification protects accounts across five core flows: registration, upgrades, reactivation,… - The Importance of an SMS Firewall (https://www.broadnet.me/blog/the-importance-of-an-sms-firewall): How an SMS firewall shields mobile operators and subscribers, filtering MO, MT and SMPP traffic to b… - What an SMS Gateway Is — and How to Choose One That Delivers (https://www.broadnet.me/blog/what-an-sms-gateway-is-and-how-to-choose-one-that-delivers): An SMS gateway bridges your application and the mobile networks. Here's what it does, and how to wei… - Text Message Marketing Best Practices (https://www.broadnet.me/blog/text-message-marketing-best-practices): The core best practices for a compliant, effective SMS program: get opt-in consent, cap message freq… - Bulk SMS API vs a bulk SMS platform (console): which one you actually need (https://www.broadnet.me/blog/bulk-sms-api-vs-platform-console): Two ways to send SMS at scale: an API your app calls on an event, or a console your team runs campai… - Transactional vs Promotional SMS: The Real Difference — and Why It Changes Routing, Sender IDs, and Consent (https://www.broadnet.me/blog/transactional-vs-promotional-sms): Carriers and regulators don't treat SMS as one channel. Intent — not tone — decides routing, sender … - The Best Time to Send Bulk SMS: Send-Time Optimization and Cadence, Driven by Data (https://www.broadnet.me/blog/best-time-to-send-bulk-sms): Send time shapes whether bulk SMS gets read or ignored. A data-driven approach to timing, local quie… - Inbound and two-way SMS: long codes, short codes, virtual numbers, keywords and autoresponders (https://www.broadnet.me/blog/inbound-and-two-way-sms): Inbound and two-way SMS turn broadcast into a conversation: how receiving numbers work, short codes … - Everything You Need to Know About SMS Verification (https://www.broadnet.me/blog/everything-you-need-to-know-about-sms-verification): How SMS (OTP) verification confirms user identity: how the code flow works, the landline limitation … - Using HLR lookup to cut messaging spend and lift deliverability (https://www.broadnet.me/blog/using-hlr-lookup-to-cut-messaging-spend-and-lift-deliverability): An HLR lookup shows which numbers are real, active, and correctly routed before you send — so you st… ## Events (index) - GCCM Brazil 2023 (https://www.broadnet.me/events/gccm-brazil-2023): BroadNet joined GCCM Brazil 2023, meeting wholesale carriers and messaging partners across Latin America on A2P SMS delivery, grey-route… - Seamless KSA 2023 (https://www.broadnet.me/events/seamless-ksa-2023): BroadNet exhibited at Seamless Saudi Arabia 2023 in Riyadh, meeting enterprises and banks on A2P SMS, OTP authentication, and omnichannel… - WWC Madrid 2023 (https://www.broadnet.me/events/wwc-madrid-2023): BroadNet exhibited at WWC Madrid 2023 from Booths #19 and #20, meeting international carriers and aggregators on A2P SMS routing, firewall… - MWC Las Vegas 2023 (https://www.broadnet.me/events/mwc-las-vegas-2023): BroadNet joined MWC Las Vegas 2023 at Booth 912, showing operators and enterprises its A2P SMS, SMS firewall, and omnichannel messaging… - GITEX Dubai 2023 (https://www.broadnet.me/events/gitex-dubai-2023): BroadNet exhibited at GITEX Global Dubai 2023 from Booth #H5-35, meeting enterprises and operators across MENA on A2P SMS, OTP, and… - GCCM Muscat 2023 (https://www.broadnet.me/events/gccm-muscat-2023): BroadNet joined GCCM Muscat 2023, meeting Middle East and international carriers on A2P SMS termination, SMS firewall protection, and… - Capacity Asia 2023 (https://www.broadnet.me/events/capacity-asia-2023): BroadNet took part in Capacity Asia 2023 in Singapore, meeting carriers and aggregators across APAC on A2P SMS wholesale, SMS and SS7… - GCCM Miami 2023 (https://www.broadnet.me/events/gccm-miami-2023): BroadNet met messaging experts and carriers at GCCM Miami 2023 at SLS Brickell, discussing A2P SMS termination, SMS firewall protection… - WAS #18 2023 (https://www.broadnet.me/events/was-18-2023): BroadNet took part in WAS #18, meeting the international wholesale messaging community on A2P SMS routing, firewall protection, and… - Capacity Middle East 2024 (https://www.broadnet.me/events/capacity-middle-east-2024): BroadNet joined Capacity Middle East 2024 at the Grand Hyatt Dubai, meeting regional carriers and aggregators on A2P SMS wholesale, SMS and - MWC Barcelona 2024 (https://www.broadnet.me/events/mwc-barcelona-2024): BroadNet exhibited at MWC Barcelona 2024 from Booth #5D31, meeting operators, aggregators, and enterprises on A2P SMS, SMS firewall… - AWC Miami 2024 (https://www.broadnet.me/events/awc-miami-2024): BroadNet exhibited at AWC Miami 2024, meeting carriers and enterprises across the Americas to explore A2P SMS, OTP authentication, and… - WAS #19 Istanbul 2024 (https://www.broadnet.me/events/was-19-istanbul-2024): BroadNet joined WAS #19 in Istanbul, meeting wholesale carriers and aggregators on A2P SMS routing, SMS firewall protection, and… - ITW Washington 2024 (https://www.broadnet.me/events/itw-washington-2024): BroadNet exhibited at International Telecoms Week 2024 in Washington from Booth #2422, meeting global carriers on A2P SMS wholesale, SMS… - GITEX Dubai 2024 (https://www.broadnet.me/events/gitex-dubai-2024): BroadNet exhibited at GITEX Global 2024 at the Dubai World Trade Centre, Booth #H5-35, meeting enterprises and operators on A2P SMS, OTP… - GCCM London 2025 (https://www.broadnet.me/events/gccm-london-2025): BroadNet joined GCCM London 2025 at County Hall, meeting international carriers on advanced SMS firewall and SMSC gateway solutions that… - Capacity Middle East 2025 (https://www.broadnet.me/events/capacity-middle-east-2025): BroadNet returned to Capacity Middle East 2025 at the Grand Hyatt Dubai, meeting regional carriers and aggregators on A2P SMS wholesale… - MWC Barcelona 2025 (https://www.broadnet.me/events/mwc-barcelona-2025): BroadNet exhibited at MWC Barcelona 2025 in Hall 5, Booth #5D31, meeting operators, aggregators, and enterprises on A2P SMS, SMS firewall… - Enterprise Connect 2025 (https://www.broadnet.me/events/enterprise-connect-2025): BroadNet exhibited at Enterprise Connect 2025 at the Gaylord Palms, meeting enterprise communications leaders on API-driven messaging, OTP… - AWC Miami 2025 (https://www.broadnet.me/events/awc-miami-2025): BroadNet exhibited at AWC Miami 2025 from the SMS Corner, Table #8, showing carriers and enterprises its SMSC gateway, SMS firewall, and… - WAS #21 Dubai 2025 (https://www.broadnet.me/events/was-21-dubai-2025): BroadNet joined WAS #21 in Dubai, meeting wholesale carriers and aggregators to explore the future of A2P SMS, firewall protection, and… - ITW 2025 (https://www.broadnet.me/events/itw-2025): BroadNet joined International Telecoms Week 2025, meeting global carriers and aggregators on A2P SMS wholesale, SMS and SS7 firewall… - Seamless Middle East 2025 (https://www.broadnet.me/events/seamless-middle-east-2025): BroadNet exhibited at Seamless Middle East 2025 at the Dubai World Trade Centre, meeting enterprises and banks on A2P SMS, OTP… - Europe GCCM Berlin 2025 (https://www.broadnet.me/events/europe-gccm-berlin-2025): BroadNet joined Europe GCCM & MMS 2025 at the Hotel Palace Berlin, meeting international carriers on next-generation messaging, A2P SMS… - WWC Madrid 2025 (https://www.broadnet.me/events/wwc-madrid-2025): BroadNet exhibited at WWC Madrid 2025 from Booths #20 and #21, meeting international carriers and aggregators on A2P SMS routing, firewall… - GITEX Dubai 2025 (https://www.broadnet.me/events/gitex-dubai-2025): BroadNet joined GITEX Global 2025 in Dubai at the Dubai World Trade Centre, Booth #H5-35, meeting enterprises and operators on A2P SMS… - MWC Las Vegas 2025 (https://www.broadnet.me/events/mwc-las-vegas-2025): BroadNet exhibited at MWC Las Vegas 2025 at the Fontainebleau, Booth 206, meeting operators and enterprises on AI-driven robocall defense… - BroadNet AI Web Seminar 2025 (https://www.broadnet.me/events/broadnet-ai-web-seminar-2025): BroadNet hosted an online AI seminar exploring how two decades of telecom expertise combine with machine learning to power secure… - GCCM Muscat 2025 (https://www.broadnet.me/events/gccm-muscat-2025): BroadNet joined the carrier community in Muscat, meeting Middle East and international operators on A2P SMS termination, SMS firewall… - Smartech Amman 2025 (https://www.broadnet.me/events/smartech-amman-2025): BroadNet exhibited at Smartech Amman 2025 at Mecca Mall, Booth #A30, showing enterprises next-generation messaging — bulk and promotional… - Seamless Saudi Arabia 2025 (https://www.broadnet.me/events/broadnet-riyadh-2025): BroadNet exhibited at Seamless Saudi Arabia 2025 in Riyadh from Booth #AB50-H4, meeting Saudi enterprises on bulk SMS and API-integrated… - Ramadan Messaging Strategy for the Gulf — Timing, Tone & Capacity (https://www.broadnet.me/events/ramadan-messaging-strategy-webinar-2026): A pre-season webinar on how Ramadan reshapes engagement windows in the Gulf, and how to plan campaign timing, tone, and route capacity… - Capacity Middle East (https://www.broadnet.me/events/capacity-middle-east-2026): BroadNet exhibited at Capacity Middle East 2026 at the Grand Hyatt Dubai, Table #E31, meeting carriers and aggregators on intelligent… - AI Everything Egypt 2026 (https://www.broadnet.me/events/ai-everything-egypt-2026): BroadNet brought its global expertise to AI Everything Egypt 2026 at the Egypt International Exhibition Center, Stand #H1-102, showcasing… - Recovering A2P Revenue — An Operator Firewall Roundtable (https://www.broadnet.me/events/operator-firewall-roi-roundtable-2026): An invitation-only roundtable for mobile network operators on closing A2P revenue leakage with modern ML-based SMS and SS7 firewalls. - BroadNet at MWC 2026 — Mobile World Congress (https://www.broadnet.me/events/mwc-2026-barcelona): The BroadNet team met operators, aggregators, and enterprise messaging leaders at the world's largest connectivity event to talk firewalls, - Enterprise Connect 2026 (https://www.broadnet.me/events/broadnet-las-vegas-2026): BroadNet exhibited at Enterprise Connect 2026 in Las Vegas from Booth #208, meeting enterprises and operators on next-generation AI… - AWC Miami 2026 (https://www.broadnet.me/events/awc-miami-2026): BroadNet exhibited at AWC Miami 2026 at Table 67, meeting carriers and enterprises across the Americas on AI-powered messaging, A2P SMS… - SMPP vs HTTP — Choosing the Right Messaging Integration (https://www.broadnet.me/events/smpp-vs-http-integration-workshop-2026): A technical workshop walking engineering teams through the SMPP-versus-HTTP decision — connection models, DLR handling, throughput, and… - ITW 2026 (https://www.broadnet.me/events/itw-2026): BroadNet exhibited at International Telecoms Week 2026 in National Harbor, Maryland, from Booth #508, meeting global carriers and… - Europe GCCM Berlin 2026 (https://www.broadnet.me/events/europe-gccm-berlin-2026): BroadNet joined Europe GCCM & MMS 2026 in Berlin at Booth #E27, meeting international carriers on AI chatbot and omnichannel innovation… - A2P SMS Compliance in the GCC — TDRA & CST Regulatory Update (https://www.broadnet.me/events/a2p-compliance-gcc-tdra-citc-update-2026): A live walkthrough of the latest A2P SMS rules across the Gulf — the UAE telemarketing rules (Cabinet Resolution No. 56 of 2024), Saudi… - WhatsApp Business API Masterclass — Templates, Pricing & the 24-Hour Window (https://www.broadnet.me/events/whatsapp-business-api-masterclass-2026): A hands-on half-day workshop on architecting a cost-efficient WhatsApp Business deployment — message categories, template strategy, and… - Securing OTP at Scale — Latency, Fallback & Fraud (https://www.broadnet.me/events/securing-otp-at-scale-workshop-2026): A technical workshop for teams running high-volume one-time-passcode flows — building fast, resilient, multi-channel OTP delivery that… - WWC Madrid 2026 (https://www.broadnet.me/events/wwc-madrid-2026): BroadNet exhibited at WWC Madrid 2026 from Booths #20 and #21, meeting international carriers and aggregators on A2P SMS routing, SMS… - Seamless Middle East 2026 (https://www.broadnet.me/events/seamless-middle-east-2026): BroadNet exhibited at Seamless Middle East 2026 at the Dubai World Trade Centre, Booth #L70, meeting enterprises and banks on A2P SMS, OTP, - MEF Global Messaging Congress (https://www.broadnet.me/events/mef-gmc-dubai-2026): The industry forum for trusted mobile messaging. BroadNet's compliance and product leads joined the conversation on sender-ID governance… - RCS Business Messaging in MENA — Is the Channel Ready? (https://www.broadnet.me/events/rcs-business-messaging-mena-webinar-2026): A clear-eyed look at RCS rollout across the Gulf operators, capability-check architecture, and how to deploy RCS in 2026 without stranding… - GITEX Global (https://www.broadnet.me/events/gitex-global-dubai-2026): The largest tech event in MENA. BroadNet's enterprise team will be hosting executive briefings on omnichannel customer messaging — A2P SMS, - Middle East 2026 GCCM & SIS Summit (https://www.broadnet.me/events/gccm-muscat-2026): BroadNet joins the Middle East 2026 GCCM & SIS Summit in Muscat, 1–4 November, to meet carriers, operators and infrastructure leaders on… - GSMA M360 MENA (https://www.broadnet.me/events/gsma-m360-mena-2026): The GSMA's flagship event for MENA operators. We'll be in the operator track talking SS7 & SMS firewall deployments, GSMA FS.11 / FS.19… - AfCom — Africa Communications Week (https://www.broadnet.me/events/afcom-cairo-2026): Africa's annual gathering of carriers, towercos and digital-services providers. BroadNet's Cairo team will be meeting operators and… - Mobile World Congress (https://www.broadnet.me/events/mwc-barcelona-2027): The largest connectivity event in the world. BroadNet's operator-solutions and product teams will be on the ground for four days of… ## Full answers (inlined) ### What is A2P SMS URL: https://www.broadnet.me/answers/what-is-a2p-sms Last reviewed: August 8, 2026 A2P (application-to-person) SMS is a text message initiated by a business software application — for OTPs, notifications, alerts, transactional confirmations, marketing — delivered to a consumer mobile phone. A2P is the dominant business-messaging modality globally, with over 2 trillion A2P messages sent per year. **How A2P SMS works** An enterprise application calls a CPaaS or SMS API (like BroadNet's). The CPaaS routes the message through its SMSC to a mobile network operator via SMPP, SS7, or HTTP. The operator's SMSC delivers to the recipient's handset. A delivery receipt comes back through the same path. **A2P vs P2P SMS** P2P is text from one person to another via their mobile dial-pad. A2P is sent by software to a person. A2P is regulated, monetized, and routed differently from P2P — A2P routes have higher operator fees but high, operator-direct deliverability. **What's a grey route?** A grey route is A2P traffic that bypasses official A2P agreements by appearing as P2P — using consumer SIMs, foreign HLRs, or SS7 backdoors. Grey routes deliver but are unreliable, untraceable, and cost operators billions in lost revenue. BroadNet operates on direct A2P routes only. ### What is an SMS API URL: https://www.broadnet.me/answers/what-is-sms-api Last reviewed: September 30, 2026 An SMS API is a REST or SMPP endpoint that enterprise applications call to send SMS messages programmatically. It abstracts the SMSC, the operator connections, the SS7 signalling, and the regulatory compliance — exposing a simple POST /messages or SMPP submit_sm command. **REST vs SMPP** REST (HTTPS POST) has no fixed per-account rate limit at BroadNet — throughput is sized to your traffic. SMPP 3.4 binding suits sustained volumes of several hundred messages per second or workloads that need persistent binds (capacity per bind agreed with your account team, up to 30,000 SMS/s per node) — typically OTP services, large e-commerce, or operator-level traffic. ### What is CPaaS URL: https://www.broadnet.me/answers/what-is-cpaas Last reviewed: October 1, 2026 CPaaS — Communications Platform as a Service — is cloud software that exposes SMS, voice, WhatsApp, RCS, email, and verification as developer APIs, so a business can build customer communications into its own apps without contracting mobile operators directly. It turns multi-operator telecom plumbing — SMSCs, SS7, sender-ID registration, routing and failover — into a few authenticated API calls. BroadNet has run a MENA-native CPaaS since 2003, reaching 200+ countries over 1,000+ direct operator connections, with direct binds in 86 of them. **What a CPaaS exposes** At the core are channel APIs — SMS, voice, WhatsApp, RCS, email, and verification (OTP/2FA) — reached over a REST endpoint or an SMPP bind and wrapped in SDKs. Around them sit the pieces that make those channels usable: phone-number and sender-ID provisioning, a routing-and-failover engine across operator connections, delivery receipts and inbound webhooks, and dashboards for analytics, logs, and billing. You make one API call; the platform handles encoding, least-cost routing, regulatory compliance, and status callbacks. See /answers/what-is-sms-api and /products/omnichannel. **How it differs from raw carrier integration** Without a CPaaS, reaching subscribers means negotiating a separate contract with each mobile operator, running your own SMSC or SS7/SMPP stack, handling sender-ID registration market by market, and rebuilding all of it for every new country or channel. A CPaaS collapses that into one integration and one invoice: it already holds the operator agreements, maintains the routes, and keeps compliance current — so adding a country, or a channel like WhatsApp or RCS, becomes a config change instead of a new telecom project. See /answers/cpaas-explained. **Typical use cases** OTP and two-factor authentication in signup and login flows; transactional alerts such as payment confirmations and shipping or appointment reminders; marketing and re-engagement campaigns; two-way conversational support over WhatsApp or SMS; and programmable voice for notifications, IVR, and voice OTP. The common thread is a developer embedding communications into an existing product rather than buying a separate messaging tool. See /answers/what-is-otp and /answers/what-is-omnichannel-messaging. **CPaaS vs. a messaging aggregator** Historically an SMS aggregator resold bulk SMS termination wholesale, while a CPaaS added voice, omnichannel, and developer APIs on top. Today the terms overlap — most CPaaS vendors are also aggregators, and aggregators have added CPaaS-style APIs. The useful test is breadth and programmability: a true CPaaS gives you multiple channels and real SDKs, not just an SMS HTTP endpoint. See /answers/what-is-sms-aggregator. ### What is CPaaS, and how does it work URL: https://www.broadnet.me/answers/cpaas-explained Last reviewed: October 2, 2026 CPaaS (Communications Platform as a Service) is cloud software that exposes voice, SMS, WhatsApp, RCS, email, and verification as developer APIs — so a business can add communications to its own apps without contracting mobile operators directly. BroadNet is a MENA-native CPaaS operating since 2003, reaching 200+ countries over 1,000+ operator connections and carrying 300M+ messages a day. **How a CPaaS works** Your application makes an HTTPS (or SMPP) call to the platform's API; the CPaaS handles carrier connectivity, number provisioning, message encoding, least-cost routing, regulatory compliance, and delivery-receipt handling, then streams status back via webhooks. The developer never touches an SMSC, an SS7 stack, or an operator contract — the platform abstracts all of it behind a REST endpoint and SDKs. See /platforms/cpaas and /answers/what-is-sms-api. **The core components** Channel APIs (SMS, voice, WhatsApp, RCS, email, verification); SDKs and a REST/SMPP surface; phone-number and sender-ID provisioning; a routing and failover engine across operator connections; delivery receipts and webhooks; and dashboards for analytics, logs, and billing. Together they turn multi-operator telecom plumbing into a few API calls. See /answers/what-is-cpaas and /answers/what-is-omnichannel-messaging. **CPaaS vs UCaaS vs CCaaS** CPaaS sells building-block APIs that developers embed in their own software. UCaaS (Unified Communications) sells a finished product — cloud phone system, meetings, chat — for internal collaboration. CCaaS (Contact Center) sells a finished agent-facing contact-centre suite. The distinction is programmability: CPaaS is the toolkit; UCaaS and CCaaS are the assembled applications, often built on top of a CPaaS. See /products/omnichannel. **Benefits of building on a CPaaS** One integration reaches every operator and channel; pay-per-use billing instead of carrier contracts and minimum commits; new channels (add WhatsApp or RCS) without new plumbing; and built-in compliance, routing, and failover the platform maintains for you. It puts SMS, voice, and rich messaging on the same developer footing as any other API in your stack. See /products/sms-api, /products/voice, and /products/whatsapp-business-api. **Limitations and what to evaluate** CPaaS quality varies on the things you cannot see from the API: route directness (are they on direct A2P routes or grey routes?), operator coverage in your target markets, deliverability and DLR fidelity, support responsiveness, and regulatory reach for sender-ID registration. A clean API in front of poor routes still delivers poorly — evaluate the network, not just the docs. See /answers/what-is-grey-route-sms and /answers/what-is-throughput-sla. **Is CPaaS the same as an SMS aggregator?** Historically no: an SMS aggregator resold bulk SMS termination, while a CPaaS added voice, omnichannel, and developer APIs on top. Today the terms overlap — most CPaaS vendors are also aggregators, and aggregators have added CPaaS-style APIs. The useful test is breadth and programmability: a true CPaaS gives you multiple channels and real SDKs, not just an SMS HTTP endpoint. See /answers/what-is-a2p-sms. ### What is OTP URL: https://www.broadnet.me/answers/what-is-otp Last reviewed: July 20, 2026 OTP (One-Time Password) is a single-use code sent to a user to verify their identity for login, transaction, or account recovery. OTPs are most commonly delivered via SMS, but also via WhatsApp, email, voice, and authenticator apps. OTP is the most common form of 2FA (two-factor authentication) globally. ### What is RCS URL: https://www.broadnet.me/answers/what-is-rcs Last reviewed: July 16, 2026 RCS (Rich Communication Services) is the modern replacement for SMS — a protocol that supports verified branded senders, rich cards, suggested replies, read receipts, and group messaging. RCS Business Messaging (RBM) is the enterprise variant. Native in Android Messages since 2019; supported on iPhone since iOS 18 (2024). ### How does RCS Business Messaging work URL: https://www.broadnet.me/answers/rcs-business-messaging Last reviewed: July 22, 2026 RCS Business Messaging (RBM) is the GSMA Universal Profile channel that lets a verified brand send rich, interactive messages — a logo, verified sender name, rich cards, carousels, suggested replies, and read receipts — to the native Messages app on Android and, since iOS 18 (2024), iPhone. It upgrades SMS to an app-like experience without the recipient installing anything. **How RBM works, end to end** A brand registers an RBM agent, which is verified by the carrier or an aggregator and given a branded sender identity. Messages are submitted over the RBM API to the RCS platform (often Google's Jibe or a carrier hub), delivered to the recipient's Messages app, and — crucially — fall back to SMS automatically when the recipient's device or network doesn't support RCS. See /products/rcs-messaging and /answers/what-is-rcs. **The message types RBM supports** Rich cards (image, title, description, tappable buttons), horizontal carousels of cards, suggested replies and suggested actions (open URL, dial, share location, add to calendar), plus read receipts and typing indicators. Content is far richer than SMS's 160 characters or MMS media. See /answers/what-is-rcs-business-messaging and /answers/rcs-vs-sms. **Verified sender — why it matters** Every RBM agent is verified, so the brand name, logo, and a verification checkmark are cryptographically bound to the sender. The recipient can trust the message is genuinely from the brand — closing the sender-ID spoofing gap that makes SMS a smishing vector. See /answers/what-is-sender-id-spoofing and /answers/what-is-smishing. **Benefits over SMS** Branded, trusted sender identity; app-like interactivity that lifts conversion; read receipts and analytics SMS can't provide; and automatic SMS fallback so you never lose reach. For customer journeys that need buttons, images, and two-way flow without an installed app, RBM is the native upgrade path. See /answers/rcs-vs-whatsapp. **Limitations to plan for** Reach depends on device, OS version, and carrier RCS enablement, so coverage varies by market and you must design an SMS fallback. Agent verification and carrier onboarding take time, and rich features degrade gracefully when the recipient is on an older client. RBM complements, rather than fully replaces, SMS and WhatsApp. See /answers/what-is-ott-bypass. **Does RCS Business Messaging work on iPhone?** Yes — Apple added RCS Universal Profile support in iOS 18 (2024), so iPhones on a carrier with RCS enabled receive RBM messages in the native Messages app. Before that, RBM reached Android only. Because support still varies by device and carrier, a well-built RBM campaign always falls back to SMS for recipients who can't receive RCS. See /answers/rcs-vs-sms. ### What is a WhatsApp BSP URL: https://www.broadnet.me/answers/what-is-whatsapp-bsp Last reviewed: October 10, 2026 A WhatsApp Business Solution Provider (BSP) is a Meta-approved partner that hosts enterprise access to the WhatsApp Business API. Businesses can also connect directly through Meta's Cloud API, but most work through a BSP for onboarding, template approval, verification, billing and support. BroadNet is an official Meta BSP. **What does a BSP do?** Onboards your WhatsApp Business Account, submits message templates for Meta approval, hosts the API endpoint, manages Green Tick verification, and bills you for the messages you send. Provides webhooks, SDKs, and the operational continuity that direct WhatsApp Business API access wouldn't. ### What is WhatsApp Business API URL: https://www.broadnet.me/answers/what-is-whatsapp-business-api Last reviewed: October 20, 2026 WhatsApp Business API is Meta's enterprise messaging product — a programmatic interface for businesses with more than a few hundred customer conversations per day. Unlike the free WhatsApp Business app (designed for SMEs), the API has no UI: you integrate it into your CRM, support desk, or in-house systems via a Meta-approved Business Solution Provider (BSP). **How it differs from the WhatsApp Business app** The free app is a single-device application that a small business owner runs on their phone. The API is a server-side product: webhook-driven, multi-agent, integrable, and built for volume. The API has a strict template-approval process, per-message template pricing, and a Green Tick verification track that the app does not get. **Why most businesses use a BSP** A business can connect to the WhatsApp Business Platform directly through Meta's Cloud API, or through a Meta-approved Business Solution Provider (BSP) such as BroadNet. Most enterprises choose a BSP for onboarding, template approval, Green Tick verification, billing and support. The BSP manages your phone number's WhatsApp Business Account (WABA), submits templates for Meta approval and provides the API endpoint, webhooks and tooling your code uses. Switching BSPs means migrating the WABA — disruptive but doable. **Per-message pricing** Since 1 July 2025 Meta bills each delivered template message, classified as Marketing, Utility or Authentication, at list rates that Meta sets per market and revises from time to time; BroadNet quotes the current rate for each market you send to. From 1 October 2026 Meta bills replies inside the 24-hour customer service window per message, at the same rate as utility and authentication messages in that market: service replies after a free tier of 1,000 service messages per business phone number per month, utility templates from the first message. Your BSP passes Meta cost through plus a small platform fee. **What templates are and why they matter** Any business-initiated message must use a pre-approved template — a structured message with placeholders, submitted via the API and reviewed by Meta within 24 hours. Templates are categorised at approval; misclassified templates get rejected or auto-recategorised. Get your template strategy right at integration time or you will be reworking them six months in. See /products/whatsapp-business-api for the integration guide. ### What is an SMS firewall URL: https://www.broadnet.me/answers/what-is-sms-firewall Last reviewed: September 30, 2026 An SMS firewall is an operator platform that inspects, classifies, and controls SMS traffic on the messaging path. It blocks grey routes, SIM-box injection, smishing, and sender-ID spoofing while enforcing that application-to-person (A2P) traffic is properly declared and billed — protecting subscribers from fraud and recovering leaked A2P revenue. **The control point on the messaging path** An SMS firewall sits on or alongside the operator's SMSC and message interconnect, inspecting SMS as it enters the network. Where an SS7 firewall polices signaling, an SMS firewall polices messaging: it separates person-to-person (P2P) traffic from application-to-person (A2P) traffic — the OTPs, alerts, and marketing sent by enterprises — and applies commercial and security policy. That distinction is the economic heart of the system: A2P termination is a significant, billable revenue stream that fraudsters constantly try to bypass by disguising A2P as P2P. - Inspects SMPP-, MAP-, and SIP-based message flows entering the network. - Classifies P2P vs. A2P and by content category (OTP, transactional, promotional). - Applies security policy (block/allow/throttle) and commercial policy (bill A2P correctly). - Typically integrated with an A2P monetization / hubbing agreement. **How an SMS firewall works** The firewall sits inline at the SMS interconnect — on the SS7/SIGTRAN signalling path and on the SMPP application path. For each message it inspects the sender ID, content, origin, and throughput, scores it against per-peer reputation and policy, then passes, tags, rate-limits, or drops it. Every decision is logged for audit. **Why operators deploy SMS firewalls** The primary commercial driver is A2P monetization. Enterprises pay to reach subscribers, but if that traffic sneaks in as P2P through grey routes or SIM boxes, the operator terminates it for free and loses the revenue. An SMS firewall detects disguised A2P and forces it onto the sanctioned, billable route — often the difference between a messaging channel that leaks money and one that is a profit center. The global A2P messaging market is measured in tens of billions of dollars a year, so even small leakage rates represent material lost revenue. - Recover revenue from A2P disguised as P2P. - Enforce that enterprise traffic uses contracted, billable termination. - Provide the commercial data (who is sending what) to support A2P wholesale deals. **Grey routes and SIM boxes — the two classic leak vectors** A grey route is a delivery path that is technically functional but commercially or legally unsanctioned — most often A2P injected as P2P to dodge A2P termination fees. SIM boxes (SIM farms) are the physical version: racks of SIMs that originate bulk enterprise messages as if they were ordinary subscribers, terminating for free. An SMS firewall detects these through message velocity (a single 'subscriber' sending thousands of near-identical messages), content fingerprinting (the same OTP template across many senders), and source anomalies. Grey routes are also the primary channel through which artificially inflated traffic (AIT) flows. - Grey route: A2P disguised as P2P to avoid A2P fees; ambiguous legality. - SIM box: SIM farm injecting bulk A2P as local P2P. - Detection: velocity, content fingerprinting, source/behaviour anomalies. - Grey routes carry unreliable delivery and are the main AIT and interception conduit. **Sender-ID enforcement — stopping spoofed senders** Alphanumeric and numeric sender IDs are trivially spoofable at the protocol level, which is how phishing messages appear to come from a bank or delivery company. An SMS firewall enforces sender-ID policy: allow-listing registered enterprise sender IDs, blocking or quarantining unregistered ones, and rejecting messages that spoof protected brands. Regulator-driven registration regimes make this concrete — India's TRAI DLT framework requires senders and templates to be pre-registered, and the industry-run MEF SMS SenderID Protection Registry lets brands and operators protect specific sender IDs across networks. - Allow-list registered enterprise sender IDs; block or quarantine the rest. - Enforce anti-spoofing on protected brand names. - Support regulator regimes (e.g., India TRAI DLT registration). - Integrate with the MEF SMS SenderID Protection Registry where available. **Smishing and content threats** Smishing (SMS phishing) tricks subscribers into clicking malicious links or surrendering credentials. An SMS firewall applies content controls — URL extraction and reputation checks, known-bad-link blocklists, keyword and template matching, and machine-learning classifiers that catch novel campaigns by their structure rather than an exact signature. Because fraudsters rotate URLs and wording quickly, effective smishing defence combines static blocklists (fast, precise) with behavioural/ML detection (adaptive), rather than relying on either alone. - Extract and reputation-check embedded URLs. - Blocklist known malicious links and templates. - ML classification to catch reworded / novel campaigns. - Feed confirmed smishing patterns back into the rule base. **How detection works — DPI plus machine learning** SMS firewalls combine deep packet inspection (DPI) with statistical and machine-learning analysis. DPI parses the message and protocol fields to classify P2P vs. A2P, extract sender IDs and URLs, and apply signature rules. Machine learning adds the behavioural layer: baselining normal per-sender and per-route volumes, flagging spikes and pattern shifts, and scoring traffic for grey-route or AIT characteristics that no single message would reveal. Signature rules give precision and speed; ML gives adaptability against fraud that constantly mutates. - DPI: protocol/content parsing, classification, signature rules. - ML: behavioural baselining, anomaly and fraud scoring. - Fusion: precision of rules plus adaptability of models. **The two planes: A2P/content vs SS7/signalling** A complete firewall covers two planes. The A2P (content) firewall inspects SMPP message bodies, sender IDs, and URLs. The signalling firewall inspects SS7 MAP and Diameter operations to stop location-tracking and interception. Best practice is a single policy engine spanning both, with shared subscriber reputation — split stacks drift. See /answers/gsma-fs07-fs11-signaling-firewall and /operators/ss7-firewall. **Deployment and operations** An SMS firewall integrates at the SMSC/interconnect and can run inline (blocking in real time) or in analysis mode for tuning. Operationally it must handle carrier-scale throughput, expose clear reporting for fraud and wholesale teams, and stay current as threats and regulations evolve. Many operators run it as part of a managed A2P / hubbing relationship, where the partner also brings destination-network reach and sender-ID registration — which is how BroadNet's operator SMS firewall is typically delivered. - Integrate at SMSC/interconnect; inline enforcement plus analysis mode. - Carrier-grade throughput and availability. - Fraud and commercial reporting for security and wholesale teams. - Often delivered as a managed A2P monetization service. **Limitations and operational realities** A firewall is only as good as its tuning. Over-aggressive rules create false positives that block legitimate A2P; under-tuned rules leak revenue. It needs constant rule maintenance and fresh reputation feeds, and it cannot see inside encrypted OTT channels — WhatsApp and RCS traffic sits outside the SMS firewall's scope entirely. See /answers/what-is-ott-bypass. Q: What is the difference between an SMS firewall and an SS7 firewall? A: An SMS firewall works at the messaging layer — content, sender ID, routing, and A2P billing. An SS7 firewall works at the signaling layer — location, mobility, and interception attacks. They solve different problems and are often deployed together. Q: Will an SMS firewall recover lost A2P revenue? A: That is one of its main purposes. By detecting A2P traffic disguised as P2P and forcing it onto the sanctioned billable route, an SMS firewall converts leaked traffic into billed traffic. The recovered revenue frequently funds the deployment itself. Q: Does an SMS firewall hurt legitimate enterprise messaging? A: It should improve it. Legitimate senders using registered sender IDs and sanctioned routes pass cleanly and get accurate delivery receipts, while grey-route competitors are removed. Proper tuning and an analysis-mode rollout keep false positives low. Q: How does an SMS firewall detect grey routes if the message looks normal? A: Individual messages can look legitimate; the firewall detects grey routes through behaviour — volume, velocity, content repetition across supposed P2P senders, and source anomalies — plus route reputation, rather than judging a single message in isolation. Q: Is an SMS firewall required for regulatory compliance? A: In several markets, sender-ID registration and anti-spam obligations effectively require operator-side control that an SMS firewall provides (for example, India's TRAI DLT regime). Requirements vary by country. Q: Can an SMS firewall stop AIT / SMS pumping? A: It is a key control. The firewall can spot abnormal OTP-request surges and unusual destination concentration and throttle or block them, though the strongest defence pairs the firewall with sender-side controls on the enterprise's OTP endpoints. Q: Inline or analysis mode first? A: Most operators start in analysis mode to baseline traffic and tune classification, then move to inline blocking once false-positive rates on legitimate P2P and A2P are acceptable. ### How does SS7 and Diameter signaling security work URL: https://www.broadnet.me/answers/ss7-signaling-security Last reviewed: July 22, 2026 SS7 signaling security is the set of operator controls — signaling firewalls, per-category message filtering, and peer reputation scoring — that protect the SS7 and Diameter control plane from location tracking, SMS interception, and fraud. Aligned to GSMA IR.82, IR.88, FS.07 and FS.11, it screens MAP and Diameter operations at the network edge so only legitimate inter-operator signaling passes. **How SS7 and Diameter signaling security works** A signaling firewall sits inline at the interconnect, inspecting every inbound SS7 MAP and 4G Diameter operation before it reaches the HLR, HSS, or MSC. Each message is checked against GSMA category rules, the sender's global-title reputation, and plausibility (does this roaming update make geographic sense?), then passed, rate-limited, or dropped. Every decision is logged for audit. See /answers/what-is-ss7 and /answers/ss7-map-explained. **The threats it stops** SendRoutingInfoForSM harvesting that reveals a subscriber's IMSI and serving MSC for location tracking; ProvideSubscriberInfo and AnyTimeInterrogation location queries; SMS interception via rogue MT-ForwardSM; and Diameter equivalents on 4G. See /answers/ss7-map-send-routing-info-for-sm, /answers/ss7-map-provide-subscriber-info, and /answers/diameter-s6a-explained. **The GSMA standards: IR.82, IR.88, FS.07 and FS.11** GSMA IR.82 sets SS7 security implementation guidelines and the Category 1/2/3 message classification; IR.88 covers LTE/EPC Diameter roaming; FS.07 defines SS7 monitoring and FS.11 the SS7 interconnect security controls. Together they tell operators which inter-network operations to block, rate-limit, or allow by peer. See /answers/gsma-fs07-fs11-signaling-firewall. **Benefits for the operator** Subscriber protection against tracking and interception, regulatory and GSMA compliance, a tamper-evident signaling audit trail, and the ability to correlate signaling with A2P traffic to catch fraud that spans both planes. BroadNet pairs the signaling firewall with SMS-firewall and CDR intelligence for one policy view. See /operators/ss7-firewall and /platforms/signaling-cdr. **Limitations and operational realities** A signaling firewall is only as good as its category rules and reputation feeds — over-blocking breaks legitimate roaming, under-tuning leaks attacks. It must span both SS7 and Diameter because networks run hybrid 2G/3G/4G cores, and it cannot see inside encrypted 5G service-based signaling, which needs its own SEPP controls. See /answers/what-is-sigtran. **SS7 firewall vs SMS firewall — what's the difference?** An SS7 (signaling) firewall polices the network control plane — MAP and Diameter operations — to stop location tracking and interception. An SMS (A2P) firewall polices the application layer — message content, sender IDs, and SMPP delivery — to stop smishing and grey routes. They defend different layers and are strongest deployed together. BroadNet delivers both. See /operators/sms-firewall and /operators/ss7-firewall. ### What is SS7 URL: https://www.broadnet.me/answers/what-is-ss7 Last reviewed: July 22, 2026 SS7 (Signalling System No. 7) is the ITU-T-defined control-plane signalling system that 2G and 3G mobile networks use for call setup, mobility management, and SMS routing. Its layered stack — MTP, SCCP, TCAP, and MAP — carries the SendRoutingInfoForSM and MT-ForwardSM operations that deliver every cross-operator SMS to a handset. On 4G and 5G, Diameter and HTTP/2 signalling take over, but SS7 still underpins the majority of SMS delivered today. **The SS7 stack, layer by layer** MTP (Message Transfer Part) is the transport; SCCP (Signalling Connection Control Part) adds global-title routing; TCAP (Transaction Capabilities) handles dialogues; and MAP (Mobile Application Part) is the mobile application layer that actually carries SMS and location operations. Over IP, SS7 rides on SIGTRAN. See /answers/ss7-map-explained and /answers/what-is-sigtran. **Why SS7 is a security concern** SS7 was designed for a small, trusted club of state telcos, so peers largely trust each other with no per-message authentication. That trust is abused for location tracking and SMS interception — most notoriously via SendRoutingInfoForSM harvesting. GSMA FS.07 and FS.11 define the signalling-firewall controls that close these holes; BroadNet operates one at /operators/ss7-firewall. ### How does Diameter signaling security work URL: https://www.broadnet.me/answers/diameter-signaling-security Last reviewed: July 22, 2026 Diameter signaling security is the set of operator controls — a Diameter Edge Agent (DEA) and a signaling firewall applying GSMA FS.19 rules — that protect the 4G/LTE and 5G non-standalone Diameter control plane from location tracking, subscriber-data theft, and fraud. It screens S6a/S6d and roaming Diameter messages at the network edge so only legitimate inter-operator signaling reaches the HSS. **How Diameter signaling security works** Diameter is the AAA signaling protocol that replaced SS7 MAP on the 4G core — the MME and HSS exchange S6a/S6d messages to attach subscribers, authorise service, and route SMS. A Diameter Edge Agent sits at the roaming interconnect (the S6a/S9/S6d border) and every inbound message is checked against GSMA FS.19 rules, the origin realm's reputation, and plausibility — does this Update-Location come from a realm the subscriber could actually be roaming in? — then passed, rate-limited, or dropped, with every decision logged. See /answers/diameter-s6a-explained and /answers/what-is-hss. **The threats it stops** Forged Update-Location-Request (ULR) messages that hijack a subscriber's routing to intercept calls and SMS; Insert-Subscriber-Data and Cancel-Location abuse that tampers with a profile or forces a denial of service; and location disclosure through the SLh/SLg location interfaces. These are the Diameter equivalents of the SS7 MAP attacks GSMA FS.11 addresses. See /answers/ss7-signaling-security and /answers/ss7-map-send-routing-info-for-sm. **GSMA FS.19 and the Diameter Edge Agent** GSMA FS.19 (Diameter Interconnect Security) is the reference document: it defines a category model for inter-operator Diameter messages and tells operators which to block, rate-limit, or allow by realm. The Diameter Edge Agent is the border element that enforces it — the topology-hiding, screening choke point at the LTE roaming edge, the exact analogue of the STP-plus-firewall on the SS7 side. See /answers/gsma-fs07-fs11-signaling-firewall. **Diameter vs SS7 signaling security** SS7/MAP security defends the 2G/3G control plane; Diameter security defends the 4G/LTE control plane. Because most networks run a hybrid 2G/3G/4G core and SMS still falls back to SS7 for many handsets, an attacker who is blocked on one plane simply tries the other — so the two firewalls must run as one policy with shared subscriber reputation. On 5G standalone the equivalent job passes to the SEPP over HTTP/2. See /answers/what-is-ss7 and /answers/what-is-sigtran. **Benefits for the operator** Subscriber protection against tracking and interception, GSMA and regulator compliance, a tamper-evident Diameter audit trail, and the ability to correlate Diameter with SS7 and A2P traffic to catch fraud that spans planes. BroadNet pairs the Diameter and SS7 signaling firewall with SMS-firewall and CDR intelligence for a single policy view across the network. See /operators/ss7-firewall and /platforms/signaling-cdr. **Limitations and operational realities** A Diameter firewall is only as good as its category rules and realm reputation — over-blocking breaks legitimate roaming partners, under-tuning leaks attacks. It cannot see inside the encrypted service-based signaling of a 5G standalone core, which needs its own SEPP and TLS controls, and it must be kept in step with the SS7 firewall so hybrid-core gaps do not open. See /answers/ss7-signaling-security. **Is Diameter more secure than SS7?** Only marginally, and not by design. Diameter supports IPsec/TLS and realm-based screening that SS7 lacked, but early LTE roaming shipped without them, so real-world Diameter interconnects inherited the same trust-the-peer weakness as SS7 — which is why GSMA FS.19 exists. The practical answer is that neither plane is safe unattended: both need a signaling firewall. BroadNet secures both across 60+ operator networks. See /operators/ss7-firewall. ### How does telecom fraud prevention work URL: https://www.broadnet.me/answers/telecom-fraud-prevention Last reviewed: July 22, 2026 Telecom fraud prevention is the layered defence operators and enterprises use against messaging and voice fraud — AIT/SMS pumping, grey routes, SIM-box bypass, smishing, sender-ID spoofing, and Wangiri call-back scams. It combines SMS and SS7/Diameter firewalls, real-time number intelligence, traffic analytics, and content screening to detect and block abuse at the moment it enters the network. **How fraud prevention works** There is no single control — effective defence is layered. Firewalls inspect messaging and signaling inline; number intelligence validates and screens destinations before a send; traffic analytics profile behaviour to spot anomalies (a sudden OTP flood to one number range, one-way high-throughput SMS from consumer SIMs); and content screening catches malicious URLs and spoofed sender IDs. Each layer catches what the others miss. See /operators/anti-fraud-sms and /operators/sms-firewall. **The main fraud types** AIT / SMS pumping (inflated OTP traffic to premium ranges); grey routes (A2P sneaking in as cheap P2P); SIM-box bypass (fraudulent gateways terminating international traffic as local); smishing (phishing over SMS); sender-ID spoofing (impersonating a trusted brand); and Wangiri (missed-call scams luring premium-rate call-backs). See /answers/what-is-ait, /answers/what-is-grey-route-sms, /answers/what-is-sim-box-fraud, /answers/what-is-smishing, and /answers/what-is-wangiri-fraud. **The tools: SMS firewall, SS7 firewall, number intelligence** An SMS (A2P) firewall polices message content, sender IDs, and delivery; an SS7/Diameter signaling firewall polices the control plane to stop interception and location tracking; and HLR/number-intelligence lookups validate destinations before a send to blunt AIT and dead-number waste. Deployed together with shared reputation, they defend the application and network planes as one. See /operators/ss7-firewall, /products/hlr-lookup, and /answers/what-is-sender-id-spoofing. **Benefits** For operators: subscriber protection, recovered revenue from blocked bypass, and regulator/GSMA compliance with an audit trail. For enterprises: lower verification spend as AIT is throttled, protected brand reputation as spoofing and smishing are blocked, and cleaner deliverability once grey routes are off the path. See /answers/what-is-a2p-monetization and /answers/messaging-monetization. **Limitations and operational realities** Fraud defence is a moving target — rules and reputation feeds need constant maintenance, over-blocking creates false positives that harm legitimate traffic, and encrypted OTT channels (WhatsApp, RCS) sit outside an SMS firewall's view. Fraudsters shift planes and geographies as controls tighten, so detection has to correlate messaging, signaling, and CDR data rather than watch any one silo. See /answers/what-is-ott-bypass and /platforms/signaling-cdr. **What is the most common messaging fraud today?** Artificially inflated traffic — AIT, or SMS pumping — is the fastest-growing and most costly for enterprises: bots trigger OTP floods to number ranges the fraudster profits from, and the victim only sees the bill. The single most effective countermeasure is validating the destination number before sending and rate-limiting per number and IP, backed by an operator SMS firewall on the terminating side. See /answers/what-is-sms-pumping and /operators/anti-fraud-sms. ### What is SMS pumping / artificial inflated traffic (AIT) URL: https://www.broadnet.me/answers/what-is-sms-pumping Last reviewed: September 27, 2026 Artificially Inflated Traffic (AIT) — also called SMS pumping or SMS toll fraud — is a scam in which bots trigger huge volumes of one-time-passcode and verification SMS from a brand's own app or website. The messages never reach real users; fraudsters colluding in the delivery chain simply collect the per-message termination fees. You pay the SMS bill; they take the cut. **How a pumping attack works** AIT abuses any web or app form that sends an SMS on demand — signup, login, phone verification, "resend code." A fraudster scripts bots to request that SMS thousands or millions of times, targeting phone numbers in ranges they control or that route through a colluding party in the delivery chain (an aggregator or terminating operator taking a revenue share). Each message the brand's provider sends generates a billable termination fee that flows, in part, to the fraudster. - Entry point: any unauthenticated "send me an SMS" endpoint (OTP, verify, resend). - Bots generate mass requests to fraudster-controlled or colluding number ranges. - Revenue-share collusion in the delivery chain converts volume into payout. - The brand pays; no real user ever receives value. **The fraud economics — why AIT is a business** AIT is a revenue-share fraud. It only works when someone in the termination chain — a rogue aggregator or an operator willing to look the other way — shares the inflated termination fee with the party generating the traffic. High-cost international number ranges are especially attractive because each pumped message carries a larger fee to split. Grey routes are the natural conduit, since sanctioned operator-direct routes are monitored and reconciled. - Requires collusion in the terminating chain to monetize. - High-cost destination ranges maximize the fraudster's cut per message. - Grey routes are the preferred, harder-to-reconcile conduit. - Industrialized scale — Juniper Research estimated known AIT at ~18% of international A2P SMS in 2023. **What it costs the industry** Estimates vary by scope, so cite carefully. Juniper Research (published March 2024, with VOX Solutions) put the global cost of AIT and SMS trashing to enterprises at roughly USD 8.5 billion in 2023, projecting it to still cost around USD 23.4 billion by 2027. For context, the CFCA Global Fraud Loss Survey 2023 estimated total telecom fraud at about USD 38.95 billion. - Juniper Research: ~USD 8.5B cost to enterprises in 2023; ~USD 23.4B by 2027. - CFCA 2023: total telecom fraud ~USD 38.95B. - Attribute every number to its source and year — scopes differ. **Detection signals — how to tell you are being pumped** AIT leaves a distinctive fingerprint because the traffic is engineered for fees, not users. The clearest tell is a spike in OTP/verification requests that does not convert into signups, logins, or any downstream activity — high send volume, near-zero engagement. Pumped numbers often do not exist on the network, so delivery receipts come back undelivered with absent-subscriber codes. Watching send-to-conversion by destination is often the single most revealing metric. - OTP request surge with no signup/login conversion. - Traffic suddenly concentrated in unusual countries or number ranges. - Automation-shaped time-of-day and burst patterns. - Low DLR success (absent-subscriber codes) on the pumped ranges. **Sender-side defenses — what the brand controls** Because AIT starts at the brand's own endpoint, the first line of defense is there. Rate-limit and add CAPTCHA or bot-detection to OTP endpoints. Apply geo and velocity controls — block or challenge verification requests to destinations you do not serve. Validate the destination number with HLR Lookup before sending; pumped numbers often fail. Where possible, move high-risk flows to authenticator apps or silent network verification, which remove the pumpable SMS entirely. - Rate limiting plus CAPTCHA/bot detection on OTP endpoints. - Geo/velocity limits; block destinations you do not serve. - HLR pre-validation and number-range blocklists. - Migrate high-risk flows to flash-call or silent network verification. **Network-side defenses — what the operator and firewall control** On the network side, an SMS firewall and route monitoring catch what the brand misses. The firewall detects abnormal OTP-request concentration and destination anomalies and can throttle or block suspect flows, while route reconciliation exposes the grey routes and high-cost ranges AIT depends on. Operating over sanctioned operator-direct routes rather than grey routes removes the fraudster's preferred conduit and yields accurate, handset-confirmed delivery receipts that make pumping easier to spot. - Firewall-level anomaly detection on OTP and destination patterns. - Route reconciliation to surface grey routes and high-cost ranges. - Operator-direct routing removes the grey-route conduit AIT relies on. - Accurate DLRs make pumped, never-read traffic visible. **How BroadNet helps** BroadNet's OTP product (/products/myotp) ships with AIT protection on by default: per-MSISDN, per-IP and per-device rate limiting; HLR pre-validation; auto-block of MCC/MNC ranges with no historical delivery success in your account; and an AIT-detection model trained on cross-customer attack patterns. Combined with operator-direct routing, it narrows the space in which pumped traffic can hide and be monetized. - Rate limiting per MSISDN, IP and device by default. - HLR pre-validation + auto-block of no-delivery ranges. - AIT-detection model on cross-customer patterns. - Operator-direct routing + honest DLRs to expose pumped traffic. Q: Is AIT the same as SMS pumping and SMS toll fraud? A: Yes — they are different names for the same fraud. "AIT" (Artificially Inflated Traffic) is the term used in the operator/aggregator world; "SMS pumping" and "SMS toll fraud" are more common on the enterprise/developer side. The mechanism is identical. Q: Who actually profits from AIT? A: A colluding party in the termination chain — typically a rogue aggregator or an operator taking a revenue share — splits the inflated termination fees with whoever generates the bot traffic. That is why AIT concentrates on high-cost ranges and grey routes. Q: How do I know if my company is a victim? A: Watch send-to-conversion by destination. A surge in OTP or verification sends that produces no signups or logins — especially concentrated in unusual countries, with low delivery-receipt success — is the classic AIT signature. Q: Can a CAPTCHA alone stop AIT? A: It helps but is not sufficient. Sophisticated bots defeat weak CAPTCHAs, so effective defense layers CAPTCHA with rate limiting, geo/velocity controls, HLR pre-validation, number-range blocklists, and network-side firewall detection. Q: Does switching to an authenticator app or silent verification eliminate AIT? A: For those flows, largely yes — if there is no SMS to trigger, there is nothing to pump. Network-based silent verification and authenticator apps remove the pumpable SMS entirely, though many businesses still need SMS as a fallback. Q: How does operator-direct routing help against AIT? A: AIT depends on grey routes and high-cost ranges that are hard to audit, and their fabricated delivery receipts hide pumped traffic. Operator-direct routing runs traffic over sanctioned, reconciled paths with accurate handset-confirmed receipts, shrinking the space where pumped traffic can hide. ### What is smishing URL: https://www.broadnet.me/answers/what-is-smishing Last reviewed: July 22, 2026 Smishing (SMS phishing) is a fraud technique where attackers send SMS impersonating banks, government agencies, or delivery services to trick recipients into clicking malicious links, revealing credentials, or paying fake fees. Because people are conditioned to trust and act quickly on SMS from brands, smishing is highly effective. Defence is layered: operator SMS firewalls, sender-ID registration and anti-spoofing, URL reputation, and subscriber education. **Why smishing works** SMS is a trusted, high-open-rate channel, messages are short and urgent ('your parcel is held', 'confirm this transaction'), and the sender field is easy to spoof on grey routes — so a fake 'from' can mimic a real bank. The combination of trust, time-pressure, and spoofability makes smishing one of the most cost-effective attacks going. See /answers/what-is-sender-id-spoofing and /answers/what-is-grey-route-sms. **How operators fight it** The operator SMS firewall inspects content and URLs, enforces sender-ID whitelists, blocks known malicious shorteners, and shares fraud intelligence through GSMA channels. Verified-sender channels such as RCS Business Messaging remove spoofing entirely by cryptographically binding the brand to the message. See /operators/sms-firewall and /answers/what-is-rcs-business-messaging. ### What is a grey route in SMS URL: https://www.broadnet.me/answers/what-is-grey-route-sms Last reviewed: September 30, 2026 A grey route is A2P SMS traffic that bypasses the destination operator's official A2P agreement and is delivered through a path priced for P2P or other consumer-class traffic — typically a SIM box, a foreign HLR backdoor, or an undeclared aggregator interconnect. Grey routes deliver messages cheaply but unreliably, undermine operator monetization, and are aggressively blocked by SMS firewalls. **What a grey route is** SMS routes are informally graded white, grey, and black. White (operator-direct) routes are fully contracted and declared. Black routes are outright illegal. Grey routes sit between: the message is delivered, but through a path the destination operator has not sanctioned for that traffic type — most commonly A2P enterprise traffic pushed through P2P agreements or SIM farms to avoid A2P termination charges. The route works until an SMS firewall detects and blocks it, which is why grey-route delivery is inconsistent and deteriorates over time. - White: contracted, declared operator-direct A2P termination. - Grey: functional but unsanctioned — usually A2P sent as P2P. - Black: outright illegal delivery. - Grey delivery degrades as operators deploy SMS firewalls. **Why grey routes exist** Because the price gap between consumer P2P SMS and wholesale A2P SMS is large enough — often 3-10x — that opportunistic aggregators can underprice the legitimate market and still make a margin. Globally, grey-route A2P represents an estimated USD 5-15 billion per year in displaced operator revenue. **Why they fail** Three structural reasons. SMS firewalls catch the behavioural fingerprint (high-throughput one-way SMS from consumer SIMs) within hours-to-days. Operators classify the routes and selectively block. Sender-ID enforcement fails on grey routes because the carrying SIM has no registered alphanumeric overlay capability — your messages start arriving with the originating SIM's MSISDN instead of your brand. **How to tell if you're on one** Three signals. Your aggregator's quoted price for a country is more than 40% below the next-cheapest reputable aggregator. DLR success rates oscillate (high one week, very low the next as firewalls catch the route and the aggregator re-routes). DLR error codes are generic (UNKNOWN, 0x000000FF) instead of operator-specific MSC reasons. Run a test campaign and audit the DLR feed. **Delivery-receipt accuracy** Delivery receipts (DLRs) are the feedback loop enterprises rely on to confirm a message reached the handset. Grey routes frequently return fabricated DLRs — reporting "delivered" for messages that were never received — which corrupts analytics, masks failures, and, critically, hides AIT. Operator-direct routes return genuine, handset-confirmed DLRs, so send-to-delivery and send-to-conversion metrics are trustworthy. - Grey: fabricated "delivered" DLRs that mask failures and fraud. - Operator-direct: genuine handset-confirmed DLRs. - Accurate DLRs underpin both analytics and AIT detection. **Compliance and legal exposure** Grey routes routinely breach local telecom regulation, sender-ID registration rules, and consent/data-protection obligations, exposing the brand and its provider to blocking, fines, and reputational damage. Operator-direct routes are declared and contracted, aligning with regulatory frameworks and giving a clean audit trail. As more regulators mandate registration and anti-spam controls, the compliance gap between grey and direct widens. - Grey: breaches registration, consent, and interconnect rules. - Operator-direct: declared, contracted, auditable, regulator-aligned. - Tightening registration/anti-spam rules make grey routes a growing liability. **What to do about it** Switch to a direct-A2P aggregator. The unit price will be higher; the effective cost-per-delivered-message will usually be lower once you account for re-sends, sender-ID degradation, and customer-experience cost of failed messages. BroadNet operates on direct A2P agreements only — see /operators for the route list. Q: What exactly makes a route "grey"? A: A grey route delivers messages through a path the destination operator has not sanctioned for that traffic type — most often A2P enterprise traffic disguised as P2P to avoid A2P termination fees. It works technically but violates commercial and often regulatory terms. Q: Are grey routes illegal? A: They occupy a legal grey zone rather than being outright illegal like "black" routes, but they typically breach interconnect agreements, sender-ID registration, and consent rules — so using them carries real regulatory and contractual risk. Q: How do I tell whether my provider is using grey routes? A: Warning signs include unusually low pricing, sender IDs arriving stripped or replaced, inconsistent delivery, and delivery receipts that report success while users never receive messages. Genuine, handset-confirmed DLRs and preserved sender IDs point to operator-direct routing. Q: Is operator-direct routing always worth the higher price? A: For OTP, transactional, and security-critical traffic, almost always — the cost of a failed authentication, a stripped brand ID, a compliance fine, or AIT losses dwarfs the per-message premium. For very low-value bulk traffic the trade-off is closer, but the risks remain. Q: How do grey routes relate to AIT and SS7 attacks? A: Grey routes are the preferred conduit for AIT because they are hard to audit and reconcile, and their fabricated DLRs hide pumped traffic. They also correlate with weaker overall messaging security. Operator-direct routing removes that conduit and restores visibility. ### What is A2P monetization URL: https://www.broadnet.me/answers/what-is-a2p-monetization Last reviewed: October 1, 2026 A2P monetization is the operator-side discipline of capturing wholesale revenue from application-to-person SMS traffic that would otherwise be delivered grey or peer-to-peer. It is one of the largest single SMS revenue streams for tier-1 operators globally — the A2P SMS market is worth USD 75-95 billion per year, and operators capture an increasing share through firewalls, direct agreements, and IR.71-aligned commercial frameworks. **The leakage problem** Before A2P monetization programmes, operators typically captured only part of the A2P revenue that should have flowed to them. The rest leaked through grey routes (SIM boxes, foreign HLR abuse), through P2P-impersonating traffic, and through interconnect partners who undeclared A2P share. Closing this gap is the core economic motivation for every SMS firewall deployment. **The three components** Detection (firewall classifies inbound SMS as A2P or P2P based on content, source, behavioural patterns). Enforcement (block, throttle, or whitelist-only — depending on policy). Commercial onboarding (the aggregators caught delivering grey-route A2P are offered an A2P agreement at the wholesale rate; either they accept and become a paying partner, or their traffic is permanently blocked). The third step is what converts firewall detection into recurring revenue. **How much revenue comes back** It depends on the network: how much A2P traffic was arriving grey beforehand, and how disciplined the enforcement is. BroadNet does not publish a benchmark figure — the operator assessment measures the grey-route volume on your own traffic, in mirror mode, before anything is enforced, and the business case is built from that measurement. **What operators should look for** A firewall vendor that also operates the commercial side — i.e. doesn't just detect grey traffic but actively onboards the offending aggregators into a legitimate agreement. BroadNet runs both products: the firewall and the A2P monetization desk. The combination is what closes the leak, not just measures it. ### How does A2P messaging monetization work URL: https://www.broadnet.me/answers/messaging-monetization Last reviewed: October 1, 2026 Messaging monetization is how a mobile operator captures the revenue in application-to-person traffic — deploying an SMS firewall to force grey-route traffic onto paid A2P routes, running a sender-ID registry so only licensed brands can send, and billing A2P at its true wholesale value. **How A2P monetization works** Most operators historically terminated large volumes of enterprise A2P SMS as if it were free consumer P2P, because it arrived over grey routes and consumer SIMs. Monetization closes that leak: a firewall classifies every inbound message, blocks the traffic that bypasses the A2P agreement, and forces senders onto the operator's paid, declared route — where it is billed at the A2P wholesale rate. The firewall is the enforcement point; the commercial framework is the A2P agreement. See /operators/a2p-monetization and /answers/what-is-a2p-monetization. **The building blocks** Four pieces: an SMS firewall to classify and enforce; a sender-ID registry so only approved brands and alphanumeric IDs can send; GSMA IR.71-aligned interconnect agreements defining the commercial terms; and billing/settlement to invoice the recovered traffic. Remove any one and revenue leaks — a firewall with no registry cannot tell a licensed brand from a spoofer. See /answers/what-is-sms-firewall and /answers/gsma-ir71-explained. **The sender-ID registry — why it matters** A sender-ID registry is the whitelist of who is allowed to send under which alphanumeric or short-code identity in a market. It underpins both monetization and security: only registered senders get delivery, so grey traffic and spoofed brands are denied, and each delivered message maps to a billable, accountable sender. Many regulators now mandate one. See /operators/sender-id-registry, /answers/what-is-sender-id, and /answers/what-is-verified-sender. **Benefits: revenue recovery and protection** The headline is revenue: GSMA IR.71-aligned enforcement recovers previously leaked A2P revenue by moving grey traffic onto paid routes. Alongside it, the same controls protect subscribers from smishing and spoofing, satisfy regulator and GSMA compliance obligations, and produce the tamper-evident audit trail those regulators expect. Monetization and fraud prevention are the same control viewed from two angles. See /answers/telecom-fraud-prevention. **Limitations and operational realities** Enforcement is a tuning problem — too aggressive and you block legitimate brands and anger enterprise customers; too loose and revenue leaks back out. It needs fresh grey-route reputation feeds, an actively maintained registry, and regulator alignment on sender-ID rules. And it only covers SMS: A2P value migrating to WhatsApp and RCS has to be monetized on those channels separately. See /answers/what-is-grey-route-sms and /answers/what-is-ott-bypass. **How much revenue does A2P monetization recover?** How much comes back depends on how much traffic was arriving grey before a firewall and sender-ID registry are enforced, and on how disciplined the enforcement is — BroadNet does not publish a benchmark figure, and the operator assessment measures it on your own traffic. The gain is recurring, not one-off, because the firewall keeps grey traffic off the network continuously. BroadNet delivers the firewall, registry, and SMSC gateway that make it work. See /operators/sms-firewall and /operators/smsc-gateway. ### What is SMPP URL: https://www.broadnet.me/answers/what-is-smpp Last reviewed: July 20, 2026 SMPP (Short Message Peer-to-Peer) is the open-protocol standard for exchanging SMS between SMSCs, ESMEs (External Short Message Entities), and aggregators. Version 3.4 is the most widely deployed; 5.0 adds Unicode-clean headers. BroadNet supports both via plain TCP and TLS. ### How does the SMPP protocol work URL: https://www.broadnet.me/answers/smpp-protocol Last reviewed: October 2, 2026 SMPP (Short Message Peer-to-Peer) is the open TCP protocol that carries A2P SMS between an application — the ESME — and a mobile operator's SMSC. The ESME opens a persistent bind, submits messages as binary submit_sm PDUs, and receives delivery receipts back over the same socket. Version 3.4 (1999) runs almost every commercial A2P bind today; 5.0 exists but is rarely deployed. SMPP is the high-throughput alternative to a REST SMS API. **How SMPP works, step by step** The ESME opens a TCP (ideally TLS) connection and sends bind_transceiver with a system_id and password. Once bound, it submits each message as a submit_sm PDU; the SMSC acknowledges with a submit_sm_resp carrying a message_id. Delivery receipts arrive asynchronously as deliver_sm PDUs on the same socket, matched back by message_id. An enquire_link heartbeat every 30 seconds keeps the session alive, and unbind closes it cleanly. See /answers/what-is-smpp and /answers/what-is-esme. **Bind types and versions** An ESME binds as Transmitter (send-only), Receiver (receive-only), or Transceiver (both on one connection). Transceiver over SMPP 3.4 is the modern default. SMPP 5.0 added Unicode-clean headers and cell-broadcast support but almost nobody deployed it — the install base is overwhelmingly 3.4. BroadNet accepts SMPP 3.4 binds; the host, port and credentials are provided with your test access. See /answers/smpp-3-4-vs-5-0. **Benefits over a REST API** A persistent bind costs nothing per message once established, so at sustained volume SMPP uses roughly a tenth of the CPU and a quarter of the bandwidth of per-request HTTPS. It is the only way to reach sub-100ms p99 latency to an SMSC — there is no HTTP handshake on the critical path — and it streams DLRs back in real time. See /compare/sms-api-vs-smpp. **Limitations and gotchas** SMPP is a binary protocol you must operate: bind management, reconnect with exponential backoff, sequence-number tracking, and DLR matching by message_id (returned as hex on some SMSCs, decimal on others) are all on you. Error handling is terse — a failed submit returns a numeric command_status you must decode. Use the /tools/smpp-error-codes lookup to turn those codes into an action. A production-grade SMPP client is a multi-thousand-line codebase; buy one rather than build one. **When should you choose SMPP over REST?** Choose SMPP when you sustain several hundred messages per second or need persistent binds (capacity per bind is agreed with your account team), run latency-critical OTP where every millisecond counts, or integrate into an operator/aggregator ecosystem that already speaks SMPP everywhere. Otherwise a REST SMS API (no fixed per-account rate limit at BroadNet) is simpler to run and delivers over the identical routes. See /developers/smpp and /products/sms-api. **What port does SMPP use, and is it still used in 2026?** SMPP has no single reserved port; 2775 is the historical plaintext default and operators commonly expose TLS on a dedicated port (BroadNet provides its TLS port with your account). And yes — SMPP is thoroughly current: it is the protocol pinned at the top of virtually every A2P interconnect contract, and BroadNet runs over 1,000 active binds behind 1,000+ operator connections, carrying 300M+ messages a day at 99.99% uptime since 2003. ### What is an SMSC URL: https://www.broadnet.me/answers/what-is-smsc Last reviewed: May 26, 2026 An SMSC (Short Message Service Center) is the core infrastructure component of a mobile network that stores, forwards, and delivers SMS messages between mobile devices and external applications. Every SMS — A2P, P2P, MO, MT — passes through an SMSC. ### How does SIGTRAN (SS7 over IP) work URL: https://www.broadnet.me/answers/sigtran-explained Last reviewed: August 8, 2026 SIGTRAN is the IETF family of protocols that carries legacy SS7 signaling over IP networks instead of dedicated TDM links. It uses SCTP as a reliable, multi-homed transport and adaptation layers such as M3UA and M2PA to present SS7's MTP interface to IP — letting operators run SS7/MAP interconnects, SMS delivery, and HLR queries across modern packet networks without changing the applications on top. **How SIGTRAN works, layer by layer** SIGTRAN keeps the SS7 application stack — MAP over TCAP over SCCP — completely unchanged and swaps out only the bottom transport. Where classic SS7 used MTP1/MTP2/MTP3 over TDM timeslots, SIGTRAN runs SCTP over IP and inserts an adaptation layer that emulates the MTP service the upper layers expect. An SMSC, HLR, or firewall speaks exactly the same MAP it always did; it just reaches its peer over an IP association instead of a 64 kbit/s link. See /answers/what-is-sigtran and /answers/sigtran-adaptation-layers. **SCTP: the transport underneath** SIGTRAN does not use TCP. It uses SCTP (Stream Control Transmission Protocol, RFC 4960) because signaling needs three things TCP lacks: it is message-oriented rather than byte-stream, it multiplexes several independent streams to avoid head-of-line blocking, and it is multi-homed — an association can span two IP paths and fail over instantly if one drops. Those are exactly the resilience properties a carrier control plane requires. See /answers/what-is-sctp. **The adaptation layers: M3UA, M2PA, M2UA, SUA** The adaptation layer decides which MTP boundary is emulated. M3UA presents the MTP3 service to SCCP users and is what most operators run to reach SS7/MAP peers today. M2PA links two signaling points as if by an MTP2 link (for IP-based STPs). M2UA backhauls raw MTP2 from a media gateway to a signaling gateway. SUA carries SCCP users directly over SCTP. See /answers/what-is-m3ua and /answers/what-is-sccp. **Benefits over TDM SS7** Far higher bandwidth per association than a 56/64 kbit/s TDM link, cheaper commodity IP transport, built-in multi-homed failover from SCTP, and simpler scaling — you add capacity by adding associations, not by cabling more E1/T1 links. SIGTRAN is why an SMSC gateway can front thousands of SMPP binds and still reach the SS7 world at volume. See /operators/smsc-gateway. **Limitations and the security implication** Moving SS7 onto IP inherits IP's exposure: a signaling endpoint reachable over IP is reachable by anyone who can route to it, so SIGTRAN interconnects widened the SS7 attack surface that GSMA FS.07/FS.11 were written to close. SCTP is also less widely supported by commodity firewalls and NAT than TCP, so associations need careful network design. The mitigation is a signaling firewall inspecting the MAP riding on top. See /operators/ss7-firewall and /answers/gsma-fs07-fs11-signaling-firewall. **Is SIGTRAN the same as SS7?** No — SIGTRAN is not a replacement for SS7, it is a transport for it. The SS7 application protocols (MAP, CAP, ISUP, TCAP, SCCP) are identical; SIGTRAN only carries them over IP instead of TDM. So an SMS delivered over a SIGTRAN link is still an SS7 MAP MT-ForwardSM — which is why an SS7 firewall inspects SIGTRAN and TDM traffic the same way. BroadNet runs SIGTRAN-based interconnects behind 1,000+ operator connections. See /answers/ss7-map-explained. ### SIGTRAN — SS7 over IP explained URL: https://www.broadnet.me/answers/what-is-sigtran Last reviewed: May 28, 2026 SIGTRAN is the IETF/3GPP family of protocols that transports SS7 signalling over IP networks (typically over SCTP, not TCP, for ordered multi-streamed reliable delivery). It replaced the dedicated TDM/E1 SS7 links that operators used to lease at huge cost, letting SS7 ride the same IP backbone as everything else. Almost every operator-to-operator SS7 link in 2026 is in fact SIGTRAN underneath. **What it actually does** SIGTRAN preserves the SS7 application protocols (MAP, CAP, ISUP, TCAP, SCCP) and replaces only the lower transport layers. Where classic SS7 used MTP1/2/3 over E1 links, SIGTRAN uses adaptation layers (M2PA, M2UA, M3UA, SUA) over SCTP over IP. From the application's perspective — an HLR, an SMSC, an MSC — nothing changes. From the network's perspective, everything changes: signalling now rides leased lines, MPLS, or even the public internet (typically with IPsec). **Why it matters commercially** SIGTRAN is why a new operator can get signalling connectivity in days instead of months. Provisioning a SIGTRAN association requires IP transit and an STP peer agreement; provisioning an old-school SS7 link required physical E1 circuits, line drivers, and a months-long telco install. SIGTRAN reduced SS7 transport cost by an order of magnitude, which is why SS7 message volumes per operator grew 10-100x between 2005 and 2015 — and why SS7 firewalls became a necessity. BroadNet operates SIGTRAN STPs in MENA data centres for SS7 interconnect (/operators/ss7-firewall) and global signalling reach. **Latency, scale, and compliance angle** SIGTRAN latency over a dedicated fibre IP path is comparable to TDM SS7 (single-digit ms within a country, 50-150 ms intercontinental). SCTP's multi-homing means a SIGTRAN association can survive a single ISP failure without dropping signalling. Scale: a single SIGTRAN association can carry tens of thousands of MAP messages per second. Compliance: GSMA FS.07/FS.11 (/answers/gsma-fs07-fs11-signaling-firewall) apply to SIGTRAN exactly as they applied to classic SS7. **Privacy and compliance considerations** SIGTRAN over the public internet without IPsec is a privacy risk — SS7 signalling contains IMSI, MSISDN, location, and routing data that should not be exposed. Modern operators wrap SIGTRAN in IPsec tunnels between peer STPs, or use private MPLS. Cross-border SIGTRAN traffic between operators is in scope for the data-export rules of both jurisdictions (EU GDPR Schrems II, KSA PDPL cross-border transfer rules). Mature operators document each SIGTRAN peer relationship and the legal basis for the data flow. ### How does programmable voice work URL: https://www.broadnet.me/answers/programmable-voice Last reviewed: July 22, 2026 Programmable voice is a cloud API that lets applications place, receive, and control phone calls in code — building IVR menus, click-to-call, call tracking, and voice OTP without owning telephony hardware. Calls terminate to any PSTN or mobile number over the same carrier interconnects that carry SMS, and the call flow is driven in real time by API callbacks as the call progresses. **How a programmable voice API works** Your application makes a REST call (or answers an inbound call) and the platform sets up the call over SIP to the PSTN and mobile networks. As the call progresses — ringing, answered, digit pressed, hung up — the platform posts webhooks back to your app, and you respond with instructions to play audio, gather input, record, or bridge. It's the voice equivalent of an SMS API. See /products/voice and /products/voice. **The core building blocks** DID numbers to receive inbound calls; IVR to play prompts and gather DTMF or speech; text-to-speech and speech recognition for dynamic audio; call recording and transcription; and conferencing/bridging to connect callers to agents. Each is exposed as an API primitive you compose into a flow. See /answers/what-is-did and /answers/what-is-ivr. **Voice OTP and its trade-offs** Voice OTP places an automated call that reads a one-time code aloud — useful as a fallback when SMS OTP fails, for landlines, or where a market is being SMS-pumped. It reaches numbers SMS can't and is harder to intercept silently, but costs more per attempt and takes longer to complete than an SMS. Robust verification fails over between SMS, voice, and flash call. See /answers/what-is-otp and /answers/what-is-flash-call-verification. **The metrics that matter: ASR, ACD, and PDD** Answer-Seizure Ratio (ASR) measures the share of call attempts that connect; Average Call Duration (ACD) measures how long answered calls last; and Post-Dial Delay (PDD) measures how long callers wait before ringing. Together they reveal route quality — low ASR or high PDD signals a poor carrier path. Size trunks and agents with the /tools/erlang-calculator. See /answers/what-is-asr, /answers/what-is-acd, and /answers/what-is-pdd. **Benefits of building on a voice API** No telephony hardware or carrier contracts to manage, global reach through one interconnect, pay-per-use billing, and the ability to change call flows in code rather than reprogramming a PBX. It puts inbound and outbound voice on the same developer footing as SMS and WhatsApp. See /products/voice. **Limitations and things to plan for** Voice is rate-limited by calls per second (CPS) and concurrent-channel capacity, so bursts must be paced; regulations (DNC lists, caller-ID/CLI rules, STIR/SHAKEN in North America) constrain outbound dialing; and per-minute economics differ sharply from per-message SMS. Model concurrency and CPS before a large campaign. See /answers/what-is-cps and /answers/what-is-dnc. ### How does a voice API and SIP trunking work URL: https://www.broadnet.me/answers/voice-api-sip-trunking Last reviewed: August 8, 2026 A voice API and SIP trunking give applications programmable access to the telephone network over IP. SIP trunking replaces physical phone lines with SIP sessions that carry calls to and from the PSTN and mobile networks; a voice API layers a REST and webhook control surface on top, so software can place, receive, and steer calls in code across 200+ countries. **How it works, end to end** A SIP trunk is a virtual connection that sets up calls with SIP signaling and streams the audio as RTP media. Your PBX, softswitch, or application registers to the trunk; when a call is placed, SIP negotiates the session (via an SDP offer/answer) and RTP carries the voice. A voice API wraps this so an HTTPS request starts a call and webhooks drive the flow as it progresses. See /answers/what-is-sip, /answers/what-is-rtp, and /products/voice. **SIP trunking vs a programmable voice API** A SIP trunk is raw connectivity — you bring your own PBX or softswitch and speak SIP directly, ideal for contact centres and carriers moving high call volumes. A programmable voice API abstracts SIP entirely behind REST and webhooks, ideal for developers adding click-to-call, IVR, or voice OTP without running telephony infrastructure. Most platforms, BroadNet included, offer both. See /answers/programmable-voice and /products/voice. **The building blocks** DID numbers for inbound calls; PSTN and mobile termination for outbound; concurrent-channel capacity (how many calls run at once) and a calls-per-second cap that pace bursts; a Session Border Controller policing the SIP edge; and codecs (G.711, Opus) encoding the audio. Each is provisioned per account and composed into a call flow. See /answers/what-is-did, /answers/what-is-sbc, and /answers/what-is-voice-codec. **Benefits over legacy PRI lines** No physical circuits to install, capacity that scales by adding sessions rather than cabling, one interconnect for 200+ countries, pay-per-use billing, and call flows changed in code instead of reprogramming a PBX. SIP trunking also consolidates inbound and outbound onto the same IP path, cutting cost and simplifying failover. See /products/voice and /tools/erlang-calculator. **Limitations and what to plan for** Voice over IP is sensitive to network quality — jitter, packet loss, and latency degrade call audio, so trunks need QoS and monitoring. NAT and firewall traversal must be handled at the SIP edge, capacity is bounded by concurrent channels and calls per second, and outbound dialing is constrained by caller-ID (CLI/STIR-SHAKEN) and Do-Not-Call rules. See /answers/voip-quality, /answers/what-is-nat-traversal, and /answers/what-is-cps. **Is a SIP trunk the same as a voice API?** No. A SIP trunk is the connectivity layer — it carries calls between your telephony system and the network using SIP and RTP. A voice API is a developer control layer on top that lets code place and manage calls without speaking SIP at all. You can use a SIP trunk without an API, but a modern programmable voice service gives you both. BroadNet delivers voice connectivity across 1,000+ operator connections at 99.99% uptime. See /products/voice. ### What determines VoIP call quality URL: https://www.broadnet.me/answers/voip-quality Last reviewed: July 22, 2026 VoIP call quality is decided by four network impairments — latency, jitter, packet loss, and the codec — summarised by a single Mean Opinion Score (MOS). Because voice is carried as RTP packets over IP, delayed, out-of-order, or dropped packets degrade the audio the listener hears. Managing these with QoS, jitter buffers, and the right codec is what keeps calls clear at scale. **How VoIP quality is measured: MOS** Mean Opinion Score (MOS) rates call quality from 1 (bad) to 5 (excellent); 4.0+ is toll quality, below 3.5 is noticeably degraded. Originally a human listening test, MOS is now estimated automatically (per ITU-T models) from measured latency, jitter, and packet loss. It is the single number carriers and platforms track to compare routes and diagnose a bad call path. See /answers/what-is-mos. **The impairments that lower quality** Latency (one-way delay above ~150ms makes conversation feel like a walkie-talkie); jitter (variation in packet arrival that garbles audio unless a jitter buffer smooths it); and packet loss (missing RTP packets heard as clipping or dropouts — above ~1% is audible). These accumulate across every hop, which is why direct, well-provisioned routes sound better than long ones. See /answers/what-is-jitter and /answers/what-is-rtp. **Codecs and the quality-vs-bandwidth trade-off** The codec sets the ceiling. G.711 is uncompressed toll-quality at ~64 kbit/s; Opus adapts bitrate and is resilient to loss; low-bitrate codecs save bandwidth but cap MOS. Transcoding between codecs along the path costs quality and adds delay, so matching codecs end to end matters. See /answers/what-is-voice-codec and /answers/what-is-sip. **How to protect quality** Prioritise voice with QoS/DiffServ so RTP is not queued behind bulk data; size jitter buffers to trade a little delay for smoother audio; pick loss-resilient codecs like Opus on lossy paths; and choose direct routes with few hops. Continuous MOS, ASR, and PDD monitoring surfaces a degrading route before customers complain. See /answers/what-is-asr, /answers/what-is-pdd, and /products/voice. **Where poor quality actually comes from** Most bad VoIP is not the codec — it is the network path. Grey or over-hopped wholesale voice routes add latency and loss at each transit carrier, congested access links starve RTP of bandwidth, and unmanaged Wi-Fi introduces jitter. Diagnosing quality means correlating MOS with the route and the KPIs (ASR, ACD, PDD) that reveal a weak carrier leg. See /answers/programmable-voice and /platforms/signaling-cdr. **What is a good MOS score for VoIP?** A MOS of 4.0 or above is considered toll quality — indistinguishable from a landline to most listeners. 3.5-4.0 is acceptable, 3.0-3.5 is noticeably degraded, and below 3.0 frustrates callers. G.711 on a clean path tops out near 4.4; the goal of QoS, jitter buffers, and direct routing is to keep the delivered MOS as close to that ceiling as the network allows. See /answers/what-is-mos and /products/voice. ### What is SIP (Session Initiation Protocol) URL: https://www.broadnet.me/answers/what-is-sip Last reviewed: July 22, 2026 SIP (Session Initiation Protocol, RFC 3261) is the signaling protocol that sets up, modifies, and tears down real-time voice and video sessions over IP. It handles the call control — inviting, ringing, answering, and hanging up — while the actual audio travels separately as RTP media negotiated through an SDP offer/answer inside the SIP messages. SIP is the backbone of VoIP, SIP trunking, and programmable voice. See /answers/what-is-rtp, /answers/what-is-sdp, and /answers/voice-api-sip-trunking. ### How does HLR lookup and MNP number intelligence work URL: https://www.broadnet.me/answers/hlr-mnp-number-intelligence Last reviewed: July 22, 2026 HLR lookup and MNP (mobile number portability) intelligence is real-time number validation that queries the Home Location Register over SS7 to confirm whether a number is active, which operator currently owns it after any porting, and whether it is roaming — all before you send. It removes invalid numbers, corrects routing for ported numbers, and cuts wasted A2P spend and fraud exposure. **How an HLR lookup works** The lookup sends an SS7 MAP SendRoutingInfoForSM query to the number's home HLR, exactly as an SMSC would before delivering a message. The HLR responds with the subscriber's status, the current serving network (MCC/MNC), and the IMSI — revealing whether the number is live and reachable without ever sending an SMS. See /answers/what-is-hlr and /answers/ss7-map-explained. **What MNP (number portability) changes** Number portability lets a subscriber keep their MSISDN when they switch operator, so the dial-code prefix no longer reliably identifies the carrier. An HLR/MNP lookup returns the operator that actually owns the number today — essential for routing A2P traffic to the correct interconnect and pricing it correctly. See /answers/what-is-mnp and /answers/what-is-msisdn. **What the response tells you** A typical result flags the number as active, absent, or invalid; returns the current MCC/MNC (network); indicates whether the subscriber is roaming; and shows a ported flag when the number has moved networks. That's the raw material for list hygiene, least-cost routing, and pre-send validation. See /products/hlr-lookup. **Benefits: deliverability, cost, and fraud screening** Scrubbing a list against HLR before a campaign lifts delivery rates by dropping dead numbers, routes ported numbers correctly, and reduces spend on undeliverable sends. It's also a front-line control against artificially inflated traffic (AIT/SMS pumping) — validating numbers before OTP sends stops bots draining your budget. See /answers/what-is-ait and /answers/what-is-sms-pumping. **Limitations to be aware of** Some operators restrict or obscure HLR responses for privacy, so coverage and field completeness vary by country. On 4G/5G cores the HSS (and 5G UDM) replaces the HLR, though the lookup service abstracts that difference. And a lookup is a point-in-time snapshot — status can change between validation and send. See /answers/what-is-hss and /answers/what-is-hlr-lookup. **HLR lookup vs a simple number-format check** A format check (E.164 validation) only confirms a number is well-formed — it can't tell you if the number is real, active, or which network owns it after porting. An HLR lookup queries the live network, so it catches disconnected numbers, corrects ported routing, and screens fraud that format validation misses. Use both: normalise to E.164, then validate against the HLR. See /answers/what-is-e164. ### What is HLR Lookup URL: https://www.broadnet.me/answers/what-is-hlr-lookup Last reviewed: September 24, 2026 An HLR (Home Location Register) lookup is a real-time query against a mobile operator's subscriber database that returns whether a number is active, who owns it today (the original operator if ported, the current operator if not), what country it terminates in, and whether the subscriber is currently roaming. It is the single most useful number-quality check before sending an SMS. **What the lookup actually does** An HLR Lookup request triggers an SS7 MAP-SRI-FOR-SM (or a SIP/IMS-equivalent on 5G) toward the recipient's home network. The response carries the IMSI, the serving MSC address, and the current MNC/MCC (which reveals roaming). It does not reveal the subscriber's location beyond country/operator granularity, and it does not deliver a message — it is the lookup step the SMSC would perform anyway, exposed as a standalone API. **Why it matters commercially** Three reasons. You stop paying SMS fees on dead numbers (typically 8–18% of a stale marketing list). You route around ported numbers correctly — sending to a number's original operator when it has ported costs 40–60% more on some routes and increases failure rates. You catch numbers that are roaming and decide whether to charge the international rate or hold the send. **Latency and limits** BroadNet's HLR Lookup API answers in about 350ms for a live query and under 50ms from cache, across 200+ countries, with batch endpoints for the once-a-week list scrub and a streaming endpoint for the before-every-send-OTP pattern. There is no fixed per-account lookup rate limit; throughput is sized to your traffic. See /products/hlr-lookup for the full spec. **Privacy and compliance** HLR Lookup is regulated. In the EU under GDPR, an HLR query against a subscriber number is treated as personal data processing — you need a lawful basis. In KSA under PDPL 2023, MSISDN-level queries are also in scope. BroadNet's HLR Lookup endpoint logs only the hash of the queried number by default, with optional full-trace for customers in fraud-prevention use cases that have legal basis. ### How does number verification (OTP and 2FA) work URL: https://www.broadnet.me/answers/number-verification Last reviewed: September 24, 2026 Number verification confirms that a user actually controls a given phone number — the core of OTP and two-factor authentication. It spans SMS OTP, voice OTP, WhatsApp OTP, flash-call verification, and silent network authentication (a data-session check against the operator with no code to type). Coverage, deliverability, latency, and anti-fraud screening decide which method fits which market. **How number verification works** The classic flow: your app requests a one-time passcode, the platform generates it and delivers it to the number over a channel (SMS, voice, WhatsApp), and the user types it back to prove possession. Newer methods skip the code entirely — flash call verification reads the passcode from an unanswered call's caller ID, and silent network authentication verifies the SIM against the operator over a data session invisibly. See /products/otp, /products/myotp, and /answers/what-is-otp. **The verification methods** SMS OTP (universal reach, most common); voice OTP (reaches landlines and SMS-degraded markets, read aloud); WhatsApp OTP (rich, cheap where the app is installed); flash call (fast, cheap, no message body, Android-friendly); and silent network authentication (zero user friction, strongest against interception). A robust verification service fails over between them by country and delivery result. See /answers/what-is-2fa and /answers/what-is-flash-call-verification. **Silent network authentication and GSMA Open Gateway** Silent network authentication (SNA) opens a data connection that the mobile operator authenticates against the SIM, confirming possession of the number with nothing for the user to type and nothing an attacker can phish or intercept. It is exposed through GSMA Open Gateway and the CAMARA Number Verification API, and it is the lowest-friction, highest-assurance option where operator coverage exists. See /answers/silent-network-authentication and /answers/gsma-open-gateway. **The fraud problem: AIT and SMS pumping** OTP traffic is the prime target for artificially inflated traffic (AIT), also called SMS pumping: fraudsters trigger floods of OTP sends to premium-rate number ranges they profit from, draining your verification budget. Defences include pre-send HLR/number-range validation, per-number and per-IP rate limits, and shifting high-risk geographies to flash call or silent auth. See /answers/what-is-ait and /answers/what-is-sms-pumping. **Benefits and choosing a method** Number verification stops account takeover, bot signups, and payment fraud while proving a reachable, real customer. Choose by market: SMS for universal reach, silent auth or flash call to cut cost and friction where covered, voice as a fallback, and always validate numbers first to blunt AIT. BroadNet's verification stack routes across all of these. See /products/hlr-lookup and /operators/flash-call. **Which number verification method is most secure?** Silent network authentication is the strongest: because it checks the SIM against the operator over the data plane, there is no code to phish, intercept over SS7, or social-engineer out of a user. Flash call is next. Plain SMS OTP is the most universal but the most attackable, so pair it with number validation and rate limits. The practical answer is a policy that fails over between methods by risk and coverage. See /answers/what-is-2fa. ### What is Flash Call verification URL: https://www.broadnet.me/answers/what-is-flash-call-verification Last reviewed: May 27, 2026 Flash Call is a number-verification technique that places a missed call to the user's phone with a one-time short MSISDN as the caller-ID. The user's app reads the last 4-6 digits of the incoming caller-ID — that is the OTP — and the call is hung up before it rings. The user sees nothing; the verification completes silently. It is faster, cheaper, and harder to spoof than SMS OTP. **How it works end-to-end** Your app calls our /verify/start with a phone number and method=flashcall. We dial the number from a single-use MSISDN whose last digits encode the OTP. The Android CALL_LOG permission lets your app read the incoming caller-ID; it strips the last 4-6 digits, hashes them, and POSTs to /verify/check. If the hash matches, the user is verified. End-to-end: 3-5 seconds. Cost: 30-60% of SMS OTP. **Why operators love it** Flash Call doesn't touch the SMSC, doesn't consume a billable SMS event, and doesn't burn an A2P trunk. It is a single CAMEL/SIP call setup that gets cancelled before connect — most operators treat it as an unanswered call (free or near-free). For high-volume OTP services in markets where SMS A2P pricing is punishing (India, Indonesia, Brazil), Flash Call drops verification cost dramatically. **Where it doesn't work** iOS apps cannot read incoming caller-ID programmatically. Flash Call is Android-only (and only via the user granting CALL_LOG, which Google has been increasingly restrictive about — Android 11+ requires the app to be the default Caller ID app or use SMS_RETRIEVER as a fallback). Always pair Flash Call with an SMS-OTP fallback. BroadNet's /products/myotp service auto-falls-back from Flash Call → SMS OTP → WhatsApp OTP → Voice OTP in a single API call. **Regulatory state** GSMA published RCC.20 guidelines for Flash Call in 2022, treating it as a legitimate verification technique. Some operators (parts of India, the UAE) have started classifying it as A2P and applying A2P pricing; others (most of MENA, EU) still treat it as a voice event. Pricing varies accordingly. We track per-country classification and price accordingly. ### What is a sender ID URL: https://www.broadnet.me/answers/what-is-sender-id Last reviewed: July 22, 2026 A sender ID is the 'from' identity a recipient sees on an A2P SMS. It can be an alphanumeric string (up to 11 GSM-7 characters, typically a brand name), a numeric long code, or a short code. Alphanumeric sender IDs let brands show a recognisable name instead of a number, but most countries require them to be pre-registered with the regulator or operator before traffic will deliver. **Alphanumeric vs numeric vs short code** Alphanumeric IDs are one-way (the recipient can't reply) and ideal for OTPs and notifications. Long codes are two-way and support conversational replies. Short codes offer the highest throughput for large campaigns. Some markets — notably the United States — do not allow alphanumeric IDs at all and require 10DLC, toll-free, or short codes instead. See /answers/what-is-short-code-vs-long-code. **Registration and spoofing** Sender-ID registration is per country and often per operator; unregistered IDs are dropped by the operator's SMS firewall. Because the SMS 'from' field is trivially spoofable on grey routes, sender-ID spoofing is a common smishing vector — defended by firewalls, registration enforcement, and verified-sender channels like RCS Business Messaging. See /answers/sender-id-registration-uae-tdra and /answers/what-is-sender-id-spoofing. ### What is a verified sender URL: https://www.broadnet.me/answers/what-is-verified-sender Last reviewed: July 22, 2026 A verified sender is a business messaging identity that a channel has authenticated and bound to a real brand — an RCS/RBM verified agent with logo and checkmark, a verified WhatsApp Business, or a registered SMS sender ID. Verification proves the message genuinely comes from the brand, closing the sender-ID spoofing gap that makes unauthenticated SMS a smishing vector. It is central to both trust and A2P monetization. See /answers/rcs-business-messaging, /answers/what-is-sender-id-spoofing, and /answers/what-is-smishing. ### How does omnichannel messaging work URL: https://www.broadnet.me/answers/omnichannel-messaging Last reviewed: July 22, 2026 Omnichannel messaging reaches a customer across SMS, WhatsApp, RCS, voice, and email through one API and one conversation thread — automatically choosing or failing over between channels by reach, cost, and delivery result. Instead of integrating each channel separately, a business sends to a customer and the platform selects the best route, so the conversation stays continuous no matter which channel actually delivers. **How omnichannel messaging works** You send a message to a customer through a single API; the platform resolves which channels the recipient can receive, applies your priority and cost rules, and delivers over the best one — falling back automatically if it isn't delivered. A unified thread stitches replies from every channel into one conversation, so an SMS OTP, a WhatsApp reply, and an email receipt all belong to the same customer record. See /products/omnichannel and /answers/what-is-omnichannel-messaging. **The channels it spans** SMS for universal reach; WhatsApp for rich, two-way conversation where the app is installed; RCS Business Messaging for branded, interactive native messaging; voice for calls and voice OTP; and email for long-form and receipts. Each has different reach, cost, and interactivity, which is exactly why routing across them beats committing to one. See /answers/rcs-business-messaging, /answers/what-is-whatsapp-business-api, and /answers/email-deliverability. **Channel selection and failover** The routing engine picks a channel by rules you set — cheapest-that-reaches, richest-that-reaches, or a fixed cascade like WhatsApp then SMS then voice for a verification code. If the primary isn't confirmed delivered within a window, it fails over to the next, and you are billed once for the outcome, not once per attempt. This lifts delivery rates while controlling spend. See /answers/what-is-route-failover and /answers/number-verification. **Benefits over single-channel messaging** Higher delivery through automatic fallback, lower cost by routing to the cheapest channel that reaches, a consistent branded experience across touchpoints, one integration instead of five, and a single customer conversation history for support and analytics. It turns disconnected channel silos into one coherent communications layer. See /answers/what-is-cpaas and /products/omnichannel. **Limitations and what to plan for** Each channel keeps its own rules — WhatsApp's 24-hour window and template approval, RCS device and carrier coverage, SMS sender-ID registration — so an omnichannel strategy must respect all of them, not paper over them. Encrypted OTT channels also sit outside SMS-firewall visibility, and per-channel pricing differs, so cost modelling matters. See /answers/whatsapp-24-hour-window and /answers/what-is-ott-bypass. **Is omnichannel the same as multichannel messaging?** No. Multichannel means you offer several channels, but each runs as its own silo with a separate thread. Omnichannel unifies them: one API, one customer conversation, and automatic routing and failover between channels. The practical difference is continuity — in omnichannel a customer who switches from SMS to WhatsApp mid-conversation stays in the same thread. See /answers/what-is-omnichannel-messaging. ### What is omnichannel messaging URL: https://www.broadnet.me/answers/what-is-omnichannel-messaging Last reviewed: October 10, 2026 Omnichannel messaging is the orchestration of multiple messaging channels (SMS, WhatsApp, RCS, email, push, voice) as a single coherent customer journey, where channel choice is selected per message based on reachability, cost, urgency, and user preference — rather than being hard-coded per use case. **Multichannel vs omnichannel** Multichannel: you support several channels but each is its own pipeline. The customer gets an order confirmation via SMS, a shipping update via email, and a delivery notification via WhatsApp — three disjoint flows with no shared context. Omnichannel: a single conversation graph spans channels. The customer's reply to the WhatsApp delivery notification updates the SMS-thread state. The fallback for an unread WhatsApp marketing message is an SMS to the same MSISDN 24 hours later. **What good orchestration does** Five things. Reach detection: HLR + WhatsApp account lookup + RCS capability check to know what's deliverable. Cost optimisation: pick the cheapest channel that delivers (RCS often beats SMS in MENA marketing; WhatsApp service replies inside the 24-hour window need no template and are billed per message from 1 October 2026, after a free tier of 1,000 service messages per business phone number per month). Channel preference per user: respect opt-outs and observed engagement. Fallback chains: WhatsApp → SMS → Voice for OTPs; RCS → SMS for marketing. Unified DLR feed: one webhook with one event model across channels. **What it requires under the hood** A unified contact graph (one customer's MSISDN, WhatsApp ID, RCS handle, email all linked). A channel-aware routing engine with per-channel cost and reach data. A single rules layer for opt-in/opt-out across channels. BroadNet's omnichannel product (/products/omnichannel) is built around exactly this — one API, smart channel selection, one consolidated event stream. **What it isn't** It is not just "we support SMS and WhatsApp from one dashboard." That's multichannel UI. Real omnichannel is a routing decision made per message based on live channel data — and it requires you to give the platform the freedom to pick the channel, not pre-decide for it. ### How does conversational AI for voice work URL: https://www.broadnet.me/answers/conversational-ai-voice Last reviewed: July 22, 2026 Conversational AI for voice — a voice bot or AI voice agent — lets callers speak naturally to software that understands intent and responds in real time. It chains speech-to-text, a language-understanding or LLM layer, dialogue logic, and text-to-speech over a programmable voice call, so routine contacts are handled end to end without a human agent while complex ones escalate cleanly. **How a voice AI agent works** A call arrives over the voice API; the caller's speech is streamed to automatic speech recognition (ASR) and transcribed; a natural-language-understanding or LLM layer interprets intent and decides the next step against your business logic and data; and a text-to-speech engine speaks the reply back — all in a low-latency loop that feels like conversation. It is the voice equivalent of a chatbot, running over a live phone call. See /platforms/broadnet-ai and /products/voice. **The building blocks** Speech-to-text (ASR) to hear the caller; natural-language understanding or an LLM to interpret and reason; dialogue management to track context across turns; integrations to CRMs and back-end systems for real answers; and text-to-speech for a natural voice. Barge-in (letting callers interrupt) and low round-trip latency are what separate a usable agent from a frustrating one. See /answers/what-is-ivr and /ai. **Conversational AI voice vs traditional IVR** A classic IVR is a rigid menu tree — press 1, press 2 — that callers navigate. A conversational AI agent lets the caller simply say what they want in natural language and understands it, handling open-ended requests, follow-ups, and context an IVR can't. It is the difference between a decision tree and a dialogue. Many deployments keep IVR fallbacks for reliability. See /answers/what-is-ivr and /answers/what-is-dtmf. **Benefits and use cases** 24/7 availability, instant answering with no queue, consistent handling, and deflection of routine contacts — balance checks, order status, appointment booking, first-line triage — so human agents focus on complex work. It scales elastically for peaks and captures every interaction as structured data. Voice AI also delivers spoken OTPs and outbound reminders conversationally. See /platforms/broadnet-ai and /answers/contact-center-ccaas. **Limitations and what to plan for** Speech recognition still struggles with heavy accents, background noise, and code-switching; latency in the ASR-to-TTS loop breaks the feel of conversation if unmanaged; and callers must be able to reach a human when the bot can't help. Governance matters too — the agent must not fabricate answers, and sensitive actions need verification. Design escalation and guardrails from the start. See /answers/voip-quality and /ai. **Is a voice AI agent the same as an IVR?** No. An IVR follows a fixed menu the caller navigates with keypad or set phrases. A conversational AI voice agent understands natural, open-ended speech and holds a contextual dialogue, so callers state their need in their own words rather than matching a menu. A voice agent can replace or front-end an IVR, and often keeps a menu fallback for edge cases. See /platforms/broadnet-ai. ### What is a cloud contact center (CCaaS) URL: https://www.broadnet.me/answers/contact-center-ccaas Last reviewed: July 22, 2026 A cloud contact center, or CCaaS (Contact Center as a Service), is a hosted platform that runs customer-service voice and digital interactions — inbound and outbound calls, IVR, skills-based routing, agent desktops, and analytics — delivered over the internet instead of on-premise hardware. It combines telephony (often over a voice API and SIP trunking) with channel and workforce tooling into one agent-facing application. **How a CCaaS works** Inbound calls and messages arrive over SIP trunks and channel APIs; an IVR and automatic call distributor (ACD) qualify and queue each contact; skills-based routing matches it to the right available agent; and an agent desktop presents the interaction with customer context. Supervisors get live queues and analytics, and everything runs from the cloud so agents can work anywhere. See /answers/what-is-ivr, /answers/what-is-acd, and /products/voice. **CCaaS vs CPaaS vs UCaaS** CCaaS is a finished contact-centre application for customer-facing agents. CPaaS is the developer building-block layer — voice, SMS, WhatsApp APIs — that a CCaaS is often built on. UCaaS is internal collaboration: cloud phone system, meetings, and chat for employees. In short, CPaaS is the toolkit; CCaaS and UCaaS are assembled products for different audiences. See /answers/cpaas-explained. **The core capabilities** Omnichannel intake (voice, SMS, WhatsApp, chat, email) into one queue; IVR and self-service; ACD and skills-based routing; outbound and dialler campaigns; call recording and quality monitoring; workforce management; and real-time plus historical analytics. Increasingly a conversational-AI layer deflects routine contacts before they reach an agent. See /answers/omnichannel-messaging and /answers/conversational-ai-voice. **Benefits over an on-premise contact centre** No telephony hardware to buy or maintain, elastic capacity for seasonal peaks, remote and distributed agents, faster rollout of new channels, pay-per-use economics, and continuous updates. Because it rides on programmable voice and messaging, a CCaaS can be extended in code rather than waiting on a vendor. See /products/voice and /tools/erlang-calculator. **Limitations and what to evaluate** CCaaS quality depends on the underlying voice routes (a slick agent desktop over poor carrier paths still drops calls), on integration with your CRM, and on channel coverage in your markets. Concurrency and calls-per-second limits, compliance (recording consent, caller-ID rules), and agent-experience design all shape the outcome. Evaluate the network and integrations, not just the UI. See /answers/voip-quality and /answers/what-is-cps. **What is the difference between CCaaS and a call center?** A traditional call centre is on-premise: physical phone systems, fixed capacity, and agents on site. CCaaS delivers the same functions — routing, IVR, agent desktops, analytics — as a cloud service, so capacity scales on demand, agents work remotely, and digital channels join voice in one queue. The functions are similar; the delivery model and flexibility are not. BroadNet supplies the voice connectivity and messaging channels a CCaaS runs on. See /products/voice. ### How does email deliverability work URL: https://www.broadnet.me/answers/email-deliverability Last reviewed: July 22, 2026 Email deliverability is the discipline of getting legitimate email into the inbox rather than the spam folder or a hard bounce. It rests on sender authentication (SPF, DKIM, DMARC), a warmed sending reputation tied to your IP and domain, clean list hygiene, and engagement signals mailbox providers watch. Authentication proves who sent the message; reputation and engagement decide where it lands. **How deliverability works** When you send, the receiving mailbox provider checks that the message is authenticated, scores the sending IP and domain reputation, weighs recipient engagement (opens, replies, spam complaints), and then decides inbox, spam, or reject. Getting to the inbox is therefore not about content alone — it is about trust the receiver has built up in your sending identity over time. See /products/email and /answers/what-is-verified-sender. **The three authentication standards** SPF lists which servers may send for your domain; DKIM cryptographically signs each message so tampering and forgery are detectable; and DMARC ties the two together, tells receivers what to do with failures, and reports abuse of your domain. All three aligned is the baseline every mailbox provider now expects before it will trust bulk mail. See /answers/gdpr-for-messaging. **Reputation, warm-up, and list hygiene** Reputation attaches to your sending IP and domain and is built by sending wanted mail consistently. New IPs must be warmed — volume ramped gradually — or providers throttle them. List hygiene keeps it healthy: remove hard bounces, honour unsubscribes, and never send to purchased lists, because spam-trap hits and complaints collapse reputation fast. See /answers/what-is-dnc. **Benefits of getting it right** More email reaching the inbox at the same send volume, fewer bounces and blocks, protection of your domain from spoofing and phishing (a security win as much as a marketing one), and richer analytics on what recipients actually engage with. Strong deliverability makes email a dependable channel in an omnichannel mix rather than a black hole. See /answers/omnichannel-messaging and /products/email. **Limitations and ongoing work** Deliverability is never finished — reputation decays if you send poorly, provider rules change, and one bad campaign can undo months of trust. It also can't rescue unwanted mail: authentication and warm-up get permission-based email delivered, but they won't force content recipients mark as spam into the inbox. Consent and relevance are prerequisites, not optional. See /answers/gdpr-for-messaging. **Why do my emails go to spam even though they're legitimate?** Usually one of four causes: missing or misaligned SPF/DKIM/DMARC so the receiver can't verify you; a cold or poor-reputation sending IP or domain; list problems (bounces, spam-trap hits, low engagement, or purchased lists); or content and sending patterns that look bulk and unwanted. Fix authentication first, then warm the sending identity and clean the list. See /products/email and /answers/what-is-verified-sender. ### How does SMS routing and least-cost routing (LCR) work URL: https://www.broadnet.me/answers/sms-routing-lcr Last reviewed: October 1, 2026 SMS routing decides which operator path each message takes to reach a handset; least-cost routing (LCR) automatically selects the cheapest available route that still meets quality and compliance rules. Because every destination has multiple possible paths at different prices and reliabilities, good routing balances cost against deliverability — favouring direct operator routes and steering clear of grey routes that are cheap but unreliable. **How SMS routing works** For each message the platform looks up the destination's home operator (after any number portability), consults the routes available to that operator, and picks one by your policy — cheapest, highest quality, or a blend. The message is submitted over that route's SMPP or SS7 interconnect, and the delivery receipt confirms the outcome. An HLR lookup first ensures the number is live and correctly attributed. See /operators/smsc-gateway and /answers/hlr-mnp-number-intelligence. **What least-cost routing (LCR) actually does** LCR maintains a rate table of every route to every destination and, per message, chooses the lowest-priced route that satisfies quality and regulatory constraints — then fails over to the next if it degrades. Pure lowest-price routing is a trap: the cheapest path is often a grey route, so mature LCR weights price against measured deliverability and sender-ID support, not price alone. See /answers/what-is-lcr and /answers/what-is-route-failover. **Direct routes vs grey routes** A direct route terminates over the destination operator's official A2P agreement — reliable delivery, sender-ID support, and traceable receipts, at a higher wholesale price. A grey route sneaks A2P in as cheap P2P through SIM boxes or foreign HLR backdoors; it is cheaper but delivery oscillates, sender IDs break, and operators block it. Least effective cost, not lowest sticker price, is the right metric. See /answers/what-is-grey-route-sms and /answers/what-is-grey-route-sms. **Benefits of quality-aware routing** Lower effective cost per delivered message once re-sends and failures are counted, higher and more stable delivery rates, preserved sender-ID branding, and clean operator-specific delivery receipts for troubleshooting. Automatic failover keeps traffic flowing when a route degrades, and direct routing keeps you compliant with operator and regulator rules. See /answers/what-is-dlr and /answers/what-is-throughput-sla. **Limitations and what to watch** Rate and quality tables must be kept current or LCR optimises against stale data; over-indexing on price alone routes you onto grey paths whose apparent savings evaporate in failed messages and broken sender IDs; and route quality shifts as operators block and aggregators re-route, so continuous DLR monitoring is essential. The signal to watch is oscillating DLR success on a suspiciously cheap route. See /answers/what-is-hop-by-hop-latency and /platforms/esme-cdr. **Is the cheapest SMS route always the best?** No — the cheapest sticker price is frequently a grey route whose real cost is higher once undelivered messages, re-sends, and broken sender-ID branding are counted. The right metric is least effective cost: the price per successfully delivered, correctly branded message. BroadNet routes on direct operator agreements across 1,000+ operator connections — direct to the operator in 86 countries, reaching 200+ — so cost is optimised without sacrificing deliverability. See /operators/smsc-gateway and /answers/what-is-grey-route-sms. ### How do I choose an SMS provider URL: https://www.broadnet.me/answers/how-to-choose-sms-provider Last reviewed: October 1, 2026 Choose an SMS provider on five measurable criteria: route quality (direct operator agreements versus grey routes), geographic coverage, deliverability transparency (real-time delivery receipts with operator-level error codes), throughput and uptime SLA, and compliance support (sender-ID registration, data residency). Price matters, but the cheapest per-message rate is usually a grey route that costs more per delivered message. BroadNet runs A2P to 200+ countries — direct to the operator in 86, over 1,000+ direct operator connections — at a 99.99% platform SLA — see /operators. **1. Route quality is the single biggest factor** A provider either holds direct A2P agreements with operators or resells cheaper grey routes that impersonate P2P traffic. Direct routes preserve your sender ID, deliver predictably, and return real operator error codes; grey routes are blocked by SMS firewalls in hours-to-days. Ask any shortlisted provider, in writing, whether the route to each of your priority countries is direct. See /answers/what-is-grey-route-sms. **2. Deliverability transparency** You cannot manage what you cannot see. A serious provider returns per-message delivery receipts (DLRs) with operator-specific error codes, not generic UNKNOWN failures — so you can diagnose why a message failed and to which network. See /answers/what-is-dlr and the /tools/smpp-error-codes lookup. **3. Coverage, throughput and SLA** Match the provider's footprint to your destinations, confirm sustained throughput (TPS) for OTP-class bursts, and get the uptime SLA in the contract. BroadNet sustains up to 30,000 SMS/sec per node and publishes a 99.99% platform SLA. See /answers/what-is-tps and /answers/what-is-throughput-sla. **4. Compliance and regional support** In regulated markets you must pre-register alphanumeric sender IDs and, increasingly, honour data-residency rules. A provider with local regulatory knowledge and operator relationships shortens go-live. See /answers/how-to-register-sender-id and /regulations. **5. Total cost of a delivered message** Compare cost-per-delivered-message, not the headline per-message rate. Grey routes look cheap until you add re-sends, sender-ID degradation, and the customer-experience cost of failed OTPs. See /answers/how-to-reduce-sms-costs. ### How do I choose a CPaaS provider URL: https://www.broadnet.me/answers/how-to-choose-cpaas-provider Last reviewed: September 29, 2026 Evaluate a CPaaS provider on six dimensions: channel breadth (SMS, WhatsApp, RCS, voice and email behind one API), route ownership, developer experience (SDKs, test access before you sign, honest docs), reliability SLA, regional depth and compliance, and the support model. A true CPaaS unifies every channel behind one API and one contract instead of forcing a separate integration per channel. BroadNet has operated as a MENA-native CPaaS since 2003, with omnichannel APIs over directly owned carrier routes — see /products/omnichannel. **1. Channel breadth behind one API** The value of CPaaS is consolidation: one integration, one identity, one invoice across SMS, WhatsApp, RCS, voice and email. If you would still need three vendors to cover your channels, it is not really a platform. See /answers/what-is-cpaas and /answers/what-is-omnichannel-messaging. **2. Route ownership vs reselling** Some CPaaS vendors own operator interconnects; others resell another aggregator's routes with a markup and less control over deliverability. Owned, direct routes mean better delivery, cleaner error data, and accountability when something breaks. See /answers/what-is-grey-route-sms. **3. Developer experience** Time-to-first-message is a real cost. Look for maintained SDKs, test credentials you can use against the real API before you sign, clear REST and SMPP references, and webhooks with signed payloads. See /developers and /answers/what-is-sandbox-vs-production. **4. Regional depth and compliance** Global averages hide regional gaps. A provider strong in your actual markets — with local sender-ID registration, operator relationships and data-residency options — will outperform a bigger vendor that is thin where you operate. See /regulations. **5. Reliability, SLA and support** Get the uptime SLA, the throughput ceiling, the route-failover behaviour, and the support responsiveness in writing. BroadNet publishes a 99.99% platform SLA with automatic route failover. See /answers/what-is-route-failover. ### How do you send an SMS via API URL: https://www.broadnet.me/answers/how-to-send-sms-via-api Last reviewed: September 24, 2026 Sending an SMS through an HTTP API means passing the destination number, sender ID, and message text to a REST endpoint that hands the message to operator networks and returns a message ID you can track for delivery. **The request** BroadNet's gateway accepts a POST to https://api.broadnet.me/sms/sendSms with an Authorization: Bearer token and a JSON body: senderId (the sender ID), destinationNumber (the destination number in international format, digits only, no plus sign), message (the text), and messageType (TEXT for GSM-7, UNICODE for Arabic, emoji and other non-Latin scripts). A successful call returns 200 OK with the message ID in the response body. **Encoding and length** A GSM-7 message fits 160 characters per segment (153 once a message spans multiple segments); switching to Unicode for emoji or non-Latin scripts drops that to 70 (67 concatenated). Set messageType to TEXT for plain GSM-7 and UNICODE when the body needs Unicode or Arabic, so characters aren't garbled — POST /sms/identify returns the encoding and segment count before you send. **Track delivery, don't assume it** The returned message ID is the handle for delivery receipts (DLRs). Configure a webhook to receive the operator's final status — delivered, failed, or expired — rather than treating a 200 on submission as proof the handset received the message. **Moving to production** Use international E.164 numbers, register your sender ID in each destination market before you scale, and send over direct operator routes for consistent latency. For high volume the same account is reachable over SMPP as well as REST, so you can start on HTTP and switch bind types without re-onboarding. Q: Can I send an SMS with a GET request, or do I need POST? A: Use POST. The REST endpoint POST /sms/sendSms takes a JSON body and a Bearer token, so the message text and credentials never appear in URLs or server logs. The legacy HTTP API (/websmpp/websms) still accepts GET for existing SMPP-era integrations, but new integrations should use the REST API. Q: Do I need SMPP, or is the HTTP API enough? A: The REST/HTTP API is enough for most volumes and is the fastest to integrate. SMPP suits very high sustained throughput and persistent binds. The same BroadNet account works over both, so you can start on HTTP and add SMPP later without re-onboarding. Q: How do I know a message was actually delivered? A: Submission returns a message ID; the final handset status arrives asynchronously as a delivery receipt (DLR) on your webhook — delivered, failed, or expired. Don't treat the submission response as proof of delivery. ### Why are my SMS messages not being delivered URL: https://www.broadnet.me/answers/why-are-my-sms-not-delivering Last reviewed: July 31, 2026 Undelivered SMS almost always trace to one of a few causes — an unregistered sender ID, an invalid or unreachable number, grey-route filtering, wrong encoding, or a handset that is off — and each shows up differently in the delivery receipt. **Sender ID not registered** In regulated markets the operator drops A2P traffic from sender IDs that aren't on the registry. The DLR typically reads as rejected. Registering the ID in that market clears the block. **Invalid or unreachable number** Numbers that are disconnected, ported, or roaming out of coverage fail at the network level. An HLR lookup before sending flags these so they don't count against your delivery rate or your bill. **Grey-route filtering** If your traffic is routed over a grey path, operator SMS firewalls silently discard it and you may see no receipt at all. Moving to a direct operator route restores delivery. **Encoding or content** A Unicode body submitted as GSM-7 (or the reverse) can be rejected or arrive garbled, and spam-like content or forbidden keywords are filtered. Read the DLR — 'rejected' versus 'expired' versus 'undelivered' points straight at the cause. Q: My API call returns success but the SMS never arrives — why? A: A success on submission only means the gateway accepted the message. The handset outcome comes later in the DLR, and a submitted message can still fail at the operator for an unregistered sender ID, an invalid number, or grey-route filtering. Read the DLR, not the submit response. Q: Does an invalid or ported number count against my delivery rate? A: Yes. Sending to disconnected, invalid, or out-of-coverage numbers produces failures that lower your delivery ratio and cost you money. Run an HLR lookup first to drop them before you send. Q: Why do messages deliver in one country but not another? A: Delivery is operator- and market-specific. A route that's direct in one country may be grey (and firewall-filtered) in another, and some regulators require a registered sender ID per market. Confirm each destination is on a direct route with a registered ID. ### What is 2FA (two-factor authentication) URL: https://www.broadnet.me/answers/what-is-2fa Last reviewed: July 22, 2026 Two-factor authentication (2FA) requires a user to prove their identity with two independent factors before access is granted — typically something they know (a password) and something they have (a phone receiving an OTP). SMS OTP is the most widely deployed second factor in the world. 2FA sharply reduces account-takeover risk, because a stolen password alone is no longer enough to log in. **The factor categories** Authentication factors fall into three groups: something you know (password, PIN), something you have (phone, hardware token, passkey), and something you are (fingerprint, face). 2FA combines exactly two of these; MFA (multi-factor) combines two or more. SMS OTP pairs a password with possession of the phone. See /answers/what-is-otp. **Delivery channels and their trade-offs** SMS OTP has the widest reach but is exposed to SIM-swap and AIT abuse; authenticator-app TOTP is phishing-resistant but needs setup; WhatsApp, voice, and Flash Call OTP add reach and cost options; passkeys remove the shared secret entirely. Robust systems fail over across channels in one call. See /answers/what-is-flash-call-verification and /products/myotp. ## All other answers (quick answers) ### A2P vs P2P SMS — what's the difference? URL: https://www.broadnet.me/answers/a2p-vs-p2p-sms · Markdown: https://www.broadnet.me/answers/a2p-vs-p2p-sms.md · Last reviewed: 2026-08-08 P2P (person-to-person) SMS is one mobile subscriber texting another from their dial-pad. A2P (application-to-person) SMS is a software application messaging a subscriber — OTPs, alerts, notifications, marketing. They look identical on the handset, but underneath they use different operator agreements, different routes, different rate structures, and different regulatory regimes. Sending A2P traffic over P2P routes is exactly what grey-route fraud is, and it is why operators deploy SMS firewalls. ### The WhatsApp 24-hour window explained URL: https://www.broadnet.me/answers/whatsapp-24-hour-window · Markdown: https://www.broadnet.me/answers/whatsapp-24-hour-window.md · Last reviewed: 2026-10-10 When a customer messages your WhatsApp Business number, you can reply freely with Service-category messages for the next 24 hours; from 1 October 2026 Meta bills service replies per message after a free tier of 1,000 service messages per business phone number per month. After the 24-hour window closes, you must use a pre-approved template (a Marketing, Utility or Authentication message, billed per delivered message) to re-initiate. ### RCS vs SMS — compared URL: https://www.broadnet.me/answers/rcs-vs-sms · Markdown: https://www.broadnet.me/answers/rcs-vs-sms.md · Last reviewed: 2026-08-08 SMS is the 1980s text-only bearer: 160 GSM-7 characters per segment, no media, no branding, delivered over the signalling channel to literally every mobile phone on Earth. RCS Business Messaging (RBM) is the GSMA's modern replacement carried over data: multi-thousand-character messages, rich cards and carousels, a verified branded sender with your logo and name, read receipts, typing indicators and suggested replies. SMS reaches everyone with a phone; RCS reaches modern Android (Universal Profile since 2019) and iPhone (iOS 18, 2024) — and falls back to SMS when RCS is unavailable. ### RCS vs WhatsApp — compared URL: https://www.broadnet.me/answers/rcs-vs-whatsapp · Markdown: https://www.broadnet.me/answers/rcs-vs-whatsapp.md · Last reviewed: 2026-10-10 Both are branded, interactive business messaging that beat plain SMS on engagement — but they are architecturally opposite. RCS is a carrier network protocol (GSMA Universal Profile) delivered into the phone's native Messages app, with no app to install. WhatsApp is a Meta over-the-top application installed by 2B+ users worldwide, billed per delivered template message. RCS wins on frictionless native reach and in markets where WhatsApp faces restrictions; WhatsApp wins on installed-base depth, richer media, groups, and mature conversational commerce. ### GSMA IR.71 explained URL: https://www.broadnet.me/answers/gsma-ir71-explained · Markdown: https://www.broadnet.me/answers/gsma-ir71-explained.md · Last reviewed: 2026-10-01 GSMA Permanent Reference Document IR.71 — "SMS Network-to-Network Interconnect" — is the GSMA's guidance for monetizing A2P SMS traffic between operators. It defines the commercial framework for A2P route agreements, signalling expectations, anti-abuse measures, and audit trail requirements. ### SMPP 3.4 vs SMPP 5.0 — what changed and what to use URL: https://www.broadnet.me/answers/smpp-3-4-vs-5-0 · Markdown: https://www.broadnet.me/answers/smpp-3-4-vs-5-0.md · Last reviewed: 2026-09-30 SMPP 3.4 (1999) is still the SMS interconnect protocol that runs almost every A2P bind in production today. SMPP 5.0 (2003) added Unicode-clean headers, broadcast and cell-broadcast support, and TLVs for richer message classes — but most SMSCs and aggregators never moved to it. If you are picking today, bind to SMPP 3.4 over TLS unless your counterparty specifically asks for 5.0. ### SS7 MAP — what it is and why messaging still depends on it URL: https://www.broadnet.me/answers/ss7-map-explained · Markdown: https://www.broadnet.me/answers/ss7-map-explained.md · Last reviewed: 2026-05-27 SS7 MAP (Mobile Application Part) is the signalling protocol GSM/UMTS networks use for everything that is not a voice call or data session — location updates, supplementary services, USSD, and the SRI-for-SM / MT-ForwardSM exchange that delivers every SMS to a handset. Even in 2026, every cross-operator SMS in a 2G/3G/4G/5G non-standalone network still terminates through MAP. ### Diameter S6a — the 4G equivalent of MAP URL: https://www.broadnet.me/answers/diameter-s6a-explained · Markdown: https://www.broadnet.me/answers/diameter-s6a-explained.md · Last reviewed: 2026-05-27 Diameter S6a is the 3GPP-defined interface between a 4G MME (Mobility Management Entity) and an HSS (Home Subscriber Server). It carries authentication vectors, location updates, and — relevant for messaging — the Send-Routing-Info-for-SM equivalent used when SMS is delivered via SGs or SMS-over-IP. Diameter is to 4G what SS7 MAP is to 2G/3G. ### GSMA IR.71 testing — what an A2P route audit looks like URL: https://www.broadnet.me/answers/gsma-ir71-testing · Markdown: https://www.broadnet.me/answers/gsma-ir71-testing.md · Last reviewed: 2026-05-27 GSMA IR.71 is the GSMA's reference document for A2P SMS network-to-network interconnect. Beyond defining the commercial framework, IR.71 prescribes a testing regime that operators use to validate that an aggregator's route is legitimate, well-formed, and free of grey-route bypass. Passing IR.71 testing is the prerequisite for getting a direct A2P agreement with most tier-1 operators. ### GSMA FS.07 and FS.11 — the SS7 signalling firewall standards URL: https://www.broadnet.me/answers/gsma-fs07-fs11-signaling-firewall · Markdown: https://www.broadnet.me/answers/gsma-fs07-fs11-signaling-firewall.md · Last reviewed: 2026-05-27 GSMA FS.07 ("SS7 and Sigtran Network Security") and FS.11 ("SS7 Interconnect Security Monitoring Guidelines") are the two GSMA Permanent Reference Documents that define what a modern SS7 signalling firewall must do. Every operator that wants to be considered for a roaming or A2P agreement with a tier-1 partner must demonstrate FS.07/FS.11 compliance. ### SGP.32 — eSIM IoT for M2M without the SM-DP+ dance URL: https://www.broadnet.me/answers/sgp-32-esim · Markdown: https://www.broadnet.me/answers/sgp-32-esim.md · Last reviewed: 2026-05-27 SGP.32 is the GSMA's 2023 specification for IoT eSIM provisioning. Where the consumer eSIM spec (SGP.22) requires user interaction with a QR code and the legacy M2M spec (SGP.02) requires a heavyweight SM-DP/SM-SR pair, SGP.32 introduces the IoT Profile Assistant (IPA) and a remote SIM provisioning flow designed for headless devices that ship without a screen. ### SAS-SM certification — what it means for SIM and eSIM trust URL: https://www.broadnet.me/answers/sas-sm-certification · Markdown: https://www.broadnet.me/answers/sas-sm-certification.md · Last reviewed: 2026-09-29 SAS-SM is the GSMA's Security Accreditation Scheme for Subscription Management — the audit that any vendor running SM-DP+, SM-SR, or eIM infrastructure must pass to be trusted by mobile operators for eSIM profile provisioning. Without SAS-SM, no tier-1 operator will exchange profile signing keys with you. ### HMAC-SHA256 for DLR webhook signing — how and why URL: https://www.broadnet.me/answers/hmac-sha256-dlr-signing · Markdown: https://www.broadnet.me/answers/hmac-sha256-dlr-signing.md · Last reviewed: 2026-09-24 HMAC-SHA256 is the cryptographic primitive every modern messaging platform uses to sign delivery-receipt and inbound-message webhooks. The platform computes a keyed hash over the request body using a shared secret; your endpoint recomputes the same hash and compares. This proves the webhook came from the platform — not from someone who guessed your URL — and that the body was not tampered with in transit. ### TLS 1.3 in messaging — what changed and why it matters for SMPP URL: https://www.broadnet.me/answers/tls-1-3-in-messaging · Markdown: https://www.broadnet.me/answers/tls-1-3-in-messaging.md · Last reviewed: 2026-09-24 TLS 1.3 (RFC 8446, 2018) replaced TLS 1.2 with a faster handshake, removed every algorithm that had been broken in the previous decade, and made forward secrecy mandatory. For messaging, the practical impact is on SMPP bindings: shorter handshake means faster reconnect when an SMSC reboots, and removal of RSA key exchange means a captured pcap of past SMPP traffic cannot be decrypted later even if the private key leaks. ### What is P2P SMS? URL: https://www.broadnet.me/answers/what-is-p2p-sms · Markdown: https://www.broadnet.me/answers/what-is-p2p-sms.md · Last reviewed: 2026-05-27 P2P (person-to-person) SMS is a text message sent from one mobile subscriber to another using their handset's native messaging app — the kind of SMS that has existed since 1992. It rides over operator P2P routes, uses the originator's MSISDN as the sender, and is priced inside the consumer's tariff bundle rather than as a commercial event. ### What is MNP (Mobile Number Portability)? URL: https://www.broadnet.me/answers/what-is-mnp · Markdown: https://www.broadnet.me/answers/what-is-mnp.md · Last reviewed: 2026-10-01 MNP is the regulatory regime that lets a subscriber keep their mobile number when they switch from one operator to another. The number is unchanged; the routing is updated. Every operator maintains a central or per-operator number portability database, queried at call/SMS routing time so the message reaches the new operator's HLR, not the original one. ### What is a DLR (Delivery Receipt)? URL: https://www.broadnet.me/answers/what-is-dlr · Markdown: https://www.broadnet.me/answers/what-is-dlr.md · Last reviewed: 2026-05-27 A DLR is the asynchronous confirmation that an SMS has been delivered (or failed to deliver) at the handset. It is generated by the recipient operator's SMSC, returned over SMPP via deliver_sm or HTTP webhook, and carries a state (DELIVRD, UNDELIV, REJECTD, EXPIRED) plus an operator-specific error code. ### MO vs MT — what's the difference? URL: https://www.broadnet.me/answers/what-is-mo-vs-mt · Markdown: https://www.broadnet.me/answers/what-is-mo-vs-mt.md · Last reviewed: 2026-07-25 MT (mobile-terminated) is a message destined for a handset — the operator's network is the destination. MO (mobile-originated) is a message sent from a handset — the operator's network is the source. From an enterprise perspective, every A2P SMS you send is MT, and every reply or inbound keyword (STOP, START, HELP) you receive is MO. ### What is an MMSC (Multimedia Messaging Service Centre)? URL: https://www.broadnet.me/answers/what-is-mmsc · Markdown: https://www.broadnet.me/answers/what-is-mmsc.md · Last reviewed: 2026-05-27 An MMSC is the operator infrastructure node that stores, transcodes, and forwards MMS messages — picture messages, video, audio, and rich text larger than the SMS 160-character limit. Every MMS sent or received on a 2G/3G/4G mobile network is brokered by an MMSC, the multimedia equivalent of the SMSC. ### What is RCS Business Messaging (RBM)? URL: https://www.broadnet.me/answers/what-is-rcs-business-messaging · Markdown: https://www.broadnet.me/answers/what-is-rcs-business-messaging.md · Last reviewed: 2026-09-26 RCS Business Messaging is the enterprise variant of RCS — the GSMA-standardised successor to SMS. It lets verified brands send rich cards, carousels, suggested replies, buttons, and read-receipt-trackable content into the recipient's native Messages app, without requiring the user to install anything. RBM is supported on Android via Google Messages and on iPhone since iOS 18 (2024). ### Sender ID registration in the UAE — the TDRA process URL: https://www.broadnet.me/answers/sender-id-registration-uae-tdra · Markdown: https://www.broadnet.me/answers/sender-id-registration-uae-tdra.md · Last reviewed: 2026-09-26 Every alphanumeric sender ID used to send A2P SMS to UAE mobile numbers must be pre-registered with the TDRA (Telecommunications and Digital Government Regulatory Authority). Registration goes through a licensed local aggregator (BroadNet, du, e&), takes 5-7 business days, and costs AED 250 one-time plus AED 500 annually per sender ID. ### Sender ID registration in Saudi Arabia — the CST process URL: https://www.broadnet.me/answers/sender-id-registration-ksa-cst · Markdown: https://www.broadnet.me/answers/sender-id-registration-ksa-cst.md · Last reviewed: 2026-10-01 All A2P SMS to KSA mobile numbers must use a CST-registered alphanumeric sender ID. CST (Communications, Space and Technology Commission) requires submission through a licensed local aggregator. Registration typically takes 5-10 business days. STC, Mobily, and Zain KSA each maintain their own enforcement databases synced from CST. ### Sender ID registration in Egypt — the NTRA process URL: https://www.broadnet.me/answers/sender-id-registration-egypt-ntra · Markdown: https://www.broadnet.me/answers/sender-id-registration-egypt-ntra.md · Last reviewed: 2026-05-27 Egypt's NTRA (National Telecommunications Regulatory Authority) requires all A2P SMS sender IDs to be pre-approved and all A2P traffic to terminate through NTRA-licensed local aggregators. There is no grey-route tolerance in Egypt — non-licensed routes are detected and blocked by the operator firewalls within days. Registration takes 10-15 business days. ### Sender ID registration in Jordan — the TRC process URL: https://www.broadnet.me/answers/sender-id-registration-jordan-trc · Markdown: https://www.broadnet.me/answers/sender-id-registration-jordan-trc.md · Last reviewed: 2026-09-26 Jordan's TRC (Telecommunications Regulatory Commission) requires sender-ID pre-registration for all A2P SMS to Jordanian mobile numbers. Registration is handled by the destination operator (Zain Jordan, Orange Jordan, Umniah) or via a licensed local aggregator. Standard turnaround: 5-7 business days. Cost: JOD 50-100 one-time plus modest annual renewal. ### PDPL (KSA) — what the Saudi Personal Data Protection Law means for messaging URL: https://www.broadnet.me/answers/pdpl-ksa-explained · Markdown: https://www.broadnet.me/answers/pdpl-ksa-explained.md · Last reviewed: 2026-05-27 The Personal Data Protection Law (PDPL) is the Kingdom of Saudi Arabia's comprehensive data-protection framework, in force since 14 September 2023 with full enforcement from September 2024. It governs every collection, use, and cross-border transfer of personal data of individuals in KSA — including the MSISDN you message, the consent record you keep, and where in the world that data is processed. ### GDPR for messaging — what enterprise senders need to know URL: https://www.broadnet.me/answers/gdpr-for-messaging · Markdown: https://www.broadnet.me/answers/gdpr-for-messaging.md · Last reviewed: 2026-05-27 The General Data Protection Regulation (EU 2016/679) governs every collection and use of personal data of individuals in the EU/EEA, including MSISDNs used for messaging. For business messaging, GDPR matters most in five places: lawful basis, opt-out / right to erasure, cross-border transfers, processor agreements, and data-breach notification. Penalties reach the higher of €20 million or 4% of global annual turnover. ### HIPAA for messaging — what healthcare senders need to know URL: https://www.broadnet.me/answers/hipaa-for-messaging · Markdown: https://www.broadnet.me/answers/hipaa-for-messaging.md · Last reviewed: 2026-09-27 HIPAA (the US Health Insurance Portability and Accountability Act) governs Protected Health Information (PHI) — any information that ties an individual to their medical care. For messaging, HIPAA is triggered the moment your SMS or WhatsApp message conveys PHI (a clinic name, an appointment specialty, a test result, a prescription). The relevant rules are the Privacy Rule, the Security Rule, and the Breach Notification Rule. ### What is GSMA Open Gateway? URL: https://www.broadnet.me/answers/gsma-open-gateway · Markdown: https://www.broadnet.me/answers/gsma-open-gateway.md · Last reviewed: 2026-05-27 GSMA Open Gateway is the industry initiative — launched at MWC 2023 — for mobile network operators to expose network capabilities (number verification, location, device status, quality-on-demand) through a single set of standardised, CAMARA-defined APIs. It is the operator industry's answer to the fragmentation of CPaaS, RCS hubs, and per-operator interconnect. ### What is SIM box fraud? URL: https://www.broadnet.me/answers/what-is-sim-box-fraud · Markdown: https://www.broadnet.me/answers/what-is-sim-box-fraud.md · Last reviewed: 2026-05-27 A SIM box is a piece of hardware that holds dozens or hundreds of physical SIM cards from a mobile operator and uses them to terminate inbound international calls (or A2P SMS) as if they originated on-net from individual consumer subscribers. It bypasses the operator's international termination tariff and the A2P SMS tariff, costing operators globally an estimated USD 3-7 billion per year. ### What is sender ID spoofing? URL: https://www.broadnet.me/answers/what-is-sender-id-spoofing · Markdown: https://www.broadnet.me/answers/what-is-sender-id-spoofing.md · Last reviewed: 2026-09-26 Sender ID spoofing is sending an SMS with a falsified originator — appearing as `BANK-OF-X`, `DHL`, `MyBrand` when the sender has no authorisation to use that string. It is the SMS equivalent of email phishing, and it is the dominant vector for smishing attacks globally. The protocol weakness: GSM SMS has no end-to-end sender authentication, so the SMSC accepts whatever sender ID the originating ESME submits. ### What is OTT bypass? URL: https://www.broadnet.me/answers/what-is-ott-bypass · Markdown: https://www.broadnet.me/answers/what-is-ott-bypass.md · Last reviewed: 2026-05-27 OTT bypass is the slow replacement of operator SMS revenue by Over-The-Top messaging apps (WhatsApp, Telegram, iMessage, Signal). Globally, P2P SMS traffic has declined ~30% since 2019 as users move conversational messaging to OTT. For operators, OTT bypass is the loss of the consumer messaging tariff. For enterprise senders, it is the rebalancing of channel mix toward WhatsApp and RCS. ### What is hop-by-hop latency in SMS delivery? URL: https://www.broadnet.me/answers/what-is-hop-by-hop-latency · Markdown: https://www.broadnet.me/answers/what-is-hop-by-hop-latency.md · Last reviewed: 2026-05-27 Hop-by-hop latency is the cumulative delay added by each intermediate SMSC or aggregator between your application and the recipient's handset. A direct A2P route has 2-3 hops (app → BroadNet SMSC → operator SMSC → handset). A grey route can have 8-12 hops, each adding tens to hundreds of milliseconds of queue and signalling delay. For OTPs and time-sensitive messaging, hop count is the dominant cost. ### What is route failover in messaging? URL: https://www.broadnet.me/answers/what-is-route-failover · Markdown: https://www.broadnet.me/answers/what-is-route-failover.md · Last reviewed: 2026-07-22 Route failover is the automatic re-routing of an SMS submission from a failing primary route to a healthy secondary route, ideally within the same submit_sm transaction. For a CPaaS handling tens of millions of messages a day, failover is the difference between a 99.9% delivery rate and a 99.05% rate — a tenfold difference in user-visible failures. ### SMS pricing per MT — what you're actually paying for URL: https://www.broadnet.me/answers/sms-pricing-per-mt-explained · Markdown: https://www.broadnet.me/answers/sms-pricing-per-mt-explained.md · Last reviewed: 2026-05-27 An SMS price quote is almost always "per MT," meaning per mobile-terminated message — per message arriving at a handset. The headline number is the unit you pay for, but the full cost of an SMS programme includes setup fees, sender-ID fees, minimum commitments, surge pricing during peak hours, and the carrier-specific tariff for the destination operator. ### Test credentials vs production: what changes when you go live? URL: https://www.broadnet.me/answers/what-is-sandbox-vs-production · Markdown: https://www.broadnet.me/answers/what-is-sandbox-vs-production.md · Last reviewed: 2026-09-29 BroadNet does not run a separate sandbox. Your test credentials work against the production endpoint, https://api.broadnet.me, with the same API and the same code you will run in production; test messages go only to your own verified number(s), and their delivery receipts come back to your webhook. Production access and routes are switched on for your account after approval (sender identity, traffic purpose and sender IDs), typically 5–15 business days from request, and your code does not change. ### What is conversation pricing for WhatsApp? URL: https://www.broadnet.me/answers/what-is-conversation-pricing-whatsapp · Markdown: https://www.broadnet.me/answers/what-is-conversation-pricing-whatsapp.md · Last reviewed: 2026-10-10 Conversation pricing was Meta's billing model for the WhatsApp Business API until 1 July 2025: you paid per 24-hour conversation window with a user. Since then Meta bills per delivered template message — Marketing, Utility or Authentication — by category and country. From 1 October 2026 Meta bills replies inside the 24-hour customer service window per message, at the same rate as utility and authentication messages in that market: service replies after a free tier of 1,000 service messages per business phone number per month, utility templates from the first message. ### What is a throughput SLA? URL: https://www.broadnet.me/answers/what-is-throughput-sla · Markdown: https://www.broadnet.me/answers/what-is-throughput-sla.md · Last reviewed: 2026-09-27 A throughput SLA is the contractually guaranteed sustained rate at which an aggregator will accept your submissions and deliver them to the operator — typically expressed in messages per second (MPS) or transactions per second (TPS). For OTP services, marketing-burst campaigns, and operator-grade integrations, throughput SLA is often more important than the unit price. ### What is the SMS validity period? URL: https://www.broadnet.me/answers/what-is-validity-period · Markdown: https://www.broadnet.me/answers/what-is-validity-period.md · Last reviewed: 2026-05-27 The validity period is how long an SMSC will keep retrying delivery of a message that didn't reach the handset on first attempt — typically because the recipient was off-network, out of coverage, or had a full inbox. After the validity period expires, the SMSC drops the message and emits an EXPIRED DLR. Default is usually 24 hours; the SMPP submit_sm validity_period field lets you override. ### GSM 7-bit vs UCS-2 encoding — when each is used URL: https://www.broadnet.me/answers/what-is-encoding-gsm-7-ucs-2 · Markdown: https://www.broadnet.me/answers/what-is-encoding-gsm-7-ucs-2.md · Last reviewed: 2026-05-27 An SMS body can be encoded in GSM 7-bit (160 characters per segment, covers ASCII plus a small extension table) or UCS-2 (70 characters per segment, covers any Unicode codepoint including Arabic, Chinese, emoji). The choice happens automatically — your aggregator scans the body and picks the narrowest encoding that fits. Mixed encoding is not allowed within a single SMS; one non-GSM-7 character forces the whole message to UCS-2. ### Short code vs long code — when to use each URL: https://www.broadnet.me/answers/what-is-short-code-vs-long-code · Markdown: https://www.broadnet.me/answers/what-is-short-code-vs-long-code.md · Last reviewed: 2026-07-25 A short code is a 3-6 digit number leased from a country regulator/operator for high-volume A2P SMS (typically marketing campaigns, voting, donations). A long code is a regular 10-12 digit MSISDN used for two-way conversational SMS or low-volume A2P. They differ in cost, throughput, MO capability, and consumer recognition. ### SM-DP+ — Subscription Manager Data Preparation, explained URL: https://www.broadnet.me/answers/sm-dp-plus · Markdown: https://www.broadnet.me/answers/sm-dp-plus.md · Last reviewed: 2026-09-29 SM-DP+ (Subscription Manager — Data Preparation +) is the GSMA-defined server that prepares, encrypts, and securely delivers eSIM profiles to an eUICC. It is the central trust component of the consumer eSIM architecture (GSMA SGP.21/22) and the IoT eSIM architecture (SGP.31/32), holding the operator's profile signing keys inside an HSM and binding each profile to one specific eUICC identifier (EID). ### SM-DS — Subscription Manager Discovery Service URL: https://www.broadnet.me/answers/sm-ds · Markdown: https://www.broadnet.me/answers/sm-ds.md · Last reviewed: 2026-05-28 SM-DS (Subscription Manager — Discovery Service) is the GSMA-defined directory that lets an eUICC discover that one or more SM-DP+ servers have profile downloads waiting for it, without the user needing to scan a QR code or type an activation code. It is the silent partner of SM-DP+: SM-DP+ holds the profile, SM-DS tells the eUICC where to fetch it. ### eUICC — the embedded UICC chip explained URL: https://www.broadnet.me/answers/what-is-euicc · Markdown: https://www.broadnet.me/answers/what-is-euicc.md · Last reviewed: 2026-05-28 An eUICC (embedded Universal Integrated Circuit Card) is the soldered-down successor to the removable plastic SIM card. Physically it is a tamper-resistant secure element on the device PCB. Functionally it can hold multiple operator profiles simultaneously, switch between them remotely (Remote SIM Provisioning), and run JavaCard applets. eUICC is the hardware foundation that makes consumer eSIM (SGP.22) and IoT eSIM (SGP.32) possible. ### EID — the eUICC identifier, explained URL: https://www.broadnet.me/answers/what-is-eid · Markdown: https://www.broadnet.me/answers/what-is-eid.md · Last reviewed: 2026-05-28 EID (eUICC Identifier) is the globally-unique 32-digit numeric serial number burned into every eUICC at manufacture. It identifies the secure element across its lifetime — through every operator change, every profile install, every device repurpose. EID is to eUICC what ICCID is to a classic SIM, but it is bound to the chip, not to any single operator's subscription. ### eUICC security domains — ISD-R, ISD-P, MNO-SD, ECASD URL: https://www.broadnet.me/answers/euicc-security-domains · Markdown: https://www.broadnet.me/answers/euicc-security-domains.md · Last reviewed: 2026-05-28 Inside an eUICC, every cryptographic key and every profile is isolated inside a Security Domain — a logical container with its own keys, its own access rules, and its own privileges. The four domains that matter for eSIM Remote SIM Provisioning are ISD-R (the boss), ISD-P (per-profile), MNO-SD (operator OTA), and ECASD (the certificate root). Understanding them is the difference between debugging an eSIM failure in an hour and debugging it in a week. ### Milenage algorithm — 3GPP authentication explained URL: https://www.broadnet.me/answers/milenage-algorithm · Markdown: https://www.broadnet.me/answers/milenage-algorithm.md · Last reviewed: 2026-09-29 Milenage is the 3GPP-standardised authentication and key-generation algorithm that every GSM/UMTS/LTE network uses to verify a subscriber and derive session keys. It runs inside the SIM/eUICC and inside the operator's HLR/HSS, taking the subscriber's Ki (long-term key), OPc (operator-customised constant), and a network random challenge (RAND), and producing the response (RES), the ciphering key (CK), the integrity key (IK), and an anonymity key (AK). It is the cryptographic foundation of mobile authentication. ### Tuak algorithm — the higher-strength Milenage alternative URL: https://www.broadnet.me/answers/tuak-algorithm · Markdown: https://www.broadnet.me/answers/tuak-algorithm.md · Last reviewed: 2026-05-28 Tuak (sometimes written TUAK) is the 3GPP-specified second-generation authentication algorithm for mobile networks, designed as a future-proof alternative to Milenage. Where Milenage is built on AES-128, Tuak is built on the Keccak permutation (the same primitive behind SHA-3), allowing larger key sizes (up to 256 bits) and a different cryptographic family in case AES-based Milenage ever weakens. Tuak is functionally interchangeable with Milenage at the air-interface level — the network selects which to use. ### eSIM ES interfaces — ES2+, ES8+, ES9+, ES10 explained URL: https://www.broadnet.me/answers/esim-es-interfaces-explained · Markdown: https://www.broadnet.me/answers/esim-es-interfaces-explained.md · Last reviewed: 2026-05-28 The eSIM ecosystem is held together by a set of ES (eSIM) interfaces defined in GSMA SGP.22 (consumer) and SGP.32 (IoT). Each ES interface specifies who talks to whom, what they exchange, and how it is secured. ES2+ is operator-to-SM-DP+. ES8+ is SM-DP+-to-eUICC over the air. ES9+ is LPA-to-SM-DP+ over HTTPS. ES10 is LPA-to-eUICC inside the device. Knowing these is the difference between reading the spec and reading hieroglyphs. ### ASR — Answer-Seizure Ratio explained URL: https://www.broadnet.me/answers/what-is-asr · Markdown: https://www.broadnet.me/answers/what-is-asr.md · Last reviewed: 2026-05-28 ASR (Answer-Seizure Ratio) is the percentage of call attempts (seizures) that are answered by the called party. It is the single most important voice-quality KPI in carrier interconnect — operators, wholesale voice traders, and contact-centre platforms all live and die by their ASR per destination. ASR below the destination's normal range is an immediate red flag for routing degradation, fraud, or signalling issues. ### SIGTRAN adaptation layers — M3UA, M2UA, SUA explained URL: https://www.broadnet.me/answers/sigtran-adaptation-layers · Markdown: https://www.broadnet.me/answers/sigtran-adaptation-layers.md · Last reviewed: 2026-05-28 Inside SIGTRAN, the SS7 application protocols (MAP, ISUP, SCCP) need a bridge to the IP/SCTP transport. That bridge is an adaptation layer. Three are in production use: M2UA (replaces MTP2), M3UA (replaces MTP3), and SUA (SCCP-User Adaptation — bypasses MTP3 entirely and connects SCCP directly to SCTP). Picking the right layer is mostly about how much of the legacy SS7 stack you want to keep. ### OPC and DPC — SS7 Point Codes explained URL: https://www.broadnet.me/answers/ss7-opc-dpc · Markdown: https://www.broadnet.me/answers/ss7-opc-dpc.md · Last reviewed: 2026-05-28 Every SS7 node (STP, HLR, MSC, SMSC, SCP) has a unique numeric address called a Point Code (PC). On every SS7 message, the Originating Point Code (OPC) identifies the sender and the Destination Point Code (DPC) identifies the intended recipient — exactly analogous to IP source and destination addresses, but in the SS7 numbering plan. OPC/DPC routing is the foundation of how SS7 traffic moves between network elements. ### GT — Global Title in SS7 routing explained URL: https://www.broadnet.me/answers/ss7-global-title · Markdown: https://www.broadnet.me/answers/ss7-global-title.md · Last reviewed: 2026-05-28 A Global Title (GT) is an SS7 address — usually a phone number or an E.164-style numeric — used to route SCCP messages between network elements when the sender does not know (or does not want to know) the destination's Point Code. Where Point Codes are network-internal addresses, Global Titles are application-level addresses; the STP translates GT to DPC at routing time. Every MAP query against an HLR uses GT-based routing. ### OCS, IN, and INAP — operator real-time charging explained URL: https://www.broadnet.me/answers/ocs-in-inap-explained · Markdown: https://www.broadnet.me/answers/ocs-in-inap-explained.md · Last reviewed: 2026-05-28 OCS (Online Charging System), IN (Intelligent Network), and INAP (Intelligent Network Application Protocol) are the operator-side components that decide, in real time, whether a subscriber can complete a call, send an SMS, or use a kilobyte of data — and how much to charge. For prepaid networks they are non-negotiable; for postpaid they are increasingly used for plan policy enforcement. ### UDH — User Data Header in SMS explained URL: https://www.broadnet.me/answers/what-is-udh-sms · Markdown: https://www.broadnet.me/answers/what-is-udh-sms.md · Last reviewed: 2026-05-28 UDH (User Data Header) is the 6-byte (or longer) prefix attached to the body of an SMS to carry control information — most importantly the concatenation header that tells the recipient handset how to stitch a multi-part long SMS back together. UDH is also how WAP push, OTA SIM update messages, and binary SMS payloads are framed. Without UDH, SMS would have remained a strictly 160-character protocol. ### UCS-2 — Unicode SMS encoding explained URL: https://www.broadnet.me/answers/what-is-ucs-2-sms · Markdown: https://www.broadnet.me/answers/what-is-ucs-2-sms.md · Last reviewed: 2026-05-28 UCS-2 is the 16-bit Unicode encoding used by SMS when the message body contains any character that is not in the GSM 7-bit alphabet. Arabic, Chinese, Cyrillic, Vietnamese, emoji, and curly quotes all force a message to UCS-2. The trade-off: a UCS-2 SMS carries only 70 characters per segment (vs 160 for GSM 7-bit) — so a 150-character Arabic message costs three billable segments where the same-length English message costs one. ### ATG — Anti Traffic Generation in A2P firewalls URL: https://www.broadnet.me/answers/what-is-atg-firewall · Markdown: https://www.broadnet.me/answers/what-is-atg-firewall.md · Last reviewed: 2026-10-01 ATG (Anti Traffic Generation) is the umbrella term for the set of techniques an operator-side SMS firewall uses to detect and stop artificially-generated SMS traffic — pumped OTPs, SIM-box-originated A2P, bot-driven smishing campaigns, and the various flavours of grey-route abuse that look like organic traffic but aren't. ATG is what stands between the operator's revenue and the always-evolving fraud market. ### EDR vs CDR — what's the difference? URL: https://www.broadnet.me/answers/edr-vs-cdr · Markdown: https://www.broadnet.me/answers/edr-vs-cdr.md · Last reviewed: 2026-07-25 CDR (Call Detail Record) is the operator's billing record for a single chargeable event — a call, an SMS, a data session — typically generated at the network element that mediated the event (MSC, SMSC, GGSN, OCS). EDR (Event Detail Record) is the broader analytics-and-application-layer record that captures everything happening around an event: not just the billed call, but the platform-level metadata that surrounds it. CDRs are what get billed; EDRs are what get analysed. ### MTTR — Mean Time To Recovery explained URL: https://www.broadnet.me/answers/what-is-mttr · Markdown: https://www.broadnet.me/answers/what-is-mttr.md · Last reviewed: 2026-10-01 MTTR (Mean Time To Recovery, sometimes Mean Time To Restore or Mean Time To Repair) is the average time from when a service incident begins to when normal service is restored. It is the single most actionable operational KPI on a telecom platform — every minute of MTTR reduction directly translates to fewer subscriber complaints, fewer SLA breach credits, and lower revenue loss during incidents. ### MAP-PSI — Provide-Subscriber-Info, and why it matters for SS7 security URL: https://www.broadnet.me/answers/ss7-map-provide-subscriber-info · Markdown: https://www.broadnet.me/answers/ss7-map-provide-subscriber-info.md · Last reviewed: 2026-05-28 MAP-PROVIDE-SUBSCRIBER-INFO (MAP-PSI) is an SS7 MAP operation that lets one network element query another for subscriber state — typically the serving MSC, the current location (Cell-ID and LAI), and the IMEI. It was designed for legitimate inter-operator uses (roaming partner queries, lawful intercept, network-internal services), but it became one of the canonical SS7 attack-surface operations and is now tightly controlled by SS7 signalling firewalls. ### MAP-SRI-for-SM — Send-Routing-Info-for-SM, and SS7 SMS security URL: https://www.broadnet.me/answers/ss7-map-send-routing-info-for-sm · Markdown: https://www.broadnet.me/answers/ss7-map-send-routing-info-for-sm.md · Last reviewed: 2026-07-22 MAP-SEND-ROUTING-INFO-FOR-SM (MAP-SRI-for-SM) is the SS7 MAP operation an SMSC sends to a recipient's HLR to ask "where is this subscriber right now, and how do I deliver an SMS to them?" The response includes the IMSI and the serving MSC address — without which no cross-operator SMS can be delivered. It is also, historically, the single most-abused SS7 operation in the world, and the centrepiece of SS7 firewall policy. ### What is P2A SMS? URL: https://www.broadnet.me/answers/what-is-p2a-sms · Markdown: https://www.broadnet.me/answers/what-is-p2a-sms.md · Last reviewed: 2026-07-22 P2A (person-to-application) SMS is a message a mobile subscriber sends from their handset to a business application — texting a keyword like STOP, HELP, BALANCE, or a competition code to a short code or virtual long number. It is the inbound, mobile-originated counterpart to A2P (application-to-person) SMS, and the mechanism behind two-way SMS, opt-in keywords, and conversational campaigns. ### What is GSM-7 encoding? URL: https://www.broadnet.me/answers/what-is-gsm-7 · Markdown: https://www.broadnet.me/answers/what-is-gsm-7.md · Last reviewed: 2026-07-22 GSM-7 is the default 7-bit character encoding for SMS, defined in 3GPP TS 23.038. It covers the basic Latin alphabet, digits, and punctuation — roughly 128 characters — and fits 160 characters into a single SMS segment. Any character outside the GSM-7 set (emoji, Arabic, Cyrillic, accented Latin such as é or ñ) forces the whole message into UCS-2, which drops the limit to 70 characters per segment. ### What is an HLR (Home Location Register)? URL: https://www.broadnet.me/answers/what-is-hlr · Markdown: https://www.broadnet.me/answers/what-is-hlr.md · Last reviewed: 2026-09-30 The HLR (Home Location Register) is the central subscriber database in a 2G/3G mobile network. It stores each subscriber's MSISDN, IMSI, service entitlements, and the address of the MSC/VLR currently serving them. When an SMS arrives, the destination operator's SMSC queries the HLR over SS7 MAP (SendRoutingInfoForSM) to locate the subscriber before delivery. In 4G/5G the HSS — and later the 5G UDM — replaces it. The HLR is the network element itself; querying it from outside the operator is a separate service, HLR Lookup — see /answers/what-is-hlr-lookup. ### What is an MSISDN? URL: https://www.broadnet.me/answers/what-is-msisdn · Markdown: https://www.broadnet.me/answers/what-is-msisdn.md · Last reviewed: 2026-07-22 MSISDN (Mobile Subscriber ISDN Number) is the technical name for a phone number — the E.164-formatted number (country code plus national subscriber number, up to 15 digits) used to route calls and SMS to a subscriber. It is the value you put in the `to` field of an SMS API call. The MSISDN is distinct from the IMSI, the internal SIM identifier the network uses on the signalling plane and never exposes to other subscribers. ### What is an IMSI? URL: https://www.broadnet.me/answers/what-is-imsi · Markdown: https://www.broadnet.me/answers/what-is-imsi.md · Last reviewed: 2026-07-22 IMSI (International Mobile Subscriber Identity) is the globally unique identifier a mobile network uses to recognise a subscriber. Stored on the SIM/eUICC and in the HLR/HSS, it is up to 15 digits: a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a subscriber identity (MSIN). Unlike the MSISDN — the dialable phone number — the IMSI lives on the signalling plane and is never exposed to other subscribers. ### What is an IMEI? URL: https://www.broadnet.me/answers/what-is-imei · Markdown: https://www.broadnet.me/answers/what-is-imei.md · Last reviewed: 2026-07-22 IMEI (International Mobile Equipment Identity) is the 15-digit serial number that identifies a physical handset, not the subscriber. Where the IMSI identifies the SIM and the MSISDN is the phone number, the IMEI identifies the device itself. Operators use it to block stolen handsets through the EIR (Equipment Identity Register) and to enforce device-based policy. It plays no direct role in SMS routing but often appears alongside the IMSI in fraud analysis. ### What is an ESME? URL: https://www.broadnet.me/answers/what-is-esme · Markdown: https://www.broadnet.me/answers/what-is-esme.md · Last reviewed: 2026-07-22 ESME (External Short Messaging Entity) is the SMPP term for any application outside the SMSC that submits or receives SMS. In an A2P deployment your gateway is the ESME, binding to the operator's SMSC over SMPP. An ESME binds in one of three session modes — Transmitter (send-only), Receiver (receive-only), or Transceiver (both directions on one connection, added in SMPP 3.4). Modern deployments almost always use a single Transceiver bind. ### What is a VLR (Visitor Location Register)? URL: https://www.broadnet.me/answers/what-is-vlr · Markdown: https://www.broadnet.me/answers/what-is-vlr.md · Last reviewed: 2026-07-22 The VLR (Visitor Location Register) is a temporary subscriber database attached to each MSC. When a handset camps on an MSC — at home or roaming — the VLR pulls a working copy of that subscriber's profile from the HLR, so the serving network can set up calls and deliver SMS without querying the home HLR every time. It is the local cache to the HLR's system of record. ### What is an MSC (Mobile Switching Centre)? URL: https://www.broadnet.me/answers/what-is-msc · Markdown: https://www.broadnet.me/answers/what-is-msc.md · Last reviewed: 2026-07-22 The MSC (Mobile Switching Centre) is the core 2G/3G network node that switches voice calls and relays SMS for the handsets currently in its coverage area. For a mobile-terminated SMS, the sending SMSC uses SS7 MAP MT-ForwardSM to hand the message to the recipient's serving MSC, which pages the handset and delivers it. Each MSC is paired with a VLR that caches subscriber data for the devices it serves. ### What is AIT (Artificially Inflated Traffic)? URL: https://www.broadnet.me/answers/what-is-ait · Markdown: https://www.broadnet.me/answers/what-is-ait.md · Last reviewed: 2026-07-22 AIT (artificially inflated traffic) — also called SMS pumping or toll fraud — is a scheme where fraudsters use bots to trigger huge volumes of OTP or verification SMS to number ranges they control on a complicit operator, then collect a share of the termination fees. The victim is the business paying for the messages. Left unchecked, AIT can inflate an OTP bill many times over before anyone notices. ### What is E.164? URL: https://www.broadnet.me/answers/what-is-e164 · Markdown: https://www.broadnet.me/answers/what-is-e164.md · Last reviewed: 2026-07-22 E.164 is the ITU-T international public telecommunication numbering plan — the worldwide standard format for phone numbers. An E.164 number is a country code followed by a national subscriber number, up to 15 digits total, written with a leading '+' (for example +9714XXXXXXX). Every MSISDN follows E.164. Passing numbers in strict E.164 form is the single most reliable way to avoid routing and delivery failures on an A2P SMS API. ### What is SIM swap fraud? URL: https://www.broadnet.me/answers/what-is-sim-swap-fraud · Markdown: https://www.broadnet.me/answers/what-is-sim-swap-fraud.md · Last reviewed: 2026-09-10 SIM swap fraud is an attack where a criminal persuades or bribes a mobile operator to move a victim's number onto a SIM the attacker controls. Every SMS one-time passcode for that number then arrives on the attacker's handset, which is why SMS OTP alone is not sufficient authentication for a high-value action. ### What is DLT registration in India? URL: https://www.broadnet.me/answers/what-is-dlt-registration-india · Markdown: https://www.broadnet.me/answers/what-is-dlt-registration-india.md · Last reviewed: 2026-09-10 DLT (Distributed Ledger Technology) registration is the mandatory Indian regime, set by TRAI, under which every commercial SMS sender, sender ID and message template must be registered on an operator-run blockchain platform before traffic will deliver. Unregistered or mismatched messages are blocked by the operator, not merely rate-limited. ### What is TCPA compliance for SMS? URL: https://www.broadnet.me/answers/what-is-tcpa-compliance · Markdown: https://www.broadnet.me/answers/what-is-tcpa-compliance.md · Last reviewed: 2026-09-10 The Telephone Consumer Protection Act is the United States law governing calls and text messages to mobile numbers. For A2P senders it sets the consent standard, the opt-out obligation and the time-of-day restriction — and it carries statutory damages per message, which is why US messaging programmes are audited more carefully than most. ### What are SMS quiet hours? URL: https://www.broadnet.me/answers/what-are-sms-quiet-hours · Markdown: https://www.broadnet.me/answers/what-are-sms-quiet-hours.md · Last reviewed: 2026-09-10 Quiet hours are the periods when a market forbids or restricts commercial messaging — typically overnight, sometimes also on religious or national holidays. The window is set per country by the regulator or the operators, applies to the recipient's local time, and usually exempts transactional traffic such as one-time passcodes. ### What is SMPP window size? URL: https://www.broadnet.me/answers/what-is-smpp-window-size · Markdown: https://www.broadnet.me/answers/what-is-smpp-window-size.md · Last reviewed: 2026-09-10 The window is the number of SMPP PDUs an ESME may have in flight — submitted but not yet acknowledged — on a single bind at any moment. It is the single biggest determinant of the throughput you get from a bind, and the setting most often left at a default that silently caps an integration far below its agreed rate. ### SMS OTP or an authenticator app — which should I use? URL: https://www.broadnet.me/answers/sms-otp-vs-authenticator-app · Markdown: https://www.broadnet.me/answers/sms-otp-vs-authenticator-app.md · Last reviewed: 2026-09-10 Use both, for different jobs. An authenticator app is the stronger factor and cannot be intercepted by a SIM swap, but it requires the user to install and enrol something. SMS OTP is weaker but reaches any handset in any market with nothing installed, which is why it remains the only option that works for every user you have. ### What is STIR/SHAKEN? URL: https://www.broadnet.me/answers/what-is-stir-shaken · Markdown: https://www.broadnet.me/answers/what-is-stir-shaken.md · Last reviewed: 2026-07-22 STIR/SHAKEN is a framework of IETF and ATIS standards that cryptographically signs the calling number on a VoIP call so terminating carriers can verify the caller ID has not been spoofed. STIR (Secure Telephone Identity Revisited) defines the signed PASSporT token; SHAKEN (Signature-based Handling of Asserted information using toKENs) defines how carriers apply it. It is mandated for US and Canadian carriers to fight illegal caller-ID spoofing and robocalls. See /answers/what-is-cli and /answers/what-is-sender-id-spoofing. ### What is CLI (Calling Line Identification)? URL: https://www.broadnet.me/answers/what-is-cli · Markdown: https://www.broadnet.me/answers/what-is-cli.md · Last reviewed: 2026-07-22 CLI (Calling Line Identification) is the telephone number presented to the called party as the origin of a call — the voice-network equivalent of an SMS sender ID. It is carried in call signaling (SS7 IAM, or SIP From / P-Asserted-Identity). CLI can be legitimately set — a business showing its main number — or fraudulently spoofed, which is exactly why authentication frameworks like STIR/SHAKEN exist. See /answers/what-is-ani, /answers/what-is-stir-shaken, and /answers/what-is-did. ### What is ANI (Automatic Number Identification)? URL: https://www.broadnet.me/answers/what-is-ani · Markdown: https://www.broadnet.me/answers/what-is-ani.md · Last reviewed: 2026-07-22 ANI (Automatic Number Identification) is a telephony feature that identifies the originating/billing number of a caller and passes it to the receiving end. Originating in the North American PSTN, ANI is often used interchangeably with CLI, but they differ: ANI reflects the billing line and is harder to alter, while CLI (caller ID) is the display number the callee sees and can be spoofed. See /answers/what-is-cli and /answers/what-is-did. ### What is a DID (Direct Inward Dialing) number? URL: https://www.broadnet.me/answers/what-is-did · Markdown: https://www.broadnet.me/answers/what-is-did.md · Last reviewed: 2026-07-22 A DID (Direct Inward Dialing) number — also called a virtual or direct-dial number — is a phone number that routes inbound calls (and often SMS) straight to a specific endpoint such as an IVR, an agent, or an application, without a dedicated physical line per number. In programmable voice, DIDs are rented per number per month and provisioned in code to receive calls or two-way messages. See /answers/what-is-ivr and /products/voice. ### What is IVR (Interactive Voice Response)? URL: https://www.broadnet.me/answers/what-is-ivr · Markdown: https://www.broadnet.me/answers/what-is-ivr.md · Last reviewed: 2026-07-22 IVR (Interactive Voice Response) is an automated telephony system that plays voice prompts and collects caller input via keypad (DTMF) tones or speech recognition, then routes the call or serves information without a human agent. Programmable-voice IVR flows are built in code — 'press 1 for sales' menus, self-service balance checks, or voice-OTP delivery. See /answers/what-is-acd, /answers/what-is-did, /products/voice, and /products/voice. ### What is ACD (Average Call Duration)? URL: https://www.broadnet.me/answers/what-is-acd · Markdown: https://www.broadnet.me/answers/what-is-acd.md · Last reviewed: 2026-07-22 ACD (Average Call Duration) is the mean length of answered calls over a period — total talk time divided by the number of answered calls. It is a core voice-traffic KPI: combined with call volume it gives the Erlang load used to size trunks and agents, and alongside ASR it reveals route and service quality. (Not to be confused with an Automatic Call Distributor.) Size capacity with the /tools/erlang-calculator. See /answers/what-is-asr and /answers/what-is-pdd. ### What is PDD (Post-Dial Delay)? URL: https://www.broadnet.me/answers/what-is-pdd · Markdown: https://www.broadnet.me/answers/what-is-pdd.md · Last reviewed: 2026-07-22 PDD (Post-Dial Delay) is the time between the moment a call is initiated — a caller finishing dialing, or a system placing a call — and the moment ringing is heard or the call connects. High PDD, usually caused by long signaling paths or route-hunting across multiple carriers, makes callers hang up before connection and is a classic symptom of low-quality wholesale voice routes. See /answers/what-is-asr, /answers/what-is-acd, and /tools/erlang-calculator. ### What is TPS (Transactions Per Second)? URL: https://www.broadnet.me/answers/what-is-tps · Markdown: https://www.broadnet.me/answers/what-is-tps.md · Last reviewed: 2026-07-22 TPS (transactions per second) — also called MPS or send rate — is the throughput ceiling of a messaging bind or account: how many SMS submit_sm PDUs the SMSC accepts per second before it returns throttling errors. A2P binds are provisioned at a contracted TPS; exceeding it triggers ESME_RTHROTTLED responses. TPS, not raw volume, determines how fast a campaign or OTP burst clears. See /answers/what-is-throughput-sla, /answers/what-is-cps, and /tools/smpp-error-codes. ### What is CPS (Calls Per Second)? URL: https://www.broadnet.me/answers/what-is-cps · Markdown: https://www.broadnet.me/answers/what-is-cps.md · Last reviewed: 2026-07-22 CPS (calls per second) is the voice-network equivalent of messaging TPS: the maximum rate at which a platform or carrier trunk accepts new call attempts. It caps outbound dialing bursts — voice-OTP campaigns, notifications, or contact-center diallers — independently of how many calls are concurrently active. Exceeding the contracted CPS causes call attempts to be rejected or queued. See /answers/what-is-tps, /answers/what-is-pdd, and /tools/erlang-calculator. ### What is a DNC (Do Not Call) list? URL: https://www.broadnet.me/answers/what-is-dnc · Markdown: https://www.broadnet.me/answers/what-is-dnc.md · Last reviewed: 2026-07-22 A DNC (Do Not Call) list — also called Do Not Disturb (DND) in some markets — is a register of phone numbers whose owners have opted out of marketing calls or messages. Many regulators run national DNC/DND registries, and scrubbing your list against them before a campaign is a legal requirement in most markets. Honouring STOP/opt-out keywords is the SMS equivalent. See /answers/what-is-p2a-sms and /answers/gdpr-for-messaging. ### What is an SMS short code? URL: https://www.broadnet.me/answers/what-is-short-code · Markdown: https://www.broadnet.me/answers/what-is-short-code.md · Last reviewed: 2026-07-22 A short code is a special 3-8 digit number, shorter than a full phone number, leased for high-throughput A2P and P2A SMS — marketing campaigns, keyword opt-ins, and two-way programmes. Short codes are provisioned per country, approved by operators, and carry the highest send rates and best deliverability, but cost more and take weeks to activate. See the fuller comparison at /answers/what-is-short-code-vs-long-code and /answers/what-is-long-code. ### What is a long code? URL: https://www.broadnet.me/answers/what-is-long-code · Markdown: https://www.broadnet.me/answers/what-is-long-code.md · Last reviewed: 2026-07-22 A long code is a standard-length E.164 phone number — a virtual mobile or geographic number — used to send and receive SMS. Unlike a short code it supports two-way conversational messaging and is quick and cheap to provision, but has lower throughput and, on unregistered routes, weaker deliverability. In the United States, A2P long-code traffic must be registered as 10DLC. See /answers/what-is-short-code and /answers/what-is-short-code-vs-long-code. ### What is MMS (Multimedia Messaging Service)? URL: https://www.broadnet.me/answers/what-is-mms · Markdown: https://www.broadnet.me/answers/what-is-mms.md · Last reviewed: 2026-07-22 MMS (Multimedia Messaging Service) is the carrier messaging standard that extends SMS to carry images, audio, video, and longer text. Messages transit an MMSC — rather than an SMSC — and are fetched by the handset over the data network. A2P MMS is used for rich marketing where supported, though RCS Business Messaging and WhatsApp increasingly replace it. See /answers/what-is-mmsc, /answers/what-is-rcs-business-messaging, and /products/mms. ### What is an HSS (Home Subscriber Server)? URL: https://www.broadnet.me/answers/what-is-hss · Markdown: https://www.broadnet.me/answers/what-is-hss.md · Last reviewed: 2026-07-22 The HSS (Home Subscriber Server) is the central subscriber database of a 4G LTE / IMS core network — the Diameter-based successor to the 2G/3G HLR. It stores subscriber identities, authentication keys, and service profiles, and answers S6a/S6d signaling from the MME during attach and SMS delivery. On 5G standalone its role passes to the UDM. See /answers/what-is-hlr, /answers/diameter-s6a-explained, and /products/hlr-lookup. ### What is M3UA? URL: https://www.broadnet.me/answers/what-is-m3ua · Markdown: https://www.broadnet.me/answers/what-is-m3ua.md · Last reviewed: 2026-07-22 M3UA (MTP Level 3 User Adaptation) is a SIGTRAN protocol that carries SS7 MTP3-user signaling — SCCP and ISUP — over IP using SCTP, letting legacy SS7 applications run across modern IP networks without TDM links. It is the transport most operators use to reach SS7/MAP peers today, and the layer an SS7 signaling firewall inspects. See /answers/what-is-sigtran, /answers/sigtran-adaptation-layers, and /answers/what-is-sccp. ### What is SCCP? URL: https://www.broadnet.me/answers/what-is-sccp · Markdown: https://www.broadnet.me/answers/what-is-sccp.md · Last reviewed: 2026-07-22 SCCP (Signalling Connection Control Part) is the SS7 network-layer protocol that adds global-title routing and subsystem addressing on top of MTP, so signaling can reach nodes — HLRs, MSCs, SMSCs — by global title rather than a fixed point code. TCAP and MAP ride on SCCP, and SCCP-level Global Title translation is where operators and firewalls steer and screen inter-network SMS signaling. See /answers/what-is-tcap, /answers/ss7-global-title, and /answers/what-is-m3ua. ### What is TCAP? URL: https://www.broadnet.me/answers/what-is-tcap · Markdown: https://www.broadnet.me/answers/what-is-tcap.md · Last reviewed: 2026-07-22 TCAP (Transaction Capabilities Application Part) is the SS7 layer that manages request/response dialogues between network nodes, carrying application operations such as MAP on top of SCCP. Every HLR query and MT-ForwardSM that delivers an SMS is a TCAP transaction. Because TCAP wraps the MAP operations attackers abuse, it is a key inspection point for SS7 signaling firewalls. See /answers/what-is-sccp, /answers/ss7-map-explained, and /operators/ss7-firewall. ### What is GTT (Global Title Translation)? URL: https://www.broadnet.me/answers/what-is-gtt · Markdown: https://www.broadnet.me/answers/what-is-gtt.md · Last reviewed: 2026-07-22 GTT (Global Title Translation) is the SCCP-layer function that resolves a global title — a network address such as an E.164 or E.214 number — into the point code and subsystem number needed to route SS7 signaling to the right node: an HLR, SMSC, or MSC. Because senders address a global title rather than a physical point code, GTT is where operators (and SS7 firewalls) steer and screen inter-network SMS and MAP signaling. See /answers/ss7-global-title, /answers/what-is-sccp, and /operators/ss7-firewall. ### What is SCTP (Stream Control Transmission Protocol)? URL: https://www.broadnet.me/answers/what-is-sctp · Markdown: https://www.broadnet.me/answers/what-is-sctp.md · Last reviewed: 2026-07-22 SCTP (Stream Control Transmission Protocol, RFC 4960) is the transport-layer protocol that carries SIGTRAN signaling over IP. Unlike TCP it is message-oriented, multi-streamed (so one lost packet does not head-of-line-block the others), and multi-homed (an association spans multiple IP paths for instant failover) — the resilience properties a telecom control plane needs. M3UA and the other SIGTRAN adaptation layers ride on SCTP to move SS7 over IP. See /answers/sigtran-explained, /answers/what-is-m3ua, and /answers/what-is-sigtran. ### What is ENUM (E.164 Number Mapping)? URL: https://www.broadnet.me/answers/what-is-enum · Markdown: https://www.broadnet.me/answers/what-is-enum.md · Last reviewed: 2026-07-22 ENUM (E.164 Number Mapping, RFC 6116) is an IETF standard that maps an E.164 phone number to internet resources — SIP URIs, email, web — by encoding the number as a domain name and looking it up in DNS. It lets carriers and enterprises route calls and messages to IP endpoints straight from a phone number, and underpins number portability and VoIP interconnect. See /answers/what-is-e164, /answers/what-is-mnp, and /answers/programmable-voice. ### What is an MSRN (Mobile Station Roaming Number)? URL: https://www.broadnet.me/answers/what-is-msrn · Markdown: https://www.broadnet.me/answers/what-is-msrn.md · Last reviewed: 2026-07-22 An MSRN (Mobile Station Roaming Number) is a temporary number the visited network's VLR allocates so an incoming call can be routed to a subscriber's current serving MSC. During call setup the HLR requests it over MAP (Provide-Roaming-Number); the network uses it to route the call, then releases it. It is a routing number, never dialed by a user, and it is how roaming and forwarded calls reach the right switch. See /answers/what-is-vlr, /answers/what-is-hlr, and /answers/ss7-map-explained. ### What is TAP (Transferred Account Procedure)? URL: https://www.broadnet.me/answers/what-is-tap · Markdown: https://www.broadnet.me/answers/what-is-tap.md · Last reviewed: 2026-07-22 TAP (Transferred Account Procedure) is the GSMA standard file format — TAP3, defined in GSMA TD.57 — that a visited operator uses to send records of a roamer's calls, messages, and data usage back to their home operator for inter-operator billing settlement. TAP files are exchanged through data clearing houses, usually daily. Its near-real-time companion, NRTRDE, exists to catch roaming fraud faster than a daily TAP cycle allows. See /answers/what-is-nrtrde and /answers/edr-vs-cdr. ### What is NRTRDE (Near Real Time Roaming Data Exchange)? URL: https://www.broadnet.me/answers/what-is-nrtrde · Markdown: https://www.broadnet.me/answers/what-is-nrtrde.md · Last reviewed: 2026-07-22 NRTRDE (Near Real Time Roaming Data Exchange), defined in GSMA TD.35, requires a visited operator to send roaming usage records to the home operator within four hours of the event — far faster than the daily TAP file. Its purpose is fraud control: high-value roaming fraud such as SIM-box or premium-rate abuse can run up huge losses before a daily TAP cycle would surface it, so NRTRDE shortens the detection window. See /answers/what-is-tap and /answers/telecom-fraud-prevention. ### What is RCS MaaP (Messaging as a Platform)? URL: https://www.broadnet.me/answers/what-is-rcs-maap · Markdown: https://www.broadnet.me/answers/what-is-rcs-maap.md · Last reviewed: 2026-07-22 RCS MaaP (Messaging as a Platform) is the GSMA architecture that lets brands and chatbots reach subscribers over RCS through the carrier's messaging platform. MaaP hosts business agents, applies verification, and connects them to the RCS network, so an aggregator or brand integrates once to reach every subscriber on that platform. It is the plumbing behind RCS Business Messaging — the layer where verified agents, bots, and rich-card content are managed. See /answers/rcs-business-messaging and /answers/what-is-rcs-business-messaging. ### What is toll-free messaging? URL: https://www.broadnet.me/answers/what-is-toll-free-messaging · Markdown: https://www.broadnet.me/answers/what-is-toll-free-messaging.md · Last reviewed: 2026-09-30 Toll-free messaging is A2P SMS and MMS sent from a toll-free number — in North America the 800, 833, 844, 855, 866, 877, and 888 prefixes. Toll-free numbers must be verified with the carriers before they can send A2P at scale; once verified they offer high throughput and broad reach without the cost and lead time of a short code. It is a common alternative to 10DLC for higher-volume US traffic. See /answers/what-is-a2p-10dlc and /answers/what-is-short-code. ### What is Wangiri fraud? URL: https://www.broadnet.me/answers/what-is-wangiri-fraud · Markdown: https://www.broadnet.me/answers/what-is-wangiri-fraud.md · Last reviewed: 2026-07-22 Wangiri (Japanese for 'one ring and cut') is a voice fraud in which scammers place brief missed calls from premium-rate international numbers, hoping victims call back and get charged high per-minute fees the fraudster shares in. An SMS variant lures the call-back with a text. Defences include call-pattern analytics, premium-rate destination blocking, and subscriber education. See /answers/telecom-fraud-prevention and /answers/what-is-cli. ### What is number masking? URL: https://www.broadnet.me/answers/what-is-number-masking · Markdown: https://www.broadnet.me/answers/what-is-number-masking.md · Last reviewed: 2026-07-22 Number masking (call and SMS anonymization) uses a temporary proxy number to connect two parties — a rider and driver, a buyer and seller — so neither sees the other's real number. The platform maps both real numbers to the proxy and relays calls and texts through it, protecting privacy and keeping the conversation on-platform for safety and auditability. It is built on DID numbers and programmable voice and SMS. See /answers/what-is-did and /answers/programmable-voice. ### What is RTP (Real-time Transport Protocol)? URL: https://www.broadnet.me/answers/what-is-rtp · Markdown: https://www.broadnet.me/answers/what-is-rtp.md · Last reviewed: 2026-07-22 RTP (Real-time Transport Protocol, RFC 3550) is the protocol that carries the actual audio and video media of a VoIP call over IP, usually over UDP. While SIP handles call setup, RTP streams the encoded voice packets with sequence numbers and timestamps so the receiver can reorder them and play them back in time. Its companion RTCP reports on jitter and packet loss; SRTP adds encryption. See /answers/what-is-sip, /answers/what-is-srtp, and /answers/voip-quality. ### What is SDP (Session Description Protocol)? URL: https://www.broadnet.me/answers/what-is-sdp · Markdown: https://www.broadnet.me/answers/what-is-sdp.md · Last reviewed: 2026-07-22 SDP (Session Description Protocol, RFC 8866) is the text format that describes a media session — which codecs, IP addresses, ports, and parameters each side will use. It is not a transport itself; it rides inside SIP (or WebRTC) as an offer/answer exchange, so the two endpoints agree on how to send RTP before the media flows. Codec negotiation and NAT candidate exchange both happen in SDP. See /answers/what-is-sip, /answers/what-is-voice-codec, and /answers/what-is-webrtc. ### What is DTMF? URL: https://www.broadnet.me/answers/what-is-dtmf · Markdown: https://www.broadnet.me/answers/what-is-dtmf.md · Last reviewed: 2026-07-22 DTMF (Dual-Tone Multi-Frequency) is the signaling produced when a caller presses a phone keypad — each digit is a pair of audio tones the network decodes. It is how callers navigate IVR menus ('press 1 for sales') and enter data like account numbers or a voice-OTP confirmation. In VoIP, DTMF is commonly sent out-of-band (RFC 2833 / telephone-event) rather than as in-band audio, so it survives compression. See /answers/what-is-ivr and /answers/programmable-voice. ### What are voice codecs (G.711, Opus)? URL: https://www.broadnet.me/answers/what-is-voice-codec · Markdown: https://www.broadnet.me/answers/what-is-voice-codec.md · Last reviewed: 2026-07-22 A voice codec encodes analogue speech into digital packets for transport and decodes it back, trading bandwidth against audio quality. G.711 is the classic uncompressed toll-quality codec at ~64 kbit/s, ubiquitous and low-latency but bandwidth-heavy. Opus (RFC 6716) adapts its bitrate dynamically and is highly resilient to packet loss, making it the modern choice for VoIP and WebRTC. Transcoding between codecs on a call path costs quality and adds delay. See /answers/voip-quality, /answers/what-is-webrtc, and /products/voice. ### What is jitter in VoIP? URL: https://www.broadnet.me/answers/what-is-jitter · Markdown: https://www.broadnet.me/answers/what-is-jitter.md · Last reviewed: 2026-07-22 Jitter is the variation in the arrival time of RTP voice packets. Packets sent at even intervals arrive unevenly because of network congestion and varying routes, and that unevenness garbles audio if played straight out. A jitter buffer holds incoming packets briefly and releases them at a steady rate to smooth playback — trading a little added delay for cleaner sound. Excessive jitter beyond the buffer's depth causes dropouts. See /answers/voip-quality, /answers/what-is-rtp, and /answers/what-is-mos. ### What is MOS (Mean Opinion Score)? URL: https://www.broadnet.me/answers/what-is-mos · Markdown: https://www.broadnet.me/answers/what-is-mos.md · Last reviewed: 2026-07-22 MOS (Mean Opinion Score) is the standard measure of voice call quality, rated 1 (bad) to 5 (excellent). 4.0 and above is toll quality; below 3.5 is noticeably degraded. Originally a human listening test, MOS is now usually estimated automatically (per ITU-T models) from measured latency, jitter, and packet loss. It is the single number carriers use to compare routes and diagnose a poor call path. See /answers/voip-quality, /answers/what-is-jitter, and /products/voice. ### What is WebRTC? URL: https://www.broadnet.me/answers/what-is-webrtc · Markdown: https://www.broadnet.me/answers/what-is-webrtc.md · Last reviewed: 2026-07-22 WebRTC (Web Real-Time Communication) is an open standard that lets browsers and apps exchange real-time audio, video, and data peer-to-peer without a plugin. It bundles media capture, the Opus and VP8/VP9 codecs, encrypted transport (SRTP), and NAT traversal (ICE/STUN/TURN), negotiating sessions with SDP. WebRTC powers in-browser click-to-call, video, and voice-agent experiences, often bridged to SIP and the PSTN by a gateway. See /answers/what-is-sip, /answers/what-is-srtp, and /answers/what-is-nat-traversal. ### What is LCR (Least-Cost Routing)? URL: https://www.broadnet.me/answers/what-is-lcr · Markdown: https://www.broadnet.me/answers/what-is-lcr.md · Last reviewed: 2026-07-22 LCR (Least-Cost Routing) automatically selects the cheapest available route for each message or call from a rate table of every path to a destination. Mature LCR weighs price against quality and compliance, not price alone — because the cheapest SMS path is often a grey route whose delivery is unreliable and whose sender IDs break. The right target is least effective cost: price per successfully delivered message. See /answers/sms-routing-lcr, /answers/what-is-grey-route-sms, and /operators/smsc-gateway. ### What is a concatenated SMS? URL: https://www.broadnet.me/answers/what-is-concatenated-sms · Markdown: https://www.broadnet.me/answers/what-is-concatenated-sms.md · Last reviewed: 2026-07-22 A concatenated (or multipart) SMS is a message longer than a single segment — 160 GSM-7 characters, or 70 in UCS-2 — split across multiple SMS parts and reassembled into one message on the handset. A User Data Header (UDH) in each part carries a reference number and sequence so the phone stitches them in order. Concatenation reduces the per-segment payload to 153/67 characters to make room for the UDH, and each part is billed separately. See /answers/what-is-udh-sms, /answers/what-is-encoding-gsm-7-ucs-2, and /tools/sms-segment-calculator. ### What is SRTP (Secure RTP)? URL: https://www.broadnet.me/answers/what-is-srtp · Markdown: https://www.broadnet.me/answers/what-is-srtp.md · Last reviewed: 2026-07-22 SRTP (Secure Real-time Transport Protocol, RFC 3711) is the encrypted profile of RTP: it encrypts and authenticates the voice and video media of a VoIP call so it can't be eavesdropped or tampered with in transit. It is typically paired with SIP over TLS (which protects the signaling) and with DTLS key exchange in WebRTC, giving end-to-end call confidentiality. See /answers/what-is-rtp, /answers/what-is-sip, and /answers/what-is-webrtc. ### What is the PSTN? URL: https://www.broadnet.me/answers/what-is-pstn · Markdown: https://www.broadnet.me/answers/what-is-pstn.md · Last reviewed: 2026-07-22 The PSTN (Public Switched Telephone Network) is the traditional circuit-switched telephone network of landlines, exchanges, and interconnects that predates VoIP. Programmable voice and SIP trunking reach it through PSTN termination and origination, so a call placed by an API can ring any ordinary phone number and inbound calls from landlines can reach an application. Much of the PSTN core is now IP, but the numbering plan and reach it represents remain central to voice. See /answers/voice-api-sip-trunking, /answers/what-is-did, and /products/voice. ### What is an SBC (Session Border Controller)? URL: https://www.broadnet.me/answers/what-is-sbc · Markdown: https://www.broadnet.me/answers/what-is-sbc.md · Last reviewed: 2026-07-22 An SBC (Session Border Controller) is the security and control element that sits at the edge of a VoIP network, policing SIP signaling and RTP media as they cross between networks. It handles NAT and firewall traversal, hides internal topology, enforces call admission and rate limits, transcodes codecs when two sides differ, and defends against SIP-based attacks and toll fraud. Every serious SIP trunking and voice-API deployment sits behind one. See /answers/what-is-sip, /answers/what-is-nat-traversal, and /answers/voice-api-sip-trunking. ### What is NAT traversal in VoIP? URL: https://www.broadnet.me/answers/what-is-nat-traversal · Markdown: https://www.broadnet.me/answers/what-is-nat-traversal.md · Last reviewed: 2026-07-22 NAT traversal is how a VoIP endpoint behind a router (which rewrites private IP addresses) still receives voice media. Because SIP and RTP carry IP addresses inside their payloads, plain NAT breaks the media path; techniques such as STUN, TURN, and ICE — plus a Session Border Controller on the network edge — discover the public address and relay media when needed so audio flows both ways. It is a common cause of one-way-audio faults. See /answers/what-is-sbc, /answers/what-is-webrtc, and /answers/what-is-sip. ### How do I activate my BroadNet account? URL: https://www.broadnet.me/answers/activate-account · Markdown: https://www.broadnet.me/answers/activate-account.md · Last reviewed: 2026-09-29 Request test access at /signup and a BroadNet engineer replies within one business day with test credentials; your first test message typically goes out about five minutes after you receive them. Test credentials work against the production endpoint, https://api.broadnet.me, and test messages go only to the mobile number you verify, so you can build and test end to end. To reach real recipients you complete business/KYC verification, which unlocks live sending and registered sender IDs, and add billing; production access is then switched on for your account, typically 5–15 business days from request to production. Going live is not a code change. See /developers/quickstart. ### How do I rotate or revoke API keys? URL: https://www.broadnet.me/answers/rotate-api-keys · Markdown: https://www.broadnet.me/answers/rotate-api-keys.md · Last reviewed: 2026-09-29 In the dashboard, go to API keys, generate a new key, deploy it to your applications, then revoke the old key. Revocation is instant, and keys are never logged, so a rotated key stops working immediately with no residual exposure. Rotate on a schedule (for example quarterly) and immediately after any suspected exposure, and treat the token from your test credentials as a production secret: it calls the production endpoint. See /developers/authentication. ### How do I top up my balance? URL: https://www.broadnet.me/answers/top-up · Markdown: https://www.broadnet.me/answers/top-up.md · Last reviewed: 2026-07-22 BroadNet prepaid accounts run on a balance you top up in advance. In the dashboard, go to Billing → add funds to top up by card or bank transfer. Set an auto-recharge threshold so your balance refills automatically and sending never pauses mid-campaign. Enterprise accounts can instead use monthly invoicing with agreed credit terms rather than pre-funding a balance. ### How do I download invoices and statements? URL: https://www.broadnet.me/answers/download-invoices · Markdown: https://www.broadnet.me/answers/download-invoices.md · Last reviewed: 2026-07-22 In the dashboard, go to Billing → Invoices and download any invoice as a PDF. Monthly statements are itemised by channel and destination country so you can see exactly where spend went. For UAE accounts, invoices are VAT-compliant and show your TRN (Tax Registration Number). ### What currencies and payment methods does BroadNet support? URL: https://www.broadnet.me/answers/payment-methods · Markdown: https://www.broadnet.me/answers/payment-methods.md · Last reviewed: 2026-07-22 BroadNet bills in AED and SAR for MENA accounts and in USD for international accounts. You can pay by major credit and debit card or by bank transfer, and enterprise accounts can arrange invoicing with agreed net credit terms instead of pre-funding a balance. ### How do I register an alphanumeric sender ID? URL: https://www.broadnet.me/answers/how-to-register-sender-id · Markdown: https://www.broadnet.me/answers/how-to-register-sender-id.md · Last reviewed: 2026-07-22 Most regulators require alphanumeric sender IDs to be pre-registered before any A2P SMS is accepted, so registration is a prerequisite, not an option. The general path is: choose a compliant sender ID (up to 11 GSM-7 characters), submit your brand, use case, and sample content, then wait for regulator/operator review. Requirements and lead times differ by country — see the country guides for the exact process in each market. ### How much does A2P SMS cost? URL: https://www.broadnet.me/answers/sms-pricing-explained · Markdown: https://www.broadnet.me/answers/sms-pricing-explained.md · Last reviewed: 2026-07-22 A2P SMS is priced per message segment (an MT, or mobile-terminated message), and the rate varies by destination country and operator — from fractions of a cent in some markets to several cents in others, driven mostly by the operator's A2P termination fee. Long messages are split into 160-character (GSM-7) or 70-character (Unicode/UCS-2) segments, and every segment is billed separately. For country-by-country rates see /pricing/sms, and estimate segment counts with /tools/sms-segment-calculator. ### How can I reduce SMS costs? URL: https://www.broadnet.me/answers/how-to-reduce-sms-costs · Markdown: https://www.broadnet.me/answers/how-to-reduce-sms-costs.md · Last reviewed: 2026-07-22 Reduce SMS costs by attacking both the price per message and the number of wasted messages: keep messages inside one segment, stay on GSM-7 encoding, validate numbers before sending so you don't pay to text dead or wrong-country numbers, route over direct agreements to avoid re-sends, register sender IDs so firewalls don't silently drop traffic, and move rich or high-volume flows to the channel with the best economics. The largest saving is usually eliminating failed and duplicate sends, not shaving the unit rate. ### What are SMS OTP best practices? URL: https://www.broadnet.me/answers/sms-otp-best-practices · Markdown: https://www.broadnet.me/answers/sms-otp-best-practices.md · Last reviewed: 2026-07-22 Deliver SMS one-time passwords over a dedicated high-priority route, keep codes short (4–8 digits), expire them quickly (typically 5–10 minutes), enforce single use, and rate-limit requests per number to defend against SMS-pumping fraud. Put the brand name and the code near the start of the message, include no clickable links (so the message can't be confused with phishing), and configure a fallback channel for when SMS is slow. See /products/otp. ### How do I improve SMS delivery rates? URL: https://www.broadnet.me/answers/how-to-improve-sms-delivery-rates · Markdown: https://www.broadnet.me/answers/how-to-improve-sms-delivery-rates.md · Last reviewed: 2026-07-22 Improve SMS delivery rates by sending over direct operator routes, registering your alphanumeric sender IDs, cleaning recipient lists with HLR lookups, using correct GSM-7/Unicode encoding, and monitoring delivery receipts so you catch and re-route failures fast. Most chronic delivery problems trace back to two causes: grey routes that firewalls block, and unregistered sender IDs that operators drop before the message ever reaches a handset. ### How do you use SMS for appointment reminders? URL: https://www.broadnet.me/answers/sms-for-appointment-reminders · Markdown: https://www.broadnet.me/answers/sms-for-appointment-reminders.md · Last reviewed: 2026-07-22 SMS appointment reminders cut no-shows by delivering a timely, high-open-rate reminder with the date, time and location, plus a reply-to-confirm or reply-to-reschedule option using two-way SMS. Because SMS needs no app and is read within minutes, it reaches patients and customers that email and app notifications miss — which is why clinics, healthcare providers, salons and service businesses rely on it. See /products/two-way-sms. ### How do you use SMS for delivery notifications? URL: https://www.broadnet.me/answers/sms-for-delivery-notifications · Markdown: https://www.broadnet.me/answers/sms-for-delivery-notifications.md · Last reviewed: 2026-07-22 SMS delivery notifications keep customers informed at each fulfilment milestone — order confirmed, shipped, out for delivery, delivered — with an optional tracking link and a reply channel to reschedule. SMS is ideal for logistics updates because it is read within minutes and needs no app install, so time-sensitive 'your driver is 10 minutes away' messages actually get seen. Common across e-commerce, retail and logistics; see /solutions/ecommerce-retail. ### How do you use SMS for payment and transaction alerts? URL: https://www.broadnet.me/answers/sms-for-payment-alerts · Markdown: https://www.broadnet.me/answers/sms-for-payment-alerts.md · Last reviewed: 2026-07-22 SMS payment and transaction alerts notify customers in real time about debits, credits, low balances, and suspected fraud — a core requirement for banks, fintechs and payment providers. These messages must be fast, reliable and sent over direct routes with a strong SLA, classified as transactional (never marketing), and free of sensitive data such as full card numbers. See /solutions/banking-finance. ### How do you use SMS for abandoned-cart recovery? URL: https://www.broadnet.me/answers/abandoned-cart-sms · Markdown: https://www.broadnet.me/answers/abandoned-cart-sms.md · Last reviewed: 2026-07-22 Abandoned-cart SMS re-engages shoppers who left items in their basket with a short, timely reminder — often with a product image via RCS or WhatsApp, and sometimes an incentive — recovering revenue that would otherwise be lost. Because it is a marketing message, it requires explicit opt-in and DNC/quiet-hours compliance. It is one of the highest-ROI messaging use cases in e-commerce; see /solutions/ecommerce-retail. ### SMS vs WhatsApp for business — which should you use? URL: https://www.broadnet.me/answers/sms-vs-whatsapp-for-business · Markdown: https://www.broadnet.me/answers/sms-vs-whatsapp-for-business.md · Last reviewed: 2026-09-26 Use SMS when you need universal reach and instant delivery with no app or opt-in dependency — OTPs, transaction alerts, and any message that must reach every phone. Use WhatsApp when you want a branded, verified sender, rich media, and two-way conversation — marketing, support, and richer notifications — accepting that it requires the app, an opt-in, and template approval. The strongest programs use both behind one omnichannel API, choosing per message. See /products/omnichannel. ### SMS vs email marketing — how do they compare? URL: https://www.broadnet.me/answers/sms-vs-email-marketing · Markdown: https://www.broadnet.me/answers/sms-vs-email-marketing.md · Last reviewed: 2026-07-22 SMS delivers far higher open and read rates than email — industry studies consistently report SMS open rates around 98%, most within minutes — making it ideal for time-sensitive, short, high-urgency messages. Email carries richer content, images and long-form copy at a lower cost per message, making it better for newsletters, detailed offers and content. They are complementary: use SMS for immediacy and email for depth, and coordinate both in one omnichannel program. See /products/omnichannel. ### How do I send bulk SMS? URL: https://www.broadnet.me/answers/how-to-send-bulk-sms · Markdown: https://www.broadnet.me/answers/how-to-send-bulk-sms.md · Last reviewed: 2026-09-27 To send bulk SMS, connect to a provider over REST or SMPP (or upload a list to a campaign dashboard), register your sender ID, confirm every recipient has opted in, then send in throughput-managed batches while watching delivery receipts. The four things that determine success are a clean consented list, a registered sender ID, correct encoding to control segment count, and DLR monitoring so you catch failures early. See /products/bulk-sms. ### What are SMS marketing best practices? URL: https://www.broadnet.me/answers/sms-marketing-best-practices · Markdown: https://www.broadnet.me/answers/sms-marketing-best-practices.md · Last reviewed: 2026-07-22 Effective SMS marketing rests on permission and restraint: message only opted-in recipients, identify your brand, lead with clear value, keep it to one idea and one call to action, respect quiet hours and frequency limits, and always offer an easy opt-out. Because SMS is read within minutes by nearly everyone, the channel rewards relevance and punishes over-sending. See /products/bulk-sms and /solutions/ecommerce-retail. ### How do you use WhatsApp for customer support? URL: https://www.broadnet.me/answers/whatsapp-for-customer-support · Markdown: https://www.broadnet.me/answers/whatsapp-for-customer-support.md · Last reviewed: 2026-10-10 WhatsApp Business API turns WhatsApp into a scalable support channel: customers message your verified business number, and within the 24-hour service window your agents (and bots) can reply freely with text, images, documents, and quick-reply buttons. It suits asynchronous, media-rich support at scale, with automation handling routine questions and smooth handoff to human agents for the rest. See /products/whatsapp-business-api. ### What is conversational commerce? URL: https://www.broadnet.me/answers/what-is-conversational-commerce · Markdown: https://www.broadnet.me/answers/what-is-conversational-commerce.md · Last reviewed: 2026-07-22 Conversational commerce is buying, selling, and supporting customers through messaging channels — WhatsApp, RCS, SMS, and chat — so product discovery, questions, checkout, and after-sales all happen in one continuous thread. It has grown quickly because customers increasingly prefer messaging a business over calling or navigating a website, and messaging's high open rates make it a reliable place to reach them. See /products/omnichannel. ### How does number masking protect user privacy? URL: https://www.broadnet.me/answers/number-masking-for-privacy · Markdown: https://www.broadnet.me/answers/number-masking-for-privacy.md · Last reviewed: 2026-07-22 Number masking (number anonymization) connects two people — a rider and driver, a buyer and courier, a patient and clinician — through a temporary proxy number, so neither party ever sees the other's real phone number. It protects personal privacy, keeps the communication on your platform, and gives you a controllable, auditable channel for calls and SMS. See /answers/what-is-number-masking. ### What is the best channel for OTP delivery? URL: https://www.broadnet.me/answers/best-channel-for-otp · Markdown: https://www.broadnet.me/answers/best-channel-for-otp.md · Last reviewed: 2026-09-24 SMS is the default OTP channel because it reaches every phone with no app, but the best choice depends on the market and risk profile: SMS for universal reach, flash call for lower cost and speed where supported, WhatsApp for app-engaged users, silent network authentication for frictionless verification, and voice as a fallback. The strongest verification flows don't pick one — they cascade through several so a failed channel never blocks a login. See /products/otp. ### What is RCS for business (RBM)? URL: https://www.broadnet.me/answers/rcs-for-business · Markdown: https://www.broadnet.me/answers/rcs-for-business.md · Last reviewed: 2026-07-22 RCS Business Messaging (RBM) lets brands send verified, richly formatted messages straight to the native Messages app — a branded sender with logo and verified checkmark, image cards, carousels, suggested-reply and suggested-action buttons, plus delivery and read receipts and analytics. It is the natural upgrade from SMS on supported devices, with SMS remaining the fallback where RCS isn't available. See /products/rcs-messaging. ### What is an SMS fallback strategy? URL: https://www.broadnet.me/answers/sms-fallback-strategy · Markdown: https://www.broadnet.me/answers/sms-fallback-strategy.md · Last reviewed: 2026-08-08 An SMS fallback strategy automatically re-sends a message via SMS when a richer channel — WhatsApp or RCS — fails to deliver or the recipient isn't reachable there, so the message still lands. It combines the branding, richness, and economics of modern channels with SMS's universal reach as the safety net, so you get the best of both without sacrificing deliverability. See /products/omnichannel. ### What is the SMS character limit? URL: https://www.broadnet.me/answers/sms-character-limit-explained · Markdown: https://www.broadnet.me/answers/sms-character-limit-explained.md · Last reviewed: 2026-07-22 A single SMS holds 160 characters in the GSM-7 alphabet, or 70 characters if the message contains any Unicode (UCS-2) character such as an emoji or a non-Latin script. Longer messages are split into concatenated segments of 153 GSM-7 characters (or 67 Unicode characters) each, because a header is reserved to reassemble them — and every segment is billed separately. ### How do I send international SMS? URL: https://www.broadnet.me/answers/how-to-send-international-sms · Markdown: https://www.broadnet.me/answers/how-to-send-international-sms.md · Last reviewed: 2026-07-22 To send SMS internationally, format every number in full E.164 form (a plus sign, country code, and national number), send through a provider with direct routes to your destination countries, register a sender ID where the market requires it, and account for per-country pricing and content rules. The hard part is not the API call — it is route quality and compliance, which vary sharply from one country to the next. ### What is on an SMS compliance checklist? URL: https://www.broadnet.me/answers/sms-compliance-checklist · Markdown: https://www.broadnet.me/answers/sms-compliance-checklist.md · Last reviewed: 2026-07-22 An SMS compliance programme rests on five pillars: obtain and record explicit opt-in, honour opt-out (STOP) immediately, register and correctly classify sender IDs, respect quiet hours and local marketing law, and protect personal data under the applicable privacy regime. Requirements differ by country, but these fundamentals apply almost everywhere and are what operators and regulators actually enforce. ### How do I get an SMS short code? URL: https://www.broadnet.me/answers/how-to-get-a-short-code · Markdown: https://www.broadnet.me/answers/how-to-get-a-short-code.md · Last reviewed: 2026-07-22 A short code is a 4–6 digit number leased for high-volume two-way SMS, obtained by applying through a provider or the market's short-code registry, submitting your brand and use case for operator approval, and waiting through a provisioning and vetting period. Short codes offer high throughput and strong deliverability for campaigns and OTP, but they cost more and take longer to provision than a sender ID or long code. ### What is voice OTP? URL: https://www.broadnet.me/answers/voice-otp-explained · Markdown: https://www.broadnet.me/answers/voice-otp-explained.md · Last reviewed: 2026-09-24 Voice OTP delivers a one-time passcode as an automated phone call that reads the code aloud, rather than as a text message. It is used as a fallback when SMS is undelivered or unsupported, for landlines and feature phones, and for accessibility — ensuring a user can still verify when a text cannot reach them. It is a core part of a resilient, multi-channel verification flow. ### What is a messaging webhook? URL: https://www.broadnet.me/answers/what-is-a-messaging-webhook · Markdown: https://www.broadnet.me/answers/what-is-a-messaging-webhook.md · Last reviewed: 2026-07-22 A messaging webhook is an HTTPS endpoint on your server that a messaging platform calls to push you real-time events — delivery receipts, inbound (mobile-originated) messages, and status changes — instead of you polling an API for them. It is how your application learns that a message was delivered, failed, or received, the instant it happens, so you can react programmatically. ### RCS vs MMS — what's the difference? URL: https://www.broadnet.me/answers/rcs-vs-mms · Markdown: https://www.broadnet.me/answers/rcs-vs-mms.md · Last reviewed: 2026-07-22 MMS is the legacy multimedia messaging standard that attaches an image, audio, or video to a message over the carrier network; RCS Business Messaging is the modern successor that adds verified branding, interactive cards and buttons, suggested replies, and delivery and read receipts. MMS works on almost any phone as a heavier paid message; RCS works on supported Android and iOS 18+ devices and is far richer, with SMS/MMS as the fallback. ### SMS vs push notifications — how do they compare? URL: https://www.broadnet.me/answers/sms-vs-push-notifications · Markdown: https://www.broadnet.me/answers/sms-vs-push-notifications.md · Last reviewed: 2026-08-08 SMS reaches any mobile number on any phone with no app and is read within minutes, making it ideal for critical, universal messages like OTP and alerts; push notifications are free to send but only reach users who installed your app and granted permission, and are easily muted or ignored. Use SMS for reach and reliability, push for engaged in-app users, and combine them so a missed push can fall back to SMS. ### What is two-way messaging? URL: https://www.broadnet.me/answers/what-is-two-way-messaging · Markdown: https://www.broadnet.me/answers/what-is-two-way-messaging.md · Last reviewed: 2026-07-22 Two-way messaging is SMS (or another channel) that both sends to and receives replies from a recipient, so a customer can text back to confirm, opt out, ask a question, or trigger an action. It requires a number capable of receiving inbound messages — a long code, short code, or toll-free number — and a webhook to route replies into your application in real time. ### What is rate limiting in SMS? URL: https://www.broadnet.me/answers/what-is-rate-limiting-sms · Markdown: https://www.broadnet.me/answers/what-is-rate-limiting-sms.md · Last reviewed: 2026-07-22 Rate limiting caps how many messages or requests are accepted in a given time window — per API key, per sender, or per destination number — to protect throughput, enforce fair use, and defend against abuse such as SMS pumping. It is expressed as a rate (for example messages per second) and is what keeps one runaway job or one attacker from degrading delivery for everyone. ### How do I test an SMS integration? URL: https://www.broadnet.me/answers/how-to-test-sms-integration · Markdown: https://www.broadnet.me/answers/how-to-test-sms-integration.md · Last reviewed: 2026-09-29 Test an SMS integration with your test credentials first: they work against the production endpoint, so send to your own verified number, confirm the API returns the expected accepted response, verify the delivery receipt (DLR) arrives via webhook, then check encoding, sender ID, and segment count before you go live. After approval, send a small first batch to your real destination countries to validate route quality, and only then scale. ### What are SMS sender ID best practices? URL: https://www.broadnet.me/answers/sms-sender-id-best-practices · Markdown: https://www.broadnet.me/answers/sms-sender-id-best-practices.md · Last reviewed: 2026-07-22 Register alphanumeric sender IDs in every market that requires it, keep the ID to a recognizable brand name (up to 11 GSM-7 characters), classify traffic correctly as transactional or promotional, use it consistently so customers learn to trust it, and never send content that contradicts the registered use case. A well-managed sender ID lifts trust and delivery; a mismatched one gets suspended by the operator firewall. ### How do I handle SMS opt-outs? URL: https://www.broadnet.me/answers/how-to-handle-sms-opt-outs · Markdown: https://www.broadnet.me/answers/how-to-handle-sms-opt-outs.md · Last reviewed: 2026-07-22 Honour opt-outs instantly and permanently: recognize standard keywords like STOP (and localized equivalents), add the number to a suppression list, stop all marketing to it immediately, and confirm the opt-out once. Handling opt-outs correctly is both a legal requirement in most markets and a deliverability protection — repeated messaging to people who opted out damages sender reputation. ### What is a WhatsApp template message? URL: https://www.broadnet.me/answers/whatsapp-template-message-guide · Markdown: https://www.broadnet.me/answers/whatsapp-template-message-guide.md · Last reviewed: 2026-09-26 A WhatsApp template message is a pre-approved, reusable message format that businesses must use to initiate a conversation or message a user outside the 24-hour service window. Templates are submitted to Meta for review, categorized as Utility, Authentication, or Marketing, and can include variables, buttons, and media — they are how you proactively reach customers on WhatsApp in a permission-based way. ### How do you use SMS for two-factor authentication? URL: https://www.broadnet.me/answers/sms-for-two-factor-authentication · Markdown: https://www.broadnet.me/answers/sms-for-two-factor-authentication.md · Last reviewed: 2026-07-22 SMS two-factor authentication (2FA) adds a second check to a login by sending a one-time passcode to the user's phone, which they enter alongside their password. It is the most widely deployed 2FA method because it works on any phone with no app, though for high-assurance flows it is increasingly paired with or replaced by phishing-resistant methods. Deliver it over direct routes with rate limiting and short expiry. ### How do I migrate to a new SMS provider? URL: https://www.broadnet.me/answers/how-to-migrate-sms-provider · Markdown: https://www.broadnet.me/answers/how-to-migrate-sms-provider.md · Last reviewed: 2026-07-22 Migrate to a new SMS provider by running the new route in parallel with your current one, re-registering sender IDs in each market, updating API or SMPP credentials and webhook endpoints, testing delivery on real destinations, then shifting traffic gradually while watching delivery receipts. A phased cutover — not a hard switch — protects deliverability and lets you compare cost per delivered message before you fully commit. ### What is a good SMS delivery rate? URL: https://www.broadnet.me/answers/sms-delivery-rate-benchmarks · Markdown: https://www.broadnet.me/answers/sms-delivery-rate-benchmarks.md · Last reviewed: 2026-07-22 A healthy A2P SMS delivery rate on direct routes is typically in the high-90s percent for clean, consented lists in well-supported markets, though the realistic ceiling varies by country, operator, and list quality. What matters more than a single benchmark is stability: direct routes deliver consistently, while grey routes may look high one week and collapse the next as firewalls catch them. Measure your own rate by country and operator over time. ### What is a flash SMS? URL: https://www.broadnet.me/answers/what-is-flash-sms · Markdown: https://www.broadnet.me/answers/what-is-flash-sms.md · Last reviewed: 2026-07-22 A flash SMS (class 0 message) is a text that appears immediately on the recipient's screen without being saved to the inbox by default, so it demands instant attention and disappears unless the user chooses to keep it. It is used for urgent, ephemeral alerts — critical security warnings, emergency notifications, or attention-grabbing prompts — where an ordinary inbox message might be missed or where you do not want the content stored. ### What is OTP delivery rate? URL: https://www.broadnet.me/answers/what-is-otp-delivery-rate · Markdown: https://www.broadnet.me/answers/what-is-otp-delivery-rate.md · Last reviewed: 2026-10-02 OTP delivery rate is the share of one-time passcode messages that the destination operator confirms as delivered to the handset: delivered receipts divided by OTPs submitted, measured from delivery receipts (DLRs). It is not the same as the verification (conversion) rate, the share of users who actually enter the code, because a delivered code can still go unused. BroadNet's coverage pages give the typical operator-direct delivery rate for each market; on the UAE page it is 99.6%. ### How do I build an OTP verification flow? URL: https://www.broadnet.me/answers/how-to-build-otp-flow · Markdown: https://www.broadnet.me/answers/how-to-build-otp-flow.md · Last reviewed: 2026-07-22 Build an OTP flow in five steps: generate a short single-use code server-side, send it over a high-priority channel with a fallback, store a hashed copy with a short expiry, verify the user's input against it with attempt limits, and rate-limit requests to defend against pumping. Keep the code out of logs, never trust the client to validate, and prefer network-based verification where it removes the code entirely. ### What is a verification flow? URL: https://www.broadnet.me/answers/what-is-a-verification-flow · Markdown: https://www.broadnet.me/answers/what-is-a-verification-flow.md · Last reviewed: 2026-07-22 A verification flow is the end-to-end process that confirms a user controls a phone number or identity — requesting a factor, delivering it over one or more channels, collecting the user's response, and confirming or rejecting it. Modern flows are multi-channel and risk-aware: they cascade methods (network authentication, SMS, voice) so a single failed channel never blocks a legitimate user. ### What is conversational AI in messaging? URL: https://www.broadnet.me/answers/what-is-conversational-ai · Markdown: https://www.broadnet.me/answers/what-is-conversational-ai.md · Last reviewed: 2026-07-22 Conversational AI is software that understands and responds to natural-language messages, letting businesses automate two-way conversations across SMS, WhatsApp, RCS, and voice. In messaging it powers chatbots and virtual agents that answer questions, complete tasks, and escalate to humans with context — handling routine volume 24/7 while keeping the option of a person when the conversation needs one. ### What is a chatbot for business messaging? URL: https://www.broadnet.me/answers/what-is-a-chatbot-for-messaging · Markdown: https://www.broadnet.me/answers/what-is-a-chatbot-for-messaging.md · Last reviewed: 2026-07-22 A messaging chatbot is an automated agent that holds two-way conversations with customers on channels like WhatsApp, RCS, and SMS — answering FAQs, checking order status, capturing leads, and triaging support around the clock. It can be rule-based (following scripted flows) or AI-powered (understanding natural language), and the best implementations hand off to a human agent when the conversation needs one. ### How do I scale SMS throughput? URL: https://www.broadnet.me/answers/how-to-scale-sms-throughput · Markdown: https://www.broadnet.me/answers/how-to-scale-sms-throughput.md · Last reviewed: 2026-09-30 Scale SMS throughput by binding over SMPP for sustained high volume, provisioning enough operator capacity ahead of demand, spreading load across multiple binds or routes, respecting rate limits with backoff, and validating lists first so you are not wasting capacity on undeliverable numbers. Peak bursts — like OTP at a product launch — need capacity reserved in advance, not requested live. ### What is omnichannel orchestration? URL: https://www.broadnet.me/answers/what-is-omnichannel-orchestration · Markdown: https://www.broadnet.me/answers/what-is-omnichannel-orchestration.md · Last reviewed: 2026-08-08 Omnichannel orchestration is the logic that decides, per message and per recipient, which channel to use and in what order — sending on the best eligible channel (WhatsApp, RCS, SMS, voice, email) and falling back automatically when one is unavailable or undelivered. It turns a set of separate channels into a single intelligent delivery layer that maximizes reach, richness, and cost-efficiency at once. ### What is a number lookup API? URL: https://www.broadnet.me/answers/number-lookup-api-explained · Markdown: https://www.broadnet.me/answers/number-lookup-api-explained.md · Last reviewed: 2026-07-22 A number lookup API returns intelligence about a phone number in real time — whether it is valid and active, which country and operator it belongs to, whether it has been ported, and its line type. It queries the operator's HLR (or a number-intelligence database) so you can clean lists, route correctly, price accurately, and screen for fraud before you spend on a message or a call. ### How do you measure SMS marketing ROI? URL: https://www.broadnet.me/answers/sms-marketing-roi · Markdown: https://www.broadnet.me/answers/sms-marketing-roi.md · Last reviewed: 2026-07-22 Measure SMS marketing ROI by attributing revenue driven by a campaign against its full cost — message spend plus incentives — using unique links, promo codes, or holdout groups to isolate the SMS effect. Because SMS is read almost universally within minutes, well-targeted, consented campaigns typically show strong returns, but the honest number depends on attribution discipline and list quality, not on open rates alone. ### What is voice broadcast? URL: https://www.broadnet.me/answers/voice-broadcast-explained · Markdown: https://www.broadnet.me/answers/voice-broadcast-explained.md · Last reviewed: 2026-07-22 Voice broadcast is the automated delivery of a pre-recorded or text-to-speech voice message to many recipients at once — used for alerts, reminders, notifications, and surveys. It reaches people who may not read a text, works on landlines and feature phones, and can collect responses via keypad (DTMF), making it a useful complement to SMS for urgent or accessibility-sensitive communications. ### What is transactional SMS? URL: https://www.broadnet.me/answers/what-is-transactional-sms · Markdown: https://www.broadnet.me/answers/what-is-transactional-sms.md · Last reviewed: 2026-07-22 Transactional SMS is a message triggered by a user's action or account and essential to a service — an OTP, an order confirmation, a fraud alert, a delivery update. It carries no marketing, is usually exempt from marketing-consent rules (though still regulated), and is routed on high-priority, reliable paths because its value depends on arriving immediately. It is the opposite of promotional SMS. ### What is promotional SMS? URL: https://www.broadnet.me/answers/what-is-promotional-sms · Markdown: https://www.broadnet.me/answers/what-is-promotional-sms.md · Last reviewed: 2026-07-22 Promotional SMS is marketing sent by SMS — offers, campaigns, announcements, abandoned-cart nudges. Unlike transactional messages, it requires explicit marketing opt-in, must honour opt-out (STOP) and quiet hours, and is often registered and routed as a distinct traffic class. Done well on consented lists it converts strongly; sent without consent it wastes spend and damages sender reputation. ### What are SMS opt-in best practices? URL: https://www.broadnet.me/answers/sms-opt-in-best-practices · Markdown: https://www.broadnet.me/answers/sms-opt-in-best-practices.md · Last reviewed: 2026-07-22 Collect explicit, informed opt-in before sending marketing SMS: tell subscribers what they are signing up for, how often you will message, and how to stop; keep an auditable record of when and how consent was given; and confirm the subscription with a single welcome message. Clean, consented opt-in is the foundation of both compliance and deliverability — bought or scraped lists fail on both. ### What is an SMS gateway? URL: https://www.broadnet.me/answers/what-is-a-sms-gateway · Markdown: https://www.broadnet.me/answers/what-is-a-sms-gateway.md · Last reviewed: 2026-07-22 An SMS gateway is the system that connects applications to mobile networks so software can send and receive SMS — translating an API or SMPP request into the operator protocols that deliver a message to a handset, and passing delivery receipts and inbound messages back. It abstracts the SMSC connections, routing, and signalling so you integrate once instead of connecting to every operator yourself. ### What is bulk messaging? URL: https://www.broadnet.me/answers/what-is-bulk-messaging · Markdown: https://www.broadnet.me/answers/what-is-bulk-messaging.md · Last reviewed: 2026-07-22 Bulk messaging is sending a large volume of messages — SMS or another channel — to many recipients at once, for alerts, notifications, or marketing campaigns. It depends on a consented list, a registered sender ID, correct encoding to control cost, adequate throughput, and delivery-receipt monitoring. The scale is what makes list quality and route quality matter: small per-message problems multiply across a large send. ### What is the WhatsApp green tick (verified badge)? URL: https://www.broadnet.me/answers/whatsapp-green-tick-verification · Markdown: https://www.broadnet.me/answers/whatsapp-green-tick-verification.md · Last reviewed: 2026-07-22 The WhatsApp green tick is the official verified badge Meta grants to a business's WhatsApp account, shown next to the business name to confirm it is authentic and notable. It raises customer trust and reduces impersonation, and is granted by Meta based on the brand's notability and policy compliance — applied for through your Business Solution Provider, not bought. ### How can I reduce OTP costs? URL: https://www.broadnet.me/answers/how-to-reduce-otp-costs · Markdown: https://www.broadnet.me/answers/how-to-reduce-otp-costs.md · Last reviewed: 2026-09-24 Reduce OTP costs by sending fewer, cheaper, and more successful codes: prefer network-based verification (silent network authentication) that sends no billable message where supported, rate-limit to stop SMS pumping inflating volume, keep OTP messages to one GSM-7 segment, route over direct paths so codes are not re-sent, and use cheaper channels like flash call where they fit. The biggest saving is usually eliminating fraudulent and failed sends, not shaving the unit rate. ### SMS vs RCS for OTP — which should you use? URL: https://www.broadnet.me/answers/sms-vs-rcs-for-otp · Markdown: https://www.broadnet.me/answers/sms-vs-rcs-for-otp.md · Last reviewed: 2026-07-22 Use SMS for OTP as the universal baseline — it reaches any handset with no app and remains the standard for one-time codes. RCS can carry a verified, branded OTP with a better anti-phishing signal on capable devices, but its reach is not yet universal, so it works best as an enhancement with SMS underneath. For most verification flows in 2026, SMS (or a network check) delivers the code and RCS is optional polish. ### What is an SMS short link? URL: https://www.broadnet.me/answers/what-is-a-sms-short-link · Markdown: https://www.broadnet.me/answers/what-is-a-sms-short-link.md · Last reviewed: 2026-07-22 An SMS short link is a shortened, often branded URL used in a text message to save characters and track clicks. Because SMS is billed per segment, a long URL can push a message into a second segment; a short link keeps it compact, and a branded domain keeps it trustworthy. Link analytics then tell you how many recipients clicked — the closest thing SMS has to an engagement metric. ### What is an SMS survey? URL: https://www.broadnet.me/answers/what-is-sms-survey · Markdown: https://www.broadnet.me/answers/what-is-sms-survey.md · Last reviewed: 2026-07-22 An SMS survey collects feedback by text — sending a question and capturing the recipient's reply through two-way messaging. Because SMS is read within minutes by nearly everyone, response rates are high and fast, which makes it strong for short pulse surveys, NPS scores, and post-interaction feedback. It needs a number that can receive replies and a webhook to route responses into your system. ### What is a notification API? URL: https://www.broadnet.me/answers/what-is-a-notification-api · Markdown: https://www.broadnet.me/answers/what-is-a-notification-api.md · Last reviewed: 2026-08-08 A notification API is a programmatic interface that lets an application send notifications to users across channels — SMS, WhatsApp, RCS, voice, email, push — from a single integration. It abstracts each channel's delivery mechanics so your software can trigger a message with one call, and increasingly it orchestrates channel choice and fallback so a notification reliably reaches the user. ### What is SMS scheduling? URL: https://www.broadnet.me/answers/what-is-sms-scheduling · Markdown: https://www.broadnet.me/answers/what-is-sms-scheduling.md · Last reviewed: 2026-07-22 SMS scheduling is sending a message at a specified future time rather than immediately — used to reach recipients during their local business hours, coordinate campaigns, and time reminders. Good scheduling is timezone-aware and respects quiet hours, so a message meant for 10am arrives at 10am for each recipient, not all at once in one timezone. ### What do SMS message statuses mean? URL: https://www.broadnet.me/answers/what-is-message-status · Markdown: https://www.broadnet.me/answers/what-is-message-status.md · Last reviewed: 2026-07-22 An SMS message moves through statuses on its way to a handset — typically queued or accepted (received by the platform), sent (handed to the operator), delivered (confirmed on the handset), and failed, expired, or rejected when something goes wrong. These states come back as delivery receipts (DLRs), and reading them by status and error code is how you know what actually happened to each message. ### What is a customer engagement platform? URL: https://www.broadnet.me/answers/what-is-customer-engagement-platform · Markdown: https://www.broadnet.me/answers/what-is-customer-engagement-platform.md · Last reviewed: 2026-07-22 A customer engagement platform (CEP) is software that orchestrates communication with customers across channels — SMS, WhatsApp, RCS, voice, email, push — often adding segmentation, journeys, automation, and analytics on top of the messaging layer. Where a CPaaS provides the channels and APIs, a CEP adds the campaign, journey, and data tooling to run engagement programs on them. ### What is rich card messaging? URL: https://www.broadnet.me/answers/what-is-rich-card-messaging · Markdown: https://www.broadnet.me/answers/what-is-rich-card-messaging.md · Last reviewed: 2026-09-30 Rich card messaging sends a visually formatted card — an image or media, a title and description, and tappable buttons or suggested actions — instead of plain text, on channels like RCS and WhatsApp. Cards turn a notification into an interactive unit: a product with a Buy button, an order with a Track button, a booking with Confirm and Reschedule — driving action inside the message thread. ### Two-factor authentication vs multi-factor authentication — what's the difference? URL: https://www.broadnet.me/answers/what-is-two-factor-vs-mfa · Markdown: https://www.broadnet.me/answers/what-is-two-factor-vs-mfa.md · Last reviewed: 2026-07-22 Two-factor authentication (2FA) requires exactly two independent factors to verify identity; multi-factor authentication (MFA) requires two or more. So 2FA is a specific case of MFA. Both combine factor types — something you know (password), something you have (a phone or passkey), something you are (biometric) — and messaging channels commonly deliver the 'something you have' factor as an OTP or a network check. ### What is a messaging platform? URL: https://www.broadnet.me/answers/what-is-a-messaging-platform · Markdown: https://www.broadnet.me/answers/what-is-a-messaging-platform.md · Last reviewed: 2026-07-22 A messaging platform is software that lets a business send and receive messages across channels — SMS, WhatsApp, RCS, voice, email — through one system, typically with APIs, routing, delivery tracking, and often campaign and automation tooling. It sits between your applications and the mobile networks, so you build once and reach customers on any channel rather than integrating each operator and app yourself. ### What is SMS marketing automation? URL: https://www.broadnet.me/answers/what-is-sms-marketing-automation · Markdown: https://www.broadnet.me/answers/what-is-sms-marketing-automation.md · Last reviewed: 2026-07-22 SMS marketing automation triggers text messages automatically based on customer behaviour, events, or a schedule — a welcome message on signup, a cart-abandonment nudge, a birthday offer, a re-engagement series — rather than sending each campaign by hand. It combines audience data, triggers, and templates so the right message goes to the right person at the right moment, at scale, on consented lists. ### What is an SMS keyword campaign? URL: https://www.broadnet.me/answers/what-is-a-keyword-campaign · Markdown: https://www.broadnet.me/answers/what-is-a-keyword-campaign.md · Last reviewed: 2026-07-22 An SMS keyword campaign invites people to text a keyword (like JOIN or SALE) to a short code or number to opt in, get information, or enter a promotion. The inbound keyword triggers an automated response and adds the sender to a consented list. It is a clean, self-service way to collect opt-in and run interactive promotions, and it depends on two-way messaging and a number that can receive replies. ### What is inbound SMS? URL: https://www.broadnet.me/answers/what-is-inbound-sms · Markdown: https://www.broadnet.me/answers/what-is-inbound-sms.md · Last reviewed: 2026-07-22 Inbound SMS — also called mobile-originated (MO) SMS — is a message sent by a person to your business number, such as a reply, a keyword, or a STOP request. It arrives at your application through a webhook and is the foundation of two-way messaging: confirmations, support conversations, surveys, keyword campaigns, and opt-out handling all depend on receiving inbound messages. ### What is outbound SMS? URL: https://www.broadnet.me/answers/what-is-outbound-sms · Markdown: https://www.broadnet.me/answers/what-is-outbound-sms.md · Last reviewed: 2026-07-22 Outbound SMS — also called mobile-terminated (MT) SMS — is a message your business sends to a person's phone, such as an OTP, alert, notification, or marketing message. It is submitted through an SMS API or SMPP, routed to the recipient's operator, and confirmed by a delivery receipt. Most A2P traffic is outbound; pairing it with inbound SMS creates two-way conversations. ### What is an SMS blast? URL: https://www.broadnet.me/answers/what-is-a-sms-blast · Markdown: https://www.broadnet.me/answers/what-is-a-sms-blast.md · Last reviewed: 2026-07-22 An SMS blast is a single message sent to a large list of recipients at once — a broad announcement, alert, or promotion. It is the simplest form of bulk messaging, but 'blast' also carries a warning: sending the same message to everyone regardless of consent, segment, or timing wastes spend and hurts deliverability. Effective bulk sending is targeted and consented, not indiscriminate. ### What is an SMS aggregator? URL: https://www.broadnet.me/answers/what-is-sms-aggregator · Markdown: https://www.broadnet.me/answers/what-is-sms-aggregator.md · Last reviewed: 2026-07-22 An SMS aggregator is a company that connects to mobile operators and resells that connectivity to businesses, so enterprises can reach many networks through one relationship instead of contracting each operator. Aggregators route A2P traffic, handle sender-ID and compliance, and pass back delivery receipts. The key distinction is whether an aggregator holds direct operator agreements or resells another party's routes. ### What is toll-free SMS? URL: https://www.broadnet.me/answers/what-is-toll-free-sms · Markdown: https://www.broadnet.me/answers/what-is-toll-free-sms.md · Last reviewed: 2026-09-30 Toll-free SMS is A2P text messaging sent from a toll-free number (in North America, the 800/888/877-style numbers). Toll-free numbers can send and receive SMS at higher throughput than an ordinary long code once verified, and are a common choice for two-way business messaging in the US and Canada. They require verification to send at scale and sit between a long code and a short code in cost and capacity. ### What is message personalization? URL: https://www.broadnet.me/answers/what-is-message-personalization · Markdown: https://www.broadnet.me/answers/what-is-message-personalization.md · Last reviewed: 2026-07-22 Message personalization tailors each message to the individual recipient — inserting their name, order, appointment, or other data through template variables — so a single campaign produces thousands of relevant, individual messages. Done well it lifts engagement and conversion; done carelessly it leaks a literal {{name}} to customers or, worse, the wrong person's data. Preview and validate templates before sending. ### What is double opt-in? URL: https://www.broadnet.me/answers/what-is-double-opt-in · Markdown: https://www.broadnet.me/answers/what-is-double-opt-in.md · Last reviewed: 2026-07-22 Double opt-in is a two-step consent process: after a user signs up for messages, you send a confirmation asking them to confirm the subscription (for example by replying YES), and only add them once they do. It produces the cleanest, most defensible consent — proving the number's owner genuinely wanted the messages — which protects both deliverability and compliance for marketing programs. ### What is SMS analytics? URL: https://www.broadnet.me/answers/what-is-sms-analytics · Markdown: https://www.broadnet.me/answers/what-is-sms-analytics.md · Last reviewed: 2026-07-22 SMS analytics is the measurement of messaging performance — delivery rate, failure reasons by operator, click-through on links, inbound replies, opt-outs, and ultimately conversion and ROI. Because SMS has no native open rate, analytics is built from delivery receipts, tracked links, and downstream conversions. Good analytics turns sending into a feedback loop you can optimize. ### What is smart routing in SMS? URL: https://www.broadnet.me/answers/what-is-smart-routing · Markdown: https://www.broadnet.me/answers/what-is-smart-routing.md · Last reviewed: 2026-07-22 Smart routing is the logic a messaging platform uses to choose the best path for each message in real time — selecting among operator routes by quality, cost, and destination, and re-routing automatically when a path degrades. It aims to maximize delivery and control cost without manual intervention, and is closely related to least-cost routing and automatic route failover. ### What is a message queue in messaging? URL: https://www.broadnet.me/answers/what-is-a-message-queue · Markdown: https://www.broadnet.me/answers/what-is-a-message-queue.md · Last reviewed: 2026-07-22 A message queue holds submitted messages until they can be sent, smoothing bursts and respecting throughput limits. When you submit faster than the route allows, the platform queues the overflow and releases it at the permitted rate, so a spike does not overwhelm the operator or breach rate limits. Queue behaviour affects how quickly a large or bursty send actually goes out. ### What is channel fallback? URL: https://www.broadnet.me/answers/what-is-channel-fallback · Markdown: https://www.broadnet.me/answers/what-is-channel-fallback.md · Last reviewed: 2026-09-30 Channel fallback is automatically re-sending a message on a second channel when the first fails to deliver or is unavailable — for example WhatsApp or RCS first, then SMS. It maximizes the chance the message reaches the recipient by pairing a rich, preferred channel with a universal one underneath, and is the mechanism that lets omnichannel messaging combine richness with reliability. ### What is a broadcast list? URL: https://www.broadnet.me/answers/what-is-a-broadcast-list · Markdown: https://www.broadnet.me/answers/what-is-a-broadcast-list.md · Last reviewed: 2026-07-22 A broadcast list is a saved group of recipients you can message together — the audience for a bulk send or campaign. Unlike a group chat, recipients receive the message individually and do not see each other. A well-managed broadcast list is consented, segmented, and kept clean with validation and opt-out suppression, so each send reaches real, willing recipients. ### A2P vs bulk SMS — what's the difference? URL: https://www.broadnet.me/answers/a2p-vs-bulk-sms · Markdown: https://www.broadnet.me/answers/a2p-vs-bulk-sms.md · Last reviewed: 2026-09-24 A2P SMS and bulk SMS overlap but are not the same thing: A2P (application-to-person) describes who sends a message — a software application reaching a person with an OTP, alert, or notification — while bulk SMS describes how you send — one message pushed to many recipients at once, almost always for marketing. All bulk SMS is A2P, but not all A2P is bulk. ### CPaaS vs UCaaS — what's the difference? URL: https://www.broadnet.me/answers/cpaas-vs-ucaas · Markdown: https://www.broadnet.me/answers/cpaas-vs-ucaas.md · Last reviewed: 2026-07-30 CPaaS (Communications Platform as a Service) and UCaaS (Unified Communications as a Service) are both cloud communications, but serve opposite jobs: CPaaS gives developers APIs to embed messaging, voice, and video inside their own apps and workflows, while UCaaS is a ready-made suite — business phone, video meetings, and team chat — for a company's employees. CPaaS is building blocks; UCaaS is a finished product. ### OTP vs 2FA — what's the difference? URL: https://www.broadnet.me/answers/otp-vs-2fa · Markdown: https://www.broadnet.me/answers/otp-vs-2fa.md · Last reviewed: 2026-09-24 An OTP (one-time password) and 2FA (two-factor authentication) are related but not the same: an OTP is a single-use code, while 2FA is the security model that requires two independent proofs of identity. An OTP is one common way to deliver the second factor, but 2FA can also use authenticator apps, security keys, or biometrics. OTP is a tool; 2FA is the goal. ### HLR lookup vs MNP — what's the difference? URL: https://www.broadnet.me/answers/hlr-vs-mnp · Markdown: https://www.broadnet.me/answers/hlr-vs-mnp.md · Last reviewed: 2026-07-30 An HLR lookup and MNP are two sides of number intelligence: an HLR (Home Location Register) lookup queries a mobile network over SS7 to confirm whether a number is live and which operator now serves it, while MNP (mobile number portability) is the rule that lets subscribers keep their number when switching operator. Because ported numbers break the old prefix-to-operator mapping, an HLR lookup is how you find a number's real current network. ### SMSC vs SMS gateway — what's the difference? URL: https://www.broadnet.me/answers/smsc-vs-sms-gateway · Markdown: https://www.broadnet.me/answers/smsc-vs-sms-gateway.md · Last reviewed: 2026-09-24 An SMSC and an SMS gateway sit at different layers of the delivery path. An SMSC (Short Message Service Centre) is the store-and-forward node inside a mobile operator's core network that queues and delivers SMS to handsets; an SMS gateway is the application-facing platform that accepts messages over HTTP or SMPP and routes them to the correct operator's SMSC. Every SMS passes through an SMSC; a gateway is how an application reaches one. ### Does the iPhone support RCS? URL: https://www.broadnet.me/answers/iphone-rcs-support · Markdown: https://www.broadnet.me/answers/iphone-rcs-support.md · Last reviewed: 2026-09-30 Yes — the iPhone supports RCS. Apple added RCS Universal Profile support in iOS 18, released in September 2024, so any iPhone running iOS 18 or later can send and receive RCS in the native Messages app when the recipient and both carriers also support it. Before iOS 18, iPhones fell back to SMS and MMS for messages to non-iMessage users. ### What is silent network authentication? URL: https://www.broadnet.me/answers/silent-network-authentication · Markdown: https://www.broadnet.me/answers/silent-network-authentication.md · Last reviewed: 2026-09-24 Silent network authentication (SNA) verifies a phone number by checking it directly against the mobile operator's network over the device's data connection, instead of sending an SMS one-time password. The user types nothing and sees no code — the operator confirms the SIM in the device matches the number claimed. It is fast, invisible, and resistant to the phishing and SMS-pumping fraud that plague SMS OTP. ### What is A2P 10DLC? URL: https://www.broadnet.me/answers/what-is-a2p-10dlc · Markdown: https://www.broadnet.me/answers/what-is-a2p-10dlc.md · Last reviewed: 2026-09-30 A2P 10DLC (10-digit long code) is the US carrier framework that lets businesses send application-to-person SMS from standard 10-digit local numbers, provided the brand and each campaign are registered with The Campaign Registry (TCR). Registration unlocks sanctioned, higher throughput and better deliverability than an unregistered long code, which US carriers now filter or block. It sits between short codes and toll-free among US A2P options. ### SMS marketing vs transactional SMS — what's the difference? URL: https://www.broadnet.me/answers/sms-marketing-vs-transactional · Markdown: https://www.broadnet.me/answers/sms-marketing-vs-transactional.md · Last reviewed: 2026-07-30 Transactional SMS and marketing SMS are both A2P, but regulators and carriers treat them very differently. Transactional SMS delivers information a user requested or needs — OTPs, order updates, appointment reminders — and can generally be sent without marketing consent; marketing SMS promotes offers and requires explicit opt-in and a working opt-out. They also differ on timing windows, sender IDs, and routing priority. ### What is an alphanumeric sender ID? URL: https://www.broadnet.me/answers/what-is-alphanumeric-sender-id · Markdown: https://www.broadnet.me/answers/what-is-alphanumeric-sender-id.md · Last reviewed: 2026-10-20 An alphanumeric sender ID is a brand name of up to 11 letters and digits that appears instead of a phone number as the sender of an SMS. It makes a message instantly recognisable, but recipients cannot reply to it, and most regulated markets require each ID to be registered before operators will deliver it. ### What is a direct operator connection? URL: https://www.broadnet.me/answers/what-is-direct-operator-connection · Markdown: https://www.broadnet.me/answers/what-is-direct-operator-connection.md · Last reviewed: 2026-10-20 A direct operator connection is an interconnect in which a messaging provider binds straight to a mobile operator's SMSC or A2P gateway under its own contract with that operator, instead of handing traffic to another aggregator. Each message takes one hop to the network that delivers it, which keeps latency, delivery receipts and pricing transparent. ### What is cell broadcast? URL: https://www.broadnet.me/answers/what-is-cell-broadcast · Markdown: https://www.broadnet.me/answers/what-is-cell-broadcast.md · Last reviewed: 2026-10-20 Cell broadcast is a mobile network service that sends one message to every handset connected to a chosen set of cell towers at the same moment, without knowing any phone numbers. Authorities use it for public warnings — earthquakes, floods, missing children — because it reaches everyone in an area even when the network is congested. ### What is the RCS Universal Profile? URL: https://www.broadnet.me/answers/what-is-rcs-universal-profile · Markdown: https://www.broadnet.me/answers/what-is-rcs-universal-profile.md · Last reviewed: 2026-10-20 The RCS Universal Profile is the GSMA specification that defines which Rich Communication Services features phones, operator networks and messaging apps must support so that RCS works across all of them. It is the common rulebook behind typing indicators, read receipts, high-resolution media, group chat and RCS Business Messaging. ### What are WhatsApp Flows? URL: https://www.broadnet.me/answers/what-is-whatsapp-flows · Markdown: https://www.broadnet.me/answers/what-is-whatsapp-flows.md · Last reviewed: 2026-10-20 WhatsApp Flows are interactive, multi-screen forms that a business sends inside a WhatsApp chat — to book an appointment, capture a lead or complete a sign-up — so the customer fills in structured fields without leaving the conversation or opening a website. ### What is Remote SIM Provisioning (RSP)? URL: https://www.broadnet.me/answers/what-is-remote-sim-provisioning · Markdown: https://www.broadnet.me/answers/what-is-remote-sim-provisioning.md · Last reviewed: 2026-10-20 Remote SIM Provisioning (RSP) is the GSMA architecture that lets an operator download, enable and delete subscriber profiles on an eSIM over the air, instead of shipping a physical SIM card. It is what happens when a user scans an eSIM QR code and the phone joins a new network. ### What is IMS (IP Multimedia Subsystem)? URL: https://www.broadnet.me/answers/what-is-ims · Markdown: https://www.broadnet.me/answers/what-is-ims.md · Last reviewed: 2026-10-20 IMS (IP Multimedia Subsystem) is the 3GPP core-network architecture that delivers voice, video and messaging over IP on mobile and fixed networks. It carries VoLTE and 5G voice calls, RCS and SMS over IP, using SIP to set up sessions and Diameter to read subscriber data. ### What is an MVNO? URL: https://www.broadnet.me/answers/what-is-mvno · Markdown: https://www.broadnet.me/answers/what-is-mvno.md · Last reviewed: 2026-10-20 An MVNO (mobile virtual network operator) is a mobile service provider that sells its own branded plans but does not own a radio network — it buys access to a host operator's network at wholesale rates. The MVNO owns the brand, the customer relationship and usually the billing, while the host network carries the calls, data and messages. ### What are MCC and MNC codes? URL: https://www.broadnet.me/answers/what-is-mcc-mnc · Markdown: https://www.broadnet.me/answers/what-is-mcc-mnc.md · Last reviewed: 2026-10-20 MCC (Mobile Country Code) and MNC (Mobile Network Code) together identify one mobile network anywhere in the world. The three-digit MCC names the country and the two- or three-digit MNC names the operator within it — MCC 424 is the United Arab Emirates, and 424-02 and 424-03 are e& (Etisalat) and du. ### What is an SMS suppression list? URL: https://www.broadnet.me/answers/what-is-sms-suppression-list · Markdown: https://www.broadnet.me/answers/what-is-sms-suppression-list.md · Last reviewed: 2026-10-20 An SMS suppression list is a sender's own register of phone numbers that must not receive its marketing messages — people who replied STOP, withdrew consent or asked not to be contacted. Every promotional send is checked against it, so an opted-out number is never messaged again by mistake. ### What is a silent SMS? URL: https://www.broadnet.me/answers/what-is-silent-sms · Markdown: https://www.broadnet.me/answers/what-is-silent-sms.md · Last reviewed: 2026-10-20 A silent SMS — formally a Type 0 short message — is a text that a phone must acknowledge to the network but then discards without displaying it or alerting the user. Networks use it to check that a handset is reachable; it can also be abused to track a device, which is why operators screen unsolicited Type 0 traffic. ### What is IRSF (International Revenue Share Fraud)? URL: https://www.broadnet.me/answers/what-is-irsf · Markdown: https://www.broadnet.me/answers/what-is-irsf.md · Last reviewed: 2026-10-20 IRSF (International Revenue Share Fraud) is a telecom fraud in which criminals lease international premium-rate numbers and then generate artificial calls or messages to them, so the originating operator or business pays inflated termination fees while the fraudster and the number provider split the revenue. ### WhatsApp Cloud API vs On-Premises API: what changed? URL: https://www.broadnet.me/answers/whatsapp-cloud-api-vs-on-premises · Markdown: https://www.broadnet.me/answers/whatsapp-cloud-api-vs-on-premises.md · Last reviewed: 2026-10-20 The Cloud API is the version of the WhatsApp Business Platform API that Meta hosts; the On-Premises API was the older version that a business or its provider ran on its own servers. Meta has retired the On-Premises API — its final version expired on 23 October 2025 — so new integrations use the Cloud API. BroadNet, an official Meta Business Solution Provider, onboards customers directly onto the Cloud API. ### What are the WhatsApp opt-in rules? URL: https://www.broadnet.me/answers/whatsapp-opt-in-rules · Markdown: https://www.broadnet.me/answers/whatsapp-opt-in-rules.md · Last reviewed: 2026-10-20 WhatsApp requires a business to get a person's opt-in before messaging them through the WhatsApp Business Platform. Under Meta's policy the opt-in must make clear that the person agrees to receive messages from your business and must name your business; you choose how to collect it, and you must also meet the consent laws of every country you send to. BroadNet, an official Meta Business Solution Provider, sets up opt-in and opt-out handling as part of WhatsApp onboarding. ### How do you register a WhatsApp Business API number? URL: https://www.broadnet.me/answers/how-to-register-whatsapp-business-number · Markdown: https://www.broadnet.me/answers/how-to-register-whatsapp-business-number.md · Last reviewed: 2026-10-20 To register a number for the WhatsApp Business API you need a Meta business portfolio, a WhatsApp Business Account (WABA) inside it and a phone number you own that can receive an SMS or a voice call. You add the number to the WABA with a display name, verify it with the code Meta sends, set a two-step verification PIN and register it on the Cloud API. BroadNet, an official Meta Business Solution Provider, runs these steps with its customers. ### What are the WhatsApp message categories? URL: https://www.broadnet.me/answers/whatsapp-message-categories · Markdown: https://www.broadnet.me/answers/whatsapp-message-categories.md · Last reviewed: 2026-10-20 WhatsApp Business Platform messages fall into four categories that Meta uses for its rules and its pricing: Marketing, Utility and Authentication, which are pre-approved templates, and Service, the free-form replies a business sends inside the 24-hour customer service window. Each delivered message is billed by category and market, and from 1 October 2026 service replies are billed after a free tier of 1,000 service messages per business phone number per month. BroadNet, an official Meta Business Solution Provider, helps customers choose and submit the right category for each template. ## A2P SMS regulations by country ### A2P SMS regulations in the United Arab Emirates URL: https://www.broadnet.me/regulations/uae · Markdown: https://www.broadnet.me/regulations/uae.md · Last reviewed: 2026-10-20 A2P SMS in the UAE is regulated by the TDRA (Telecommunications and Digital Government Regulatory Authority) under its Unsolicited Electronic Communications policy. Every business must register an approved alphanumeric sender ID through Etisalat (e&) or du; promotional messages require the "AD" prefix, prior opt-in consent, and may only be sent between 7am and 9pm UAE time. - Regulator: TDRA (Telecommunications and Digital Government Regulatory Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: Alphanumeric sender IDs must be pre-registered with TDRA via the operator. One ID per legal entity per use case. AD- prefix mandatory on promotional senders under TDRA rules. - Compliance: PDPL (Federal Decree-Law 45/2021) governs PII handling. Promotional traffic restricted to 07:00–21:00 GST; transactional 24/7. Data plane sits in Dubai Tier-3 facilities. - Sources: TDRA https://tdra.gov.ae/ · TDRA spam policy https://tdra.gov.ae/-/media/About/regulations-and-ruling/EN/cellular-phone-spam-regulatory-policy-English.ashx ### A2P SMS regulations in Saudi Arabia URL: https://www.broadnet.me/regulations/saudi-arabia · Markdown: https://www.broadnet.me/regulations/saudi-arabia.md · Last reviewed: 2026-10-20 In Saudi Arabia, A2P SMS is governed by the Communications, Space & Technology Commission (CST, formerly CITC) under its Regulations for Curbing SPAM Messages & Calls. Every alphanumeric sender name must be pre-registered and whitelisted through the operator Bulk SMS e-System, promotional messages require documented prior opt-in consent, and marketing is prohibited between 10:00pm and 9:00am. - Regulator: CST (Communications, Space and Technology Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Alphanumeric IDs require CST + operator approval; one ID per legal entity per use case. Foreign senders must bind through a CST-licensed local aggregator. Arabic and Latin scripts both supported. - Compliance: Saudi PDPL fully enforced from 2024 — consent, data minimisation, 72-hour breach notification, cross-border restrictions. Some categories (banking, government) require Arabic content. Operator-specific quiet hours apply. - Sources: CST https://www.cst.gov.sa/en/ · CST SPAM regulations https://www.cst.gov.sa/en/regulations-and-licenses/regulations/Document-522 ### A2P SMS regulations in Egypt URL: https://www.broadnet.me/regulations/egypt · Markdown: https://www.broadnet.me/regulations/egypt.md · Last reviewed: 2026-10-20 Egypt has one of the region's strictest A2P SMS regimes, overseen by the National Telecom Regulatory Authority (NTRA). Every commercial sender must register an alphanumeric sender ID with the operators, route traffic through licensed local channels, and honour Egypt's Personal Data Protection Law (Law No. 151 of 2020). Marketing needs prior consent and opt-out; grey routes are actively prosecuted. - Regulator: NTRA (National Telecommunications Regulatory Authority) - Sender-ID lead time: 7-14 business days - Sender-ID rules: Every alphanumeric ID requires NTRA + operator approval. Latin or Arabic; one ID per use-case per entity. Foreign senders must terminate via an NTRA-licensed local aggregator. - Compliance: Egyptian Data Protection Law 151/2020 applies — consent, lawful basis, data subject rights, cross-border restrictions. Gambling, pharma, and crypto blocked at operator firewall. Grey routes carry penalties up to EGP 5,000,000. - Sources: NTRA https://tra.gov.eg/ · Law 10/2003 https://tra.gov.eg/rules/law-no-10-of-2003 ### A2P SMS regulations in Jordan URL: https://www.broadnet.me/regulations/jordan · Markdown: https://www.broadnet.me/regulations/jordan.md · Last reviewed: 2026-10-20 In Jordan, every A2P sender ID must be pre-registered with the Telecommunications Regulatory Commission (TRC), and promotional SMS needs verifiable opt-in. Consent records are kept for 12 months and shown to the TRC on request, and recipients' personal data falls under the Personal Data Protection Law of 2023. - Regulator: TRC (Telecommunications Regulatory Commission) - Sender-ID lead time: 5-7 business days - Sender-ID rules: All alphanumeric IDs must be pre-registered with TRC. One ID per use-case per entity; renewals annual. Arabic and Latin scripts both supported at parity. - Compliance: Jordan's PDPL (2023) applies to all recipient PII. Promotional SMS requires verifiable opt-in; records retained 12 months and available to TRC on request. - Sources: TRC https://trc.gov.jo/ ### A2P SMS regulations in Lebanon URL: https://www.broadnet.me/regulations/lebanon · Markdown: https://www.broadnet.me/regulations/lebanon.md · Last reviewed: 2026-10-20 In Lebanon, A2P sender IDs are registered directly with the two mobile operators, Alfa and Touch, under the Telecommunications Regulatory Authority (TRA). Personal data falls under Law 81/2018. - Regulator: TRA (Telecommunications Regulatory Authority) - Sender-ID lead time: 3-5 business days - Sender-ID rules: Sender IDs are registered directly with Alfa and Touch via BroadNet's operator account team. Arabic, Latin, and French scripts all handled. - Compliance: Law 81/2018 (e-Transactions and Personal Data) governs PII. - Sources: TRA https://www.tra.gov.lb/ ### SMS regulations in the United States URL: https://www.broadnet.me/regulations/united-states · Markdown: https://www.broadnet.me/regulations/united-states.md · Last reviewed: 2026-10-02 US A2P messaging is governed by carrier registration through The Campaign Registry (10DLC brand + campaign vetting), the CTIA Messaging Principles, and the TCPA consent regime — number-based registration, not alphanumeric sender IDs. - Regulator: FCC + CTIA (Federal Communications Commission (FCC) and CTIA (carrier consortium)) - Sender-ID lead time: 7-14 business days (10DLC) - Sender-ID rules: 10DLC Brand vetting + Campaign registration via The Campaign Registry (TCR) for long codes. Toll-Free Verification via carrier-verified business profiles. Short codes leased + provisioned. - Compliance: TCPA enforced — opt-in, HELP/STOP keyword handling, statutory damages from $500/message. SHAFT-C content restricted across all US carriers. - Sources: 47 CFR 64.1200 https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200 · FCC https://www.fcc.gov/ · CTIA https://www.ctia.org/ · TCR https://www.campaignregistry.com/ · TCR FAQ https://www.campaignregistry.com/resources/ · CTIA Messaging Principles https://api.ctia.org/wp-content/uploads/2023/05/230523-CTIA-Messaging-Principles-and-Best-Practices-FINAL.pdf ### A2P SMS regulations in Qatar URL: https://www.broadnet.me/regulations/qatar · Markdown: https://www.broadnet.me/regulations/qatar.md · Last reviewed: 2026-09-29 Qatar's Communications Regulatory Authority (CRA) governs A2P SMS. Senders need prior, explicit recipient consent and a registered alphanumeric sender ID on each operator (Ooredoo, Vodafone). Direct-marketing texts are barred between 9pm and 9am, must identify the sender in Arabic and English, and carry a free "STOP" opt-out. - Regulator: CRA (Communications Regulatory Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: Sender IDs pre-registered with CRA. Promotional senders require explicit opt-in language. Arabic and Latin both supported. - Compliance: Qatar PDPPL (Law No. 13/2016) governs PII. CRA enforces opt-out language on every promotional message. Operator-side firewall blocks restricted categories. - Sources: CRA https://www.cra.gov.qa/ · CRA Spam Regulation https://www.cra.gov.qa/-/media/System/1/A/1/B/1A1B31855B7654C4A360A3C20E55D739/Spam-Regulation-Amended-English-Version.ashx ### A2P SMS regulations in Kuwait URL: https://www.broadnet.me/regulations/kuwait · Markdown: https://www.broadnet.me/regulations/kuwait.md · Last reviewed: 2026-10-20 Kuwait's A2P SMS market is regulated by CITRA (Communications and Information Technology Regulatory Authority). Every commercial alphanumeric sender ID must be pre-registered with CITRA and the mobile operators before traffic is delivered, unregistered IDs are blocked, and marketing messages require documented opt-in consent with a working opt-out. Data handling follows CITRA's Data Privacy Protection Regulation. - Regulator: CITRA (Communication and Information Technology Regulatory Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: Alphanumeric sender IDs require CITRA + operator approval. Each use case needs its own ID; renewals annual. Arabic and Latin scripts at parity. - Compliance: Kuwait DPPR (Data Privacy Protection Regulation) applies via CITRA. - Sources: CITRA https://www.citra.gov.kw/ ### A2P SMS regulations in Oman URL: https://www.broadnet.me/regulations/oman · Markdown: https://www.broadnet.me/regulations/oman.md · Last reviewed: 2026-10-20 A2P SMS in Oman is regulated by the Telecommunications Regulatory Authority (TRA) and the operators Omantel, Ooredoo Oman and Vodafone Oman. Alphanumeric sender IDs must be pre-registered before traffic flows. Marketing messages require prior consent under the Personal Data Protection Law (Royal Decree 6/2022); spam, and political, religious or gambling content, are prohibited. - Regulator: TRA-Oman (Telecommunications Regulatory Authority) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Alphanumeric sender IDs pre-registered with TRA-Oman via the operator. Arabic and Latin scripts supported. Renewals annual. - Compliance: Oman Personal Data Protection Law (Royal Decree 6/2022) effective 2024. Consent, breach notification, and cross-border restrictions enforced. - Sources: TRA https://www.tra.gov.om/ ### A2P SMS regulations in Bahrain URL: https://www.broadnet.me/regulations/bahrain · Markdown: https://www.broadnet.me/regulations/bahrain.md · Last reviewed: 2026-10-20 A2P SMS in Bahrain is overseen by the Telecommunications Regulatory Authority (TRA Bahrain), with data-privacy obligations under the Personal Data Protection Law (Law No. 30 of 2018). Senders must use an approved alphanumeric sender ID carrying the brand name, obtain prior opt-in consent for marketing, and honour opt-out (STOP) requests. Numeric and generic sender IDs are generally blocked. - Regulator: TRA-BH (Telecommunications Regulatory Authority of Bahrain) - Sender-ID lead time: 5-7 business days - Sender-ID rules: TRA-BH sender ID pre-registration required. Arabic + Latin scripts both at parity. - Compliance: Bahrain PDPL (Law 30/2018) is one of the most mature in the GCC. Cross-border restrictions, breach notification, and recipient rights all enforced. - Sources: TRA https://www.tra.org.bh/ ### A2P SMS regulations in India URL: https://www.broadnet.me/regulations/india · Markdown: https://www.broadnet.me/regulations/india.md · Last reviewed: 2026-10-01 A2P SMS in India is governed by TRAI (the Telecom Regulatory Authority of India) under the TCCCPR 2018 (Telecom Commercial Communications Customer Preference Regulations). Every commercial sender must complete DLT (Distributed Ledger Technology) registration — Principal Entity, Header (sender ID), and Content Template — on the operator DLT portals before any message will deliver. Traffic is category-scoped (Promotional, Transactional, Service), promotional SMS is limited to 10am–9pm, and subscriber preferences are honoured through the DND registry. - Regulator: TRAI (Telecom Regulatory Authority of India) - Sender-ID lead time: 3-7 business days (DLT header registration) - Sender-ID rules: TRAI DLT registration mandatory: Header (sender ID), Entity, and Template all pre-registered on the DLT blockchain. Every message variant scrubbed at operator firewall. - Compliance: DPDP Act 2023 governs PII (Data Protection Board enforcement). DND (Do Not Disturb) registry honoured for promotional. Under TCCCPR 2018, promotional delivery is by default limited to 10:00-21:00 IST; Service Implicit and Transactional 24/7. - Sources: TRAI https://www.trai.gov.in/ · TCCCPR 2018 https://www.trai.gov.in/sites/default/files/2025-01/RegulationUcc19072018.pdf · VILPOWER DLT FAQ https://www.vilpower.in/faq/ ### A2P SMS regulations in Türkiye URL: https://www.broadnet.me/regulations/turkey · Markdown: https://www.broadnet.me/regulations/turkey.md · Last reviewed: 2026-10-20 Commercial SMS in Türkiye is governed by Law No. 6563 on the Regulation of Electronic Commerce and its Commercial Communication regulation, enforced by the Ministry of Trade (Ticaret Bakanlığı). Before sending any commercial message ("ticari elektronik ileti"), senders must register recipient opt-in in İYS (İleti Yönetim Sistemi — the national Message Management System). Every message must carry a working opt-out, and personal data is governed by KVKK (Law No. 6698). BTK, the telecoms regulator, oversees the operators that carry the traffic. - Regulator: BTK (Bilgi Teknolojileri ve İletişim Kurumu) - Sender-ID lead time: 5-7 business days - Sender-ID rules: Alphanumeric sender IDs (originators) are set up with the operators. İYS (İleti Yönetim Sistemi) opt-in registry mandatory for commercial messages. Turkish diacritics in UCS-2. - Compliance: KVKK (Turkish PDP Law) enforced. İYS opt-in registry mandatory for marketing — pre-flight check per recipient. - Sources: Ticaret Bakanlığı https://ticaret.gov.tr/ · Law No. 6563 https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6563.pdf · İYS https://iys.org.tr/ · BTK https://www.btk.gov.tr/en ### A2P SMS regulations in Pakistan URL: https://www.broadnet.me/regulations/pakistan · Markdown: https://www.broadnet.me/regulations/pakistan.md · Last reviewed: 2026-10-01 A2P SMS in Pakistan is regulated by the PTA (Pakistan Telecommunication Authority). Corporate and brand SMS is sent under a registered sender-ID "mask", provisioned through the mobile operators (Jazz, Zong, Telenor and Ufone); unregistered masks and grey-route traffic are blocked. Anti-spam obligations flow from the PTA's SOPs and PECA, marketing requires consent and an opt-out, and a Personal Data Protection framework is still being finalised. - Regulator: PTA (Pakistan Telecommunication Authority) - Sender-ID lead time: 7-14 business days - Sender-ID rules: PTA sender ID (mask) registration mandatory. English and Urdu both supported. Operator-aligned content filters apply. - Compliance: PTA's Spam Regulations (as amended in 2022) require consent before marketing, suppression of the 3627 Do Not Call Register, and delivery of promotional SMS within normal business hours. Personal Data Protection Bill (draft) progressing toward enforcement. - Sources: PTA https://www.pta.gov.pk/ ### A2P SMS regulations in Bangladesh URL: https://www.broadnet.me/regulations/bangladesh · Markdown: https://www.broadnet.me/regulations/bangladesh.md · Last reviewed: 2026-09-29 A2P SMS in Bangladesh is regulated by the BTRC (Bangladesh Telecommunication Regulatory Commission). Commercial traffic is sent under a registered, branded sender-ID "mask" provisioned through the operators (Grameenphone, Robi, Banglalink and Teletalk), with content approval and BTRC anti-spam directives. Marketing needs consent and an opt-out, and a dedicated data-protection statute is still in draft. - Regulator: BTRC (Bangladesh Telecommunication Regulatory Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: BTRC sender ID registration via the operator. Bangla (UCS-2) and English both supported. - Compliance: Bangladesh Digital Security Act applies. Content filters operator-side. - Sources: BTRC https://btrc.gov.bd/ ### A2P SMS regulations in Nigeria URL: https://www.broadnet.me/regulations/nigeria · Markdown: https://www.broadnet.me/regulations/nigeria.md · Last reviewed: 2026-10-20 A2P SMS in Nigeria is regulated by the NCC (Nigerian Communications Commission). Subscribers opt out of unsolicited marketing through the national DND (Do Not Disturb) facility on the 2442 short code, commercial senders register a branded sender ID with the operators, and NCC guidelines govern unsolicited messages. Personal data is governed by the Nigeria Data Protection Act, 2023 (NDPA), enforced by the Nigeria Data Protection Commission (NDPC). - Regulator: NCC (Nigerian Communications Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: NCC sender ID registration via licensed local aggregator. White-listed senders only; one ID per use case per entity. English and Hausa scripts supported. - Compliance: NCC enforces strict promotional opt-in (DND registry). NDPR (Nigeria Data Protection Regulation) governs PII. Quiet hours 20:00-08:00 for marketing. - Sources: NCC https://www.ncc.gov.ng/ · NCC CME report https://www.ncc.gov.ng/node/265 · NCC VAS framework https://old.ncc.gov.ng/documents/791-value-added-service-aggregator/file · NCC VAS aggregator licence https://old.ncc.gov.ng/documents/914-licensing-vas-aggregator-license/file ### A2P SMS regulations in the United Kingdom URL: https://www.broadnet.me/regulations/united-kingdom · Markdown: https://www.broadnet.me/regulations/united-kingdom.md · Last reviewed: 2026-10-02 A2P SMS in the UK sits under two regulators: Ofcom for telecoms and the ICO (Information Commissioner's Office) for data protection. Marketing texts are governed by PECR (the Privacy and Electronic Communications Regulations 2003) and UK GDPR / the Data Protection Act 2018, which require opt-in consent and a clear opt-out. There is no government sender-ID registry; alphanumeric sender IDs are used, and the industry combats spoofing through the MEF SMS Sender ID Protection Registry and an operator code of conduct. - Regulator: ICO + Ofcom (Information Commissioner's Office (ICO) and Office of Communications (Ofcom)) - Sender-ID lead time: Free-form (no formal registration) - Sender-ID rules: Alphanumeric sender IDs do not require pre-registration but must be consistent and brand-identifiable. Under Ofcom rules finalised in July 2026, providers must check business senders and their sender IDs from 15 July 2027. - Compliance: UK GDPR + PECR (Privacy and Electronic Communications Regulations 2003). Explicit opt-in for marketing, opt-out on every send. Per-message HLR lookup for MNP at no extra fee. - Sources: Ofcom https://www.ofcom.org.uk/ · ICO https://ico.org.uk/ · Ofcom scam-text rules https://www.ofcom.org.uk/phones-and-broadband/scam-calls-and-messages/new-rules-to-thwart-text-message-scammers-and-protect-consumers-and-businesses ### A2P SMS regulations in Germany URL: https://www.broadnet.me/regulations/germany · Markdown: https://www.broadnet.me/regulations/germany.md · Last reviewed: 2026-09-29 Germany runs one of the strictest marketing-SMS regimes in the EU. The Bundesnetzagentur (BNetzA) is the telecoms regulator, data protection follows the GDPR and the Federal Data Protection Act (BDSG), and unsolicited advertising is governed by the UWG (Act Against Unfair Competition). Marketing SMS requires prior express opt-in — double opt-in is the market standard — with a clear opt-out on every message; sender-ID spoofing is actively enforced. - Regulator: BNetzA (Bundesnetzagentur) - Sender-ID lead time: Free-form (numeric preferred) - Sender-ID rules: Alphanumeric sender IDs allowed but numeric preferred for transactional. GDPR opt-in mandatory for marketing. - Compliance: GDPR + TKG enforced. Double opt-in for marketing (DSGVO). BNetzA actively blocks high-fraud senders. - Sources: BNetzA https://www.bundesnetzagentur.de/ ### A2P SMS regulations in France URL: https://www.broadnet.me/regulations/france · Markdown: https://www.broadnet.me/regulations/france.md · Last reviewed: 2026-09-29 A2P SMS in France is overseen by ARCEP for telecoms and the CNIL for data protection under the GDPR. Marketing texts require consent and a mandatory "STOP" opt-out. France also runs the 33700 short code, a national facility for reporting spam SMS. Alphanumeric sender IDs are used. - Regulator: ARCEP (Autorité de Régulation des Communications Électroniques et des Postes) - Sender-ID lead time: 5-10 business days (alphanumeric) - Sender-ID rules: Alphanumeric sender IDs require registration with operator (and 33700 anti-spam). French STOP keyword mandatory for promotional. - Compliance: GDPR + LCEN. CNIL enforcement. STOP and STOP MAIL keywords honoured in French. - Sources: ARCEP https://www.arcep.fr/ · CNIL https://www.cnil.fr/ ### A2P SMS regulations in Brazil URL: https://www.broadnet.me/regulations/brazil · Markdown: https://www.broadnet.me/regulations/brazil.md · Last reviewed: 2026-09-29 A2P SMS in Brazil is regulated by ANATEL (Agência Nacional de Telecomunicações), with data protection governed by the LGPD (Lei Geral de Proteção de Dados) and supervised by the ANPD (Autoridade Nacional de Proteção de Dados). Marketing requires consent, sender IDs are registered through the operators, and subscribers can block unwanted telemarketing through the "Não Perturbe" do-not-disturb registry. - Regulator: Anatel (Agência Nacional de Telecomunicações) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Anatel + operator sender ID registration (CNPJ-verified). Portuguese supported in UCS-2 (diacritics) or GSM-7 transliteration. - Compliance: LGPD (Lei Geral de Proteção de Dados) enforced by ANPD. CNPJ verification required for sender. - Sources: ANATEL https://www.gov.br/anatel/ · ANPD https://www.gov.br/anpd/ ### A2P SMS regulations in Indonesia URL: https://www.broadnet.me/regulations/indonesia · Markdown: https://www.broadnet.me/regulations/indonesia.md · Last reviewed: 2026-09-30 A2P SMS in Indonesia is regulated by the Ministry of Communications and Digital Affairs — Komdigi, formerly Kominfo — with data protection governed by the Personal Data Protection Law (Law No. 27 of 2022). Commercial traffic is sent under a registered "masking" sender ID provisioned through the operators (Telkomsel, Indosat, XL), consent is required for marketing, and anti-spam controls apply. - Regulator: Komdigi (Ministry of Communication and Digital Affairs) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Komdigi + operator sender ID registration. Bahasa Indonesia and English supported. - Compliance: Personal Data Protection Law (UU PDP 2022) enforced. Data localisation requirements for some categories. - Sources: Komdigi https://www.komdigi.go.id/ ### A2P SMS regulations in the Philippines URL: https://www.broadnet.me/regulations/philippines · Markdown: https://www.broadnet.me/regulations/philippines.md · Last reviewed: 2026-09-29 A2P SMS in the Philippines is regulated by the NTC (National Telecommunications Commission), with data protection under the Data Privacy Act of 2012 enforced by the National Privacy Commission (NPC). Commercial traffic uses registered sender IDs provisioned through the operators, marketing requires consent, and the SIM Registration Act of 2022 shapes the wider anti-scam context. - Regulator: NTC (National Telecommunications Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: NTC + operator sender ID registration. SIM Registration Act 2022 also applies to recipients. - Compliance: Data Privacy Act 2012 (NPC enforcement) in force. SIM Registration Act 2022 means recipient verification is high. Anti-Spam policy mandates opt-in for marketing. - Sources: NTC https://ntc.gov.ph/ · NPC https://privacy.gov.ph/ ### A2P SMS regulations in South Africa URL: https://www.broadnet.me/regulations/south-africa · Markdown: https://www.broadnet.me/regulations/south-africa.md · Last reviewed: 2026-10-02 A2P SMS in South Africa is regulated by ICASA (the Independent Communications Authority of South Africa), with data protection and direct-marketing rules set by POPIA (the Protection of Personal Information Act) and enforced by the Information Regulator. Direct-marketing SMS requires opt-in consent (POPIA section 69) and a working opt-out, and every message must identify the sender. - Regulator: ICASA (Independent Communications Authority of South Africa) - Sender-ID lead time: Free-form (no pre-registration) - Sender-ID rules: The WASPA Code of Conduct sets no sender-ID pre-registration; alphanumeric sender IDs must identify the business, and WASPA members must give WASPA their alphanumeric IDs on request. - Compliance: POPIA (Protection of Personal Information Act) fully enforced. Opt-in required for direct marketing; opt-out on every promotional send. WASPA dispute resolution applies. - Sources: ICASA https://www.icasa.org.za/ · Information Regulator https://inforegulator.org.za/ · WASPA Code of Conduct https://waspa.org.za/wp-content/uploads/2026/09/WASPA-Code-of-Conduct-17.15-clean.pdf ### A2P SMS regulations in Iraq URL: https://www.broadnet.me/regulations/iraq · Markdown: https://www.broadnet.me/regulations/iraq.md · Last reviewed: 2026-10-20 A2P SMS to Iraq is regulated by the Communications and Media Commission (CMC). Sender IDs registered through CMC-licensed operators. Arabic + Latin both supported. Some operators require deposit per ID, with approval typically taking 7-14 business days. CMC enforces content rules around political and religious material. BroadNet carries this traffic over direct operator connections. - Regulator: CMC (Communications and Media Commission) - Sender-ID lead time: 7-14 business days - Sender-ID rules: Sender IDs registered through CMC-licensed operators. Arabic + Latin both supported. Some operators require deposit per ID. - Compliance: CMC enforces content rules around political and religious material. Pre-paid market — DLR rates vary by region. Local Iraqi entity recommended for direct billing. - Sources: CMC https://cmc.iq/ ### A2P SMS regulations in Palestine URL: https://www.broadnet.me/regulations/palestine · Markdown: https://www.broadnet.me/regulations/palestine.md · Last reviewed: 2026-09-29 A2P SMS to Palestine is regulated by the Ministry of Telecommunications and Information Technology (MTIT). Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported, with approval typically taking 7-10 business days. Routing handles West Bank and Gaza differently due to network topology — BroadNet's engine selects the right MNO per recipient prefix automatically. BroadNet carries this traffic over direct operator connections. - Regulator: MTIT (Ministry of Telecommunications and Information Technology) - Sender-ID lead time: 7-10 business days - Sender-ID rules: Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported. - Compliance: Routing handles West Bank and Gaza differently due to network topology — BroadNet's engine selects the right MNO per recipient prefix automatically. - Sources: MTIT https://www.mtit.gov.ps/ ### A2P SMS regulations in Tunisia URL: https://www.broadnet.me/regulations/tunisia · Markdown: https://www.broadnet.me/regulations/tunisia.md · Last reviewed: 2026-10-20 A2P SMS to Tunisia is regulated by the Instance Nationale des Télécommunications (INT). Alphanumeric sender IDs pre-registered with INT via the operator. Arabic, French, and Latin scripts supported, with approval typically taking 5-7 business days. Tunisia Personal Data Protection Law applies. BroadNet carries this traffic over direct operator connections. - Regulator: INT (Instance Nationale des Télécommunications) - Sender-ID lead time: 5-7 business days - Sender-ID rules: Alphanumeric sender IDs pre-registered with INT via the operator. Arabic, French, and Latin scripts supported. - Compliance: Tunisia Personal Data Protection Law applies. Promotional traffic requires opt-in. Operator-side filtering enforces content rules. - Sources: INT https://www.intt.tn/ ### A2P SMS regulations in Algeria URL: https://www.broadnet.me/regulations/algeria · Markdown: https://www.broadnet.me/regulations/algeria.md · Last reviewed: 2026-10-20 A2P SMS to Algeria is regulated by the Autorité de Régulation de la Poste et des Communications Électroniques (ARPCE). Sender IDs require ARPCE + operator approval. Arabic and French primary; Latin acceptable, with approval typically taking 10-14 business days. Algerian Data Protection Law 18-07 applies. BroadNet carries this traffic over direct operator connections. - Regulator: ARPCE (Autorité de Régulation de la Poste et des Communications Électroniques) - Sender-ID lead time: 10-14 business days - Sender-ID rules: Sender IDs require ARPCE + operator approval. Arabic and French primary; Latin acceptable. - Compliance: Algerian Data Protection Law 18-07 applies. Cross-border data transfers restricted. Local entity recommended for direct billing. - Sources: ARPCE https://www.arpce.dz/ ### A2P SMS regulations in Morocco URL: https://www.broadnet.me/regulations/morocco · Markdown: https://www.broadnet.me/regulations/morocco.md · Last reviewed: 2026-10-20 A2P SMS to Morocco is regulated by the Agence Nationale de Réglementation des Télécommunications (ANRT). Sender IDs pre-registered with ANRT via the operator. Arabic, French, and Latin scripts all supported, with approval typically taking 5-10 business days. Moroccan Data Protection Law 09-08 (CNDP enforced). BroadNet carries this traffic over direct operator connections. - Regulator: ANRT (Agence Nationale de Réglementation des Télécommunications) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Sender IDs pre-registered with ANRT via the operator. Arabic, French, and Latin scripts all supported. - Compliance: Moroccan Data Protection Law 09-08 (CNDP enforced). Promotional A2P requires opt-in. - Sources: ANRT https://www.anrt.ma/ ### A2P SMS regulations in Mauritania URL: https://www.broadnet.me/regulations/mauritania · Markdown: https://www.broadnet.me/regulations/mauritania.md · Last reviewed: 2026-09-29 A2P SMS to Mauritania is regulated by the Autorité de Régulation (ARE). Sender IDs registered via operator. Arabic + French; Latin acceptable, with approval typically taking 10-14 business days. Three operators: Mauritel, Mattel, Chinguitel. BroadNet carries this traffic over direct operator connections. - Regulator: ARE (Autorité de Régulation) - Sender-ID lead time: 10-14 business days - Sender-ID rules: Sender IDs registered via operator. Arabic + French; Latin acceptable. - Compliance: Three operators: Mauritel, Mattel, Chinguitel. ARE enforces content rules at the operator level. - Sources: ARE https://www.are.mr/ ### A2P SMS regulations in Djibouti URL: https://www.broadnet.me/regulations/djibouti · Markdown: https://www.broadnet.me/regulations/djibouti.md · Last reviewed: 2026-09-29 A2P SMS to Djibouti is regulated by the Ministère de la Communication, Postes et Télécommunications (MCPT). Sender IDs registered via Djibouti Telecom. Arabic, French, and Latin all supported, with approval typically taking 10-14 business days. Single-operator market (Djibouti Telecom / Evatis). BroadNet carries this traffic over direct operator connections. - Regulator: MCPT (Ministère de la Communication, Postes et Télécommunications) - Sender-ID lead time: 10-14 business days - Sender-ID rules: Sender IDs registered via Djibouti Telecom. Arabic, French, and Latin all supported. - Compliance: Single-operator market (Djibouti Telecom / Evatis). Operator-direct route. Content rules per government framework. - Sources: MCPT https://communication.gouv.dj/ ### A2P SMS regulations in Comoros URL: https://www.broadnet.me/regulations/comoros · Markdown: https://www.broadnet.me/regulations/comoros.md · Last reviewed: 2026-09-29 A2P SMS to Comoros is regulated by the Autorité Nationale de Régulation des TIC (ANRTIC). Sender IDs via Comores Telecom and Telma operator routes. Arabic, French, and Comorian supported, with approval typically taking 10-14 business days. Two-operator market. BroadNet carries this traffic over direct operator connections. - Regulator: ANRTIC (Autorité Nationale de Régulation des TIC) - Sender-ID lead time: 10-14 business days - Sender-ID rules: Sender IDs via Comores Telecom and Telma operator routes. Arabic, French, and Comorian supported. - Compliance: Two-operator market. Routes via aggregator partners. Content compliance per ANRTIC framework. - Sources: ANRTIC https://www.anrtic.km/ ### A2P SMS regulations in Kenya URL: https://www.broadnet.me/regulations/kenya · Markdown: https://www.broadnet.me/regulations/kenya.md · Last reviewed: 2026-09-29 A2P SMS to Kenya is regulated by the Communications Authority of Kenya (CA). CA + operator sender ID registration. Safaricom requires content templates approved per use case. English and Swahili scripts supported, with approval typically taking 5-7 business days. Kenya Data Protection Act 2019 fully enforced (ODPC). BroadNet carries this traffic over direct operator connections. - Regulator: CA (Communications Authority of Kenya) - Sender-ID lead time: 5-7 business days - Sender-ID rules: CA + operator sender ID registration. Safaricom requires content templates approved per use case. English and Swahili scripts supported. - Compliance: Kenya Data Protection Act 2019 fully enforced (ODPC). Mandatory opt-in for promotional. Communications Authority of Kenya guidelines allow promotional messages only between 07:00 and 19:00. - Sources: CA https://www.ca.go.ke/ · CA consumer guidelines https://www.ca.go.ke/sites/default/files/2023-06/Consumer-Protection-Guidelines-and-Customer-Care-Standards.pdf ### A2P SMS regulations in Ethiopia URL: https://www.broadnet.me/regulations/ethiopia · Markdown: https://www.broadnet.me/regulations/ethiopia.md · Last reviewed: 2026-09-29 A2P SMS to Ethiopia is regulated by the Ethiopian Communications Authority (ECA). Sender IDs registered through Ethio Telecom (and now Safaricom Ethiopia). Amharic and English supported, with approval typically taking 10-14 business days. Recently liberalised market (Safaricom Ethiopia launched 2022). BroadNet carries this traffic over direct operator connections. - Regulator: ECA (Ethiopian Communications Authority) - Sender-ID lead time: 10-14 business days - Sender-ID rules: Sender IDs registered through Ethio Telecom (and now Safaricom Ethiopia). Amharic and English supported. - Compliance: Recently liberalised market (Safaricom Ethiopia launched 2022). Cross-border data restrictions; local entity recommended for direct billing. - Sources: ECA https://www.eca.et/ ### A2P SMS regulations in Tanzania URL: https://www.broadnet.me/regulations/tanzania · Markdown: https://www.broadnet.me/regulations/tanzania.md · Last reviewed: 2026-09-29 A2P SMS to Tanzania is regulated by the Tanzania Communications Regulatory Authority (TCRA). TCRA sender ID registration via the operator. English and Swahili scripts supported, with approval typically taking 5-10 business days. TCRA enforces opt-in for promotional. BroadNet carries this traffic over direct operator connections. - Regulator: TCRA (Tanzania Communications Regulatory Authority) - Sender-ID lead time: 5-10 business days - Sender-ID rules: TCRA sender ID registration via the operator. English and Swahili scripts supported. - Compliance: TCRA enforces opt-in for promotional. Personal Data Protection Act 2022 in force. - Sources: TCRA https://www.tcra.go.tz/ ### A2P SMS regulations in Uganda URL: https://www.broadnet.me/regulations/uganda · Markdown: https://www.broadnet.me/regulations/uganda.md · Last reviewed: 2026-09-29 A2P SMS to Uganda is regulated by the Uganda Communications Commission (UCC). UCC sender ID registration via the operator. English and Swahili supported, with approval typically taking 5-10 business days. UCC enforces opt-in for promotional. BroadNet carries this traffic over direct operator connections. - Regulator: UCC (Uganda Communications Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: UCC sender ID registration via the operator. English and Swahili supported. - Compliance: UCC enforces opt-in for promotional. Data Protection and Privacy Act 2019 in force. - Sources: UCC https://www.ucc.co.ug/ ### A2P SMS regulations in Ghana URL: https://www.broadnet.me/regulations/ghana · Markdown: https://www.broadnet.me/regulations/ghana.md · Last reviewed: 2026-09-29 A2P SMS to Ghana is regulated by the National Communications Authority (NCA-GH). NCA sender ID registration via operator. English primary; local languages acceptable in UCS-2, with approval typically taking 5-7 business days. Ghana Data Protection Act 2012 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: NCA-GH (National Communications Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: NCA sender ID registration via operator. English primary; local languages acceptable in UCS-2. - Compliance: Ghana Data Protection Act 2012 enforced. Mandatory opt-in for promotional. - Sources: NCA https://nca.org.gh/ ### A2P SMS regulations in Ivory Coast URL: https://www.broadnet.me/regulations/ivory-coast · Markdown: https://www.broadnet.me/regulations/ivory-coast.md · Last reviewed: 2026-09-29 A2P SMS to Ivory Coast is regulated by the Autorité de Régulation des Télécommunications de Côte d'Ivoire (ARTCI). ARTCI sender ID registration via operator. French primary; English acceptable, with approval typically taking 7-10 business days. Ivorian Data Protection Law 2013 in force. BroadNet carries this traffic over direct operator connections. - Regulator: ARTCI (Autorité de Régulation des Télécommunications de Côte d'Ivoire) - Sender-ID lead time: 7-10 business days - Sender-ID rules: ARTCI sender ID registration via operator. French primary; English acceptable. - Compliance: Ivorian Data Protection Law 2013 in force. - Sources: ARTCI https://artci.ci/ ### A2P SMS regulations in Senegal URL: https://www.broadnet.me/regulations/senegal · Markdown: https://www.broadnet.me/regulations/senegal.md · Last reviewed: 2026-09-29 A2P SMS to Senegal is regulated by the Autorité de Régulation des Télécommunications et des Postes (ARTP). ARTP sender ID registration via operator. French primary; English and Wolof acceptable, with approval typically taking 7-10 business days. Senegal Data Protection Law 2008 (CDP) in force. BroadNet carries this traffic over direct operator connections. - Regulator: ARTP (Autorité de Régulation des Télécommunications et des Postes) - Sender-ID lead time: 7-10 business days - Sender-ID rules: ARTP sender ID registration via operator. French primary; English and Wolof acceptable. - Compliance: Senegal Data Protection Law 2008 (CDP) in force. Cross-border data transfers regulated. - Sources: ARTP https://artp.sn/ ### A2P SMS regulations in Cameroon URL: https://www.broadnet.me/regulations/cameroon · Markdown: https://www.broadnet.me/regulations/cameroon.md · Last reviewed: 2026-09-29 A2P SMS to Cameroon is regulated by the Agence de Régulation des Télécommunications (ART). ART sender ID registration via operator. French and English (bilingual market), with approval typically taking 7-14 business days. Cameroon Cybersecurity Law 2010 governs PII. BroadNet carries this traffic over direct operator connections. - Regulator: ART (Agence de Régulation des Télécommunications) - Sender-ID lead time: 7-14 business days - Sender-ID rules: ART sender ID registration via operator. French and English (bilingual market). - Compliance: Cameroon Cybersecurity Law 2010 governs PII. Bilingual market — both French and English content required for some categories. - Sources: ART https://www.art.cm/ ### A2P SMS regulations in Angola URL: https://www.broadnet.me/regulations/angola · Markdown: https://www.broadnet.me/regulations/angola.md · Last reviewed: 2026-09-29 A2P SMS to Angola is regulated by the Instituto Angolano das Comunicações (INACOM). INACOM sender ID registration via operator. Portuguese primary; English acceptable, with approval typically taking 10-14 business days. Angola Data Protection Law 22/11 in force. BroadNet carries this traffic over direct operator connections. - Regulator: INACOM (Instituto Angolano das Comunicações) - Sender-ID lead time: 10-14 business days - Sender-ID rules: INACOM sender ID registration via operator. Portuguese primary; English acceptable. - Compliance: Angola Data Protection Law 22/11 in force. - Sources: INACOM https://inacom.gov.ao/ ### A2P SMS regulations in Mozambique URL: https://www.broadnet.me/regulations/mozambique · Markdown: https://www.broadnet.me/regulations/mozambique.md · Last reviewed: 2026-09-29 A2P SMS to Mozambique is regulated by the Instituto Nacional das Comunicações de Moçambique (INCM). INCM sender ID registration via operator. Portuguese primary, with approval typically taking 10-14 business days. PII handling per government framework. BroadNet carries this traffic over direct operator connections. - Regulator: INCM (Instituto Nacional das Comunicações de Moçambique) - Sender-ID lead time: 10-14 business days - Sender-ID rules: INCM sender ID registration via operator. Portuguese primary. - Compliance: PII handling per government framework. - Sources: INCM https://www.incm.gov.mz/ ### A2P SMS regulations in Madagascar URL: https://www.broadnet.me/regulations/madagascar · Markdown: https://www.broadnet.me/regulations/madagascar.md · Last reviewed: 2026-09-29 A2P SMS to Madagascar is regulated by the Autorité de Régulation des Technologies de Communication (ARTEC). ARTEC sender ID registration via operator. French and Malagasy supported, with approval typically taking 10-14 business days. BroadNet carries this traffic over direct operator connections. - Regulator: ARTEC (Autorité de Régulation des Technologies de Communication) - Sender-ID lead time: 10-14 business days - Sender-ID rules: ARTEC sender ID registration via operator. French and Malagasy supported. - Compliance: PII handled per ARTEC framework. - Sources: ARTEC https://www.artec.mg/ ### A2P SMS regulations in Zambia URL: https://www.broadnet.me/regulations/zambia · Markdown: https://www.broadnet.me/regulations/zambia.md · Last reviewed: 2026-09-29 A2P SMS to Zambia is regulated by the Zambia Information and Communications Technology Authority (ZICTA). ZICTA sender ID registration via operator. English primary; local languages acceptable, with approval typically taking 5-10 business days. Zambia Data Protection Act 2021 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: ZICTA (Zambia Information and Communications Technology Authority) - Sender-ID lead time: 5-10 business days - Sender-ID rules: ZICTA sender ID registration via operator. English primary; local languages acceptable. - Compliance: Zambia Data Protection Act 2021 enforced. - Sources: ZICTA https://www.zicta.zm/ ### A2P SMS regulations in Rwanda URL: https://www.broadnet.me/regulations/rwanda · Markdown: https://www.broadnet.me/regulations/rwanda.md · Last reviewed: 2026-09-29 A2P SMS to Rwanda is regulated by the Rwanda Utilities Regulatory Authority (RURA). RURA sender ID registration via operator. English, French, and Kinyarwanda supported, with approval typically taking 5-7 business days. Rwanda Data Protection Law 2021 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: RURA (Rwanda Utilities Regulatory Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: RURA sender ID registration via operator. English, French, and Kinyarwanda supported. - Compliance: Rwanda Data Protection Law 2021 enforced. Pro-digital regulator with fast turnaround. - Sources: RURA https://www.rura.rw/ ### A2P SMS regulations in Botswana URL: https://www.broadnet.me/regulations/botswana · Markdown: https://www.broadnet.me/regulations/botswana.md · Last reviewed: 2026-09-29 A2P SMS to Botswana is regulated by the Botswana Communications Regulatory Authority (BOCRA). BOCRA sender ID registration via operator. English primary; Setswana acceptable, with approval typically taking 5-7 business days. Botswana Data Protection Act 2018 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: BOCRA (Botswana Communications Regulatory Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: BOCRA sender ID registration via operator. English primary; Setswana acceptable. - Compliance: Botswana Data Protection Act 2018 enforced. - Sources: BOCRA https://www.bocra.org.bw/ ### A2P SMS regulations in Mauritius URL: https://www.broadnet.me/regulations/mauritius · Markdown: https://www.broadnet.me/regulations/mauritius.md · Last reviewed: 2026-09-29 A2P SMS to Mauritius is regulated by the Information and Communication Technologies Authority (ICTA). ICTA sender ID registration via operator. English and French both supported, with approval typically taking 5-7 business days. Mauritius Data Protection Act 2017 enforced (mature framework). BroadNet carries this traffic over direct operator connections. - Regulator: ICTA (Information and Communication Technologies Authority) - Sender-ID lead time: 5-7 business days - Sender-ID rules: ICTA sender ID registration via operator. English and French both supported. - Compliance: Mauritius Data Protection Act 2017 enforced (mature framework). - Sources: ICTA https://www.icta.mu/ ### A2P SMS regulations in Namibia URL: https://www.broadnet.me/regulations/namibia · Markdown: https://www.broadnet.me/regulations/namibia.md · Last reviewed: 2026-09-29 A2P SMS to Namibia is regulated by the Communications Regulatory Authority of Namibia (CRAN). CRAN sender ID registration via operator. English primary; Afrikaans and German acceptable, with approval typically taking 5-10 business days. Namibia draft DPL aligned with GDPR. BroadNet carries this traffic over direct operator connections. - Regulator: CRAN (Communications Regulatory Authority of Namibia) - Sender-ID lead time: 5-10 business days - Sender-ID rules: CRAN sender ID registration via operator. English primary; Afrikaans and German acceptable. - Compliance: Namibia draft DPL aligned with GDPR. - Sources: CRAN https://www.cran.na/ ### A2P SMS regulations in Vietnam URL: https://www.broadnet.me/regulations/vietnam · Markdown: https://www.broadnet.me/regulations/vietnam.md · Last reviewed: 2026-10-02 Brand names (sender IDs) for advertising SMS to Vietnam are issued through the national brand-name system run by the Authority of Information Security (AIS) under Decree 91/2020/ND-CP, and operators block names it has not issued. Allow 7-14 business days end to end. Cybersecurity Law 2018 + Decree 13/2023 (Personal Data Protection) enforced. BroadNet carries this traffic over direct operator connections. - Regulator: AIS (Authority of Information Security) - Sender-ID lead time: 7-14 business days - Sender-ID rules: Brand names (sender IDs) for advertising SMS are issued through the national brand-name system run by the Authority of Information Security under Decree 91/2020/ND-CP; operators block names it has not issued. Vietnamese diacritics supported in UCS-2. - Compliance: Cybersecurity Law 2018 + Decree 13/2023 (Personal Data Protection) enforced. Data residency rules for some categories. - Sources: AIS https://ais.gov.vn/ · Decree 91/2020 https://congbaocdn.chinhphu.vn/CongBaoCP/VanBan/2020/8/31908/32282-1-2020837-83891-2020-nd-cp.pdf ### A2P SMS regulations in Thailand URL: https://www.broadnet.me/regulations/thailand · Markdown: https://www.broadnet.me/regulations/thailand.md · Last reviewed: 2026-09-29 A2P SMS to Thailand is regulated by the National Broadcasting and Telecommunications Commission (NBTC). NBTC + operator sender ID registration. Thai (UCS-2) and English at parity, with approval typically taking 5-10 business days. PDPA 2019 (Thailand) enforced — GDPR-aligned. BroadNet carries this traffic over direct operator connections. - Regulator: NBTC (National Broadcasting and Telecommunications Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: NBTC + operator sender ID registration. Thai (UCS-2) and English at parity. - Compliance: PDPA 2019 (Thailand) enforced — GDPR-aligned. - Sources: NBTC https://www.nbtc.go.th/ ### A2P SMS regulations in Malaysia URL: https://www.broadnet.me/regulations/malaysia · Markdown: https://www.broadnet.me/regulations/malaysia.md · Last reviewed: 2026-09-29 A2P SMS to Malaysia is regulated by the Malaysian Communications and Multimedia Commission (MCMC). MCMC + operator sender ID registration. Bahasa Melayu, English, Chinese, Tamil all supported, with approval typically taking 5-7 business days. PDPA 2010 (Malaysia) enforced. BroadNet carries this traffic over direct operator connections. - Regulator: MCMC (Malaysian Communications and Multimedia Commission) - Sender-ID lead time: 5-7 business days - Sender-ID rules: MCMC + operator sender ID registration. Bahasa Melayu, English, Chinese, Tamil all supported. - Compliance: PDPA 2010 (Malaysia) enforced. Multi-script market — engine handles GSM-7 + UCS-2 mix. - Sources: MCMC https://www.mcmc.gov.my/ ### A2P SMS regulations in Sri Lanka URL: https://www.broadnet.me/regulations/sri-lanka · Markdown: https://www.broadnet.me/regulations/sri-lanka.md · Last reviewed: 2026-09-29 A2P SMS to Sri Lanka is regulated by the Telecommunications Regulatory Commission of Sri Lanka (TRCSL). TRCSL + operator sender ID registration. Sinhala, Tamil, English all supported, with approval typically taking 5-10 business days. Sri Lanka PDPA 2022 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: TRCSL (Telecommunications Regulatory Commission of Sri Lanka) - Sender-ID lead time: 5-10 business days - Sender-ID rules: TRCSL + operator sender ID registration. Sinhala, Tamil, English all supported. - Compliance: Sri Lanka PDPA 2022 enforced. Under the TRCSL promotional-messages guidelines, no promotional messages from 20:00 to 08:00. - Sources: TRCSL https://www.trc.gov.lk/ · TRCSL promo guidelines https://www.trc.gov.lk/content/files/guideline/PromotionalMessagesGuidelines.pdf ### A2P SMS regulations in Nepal URL: https://www.broadnet.me/regulations/nepal · Markdown: https://www.broadnet.me/regulations/nepal.md · Last reviewed: 2026-09-29 A2P SMS to Nepal is regulated by the Nepal Telecommunications Authority (NTA). NTA + operator sender ID registration. Nepali (Devanagari) and English supported, with approval typically taking 7-14 business days. Nepal IT Bill 2019 governs PII. BroadNet carries this traffic over direct operator connections. - Regulator: NTA (Nepal Telecommunications Authority) - Sender-ID lead time: 7-14 business days - Sender-ID rules: NTA + operator sender ID registration. Nepali (Devanagari) and English supported. - Compliance: Nepal IT Bill 2019 governs PII. - Sources: NTA https://www.nta.gov.np/ ### A2P SMS regulations in Cambodia URL: https://www.broadnet.me/regulations/cambodia · Markdown: https://www.broadnet.me/regulations/cambodia.md · Last reviewed: 2026-09-29 A2P SMS to Cambodia is regulated by the Telecommunications Regulator of Cambodia (TRC-KH). TRC-KH + operator sender ID registration. Khmer (UCS-2) and English supported, with approval typically taking 7-14 business days. Quiet hours 21:00-08:00 promotional. BroadNet carries this traffic over direct operator connections. - Regulator: TRC-KH (Telecommunications Regulator of Cambodia) - Sender-ID lead time: 7-14 business days - Sender-ID rules: TRC-KH + operator sender ID registration. Khmer (UCS-2) and English supported. - Compliance: TRC allows advertising SMS only between 08:00 and 21:00. Government framework on PII handling. - Sources: TRC https://www.trc.gov.kh/ · TRC news release https://www.trc.gov.kh/en/media/news-releases/17-news-release/ ### A2P SMS regulations in Singapore URL: https://www.broadnet.me/regulations/singapore · Markdown: https://www.broadnet.me/regulations/singapore.md · Last reviewed: 2026-10-02 A2P SMS to Singapore is regulated by the Infocomm Media Development Authority (IMDA). Alphanumeric sender IDs must be registered in the SMS Sender ID Registry (SSIR), run by SGNIC; SGNIC puts the process at about 19 calendar days. PDPA (Singapore) fully enforced. BroadNet carries this traffic over direct operator connections. - Regulator: IMDA (Infocomm Media Development Authority) - Sender-ID lead time: About 19 calendar days (SGNIC) - Sender-ID rules: SMS Sender ID Registry (SSIR), run by SGNIC for IMDA, mandatory since 31 January 2023: the organisation registers its alphanumeric sender IDs itself and selects the Participating Aggregators allowed to carry them. English primary; Chinese / Malay / Tamil supported. - Compliance: PDPA (Singapore) fully enforced. DNC (Do Not Call) registry honoured. SSIR registration mandatory — unregistered alphanumerics relabeled to 'Likely Scam'. - Sources: IMDA https://www.imda.gov.sg/ · SGNIC SSIR https://www.sgnic.sg/smsregistry/overview · SGNIC SSIR FAQ https://www.sgnic.sg/faq/sms-sender-id-registry ### A2P SMS regulations in Hong Kong URL: https://www.broadnet.me/regulations/hong-kong · Markdown: https://www.broadnet.me/regulations/hong-kong.md · Last reviewed: 2026-10-02 A2P SMS to Hong Kong is regulated by the Office of the Communications Authority (OFCA). OFCA's SMS Sender Registration Scheme is voluntary: registered senders' IDs carry a "#" prefix, and unregistered IDs are delivered without it. PDPO (Personal Data Privacy Ordinance) enforced by PCPD. BroadNet carries this traffic over direct operator connections. - Regulator: OFCA (Office of the Communications Authority) - Sender-ID lead time: Free-form (OFCA scheme voluntary) - Sender-ID rules: OFCA's SMS Sender Registration Scheme (since 28 December 2023) is voluntary: registered senders' IDs carry a "#" prefix, and unregistered IDs are still delivered without it. Chinese (Traditional) and English supported. - Compliance: PDPO (Personal Data Privacy Ordinance) enforced by PCPD. SMS Sender Registration Scheme means registered alphanumeric IDs get '#' prefix to distinguish from scams. - Sources: OFCA https://www.ofca.gov.hk/ · OFCA SSRS https://www.ofca.gov.hk/en/consumer_focus/guide/hot_topics/ssrs/index.html ### A2P SMS regulations in Taiwan URL: https://www.broadnet.me/regulations/taiwan · Markdown: https://www.broadnet.me/regulations/taiwan.md · Last reviewed: 2026-09-29 A2P SMS to Taiwan is regulated by the National Communications Commission (NCC-TW). NCC-TW + operator sender ID registration. Chinese (Traditional) and English supported, with approval typically taking 5-10 business days. Personal Data Protection Act enforced. BroadNet carries this traffic over direct operator connections. - Regulator: NCC-TW (National Communications Commission) - Sender-ID lead time: 5-10 business days - Sender-ID rules: NCC-TW + operator sender ID registration. Chinese (Traditional) and English supported. - Compliance: Personal Data Protection Act enforced. Mandatory opt-in for marketing. - Sources: NCC https://www.ncc.gov.tw/ ### A2P SMS regulations in Italy URL: https://www.broadnet.me/regulations/italy · Markdown: https://www.broadnet.me/regulations/italy.md · Last reviewed: 2026-09-29 A2P SMS to Italy is regulated by the Autorità per le Garanzie nelle Comunicazioni (AGCOM). Alphanumeric sender IDs allowed with operator registration. Italian STOP keyword honoured, with approval typically taking 5-7 business days. GDPR + Garante Privacy enforcement. BroadNet carries this traffic over direct operator connections. - Regulator: AGCOM (Autorità per le Garanzie nelle Comunicazioni) - Sender-ID lead time: 5-7 business days - Sender-ID rules: Alphanumeric sender IDs allowed with operator registration. Italian STOP keyword honoured. - Compliance: GDPR + Garante Privacy enforcement. - Sources: AGCOM https://www.agcom.it/ ### A2P SMS regulations in Spain URL: https://www.broadnet.me/regulations/spain · Markdown: https://www.broadnet.me/regulations/spain.md · Last reviewed: 2026-10-02 A2P SMS to Spain is regulated by the Comisión Nacional de los Mercados y la Competencia + Agencia Española de Protección de Datos (CNMC + AEPD). Alphanumeric sender IDs (aliases) must be registered in the CNMC alias registry, mandatory since 15 September 2026; the CNMC decides within 1 month. GDPR + LSSI-CE + AEPD enforcement. BroadNet carries this traffic over direct operator connections. - Regulator: CNMC + AEPD (Comisión Nacional de los Mercados y la Competencia + Agencia Española de Protección de Datos) - Sender-ID lead time: Up to 1 month (CNMC alias registry) - Sender-ID rules: Alphanumeric sender IDs (aliases) must be registered in the CNMC alias registry (Registro de Alias); since 15 September 2026 operators block unregistered aliases. Spanish STOP / BAJA keywords honoured. - Compliance: GDPR + LSSI-CE + AEPD enforcement. Robinson List honoured. - Sources: CNMC https://www.cnmc.es/ · AEPD https://www.aepd.es/ · CNMC Registro de Alias https://www.cnmc.es/sectores-que-regulamos/telecomunicaciones/registro-alias · CNMC alias guide https://www.cnmc.es/sites/default/files/editor_contenidos/Telecomunicaciones/Registro%20alias_DUV_.pdf ### A2P SMS regulations in the Netherlands URL: https://www.broadnet.me/regulations/netherlands · Markdown: https://www.broadnet.me/regulations/netherlands.md · Last reviewed: 2026-10-19 A2P SMS to the Netherlands is regulated by the Autoriteit Consument & Markt and Autoriteit Persoonsgegevens (ACM + AP). Alphanumeric sender IDs allowed without formal registration but brand-identifiable. Dutch STOP keyword honoured. No pre-registration lead time applies. GDPR + Telecommunicatiewet. BroadNet carries this traffic over direct operator connections. - Regulator: ACM + AP (Autoriteit Consument & Markt and Autoriteit Persoonsgegevens) - Sender-ID lead time: Free-form - Sender-ID rules: Alphanumeric sender IDs allowed without formal registration but brand-identifiable. Dutch STOP keyword honoured. - Compliance: GDPR + Telecommunicatiewet. AP enforcement. - Sources: ACM https://www.acm.nl/ · AP https://www.autoriteitpersoonsgegevens.nl/ ### A2P SMS regulations in Belgium URL: https://www.broadnet.me/regulations/belgium · Markdown: https://www.broadnet.me/regulations/belgium.md · Last reviewed: 2026-10-19 A2P SMS to Belgium is regulated by the Belgian Institute for Postal Services and Telecommunications (BIPT). Alphanumeric sender IDs allowed without formal registration. French + Dutch STOP both honoured. No pre-registration lead time applies. GDPR + Belgian Telecoms Act. BroadNet carries this traffic over direct operator connections. - Regulator: BIPT (Belgian Institute for Postal Services and Telecommunications) - Sender-ID lead time: Free-form - Sender-ID rules: Alphanumeric sender IDs allowed without formal registration. French + Dutch STOP both honoured. - Compliance: GDPR + Belgian Telecoms Act. - Sources: BIPT https://www.bipt.be/ ### A2P SMS regulations in Poland URL: https://www.broadnet.me/regulations/poland · Markdown: https://www.broadnet.me/regulations/poland.md · Last reviewed: 2026-09-29 A2P SMS to Poland is regulated by the Urząd Komunikacji Elektronicznej (UKE). Alphanumeric sender ID registration via operator. Polish characters supported in UCS-2, with approval typically taking 5-10 business days. GDPR + UODO + Polish Telecoms Act. BroadNet carries this traffic over direct operator connections. - Regulator: UKE (Urząd Komunikacji Elektronicznej) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Alphanumeric sender ID registration via operator. Polish characters supported in UCS-2. - Compliance: GDPR + UODO + Polish Telecoms Act. - Sources: UKE https://www.uke.gov.pl/ ### A2P SMS regulations in Romania URL: https://www.broadnet.me/regulations/romania · Markdown: https://www.broadnet.me/regulations/romania.md · Last reviewed: 2026-09-29 A2P SMS to Romania is regulated by the Autoritatea Națională pentru Administrare și Reglementare în Comunicații (ANCOM). Alphanumeric sender ID registration via operator. Romanian diacritics supported, with approval typically taking 5-10 business days. GDPR + ANSPDCP enforcement. BroadNet carries this traffic over direct operator connections. - Regulator: ANCOM (Autoritatea Națională pentru Administrare și Reglementare în Comunicații) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Alphanumeric sender ID registration via operator. Romanian diacritics supported. - Compliance: GDPR + ANSPDCP enforcement. - Sources: ANCOM https://www.ancom.ro/ ### A2P SMS regulations in Ukraine URL: https://www.broadnet.me/regulations/ukraine · Markdown: https://www.broadnet.me/regulations/ukraine.md · Last reviewed: 2026-09-29 A2P SMS to Ukraine is regulated by the National Commission for the State Regulation of Electronic Communications and Radio Frequency Spectrum (NCEC). NCEC + operator sender ID registration. Ukrainian (Cyrillic) supported in UCS-2, with approval typically taking 7-14 business days. Law on Protection of Personal Data enforced. BroadNet carries this traffic over direct operator connections. - Regulator: NCEC (National Commission for the State Regulation of Electronic Communications and Radio Frequency Spectrum) - Sender-ID lead time: 7-14 business days - Sender-ID rules: NCEC + operator sender ID registration. Ukrainian (Cyrillic) supported in UCS-2. - Compliance: Law on Protection of Personal Data enforced. Sanctions screening on counterparties. Cross-border data restrictions. - Sources: NCEC https://nkek.gov.ua/ ### A2P SMS regulations in Sweden URL: https://www.broadnet.me/regulations/sweden · Markdown: https://www.broadnet.me/regulations/sweden.md · Last reviewed: 2026-10-19 A2P SMS to Sweden is regulated by the Post- och telestyrelsen (PTS). Alphanumeric sender IDs allowed without formal registration but brand-identifiable. Swedish characters in UCS-2. No pre-registration lead time applies. GDPR + Swedish Marketing Act enforced. BroadNet carries this traffic over direct operator connections. - Regulator: PTS (Post- och telestyrelsen) - Sender-ID lead time: Free-form - Sender-ID rules: Alphanumeric sender IDs allowed without formal registration but brand-identifiable. Swedish characters in UCS-2. - Compliance: GDPR + Swedish Marketing Act enforced. IMY supervises. - Sources: PTS https://www.pts.se/ ### A2P SMS regulations in Norway URL: https://www.broadnet.me/regulations/norway · Markdown: https://www.broadnet.me/regulations/norway.md · Last reviewed: 2026-10-19 A2P SMS to Norway is regulated by the Nasjonal kommunikasjonsmyndighet (Nkom). Alphanumeric sender IDs allowed without formal registration. Norwegian characters in UCS-2. No pre-registration lead time applies. GDPR + Norwegian Marketing Control Act + Datatilsynet supervision. BroadNet carries this traffic over direct operator connections. - Regulator: Nkom (Nasjonal kommunikasjonsmyndighet) - Sender-ID lead time: Free-form - Sender-ID rules: Alphanumeric sender IDs allowed without formal registration. Norwegian characters in UCS-2. - Compliance: GDPR + Norwegian Marketing Control Act + Datatilsynet supervision. - Sources: Nkom https://nkom.no/ ### A2P SMS regulations in Switzerland URL: https://www.broadnet.me/regulations/switzerland · Markdown: https://www.broadnet.me/regulations/switzerland.md · Last reviewed: 2026-10-19 A2P SMS to Switzerland is regulated by the Federal Office of Communications (OFCOM-CH). Alphanumeric sender IDs allowed without formal registration. German, French, Italian all supported. No pre-registration lead time applies. revFADP (Swiss FADP) enforced from 2023. BroadNet carries this traffic over direct operator connections. - Regulator: OFCOM-CH (Federal Office of Communications) - Sender-ID lead time: Free-form - Sender-ID rules: Alphanumeric sender IDs allowed without formal registration. German, French, Italian all supported. - Compliance: revFADP (Swiss FADP) enforced from 2023. GDPR-equivalent. - Sources: OFCOM https://www.bakom.admin.ch/ ### A2P SMS regulations in Ireland URL: https://www.broadnet.me/regulations/ireland · Markdown: https://www.broadnet.me/regulations/ireland.md · Last reviewed: 2026-10-02 A2P SMS to Ireland is regulated by the Commission for Communications Regulation (ComReg). Alphanumeric sender IDs must be registered in ComReg's SMS Sender ID Registry; since 3 July 2025, messages from unregistered IDs are labelled "Likely SCAM". GDPR + ePrivacy Regulations 2011. BroadNet carries this traffic over direct operator connections. - Regulator: ComReg (Commission for Communications Regulation) - Sender-ID lead time: No published time (ComReg registry) - Sender-ID rules: Alphanumeric sender IDs must be registered in ComReg's SMS Sender ID Registry (Decision D14/24). Since 3 July 2025, messages from unregistered IDs are labelled "Likely SCAM". - Compliance: GDPR + ePrivacy Regulations 2011. DPC (Data Protection Commission) supervises. - Sources: ComReg https://www.comreg.ie/ · ComReg SMS Sender ID Registry https://www.comreg.ie/industry/electronic-communications/nuisance-communications/sms-sender-id-registry/ · ComReg registry Q&A https://www.comreg.ie/industry/electronic-communications/nuisance-communications/sms-sender-id-registry/registry-qa/ ### A2P SMS regulations in Mexico URL: https://www.broadnet.me/regulations/mexico · Markdown: https://www.broadnet.me/regulations/mexico.md · Last reviewed: 2026-09-29 A2P SMS to Mexico is regulated by the Instituto Federal de Telecomunicaciones (IFT). IFT + operator sender ID registration. Spanish characters in UCS-2 or GSM-7, with approval typically taking 5-10 business days. LFPDPPP (Mexican Federal PDP Law) enforced by INAI. BroadNet carries this traffic over direct operator connections. - Regulator: IFT (Instituto Federal de Telecomunicaciones) - Sender-ID lead time: 5-10 business days - Sender-ID rules: IFT + operator sender ID registration. Spanish characters in UCS-2 or GSM-7. - Compliance: LFPDPPP (Mexican Federal PDP Law) enforced by INAI. PROFECO consumer-protection rules. - Sources: IFT https://www.ift.org.mx/ ### A2P SMS regulations in Argentina URL: https://www.broadnet.me/regulations/argentina · Markdown: https://www.broadnet.me/regulations/argentina.md · Last reviewed: 2026-09-29 A2P SMS to Argentina is regulated by the Ente Nacional de Comunicaciones (ENACOM). ENACOM + operator sender ID registration. Spanish supported, with approval typically taking 7-14 business days. Personal Data Protection Law 25.326 enforced by AAIP. BroadNet carries this traffic over direct operator connections. - Regulator: ENACOM (Ente Nacional de Comunicaciones) - Sender-ID lead time: 7-14 business days - Sender-ID rules: ENACOM + operator sender ID registration. Spanish supported. - Compliance: Personal Data Protection Law 25.326 enforced by AAIP. - Sources: ENACOM https://www.enacom.gob.ar/ ### A2P SMS regulations in Colombia URL: https://www.broadnet.me/regulations/colombia · Markdown: https://www.broadnet.me/regulations/colombia.md · Last reviewed: 2026-09-29 A2P SMS to Colombia is regulated by the Comisión de Regulación de Comunicaciones (CRC). CRC + operator sender ID registration. Spanish supported, with approval typically taking 5-10 business days. Habeas Data Law 1581/2012 (SIC enforcement). BroadNet carries this traffic over direct operator connections. - Regulator: CRC (Comisión de Regulación de Comunicaciones) - Sender-ID lead time: 5-10 business days - Sender-ID rules: CRC + operator sender ID registration. Spanish supported. - Compliance: Habeas Data Law 1581/2012 (SIC enforcement). Law 2300 of 2023 limits advertising SMS to Monday-Friday 07:00-19:00 and Saturday 08:00-15:00, never on Sundays or public holidays. - Sources: CRC https://www.crcom.gov.co/ · Ley 2300 de 2023 https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=213990 ### A2P SMS regulations in Chile URL: https://www.broadnet.me/regulations/chile · Markdown: https://www.broadnet.me/regulations/chile.md · Last reviewed: 2026-09-29 A2P SMS to Chile is regulated by the Subsecretaría de Telecomunicaciones (Subtel). Subtel + operator sender ID registration. Spanish supported, with approval typically taking 5-10 business days. Law 19.628 (Personal Data Protection) enforced. BroadNet carries this traffic over direct operator connections. - Regulator: Subtel (Subsecretaría de Telecomunicaciones) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Subtel + operator sender ID registration. Spanish supported. - Compliance: Law 19.628 (Personal Data Protection) enforced. - Sources: Subtel https://www.subtel.gob.cl/ ### A2P SMS regulations in Peru URL: https://www.broadnet.me/regulations/peru · Markdown: https://www.broadnet.me/regulations/peru.md · Last reviewed: 2026-09-29 A2P SMS to Peru is regulated by the Organismo Supervisor de Inversión Privada en Telecomunicaciones (Osiptel). Osiptel + operator sender ID registration. Spanish + Quechua supported in UCS-2, with approval typically taking 5-10 business days. Law 29733 (Personal Data Protection) enforced. BroadNet carries this traffic over direct operator connections. - Regulator: Osiptel (Organismo Supervisor de Inversión Privada en Telecomunicaciones) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Osiptel + operator sender ID registration. Spanish + Quechua supported in UCS-2. - Compliance: Law 29733 (Personal Data Protection) enforced. - Sources: Osiptel https://www.osiptel.gob.pe/ ### A2P SMS regulations in Ecuador URL: https://www.broadnet.me/regulations/ecuador · Markdown: https://www.broadnet.me/regulations/ecuador.md · Last reviewed: 2026-09-29 A2P SMS to Ecuador is regulated by the Agencia de Regulación y Control de las Telecomunicaciones (ARCOTEL). ARCOTEL + operator sender ID registration. Spanish supported, with approval typically taking 7-14 business days. Organic Personal Data Protection Law 2021 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: ARCOTEL (Agencia de Regulación y Control de las Telecomunicaciones) - Sender-ID lead time: 7-14 business days - Sender-ID rules: ARCOTEL + operator sender ID registration. Spanish supported. - Compliance: Organic Personal Data Protection Law 2021 enforced. - Sources: ARCOTEL https://www.arcotel.gob.ec/ ### A2P SMS regulations in Bolivia URL: https://www.broadnet.me/regulations/bolivia · Markdown: https://www.broadnet.me/regulations/bolivia.md · Last reviewed: 2026-09-29 A2P SMS to Bolivia is regulated by the Autoridad de Regulación y Fiscalización de Telecomunicaciones y Transportes (ATT). ATT + operator sender ID registration. Spanish + Quechua + Aymara supported, with approval typically taking 10-14 business days. Telecommunications Law and PII rules enforced. BroadNet carries this traffic over direct operator connections. - Regulator: ATT (Autoridad de Regulación y Fiscalización de Telecomunicaciones y Transportes) - Sender-ID lead time: 10-14 business days - Sender-ID rules: ATT + operator sender ID registration. Spanish + Quechua + Aymara supported. - Compliance: Telecommunications Law and PII rules enforced. - Sources: ATT https://www.att.gob.bo/ ### A2P SMS regulations in Uruguay URL: https://www.broadnet.me/regulations/uruguay · Markdown: https://www.broadnet.me/regulations/uruguay.md · Last reviewed: 2026-09-29 A2P SMS to Uruguay is regulated by the Unidad Reguladora de Servicios de Comunicaciones (URSEC). URSEC + operator sender ID registration. Spanish supported, with approval typically taking 5-10 business days. Law 18.331 (Personal Data Protection) enforced — GDPR-aligned. BroadNet carries this traffic over direct operator connections. - Regulator: URSEC (Unidad Reguladora de Servicios de Comunicaciones) - Sender-ID lead time: 5-10 business days - Sender-ID rules: URSEC + operator sender ID registration. Spanish supported. - Compliance: Law 18.331 (Personal Data Protection) enforced — GDPR-aligned. - Sources: URSEC https://www.gub.uy/unidad-reguladora-servicios-comunicaciones/ ### A2P SMS regulations in Canada URL: https://www.broadnet.me/regulations/canada · Markdown: https://www.broadnet.me/regulations/canada.md · Last reviewed: 2026-10-02 A2P SMS to Canada is regulated by the Canadian Radio-television and Telecommunications Commission (CRTC). Common short codes are assigned by the Canadian Telecommunications Association (txt.ca) and take 3–6 weeks to provision after approval. CASL (Canadian Anti-Spam Legislation) enforced — explicit/implied consent, opt-out on every commercial message. BroadNet carries this traffic over direct operator connections. - Regulator: CRTC (Canadian Radio-television and Telecommunications Commission) - Sender-ID lead time: 3–6 weeks (short codes, after txt.ca approval) - Sender-ID rules: Common short codes are assigned by the Canadian Telecommunications Association (txt.ca) and take 3–6 weeks to provision after approval. Long-code requirements are set by the carriers; BroadNet confirms them during onboarding. CASL opt-in required. - Compliance: CASL (Canadian Anti-Spam Legislation) enforced — explicit/implied consent, opt-out on every commercial message. PIPEDA governs PII. English + French both required for some categories. - Sources: CRTC https://crtc.gc.ca/ · txt.ca https://www.txt.ca/en/apply-for-a-short-code/ ### A2P SMS regulations in Australia URL: https://www.broadnet.me/regulations/australia · Markdown: https://www.broadnet.me/regulations/australia.md · Last reviewed: 2026-10-02 A2P SMS to Australia is regulated by the Australian Communications and Media Authority (ACMA). Alphanumeric sender IDs must be in the ACMA SMS Sender ID Register; since 1 July 2026, unregistered IDs are shown as "Unverified". Allow 5-10 business days. Spam Act 2003 + Privacy Act 1988 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: ACMA (Australian Communications and Media Authority) - Sender-ID lead time: 5-10 business days - Sender-ID rules: Alphanumeric sender IDs must be in the ACMA SMS Sender ID Register (Telecommunications (SMS Sender ID Register) Industry Standard 2025); since 1 July 2026, unregistered IDs are shown as "Unverified". Numeric senders also acceptable. - Compliance: Spam Act 2003 + Privacy Act 1988 enforced. The SMS Sender ID Register Industry Standard and Determination 2025 require sender-ID registration. - Sources: ACMA https://www.acma.gov.au/ · ACMA SMS Sender ID Register https://www.acma.gov.au/sms-sender-id-register ### A2P SMS regulations in New Zealand URL: https://www.broadnet.me/regulations/new-zealand · Markdown: https://www.broadnet.me/regulations/new-zealand.md · Last reviewed: 2026-10-02 Commercial SMS to New Zealand falls under the Unsolicited Electronic Messages Act 2007, enforced by the Department of Internal Affairs (DIA). No sender-ID registry has been published; sender IDs should identify the business. Unsolicited Electronic Messages Act 2007 + Privacy Act 2020 enforced. BroadNet carries this traffic over direct operator connections. - Regulator: DIA (Department of Internal Affairs) - Sender-ID lead time: Free-form - Sender-ID rules: No sender-ID registry has been published for New Zealand; alphanumeric sender IDs should identify the business, and operator requirements are confirmed during onboarding. - Compliance: Unsolicited Electronic Messages Act 2007 + Privacy Act 2020 enforced. OPC supervises. - Sources: DIA https://www.dia.govt.nz/ · DIA anti-spam https://www.dia.govt.nz/Services-Anti-Spam-Index ## Coverage by country - [the UAE](https://www.broadnet.me/coverage/uae) (Markdown: https://www.broadnet.me/coverage/uae.md): BroadNet delivers A2P SMS and OTP in the UAE over direct connections to Etisalat / e& and du, plus an operator-grade route to Virgin Mobile, with TDRA sender ID registration in 5-7 business days. SMS from $0.0123/message (indicative list rate, 2026-09-24). - [Saudi Arabia](https://www.broadnet.me/coverage/saudi-arabia) (Markdown: https://www.broadnet.me/coverage/saudi-arabia.md): BroadNet delivers A2P SMS and OTP in Saudi Arabia over direct connections to STC, Mobily, and Zain KSA, plus an operator-grade route to Virgin Mobile KSA, with CST sender ID registration in 5-10 business days. SMS from $0.0160/message (indicative list rate, 2026-09-24). - [Egypt](https://www.broadnet.me/coverage/egypt) (Markdown: https://www.broadnet.me/coverage/egypt.md): BroadNet delivers A2P SMS and OTP in Egypt over direct connections to Vodafone Egypt, Orange Egypt, e& Egypt, and WE, with NTRA sender ID registration in 7-14 business days. SMS from $0.0280/message (indicative list rate, 2026-09-24). - [Jordan](https://www.broadnet.me/coverage/jordan) (Markdown: https://www.broadnet.me/coverage/jordan.md): BroadNet delivers A2P SMS and OTP in Jordan over direct connections to Zain Jordan, Orange Jordan, and Umniah, with TRC sender ID registration in 5-7 business days. SMS from $0.0155/message (indicative list rate, 2026-09-24). - [Kuwait](https://www.broadnet.me/coverage/kuwait) (Markdown: https://www.broadnet.me/coverage/kuwait.md): BroadNet delivers A2P SMS and OTP in Kuwait over direct connections to Zain Kuwait, STC Kuwait, and Ooredoo Kuwait, with CITRA sender ID registration in 5-7 business days. SMS from $0.0163/message (indicative list rate, 2026-09-24). - [Qatar](https://www.broadnet.me/coverage/qatar) (Markdown: https://www.broadnet.me/coverage/qatar.md): BroadNet delivers A2P SMS and OTP in Qatar over direct connections to Ooredoo Qatar and Vodafone Qatar, with CRA sender ID registration in 5-7 business days. SMS from $0.0151/message (indicative list rate, 2026-09-24). - [Bahrain](https://www.broadnet.me/coverage/bahrain) (Markdown: https://www.broadnet.me/coverage/bahrain.md): BroadNet delivers A2P SMS and OTP in Bahrain over direct connections to Batelco, stc Bahrain, and Zain Bahrain, with TRA-BH sender ID registration in 5-7 business days. SMS from $0.0159/message (indicative list rate, 2026-09-24). - [Oman](https://www.broadnet.me/coverage/oman) (Markdown: https://www.broadnet.me/coverage/oman.md): BroadNet delivers A2P SMS and OTP in Oman over direct connections to Omantel, Ooredoo Oman, and Vodafone Oman, with TRA-Oman sender ID registration in 5-10 business days. SMS from $0.0156/message (indicative list rate, 2026-09-24). - [Iraq](https://www.broadnet.me/coverage/iraq) (Markdown: https://www.broadnet.me/coverage/iraq.md): BroadNet delivers A2P SMS and OTP in Iraq over direct connections to Asiacell, Zain Iraq, and Korek, with CMC sender ID registration in 7-14 business days. SMS from $0.0450/message (indicative list rate, 2026-09-24). - [Palestine](https://www.broadnet.me/coverage/palestine) (Markdown: https://www.broadnet.me/coverage/palestine.md): BroadNet delivers A2P SMS and OTP in Palestine over direct connections to Jawwal and Wataniya, with MTIT sender ID registration in 7-10 business days. SMS from $0.0520/message (indicative list rate, 2026-09-24). - [Tunisia](https://www.broadnet.me/coverage/tunisia) (Markdown: https://www.broadnet.me/coverage/tunisia.md): BroadNet delivers A2P SMS and OTP in Tunisia over direct connections to Tunisie Telecom, Ooredoo Tunisia, and Orange Tunisia, with INT sender ID registration in 5-7 business days. SMS from $0.0460/message (indicative list rate, 2026-09-24). - [Algeria](https://www.broadnet.me/coverage/algeria) (Markdown: https://www.broadnet.me/coverage/algeria.md): BroadNet delivers A2P SMS and OTP in Algeria over direct connections to Mobilis, Djezzy, and Ooredoo Algeria, with ARPCE sender ID registration in 10-14 business days. SMS from $0.0540/message (indicative list rate, 2026-09-24). - [Morocco](https://www.broadnet.me/coverage/morocco) (Markdown: https://www.broadnet.me/coverage/morocco.md): BroadNet delivers A2P SMS and OTP in Morocco over direct connections to Maroc Telecom, Orange Morocco, and inwi, with ANRT sender ID registration in 5-10 business days. SMS from $0.0440/message (indicative list rate, 2026-09-24). - [Mauritania](https://www.broadnet.me/coverage/mauritania) (Markdown: https://www.broadnet.me/coverage/mauritania.md): BroadNet delivers A2P SMS and OTP in Mauritania over direct connections to Mauritel, Mattel, and Chinguitel, with ARE sender ID registration in 10-14 business days. SMS from $0.0640/message (indicative list rate, 2026-09-24). - [Djibouti](https://www.broadnet.me/coverage/djibouti) (Markdown: https://www.broadnet.me/coverage/djibouti.md): BroadNet delivers A2P SMS and OTP in Djibouti over direct connections to Djibouti Telecom, with MCPT sender ID registration in 10-14 business days. SMS from $0.0620/message (indicative list rate, 2026-09-24). - [Comoros](https://www.broadnet.me/coverage/comoros) (Markdown: https://www.broadnet.me/coverage/comoros.md): BroadNet delivers A2P SMS and OTP in Comoros over aggregator-direct routes to Comores Telecom and Telma Comores, with ANRTIC sender ID registration in 10-14 business days. SMS from $0.0720/message (indicative list rate, 2026-09-24). - [Lebanon](https://www.broadnet.me/coverage/lebanon) (Markdown: https://www.broadnet.me/coverage/lebanon.md): BroadNet delivers A2P SMS and OTP in Lebanon over direct connections to Alfa and Touch, with TRA sender ID registration in 3-5 business days. SMS from $0.0540/message (indicative list rate, 2026-09-24). - [Nigeria](https://www.broadnet.me/coverage/nigeria) (Markdown: https://www.broadnet.me/coverage/nigeria.md): BroadNet delivers A2P SMS and OTP in Nigeria over direct connections to MTN Nigeria, Airtel, Glo, and 9mobile, with NCC sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [South Africa](https://www.broadnet.me/coverage/south-africa) (Markdown: https://www.broadnet.me/coverage/south-africa.md): BroadNet delivers A2P SMS and OTP in South Africa over direct connections to Vodacom, MTN South Africa, Cell C, and Telkom Mobile; sender IDs need no formal pre-registration with ICASA. SMS from $0.0280/message (indicative list rate, 2026-09-24). - [Kenya](https://www.broadnet.me/coverage/kenya) (Markdown: https://www.broadnet.me/coverage/kenya.md): BroadNet delivers A2P SMS and OTP in Kenya over direct connections to Safaricom, Airtel Kenya, and Telkom Kenya, with CA sender ID registration in 5-7 business days. SMS from $0.0300/message (indicative list rate, 2026-09-24). - [Ethiopia](https://www.broadnet.me/coverage/ethiopia) (Markdown: https://www.broadnet.me/coverage/ethiopia.md): BroadNet delivers A2P SMS and OTP in Ethiopia over direct connections to Ethio Telecom and Safaricom Ethiopia, with ECA sender ID registration in 10-14 business days. SMS from $0.0520/message (indicative list rate, 2026-09-24). - [Tanzania](https://www.broadnet.me/coverage/tanzania) (Markdown: https://www.broadnet.me/coverage/tanzania.md): BroadNet delivers A2P SMS and OTP in Tanzania over direct connections to Vodacom Tanzania, Airtel Tanzania, Tigo, and Halotel, with TCRA sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [Uganda](https://www.broadnet.me/coverage/uganda) (Markdown: https://www.broadnet.me/coverage/uganda.md): BroadNet delivers A2P SMS and OTP in Uganda over direct connections to MTN Uganda, Airtel Uganda, and Lycamobile UG, with UCC sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [Ghana](https://www.broadnet.me/coverage/ghana) (Markdown: https://www.broadnet.me/coverage/ghana.md): BroadNet delivers A2P SMS and OTP in Ghana over direct connections to MTN Ghana, Telecel, and AirtelTigo, with NCA-GH sender ID registration in 5-7 business days. SMS from $0.0320/message (indicative list rate, 2026-09-24). - [Ivory Coast](https://www.broadnet.me/coverage/ivory-coast) (Markdown: https://www.broadnet.me/coverage/ivory-coast.md): BroadNet delivers A2P SMS and OTP in Ivory Coast over direct connections to Orange CI, MTN CI, and Moov CI, with ARTCI sender ID registration in 7-10 business days. SMS from $0.0360/message (indicative list rate, 2026-09-24). - [Senegal](https://www.broadnet.me/coverage/senegal) (Markdown: https://www.broadnet.me/coverage/senegal.md): BroadNet delivers A2P SMS and OTP in Senegal over direct connections to Sonatel, Free Sénégal, and Expresso, with ARTP sender ID registration in 7-10 business days. SMS from $0.0380/message (indicative list rate, 2026-09-24). - [Cameroon](https://www.broadnet.me/coverage/cameroon) (Markdown: https://www.broadnet.me/coverage/cameroon.md): BroadNet delivers A2P SMS and OTP in Cameroon over direct connections to MTN Cameroon, Orange Cameroon, and Camtel, with ART sender ID registration in 7-14 business days. SMS from $0.0380/message (indicative list rate, 2026-09-24). - [Angola](https://www.broadnet.me/coverage/angola) (Markdown: https://www.broadnet.me/coverage/angola.md): BroadNet delivers A2P SMS and OTP in Angola over direct connections to Unitel, Movicel, and Africell, with INACOM sender ID registration in 10-14 business days. SMS from $0.0480/message (indicative list rate, 2026-09-24). - [Mozambique](https://www.broadnet.me/coverage/mozambique) (Markdown: https://www.broadnet.me/coverage/mozambique.md): BroadNet delivers A2P SMS and OTP in Mozambique over direct connections to Vodacom Mozambique, mCel, and Movitel, with INCM sender ID registration in 10-14 business days. SMS from $0.0440/message (indicative list rate, 2026-09-24). - [Madagascar](https://www.broadnet.me/coverage/madagascar) (Markdown: https://www.broadnet.me/coverage/madagascar.md): BroadNet delivers A2P SMS and OTP in Madagascar over direct connections to Telma, Orange Madagascar, and Airtel Madagascar, with ARTEC sender ID registration in 10-14 business days. SMS from $0.0440/message (indicative list rate, 2026-09-24). - [Zambia](https://www.broadnet.me/coverage/zambia) (Markdown: https://www.broadnet.me/coverage/zambia.md): BroadNet delivers A2P SMS and OTP in Zambia over direct connections to Airtel Zambia, MTN Zambia, and Zamtel, with ZICTA sender ID registration in 5-10 business days. SMS from $0.0380/message (indicative list rate, 2026-09-24). - [Rwanda](https://www.broadnet.me/coverage/rwanda) (Markdown: https://www.broadnet.me/coverage/rwanda.md): BroadNet delivers A2P SMS and OTP in Rwanda over direct connections to MTN Rwanda and Airtel Rwanda, with RURA sender ID registration in 5-7 business days. SMS from $0.0320/message (indicative list rate, 2026-09-24). - [Botswana](https://www.broadnet.me/coverage/botswana) (Markdown: https://www.broadnet.me/coverage/botswana.md): BroadNet delivers A2P SMS and OTP in Botswana over direct connections to Mascom, Orange Botswana, and beMobile, with BOCRA sender ID registration in 5-7 business days. SMS from $0.0360/message (indicative list rate, 2026-09-24). - [Mauritius](https://www.broadnet.me/coverage/mauritius) (Markdown: https://www.broadnet.me/coverage/mauritius.md): BroadNet delivers A2P SMS and OTP in Mauritius over direct connections to Emtel, my.t Mobile, and Mahanagar Telephone, with ICTA sender ID registration in 5-7 business days. SMS from $0.0380/message (indicative list rate, 2026-09-24). - [Namibia](https://www.broadnet.me/coverage/namibia) (Markdown: https://www.broadnet.me/coverage/namibia.md): BroadNet delivers A2P SMS and OTP in Namibia over direct connections to MTC Namibia and TN Mobile, with CRAN sender ID registration in 5-10 business days. SMS from $0.0440/message (indicative list rate, 2026-09-24). - [India](https://www.broadnet.me/coverage/india) (Markdown: https://www.broadnet.me/coverage/india.md): BroadNet delivers A2P SMS and OTP in India over direct connections to Reliance Jio, Bharti Airtel, and Vi, plus an operator-grade route to BSNL, with TRAI sender ID registration in 3-7 business days (DLT header registration). SMS from $0.0022/message (indicative list rate, 2026-09-24). - [Pakistan](https://www.broadnet.me/coverage/pakistan) (Markdown: https://www.broadnet.me/coverage/pakistan.md): BroadNet delivers A2P SMS and OTP in Pakistan over direct connections to Jazz, Telenor Pakistan, Zong, and Ufone, with PTA sender ID registration in 7-14 business days. SMS from $0.0034/message (indicative list rate, 2026-09-24). - [Bangladesh](https://www.broadnet.me/coverage/bangladesh) (Markdown: https://www.broadnet.me/coverage/bangladesh.md): BroadNet delivers A2P SMS and OTP in Bangladesh over direct connections to Grameenphone, Robi Axiata, Banglalink, and Teletalk, with BTRC sender ID registration in 5-10 business days. SMS from $0.0027/message (indicative list rate, 2026-09-24). - [Indonesia](https://www.broadnet.me/coverage/indonesia) (Markdown: https://www.broadnet.me/coverage/indonesia.md): BroadNet delivers A2P SMS and OTP in Indonesia over direct connections to Telkomsel, Indosat Ooredoo H., XL, and Smartfren, with Komdigi sender ID registration in 5-10 business days. SMS from $0.0070/message (indicative list rate, 2026-09-24). - [Philippines](https://www.broadnet.me/coverage/philippines) (Markdown: https://www.broadnet.me/coverage/philippines.md): BroadNet delivers A2P SMS and OTP in Philippines over direct connections to Smart Communications, Globe Telecom, and DITO Telecommunity, with NTC sender ID registration in 5-10 business days. SMS from $0.0080/message (indicative list rate, 2026-09-24). - [Vietnam](https://www.broadnet.me/coverage/vietnam) (Markdown: https://www.broadnet.me/coverage/vietnam.md): BroadNet delivers A2P SMS and OTP in Vietnam over direct connections to Viettel, Vinaphone, and Mobifone, with AIS sender ID registration in 7-14 business days. SMS from $0.0360/message (indicative list rate, 2026-09-24). - [Thailand](https://www.broadnet.me/coverage/thailand) (Markdown: https://www.broadnet.me/coverage/thailand.md): BroadNet delivers A2P SMS and OTP in Thailand over direct connections to AIS, TrueMove H, and DTAC, with NBTC sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [Malaysia](https://www.broadnet.me/coverage/malaysia) (Markdown: https://www.broadnet.me/coverage/malaysia.md): BroadNet delivers A2P SMS and OTP in Malaysia over direct connections to Celcom Axiata, Maxis, Digi, and U Mobile, with MCMC sender ID registration in 5-7 business days. SMS from $0.0320/message (indicative list rate, 2026-09-24). - [Sri Lanka](https://www.broadnet.me/coverage/sri-lanka) (Markdown: https://www.broadnet.me/coverage/sri-lanka.md): BroadNet delivers A2P SMS and OTP in Sri Lanka over direct connections to Dialog Axiata, Mobitel, and Hutch Sri Lanka, with TRCSL sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [Nepal](https://www.broadnet.me/coverage/nepal) (Markdown: https://www.broadnet.me/coverage/nepal.md): BroadNet delivers A2P SMS and OTP in Nepal over direct connections to Nepal Telecom and Ncell, with NTA sender ID registration in 7-14 business days. SMS from $0.0360/message (indicative list rate, 2026-09-24). - [Cambodia](https://www.broadnet.me/coverage/cambodia) (Markdown: https://www.broadnet.me/coverage/cambodia.md): BroadNet delivers A2P SMS and OTP in Cambodia over direct connections to Cellcard, Smart Axiata, and Metfone, with TRC-KH sender ID registration in 7-14 business days. SMS from $0.0400/message (indicative list rate, 2026-09-24). - [Singapore](https://www.broadnet.me/coverage/singapore) (Markdown: https://www.broadnet.me/coverage/singapore.md): BroadNet delivers A2P SMS and OTP in Singapore over direct connections to Singtel, StarHub, and M1; sender IDs are registered with IMDA (lead time: About 19 calendar days (SGNIC)). SMS from $0.0440/message (indicative list rate, 2026-09-24). - [Hong Kong](https://www.broadnet.me/coverage/hong-kong) (Markdown: https://www.broadnet.me/coverage/hong-kong.md): BroadNet delivers A2P SMS and OTP in Hong Kong over direct connections to CSL Mobile, China Mobile HK, 3HK, and SmarTone; sender IDs need no formal pre-registration with OFCA. SMS from $0.0460/message (indicative list rate, 2026-09-24). - [Taiwan](https://www.broadnet.me/coverage/taiwan) (Markdown: https://www.broadnet.me/coverage/taiwan.md): BroadNet delivers A2P SMS and OTP in Taiwan over direct connections to Chunghwa Telecom, Taiwan Mobile, and FarEasTone, with NCC-TW sender ID registration in 5-10 business days. SMS from $0.0520/message (indicative list rate, 2026-09-24). - [the United Kingdom](https://www.broadnet.me/coverage/united-kingdom) (Markdown: https://www.broadnet.me/coverage/united-kingdom.md): BroadNet delivers A2P SMS and OTP in the United Kingdom over direct connections to EE, Vodafone UK, O2, and Three UK; sender IDs need no formal pre-registration with ICO + Ofcom. SMS from $0.0300/message (indicative list rate, 2026-09-24). - [Germany](https://www.broadnet.me/coverage/germany) (Markdown: https://www.broadnet.me/coverage/germany.md): BroadNet delivers A2P SMS and OTP in Germany over direct connections to Telekom Deutschland, Vodafone Germany, and Telefónica O2; sender IDs need no formal pre-registration with BNetzA. SMS from $0.0800/message (indicative list rate, 2026-09-24). - [France](https://www.broadnet.me/coverage/france) (Markdown: https://www.broadnet.me/coverage/france.md): BroadNet delivers A2P SMS and OTP in France over direct connections to Orange France, SFR, Bouygues Telecom, and Free Mobile, with ARCEP sender ID registration in 5-10 business days (alphanumeric). SMS from $0.0750/message (indicative list rate, 2026-09-24). - [Italy](https://www.broadnet.me/coverage/italy) (Markdown: https://www.broadnet.me/coverage/italy.md): BroadNet delivers A2P SMS and OTP in Italy over direct connections to TIM, Vodafone Italy, WINDTRE, and Iliad Italy, with AGCOM sender ID registration in 5-7 business days. SMS from $0.0700/message (indicative list rate, 2026-09-24). - [Spain](https://www.broadnet.me/coverage/spain) (Markdown: https://www.broadnet.me/coverage/spain.md): BroadNet delivers A2P SMS and OTP in Spain over direct connections to Movistar, Vodafone Spain, Orange Spain, and MásMóvil; sender IDs are registered with CNMC + AEPD (lead time: Up to 1 month (CNMC alias registry)). SMS from $0.0650/message (indicative list rate, 2026-09-24). - [the Netherlands](https://www.broadnet.me/coverage/netherlands) (Markdown: https://www.broadnet.me/coverage/netherlands.md): BroadNet delivers A2P SMS and OTP in the Netherlands over direct connections to KPN, Vodafone Netherlands, and Odido; sender IDs need no formal pre-registration with ACM + AP. SMS from $0.0680/message (indicative list rate, 2026-09-24). - [Belgium](https://www.broadnet.me/coverage/belgium) (Markdown: https://www.broadnet.me/coverage/belgium.md): BroadNet delivers A2P SMS and OTP in Belgium over direct connections to Proximus, Orange Belgium, and Telenet/BASE; sender IDs need no formal pre-registration with BIPT. SMS from $0.0700/message (indicative list rate, 2026-09-24). - [Poland](https://www.broadnet.me/coverage/poland) (Markdown: https://www.broadnet.me/coverage/poland.md): BroadNet delivers A2P SMS and OTP in Poland over direct connections to Orange Polska, T-Mobile Polska, Play, and Plus, with UKE sender ID registration in 5-10 business days. SMS from $0.0480/message (indicative list rate, 2026-09-24). - [Romania](https://www.broadnet.me/coverage/romania) (Markdown: https://www.broadnet.me/coverage/romania.md): BroadNet delivers A2P SMS and OTP in Romania over direct connections to Vodafone Romania, Orange Romania, Digi Romania, and Telekom Romania, with ANCOM sender ID registration in 5-10 business days. SMS from $0.0440/message (indicative list rate, 2026-09-24). - [Türkiye](https://www.broadnet.me/coverage/turkey) (Markdown: https://www.broadnet.me/coverage/turkey.md): BroadNet delivers A2P SMS and OTP in Türkiye over direct connections to Turkcell, Vodafone Türkiye, and Türk Telekom, with BTK sender ID registration in 5-7 business days. SMS from $0.0320/message (indicative list rate, 2026-09-24). - [Ukraine](https://www.broadnet.me/coverage/ukraine) (Markdown: https://www.broadnet.me/coverage/ukraine.md): BroadNet delivers A2P SMS and OTP in Ukraine over direct connections to Kyivstar, Vodafone Ukraine, and lifecell, with NCEC sender ID registration in 7-14 business days. SMS from $0.0480/message (indicative list rate, 2026-09-24). - [Sweden](https://www.broadnet.me/coverage/sweden) (Markdown: https://www.broadnet.me/coverage/sweden.md): BroadNet delivers A2P SMS and OTP in Sweden over direct connections to Telia Sweden, Telenor Sweden, Tele2, and Tre Sweden; sender IDs need no formal pre-registration with PTS. SMS from $0.0640/message (indicative list rate, 2026-09-24). - [Norway](https://www.broadnet.me/coverage/norway) (Markdown: https://www.broadnet.me/coverage/norway.md): BroadNet delivers A2P SMS and OTP in Norway over direct connections to Telenor Norway, Telia Norway, and Ice Norway; sender IDs need no formal pre-registration with Nkom. SMS from $0.0720/message (indicative list rate, 2026-09-24). - [Switzerland](https://www.broadnet.me/coverage/switzerland) (Markdown: https://www.broadnet.me/coverage/switzerland.md): BroadNet delivers A2P SMS and OTP in Switzerland over direct connections to Swisscom, Sunrise, and Salt; sender IDs need no formal pre-registration with OFCOM-CH. SMS from $0.0840/message (indicative list rate, 2026-09-24). - [Ireland](https://www.broadnet.me/coverage/ireland) (Markdown: https://www.broadnet.me/coverage/ireland.md): BroadNet delivers A2P SMS and OTP in Ireland over direct connections to Vodafone Ireland, Three Ireland, and Eir; sender IDs are registered with ComReg (lead time: No published time (ComReg registry)). SMS from $0.0600/message (indicative list rate, 2026-09-24). - [Brazil](https://www.broadnet.me/coverage/brazil) (Markdown: https://www.broadnet.me/coverage/brazil.md): BroadNet delivers A2P SMS and OTP in Brazil over direct connections to Vivo, Claro Brasil, TIM Brasil, and Oi, with Anatel sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [Mexico](https://www.broadnet.me/coverage/mexico) (Markdown: https://www.broadnet.me/coverage/mexico.md): BroadNet delivers A2P SMS and OTP in Mexico over direct connections to Telcel, AT&T Mexico, and Movistar Mexico, with IFT sender ID registration in 5-10 business days. SMS from $0.0280/message (indicative list rate, 2026-09-24). - [Argentina](https://www.broadnet.me/coverage/argentina) (Markdown: https://www.broadnet.me/coverage/argentina.md): BroadNet delivers A2P SMS and OTP in Argentina over direct connections to Personal, Movistar Argentina, and Claro Argentina, with ENACOM sender ID registration in 7-14 business days. SMS from $0.0360/message (indicative list rate, 2026-09-24). - [Colombia](https://www.broadnet.me/coverage/colombia) (Markdown: https://www.broadnet.me/coverage/colombia.md): BroadNet delivers A2P SMS and OTP in Colombia over direct connections to Claro Colombia, Movistar Colombia, and Tigo Colombia, with CRC sender ID registration in 5-10 business days. SMS from $0.0300/message (indicative list rate, 2026-09-24). - [Chile](https://www.broadnet.me/coverage/chile) (Markdown: https://www.broadnet.me/coverage/chile.md): BroadNet delivers A2P SMS and OTP in Chile over direct connections to Entel Chile, Movistar Chile, Claro Chile, and WOM, with Subtel sender ID registration in 5-10 business days. SMS from $0.0340/message (indicative list rate, 2026-09-24). - [Peru](https://www.broadnet.me/coverage/peru) (Markdown: https://www.broadnet.me/coverage/peru.md): BroadNet delivers A2P SMS and OTP in Peru over direct connections to Claro Peru, Movistar Peru, Entel Peru, and Bitel, with Osiptel sender ID registration in 5-10 business days. SMS from $0.0320/message (indicative list rate, 2026-09-24). - [Ecuador](https://www.broadnet.me/coverage/ecuador) (Markdown: https://www.broadnet.me/coverage/ecuador.md): BroadNet delivers A2P SMS and OTP in Ecuador over direct connections to Claro Ecuador, Movistar Ecuador, and CNT EP, with ARCOTEL sender ID registration in 7-14 business days. SMS from $0.0380/message (indicative list rate, 2026-09-24). - [Bolivia](https://www.broadnet.me/coverage/bolivia) (Markdown: https://www.broadnet.me/coverage/bolivia.md): BroadNet delivers A2P SMS and OTP in Bolivia over direct connections to Entel Bolivia, Tigo Bolivia, and Viva, with ATT sender ID registration in 10-14 business days. SMS from $0.0400/message (indicative list rate, 2026-09-24). - [Uruguay](https://www.broadnet.me/coverage/uruguay) (Markdown: https://www.broadnet.me/coverage/uruguay.md): BroadNet delivers A2P SMS and OTP in Uruguay over direct connections to Antel, Movistar Uruguay, and Claro Uruguay, with URSEC sender ID registration in 5-10 business days. SMS from $0.0400/message (indicative list rate, 2026-09-24). - [the USA](https://www.broadnet.me/coverage/united-states) (Markdown: https://www.broadnet.me/coverage/united-states.md): BroadNet delivers A2P SMS and OTP in the USA over direct connections to T-Mobile USA, AT&T, and Verizon, plus an operator-grade route to US Cellular, with FCC + CTIA sender ID registration in 7-14 business days (10DLC). SMS from $0.0095/message (indicative list rate, 2026-09-24). - [Canada](https://www.broadnet.me/coverage/canada) (Markdown: https://www.broadnet.me/coverage/canada.md): BroadNet delivers A2P SMS and OTP in Canada over direct connections to Rogers, Bell Canada, and Telus, with CRTC sender ID registration in 3–6 weeks (short codes, after txt.ca approval). SMS from $0.0170/message (indicative list rate, 2026-09-24). - [Australia](https://www.broadnet.me/coverage/australia) (Markdown: https://www.broadnet.me/coverage/australia.md): BroadNet delivers A2P SMS and OTP in Australia over direct connections to Telstra, Optus, and Vodafone Australia, with ACMA sender ID registration in 5-10 business days. SMS from $0.0460/message (indicative list rate, 2026-09-24). - [New Zealand](https://www.broadnet.me/coverage/new-zealand) (Markdown: https://www.broadnet.me/coverage/new-zealand.md): BroadNet delivers A2P SMS and OTP in New Zealand over direct connections to Spark NZ, One NZ, and 2degrees; sender IDs need no formal pre-registration with DIA. SMS from $0.0460/message (indicative list rate, 2026-09-24). --- End of corpus. Link index: https://www.broadnet.me/llms.txt