Hi David, > I think radius integration is good only when phone is http capable, in that > case you don't need wapgw to provide MSISDN, in other cases (much more) you > need wapgw to provide connection to mmsc.
Well, IMHO RADIUS is crucial even in WAP gateway scenario as it grabs MSISDN from RADIUS. I had one strange idea about those phones having TCP/IP stack. They are typically still assigned an internal IP from RADIUS and operator somewhere in the middle does the NAT. End user (service provider) sees the user's external IP, so one way to know the internal IP (and then the MSISDN) would be to ask NAT gateway for the internal IP, but that's too exotic I think :) To summarize, forcing WAP-less clients to go through HTTP proxy add add MSISDN header is the most transparent solution. > P.S. Dziugas, you are Lithuanian right? Does my name made you think so? :) Yes, I'm pure lithuanian ;) -- Dziugas _______________________________________________ Devel mailing list [email protected] http://mbuni.org/mailman/listinfo/devel_mbuni.org
