[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cisco-voip
Subject:    RE: [cisco-voip] Call failure logging
From:       "Wes Sisk" <wsisk () cisco ! com>
Date:       2004-08-25 17:29:13
Message-ID: ELEMLGDGDBLINAJEIOCLCEBHPDAA.wsisk () cisco ! com
[Download RAW message or body]

Hi Tim,

1. AFAIK it is not possible to log only cdrs for "failed" calls.  AFAIK it
is not possible to log only CDR for gateway calls.  It's all or nothing with
the only difference being "log calls with zero duration".  See the CCM
service parameter help for info on that.

2. CDRs are automagically pruned.  Look under service->service parameters
for the Cisco Database Layer Monitor process you can set the pruning time,
max number of records to maintain etc.

/Wes

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Tim Reimers
Sent: Wednesday, August 25, 2004 12:48 PM
To: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Call failure logging


Thanks Wes---

couple other related questions-

1.
Is is possible to set up CDR to only log failed calls?
or just calls leaving on the PRI?

I don't really need to log all the internal calls..

2.
I've heard that Call Manager 3.34 doesn't clear it's CDR logs by itself-
that you have to 'run' some CDR tool
before that'll happen- is that true, and is there a way to automate
that?

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


> -----Original Message-----
> From: Wes Sisk [mailto:wsisk@cisco.com]
> Sent: Wednesday, August 25, 2004 12:30 PM
> To: Tim Reimers; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] Call failure logging
>
>
> 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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net]On Behalf Of Tim Reimers
> Sent: Tuesday, August 24, 2004 3:17 PM
> To: cisco-voip@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/ci> sco-voip
>
>

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


[prev in list] [next in list] [prev in thread] [next in thread]