Virtual desktops on separate machines

[BrentBaccala]

Currently, the virtual desktops have to be on the same machine as freeswitch to allow "teacher mode" to control the audio settings.

The freeswitch API key is obtained by the scripts by reading a file in the filesystem. Having a better way to communicate this key would allow the scripts to run on a different machine and control freeswitch via a TCP session.

Alternately, the BBB server could be enhanced to control the freeswitch deaf controls, and this might be the better approach. If we start using multiple audio conferences (see the "multiple teachers" issue), then probably changes will need to be made to the BBB/freeswitch interaction. Maybe it's better for the scripts to control freeswitch by going through the bbb server.

[BrentBaccala]

The Python scripts also depend on being on the same machine as the Postgres database used to map BBB names to UNIX usernames, and for the database to be set for "trust" authentication (the default Greenlight configuration), where no password is needed when connecting from localhost.