[email protected] · 24/7 support for customers under contract

A network patch panel: dozens of blue patch leads tidied port by port in a rack.
At your premises, in the comms room

Konvoice Edge

On the day the fibre is cut, your company answers anyway.

Konvoice Edge is an appliance placed in your comms room. It holds everything your site needs to run its own telephony: the routing, the voice menu, the queues, the voicemail and your handsets’ credentials.

Konvoice Edge PWR CLOUD RTC SIP LAN WAN FXO DC
Konvoice Edge — 21 × 14 × 4 cm, fanless, 9 W. Representative image; the hardware delivered may differ.

The object

One appliance, four LEDs, no console.

It sits on a comms-room shelf. On the front: power, the state of the cloud link, the state of the backup line and the state of the handsets. On the back, two network sockets, an analogue line socket and the power inlet.

When the CLOUD LED goes out and the other three stay green, your site is still on the phone — that is the only thing this object has to say, and it says it without anybody opening a console.

Try the outage.

The diagram on the right is not an illustration: it is the real topology of a Konvoice site. Cut the link and watch what changes — and above all what does not.

  • Internal calls never cross the cloud, even when everything is working. Extension 201 calls extension 214 over the building’s network.
  • The phone system stays served locally — greetings, keypad choices, queues, opening hours, public holidays.
  • The way out fails over to the site’s backup line: a local carrier’s SIP trunk, an ISDN access or a GSM gateway.
  • Nothing is lost — call logs, recordings and messages sync up to the cloud in order as soon as the link returns.

Main site · 34 extensions

SITE LOCAL NETWORK CLOUD LINK LOCAL FALLBACK LINE SIP phones YEALINK · FANVIL App WEB · DESKTOP Mobiles IOS · ANDROID Konvoice Edge ON SITE Konvoice Cloud ADMIN · AI · CDR Carriers PSTN · SIP · GSM

Calls in progress 12 Cloud latency 18 ms Sync queue 0 For 00:00

The counters in this diagram are a simulation for demonstration purposes. The topology, the states and the behaviour described are those of the product.

What stays alive

Without the internet, here is exactly what works.

We would rather publish the list than the phrase “service continuity”. You can compare it, line by line, with what your current supplier promises.

FunctionLink upInternet cutSite power failure
Calls between handsets on the siteYesYesDepends on the UPS
Voice menu and announcementsYesYesDepends on the UPS
Queues and ring groupsYesYesDepends on the UPS
VoicemailYesYes, stored locallyDepends on the UPS
Opening hours and public holidaysYesYesDepends on the UPS
Outbound and inbound callsYesVia the local backup lineNo
Emergency callsYesVia the local backup lineNo
Mobile app in the backgroundYesNo — see the note belowNo
Cloud administration consoleYesLocal fallback administrationNo
Transcription and summariesYesDeferred, processed on reconnectionNo
The limit we do not hide A sleeping mobile app is woken by Apple’s and Google’s notification services, which need the internet. In a total outage, a locked mobile in a pocket will not ring. The guaranteed offline endpoint is the SIP phone on the desk, or the app open and connected to the site’s Wi-Fi. Any company promising you otherwise is not telling you how iOS and Android work.
An engineer in front of an open connection cabinet at the foot of a wall, the wire pairs still bare. The comms room

Where it goes

A comms room, a network socket, a power socket.

The appliance needs no rack, no air conditioning and no server next to it. It goes where your link arrives, between the router and the handsets’ network — and if your installation has an analogue backup line, it takes that too.

  • No rule to open on your firewall — the appliance calls the cloud, never the other way round.
  • No public address — nothing it exposes is reachable from the internet.
  • Two screws and a DIN rail — or simply placed on a shelf, if there is no rack.
  • Replaceable by a neighbour — the configuration is in the cloud, so a swapped appliance reconfigures itself.

Three sizes

The appliance that matches the size of the site.

A six-person practice and a three-hundred-extension factory do not have the same needs. The software is the same; what changes is the machine and the redundancy.

