I run this in 2 setups, one against the official guacd docker container "guacamole/guacd:1.0.0", and one against guacamole-lite. If guacamole-lite doesn't send the opcodes I'll stop trying with it. In the former setup I'm using the tutorial example (with the modification specified in my previous message in the index.html file) to build a custom webapp that communicates with guacd.
On Mon, Jul 22, 2019 at 3:22 PM Nick Couchman <[email protected]> wrote: > > > On Mon, Jul 22, 2019 at 4:26 AM Enrico D'Angelo <[email protected]> > wrote: > >> Hi Nick, >> >> actually I modified the tutorial with those lines: >> >> let connectionString = ""; >> Guacamole.AudioPlayer.getSupportedTypes().forEach(function (mimetype) { >> connectionString += "&GUAC_AUDIO=" + encodeURIComponent(mimetype); >> }); >> Guacamole.VideoPlayer.getSupportedTypes().forEach(function (mimetype) { >> connectionString += "&GUAC_VIDEO=" + encodeURIComponent(mimetype); >> }); >> connectionString = connectionString.slice(1); >> >> // Connect >> guac.connect(connectionString); >> >> that seems to be what the actual webapp does, the resulting >> connectionString is "GUAC_AUDIO=audio%2FL8&GUAC_AUDIO=audio%2FL16" >> > > Are you running this against the official Guacamole Client back-end > (guacamole.war in Tomcat), or against the guacamole-lite back-end? Looking > at the code for guacamole-lite, I'm not sure it implements audio support. > Based on the following lines in their code: > > > https://github.com/vadimpronin/guacamole-lite/blob/03d688a1f8633fca1f6620c955a0b31dff5f3a41/lib/GuacdClient.js#L79-L88 > > it looks to me like they just send empty audio, video, and image opcodes > during the handshake. I think this works fine because there is a default > for the image opcode, even if you send an empty one there is a default > image type that is supported - however, the same is not true of audio and > video types. > > -Nick > >> -- [image: Kopjra Logo] *Enrico D'Angelo* Senior Software Engineer +39 338 759 6369 [email protected] *Kopjra Srl* www.kopjra.com
