I took a look at the site you mentioned, and they are using a stock standard webRTC client.
Thus the code I was talking about will make no difference. That code is a catch you can use when programming your own website to handle streaming data. We've already established you are not doing that.
So now we need to look at your end.
- You mentioned a mic but not much else about it. Is this a headset with mic, you are referring to, or something else?
- In addition to the mic, are you using anything else, like a webcam?
- What browser are you using to connect to the boldago site, and what build is that browser?
- When you are connecting to website, do you have more than one tab open?
I'm asking these questions because its more than likely the issue here is your mic is in use ( albeit you not realizing that ). Chrome browsers for example, can call on your mic in multiple tabs, so if an additional tab is open when you attempt to connect using Bodalgo's website, the exeption error you are receiving can be triggered.
Likewise, you may have another application making use of your mic. For example, if you were attempting to record the stream, then the recording software may not release your mic in time for you to connect to the User you wish on the Boldago site, and that would also trigger the exception you mentioned.
Granting permission for mic to access the client via Bodalgo's site is fine, but the mic must not be in use by any other Browser, or browser tab, or other application, be that a built in Windows OS app like Skype, or any non-native apps that make use of the mic, while you are using a webRTC connection, otherwise, you will get the exception error.
In terms of browsers. Chrome browsers are not always so good at handling hardware [ in this case your mic ], and you might find that if you instead connected via FireFox, or Internet Explorer, or Edge, you would have a different experience.
Note though, that each browser may handle the same exception differently, and provide a different error message, even though the same issue is in play ( that being when the mic is being used by another application, or browser, or web base layer. )