feat: [VID-160] call inspector page #1644
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliverlaz
changed the title
myandrienko
force-pushed
the
inspector-page
branch
from
3791a6e to
2514eba
Compare
myandrienko
requested review from
oliverlaz and
tbarbugli
and removed request for
tbarbugli
oliverlaz
reviewed
Jan 27, 2025
oliverlaz
approved these changes
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Call inspector
This is the call inspector page (
/inspect):It shows device encoding and decoding capabilities (inspector does its best to show capabilities in human-readable format), as well as available media input devices.
When connected to a call, it shows a little bit more.
Joining a call
To join an existing call, enter call type, id, API key and user token, and press Enter.
Pronto has a Go to Inspector option in the dev menu:
Finally, you can press Join demo call, and a new test call will be created and joined on the current pronto environment. After you leave the test call, its credentials will remain entered, so you can reconnect.
In call
When in-call, a few more options become available.
Header shows call cid and current calling state. A little call connection log appears. If there were any problems while joining the call they will be displayed in the log.
Media input device dashes become interactive, allowing to select and toggle devices.
And a couple more dashes appear:
Connectivity dash shows current connection state to Coordinator and SFU. Little heartbeats show when status was last polled. There's a button to force close connection - it can be used to emulate network drop or server error.
When publishing, it also features a transport diagram that visualizes the selected candidate pair for the RTC connection. Re-ICE button forces forces renegotiation.
Codecs in use dash list codecs that are currently used in the call. That depends on other call participants, so there's a button to force subscribing to video from all call participants.
Markdown report
At any point you can press the little clipboard button in the top right to copy full report contents in Markdown format.
Client and call instance
Current client and call instances are exposed via the
_inspectorglobal variable, so you can inspect it using developer console.Device test page
The device test page (
/test) is absolutely the same as inspector, except for one thing: it doesn't allow joining an arbitrary call, and always connects to the demo call as soon as possible. Sharing a link to this page requires less explanation: the user sees immediately sees all the data, without additional steps.