Wholesale A2P SMS and voice for carriers and aggregators
Terminate A2P traffic through one managed interconnect instead of a patchwork of bilateral agreements. Bind over SMPP or HTTP, see quality per route and settle on records both sides can check.
# Wholesale SMPP bind (illustrative)
bind_type = bind_transceiver
host = smpp.example
port = 2776
tls = required
system_id = YOUR_SYSTEM_ID
password = YOUR_PASSWORD
system_type = WHOLESALE
interface_version = 0x34
window_size = 50
enquire_link = 30s
registered_delivery = 1
source_ton_npi = 5/0Illustrative SMPP bind settings for a wholesale interconnect. Placeholder values only; real credentials and endpoints are issued per partner.
Short answer
Updated
OmniChannels.ai wholesale gives carriers, aggregators and large platforms A2P SMS and voice termination through BroadNet's direct connections to more than 1,000 operators and aggregators. You interconnect over SMPP 3.4 with TLS or an HTTP API, receive delivery receipts on every message and per-route quality reporting, and settle against per-message CDRs. Voice is delivered over SIP. Rates are quoted per destination and tiered by committed volume.
What the wholesale interconnect includes
Direct SMPP interconnect over TLS
Dedicated SMPP 3.4 binds provisioned per partner, encrypted with TLS, with transmitter, receiver or transceiver sessions to suit your platform.
HTTP API as an alternative
Partners who prefer HTTP can submit through the REST API with bearer-token authentication and receive delivery statuses by webhook.
Termination and aggregation
Terminate A2P traffic across BroadNet's operator footprint, or aggregate traffic from your own clients onto a single interconnect.
Carrier hubbing
Operators can hand off international A2P traffic to one managed hub rather than maintaining a separate agreement with every destination network.
Per-route quality reporting
Delivery outcomes are reported per destination and route, so your NOC and commercial teams can see where traffic performs and where it does not.
Delivery receipts on every message
Delivery receipts return over your bind or as webhooks, with statuses normalised to SUBMITTED, SENT, DELIVERED, FAILED and REJECTED.
Firewall-protected routes
Traffic passes through SMS firewall controls that filter spoofed sender IDs, grey-route patterns and suspected fraud before it reaches a network.
Settlement and CDR reconciliation
Per-message CDRs support each settlement period, so billing differences are resolved against records rather than estimates.
Voice over SIP
Voice termination and programmable calling over SIP, including bring-your-own-carrier trunks, provisioned with the carrier team.
Ways to interconnect
Choose the connection that matches your traffic profile. Many partners combine more than one.
| Item | Details |
|---|---|
| SMPP 3.4 bind over TLS | For aggregators and platforms with their own SMPP stack and steady high volume. Binds, credentials and window sizes are provisioned per partner. |
| HTTP / REST API | For platforms that prefer HTTP submission with JSON responses and webhook delivery statuses. |
| Carrier hubbing | For operators handing off international A2P traffic to a single managed hub. Scoped with the carrier team. |
| Bilateral partnership | For carriers exchanging traffic in both directions, with commercial terms and settlement agreed in one contract. |
| Voice over SIP | For voice termination and programmable calling, including bring-your-own-carrier SIP trunks. |
How a wholesale interconnect goes live
Most of the time goes into commercial agreement and interoperability testing, which we run together with your NOC.
- 1
Share your traffic profile
Tell us your destinations, traffic types such as OTP or notifications, expected volumes and preferred connection method.
- 2
Agree rates and terms
Receive a rate card per destination and route, tiered by committed volume, and agree settlement and billing terms.
- 3
Provision and test the bind
We issue SMPP or API credentials, whitelist your addresses and run interoperability tests on encoding, sender IDs and delivery receipts.
- 4
Ramp up traffic
Start with controlled volume, review delivery and quality reports per route, then scale to your full traffic.
- 5
Reconcile and review
Reconcile CDRs at each settlement period and review route quality and volume with your account team.
Is wholesale interconnect right for you?
A good fit when
- You are a carrier, aggregator or platform terminating A2P SMS or voice at volume.
- You already run an SMPP stack or can integrate with an HTTP API.
- You need delivery receipts and route-level quality data you can act on, not just a sent count.
- Finance needs per-message records to reconcile settlement.
Good to know before you start
- Sender ID registration and content rules differ by country; some destinations need pre-registered senders or templates before traffic is accepted.
- Operators can block or filter traffic that breaks their rules, and firewall controls will reject spoofed or suspicious traffic.
- Postpaid and net-terms billing require a credit review; new partners usually start prepaid.
- Rates are not published. They depend on destination, route and committed volume, and are reviewed as operator costs change.
Coverage at a glance
Operator routes listed in our coverage guides, by region. Each country guide shows the operators, whether the route is direct, the regulator and the indicative SMS price.
- Middle East and North Africa47 operator routes · 17 countries
- Europe52 operator routes · 15 countries
- Asia47 operator routes · 14 countries
- Africa54 operator routes · 18 countries
- Latin America29 operator routes · 9 countries
- North America7 operator routes · 2 countries
- Oceania6 operator routes · 2 countries
Show as a table
| Region | countries | operator routes |
|---|---|---|
| Middle East and North Africa | 17 | 47 |
| Europe | 15 | 52 |
| Asia | 14 | 47 |
| Africa | 18 | 54 |
| Latin America | 9 | 29 |
| North America | 2 | 7 |
| Oceania | 2 | 6 |
Wholesale questions
Which SMPP version and security do you support?
SMPP 3.4, with TLS encryption on the bind. Binds are provisioned per partner with their own credentials, and the carrier team agrees session types and window sizes with you during interoperability testing.
Can I use HTTP instead of SMPP?
Yes. The REST API accepts message submissions with bearer-token authentication and returns delivery statuses through webhooks. Some partners use SMPP for bulk traffic and HTTP for lower-volume or event-driven sends.
How do you report route quality?
Delivery receipts come back on every message, and reports break outcomes down by destination and route. Your NOC can see where delivery is weak and raise it with the carrier team before it affects your clients.
How are settlement and disputes handled?
Settlement is based on per-message CDRs for each period. If your records and ours differ, the difference is reconciled message by message against those records rather than estimated.
Do you offer voice termination?
Yes. Voice runs over SIP and is provisioned with the carrier team rather than through public API endpoints. Bring-your-own-carrier SIP trunks are also supported.
Do you publish wholesale rates?
No. Rates depend on destination, route type and the volume you commit to, and operator costs change over time. You receive a rate card per destination during scoping, reviewed as your volume grows.
Guides on this topic
- SMS & OTPWhat Is A2P SMS? How Business Messages Reach the Handset8 min read
- UAE & Saudi ArabiaSMS Sender ID Registration in the UAE and Saudi Arabia Explained8 min read
- SMS & OTPSMS Pumping Fraud: How AIT Works and How to Stop It9 min read
- MarketingSent vs Delivered vs Read vs Failed: Message Status Explained8 min read
- SMS & OTPHLR Lookup Explained: What It Returns and When to Use It8 min read
- SMS & OTPSMS Character Limits: GSM-7, Unicode, Arabic and Emoji Explained8 min read
Explore more of the platform
Talk to the carrier team
Share your destinations, traffic types, expected volumes and preferred connection method. We will come back with a rate card and an interconnect plan.
Tell us about your business and clients. Our partnerships team will reply with the programme details and next steps.