Hmm, how can I tell GNUgk to accept an LRQ for a route which's
existence is known only from RADIUS server? I set up a gatekeeper
neighboring connection with a tech-prefix and when the terminating GK
got the call, it wasn't able to route it (in LRQ request) while the
RADIUS server's role would be to rewrite the number which is routable.
2005/01/30 23:01:17.573 5 job.cxx(360) JOB Worker threads: 8 total - 8 busy, 0 idle
2005/01/30 23:01:17.573 5 job.cxx(188) JOB Starting Job LRQ at Worker thread 245770
2005/01/30 23:01:17.573 1 RasSrv.cxx(328) RAS LRQ Received
2005/01/30 23:01:17.573 3 gkauth.h(845) GKAUTH default LRQ check ok
2005/01/30 23:01:17.573 5 Routing.h(125) ROUTING Checking policy Internal for the request LRQ 1
2005/01/30 23:01:17.573 5 Routing.h(125) ROUTING Checking policy Neighbor for the request LRQ 1
2005/01/30 23:01:17.573 5 Routing.h(125) ROUTING Checking policy Explicit for the request LRQ 1
2005/01/30 23:01:17.634 2 RasSrv.cxx(373) LRJ|
So in LRQ processing the internal logic doesn't know about the route,
so it rejects the call - while RADIUS would be able to rewrite the
number which is routable.
How could I overcome this case?
Thanks in advance,
Tamas
Monday, January 31, 2005, 12:33:16 AM, Zygmuntowicz wrote:
ZM> You don't have to authorize twice, just use a rule for ARQ,SetupUnreg.
ZM> LRQ is not supposed to trigger routing decisions - it's only to answer
ZM> whether the gatekeeper CAN route this particular destination. Actual
ZM> routing decision is done then inside Setup handler.
ZM> ----- Original Message -----
ZM> From: "Tamas J" <thomasj@xxxxxxxxx>
ZM> 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/
