The part of Kahevo that faces the internet for you, without a separate box to buy.
Kahevo has a session border controller built in, and it is in production.
What that is
A session border controller sits at the edge of a phone system, between the inside and the internet. It is usually a separate product, with its own box and its own license, and for a small office it can cost more than the phone system.
Kahevo already stands in the middle of every call, joining two separate legs. That turns out to be exactly where this work belongs.
What it does
| Job | How Kahevo does it |
|---|---|
| Hide the inside | Phones and providers each talk only to Kahevo, never to each other |
| Get through routers | Learns its public address and keeps paths open to every provider server |
| Reach phones behind routers | Sends to where a phone was really heard from, not where it claims to be |
| Keep strangers out | Challenges every sign-in and call, blocks repeat offenders, stays silent to them |
| Limit the damage | Caps on calls at once and outside calls per hour |
| Translate | Converts between codecs, and between encrypted and plain, per side |
Each side on its own terms
Because the two sides of a call are settled separately, a browser on a modern codec with encryption can talk to a provider that offers neither. Kahevo speaks each one's language.
For branch offices
Kahevo Hākuʻi extends the same idea to a branch: one encrypted link out, nothing opened on the branch's router, and the main system never exposed to the branch's network.
What you do not need
A separate appliance. A separate license. A second thing to update, monitor and explain.
What you still need
A firewall, sensibly configured, with only the ports Kahevo uses opened to it. A border controller is not a replacement for one.