Use cases/Calls that must not drop
Your call, on two links at once.
A class you teach, a consultation, an interview: for one hour the line can’t hiccup. Fenris puts the call on the quickest link and sends a copy of each packet on a second one. Whichever arrives first is used, so a link that drops is not heard.
The links you probably have
- Home fibreused all the time
- A 5G boxused all the time
- Your phonea backup, used only when nothing else works
The words on the right are the roles Fenris gives a link. You choose them.
One day, as it plays out.
A tutor who teaches from home: fibre from the local operator, a 5G box by the window, a phone. Three classes today, and a call with a parent in the evening. Two things go wrong.
The first class of the day. The fibre loses a packet now and then, as every line does.
Each lost packet is a syllable gone or a frozen face, and nobody can say why.
Each packet of the class also goes out on the 5G, and whichever copy arrives first is used. A packet lost on one link has usually arrived on the other.
- Fibreused all the time
- 5Gused all the time
- Phonea backup, used only when nothing else works
The operator’s line goes down twenty minutes into the second class. It stays down for nearly three hours.
The class freezes. You turn on the hotspot, send everyone a new link, and start again ten minutes late.
The class was already on both links, so it carries on over the 5G with nothing to switch. The copies start again by themselves when the fibre returns.
- 11:20Fibre went quiet. The other links carried its traffic.
- 14:10Fibre carries traffic again.
The 5G box loses its signal for three quarters of an hour, during the call with a parent.
Nothing happens if the call was on the fibre. If it was on the 5G, it drops. You can’t know beforehand which link it will be.
The call was on both, so it carries on over the fibre. The phone stays a backup, and its data is left alone.
- 19:405G went quiet. The other links carried its traffic.
- 20:255G carries traffic again.
What Fenris does here
Each is a feature with its own page, where it says what it costs.
- Calls that keep going
- A call goes on the quickest link, with a copy of each packet on a second. Whichever arrives first is used.
- A link drops, the others carry it
- Each link is watched in both directions. When one goes quiet the call is already on the other, so there is nothing to switch.
- Every link at once
- Both links carry traffic all day, as one connection to your server.
- Link roles
- A phone or a cellular box is treated as metered: it gets copies of calls only if you allow it.
What you need
- Where you take calls
- A router running OpenWrt or Linux, with both links plugged in. Or no router: the app on the computer you call from, using Wi-Fi and a phone on a USB cable.
- A server
- A small Linux server in a region near you. Every call goes by way of it, so a near one adds the least delay.
- Data for the copies
- A copy of a call is the call’s data a second time. Leave room for it in the second link’s plan.
Where it stops
- The copies use data.A call with a copy uses its data twice. A phone or a cellular box gets copies only if you allow it, and copies have a daily allowance of their own.
- Both links fail at once.A copy on a second link covers one link failing. If every link drops together, the call drops, and Fenris reconnects as soon as one is back.
- The other side’s line is theirs.Fenris keeps your end of the call going. A student on a weak connection is still on a weak connection.
- One link is left.The call goes on it, with no copy to fall back on. One link can’t be made steadier.
Try it on your own links
Tell us which links you have, and we’ll write when a build for your links is ready. Free during early access.