Title: Message
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
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
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
Hi,
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
Paul Keogh wrote:
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
Lars Kristian Roland wrote:
Yes, SMS is always an option, but GPRS is cheaper, so it'd be good to be
able to use it when possible, at least when there's a lot of WAP Push,
for example as part of an online game or other. It could also be the
case that the application knows the MSISDN, but doesn't
Hi,
How about digging into wapbox here and check if you can send us a
patch. I'd be willing for review.
I'm not sure I'd be able to, since my C is a bit too shaky :-)
If I manage to, I'll send it :-)) If anyone else has the time and want
to, that may be a better option.
Regarding the
