[cisco-voip] Monitoring H323 Gateways

[lelio at uoguelph.ca]

Syslog and SEC Tool is your best bet. SEC (or Simple Event Corelator)  
will buffer an alert for a period of time, say five minutes, and  
either ignore it or send you a down/up error. Or if no "interface up"  
message is received after five minutes, an interface down message is  
sent.

Lelio Fulgenzi, Senior Analyst
Computing & Communications
University of Guelph
519-824-4120 x56354

...sent from my iPod - please pardon my fat fingers ;)

[XKJ2000]

On 2009-11-29, at 9:12 AM, Chris Hill <chrishill.work at gmail.com> wrote:

>
> Hi All,
>
> 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.
> But to of the PRIs did not come back, had to bounce the interface to  
> get them back.
>
> 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.
>
> I would like to know a way can monitor these PRIs. These PRIs are  
> only used for incoming 1800 calls.
>
> Can a syslog server be configured to send out emails based on isdn  
> debug data?
>
> Any suggestions?
>
> Thanks
>
> Chris Hill - CCNA, CCNA Voice, CCVP
> chrishill.work at gmail.com
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip