[cisco-voip] CCM Reboot Times

[Lelio Fulgenzi]

The biggest issue for us was forwarding. That can usually be fixed by bouncing the dbl service, in the worst case, a restart of the cluster is needed.

If you have a true voice/data integration, something you have to think about is the monthly O/S updates that happen. You'll want to keep those up to date, so it makes sense to do monthly maintenance windows. Usually a restart is not noticed by people, as calls in progress are not interrupted and phone registration is pretty quick to backup subscribers.

  ----- Original Message ----- 
  From: Todd Franklin 
  To: cisco-voip at puck.nether.net 
  Sent: Monday, August 07, 2006 1:53 PM
  Subject: Re: [cisco-voip] CCM Reboot Times


  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?? 

  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! 





------------------------------------------------------------------------------


  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060807/09cb18e7/attachment.html