Well, I think generally the reboots are to help clean up systems level problems rather than specific features breaking.<br><br>One specific case though with us has been call forward all getting upset and not letting users forward/un-forward their lines. I've been told from several different places that a reboot helps fix this, and I've had tac actually tell me to consider a regular reboot even if no patches are needed.. to help preventing that type of problem.
<br><br><div><span class="gmail_quote">On 8/7/06, <b class="gmail_sendername">Todd Franklin</b> <<a href="mailto:toddnh65@gmail.com">toddnh65@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Getting some very interesting answers, although the norm seems to be once a month "to fix many issues." Just curious, what sorts of issues do you see, does the system start to lose functionality (unable to transfer a call) or even weirder, like do calls mean for extension B start routing to extension A??
<br><br>As far as reliability comparison goes to traditional PBX, I do have one site that must be run 24/7. So a CCM reboot is going to affect them no matter how I slice it. We never had to reboot the other traditional PBX. I can certainly live with once a month though!
<br><br><br>
</div><br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br></blockquote></div><br>
<br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations