Re: RADIUS ACCT info used in WAP Push

Stipe Tolj <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization The Kannel Group
Message-ID <[email protected]>
Lars Kristian Roland wrote:
> Hi,
>  
> Have you considered adding the RADIUS information in such a way that the
> client pushing a wap push via the push proxy can send the pap-request to
> an msisdn rather than an IP also when sending a udp push, but the push
> proxy sends it to the IP address (wap push proxy must then do the
> mapping between msisdn and ip address based on the information from
> radius acct)? 
>  
> I can see that you've implemented this mapping for receiving acct radius
> info for normal wap requests, and I guess this would be a small
> extension to that???

Hi Lars,

a good question.

But as I remember, Kannel's PPG _is_ able to send Push messages to 
MSISDN numbers generically. Since it will pass it over the SMS bearer 
to the phone. So I don't see the necessarity to have the RADIUS acct 
mapping active here.

The _only_ benefit I see from this here is to allow PI (push 
initiators) to send push messages over PPG with MSISDNs as target, and 
  wapbox would try to resolve this into IPs, in case the MSISDN is 
online and connected to the NAS at that specific point of time. So 
something like this:

a) PI sends push msg to PPG
b) PPG tries to resolve MSISDN into IP (from RADIUS acct mapping)
c) if MSISDN is online at this time, PPG is able to address the push 
message via IP
d) if it's not online, utilize SMS bearer to push the message (this is 
the current default behavior for MSISDN targets)

Hmm, Aarno, some comments from your side?

Stipe

mailto:stolj_{at}_wapme.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.2 (Cygwin)

mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-----END PGP PUBLIC KEY BLOCK-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.