You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Kjell Otto (JIRA)" <ji...@apache.org> on 2017/03/06 09:46:32 UTC

[jira] [Commented] (GUACAMOLE-228) RDP audio input not working on Windows Server 2012 / 2016

    [ https://issues.apache.org/jira/browse/GUACAMOLE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896991#comment-15896991 ] 

Kjell Otto commented on GUACAMOLE-228:
--------------------------------------

I couldn't really tell what you wanted to know, but I've had a look into {{/opt/guacd/bin/build-guacd.sh}}, which made me look into {{ /usr/local/lib/freerdp/ }}, which in turn showed this:

{code}
[root@0f6a4a838fc6 bin]# ls -la /usr/local/lib/freerdp/
total 1400
drwxr-xr-x 2 root root   4096 Mar  3 07:23 .
drwxr-xr-x 3 root root   4096 Mar  3 07:23 ..
-rwxr-xr-x 1 root root   1086 Mar  3 07:23 guacai.la
-rwxr-xr-x 1 root root 337536 Mar  3 07:23 guacai.so
-rwxr-xr-x 1 root root   1086 Mar  3 07:23 guacdr.la
-rwxr-xr-x 1 root root 543880 Mar  3 07:23 guacdr.so
-rwxr-xr-x 1 root root   1092 Mar  3 07:23 guacsnd.la
-rwxr-xr-x 1 root root 262024 Mar  3 07:23 guacsnd.so
-rwxr-xr-x 1 root root   1092 Mar  3 07:23 guacsvc.la
-rwxr-xr-x 1 root root 261680 Mar  3 07:23 guacsvc.so
[root@0f6a4a838fc6 bin]#
{code}

I'm using Google Chrome and I've just checked again, the microphone settings are set as they should, no block or anything. I've just now tested all 3 different Microphone Input selections as well. I've got "Standard Settings", "Communication" and "Microphone (High Definition Audio Device)". None of which is working.

I've opened up the browser console and right when I click on record in audacity, in Chrome this message pops up:

{code}
getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
t @ app.js?v=0.9.12-incubating:11
g.onack @ app.js?v=0.9.12-incubating:12
a.onack @ app.js?v=0.9.12-incubating:2
ack @ app.js?v=0.9.12-incubating:22
a.oninstruction @ app.js?v=0.9.12-incubating:33
b.onmessage @ app.js?v=0.9.12-incubating:121
{code}

Then I've tried Firefox and it asks me every time I want to record something, BUT: it works. The sound is recorded a bit too fast, so it sounds like it's sped up a bit when played. Also, in Firefox, this message is shown:

{code}
navigator.mozGetUserMedia has been replaced by navigator.mediaDevices.getUserMedia                    app.js:11:346
{code}

Since this might "just be a Chrome issue", I'll now try and set up an SSL certificate in order to circumvent this. Any other ideas on how to tackle this? Maybe a warning in the web would be nice?

> RDP audio input not working on Windows Server 2012 / 2016
> ---------------------------------------------------------
>
>                 Key: GUACAMOLE-228
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-228
>             Project: Guacamole
>          Issue Type: Bug
>    Affects Versions: 0.9.11-incubating
>            Reporter: Kjell Otto
>
> We're experiencing sound bugs when connecting via RDP to Windows 2012 R2 and Windows 2016 Servers. We've followed all the steps necessary in order to enable the sound and we're able to connect via Windows RDP without any issue. Connect via RDP to a target PC and have the following settings in place:
> Followed all the necessary steps gathered here: 
> https://serverfault.com/questions/549812/cant-redirect-microphone-by-rdp-no-audio-devices-are-installed# ( https://glyptodon.org/jira/browse/GUAC-1511 )
> From here: https://guacamole.incubator.apache.org/doc/gug/configuring-guacamole.html 
>  - enable-audio-input
> Also, we've started the "Windows Audio" and "Windows Audio Endpoint Builder" Service.
> On Windows Server 2012 R2 and Windows Server 02016, if you open the Sound settings, we don't see any amplitude for the "Remote Audio" microphone under the "Recording" tab. We've tried recording on both setups with audacity too, and with direct RDP connections everything works as expected.
> We would love to get feedback on this and are very willing to help in any way. Please let us know how we can help.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)