<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote>
If you look at main/manager.c, AMI is using the security events
framework.
AMI generates security events. Then you have
res/res_security_log.c, that
acts upon the events by logging them to a file. You can turn on
the file
log by using the level of "security" in the logger.conf.
By having chan_sip generate security events, any module written
for Asterisk
will be able to act upon those events in whichever way you see
fit.<br>
<br>
I have posted a patch to the issue tracker:
<a class="moz-txt-link-freetext" href="https://issues.asterisk.org/jira/browse/ASTERISK-18264">https://issues.asterisk.org/jira/browse/ASTERISK-18264</a>
The reviewboard link is listed on that issue.
Michael
(elguero) <br>
</blockquote>
Thanks Michael. It looks like your patch does what I need to hook
into the events needed. I will be out of town for a couple weeks,
and when I get back, I will generate a patch for Asterisk 1.4.X and
1.6.X (just the verbose hook) and modify my module to receive your
security events and act on them. I think what you have done is all
that is needed to get into the next Asterisk 10 beta release. My
Asterisk 1.8 and greater module will not need any additional patch
to work.<br>
<br>
Thanks,<br>
<br>
Mike<br>
<br>
</body>
</html>