It seems like Arch Linux has rolled out a fix for that: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/firefox&id=e1cb0bd2db9dcdd7d6517153f2020ddd0654fcdd

It's strange to me, because Arch did it for FF 76, and we are still in 75 which did not had that issue till parabola3 release, which is just a rebuild for latest icu. Maybe there's sth. related to that, who knows. But the important thing is that if that patch fixes the issue, then the cause wouldn't matter

i got iceweasel to build on beefcake by bypassing the profiling
stage - there is a new package *.parabola4 you can try to see
that made any difference - i ran the "WebRTC Troubleshooter" web
page; and it gives the same result for me, with all of the last
three releases: *.parabola2 *.parabola3 *.parabola4

bill-auger wrote:

i got iceweasel to build on beefcake by bypassing the profiling
stage - there is a new package *.parabola4 you can try to see
that made any difference - i ran the "WebRTC Troubleshooter" web
page; and it gives the same result for me, with all of the last
three releases: *.parabola2 *.parabola3 *.parabola4

What I do to test if it really works correctly, is to try Jitsi from two devices (in my case, my PC and my LOS phone with the Jitsi app)

the 1.parabola4 release hasn't solve anything

It happens to me too with iceweasel 1:75.0-1.parabola4.

iceweasel v76 is in the pipeline now - it has a fix for webrtc

https://lists.parabola.nu/pipermail/dev/2020-May/007745.html