[FYI] RADIOUS accounting proxy commited
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | Wapme Systems AG |
| Message-ID | <[email protected]> |
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. * gwlib/cfg.def: removed properietary groups that are *not* used inside Kannel's tree and added 'radius-acct' group configuration directives. * gw/wap-appl.c, gw/wapbox.c: added RADIUS accounting proxy related calls. * radius/*: added RADIUS accounting proxy implemenation. * test/test_radius_*.c: added some testing applications for the RADIUS routines. which means we have now a real MSISDN provisioning boarded inside Kannel using a RADIUS accounting proxy thread inside wapbox. See user's guide for guidance. It works here at Wapme for some time inside our MMSC implementation, because we pick the 'From' MMS header using the MSISDN provsioning value provided by the WAP gateway (wapbox) directly. The only thing that needs work on is the MD5 shared secret re-computation to ensure NAS and we are having the same shared secret. Usually I'm aware on how this is done, but it seems I can get this right with our Ascend MAX2000 we have here arround. BTW, we used GNU-radius as the RADIUS server back-end for authentication and account packet forwarding. Any help in getting the damn shared secret re-computation done right is highly welcome. Stipe [email protected] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [email protected] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are