[cisco-voip] updating calling search space - reset/restart required?

[Lelio Fulgenzi]

Interesting you say that. I would like to change a partition name, but will be co-ordinating this change with a restart of our cluster. I am prompted that a CM restart is required and suspect that this is the CM in the service control web page. I will do that first to ensure calls proceed as quickly as possible since the cluster restart itself takes a while.

The partition I am changing the name of does not contain phones but only a few route patterns for a specific group of phones at one site. It is contained in the CSS assigned to the device.


Lelio
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Java-Clavis-Domus Theorem: The ability to keep your hands on the home keys is inversely
related to the amount of caffeine ingested in the last 30 minutes. 

  ----- Original Message ----- 
  From: Ryan Ratliff 
  To: Lelio Fulgenzi 
  Cc: Cisco Voyp List 
  Sent: Wednesday, March 26, 2008 4:23 PM
  Subject: Re: [cisco-voip] updating calling search space - reset/restart required?


  Ah, then no restarting of anything is necessary.   When we enumerate the pss for a call it's just a pointer to the CSS so when the CSS changes the new pss is automatically used for every call after the update.  


  The same does not hold for changing partitions.  Don't ever change your partition names as it breaks lots of things.   The last time I saw this was 4.1(3) but it broke CFA for all phones in that partition and a cluster reset was necessary to fix it.  



  -Ryan



  On Mar 26, 2008, at 4:20 PM, Lelio Fulgenzi wrote:

  Sorry - I wasn't clear - I'm talking about updating a CSS with new partitions, so not making a DN change, I'm making the change in the CSS configuration page.

  Lelio
  --------------------------------------------------------------------------------
  Lelio Fulgenzi, B.A.
  Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
  (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
  Java-Clavis-Domus Theorem: The ability to keep your hands on the home keys is inversely
  related to the amount of caffeine ingested in the last 30 minutes. 

    ----- Original Message -----
    From: Ryan Ratliff
    To: Lelio Fulgenzi
    Cc: Cisco Voyp List
    Sent: Wednesday, March 26, 2008 4:12 PM
    Subject: Re: [cisco-voip] updating calling search space - reset/restart required?


    CM actually does the restart automatically when you update a line.  You should see the phone display blink when you make a change there and update.


    -Ryan


    On Mar 26, 2008, at 4:11 PM, Lelio Fulgenzi wrote:

    I remember that I used to need to restart/reset devices/lines that used a particular CSS if I made any updates. I believe that with 4.1(3) this is no longer required, i.e. I'm not prompted to reset nor is there a reset button.

    Have people had luck with this, i.e. not having to reset lines/devices after a CSS change?

    Lelio
    --------------------------------------------------------------------------------
    Lelio Fulgenzi, B.A.
    Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
    (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
    Java-Clavis-Domus Theorem: The ability to keep your hands on the home keys is inversely
    related to the amount of caffeine ingested in the last 30 minutes. 

    _______________________________________________
    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/20080326/002447cf/attachment-0001.html