[cisco-voip] live updates on subscriber - anyone tried it?

[Lelio Fulgenzi]

Thanks Wes. I wasn't sure about the service parameter because it talked about 'higher order' CallManager. In my case, when I turn off callmanager service, the phone is actually going to a lower order callmanager.
  ----- Original Message ----- 
  From: Wes Sisk 
  To: Lelio Fulgenzi 
  Cc: cisco-voip at puck.nether.net 
  Sent: Tuesday, July 18, 2006 9:20 PM
  Subject: Re: [cisco-voip] live updates on subscriber - anyone tried it?


  Stop CTIManager as well - it actually has a default hook into the local ccm.exe.  If you have an CTI apps using CTIManager this will force them to roll over to another CTI Manager and avoid a 2nd interruption.


  Yes.  CSCea71523
  Symptom:
  The actual function MaxStationsInitPerSecond parameter is somewhat 
  misleading - has nothing to do with "time".


  Condition:
  Normal operation.


  Workaround:
  None, but request this parameter be renamed to something like:


  MaxPhonesFallbackQueueDepth




  Online Help Suggestion:


  The maximum number of phone registrations a 
  higher order CallManager queues at one time.  


  When a phone determines that a higher-priority 
  CallManager is available, it sends a registration 
  request.  Once acknowledged, the phone will 
  immediately unregister on the lower-priority 
  CallManager and a registration request is placed 
  in the queue of the higher-priority CallManager.  


  A phone is unregistered for the amount of time 
  it takes the higher-priority CallManager to 
  process the queued registration request.


  Furhter: This service parameter defines the number of signals
  that StationInit process can handle at a particular time slice. So it not only controls
  registration requests it will also control things like number of simultaneous
  offhooks that may recevied by the CallManager. 


  /Wes


  On Jul 18, 2006, at 12:30 PM, Lelio Fulgenzi wrote:


  Just wondering if anyone has tried updating the O/S on a subscriber during business hours, obviously after stopping the CallManager service and forcing phones to register to another subscriber first. Our goal is to try an minimize the amount of after hours work that is involved in maintaining this new fancy system of ours. 

  Ideally, we'd see the following happening:
    a.. stop callmanager services and have phones register to another subscriber during a short maintenance window 
    b.. update O/S during the day 
    c.. start callmanager services during a short maintenance window
  Some questions:
    a.. are there any other services we should stop to make this as transparent as possible? 
    b.. does the Maximum Phone Fallback Queue Depth service parameter help in any way in getting phones to register quicker on the next callmanager in line?
  Any comments would be extremely welcome.

  --------------------------------------------------------------------------------
  Lelio Fulgenzi, B.A.
  Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
  (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
  "I can eat fifty eggs." "Nobody can eat fifty eggs."
  _______________________________________________
  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/20060718/779cf6d9/attachment.html