It seems that there is no simple solution for this, besides poking with the source code.
----- Original Message ----- From: "Tamas J" <thomasj@xxxxxxxxx>
Sent: Monday, January 31, 2005 1:01 AM
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
------------------------------------------------------- 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/
