[cisco-voip] Call failure logging

[Wes Sisk]

Best bet is to monitor CDR database for abnormal call teardown reasons.  The
reasons follow standard q931 reasons.

/Wes

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Tim Reimers
Sent: Tuesday, August 24, 2004 3:17 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Call failure logging



Hi everyone-

I'm looking for a way to monitor a CM running 3.34 and a 2651 PRI router
(H.323)

What I need to know is when a call has failed- -

After I get a report from a user that their call failed
I can certainly do the usual 'debug isdn q931' and a trace on the CM -

I'm looking for some advance notice of when calls fail - so that my
first hearing of it doesn't have to be from a user that is already
upset...

Is there anything anyone is doing with this?
perhaps SNMP traps or Syslog?

Tim Reimers
Asheville City Schools IT
tim.reimers(at)asheville(dot)k12(dot)nc(dot)us
828-350-6180


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip