Difference between revisions of "Installing and configuring the GnuGK gatekeeper"
From TD-er's Wiki
Jump to navigationJump to searchm |
|||
| Line 3: | Line 3: | ||
'''UNDER CONSTRUCTION''' | '''UNDER CONSTRUCTION''' | ||
Suggestions: Proxy, routing | Suggestions: Proxy, routing | ||
| − | |||
Start the gatekeeper with the following command: | Start the gatekeeper with the following command: | ||
gnugk -ttt -rr | gnugk -ttt -rr | ||
| − | |||
Once the gatekeeper is installed you can register your gnomemeeting clients and the trixbox with the gatekeeper (see section '''[[gnomemeeting]]'''). For the trixbox this means an amportal restart. For the clients you need to open the preferences an register with the gatekeeper. For all practical purposes it is wisest to always start your gatekeeper first before any other starting any other applications. | Once the gatekeeper is installed you can register your gnomemeeting clients and the trixbox with the gatekeeper (see section '''[[gnomemeeting]]'''). For the trixbox this means an amportal restart. For the clients you need to open the preferences an register with the gatekeeper. For all practical purposes it is wisest to always start your gatekeeper first before any other starting any other applications. | ||
Revision as of 14:50, 8 March 2007
Packages for this gatekeeper are not available for CentOS. We found out that this gatekeeper was already installed in Etch. (System administration provided us with two machines with etch so we could get the sound working).
UNDER CONSTRUCTION Suggestions: Proxy, routing
Start the gatekeeper with the following command:
gnugk -ttt -rr
Once the gatekeeper is installed you can register your gnomemeeting clients and the trixbox with the gatekeeper (see section gnomemeeting). For the trixbox this means an amportal restart. For the clients you need to open the preferences an register with the gatekeeper. For all practical purposes it is wisest to always start your gatekeeper first before any other starting any other applications.
