I'm pretty sure it can't in general.
If there is a large conference, and some people are on the same Wifi
segment, some are on the same internal network, and some are external, then
it might be possible to do some cross correlation and work out which is
likely to be the bottle-neck. However it would be a really bad idea to try
and build a "network diagnostics" module onto the side of an already large
and complex piece of software.
On 29 January 2018 at 18:11, Antony Stone <Antony.Stone@jitsi.open.source.it > wrote:
On Monday 29 January 2018 at 17:02:38, Guus der Kinderen wrote:
> Would it be possible to extend the "call quality" indicators in Meet to
> include references to those parts of the network that are most likely to
> negatively affect quality of the call? I would, for instance, be very
> interested in being told whether its my LAN (or Wifi), or my ISP uplink
> that's causing trouble.
I'm intrigued as to how Jitsi could determine this?