Kahevo measures loss, jitter and delay on every call and flags the bad ones.
"The call was choppy" is hard to act on a day later.
Measured from both ends
Kahevo now measures every call it joins. For each person on the call it keeps two views:
- what Kahevo received from them,
- and what their own phone reports about what it received.
The two people on a call are measured separately, because their connections are separate journeys. A call can be perfect on one side and dreadful on the other.
Three numbers
| Measure | What it means | Flagged as poor at |
|---|---|---|
| Loss | Packets that never arrived | 3% |
| Jitter | How unevenly packets arrive | 40 milliseconds |
| Round trip | Delay there and back | 400 milliseconds |
Loss makes voices drop out. Jitter makes them warble. Delay makes two people talk over each other and apologize.
Kept with the call
The figures are stored with the call and shown under it in the call log. A call that crosses any of the lines is written to the system log by itself, naming which side had the trouble.
So the answer to "the calls have been bad this week" is a list: which calls, which person, which measure.
What it tells you
- Bad on one extension every time: that desk's cable or switch port.
- Bad for everyone at once: the internet connection.
- Bad only on outside calls: the path to the provider.
- Fine on every measure: the trouble is beyond what Kahevo can see, often the far end's mobile signal.
Phones that vanish
A phone that loses power in the middle of a call never hangs up. Kahevo now notices when nothing at all has arrived from one side for a minute and ends the call, instead of leaving it open all night. Time on hold does not count.
Off if you prefer
Measuring is on by default and costs very little. One switch turns it off.