Re: [PATCH] [CFT] [RFC] [WIP] Next series

2004-05-09 Thread David Chkhartishvili
Paul, Unfortunately I'm not coder, but I can help you by testing your implementations against real traffic. I think it will be great, if coders like you will have dedicated repository based on cvs tree and keep your patchsets up-to-date, just like in linux kernel tree (-aa, -mm and so on serie

Re: [PATCH] [CFT] [RFC] [WIP] Next series

2004-05-08 Thread Paul P Komkoff Jr
Replying to David Chkhartishvili: > I also would like mention, that current radius implementetion not always > working properly. Sometimes we get incorrect mappings and as a result clients > get other clients MSISDN's. That situation is fatal when services are > dependent on MSIDN, for example M

Re: [PATCH] [CFT] [RFC] [WIP] Next series

2004-05-06 Thread David Chkhartishvili
I also would like mention, that current radius implementetion not always working properly. Sometimes we get incorrect mappings and as a result clients get other clients MSISDN's. That situation is fatal when services are dependent on MSIDN, for example MMS. From my point of view, Paul's implemen

[PATCH] [CFT] [RFC] [WIP] Next series

2004-05-06 Thread Paul P Komkoff Jr
OK, next step http://stingr.net/l/kannel-stingr-20040506.tar.bz2 and http://sting.net/l/stingr-20040506.patch.gz (patch to current cvs) So what's up? Here I tried to remove serious limitation. It is a proof-of-concept hack, maybe the direction is totally wrong, but it works. * Preamble Many of us