Re: [OpenSER-Users] userblacklist

2008-04-29 Thread Helmut Kuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Henning, Henning Westerholt schrieb: | Hello Helmut, | | i thought a little more about this issue, and i just ported your first patch, | without the 'old' interface change. It provides more consistency with the | check_blacklist function. Sorry

Re: [OpenSER-Users] userblacklist

2008-04-28 Thread Henning Westerholt
On Wednesday 23 April 2008, Henning Westerholt wrote: > > ok param 3 (number) is now mandatory. > > > > Param 3 was optional because I thought it would be better to keep old > > syntax instead of forcing existing openser-configurations to be > > reconfigured... > > Thank you Helmut, i'll later take

Re: [OpenSER-Users] userblacklist

2008-04-23 Thread Henning Westerholt
On Wednesday 23 April 2008, Helmut Kuper wrote: > ok param 3 (number) is now mandatory. > > Param 3 was optional because I thought it would be better to keep old > syntax instead of forcing existing openser-configurations to be > reconfigured... Thank you Helmut, i'll later take a look. Well, this

Re: [OpenSER-Users] userblacklist

2008-04-23 Thread Helmut Kuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Err, well a bit sleepy today here ... I forgot the attachment;D ... Hi Henning, ok param 3 (number) is now mandatory. Param 3 was optional because I thought it would be better to keep old syntax instead of forcing existing openser-configu

Re: [OpenSER-Users] userblacklist

2008-04-23 Thread Helmut Kuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Henning, ok param 3 (number) is now mandatory. Param 3 was optional because I thought it would be better to keep old syntax instead of forcing existing openser-configurations to be reconfigured... Param 4 is still optional. I attached a svn dif

Re: [OpenSER-Users] userblacklist

2008-04-23 Thread Henning Westerholt
On Tuesday 22 April 2008, Helmut Kuper wrote: > I enhanced userblacklist module in that way, that check_user_blacklist > function has now 2 additional, but optional, parameters: > > check_user_blacklist(string user, string domain [, string > number_to_check][, string table]) > > Purpose of all this

Re: [OpenSER-Users] userblacklist

2008-04-22 Thread Helmut Kuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I enhanced userblacklist module in that way, that check_user_blacklist function has now 2 additional, but optional, parameters: check_user_blacklist(string user, string domain [, string number_to_check][, string table]) Purpose of all this i

Re: [OpenSER-Users] userblacklist

2008-04-16 Thread Henning Westerholt
On Wednesday 16 April 2008, Helmut Kuper wrote: > so this is a confirmation from you for coding the enhancement? ;) Hi Helmut, well.. not exactly. ;-) I've not that much time for enhancements like this at the moment, unfortunally. I thought that you perhaps want to contribute a patch. ;-) Chee

Re: [OpenSER-Users] userblacklist

2008-04-16 Thread Helmut Kuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Henning, so this is a confirmation from you for coding the enhancement? ;) regards Helmut [...] | For the user blacklists (check_user_blacklist function) there could be one | more parameter for the table added. This parameter should be optional.

Re: [OpenSER-Users] userblacklist

2008-04-16 Thread Henning Westerholt
On Tuesday 15 April 2008, Helmut Kuper wrote: > is it possible to add a way to userblacklist so that we have two tables > (one for incomming and one for outgoing (user|global)blacklists) ? Hi Helmut, yes, this could be possible. The actual logic is although not designed to this case, for example

[OpenSER-Users] userblacklist

2008-04-15 Thread Helmut Kuper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, is it possible to add a way to userblacklist so that we have two tables (one for incomming and one for outgoing (user|global)blacklists) ? I enhanced userblacklist module following the sledge hammer method (just duplicating the code) so I have n