You don't have to authorize twice, just use a rule for ARQ,SetupUnreg. LRQ is not supposed to trigger routing decisions - it's only to answer whether the gatekeeper CAN route this particular destination. Actual routing decision is done then inside Setup handler.
----- Original Message ----- From: "Tamas J" <thomasj@xxxxxxxxx>
Sent: Sunday, January 30, 2005 9:09 PM
I'm trying to make h323-redirect-number working with GNUgk 2.2.2.
I noticed one thing. When I call from a registered endponit and h323-redirect-number is only for Setup message, the call goes to the previously choosed gateway in place of another according to the rewritten number. As I saw, the decision is made in phase of receiving ARQ and later h323-redirect-number with Setup only rewrites the number, no other routing is applied. In this way, I have to authorize the same call twice (ARQ and Setup).
Won't be better to be able to call routing logic after Setup message authentication as well? I know, there is h323-redirect-ip-address, but it cannot be good in case, the destination is not a permanent gateway but for example a neighbor. How should be such situation solved? Only with allowing RadAliasAuth for ARQ as well?
How can I use h323-redirect-number with LRQ? (I don't have an environment to test, I have just some thoughts)
Thanks in advance, Tamas
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
