Skip to main content
Tsahi Levent-Levi on Muck Rack

Tsahi Levent-Levi

Israel
As seen in: BlogGeek.me, Substack, Search Unified Communications, TechTarget, VentureBeat, Product Hunt, GigaOM, HackerNoon, ComputerWeekly.de, InfoQ, DEV Community and
Consulting ⭐ Training ⭐ Marketing outreach ⭐ Expert in WebRTC and Programmable Communications
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Tsahi

Contact Tsahi, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

Call quality is invisible until a customer leaves

|
By Tsahi Levent-Levi
| No Jitter Verified
on the other side of the line sit in front of a laptop or a desktop PC and answer the call inside their web browser. That second leg of the call to the agent was done over WebRTC. Say a customer had a bad call experience. He wasn't heard or the call was choppy. Would he stick around? If an agent has a bad experience - either in a specific call, a full day or as an ongoing issue - would he report it? There is no error for these types of things. No log line anywhere.
Open in Who Shared Issue with article?

What getting rtcStats seen taught me about the whole WebRTC ecosystem

|
By Tsahi Levent-Levi
| BlogGeek.me
rtcstats.com is a new initiative I started recently with Olivier and Philipp. It is genuinely useful and powerful as hell. Here’s the thing though… it sits in a tiny little niche of a niche: observability inside WebRTC inside VoIP inside communications. And in there, how do you even know it exists, besides maybe reading the stuff I write here on my blog?
Open in Who Shared Issue with article?

How to Read a webrtc-internals Dump, Section by Section

|
By Tsahi Levent-Levi
| DEV Community
When a WebRTC call goes bad, the browser already recorded what happened. Chrome keeps a live record of every peer connection at chrome://webrtc-internals, and you can export it to a JSON dump. The problem is that the dump is dense, undocumented, and easy to misread. This is a field guide to reading one by hand: what each section is, what to look at first, and the failure signatures that tell you where the call broke. It assumes you have a dump already.
Open in Who Shared Issue with article?
See all 303 licensed articles (304 Total)