Hi List,
I've just tried to use MSISDN feature of kannel. Seems like it doesn't
provide X-WAP-Network-Client-MSISDN header to http server/MMSC. Instead
I see that it transfers X-WAP-Network-Client-IP.
Here is debug log:
2003-06-20 11:47:37 [1] INFO: RADIUS: Got data from NAS edited:1646
huangcy wrote:
hi,list:
when will kannel support wap2.0?
now that's a good question ;)
I guess this depends on how many people there are outside using Kannel
and want to contribute as module maintainer. Which means people that
pick up a certain issue (like Aarno does for PPG) and provide
Stipe,
Could you please look at my debug output?
Radius proxy gets msisdn fro nas correctly, but doesn't include MSISDN
header.
David Chkhartishvili wrote:
Hi List,
I've just tried to use MSISDN feature of kannel. Seems like it doesn't
provide X-WAP-Network-Client-MSISDN header to http
David Chkhartishvili schrieb:
Stipe,
Could you please look at my debug output?
Radius proxy gets msisdn fro nas correctly, but doesn't include MSISDN
header.
yes, I'll check. Stay tuned...
Stipe
[EMAIL PROTECTED]
---
Wapme
Stipe,
Here is debug log from cisco:
16w0d: Attribute 4 6 D53D3A8C
16w0d: Attribute 5 6 0017
16w0d: Attribute 61 6 0004
16w0d: Attribute 1 5 7761701E
16w0d: Attribute 30 5 3532311F
16w0d: Attribute 31 10 39393138
16w0d: Attribute 2
the problem is that your NAS does not deliver an 'Framed-IP-Address'
attribute within the acct packet, hence the folllowing inside
radius/radius_acct.c:update_tables():
My experience is that the RADIUS attribute that contains the information
that the WAP gateway needs (ie. MSISDN) varies
wapbox.log:
2003-06-20 18:11:51 [1] DEBUG: Octet string at 0x81616c8:
2003-06-20 18:11:51 [1] DEBUG: len: 98
2003-06-20 18:11:51 [1] DEBUG: size: 99
2003-06-20 18:11:51 [1] DEBUG: immutable: 0
2003-06-20 18:11:51 [1] DEBUG: data: 04 9c 00 62 52 15 df 60 ...bR..`
2003-06-20 18:11:51 [1]
I forgot to mention that I'm using Cistron Radius ;-) , please let me
know if it might be issue.
Paul Keogh wrote:
hmmm, ok, that would be an issue.
But in the log David provided there was no client IP, even not under
different attribute name.
Then you must ask the NAS administrator to
Hi list,
I just commited this to cvs:
2003-06-20 Stipe Tolj [EMAIL PROTECTED]
* Makefile.in: added compilation of RADIUS related files inside
radius/.
* doc/userguide/userguide.xml: new MSISDN provisioning section
describing
the use of the RADIUS accounting proxy thread.
*
