P2P TC02 - Device (browser simulator)

Stands in for test_p2p_tc02_device.c: registers as a device, reads the video config (resolution / fps / bitrate) from the client's INVITE, streams a generated canvas video with that config, and reports DEVICE_STATS over the client's data channel every second. Supports parallel calls. Keep this tab visible (background tabs throttle the video source) and run it in a different tab/browser from the client.
Note: a browser cannot read process CPU/RAM, so cpuPct is the main-thread busy time spent generating frames and rssMB is the JS heap (Chrome only). Encoding cost is not included. The data-flow metrics (bitrate, fps, loss, drops, freezes) are the meaningful ones here.

Signaling / ICE






more INVITEs get 486 BUSY_HERE
force-close a call with no HANGUP (0 = off, as in the current C file)
disconnected
Video source used when the INVITE has no video config





encodes and decodes the source inside this page: tells you whether this browser can produce the video at all

Fault injection (applies to new messages / frames immediately)

client: INVITE_500_...
client: ANSWER_TIMEOUT
lowers receiver fps; counted in framesDropped
Status
-
#Call IDUserProfilePeer connectionSent kbpsSent fpsSrc fpsLimitSource framesNoiseAge (s)
Log