Edge Mini

A fanless appliance the size of a book, in the network cabinet. Up to 50 extensions and 15 simultaneous calls. Under 15 W. The format for branches, practices and shops.

Edge Redundant

Two appliances in active/standby, a shared virtual address, automatic failover in under three seconds. Up to 300 extensions. The format for head offices, clinics and contact centres.

Edge Cluster

Three machines or more in your server room or your hypervisor, distributed media and replicated databases. Beyond 300 extensions, and for sites that tolerate no interruption at all.

An open patching rack: stacked switches, tidy network cabling, lit LEDs.

Installation

Plugged in, it announces itself.

No serial console, no engineer to send out, no address to type on a telephone keypad.

  • The appliance arrives prepared for your company and sealed.
  • You plug it into power and the network; it establishes a certificate-authenticated tunnel to the cloud.
  • It downloads its site’s configuration, provisions the handsets present on the network and reports ready in your console.
  • You approve its fingerprint from the console before it takes any traffic.

See how a site is brought online

  1. Network discovery

    The Edge finds the site’s SIP phones and offers to adopt them. Nothing is adopted without your approval.

  2. Cryptographic seal

    Every Edge has a unique hardware identity. A stolen appliance does not join your company.

  3. Signed updates

    They arrive through the tunnel, are verified and then applied outside business hours, with automatic rollback if the site loses voice.

  4. Backup

    Configuration and messages exported encrypted, locally and to the cloud, at a rhythm you choose.

After the outage

Resynchronisation loses nothing and overwrites nothing.

The hard part is not surviving the outage: it is reconciling the two versions of reality cleanly when the link comes back.

Order preserved

Events produced offline go up time-stamped and in sequence, never as an unordered block.

Resume without duplicates

Every event carries an idempotency key: an upload interrupted and then resumed does not create the same call twice.

Conflicts arbitrated

If a rule was changed on both sides, the cloud version prevails for configuration and the Edge prevails for call events. The conflict is displayed, never resolved silently.

Visible in the console

You see what is still queued, for how long, and for which site. A queue that does not drain raises an alert.

< 3 sFailover to the second appliance in a redundant configuration
0Calls in progress interrupted by a cloud link outage
< 15 WPower draw of an Edge Mini in operation
30 dOffline operating time with no licence validation
Night roadworks under floodlights: several people in high-visibility gear around a machine, the carriageway open.

At two in the morning, somebody opens the road to lay a joint. Your handsets will know nothing about it.

It is the only promise on this page, and the only one that matters

Questions about the Edge

Is the appliance compulsory?
No. Konvoice works perfectly well in pure cloud mode, and that is the choice of many sales teams and well-connected head offices. The Edge becomes interesting as soon as a site has a reception desk, an on-call rota, a regulatory obligation to be reachable, or an internet connection you know goes down.
What happens if the appliance fails?
In a simple configuration, the site fails over automatically to the Konvoice cloud: you lose the offline resilience, not the telephony. In a redundant configuration, the second appliance takes over in under three seconds without dropping calls in progress. A replacement appliance ships within 24 working hours and reconfigures itself.
Do we have to open ports on our firewall?
No inbound ports. The Edge itself initiates an outbound mutual-TLS connection to the cloud. That is deliberate: an appliance reachable from the internet is an appliance that will be scanned.
Can we host it on our own hardware?
Yes. The Edge ships as a virtual machine image for the common hypervisors, as well as the physical appliance. Some organisations prefer to run it on their own infrastructure; the service commitments are then adjusted accordingly.
What if we have no backup line at all?
Internal calls, the phone system and voicemail carry on regardless. Only the way out is lost, exactly as it is today. In that case we recommend a GSM gateway costing a few hundred euros, which is enough to retain emergency calling.

Cut the link during the demo.

We are not asking you to take our word for it. During the demo we unplug the link live and you call an extension.

No commitment. No card number asked for.