[GUACAMOLE-25] Add support for audio input

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.9.10-incubating
• Component/s: guacamole, guacamole-common-js, libguac, RDP
• External issue URL: https://glyptodon.org/jira/browse/GUAC-1511
• Assignee: Mike Jumper
• Reporter: Mike Jumper
• Created: 19/May/16 06:06
• Updated: 08/Aug/16 20:37
• Resolved: 02/Jun/16 21:44

Description

The description of this issue was copied from GUAC-1511, an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the Apache Incubator.

Comments, attachments, related issues, and history from prior to acceptance have not been copied and can be found instead at the original issue.

Guacamole's protocol does already technically support audio streams in either direction, but this is only currently implemented in the server-to-client direction. The same support can be added such that client-to-server audio streams are initiated automatically (when enabled).

The procedure could be as follows:

1. Guacamole client attempts to create an audio stream be sending an "audio" instruction to the server.
2. If audio input is supported and enabled, the server responds with an "ack" instruction indicating success. The Guacamole client then requests access to the microphone via JavaScript.
3. The browser prompts the user for access if they have not already granted/denied it. If access is granted, the audio stream begins. If access is denied, the audio stream is simply closed.

This would require adding support for RDP's audio input channel (not part of RDPSND, but very similar). The same could no doubt also be done for PulseAudio.