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

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

[~mike.jumper] It works™. With SSL enabled it works with Google Chrome too. 
What's still rather weird is that all sound is played at way too much speed. 
It's at least like 2x the speed of the actual recording.



> 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)

Reply via email to