I would not setup this using parent-child configuration. I would rather setup
proxies as permanent endpoints. For authentication, remove everything
from Gatekeeper::Auth section.
I'm just setting this up, too.
The drawback of permanent endpoints is that you don't notice if a proxy goes down
(with child/parent, you do, due to outstanding registrations).
MS
----- Original Message ----- From: "david winter" <dwinter@xxxxxxxxxxxxxxxxxx>
Sent: Friday, April 30, 2004 8:08 PM
Michal,[endpoint]->reg to parent and [routingpolicy]->parent? or something along those lines?
Back to a conversation we had earlier i want to clarify my understanding. In order to maximize the potential of a proxying gnugk system. I should configure a hierarchy system where a gnugk-parent acting solely as a GK (maybe with routed signalling) controlls one to many gnugk-proxying-gateways. The proxying-gateways should all have identical routing setup so the parent can round robin the calls down to them all and expect equal behavior. The proxying-gateways should also have thier authentication config removed and only accept calls from thier parent GK?
You said this "
Currently, only a round robin policy is supported. You configure proxies just like a normal gatkeeper, but you want to disable authentication and accounting probably (and perform it on the master gk or somewhere else)."
What parts of the config do i remove authentication from? I am only using RRQAuth now on my proxy, so i would diable that, enable
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
