There are too many logs on about:webrtc page during a videocall on Cisco webex app
Categories
(Core :: WebRTC, enhancement, P3)
Tracking
()
People
(Reporter: rpopovici, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
Note:
During a call with Cisco Webex Meetings, too many logs will appear on Session Statistics(12 logs).
Affected versions:
Nightly v81.0a1
Firefox 79.0
Firefox 80.0b1
Affected platforms:
all
Steps to reproduce:
- Load www.webex.com
- Click on "Sign Up now, it's free".
- Input an email address, input name, activate the account by the emailed link and set/create password.
- Go to meetingsemea25.webex.com, host a meeting and allow the microphone and camera permissions.
- Copy the meeting link (from the address bar) and load it on another system.
Input a random name and email address and allow the microphone and camera permissions. - Join the meeting.
- Admit the join request from the host system.
Expected result
There should be displayed a single log for that call on Session Statistics(about:webrtc)
Actual result
12 logs appear on about:webrtc page
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
We end up with one log entry per PeerConnection, not per call. So if you use a site like https://whereby.com where the connections are peer-to-peer and connection to two separate computers, you'll end up with two separate entries in the log, one for each PeerConnection. Ending up with all those logs on a webex call is because the site keeps creating new PeerConnections.
I agree this is pretty bad from a usability point of view, I've had difficulties figuring out what is going on with webex because of this. We probably want some way of grouping PeerConnections that are associated with a single call or a single tab together.
Comment 2•4 years ago
|
||
We can also group PeerConnections that are never used to carry traffic, or have a checkbox to hide them, etc. IIRC most of these connections that Webex creates are never used. Grouping by "call" or tab won't really help for this case, though I think it is something we should do.
Comment 3•4 years ago
|
||
Just to be clear: the reason there are so many PeerConnections showing up on WebEx has been raised with Cisco a couple of times. WebEx appears to think that this results in better end user experience using these many, partially unused, PeerConnections.
Description
•