What's in the stack.
Voice infrastructure, integration layer, codecs, and platform reliability under one contract. We set up the SIP trunk, codecs and routing of your numbers to your PBX, and help on your PBX side — in the same chat. Your PBX, dialer and CRM stay yours.
Voice infrastructure
DID numbers in 50+ countries. Outbound pools on the directions listed on the pricing page — numbers built per customer, monitored, and replaced when they degrade.
PBX and dialer integration
3CX, Asterisk, FreePBX, FreeSWITCH, Magnus Billing, and standards-compliant auto-dialer platforms. IP-to-IP or SIP credentials. We help connect calls to your CRM through your PBX or dialer — free, in the same chat. CRM-side development stays with your team or your CRM vendor.
Codecs
G.711 a-law, G.711 μ-law, G.729.
Platform reliability
Reliability, plainly. Your numbers run on a carrier chosen for that direction, and with clean traffic routes rarely misbehave. Monitoring runs around the clock, and anything that needs attention is handled in the same chat as your engineer and account manager.
Pricing model:
traffic and numbers,
engineering not billed separately.
VoipTower bills for traffic and numbers. No engineering or integration fees, no per-hour billing; each number has a setup and monthly fee, listed on the pricing page. PBX setup, configuration, monitoring and support come with the rates — not on top of them.
| You pay for | Included with the contract |
|---|---|
| DID numbers (setup + monthly) | Number provisioning and routing configuration |
| Outbound traffic (per-minute) | CRM: calls connected through your PBX or dialer — we help. |
| Inbound termination | SIP trunk setup for 3CX, Asterisk, FreePBX, FreeSWITCH — with help on your PBX side |
| — | SIP trunk setup for your auto-dialer |
| — | Each number is routed to your PBX; help with IVR on your PBX side |
| — | KYC token — onboard once, re-orders in hours not days |
| — | Compliance review at submission |
| — | Monitoring and engineering support |
The economics —
why “engineering included”
usually works out cheaper.
Voice operations cost more than the per-minute rates suggest. Build the same capability in-house and the bill includes a voice engineer, monitoring infrastructure, an on-call rotation, and the time your product team loses to phone problems that aren't their job.
Build the same capability yourself and the bill starts with a voice engineer’s salary, then adds monitoring, on-call coverage, and the management time to run all of it.
Wholesale-grade rates for numbers and traffic. The premium pays for the team that operates the routes. Current rates — setup, monthly, inbound and outbound per minute — are published on our pricing page — the same rates the order form uses.
Companies with real call volume and no in-house voice engineer — that is where the managed model comes out ahead. Companies that already run their own voice engineering team at very large traffic volumes usually build cheaper in-house — rational at that scale. We don’t try to be that vendor.
Country coverage.
Managed voice in 25+ countries; DID numbers in 50+ countries — see the pricing page. Number types and the current ETA for each country are on the pricing page; other types on request. Full per-country capability matrix on the countries hub.
| Country | Region | Status |
|---|---|---|
| Germany | Europe | Available |
| United Kingdom | Europe | Available |
| France | Europe | Available |
| Italy | Europe | Available |
| Spain | Europe | Available |
| Netherlands | Europe | Available |
| Romania | Europe | On request |
| Switzerland | Europe | Available |
| Sweden | Europe | On request |
| Norway | Europe | Available |
| Denmark | Europe | Available |
| Poland | Europe | Available |
| Czech Republic | Europe | Available |
| Argentina | Americas | Available |
| Brazil | Americas | Available |
| Mexico | Americas | Available |
| Canada | Americas | Available |
| Colombia | Americas | Available |
| Chile | Americas | Available |
| Israel | MENA | Available |
| United Arab Emirates | MENA | Available on request |
| Saudi Arabia | MENA | On request |
| Australia | APAC | Available |
| Singapore | APAC | Available |
| South Africa | Africa | Available |
Additional markets confirmed on request during onboarding.
Onboard once.
CLI compliance always.
Documents go through compliance once. The same verified company profile applies across every future order — new countries, new routes, new numbers — and the operational form takes about five minutes per order. Directions with a Local document scope also need proof of a local address.
A single KYC token
VoipTower issues one KYC token after the first onboarding. Re-orders inside countries where you already operate run from a pre-allocated stock held for your account. A re-order from your allocated stock typically arrives within 1 to 3 hours of the form. Overall, from about an hour, up to 1 business day. We keep stock because re-ordering numbers should not be a new project every time.
Compliance review at submission
The compliance check happens when you submit, not afterwards. You qualify and proceed, or you get clear feedback: your request is reviewed within about 24 hours. Nothing sits in silent rejection.
CLI routed only for confirmed ownership
VoipTower routes CLI only for numbers issued through the platform or ported in with confirmed ownership documentation. Arbitrary caller ID is not accepted. This is the operational filter that keeps routes clean — and it self-selects the customer base.
Frequently asked
questions.
Direct answers to the questions buyers ask during evaluation.
What is VoipTower?
How is VoipTower different from API-only platforms?
How does VoipTower handle CLI compliance?
What does setup cost?
How long does it take to get live?
What documents are required to start?
Does VoipTower take commissions from CRM or dialer vendors?
Which countries are covered?
For technical questions — codecs and PBX compatibility — see the full FAQ.
Talk to engineering
before signing anything.
The conversation usually answers more than a sales call can.