Calls that keep going.
A call’s packets travel on two links at once, and the first to arrive is used. A hiccup on one link is covered by the other.
Every deviceYour serverOn by default
The fibre lost packet 4. Does the call miss it?
It doesn’t. The copy of packet 4 came over the 5G, and that one was used. Every other copy was dropped on arrival.
It doesn’t. The repair packet that followed on the 5G rebuilt packet 4, without asking for it again.
What happens
- Fenris knows a call by its own marks: RTP, STUN or a DSCP mark. It sorts on your device, never on the server.
- Each packet goes on the quickest link, and a copy goes on a second. Whichever arrives first is used, and the other is cancelled.
- A stream above 256 kbit/s, such as a video call, gets repair data instead. A few extra packets on the second link rebuild what was lost, more of them while loss comes in bursts.
- While the call is on, links busy with a download keep a shorter queue. Only where that cuts the call’s wait.
- If the link the call is on goes quiet, the call is already on the other.
What it costs
A copy is the call’s data, sent twice.
- Data
- Say an hour of voice is 50 MB. Its copy puts about another 50 MB on the second link. Repair data for video adds a fraction of the stream, not a second one.Example
- On a metered link
- Nothing, unless you allow it. Copies and repairs stay off phones and cellular modems, and where you do allow them they stop for the day at the allowance you set.
- Speed
- A call is small beside a download, so its copy takes little from one. Redundant mode, which copies everything, runs at about one link’s speed.
- Delay
- None from the copy itself: the first to arrive wins. The call still travels by way of your server.
Turn it on
It is on from the start. These change how far it goes.
| To | Command line | Router UI and app |
|---|---|---|
| Copy games and typing too | fenris settings --profile low-latency | Rules, Profile, Low latency |
| Allow copies on a metered link | fenris link usb0 --copies yes | Links, the link, Edit |
| Give copies a daily allowance | fenris link usb0 --copies-limit 200 | Links, the link, Edit, Copies a day |
| Always copy one kind of traffic | fenris rules add --ports 5060 --copies always | Rules, Add rule |
| Copy everything | fenris mode redundant | Home, Mode, Redundant |
| See what copies used | fenris usage | Usage |
Where to find it
Router UIRules. The profile, and how each kind of traffic is handled.
The appSettings, Rules.
The consoleA device’s page. Each drop the other links absorbed is counted.
The productThree of its own screens, with example data.
What it keeps
A count, and nothing about the call. The data that copies and repairs used is added to that link’s usage on the device. Your server keeps each device’s daily total for about 400 days.
Where it stops
- Both links at once
- A copy covers a loss or a stall on one link. If both fail together, the call drops like any other.
- A second link
- It needs one that is not metered, or one you have allowed. With a single link there is nowhere for a copy to go.
- A far server
- The call goes through your server. One far from you adds delay that a copy can’t take away.
- The call app
- Fenris bonds networks. It does not change your call app’s picture or sound settings.