[GnomeMeeting-devel-list] Gatekeeper/Gnomemeeting registration issue

[Gwendolynn ferch Elydyr <gwen reptiles org>]

Hola!

I'm seeing some oddball errors with gnomemeeting and gnugk, and I'm hoping
that somebody has seen this issue:

With gnomemeeting 0.98.5 against gnugk 2.0.6, on Redhat 7.3 w/gnome2:

	Registering as 'Gatekeeper ID' results in 'gatekeeper error'
		- ethereal shows two broadcast packets
	Registering as 'Gatekeeper Host' or 'Automatic' is normal
		- ethereal records h.225.0 registration traffic
		- calls proceed normally

With gnomemeeting 0.85.3 against gnugk 2.0.6, on Redhat 7.3 vanilla:

	Registering as 'Gatekeeper ID' results in 'gatekeeper error'
		- ethereal shows two broadcast packets
	Registering as 'Gatekeeper Host' or 'Automatic' is normal
		-ethereal records h.255.0 registration traffic

		-but-

		- attempting to place calls results in the gatekeeper
		returning:

ARJ|172.16.11.17:1720|172.16.11.20:h323_ID|First Last:h323_ID=Last:h323_ID|false|calledPartyNotRegistered;
ARJ|172.16.11.17:1720|172.16.11.20:h323_ID|First Last:h323_ID=Last:h323_ID|false|calledPartyNotRegistered;

		- checking registrations against the gatekeeper shows that the
		user is registered.

Does anybody know if the 'calledPartyNotRegistered' issue is a gnugk
or a gm issue - and how to resolve it?  Due to the current production
environment, upgrading to gnome2 is problematic at best, so I'm really
hoping that there's a solution that will allow 0.85.3 to work here.

cheers!
==========================================================================
"A cat spends her life conflicted between a deep, passionate and profound
desire for fish and an equally deep, passionate and profound desire to
avoid getting wet.  This is the defining metaphor of my life right now."