Thank you , Stipe tolj. I would like to ask few questions coz i wanted get clear some points as well . I am not a developer but i wanted to know exactly what is the perfect design based on kannel architecture.If every one says Kannel supports for WAP 2.0, how it is done with kannel , i do not meant about coding .
1. Can we directly forward ACC packet which passes form GGSN to the kannel box ? Don't we have a separate radius client or such a program to handle PDU's ? 2. Then all http and UDP requests goes via the wapbox ? 3.while request goes through the wapbox adding MSISDN will be happening for all udp/wap 1.2.1 requests. like that how can we add MSISDN for each HTTP requests ? 4.If we gonna be used SQUID as our proxy server , what are configurations has to be done for capture MSISDN? 5.Then what would be the relationship between squid and the wapbox ? 6.Without having a out of the box solution for WAP 2.0, can't we have WAP 1.2.1 and WAP 2.0 in a single kannel ?? Thanks William ----- Original Message ---- From: Stipe Tolj <[EMAIL PROTECTED]> To: William Carl <[EMAIL PROTECTED]> Cc: [email protected] Sent: Friday, May 23, 2008 17:55:59 Subject: Re: WAP 2.0 in Kannel William Carl schrieb: > Hello > > I have read about more articles , OMA Specs and few faqs on the kannel > mailing list archive also. But i have remained few probs with me, Can > some body help me , on develop/configure kannel for WAP 2.0 ? Hi William, Kannel can be used as WAP 1.2.1 gateway as of this time. In combination with a HTTP proxy (i.e. squid or apache2) also as WAP 2.0 gateway in some extends. In fact I provide a re-written Kannel WAP stack as commercial package, the Kannel CG (carrier-grade) WAP 1.2.1/2.0 gateway for various CDMA and GSM wirless network operators around the world, including full RADIUS accounting field value proxying. In addition Kannel-CG includes a custom HTTP proxy that integrates fully to the model. > 1. When we taking Radius Accounting to kannel box , we shouldn't have a > radius client in between GGSN/SGGSN and the Kannel Box ? or is it must > to be there for handling radius accounts ??? Now, wapbox will run an own RADIUS acct proxy thread. Meaning, we expect PDUs from the NAS (GGSN) and forward those to the final RADIUS server. In the Kannel-CG version, we have an own daemon for that, which is able to proxy to 1-to-N destination transparently, with a flexible storage subsystem for the RADIUS information retrievement. > 2. If we are using SQUID as a web proxy , and we need to get exact > clients ip , which assigned by the GGSN , how can we filtered out it > form the kannel box ? Generally web proxy server receiving wap box's > IP not the clients IP. Now, squid can be configured to pass the client IP in a specific HTTP header to the final HTTP server destination. So you get the origination source IP reference, instead of relying only to the squid server IP on the HTTP server side of the request. > 3. What is the best design for kannel WAP 2.0 architecture ??? Squid is a good approach. We use it in Kannel-CG, but with modifications to the internal code to fit seamlessly to the architecture. > 4. When receiving Accounting form the GGSN to the kannel box , how can > we filtered out all the UDP requests and HTTP requests ??? Can you point out what you want to filter here? Regards, Stipe ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org ------------------------------------------------------------------- Send instant messages to your online friends http://uk.messenger.yahoo.com
