WebRTC testing
on real machines and networks.
A lab demo won’t catch what breaks on the agent’s laptop, behind the corporate firewall, the VPN or the home network. Lens tests WebRTC in real browsers, on the machines and networks your users actually have. Powered by Lens.
Validate the whole path, not just the browser.
A WebRTC call breaks in places a SIP trace never sees and a lab demo never hits: the agent’s locked-down laptop, the corporate firewall, the VPN, the TURN relay, the JavaScript that wires media to the page. Lens drives a real browser through all of it, on the network you actually need to prove.
Real browser sessions
Actual Chrome, Firefox and Edge instances. Click-to-call, embedded video and agent consoles tested the way a user would use them.
Corporate networks & security
Run from a desktop agent behind the corporate firewall, VPN and endpoint security software, the SSL inspection, proxies and policies that block TURN and break media in production but never show up in a vendor lab.
VPN & home-office reality
Reproduce remote-agent conditions: split-tunnel VPNs, VPN hairpinning, residential NAT and Wi-Fi, the setups where the call is fine at the office and fails from home.
Full WebRTC validation
SDP offer/answer, ICE candidate gathering, STUN/TURN reachability, codec exchange, DTLS-SRTP. The whole negotiation, captured.
Audio measurement
Measure real audio inside the session: MOS, jitter and loss on the media that actually reached the browser, plus content validation.
Codec
When media fails to flow, the capture shows whether it was a codec mismatch, a blocked TURN relay, a firewall or an ICE timeout.
From web app to validated session.
Teams shipping a browser-based voice client.
If your users talk through a browser, a healthy SIP trunk and a passing lab demo are not enough. The call still has to survive their machine, their network and their VPN. Lens validates the part of the stack your users actually run.
CCaaS and UCaaS
Agent consoles, click-to-call widgets and embedded video. Validate the web client on every release, across all three browsers.
Web softphone vendors
Reference flows for the major web-softphone products. Prove the call connects and the audio is clean before customers report it does not.
Teams crossing SIP and WebRTC
When a call traverses both SIP and WebRTC, Lens pairs with Probe to validate the full path end to end.
Support and QA
Reproduce a customer’s browser conditions from a desktop agent to confirm whether the problem is the app or the network.
WebRTC Browser Testing is included from Carrier up.
Lens unlocks on the Carrier tier and above. Same engine, same dashboard, same evidence format as the rest of the platform.
Where WebRTC testing sits.
Validate the browser. 14 days, no credit card.
All four products unlocked. The AI Assistant records your first Lens flow for you. If you don’t convert, your work pauses for 6 months, resume any time.