<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [cisco-voip] Monitoring H323 Gateways</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>heh.<BR>
<BR>
Had I seen this, I'd have posted EEM before you did<BR>
;-)<BR>
<BR>
I'd also have to wonder about the possibilities of kron and a "sh isdn status"<BR>
looking for "multiple frame established"<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: cisco-voip-bounces@puck.nether.net on behalf of Jim McBurnett<BR>
Sent: Sun 11/29/2009 9:15 PM<BR>
To: Chris Hill; cisco-voip@puck.nether.net<BR>
Subject: Re: [cisco-voip] Monitoring H323 Gateways<BR>
<BR>
Guys,<BR>
There are 2 methods I use to configure this for customers:<BR>
1. EEM-- embedded event manager.. <BR>
<A HREF="http://www.cisco.com/en/US/products/ps6815/products_ios_protocol_group_home.html">http://www.cisco.com/en/US/products/ps6815/products_ios_protocol_group_home.html</A><BR>
It can watch syslog and send an email from the router-- <BR>
and even issue commands to the router as a triggered event...<BR>
2. Kiwi syslog..- for those non-Linux types.<BR>
It has a scripting engine where you can do some amazing things.<BR>
www.kiwisyslog.com<BR>
<BR>
Take a gander and see what ideas you can come up with for your needs.....<BR>
<BR>
<BR>
Jim<BR>
<BR>
<BR>
<BR>
>From the EEM datasheet:<BR>
<BR>
<BR>
The applications are endless and only limited by your imagination.<BR>
<BR>
Suppose, for example, you would like to automatically configure a switch interface depending on the device that is connected to a port or interface, an IP phone. A script can be devised that is triggered on the interface up condition and determines the details of the connected device. Upon discovery and verification of a newly connected IP phone, the port can be automatically configured according to prescribed parameters.<BR>
<BR>
Another example might be to react to an abnormal condition such as the detection of a high error rate on an interface by forcing transit traffic over a more stable and error-free path. EEM can watch for the increased error rate and trigger a policy into action. The policy could notify network operations personnel and take immediate action to reroute traffic.<BR>
<BR>
A third example might be to collect detailed data upon detection of a specific failure condition in order to gather information that can allow the root cause of the problem to be determined faster leading to a lower mean time to repair and higher availability. EEM could detect a specific Syslog message and trigger a script to collect detailed data using a series of show commands. After automatically collecting the data, it can be saved to flash memory or sent to an external management system or via email to a network operator.<BR>
<BR>
The control is in the network administrator's hands. You control what events to detect and what actions to take. EEM is optional-it is up to the network administrator if and when it should be used and only takes the actions you program it to take.<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: cisco-voip-bounces@puck.nether.net [<A HREF="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Chris Hill<BR>
Sent: Sunday, November 29, 2009 9:12 AM<BR>
To: cisco-voip@puck.nether.net<BR>
Subject: [cisco-voip] Monitoring H323 Gateways<BR>
<BR>
<BR>
Hi All,<BR>
<BR>
I ran into scenario were we had 2 PRIs down but and all the syslogs had was some netclock errors and the interfaces bouncing. Believe this was caused by a provider issue.<BR>
But to of the PRIs did not come back, had to bounce the interface to get them back.<BR>
<BR>
The only thing that indicated a problem 6 hours after the bounce was when i debugged the isdn q.921 traffic...here i saw the bad frames.<BR>
<BR>
I would like to know a way can monitor these PRIs. These PRIs are only used for incoming 1800 calls.<BR>
<BR>
Can a syslog server be configured to send out emails based on isdn debug data?<BR>
<BR>
Any suggestions?<BR>
<BR>
Thanks<BR>
<BR>
Chris Hill - CCNA, CCNA Voice, CCVP<BR>
chrishill.work@gmail.com<BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>