RE: [Asterisk-Users] Questions about alarm reporting in Asterisk
At 9:16 PM +0100 on 4/21/04, Fran Boon wrote: On Wed, 2004-04-21 at 18:41, Ernest W. Lessenger wrote: We use a package called Nagios to monitor our servers, which works quite well. It has the ability to track service and host dependencies so you don't get flooded with a bunch of "service down" alerts when the real cause is a bad switch (or similar). Nagios is great :) Here is some basic info on integration with Asterisk: http://www.voip-info.org/tiki-index.php?page=Asterisk+monitoring It would seem logical for someone (hah!) to write a res_snmp.c for asterisk that would expose a lot of asterisk's internal data. This would seem a logical step toward writing fully functional monitoring applications as well. The module would allow clients to add themselves to the list and receive traps, as well as check for the current status of various variables. Okay, this may be over the top, but here goes. Write an asterisk application that sends (and receives) status information to another box over the PSTN. My idea is not only to use this as a way to verify that * is running, but as a way to RELIABLY tell that a remote * box is actively accepting incoming calls. It wouldn't have to be anything complicated, just a heartbeat and some basic details to let the caller know that "yes, I'm alive and accepting calls over this line". Simplified protocol: 1) Monitoring box calls up and says (in DTMF): # 2) The remote box says 3) Monitoring box acknowledges and disconnects 4) Remote box disconnects 5) Monitoring box decides whether it likes the answers it received and performs actions accordingly. Great stuff - I've added this & the other comments to the Wiki page :) - please keep adding stuff there as it's an important area where we could benefit from sharing ideas (& implementations!) F There is an SNMP module for Asterisk already, but it is apparently not widely used. I've added this to the Wiki as well in response to questions about SNMP for Asterisk: http://www.faino.it/en/ast-ax-snmpd.html I took a look through this code, and it seemed to have quite a few nice things that could easily be monitored through the interface provided. Instead of traps (yuck!) it allows polls, which could then be graphed with RRDTool or monitored with Nagios easily enough... Lots of work yet to be done on it, I'm sure, but I'm sure there are good coders out there who could submit patches and updates to it. If I had time I'd implement SNMPv3 into all my * servers for monitoring... JT ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Questions about alarm reporting in Asterisk
On Wed, 2004-04-21 at 18:41, Ernest W. Lessenger wrote: > We use a package called Nagios to monitor our servers, which works quite > well. It has the ability to track service and host dependencies so you don't > get flooded with a bunch of "service down" alerts when the real cause is a > bad switch (or similar). Nagios is great :) Here is some basic info on integration with Asterisk: http://www.voip-info.org/tiki-index.php?page=Asterisk+monitoring > It would seem logical for someone (hah!) to write a res_snmp.c for asterisk > that would expose a lot of asterisk's internal data. This would seem a > logical step toward writing fully functional monitoring applications as > well. The module would allow clients to add themselves to the list and > receive traps, as well as check for the current status of various variables. > > Okay, this may be over the top, but here goes. Write an asterisk application > that sends (and receives) status information to another box over the PSTN. > My idea is not only to use this as a way to verify that * is running, but as > a way to RELIABLY tell that a remote * box is actively accepting incoming > calls. It wouldn't have to be anything complicated, just a heartbeat and > some basic details to let the caller know that "yes, I'm alive and accepting > calls over this line". > Simplified protocol: > 1) Monitoring box calls up and says (in DTMF): > ### reply in DTMF instead of voice>## > 2) The remote box says > ### number># > 3) Monitoring box acknowledges and disconnects > 4) Remote box disconnects > 5) Monitoring box decides whether it likes the answers it received and > performs actions accordingly. > Great stuff - I've added this & the other comments to the Wiki page :) - please keep adding stuff there as it's an important area where we could benefit from sharing ideas (& implementations!) F ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Questions about alarm reporting in Asterisk
> I'm interested in hearing success stories in tying things like Asterisk > YELLOW > and RED alarms and network problems into a central alarm reporting solution. > > The most common problems that I have found are: > 1. Someone unplugs a X100P from the Dmarc and nobody knows until people > complain that calls are not coming in. > 2. A network span goes down and nobody knows until they can't send or > receive > calls on that span. > > Here are some ideas that I have thought about so far: > 1. Installing a basic SNMP agent on each Linux box and using a central SNMP > manager to monitor each node. This would give notice when a remote > node became > isolated from the monitoring network. > 2. Rolling in Asterisk alarm logs into a syslog server or even as SNMP > traps. > > Any good ideas would be appreciated! There are lots of different ways to sense problems including those you've mentioned. Others include: - writing a small app that simply interrogates those interfaces that are important to the operation (iax2/udp, sip/udp, etc, send a crafted pkt and interpret the returned result. Port not open is obvious, no response is obvious, incorrect response is not so obvious) - test call to an outside number once per five minutes, hourly, or whatever trips your trigger (outside number only needs to respond with something that is predictable, doesn't have to be a person or company) - monitoring logs looking for keywords (may take some time to identify the appropriate keywords) There are open source apps available that already address some of those, but weren't written specifically for *. Rich ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Questions about alarm reporting in Asterisk
> Any good ideas would be appreciated! We use a package called Nagios to monitor our servers, which works quite well. It has the ability to track service and host dependencies so you don't get flooded with a bunch of "service down" alerts when the real cause is a bad switch (or similar). It would seem logical for someone (hah!) to write a res_snmp.c for asterisk that would expose a lot of asterisk's internal data. This would seem a logical step toward writing fully functional monitoring applications as well. The module would allow clients to add themselves to the list and receive traps, as well as check for the current status of various variables. Okay, this may be over the top, but here goes. Write an asterisk application that sends (and receives) status information to another box over the PSTN. My idea is not only to use this as a way to verify that * is running, but as a way to RELIABLY tell that a remote * box is actively accepting incoming calls. It wouldn't have to be anything complicated, just a heartbeat and some basic details to let the caller know that "yes, I'm alive and accepting calls over this line". Simplified protocol: 1) Monitoring box calls up and says (in DTMF): # 2) The remote box says 3) Monitoring box acknowledges and disconnects 4) Remote box disconnects 5) Monitoring box decides whether it likes the answers it received and performs actions accordingly. --Ernest > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Clif Jones > Sent: Wednesday, April 21, 2004 10:16 AM > To: asterisk users > Subject: [Asterisk-Users] Questions about alarm reporting in Asterisk > > I am currently helping a friend build an Asterisk PBX that spans > several cities using anything from T1s to DSL connections to > link remote SIP phones, IAX gateways, etc. to a central Asterisk > PBX server that serves up voicemail, features, etc. The > biggest problem > that I have had with this system appears to be the leading > problem that > my day job company finds with their VOIP deployments: Most common > problems are on the infrastructure network but are reported > as "phone system > problems" because that is the piece that the customer > directly interacts > with. > I'm interested in hearing success stories in tying things > like Asterisk > YELLOW > and RED alarms and network problems into a central alarm > reporting solution. > > The most common problems that I have found are: > 1. Someone unplugs a X100P from the Dmarc and nobody knows > until people > complain that calls are not coming in. > 2. A network span goes down and nobody knows until they can't send or > receive > calls on that span. > > Here are some ideas that I have thought about so far: > 1. Installing a basic SNMP agent on each Linux box and using > a central SNMP > manager to monitor each node. This would give notice > when a remote > node became > isolated from the monitoring network. > 2. Rolling in Asterisk alarm logs into a syslog server or > even as SNMP > traps. > > Any good ideas would be appreciated! > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Questions about alarm reporting in Asterisk
On Wed, 21 Apr 2004, Clif Jones wrote: > I am currently helping a friend build an Asterisk PBX that spans > several cities using anything from T1s to DSL connections to > link remote SIP phones, IAX gateways, etc. to a central Asterisk > PBX server that serves up voicemail, features, etc. The biggest problem > that I have had with this system appears to be the leading problem that > my day job company finds with their VOIP deployments: Most common > problems are on the infrastructure network but are reported as "phone system > problems" because that is the piece that the customer directly interacts > with. > I'm interested in hearing success stories in tying things like Asterisk > YELLOW > and RED alarms and network problems into a central alarm reporting solution. > > The most common problems that I have found are: > 1. Someone unplugs a X100P from the Dmarc and nobody knows until people > complain that calls are not coming in. > 2. A network span goes down and nobody knows until they can't send or > receive > calls on that span. > > Here are some ideas that I have thought about so far: > 1. Installing a basic SNMP agent on each Linux box and using a central SNMP > manager to monitor each node. This would give notice when a remote > node became > isolated from the monitoring network. > 2. Rolling in Asterisk alarm logs into a syslog server or even as SNMP > traps. > The manager interface sends events when a channel/span goes into alarm. A simple app collecting this data should be able to handle this for you James ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Questions about alarm reporting in Asterisk
I am currently helping a friend build an Asterisk PBX that spans several cities using anything from T1s to DSL connections to link remote SIP phones, IAX gateways, etc. to a central Asterisk PBX server that serves up voicemail, features, etc. The biggest problem that I have had with this system appears to be the leading problem that my day job company finds with their VOIP deployments: Most common problems are on the infrastructure network but are reported as "phone system problems" because that is the piece that the customer directly interacts with. I'm interested in hearing success stories in tying things like Asterisk YELLOW and RED alarms and network problems into a central alarm reporting solution. The most common problems that I have found are: 1. Someone unplugs a X100P from the Dmarc and nobody knows until people complain that calls are not coming in. 2. A network span goes down and nobody knows until they can't send or receive calls on that span. Here are some ideas that I have thought about so far: 1. Installing a basic SNMP agent on each Linux box and using a central SNMP manager to monitor each node. This would give notice when a remote node became isolated from the monitoring network. 2. Rolling in Asterisk alarm logs into a syslog server or even as SNMP traps. Any good ideas would be appreciated! ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
