Edited: based on Jonathan's answer (Thanks!).
It seems that the problem comes indeed, in part, from Teams.
What I observed that cause the problem for me:
From pavucontrol, it looks like Teams does not "release" it's connection to the microphone after a call.
(seen in the "Recording" tab in pavucontrol).
Slack and Chrome (tested with Meeting) do close their connnection to the microphone when you terminate your call.
And so, once the mic is used by Teams, I found out is that it cannot be used correctly by any others.
Moreover, it also comes to a point where pulseaudio seems to completely "fail" to serve the mic correctly to Teams too and to any other program or control panels.
So, by completely quitting and reloading Teams after each call I can "release" the mic and do another call (on Teams or on any other app).
Edit: Or, much simpler from Jonathan's answer: in pavucontrol's "Recording" tab, right-click on the "Skype" entry that is still recording and terminate the connection
So basically: When the mic stops working: find a way to terminate the connections between applications and the microphone
- Make sure Teams (and others like slack...) completely "quits" when you quit the application: Settings -> General -> uncheck the second option in the Application section
- Check that a program is still running with a "ps" call
- Killing and restarting pulseaudio also works but it seems you still need to "fully" quit and restart all other programs that could have had a connection to an audio device.
- Using sudo or messing with the groups probably won't really fix anything
Anyone observing the same thing from pavucontrol ?
BR!
- Teams 1.3.00.30857
- CentOS 8 (k 4.18.0-240.15.1.el8_3.x86_64)