South African SIP trunking and numbers,
run by the team that sets them up.

South African SIP trunking and numbers, run by the team that sets them up

A South African SIP trunk carries your voice traffic on the South African direction — outbound campaigns, inbound support, the calls your customers actually make and take — into the phone system you already run. VoipTower provides the trunk and the South African numbers that ride on it, then configures the routing, the PBX connection, and the ongoing operation behind both. The numbers come from the carrier. The setup and the support come from us.

That second half is where most providers wave goodbye. A trunk is easy to sell and harder to make work inside a real call operation, especially across a border, and a number on its own does nothing until something routes it. This page covers the trunk and the numbers behind it for the South African market — how the connection is built, what the local numbering actually looks like, and what it costs to run.

The South African numbering plan, and the digit that trips people up

South African numbers are administered by ICASA under the Numbering Plan Regulations, 2016 (Government Gazette No. 39861, Notice No. 370 of 2016), currently under amendment. The shape that matters for anyone choosing a number: the national significant number is nine digits, and inside the country it is dialled with a leading trunk prefix 0 — so a domestic number reads as ten digits, while internationally the same number is +27 followed by the nine digits, dropping the 0.

That trunk-0 is the detail that catches people who have set up numbers elsewhere. It is also the cleanest way to see that South Africa is not interchangeable with other nine-digit markets: a Polish national number is also nine digits and also closed, but Poland is dialled without a trunk prefix, where South Africa keeps the leading 0. Same digit count, different dialling reality — copy the wrong country's habit and the number won't read right.

Mobile sits on the 06x, 07x, and 08x ranges. There is also a number type that does not exist in most of the markets we cover: 087, a non-geographic range used specifically for VoIP and cloud business lines — a national-feeling number with no city tie, which is often the right pick for an operation that does not want to look pinned to one metro. Toll-free is 0800.

Side note on the city codes: treat them as a guide, not a guarantee of where someone sits. South Africa has had full number portability across all number types since 2022, so an 011 line does not strictly prove a Johannesburg address any more — the code signals origin and reads as local, which for a business presence is the point.

What the documents look like — and what they don't require

South African geographic numbers are provisioned through more than one carrier-partner, and the paperwork depends on which one serves your order. It is worth being exact, because "easy" and "impossible" are both wrong.

What stays true across both paths is the part that surprises people: there is no South African company, no South African director, and no South African address required. The certificate, the ID, and the address can all be from any country. So the honest line is neither "nothing beyond standard onboarding" (true only for the lighter path) nor "you need a local presence" (false for both) — it is that, depending on the serving partner, a company certificate, director ID, and Letter of Intent may be part of provisioning a South African geographic number, none of it South African.

Onboarding, timelines, and what a South African number costs

Three timelines run on different clocks, and collapsing them into one is where "instant setup" claims go wrong. Platform onboarding — the KYC and business-case review — is usually about a day. The first South African number lands in roughly five business days. Once you are already running in a country, a repeat order pulls from stock held against your account and arrives far quicker, somewhere between an hour and a single business day. The number request itself is immediate; the five days is the provisioning behind it.

The configuration work — setup, integration, the SIP-trunk build, routing — sits inside those rates; there is no separate professional-services invoice on top. A note on the single outbound rate, because it differs from some other markets we run: South Africa is priced as one outbound figure for landline and mobile, not split into two. That is a deliberate, current rate from the ordering system, not a simplification. The $10 monthly is also on the lower side of our country range — neutral fact, not a discount pitch; it is simply what a South African geographic number costs to hold.

(If you need outbound caller-ID routing as a distinct product — presenting a chosen number independent of the DID — that is a separate order line with its own rate, not part of the pricing above. We scope it directly when it comes up.)

Integration and how support actually works

A South African trunk is only useful once it lands in the tools your team already lives in. We connect over SIP — IP-to-IP or SIP credentials — into 3CX, Asterisk, FreePBX, FreeSWITCH, auto-dialers, and custom CRM workflows, built around your stack instead of replacing it. Extensions, queues, IVR, routing by department, language, or business hours, and backup destinations are configured to match how your operation actually handles calls. On codecs we run the standard set — G.711 a-law and µ-law, and G.729 where bandwidth is tighter.

Support is the part usually described worst elsewhere, so plainly: you get one dedicated chat where the engineer who knows your routing, your account manager, and billing are all present together. A change request, a new number, a routing adjustment, an invoice question — handled in the same place, no ticket queue, no being passed between departments. The monitoring and failover behind your numbers run continuously as part of the architecture; the people side is a single thread with a team that already knows your setup, not a rota of strangers reading a script.

Reliability on the South African direction comes from how the routing is built — multiple same-quality carrier routes, so an upstream problem on one moves traffic to another rather than dropping the call — and from that support model. It is worth knowing the local backdrop here: Telkom has been decommissioning its legacy copper network for years, an ongoing migration that is pushing South African voice onto IP whether businesses planned for it or not. Building on managed SIP rather than ageing copper is, increasingly, just where the market already is.

Common questions about South African business numbers

Five common questions from companies setting up voice on the South African direction.

For SIP, DID, and PBX integration in technical depth, see the services pages. For the full country list, the coverage hub. Pricing logic and the wider model are on the homepage, and onboarding starts at legal.voiptower.company.