<div>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.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>What are you doing with the reporting software that you don't what VM?</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Dec 27, 2007 10:41 AM, Hames, Joel <<a href="mailto:jhames@tamdistrict.org">jhames@tamdistrict.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">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.<br>
<div class="Ih2E3d"><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></div>
<div>
<div></div>
<div class="Wj3C7c">-----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><br></div></div></blockquote></div><br>