What are the existing features to save the current ip/msisdn of the subscriber into a file/database ? basically to store msisdn, clients ip address , session id.
As i know , in kannel there are database DLR storing methods are available.
( Hey kane , why are you silent ? I expecting your ideas also , then we can reach to the final resualts emmediatly )
Thank you,
Luke,
Deon van der Merwe <[EMAIL PROTECTED]> wrote:
Deon van der Merwe <[EMAIL PROTECTED]> wrote:
Hi Luke,
On 1/28/06, luke devon <[EMAIL PROTECTED]>wrote:
> hi ,
>
> Your scenario is just to install squid and that all WAP 2.0 clients parse
> via the proxy . Your concept is ok , only for just redirecting to the
> internet . But i think you dont consider about how to parse msisdn , session
> id , ip address ........UA profiles , etc..... to the proxy .
>
> Because most of wap sites are now very intelligent. not just a wap sites.
> They have done lots of restrictions on their end . That msisdn will be the
> main parameter.
> So that's meant , we supposed to parse that features , after decode it from
> the radius to the proxy.
>
It is not the responsibility of the proxy to do any of the
UAprofiles... as you say: the actual website already does that. The
proxy will pass all the UA headers on to that website.
Your first question was how to handle WAP2 clients. The "solution"
offered was squid/apache_mod_proxy.
Your next question is with regard to the MSISDN: you get the MSISDN
from the radius accounting packet inside Kannel. So, WAP1 clients is
no problem. You now also want the same MSISDN in your WAP2
"solution". Your first step would be just to get the WAP2 "solution"
up and running? Have you succeeded in that yet? yes? Great! Now,
try and solve your next problem...
- you now have 2 applications running that both need the MSISDN
- so you need a way of sending the MSISND/RADIUS packets to both.
- We use FreeRadius (see: http://www.freeradius.org/) to solve that
for our systems. Note also that Kannel itself can also proxy these
accounting messages to another system.
- Now you can use any of the existing features to save the current
ip/msisdn of the subscriber into a file/database
- Now you write a very small module for Squid to extract the MSISDN from there.
That is more or less the steps that I followed to solve the problems
(challanges). Hope that it helps you. Note, that getting support for
WAP2.0 has nothing to do with Kannel... the path we followed was to
see it as 2 seperate problems, each with its own solution.
Send instant messages to your online friends http://uk.messenger.yahoo.com
