Next
Voice, Numbers & DialerThe lines and numbers that ride this edge, and how local presence is actually obtained.
The operator
You are dealing with the operator of the platform. Not a brand in front of one. Not a partner programme. Not a portal skin over somebody else's switch. The edge those phones register against and the software the floor runs on are built and run by the same people. When an upstream starts returning garbage mid-shift, I move the damn traffic.
- Named hostnames you can resolve. Register the phone against them.
- When the first hop lies, I change the policy. I do not wait on their ticket.
- Your neighbour's bad week stays on their credentials, their numbers, their tape.
- Escalation ends with someone who can change the config, at 02:00 if that is when it breaks.
Footprint
Every count and every location below is generated from the edge inventory. When we bring an edge up or take one down, this page moves. There is no number sitting in this sentence waiting to go stale.
- 23 SIP edge nodes
- 19 cities
- 16 countries
Architecture
'We run our own network' is the sentence every reseller uses. Here is what I mean by it, including the layer I do not own.
Operators
The interesting question about a voice network is not what it does on a good Tuesday. It is the ninety seconds after an upstream starts returning nonsense in the middle of a shift.
- More than one edge where the inventory allows
- Where we have two edges in a region, losing one is a reroute. It is not an outage for everyone who registered to the dead one.
- Routing policy
- I can change policy for a destination, a carrier or an account without asking a partner's permission. That is the difference between an operator and a skin.
- Account isolation
- Your neighbour burns a range, that is their credentials, their numbers, their tape. It does not land on your floor.
- Monitoring and escalation
- We watch the register, the hop and the audio ourselves. When you escalate at 02:00 you are talking to someone who can change the config, not a queue.
City reach
Pick the endpoint nearest the agents instead of dragging every packet across an ocean and then blaming the internet. The full endpoint directory, including which edge your account is provisioned against, lives in the portal.
Edge location and local-number availability are separate questions. An edge in a country does not mean we can issue you a local number there. A local number in a market does not require an edge in that market. When you tell us the markets you are calling, we answer both questions separately.
Questions
- Do you own the data centres?
- No, and neither does almost anyone making that claim. We operate our SIP edge and our entire product and control stack. We do not own buildings, fibre or every upstream route, and I am not going to lie about that to win a comparison table.
- Which edge will my account use?
- Whichever is right for where your agents sit and where you are calling. Your provisioned endpoints show in the portal with your device credentials. We will move you if the floor moves.
- Is an edge in my country the same as a local number in my country?
- No. Edge location is about where the phones register and where media is handled. Local-number availability is about that country's numbering rules and what documents it wants. Ask both questions. You will get two different answers.
- What happens if an upstream carrier degrades?
- We move traffic. Carrier selection and routing policy are ours to change. That is the practical difference between an operator and a reseller. A reseller waits for the same thing you are waiting for.
Your routes
Next
Portal & APIWhere your provisioned endpoints, credentials and call records live.
Next
Get inTell us the markets. We will tell you the edge, the numbers and the documents.
Next
TerritorySame footprint. Different heat in each block of the city.