You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Alexandre Cariage <al...@sight-sound.ch> on 2022/11/01 14:32:50 UTC
State of Audio Input ?
Greetings,
I'm unable to use Audio Input with Guacamole 1.4.0.
* Guacd/tomcat server is Debian 11, only RDP built-in, as protocol.
* Host is Windows 10 Pro (N version, now that I think of it, but audio
& video playback works).
* Client is either Firefox 106.x or Edge, on top of W10-22H2. Mic
works on the client.
Note also that Host uses the RDPWrap library.
The "Audio Input" option is activated and will show up in the device
list ("Sound" panel in W10) in the Host, but nothing lights green (even
though the Client does react to audio input in that same panel).
Just checking for the generally accepted state of the feature, so that I
can define if further troubleshooting is worth it for us.
Thanks
Re: State of Audio Input ?
Posted by Alexandre Cariage <al...@sight-sound.ch>.
FYI,
I've finally setup HTTPS and indeed, both Firefox and Edge now ask for
permission to use the microphone when it is used on the remote computer.
Plus, it actually records, with pretty good quality.
Thanks all,
Alexandre Cariage
CH
Le 15/11/2022 05:53, Leslie Mann a écrit :
> Yes, there is a reverse proxy (Apache) setting a number of headers
> including a "microphone 'none'"...
>
> Guacamole is piggybacking on a primarily Nextcloud server for which the
> headers were configured. Removing the header enables the microphone so
> my problem is now solved as a web server configuration problem, not a
> Guacamole issue.
>
> Thanks for the questions leading to uncovering the configuration
> settings!!
>
> On Mon, 2022-11-14 at 20:03 -0800, Michael Jumper wrote:
>
> On Mon, Nov 14, 2022, 7:09 PM Leslie Mann <lm...@linuxolutions.com>
> wrote:
>
> I see a number of 'Feature-Policy' unrecognized feature errors and a
> 'AudioContext was not allowed to start' error.
>
> Here is the console log:
>
> Error with Feature-Policy header: Unrecognized feature:
> 'ambient-light-sensor'.
>
> This is interesting and not a header that Guacamole sets...
>
> Do you have a reverse proxy in place adding this header? What value is
> it setting? Any other headers added by that proxy?
>
> all.min.js:3 The AudioContext was not allowed to start. It must be
> resumed (or created) after a user gesture on the page.
> https://goo.gl/7K7WLu
>
> getAudioContext @ all.min.js:3
>
> Guacamole.RawAudioPlayer.getSupportedTypes @ all.min.js:8
>
> You can ignore this. This is Guacamole trying to get access to audio
> output. The browser will block some of these attempts, particularly
> Chrome. It'll keep trying and eventually succeed. In Chrome, that'll
> typically happen after some user interaction with the page.
>
> This probably has no bearing on audio input.
>
> - Mike
Re: Re: State of Audio Input ?
Posted by Leslie Mann <lm...@linuxolutions.com>.
Yes, there is a reverse proxy (Apache) setting a number of headers
including a "microphone 'none'"...
Guacamole is piggybacking on a primarily Nextcloud server for which the
headers were configured. Removing the header enables the microphone so
my problem is now solved as a web server configuration problem, not a
Guacamole issue.
Thanks for the questions leading to uncovering the configuration
settings!!
On Mon, 2022-11-14 at 20:03 -0800, Michael Jumper wrote:
> On Mon, Nov 14, 2022, 7:09 PM Leslie Mann <lm...@linuxolutions.com>
> wrote:
> > I see a number of 'Feature-Policy' unrecognized feature errors and
> > a 'AudioContext was not allowed to start' error.
> >
> > Here is the console log:
> >
> > Error with Feature-Policy header: Unrecognized feature: 'ambient-light-sensor'.
>
> This is interesting and not a header that Guacamole sets...
>
> Do you have a reverse proxy in place adding this header? What value
> is it setting? Any other headers added by that proxy?
>
> >
> > all.min.js:3 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
> > getAudioContext @ all.min.js:3
> > Guacamole.RawAudioPlayer.getSupportedTypes @ all.min.js:8
>
> You can ignore this. This is Guacamole trying to get access to audio
> output. The browser will block some of these attempts, particularly
> Chrome. It'll keep trying and eventually succeed. In Chrome, that'll
> typically happen after some user interaction with the page.
>
> This probably has no bearing on audio input.
>
> - Mike
>
>
Re: Re: State of Audio Input ?
Posted by Michael Jumper <mj...@apache.org>.
On Mon, Nov 14, 2022, 7:09 PM Leslie Mann <lm...@linuxolutions.com> wrote:
> I see a number of 'Feature-Policy' unrecognized feature errors and a
> 'AudioContext was not allowed to start' error.
>
> Here is the console log:
>
> Error with Feature-Policy header: Unrecognized feature: 'ambient-light-sensor'.
>
>
This is interesting and not a header that Guacamole sets...
Do you have a reverse proxy in place adding this header? What value is it
setting? Any other headers added by that proxy?
> all.min.js:3 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
>
> getAudioContext @ all.min.js:3
>
> Guacamole.RawAudioPlayer.getSupportedTypes @ all.min.js:8
>
>
You can ignore this. This is Guacamole trying to get access to audio
output. The browser will block some of these attempts, particularly Chrome.
It'll keep trying and eventually succeed. In Chrome, that'll typically
happen after some user interaction with the page.
This probably has no bearing on audio input.
- Mike
Re: Re: State of Audio Input ?
Posted by Leslie Mann <lm...@linuxolutions.com>.
I see a number of 'Feature-Policy' unrecognized feature errors and a
'AudioContext was not allowed to start' error.
Here is the console log:
Error with Feature-Policy header: Unrecognized feature: 'ambient-light-sensor'.
Error with Feature-Policy header: Unrecognized feature: 'animations'.
Error with Feature-Policy header: Unrecognized feature: 'image-compression'.
Error with Feature-Policy header: Unrecognized feature: 'legacy-image-formats'.
Error with Feature-Policy header: Unrecognized feature: 'max-downscaling-image'.
Error with Feature-Policy header: Unrecognized feature: 'speaker'.
Error with Feature-Policy header: Unrecognized feature: 'unsized-media'.
Error with Feature-Policy header: Unrecognized feature: 'vertical-scroll'.
Error with Feature-Policy header: Unrecognized feature: 'vr'.
/guacamole/#/:1 The key "target-densitydpi" is not supported.
DevTools failed to load source map: Could not load content for https://sidus.linuxolutions.com/guacamole/angular.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
all.min.js:3 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
getAudioContext @ all.min.js:3
Guacamole.RawAudioPlayer.getSupportedTypes @ all.min.js:8
Guacamole.AudioPlayer.getSupportedTypes @ all.min.js:4
(anonymous) @ guacamole.4a88cb501be0f26307d3.js:15730
(anonymous) @ guacamole.4a88cb501be0f26307d3.js:15723
invoke @ angular.min.js:45
(anonymous) @ angular.min.js:42
invoke @ angular.min.js:45
(anonymous) @ angular.min.js:47
d @ angular.min.js:44
(anonymous) @ guacamole.4a88cb501be0f26307d3.js:16671
invoke @ angular.min.js:45
(anonymous) @ angular.min.js:42
invoke @ angular.min.js:45
(anonymous) @ angular.min.js:47
d @ angular.min.js:44
(anonymous) @ guacamole.4a88cb501be0f26307d3.js:15767
invoke @ angular.min.js:45
(anonymous) @ angular.min.js:42
invoke @ angular.min.js:45
(anonymous) @ angular.min.js:47
d @ angular.min.js:44
(anonymous) @ guacamole.4a88cb501be0f26307d3.js:27184
invoke @ angular.min.js:45
S.instance @ angular.min.js:99
p @ angular.min.js:73
g @ angular.min.js:66
(anonymous) @ angular.min.js:65
(anonymous) @ angular.min.js:22
$eval @ angular.min.js:156
$apply @ angular.min.js:156
(anonymous) @ angular.min.js:22
invoke @ angular.min.js:45
c @ angular.min.js:22
Wc @ angular.min.js:22
Ee @ angular.min.js:21
(anonymous) @ angular.min.js:351
e @ jquery.min.js:2
t @ jquery.min.js:2
setTimeout (async)
(anonymous) @ jquery.min.js:2
c @ jquery.min.js:2
fireWith @ jquery.min.js:2
fire @ jquery.min.js:2
c @ jquery.min.js:2
fireWith @ jquery.min.js:2
ready @ jquery.min.js:2
B @ jquery.min.js:2
Les
On Mon, 2022-11-14 at 18:00 -0800, Michael Jumper wrote:
> On Sun, Nov 13, 2022, 2:46 PM Leslie Mann <lm...@linuxolutions.com>
> wrote:
> > Hi Nick:
> >
> > I've done a bit more testing with browsers and it turns out that
> > audio
> > with Firefox is working as expected! I thought I had tried Firefox
> > previously but I've been mostly 100% using Chrome due to the
> > clipboard
> > integration. I'm seeing the same behaviour on Windows, Firefox
> > audio
> > works but Chrome (and Edge) does not. No prompt to use the
> > microphone
> > and no audio in being seen.
> >
> > Any thoughts on what might be causing this?
>
> Do you see any errors/warnings in the JavaScript console when you try
> to use the connection?
>
> - Mike
>
>
Re: Re: State of Audio Input ?
Posted by Michael Jumper <mj...@apache.org>.
On Sun, Nov 13, 2022, 2:46 PM Leslie Mann <lm...@linuxolutions.com> wrote:
> Hi Nick:
>
> I've done a bit more testing with browsers and it turns out that audio
> with Firefox is working as expected! I thought I had tried Firefox
> previously but I've been mostly 100% using Chrome due to the clipboard
> integration. I'm seeing the same behaviour on Windows, Firefox audio
> works but Chrome (and Edge) does not. No prompt to use the microphone
> and no audio in being seen.
>
> Any thoughts on what might be causing this?
>
Do you see any errors/warnings in the JavaScript console when you try to
use the connection?
- Mike
Re: Re: State of Audio Input ?
Posted by Leslie Mann <lm...@linuxolutions.com>.
Hi Nick:
I've done a bit more testing with browsers and it turns out that audio
with Firefox is working as expected! I thought I had tried Firefox
previously but I've been mostly 100% using Chrome due to the clipboard
integration. I'm seeing the same behaviour on Windows, Firefox audio
works but Chrome (and Edge) does not. No prompt to use the microphone
and no audio in being seen.
Any thoughts on what might be causing this?
Les
On Sat, 2022-11-12 at 13:37 -0500, Leslie Mann wrote:
> Afternoon Nick:
>
> I'm accessing Guacamole thru a HTTPS connection proxied through
> Apache.
>
> I'm using Chrome browser on a Fedora 36 system and don't get any
> microphone access prompts. Site security is set to 'allow' so I've
> assumed that this was preventing the prompt. I've just tried setting
> the site setting to 'ask' and now I see that I still don't get the
> prompt...
>
> FYI audio in using XfreeRDP from Fedora and mstsc from WIn 11 both
> work.
>
> Thanks
> Les
>
> On Sat, 2022-11-12 at 13:24 -0500, Nick Couchman wrote:
> > On Sat, Nov 12, 2022 at 1:20 PM Leslie Mann
> > <lm...@linuxolutions.com>
> > wrote:
> > >
> > > Hi Alexandre:
> > >
> > > I'm having the same isseue as you (have a remote audio input
> > > device
> > > but
> > > no audio) so was wondering if you have been able to get audio
> > > input
> > > working?
> > >
> > > In my case I have guacamole and freeRdp installed on a Centos 8
> > > stream
> > > server connecting to a pair of Win 10 Pro clients (All QEMU
> > > VM's).
> > > Guacamole is 1.4.0-5, freerdp is 2.2.0-8. No issues with
> > > anything
> > > else, including sound, just can't get the microphone working.
> >
> > Curious if you're connecting to Guacamole via HTTP or HTTPS? Also,
> > have you received the prompt from the browser to allow Guacamole to
> > access the microphone?
> >
> > -Nick
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> > For additional commands, e-mail: user-help@guacamole.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Re: State of Audio Input ?
Posted by Leslie Mann <lm...@linuxolutions.com>.
Afternoon Nick:
I'm accessing Guacamole thru a HTTPS connection proxied through Apache.
I'm using Chrome browser on a Fedora 36 system and don't get any
microphone access prompts. Site security is set to 'allow' so I've
assumed that this was preventing the prompt. I've just tried setting
the site setting to 'ask' and now I see that I still don't get the
prompt...
FYI audio in using XfreeRDP from Fedora and mstsc from WIn 11 both
work.
Thanks
Les
On Sat, 2022-11-12 at 13:24 -0500, Nick Couchman wrote:
> On Sat, Nov 12, 2022 at 1:20 PM Leslie Mann <lm...@linuxolutions.com>
> wrote:
> >
> > Hi Alexandre:
> >
> > I'm having the same isseue as you (have a remote audio input device
> > but
> > no audio) so was wondering if you have been able to get audio input
> > working?
> >
> > In my case I have guacamole and freeRdp installed on a Centos 8
> > stream
> > server connecting to a pair of Win 10 Pro clients (All QEMU VM's).
> > Guacamole is 1.4.0-5, freerdp is 2.2.0-8. No issues with anything
> > else, including sound, just can't get the microphone working.
>
> Curious if you're connecting to Guacamole via HTTP or HTTPS? Also,
> have you received the prompt from the browser to allow Guacamole to
> access the microphone?
>
> -Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Re: State of Audio Input ?
Posted by Nick Couchman <vn...@apache.org>.
On Sat, Nov 12, 2022 at 1:20 PM Leslie Mann <lm...@linuxolutions.com> wrote:
>
> Hi Alexandre:
>
> I'm having the same isseue as you (have a remote audio input device but
> no audio) so was wondering if you have been able to get audio input
> working?
>
> In my case I have guacamole and freeRdp installed on a Centos 8 stream
> server connecting to a pair of Win 10 Pro clients (All QEMU VM's).
> Guacamole is 1.4.0-5, freerdp is 2.2.0-8. No issues with anything
> else, including sound, just can't get the microphone working.
Curious if you're connecting to Guacamole via HTTP or HTTPS? Also,
have you received the prompt from the browser to allow Guacamole to
access the microphone?
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
RE: Re: State of Audio Input ?
Posted by Leslie Mann <lm...@linuxolutions.com>.
Hi Alexandre:
I'm having the same isseue as you (have a remote audio input device but
no audio) so was wondering if you have been able to get audio input
working?
In my case I have guacamole and freeRdp installed on a Centos 8 stream
server connecting to a pair of Win 10 Pro clients (All QEMU VM's).
Guacamole is 1.4.0-5, freerdp is 2.2.0-8. No issues with anything
else, including sound, just can't get the microphone working.
Thanks
Les
On 2022/11/02 15:03:29 Alexandre Cariage wrote:
> Hi Nick, thanks again.
>
> About RDPWrap, we're definitely not worried about the legal aspect of
it
> being an issue :
> We're not selling the service, per se (although it _might_ be
considered
> we sell it as part of another service package), but, most
importantly,
> I'm planning on a single Windows 10 Host being enough for our use,
and
> for years to come, even _given the 10 maximum concurrent connections
on
> non-Server editions of Windows._ Also the link to Guacamole will not
be
> public. So, as you can see, the scale of the project is the same as
the
> scale of our business, and probably doesn't call for any action on
> Microsoft's part.
>
> About Audio Input, yes, Audio Input does NOT work on Guacamole with
and
> without RDPWrap.
>
> Finally, thanks for the insight on SSL.
>
> I'm indeed testing internally only and didn't bother setting up HTTPS
> for now.
> I don't think my browsers particularily block inputs more than the
> default settings would, but again, the prompt may not even pop-up
> because of that SSL thing.
>
> I'll keep that in mind and keep you updated.
>
> Cheers,
>
> Alexandre Cariage
> CH
>
> Le 02/11/2022 15:29, Nick Couchman a écrit :
>
> > On Wed, Nov 2, 2022 at 8:38 AM Alexandre Cariage
<al...@sight-sound.ch>
> > wrote:
> >
> >> Hi all, thanks for the guidance and test ideas.
> >>
> >> @Nick: we are a very small firm trying to offer interresting
services
> >> with what's available... and almost no budget ;-)
> >> Right now RDPWrap seems to work very well, as far as I can tell.
> >
> > I'm no legal expert, but you'll want to be careful with this one.
> > There's a discussion on the RDPWrap Github page regarding whether
or
> > not this software violates the Windows EULA. Personally, as someone
> > who is not a lawyer and not an expert in licensing, but familiar
> > enough with Microsoft to know, I think if you attempt to monetize a
> > service using this, there's a decent chance that Microsoft will
come
> > after you and attempt to shut you down (depending on how successful
> > you are). Ultimately, I believe they would be successful in arguing
> > that, whether or not this project violates the _letter_ of the
EULA,
> > it certainly violates the _spirit_ and _intent_ of it (that Windows
> > without RDS functionality/licensing is intended for a single user
at a
> > time). Just my opinion, and, if you read through the Github Issue
on
> > it, you'll see that there are many people with equally strong
opinions
> > - but most of them are just as qualified as I am to provide any
expert
> > guidance on it (that is to say, not at all :-). I recommend you
> > consult a legal expert in software licensing before you go down
this
> > path.
> >
> >> Here are some test results :
> >>
> >> Audio Input *does work* in an 'mstsc' session, *with or without*
> >> RDPWrap.
> >>
> >> It does *not* work through Guacamole, with neither latest Firefox
or
> >> Edge.
> >
> > Is this both with and without RDPWrap? If so, there's something
more
> > fundamental going on in your Guacamole setup that is blocking it
from
> > working. I've successfully used audio input with RDP (and with
Spice
> > protocol support that I've been working on), so I know that, in
> > general, it works - which just means it's going to take some more
> > digging to get to the bottom of why it isn't working for you.
> >
> >> For the record, the 'connections' were created using the web
interface
> >> (db-plugin/mariadb) with the *only* options used being :
> >>
> >> Entering the basics (connection name, protocol [RDP], hostname,
port,
> >> username + password)
> >> Ignore certificate
> >> Activate Audio Input
> >>
> >> That being said, it leads me to another question : aren't modern
web
> >> browsers actually supposed to block microphone usage ?
> >> If that's so, as far as I understand, it's not much of a surprise
they
> >> don't let audio input through; and, in my case, Guacamole didn't
> >> trigger a prompt allowing mic usage.
> >>
> >> Do you manually allow mic usage for the Guacamole tabs ?
> >
> > Well, modern browsers should block access to microphone, camera,
etc.,
> > by default, but you can change settings within those browsers to
allow
> > it. That may indeed be what is happening, here - I use Chrome, in
> > general, and when a web page, including Guacamole, wants access to
the
> > mic or camera, I get a little pop-up asking for my permission. It
may
> > be that the browser(s) you're using are just configured to deny
access
> > and not ask, in which case you'll need to dig in and adjust the
> > setting, either providing an exception for the Guacamole web page
or
> > telling it to ask.
> >
> > Oh, one other thing that may be important - many of these "modern
> > browsers" also dis-allow these types of input on plain HTTP
> > connections - so if you haven't configured Guacamole to go through
> > SSL, either by configuring Tomcat for SSL support or by using a
proxy
> > (Nginx, httpd, or your favorite reverse proxy), tne you may want to
do
> > that to make sure that isn't getting in the way.
> >
> > -Nick
> >
> > -------------------------------------------------------------------
--
> > To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> > For additional commands, e-mail: user-help@guacamole.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: State of Audio Input ?
Posted by Alexandre Cariage <al...@sight-sound.ch>.
Hi Nick, thanks again.
About RDPWrap, we're definitely not worried about the legal aspect of it
being an issue :
We're not selling the service, per se (although it _might_ be considered
we sell it as part of another service package), but, most importantly,
I'm planning on a single Windows 10 Host being enough for our use, and
for years to come, even _given the 10 maximum concurrent connections on
non-Server editions of Windows._ Also the link to Guacamole will not be
public. So, as you can see, the scale of the project is the same as the
scale of our business, and probably doesn't call for any action on
Microsoft's part.
About Audio Input, yes, Audio Input does NOT work on Guacamole with and
without RDPWrap.
Finally, thanks for the insight on SSL.
I'm indeed testing internally only and didn't bother setting up HTTPS
for now.
I don't think my browsers particularily block inputs more than the
default settings would, but again, the prompt may not even pop-up
because of that SSL thing.
I'll keep that in mind and keep you updated.
Cheers,
Alexandre Cariage
CH
Le 02/11/2022 15:29, Nick Couchman a écrit :
> On Wed, Nov 2, 2022 at 8:38 AM Alexandre Cariage <al...@sight-sound.ch>
> wrote:
>
>> Hi all, thanks for the guidance and test ideas.
>>
>> @Nick: we are a very small firm trying to offer interresting services
>> with what's available... and almost no budget ;-)
>> Right now RDPWrap seems to work very well, as far as I can tell.
>
> I'm no legal expert, but you'll want to be careful with this one.
> There's a discussion on the RDPWrap Github page regarding whether or
> not this software violates the Windows EULA. Personally, as someone
> who is not a lawyer and not an expert in licensing, but familiar
> enough with Microsoft to know, I think if you attempt to monetize a
> service using this, there's a decent chance that Microsoft will come
> after you and attempt to shut you down (depending on how successful
> you are). Ultimately, I believe they would be successful in arguing
> that, whether or not this project violates the _letter_ of the EULA,
> it certainly violates the _spirit_ and _intent_ of it (that Windows
> without RDS functionality/licensing is intended for a single user at a
> time). Just my opinion, and, if you read through the Github Issue on
> it, you'll see that there are many people with equally strong opinions
> - but most of them are just as qualified as I am to provide any expert
> guidance on it (that is to say, not at all :-). I recommend you
> consult a legal expert in software licensing before you go down this
> path.
>
>> Here are some test results :
>>
>> Audio Input *does work* in an 'mstsc' session, *with or without*
>> RDPWrap.
>>
>> It does *not* work through Guacamole, with neither latest Firefox or
>> Edge.
>
> Is this both with and without RDPWrap? If so, there's something more
> fundamental going on in your Guacamole setup that is blocking it from
> working. I've successfully used audio input with RDP (and with Spice
> protocol support that I've been working on), so I know that, in
> general, it works - which just means it's going to take some more
> digging to get to the bottom of why it isn't working for you.
>
>> For the record, the 'connections' were created using the web interface
>> (db-plugin/mariadb) with the *only* options used being :
>>
>> Entering the basics (connection name, protocol [RDP], hostname, port,
>> username + password)
>> Ignore certificate
>> Activate Audio Input
>>
>> That being said, it leads me to another question : aren't modern web
>> browsers actually supposed to block microphone usage ?
>> If that's so, as far as I understand, it's not much of a surprise they
>> don't let audio input through; and, in my case, Guacamole didn't
>> trigger a prompt allowing mic usage.
>>
>> Do you manually allow mic usage for the Guacamole tabs ?
>
> Well, modern browsers should block access to microphone, camera, etc.,
> by default, but you can change settings within those browsers to allow
> it. That may indeed be what is happening, here - I use Chrome, in
> general, and when a web page, including Guacamole, wants access to the
> mic or camera, I get a little pop-up asking for my permission. It may
> be that the browser(s) you're using are just configured to deny access
> and not ask, in which case you'll need to dig in and adjust the
> setting, either providing an exception for the Guacamole web page or
> telling it to ask.
>
> Oh, one other thing that may be important - many of these "modern
> browsers" also dis-allow these types of input on plain HTTP
> connections - so if you haven't configured Guacamole to go through
> SSL, either by configuring Tomcat for SSL support or by using a proxy
> (Nginx, httpd, or your favorite reverse proxy), tne you may want to do
> that to make sure that isn't getting in the way.
>
> -Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
Re: State of Audio Input ?
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Nov 2, 2022 at 8:38 AM Alexandre Cariage <al...@sight-sound.ch> wrote:
>
> Hi all, thanks for the guidance and test ideas.
>
> @Nick: we are a very small firm trying to offer interresting services with what's available... and almost no budget ;-)
> Right now RDPWrap seems to work very well, as far as I can tell.
>
I'm no legal expert, but you'll want to be careful with this one.
There's a discussion on the RDPWrap Github page regarding whether or
not this software violates the Windows EULA. Personally, as someone
who is not a lawyer and not an expert in licensing, but familiar
enough with Microsoft to know, I think if you attempt to monetize a
service using this, there's a decent chance that Microsoft will come
after you and attempt to shut you down (depending on how successful
you are). Ultimately, I believe they would be successful in arguing
that, whether or not this project violates the _letter_ of the EULA,
it certainly violates the _spirit_ and _intent_ of it (that Windows
without RDS functionality/licensing is intended for a single user at a
time). Just my opinion, and, if you read through the Github Issue on
it, you'll see that there are many people with equally strong opinions
- but most of them are just as qualified as I am to provide any expert
guidance on it (that is to say, not at all :-). I recommend you
consult a legal expert in software licensing before you go down this
path.
>
> Here are some test results :
>
> Audio Input *does work* in an 'mstsc' session, *with or without* RDPWrap.
>
> It does *not* work through Guacamole, with neither latest Firefox or Edge.
Is this both with and without RDPWrap? If so, there's something more
fundamental going on in your Guacamole setup that is blocking it from
working. I've successfully used audio input with RDP (and with Spice
protocol support that I've been working on), so I know that, in
general, it works - which just means it's going to take some more
digging to get to the bottom of why it isn't working for you.
>
> For the record, the 'connections' were created using the web interface (db-plugin/mariadb) with the *only* options used being :
>
> Entering the basics (connection name, protocol [RDP], hostname, port, username + password)
> Ignore certificate
> Activate Audio Input
>
> That being said, it leads me to another question : aren't modern web browsers actually supposed to block microphone usage ?
> If that's so, as far as I understand, it's not much of a surprise they don't let audio input through; and, in my case, Guacamole didn't trigger a prompt allowing mic usage.
>
> Do you manually allow mic usage for the Guacamole tabs ?
Well, modern browsers should block access to microphone, camera, etc.,
by default, but you can change settings within those browsers to allow
it. That may indeed be what is happening, here - I use Chrome, in
general, and when a web page, including Guacamole, wants access to the
mic or camera, I get a little pop-up asking for my permission. It may
be that the browser(s) you're using are just configured to deny access
and not ask, in which case you'll need to dig in and adjust the
setting, either providing an exception for the Guacamole web page or
telling it to ask.
Oh, one other thing that may be important - many of these "modern
browsers" also dis-allow these types of input on plain HTTP
connections - so if you haven't configured Guacamole to go through
SSL, either by configuring Tomcat for SSL support or by using a proxy
(Nginx, httpd, or your favorite reverse proxy), tne you may want to do
that to make sure that isn't getting in the way.
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: State of Audio Input ?
Posted by Alexandre Cariage <al...@sight-sound.ch>.
Hi all, thanks for the guidance and test ideas.
@Nick: we are a very small firm trying to offer interresting services
with what's available... and almost no budget ;-)
Right now RDPWrap seems to work very well, as far as I can tell.
Here are some test results :
Audio Input *does work* in an 'mstsc' session, *with or without*
RDPWrap.
It does *not* work through Guacamole, with neither latest Firefox or
Edge.
For the record, the 'connections' were created using the web interface
(db-plugin/mariadb) with the *only* options used being :
* Entering the basics (connection name, protocol [RDP], hostname,
port, username + password)
* Ignore certificate
* Activate Audio Input
That being said, it leads me to another question : aren't modern web
browsers actually supposed to block microphone usage ?
If that's so, as far as I understand, it's not much of a surprise they
don't let audio input through; and, in my case, Guacamole didn't trigger
a prompt allowing mic usage.
Do you manually allow mic usage for the Guacamole tabs ?
Alexandre Cariage
CH
Le 01/11/2022 18:44, Nick Couchman a écrit :
> On Tue, Nov 1, 2022 at 12:53 PM Sean Hulbert
> <sh...@securitycentric.net.invalid> wrote:
>
>> Hello Nick,
>>
>> I think this is what he is using https://github.com/stascorp/rdpwrap
>
> Well, that's an....interesting...project :-).
>
> I don't know of a reason why Guacamole's audio input would not work
> with that - at least, no reason related to Guacamole itself. Has audio
> input been tried with another RDP client - either Microsoft or
> Xfreerdp, against this same host, and is proved to work correctly?
> Also, have you tested Audio Input from your Guacamole instance against
> a host _not_ using RDPWrap to make sure that it works that way, as
> well?
>
> -Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
Re: State of Audio Input ?
Posted by Mark Barber <md...@aol.com.INVALID>.
I used to use something similar that was for home editions of windows which do not have RDP funtionality.It is worth noting that page states "at reduced functionality" so may not actually support audio.
Sent from the all-new AOL app for Android
On Tue, 1 Nov 2022 at 17:45, Nick Couchman<vn...@apache.org> wrote: On Tue, Nov 1, 2022 at 12:53 PM Sean Hulbert
<sh...@securitycentric.net.invalid> wrote:
>
> Hello Nick,
>
> I think this is what he is using https://github.com/stascorp/rdpwrap
>
Well, that's an....interesting...project :-).
I don't know of a reason why Guacamole's audio input would not work
with that - at least, no reason related to Guacamole itself. Has audio
input been tried with another RDP client - either Microsoft or
Xfreerdp, against this same host, and is proved to work correctly?
Also, have you tested Audio Input from your Guacamole instance against
a host _not_ using RDPWrap to make sure that it works that way, as
well?
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: State of Audio Input ?
Posted by Nick Couchman <vn...@apache.org>.
On Tue, Nov 1, 2022 at 12:53 PM Sean Hulbert
<sh...@securitycentric.net.invalid> wrote:
>
> Hello Nick,
>
> I think this is what he is using https://github.com/stascorp/rdpwrap
>
Well, that's an....interesting...project :-).
I don't know of a reason why Guacamole's audio input would not work
with that - at least, no reason related to Guacamole itself. Has audio
input been tried with another RDP client - either Microsoft or
Xfreerdp, against this same host, and is proved to work correctly?
Also, have you tested Audio Input from your Guacamole instance against
a host _not_ using RDPWrap to make sure that it works that way, as
well?
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
RE: State of Audio Input ?
Posted by Sean Hulbert <sh...@securitycentric.net.INVALID>.
Hello Nick,
I think this is what he is using https://github.com/stascorp/rdpwrap
Thank You
Sean Hulbert
Security Centric Inc.
A Cybersecurity Virtualization Enablement Company
We don't just run you through the motions, Our labs teach you how to think!
System Award Management
CAGE: 8AUV4
AFCEA San Francisco Chapter V.P.
If you have heard of a hacker by name, he/she has failed, fear the hacker you haven’t heard of!
CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication. Content within this email communication is not legally binding as a contract and no promises are guaranteed unless in a formal contract outside this email communication.
igitur qui desiderat pacem, praeparet bellum!!!
Epitoma Rei Militaris
-----Original Message-----
From: Nick Couchman [mailto:vnick@apache.org]
Sent: Tuesday, November 1, 2022 9:01 AM
To: user@guacamole.apache.org
Subject: Re: State of Audio Input ?
On Tue, Nov 1, 2022 at 10:33 AM Alexandre Cariage <al...@sight-sound.ch> wrote:
>
> Greetings,
>
> I'm unable to use Audio Input with Guacamole 1.4.0.
>
> Guacd/tomcat server is Debian 11, only RDP built-in, as protocol.
> Host is Windows 10 Pro (N version, now that I think of it, but audio & video playback works).
> Client is either Firefox 106.x or Edge, on top of W10-22H2. Mic works on the client.
>
> Note also that Host uses the RDPWrap library.
What do you mean "Host uses RDPWrap"? I'm not familiar with RDPWrap, and it is not clear what Host you're talking about?
>
> The "Audio Input" option is activated and will show up in the device list ("Sound" panel in W10) in the Host, but nothing lights green (even though the Client does react to audio input in that same panel).
>
> Just checking for the generally accepted state of the feature, so that I can define if further troubleshooting is worth it for us.
>
Generally, RDP audio input in Guacamole should work.
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: State of Audio Input ?
Posted by Nick Couchman <vn...@apache.org>.
On Tue, Nov 1, 2022 at 10:33 AM Alexandre Cariage <al...@sight-sound.ch> wrote:
>
> Greetings,
>
> I'm unable to use Audio Input with Guacamole 1.4.0.
>
> Guacd/tomcat server is Debian 11, only RDP built-in, as protocol.
> Host is Windows 10 Pro (N version, now that I think of it, but audio & video playback works).
> Client is either Firefox 106.x or Edge, on top of W10-22H2. Mic works on the client.
>
> Note also that Host uses the RDPWrap library.
What do you mean "Host uses RDPWrap"? I'm not familiar with RDPWrap,
and it is not clear what Host you're talking about?
>
> The "Audio Input" option is activated and will show up in the device list ("Sound" panel in W10) in the Host, but nothing lights green (even though the Client does react to audio input in that same panel).
>
> Just checking for the generally accepted state of the feature, so that I can define if further troubleshooting is worth it for us.
>
Generally, RDP audio input in Guacamole should work.
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org