<div dir="ltr"><div>I reset the repository manager service and all seems to be working as expected.</div><div> </div><div>I think the disconnect was with the billing server vendor. They didn't realize we have 2 clusters sending to the same FTP directory.</div>
<div> </div><div>Thanks for the guidance!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 4:56 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:verdana,helvetica,sans-serif;font-size:10pt">I've found changing the CDR time is a bit of a pain. I've not had much experience with v9 though, only v7 (v9 is two weeks away!).<br>
<br>Typically I make the change. Then I reset the external billing key. Then restart the Cisco CDR Repository Manager service. Usually it fixes itself.<br><br><br><br><div><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>
Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><br><a href="tel:519%E2%80%90824%E2%80%904120%20Ext%2056354" target="_blank" value="+15198244120">519‐824‐4120 Ext 56354</a><br>
<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br><a href="http://www.uoguelph.ca/ccs" target="_blank">www.uoguelph.ca/ccs</a><br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span name="x"></span><br>
</div><br><hr><div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;font-style:normal;font-weight:normal;text-decoration:none"><b>From: </b>"Erick Wellnitz" <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>><br>
<b>To: </b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br><b>Cc: </b>"cisco-voip" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Sent: </b>Monday, April 14, 2014 5:46:37 PM<br><b>Subject: </b>Re: [cisco-voip] file size sent to billing server<br><br><div dir="ltr"><div>I set that parameter to 5 minutes but it seems to be sending every 2 minutes. At 1 minute it sent every 30 seconds.</div>
<div> </div><div> </div><div>Do I need to do a reset or restart services for it to take effect?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 4:39 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div><div style="font-family:verdana,helvetica,sans-serif;font-size:10pt">
<br>Are we talking about CDRs? It's an Enterprise parameter that sets the number of minutes to send files.<br>
<br><hr><a name="145623d85919fa6a_145622df656a429e_CDRFlatFileInterval">
<label><b>CDR File Time Interval:</b>
<img alt="Required Field" src="https://iptccm71ft.cs.uoguelph.ca/ccmadmin/themes/VtgBlaf/required.gif">
</label>
</a>
This parameter specifies the time interval for collecting CDR data.
For example, if this value is set to 1, each file will contain 1 minute
of CDR data (CDRs and CMRs, if enabled). The CDR database will not
receive the data in each file until the interval has expired, so
consider how quickly you want access to the CDR data when you decide
what interval to set in this parameter. For example, setting this
parameter to 60 means that each file will contain 60 minutes worth of
data, but that data will not be available until the 60-minute period has
elapsed and the records are written to the CDR database.
This is a required field.
Default:
1
Minimum:
1
Maximum:
1440
Unit:
min
<hr><br><div><span></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst, Network Infrastructure<br>Computing and Communications Services (CCS)<br>University of Guelph<br><br><a href="tel:519%E2%80%90824%E2%80%904120%20Ext%2056354" target="_blank">519‐824‐4120 Ext 56354</a><br>
<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br><a href="http://www.uoguelph.ca/ccs" target="_blank">www.uoguelph.ca/ccs</a><br>Room 037, Animal Science and Nutrition Building<br>Guelph, Ontario, N1G 2W1<span></span><br>
</div><br><hr><div style="font-family:Helvetica,Arial,sans-serif;font-size:12pt;font-style:normal;font-weight:normal;text-decoration:none"><b>From: </b>"Erick Wellnitz" <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>><br>
<b>To: </b>"cisco-voip" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br><b>Sent: </b>Monday, April 14, 2014 5:28:34 PM<br><b>Subject: </b>[cisco-voip] file size sent to billing server<br>
<br><div dir="ltr"><div>Hopefully this is something I'm just overlooking.</div><div> </div><div>Is there a way to increase the size of the files sent via FTP to an external billing server? </div><div> </div><div>CM 9.1.2</div>
</div>
<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">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><br></div></div></blockquote></div><br></div>
</div><br></div></div></blockquote></div><br></div>