>James,
>
>Very clever!
>
>It probably is a little too convoluted, but if the dialplan contained:
>--
>exten => _.,n,Set(BLKIP1=${CUT(CHANNEL,\/,2)})
>exten => _.,n,Set(BLKIP2=${CUT(BLKIP1,\-,1)})
>exten => _.,n,Log(NOTICE,\'${BLKIP2}\' - Dialplan Ban IP Address)
>--
>it would generate the log
>--
>May 17 18:55:14 pbx local0.notice asterisk[30186]: NOTICE[30186]:
>Ext. s:5 in @ default: '10.10.50.1' - Dialplan Ban IP Address
>--
>Then the AIF adaptive-ban plugin could be tweaked to have support
>for that forced syslog string.
>
>Lonnie
I think it would be a good idea to add this to the adaptive ban
plugin (maybe with an example snippet).
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
