%{callerip} is an IP address the signalling connection comes from.
In this case, the signalling connection comes from GK1 IP.----- Original Message ----- From: "Costin Manda" <siderite@xxxxxxxxx>
Sent: Wednesday, March 30, 2005 2:01 PM
It should work fine for signalling authentication. BTW AliasAuth does not have support for Setup auth, if I remember correctly.
I checked it out. Seems cool. However it lacks something that AliasAuth has: signalling IP authentication for Setup requests.
I meant the sig ip thing. Anyway, maybe I don't understand the usage correctly. Let me lay out what I have in mind:
GW or GK (let's call it endpoint1) -> GK1 -> GK2 -> endpoint2 GK1 runs in routed mode. GK2 needs to authenticate all calls coming through GK1, no matter who endpoint1 is.
Now, if I understand correctly, SQLAuth does have a callerip variable to take into the query, but that would be the IP of endpoint1, not of GK1.
I could do this by authenticating LRQs, but I have no idea what happends when a SetupCall comes to gnugk with no LRQ or ARQ before it and AcceptUnregisteredCalls=1, it could bypass this.
I am looking at a Setup packet and it contains a sourceCallSignalAddress in it. I don't know if it is a standard parameter or not, though.
Any thought?
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
