Cengiz,

Kannel supports msisdn provisioning if its RADIUS accounting proxy is configured. It listens for RADIUS packets, manages an (ip, msisdn) table, and by using this table, it inserts an “X-WAP-Network-Client-MSISDN” header in the HTTP request headers.

This scenario works fine for WAP 1.x clients.

Now, my question is, whether msisdn provisioning is also possible for WAP 2.0 clients? As far as I understood, it does not seem possible, because there is not a way to pass WAP 2.0 (i.e. HTTP) requests over Kannel. Am I missing something?

You probably need something to run in your WAP 2.0 gateway (ie. Apache). For this, I wrote an Apache module. I don't think such a module exists otherwise. (I also use my module for WAP 1.x as I use Apache with the http-proxy option in Kannel and wrote my own RADIUS server to simplify the whole thing -- I don't use Kannel's RADIUS handling at all.) Optionally you could use Kannel's RADIUS along with Kannel's ability to forward RADIUS packets on, and then use some RADIUS server that it can forward to plus once again an Apache module (or whatever) to correlate these. That's the best way I know to do it. Note that you probably shouldn't pass the MDN/MSISDN on to every site you come across due to privacy concerns. (I think it's the law in some cases, hence my doing it on my own to ensure this.)


Jon



Reply via email to