Hello Asbern, Chrome requires having SSL (https) connection to allow usage of the microphone and some other features (geolocation....). I think there should be a message in the Chrome console when web page tries to access microphone over an insecure connection.
Please check this page as well: https://addpipe.com/blog/microphone-camera-access-no-longer-works-insecure-origins/ Regards, Marko чет, 5. апр 2018. у 11:41 Asbern <[email protected]> је написао/ла: > Yes am aware of that, in chrome I couldn’t able to enable that permission > but in firefox I could > > > > Best Regards, > A. Asbern > > > > *From:* Nick Couchman [mailto:[email protected]] > *Sent:* Thursday, April 05, 2018 3:10 PM > > > *To:* [email protected] > *Subject:* Re: Guacamole audio redirection issue > > > > On Thu, Apr 5, 2018 at 5:25 AM, Asbern <[email protected]> wrote: > > > > > > Client OS is Windows Server 2008 R2, and I have tried in chrome, IE, > Firefox > > > > I know that, at least in Chrome, you have to grant a web page access to > the microphone before it will allow it to be used. Have you done this? > There's usually a little icon that appears in the box with the URL that > indicates something attempting to access the microphone. > > > > > > I could use the microphone via normal RDP but when I try to use via > guacamole am facing this issue even though I set *enable-audio-input* as > *true* and also my Ubuntu version is 16.04 > > > > > > So, to reiterate a previous question: Does the microphone work on other > web pages that use the microphone? You can test it out, here: > https://test.webrtc.org/ > > > > -Nick >
