Nicolas,
>>You're going to see less and less new phones supporting the
>>WAP stack anyway, so you might as well get working on the next gen
>>configurations (ie. how you want to route the traffic, etc.).
>
> Ok I see. But what do you mean by "next gen configurations" ? do such
> solutions already exist ?
There are commercial WAP gateways that do both WAP 1 and WAP 2 as
well as RADIUS, yes.
> Because the problem here is that I can't obtain the MSISDN with Squid,
> that's why I need these "HTTP phones" to work with Kannel... and I assume
> I'm not the only one in this situation (?)
Yep, we had the same issue here. I ended up using Apache as the
WAP 2 server and wrote a module for it to do the RADIUS piece. There
might be some solution out there (open source) by now, though.
Jon
