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?

 

Thanks in advance.

 

Cengiz

Reply via email to