Re: radius proxy msisdn store

Stipe Tolj wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Stipe Tolj wrote:
> 
>> Your NAS (network access server), ie. any CSD dial-in node or GPRS APN point
>> will forward the RADIUS accounting PDUs (UDP datagrams) to Kannel, literally
>> wapbox. wapbox then answers to the NAS as if it is the final RADIUS daemon, so
>> NAS is satisfied in terms of a positive ACK. wapbox greps the corresponding
>> MSISDN (caller line id in RADIUS terminology) and DHCP'ed client IP and packs
>> this in a 2-way cross-referenced dictionary hash. So you can resolve MSISDN->IP
>> and IP->MSISDN within the code. When a WAP request is processed, wapbox simply
>> "queries" that dictionary hash and injects the appropriate header with the
>> resulting MSISDN. (Of course all the housekeeping with RADIUS acct start/stop
>> events are done, so we also drop the MSISDN<->IP relation when NAS indicates
>> that the session died.).
> 
> BTW, didn't mention here that Kannel will of course proxy the RADIUS acct PDUs
> towards a "final RADIUS" instance in order to have accurate accounting on the
> existing systems.
> 
> So Kannel is really acting as RADIUS acct proxy, in the middle of the NAS and
> the RADIUS daemon itself.
I've got the point. But the main objective is to make mms wap gateway 
redundant and load-sharable. Some commercial wap gateways do like this. 
All session data is stored in shared transactional databases. All wap 
gateways have access to it. If request comes all session data is stored 
and visible to all nodes. This solution is easy to scale. Of course 
there some negative impacts like performance decrease. I just wanted to 
understand is it possible to implement feature like this without serious 
changes in code. Anyway thanks for answers.
-- 
Sincerely Yours,
Andrey Loginov