[prev in list] [next in list] [prev in thread] [next in thread]
List: cisco-voip
Subject: Re: [cisco-voip] Excluding extensions from CDR reporting
From: "Hames, Joel" <jhames () tamdistrict ! org>
Date: 2007-12-27 19:48:50
Message-ID: C20E7A2C14F03F4E92C350A986E0839803DB51BD () tammail ! tuhsd ! edu
[Download RAW message or body]
Thinking about this more, I do want VM information in my call accounting
reporting. But I also want the option to filter these extensions out so
that I can get meaningful non-VM voice traffic reporting. I will pursue
this more with the call accounting software provider. Thanks for the
clarification, everyone.
Joel Hames
Senior Director, Information Technology
Tamalpais Union High School District
jhames@tamdistrict.org
From: Scott Voll [mailto:svoll.voip@gmail.com]
Sent: Thursday, December 27, 2007 10:57 AM
To: Hames, Joel
Cc: Wes Sisk; Cisco VoIP
Subject: Re: [cisco-voip] Excluding extensions from CDR reporting
if your using CER then 911 should not be an issue as it takes all the
911 calls and you don't really have a 911 or 9.911 route pattern.
on the other note. Are you sure you don't want the VM data. people
from outside still get VM if no one is there and there for I would see
this as needed info.
What are you doing with the reporting software that you don't what VM?
Scott
On Dec 27, 2007 10:41 AM, Hames, Joel <jhames@tamdistrict.org> wrote:
Thanks for the clarification and I apologize for the vagueness of the
example. We are seeing both calls to our voicemail extension (2000) and
to the MWI extensions (2090 and 2091). We recently disabled reporting
for zero duration calls, but your point is well taken regarding 911
hangups. I'll check with our implementer to see if our Emergency
Responder installation will help offset this loss of detail. As for the
voicemail extension itself (2000) that is logging all calls transferred
to VM, I'll work with RSI again to see what they can do to help filter
out this information for reporting.
Joel Hames
Senior Director, Information Technology
Tamalpais Union High School District
jhames@tamdistrict.org
-----Original Message-----
From: Wes Sisk [mailto:wsisk@cisco.com]
Sent: Thursday, December 27, 2007 10:32 AM
To: Hames, Joel
Cc: Cisco VoIP
Subject: Re: [cisco-voip] Excluding extensions from CDR reporting
The verbiage provided is vague but i'm going to assume that CDR's for
MWI calls are the crux of the issue. Those have been an issue before
and are certainly numerous enough to skew reporting.
The way CM is implemented Voicemail and the associated MWI transactions
are calls. You can set CM service parameter "CDR log calls with zero
duration" to false so that CM does not record CDR for MWI. However, you
risk losing CDR for other critical calls such as misdials/hangups to 911
where the caller hangs up before 911 service answers. Most 911
districts consider these prank calls with a quota and begin charging.
Otherwise, no, there is no way to filter these calls from CDR. The
system dumps out CDR's of all calls. Parsing, filtering, and
correlating are the job of the "Call Accounting and Reporting" package.
Just as Cisco generates the CDR flat files, RSI has to parse and import
every CDR flat file. They have equal opportunity to filter these
requests. As a bonus, RSI can do it without contending for
CPU/Memory/DiskIO that would otherwise be used for processing your
actual calls. It's a rather classic example of production vs.
reporting.
/Wes
Hames, Joel wrote:
> We have a new CCM5.1 installation, so I may ask a few basic questions
as
> we work through our first deployment. At the moment, we have
> implemented RSI's Call Accounting system and have noticed that our
> voicemail extension skews all of our reports significantly. RSI
claims
> that this is a Cisco configuration issue and that calls to that
> extension should not be passed to the call accounting system. Our
> installer claims that there is no way to filter out reporting to
certain
> extensions.
>
> Does anyone have experience with this? While we can certainly ignore
the
> reports of calls inbound and outbound to that extension, I'd like to
> clean this up as much as possible. The graphs of call lengths and
call
> costs would be much more meaningful without extraneous information
like
> this.
>
> Thank you,
>
> Joel Hames
> Senior Director, Information Technology
> Tamalpais Union High School District
> jhames@tamdistrict.org
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thinking about this more, I do want VM information in my call
accounting reporting. But I also want the option to filter these
extensions out so that I can get meaningful non-VM voice traffic
reporting. I will pursue this more with the call accounting software
provider. Thanks for the clarification, everyone.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Joel Hames</span><span style='color:#1F497D'> <br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Senior Director, Information Technology</span><span
style='color:#1F497D'> <br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Tamalpais Union High School District</span><span
style='color:#1F497D'> <br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>jhames@tamdistrict.org</span><span style='color:#1F497D'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Scott Voll \
[mailto:svoll.voip@gmail.com] <br> <b>Sent:</b> Thursday, December 27, 2007 10:57 \
AM<br> <b>To:</b> Hames, Joel<br>
<b>Cc:</b> Wes Sisk; Cisco VoIP<br>
<b>Subject:</b> Re: [cisco-voip] Excluding extensions from CDR \
reporting<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>if your using CER then 911 should not be an issue as it
takes all the 911 calls and you don't really have a 911 or 9.911 route \
pattern.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>on the other note. Are you sure you don't want the VM
data. people from outside still get VM if no one is there and there for I
would see this as needed info.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>What are you doing with the reporting software that you
don't what VM?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Scott<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>On Dec 27, 2007 10:41 AM, Hames, Joel <<a
href="mailto:jhames@tamdistrict.org">jhames@tamdistrict.org</a>> \
wrote:<o:p></o:p></p>
<p class=MsoNormal>Thanks for the clarification and I apologize for the
vagueness of the<br>
example. We are seeing both calls to our voicemail extension (2000) and <br>
to the MWI extensions (2090 and 2091). We recently disabled reporting<br>
for zero duration calls, but your point is well taken regarding 911<br>
hangups. I'll check with our implementer to see if our Emergency<br>
Responder installation will help offset this loss of detail. As for the<br>
voicemail extension itself (2000) that is logging all calls transferred<br>
to VM, I'll work with RSI again to see what they can do to help filter <br>
out this information for reporting.<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Joel Hames<br>
Senior Director, Information Technology<br>
Tamalpais Union High School District<br>
<a href="mailto:jhames@tamdistrict.org">jhames@tamdistrict.org</a><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>-----Original Message-----<br>
From: Wes Sisk [mailto:<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>]<br>
Sent: Thursday, December 27, 2007 10:32 AM<br>
To: Hames, Joel<br>
Cc: Cisco VoIP<br>
Subject: Re: [cisco-voip] Excluding extensions from CDR reporting <br>
<br>
The verbiage provided is vague but i'm going to assume that CDR's for<br>
MWI calls are the crux of the issue. Those have been an issue before<br>
and are certainly numerous enough to skew reporting.<br>
<br>
The way CM is implemented Voicemail and the associated MWI transactions<br>
are calls. You can set CM service parameter "CDR log calls with zero<br>
duration" to false so that CM does not record CDR for MWI. However,
you <br>
<br>
risk losing CDR for other critical calls such as misdials/hangups to 911<br>
<br>
where the caller hangs up before 911 service answers. Most 911<br>
districts consider these prank calls with a quota and begin charging. <br>
<br>
Otherwise, no, there is no way to filter these calls from CDR. The<br>
system dumps out CDR's of all calls. Parsing, filtering, and<br>
correlating are the job of the "Call Accounting and Reporting"
package. <br>
<br>
Just as Cisco generates the CDR flat files, RSI has to parse and import<br>
every CDR flat file. They have equal opportunity to filter these<br>
requests. As a bonus, RSI can do it without contending for<br>
CPU/Memory/DiskIO that would otherwise be used for processing your <br>
actual calls. It's a rather classic example of production vs.<br>
reporting.<br>
<br>
/Wes<br>
<br>
Hames, Joel wrote:<br>
> We have a new CCM5.1 installation, so I may ask a few basic questions<br>
as<br>
> we work through our first deployment. At the moment, we have <br>
> implemented RSI's Call Accounting system and have noticed that our<br>
> voicemail extension skews all of our reports significantly. RSI<br>
claims<br>
> that this is a Cisco configuration issue and that calls to that <br>
> extension should not be passed to the call accounting system. Our<br>
> installer claims that there is no way to filter out reporting to<br>
certain<br>
> extensions.<br>
><br>
> Does anyone have experience with this? While we can certainly ignore <br>
the<br>
> reports of calls inbound and outbound to that extension, I'd like to<br>
> clean this up as much as possible. The graphs of call lengths and<br>
call<br>
> costs would be much more meaningful without extraneous information <br>
like<br>
> this.<br>
><br>
> Thank you,<br>
><br>
> Joel Hames<br>
> Senior Director, Information Technology<br>
> Tamalpais Union High School District<br>
> <a href="mailto:jhames@tamdistrict.org">jhames@tamdistrict.org </a><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" \
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic