Hello again, :)
I have taken the work done by http://www.faino.it/en/asterisk.html and
extended it to support SNMP querying of the ZAP alarm states. I have
also made it NOT introduce delay and jitter into the Zap channels under
SNMP querying. I have also made it build on STABLE 1.0.9. As soon as I
have finished some code clean-up and write some good documentation, I
will be posting it on my website (along with other stuff I've got for
download there.)
http://www.UglyBoxIndustries.com/
If anyone has any comments, suggestions, ideas for inclusion in to the
SNMP module, let me know. I am by default building it as a listening
SNMP server, so that the main SNMPD is not required. I am choosing this
route as I want to ensure the least number of services must run on any
given Asterisk system.
-Joseph Benden
Joseph Benden wrote:
Hello,
There are a few tools to monitor SIP and IAX2 protocol communications,
and there is one SNMP module for monitoring channel information
(http://www.faino.it/en/asterisk.html which doesn't compile right on
CentOS BTW); however, what I'm wanting to know peoples thoughts on are:
What about if I wrote a module that gave SNMP answers for Zap span
alarms? (Think about having the output available from ZTTOOL)
My thinking is that by doing this, we're able to page ourselves if
SNMP isn't answering (ahhhh, the box is dead!) and we'll know if
T1/E1s go into alarm states. This in combination with existing tools
to monitor SIP and IAX2 should give us the full picture if Asterisk is
alive and well, right?
What's everyone's thoughts? Would this solve the problem?
Thanks,
-Joseph Benden
http://www.UglyBoxIndustries.com/
_______________________________________________
Asterisk-Biz mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-biz
_______________________________________________
Asterisk-Biz mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-biz
