Installing and configuring the GnuGK gatekeeper - Revision history

Fabio at 13:40, 13 March 2007

2007-03-13T13:40:14Z

Fabio: /* Installing GnuGK */

2007-03-13T13:39:48Z

Installing GnuGK

Fabio at 13:09, 13 March 2007

2007-03-13T13:09:35Z

Fabio: Configuration of GnuGK gatekeeper moved to Installing and configuring the GnuGK gatekeeper: wrong title

2007-03-13T13:07:10Z

Configuration of GnuGK gatekeeper moved to Installing and configuring the GnuGK gatekeeper: wrong title

Anneke at 13:45, 8 March 2007

2007-03-08T13:45:51Z

Anneke at 13:45, 8 March 2007

2007-03-08T13:45:03Z

Anneke at 13:44, 8 March 2007

2007-03-08T13:44:00Z

Anneke at 13:43, 8 March 2007

2007-03-08T13:43:10Z

Anneke at 13:42, 8 March 2007

2007-03-08T13:42:27Z

Anneke at 13:41, 8 March 2007

2007-03-08T13:41:42Z

@@ Line 1: / Line 1: @@
 == Installing GnuGK ==
@@ Line 14: / Line 13: @@
 Once the usefulness of GnuGK has been proven, of course it is practical to run the gatekeeper on the '''TrixBox'''. Unluckily there is no '''CentOS'''-package for it, so we first need to add other repositories.
-It turns out that OpenSUSE delivers GnuGK as a package, so we will add those repositories to the yum package manager:
+It turns out that '''OpenSUSE''' delivers GnuGK as a package, so we will add those repositories to the yum package manager:
   [root@asterisk1 ~]# cd /etc/yum.repos.d/

@@ Line 2: / Line 2: @@
 == Installing GnuGK ==
-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).
+Packages for the GnuGK gatekeeper are not present in the CentOS package repositories.
 == Running GnuGK ==

← Older revision		Revision as of 13:09, 13 March 2007
Line 1:		Line 1:
		+
		+	== Installing GnuGK ==
		+
	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).		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).
		+
		+	== Running GnuGK ==
		+
		+	=== GnuGK from the command line ===
		+

	Start the gatekeeper with the following command:		Start the gatekeeper with the following command:

← Older revision		Revision as of 13:45, 8 March 2007
Line 37:		Line 37:
	''		''

−	To make H323 -> SIP calls we are interested in '''Case III'''.	+	To make H323 -> SIP calls we are interested in '''Case III'''. We haven't accomplished anything in this area (yet).

@@ Line 26: / Line 26: @@
 From [http://www.gnugk.org/gnugk-manual-5.html#proxy Gnugk website]:
-''Call signaling messages may be passed in two ways. The first method is Direct Endpoint Call Signaling, in which case the call signaling messages are passed directly between the endpoints. The second method is Gatekeeper Routed Call Signaling. In this method, the call signaling messages are routed through the gatekeeper between the endpoints. The choice of which methods is used is made by the gatekeeper.
+''Call signaling messages may be passed in two ways. The first method is Direct Endpoint Call Signaling, in which case the call signaling messages are passed directly between the endpoints. The second method is Gatekeeper Routed Call Signaling. In this method, the call signaling messages are routed through the gatekeeper between the endpoints. The choice of which methods is used is made by the gatekeeper.''
-When Gatekeeper Routed call signaling is used, the gatekeeper may choose whether to route the H.245 control channel and logical channels.
+''When Gatekeeper Routed call signaling is used, the gatekeeper may choose whether to route the H.245 control channel and logical channels.''
-'''Case I''' The gatekeeper doesn't route them. The H.245 control channel and logical channels are established directly between the endpoints.
+'''''Case I''' The gatekeeper doesn't route them. The H.245 control channel and logical channels are established directly between the endpoints. ''
-'''Case II''' The H.245 control channel is routed between the endpoints through the gatekeeper, while the logical channels are established directly between the endpoints.
+'''''Case II''' The H.245 control channel is routed between the endpoints through the gatekeeper, while the logical channels are established directly between the endpoints. ''
-'''Case III''' The gatekeeper routes the H.245 control channel, as well as all logical channels, including RTP/RTCP for audio and video, and T.120 channel for data. In this case, no traffic is passed directly between the endpoints. This is usually called an H.323 Proxy, which can be regarded as an H.323-H.323 gateway.
+'''''Case III''' The gatekeeper routes the H.245 control channel, as well as all logical channels, including RTP/RTCP for audio and video, and T.120 channel for data. In this case, no traffic is passed directly between the endpoints. This is usually called an H.323 Proxy, which can be regarded as an H.323-H.323 gateway.
 ''
 To make H323 -> SIP calls we are interested in '''Case III'''.

← Older revision	Revision as of 13:07, 13 March 2007
(No difference)

@@ Line 22: / Line 22: @@
 Once the gatekeeper is installed you can register your gnomemeeting clients and the trixbox with the gatekeeper. For the trixbox this means an amportal restart. For the clients you need to open the preferences and register with the gatekeeper. For all practical purposes it is wisest to always start your gatekeeper first before starting any other applications. That way all devices can register once started.
-How can the gatekeeper handle calls:
+===How can the gatekeeper handle calls:===
 From [http://www.gnugk.org/gnugk-manual-5.html#proxy Gnugk website]:

@@ Line 20: / Line 20: @@
 It seems of the utmost importance that you use the -rr instead of the -r option. This made all the difference in trying to establish a SIP -> H323 call.
-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 and register with the gatekeeper. For all practical purposes it is wisest to always start your gatekeeper first before starting any other applications. That way all devices can register once started.
+Once the gatekeeper is installed you can register your gnomemeeting clients and the trixbox with the gatekeeper. For the trixbox this means an amportal restart. For the clients you need to open the preferences and register with the gatekeeper. For all practical purposes it is wisest to always start your gatekeeper first before starting any other applications. That way all devices can register once started.
 How can the gatekeeper handle calls: