Hi Abes,
GnuGk 3.2 will get a new feature to support forwarding new
registrations from the child to the parent ("additive registrations")
so you can avoid touching the config when a new endpoint registers
with the child.
In the child:
[Endpoint]
SupportAdditiveRegistration=1
In the parent:
[RasSrv::RRQFeatures]
SupportAdditiveRegistration=1
The code in the CVS is very fresh, but you can give it a try once the
anonymous CVS is reachable again.
Regards,
Jan
--
Jan Willamowius, Founder of the GNU Gatekeeper Project
EMail : jan@xxxxxxxxxxxxxx
Website: http://www.gnugk.org
Support: http://www.willamowius.com/gnugk-support.html
Abes Dabir wrote:
> Hi,
>
> I have two GnuGk gatekeepers (3.1) setup such that one is a child and
> the other is a parent. I've used the [Endpoint] section on the child to
> set this up. I have the child register a list of prefixes with the
> parent using the "Prefix" option. I know that if I have the
> "UnregisterOnReload" option set, and I modify this list of prefixes, and
> issue a reload command, the parent GK will be updated with the changes
> in the prefix list. My problem is that the child unregistering and
> re-registering causes active calls across the parent-child to be
> dropped. Is there a way for the child to update the parent about the
> list of prefixes that should be forwarded to it, without causing active
> calls across the pair to drop?
>
> My gatekeeper.ini on the child is as follows. The parent is very
> similar and I can provide that too if required:
>
>
>
>
> [Gatekeeper::Main]
> fourtytwo = 42
> name = ETcc
> timetolive = 100
> statusport = 7000
> tracelevel = 3
> home = 10.1.1.200,172.22.0.4,127.0.0.1
> externalip = 172.22.0.4
>
> [RoutedMode]
> gkrouted = 1
> h245routed = 1
> acceptunregisteredcalls = 1
> acceptneighborscalls = 1
> callsignalport = 1720
> callsignalhandlernumber = 1
> removeh245addressontunneling = 1
> dropcallsbyreleasecomplete = 1
> supportnatedendpoints = 1
> supportcallingnatedendpoints = 1
> q931portrange = 30000-30099
> h245portrange = 31000-31099
> sendreleasecompleteondrq = 1
>
> [Proxy]
> enable = 1
> internalnetwork = 10.1.1.200/255.255.255.0
> t120portrange = 32000-41999
> rtpportrange = 32000-41999
> proxyfornat = 1
> proxyforsamenat = 0
> proxyalways = 1
>
> [RasSrv::LRQFeatures]
> neighbortimeout = 6
> forwardhopcount = 8
> alwaysforwardlrq = 1
> includedestinationinfoinlcf = 1
> ciscogkcompatible = 1
>
> [RoutingPolicy]
> default = internal,explicit,parent,enum,srv,dns
>
> [Endpoint]
> Gatekeeper=172.22.0.1
> Prefix=6666
> H323ID=jimmy,6666
> UnregisterOnReload=1
>
> [GkStatus::Auth]
> rule = explicit
> delayreject = 5
> 127.0.0.1 = allow
>
> [LogFile]
> rotate = Weekly
> rotateday = Sun
> rotatetime = 00:59
> filename = /var/log/magor/gnugk/gnugk.log
>
> [PortNotifications]
> q931portopen =
> /opt/magor/util/scripts/firewall/gnugk/open-pinhole-inbound-gnugk.sh %p
> %n %i
> q931portclose =
> /opt/magor/util/scripts/firewall/gnugk/close-pinhole-inbound-gnugk.sh %p
> %n %i
> h245portopen =
> /opt/magor/util/scripts/firewall/gnugk/open-pinhole-inbound-gnugk.sh %p
> %n %i
> h245portclose =
> /opt/magor/util/scripts/firewall/gnugk/close-pinhole-inbound-gnugk.sh %p
> %n %i
> rtpportopen =
> /opt/magor/util/scripts/firewall/gnugk/open-pinhole-inbound-gnugk.sh %p
> %n %i
> rtpportclose =
> /opt/magor/util/scripts/firewall/gnugk/close-pinhole-inbound-gnugk.sh %p
> %n %i
>
>
>
>
>
>
> Thanks for the help,
> Abes Dabir
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________________
Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/
