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 [endpoint]->reg to parent and [routingpolicy]->parent? or something along those lines?
-- David Winter Senior Network Engineer Planet-Telecom, Inc. Tampa FL (813)901-5182 Office (813)864-3162 Direct (813)817-4204 Mobile (813)881-9762 Fax ------------------------------------------ AIM: mobofool ICQ: 3563403 MSN: dwinter@xxxxxx Y!: vt_fool
