<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=utf-8">
<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;}
@font-face
{font-family:Verdana;
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;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</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=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I had double checked that CDR’s were enabled on all our call
processing servers. We don’t log zero length CDRs yet, but the call in question
was several hours, so it should be in the data. I’ve had a few other reports of
incidents like this, but have always written them off as user error (aka the
call didn’t happen), now I feel like a jerk.<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>
<div>
<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"'> Lelio Fulgenzi
[mailto:lelio@uoguelph.ca] <br>
<b>Sent:</b> Monday, July 19, 2010 3:28 PM<br>
<b>To:</b> Ahmed Elnagar<br>
<b>Cc:</b> cisco-voip; Fuermann, Jason<br>
<b>Subject:</b> Re: [cisco-voip] Missing CDR data<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>That, and you might want to check off "zero length" CDRs
as well. We find that very useful in troubleshooting.<br>
<br>
It adds quite a bit of data, but it's worth it. Being able to
troubleshoot with historical data.<br>
<br>
<br>
<br>
---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<br>
<br>
----- Original Message -----<br>
From: "Ahmed Elnagar" <ahmed_elnagar@rayacorp.com><br>
To: "Jason Fuermann" <JBF005@shsu.edu><br>
Cc: "cisco-voip" <cisco-voip@puck.nether.net><br>
Sent: Monday, July 19, 2010 4:30:06 PM GMT -05:00 US/Canada Eastern<br>
Subject: Re: [cisco-voip] Missing CDR data<br>
<br>
although very trivial but a lot of times it is been forgotten :)<br>
Make sure that CDR enabled flag is enabled on all call processing servers
"it is not a cluster wide parameter"<br>
<br>
Best Regards;<br>
Ahmed Elnagar<br>
Senior Network PS Engineer<br>
Mob: +2019-0016211<br>
CCIE#24697 (Voice)<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Fuermann, Jason<br>
Sent: Monday, July 19, 2010 6:30 PM<br>
To: cisco-voip<br>
Subject: [cisco-voip] Missing CDR data<br>
<br>
CM 7.0.2<br>
Is anybody aware of a CDR bug where UCM fails to generate CDR data for calls? I
found CSCsk76737, but I wasn't logging at the info or debug level for the
scheduler, so I check if that's the problem. Anything else anybody knows of?<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
Disclaimer: NOTICE The information contained in this message is confidential
and is intended for the addressee(s) only. If you have received this message in
error or there are any problems please notify the originator immediately. The
unauthorized use, disclosure, copying or alteration of this message is strictly
forbidden. Raya will not be liable for direct, special, indirect or
consequential damages arising from alteration of the contents of this message
by a third party or as a result of any malicious code or virus being passed on.
Views expressed in this communication are not necessarily those of Raya.If you
have received this message in error, please notify the sender immediately by
email, facsimile or telephone and return and/or destroy the original message. <br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></span></p>
</div>
</div>
</body>
</html>