<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
Hi Mike:<br>
<br>
Here's are instructions on running a bridge server. The usage output
looks like this:<br>
<blockquote><tt>Usage: BridgeServer.py <<--venueServer
venueServerUrl>|</tt><br>
<tt> <--venueServerFile venueServerFile>|</tt><br>
<tt> <--file venueUrlFile>|</tt><br>
<tt> <--venue venueUrl>></tt><br>
<tt> <--qbexec quickbridgeExecutable></tt><br>
<tt> [--cert certpath]</tt><br>
<tt> [--key keypath]</tt><br>
<tt> [--name name]</tt><br>
<tt> [--location location]</tt><br>
<tt> [-h|--help]</tt><br>
<tt> [-d|--debug]</tt><br>
</blockquote>
So the required parameters are the path to a QuickBridge executable,
and one of either a venue server url, a venue server file, a venue url,
or a venue file. If given a venue server url, all venues on that
server are bridged. If given a venue url, that venue is bridged. The
file options provide a mechanism for bridging multiple venue servers or
multiple venues; in both cases, the file contains a list of urls.<br>
<br>
The name and location parameters represent the bridge provider to
bridge users, in their venue client. When a user selects "Use Unicast"
in the venue client, a list of bridges is displayed (by name and
location). The user selects one and the media tools connect to the
bridge addresses.<br>
<br>
So here's an example:<br>
<tt><br>
python2 BridgeServer.py --qbexec /usr/bin/QuickBridge \<br>
--venueServer
<a class="moz-txt-link-freetext" href="https://ag21server:8000/VenueServer">https://ag21server:8000/VenueServer</a></tt><br>
<br>
I think your use will look more like running a bridge server against
multiple venue servers, so you'll use the --venueServerFile option
instead.<br>
<br>
Let me know if you have questions.<br>
<br>
Cheers,<br>
<br>
Tom<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>