in Jitsi-Hammer, I had a bug where if it was creating a second fake user, the video for both fake users wouldn't be displayed correctly (by that I mean the video of the second user wasn't displayed, and the video of the first one would freeze like hell).
I've fixed the bug by not using the same code Jitsi use to generate the value of the 'label' attribute, because at first, I used the same code as the one in the method "getLabel" of the class "CallPeerMediaHandler", where it just return "mediaType.toString()", ie "audio", "video" etc... (I was told that the value of the 'label' attribute didn't really matters, but it seems like it do matter for Jitsi Meet).
Instead, like msLabel, I generate a random UUID, and it seems to fix the problem.
So I was wandering why in the first place in Jitsi, you doesn't generate an random UUID for the label : Jitsi Meet seems to do so, why not Jitsi?
In the comment of the function, you mention the RFC 5576, but this RFC doesn't mentions the label attribute (nor msid, or mslabel).
Thanks for your attention.