This article describes how to use the debug mode to verify the P2P setup.
StriveCast offers a debug mode on deployment level. When the debug mode is enabled, every client consuming the stream gets displayed a debug window.
- How to activate debug mode for a deployment?
- The debug window
- Common problems
- Common tests
How to activate debug mode for a deployment?
Debug mode can be activated on the integration page. When debug mode is enabled, the debug window gets displayed to every user.
The debug window
The debug window indicates if Peer-2-Peer offloading is working or not. You will then see the incoming media segments and their size. Gray bars indicate a media segment downloaded directly from the source server. Blue bars indicate a media segment downloaded via peer-2-peer.
If you open the stream in two tabs or on two different devices, after 20-30 seconds, one of them will show blue bars as the segments are loaded via Peer-2-Peer, and the other one will show gray bars as the segments are loaded from the source.
Browsers need to support WebRTC to perform peer-2-peer segment sharing. To connect clients via WebRTC UDP traffic in the port range of 30.000+ cannot be blocked.
Clients need enough bandwidth capacity towards the internet. This is not related to the StriveCast backend systems as those are low-bandwidth connections, but to the video content that is being fetched from the Origins/CDN by the clients.
StriveCast does not match mobile audiences to keep their data volume as unencumbered as possible.
Multiple browser tabs
You can perform a quick functionality test by opening the page with an integrated deployment in debug mode in two browser tabs.
You can perform a quick functionality test by opening the page with an integrated deployment in debug mode on two different devices.