<html><head></head><body bgcolor="#FFFFFF"><div>I agree. Definitely it is not acceptable. Bouncing service can be a interim solution but not a perm solution. It just show that the product is not stable enough for live deployment. </div><div><br></div><div>Chase them for a patch.<br><br>Sent from my iPhone<div>Pls pardon my fat fingers.</div></div><div><br>On 24 Dec, 2011, at 7:28 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div style="font-family: Verdana; font-size: 10pt; color: #000000">i think many people accepted that reasoning when things were running on Windows, and, in fact, we went to a monthly restart in order to avoid issues. however, with our Unity Connection 7.1, we had it running for almost (if not over) a year before we restarted. if something needs to be restarted every month to work, it really needs to be re-written. if it's Cisco code, they have no excuse. if it's part of the RHEL kernel or underlying service, again, no excuse. they have access to the source code and should make efforts to fix it as responsible members of the open source community.<br><br><br><span><span name="x"></span>---<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 (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Brian Globerman" <<a href="mailto:bgloberman@gmail.com">bgloberman@gmail.com</a>><br><b>To: </b><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><b>Sent: </b>Friday, December 23, 2011 4:31:29 PM<br><b>Subject: </b>[cisco-voip] Restart selected Unity Connection 8.5 services every 700 hours?<br><br>I had a TAC issue several months ago with delays in MWI and message <br>delivery to Exchange. TAC engineer suggested restarting core Unity <br>services after about 700 hours of use to avoid future occurrences of <br>these problems.<br><br>Question: is it common practice to bounce selected services or just <br>reboot server every 700 hours? If the former, which core services <br>should be restarted periodically?<br><br>Thanks,<br>Brian Globerman<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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></body></html>