[cisco-voip] Disaster Recovery Plan CUCM 7.1

[Ryan Ratliff]

You can also call into TAC or open an SR on the web.  There is a dedicated team for licensing that handles these SRs.  Just make sure to pick a licensing problem code so it's routed correctly.

-Ryan

On Feb 2, 2010, at 10:29 AM, Lelio Fulgenzi wrote:

you have to send a request to rehost the license to licensing at cisco.com. 

they are apparrently watching email 24 hours a day and should respond within the hour. not sure if that's an official SLA or not though.



---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it. 
                              - LFJ (with apologies to Mr. Popeil)


----- Original Message -----
From: "Reto Gassmann" <voip at mrga.ch>
To: cisco-voip at puck.nether.net
Sent: Tuesday, February 2, 2010 10:23:49 AM GMT -05:00 US/Canada Eastern
Subject: [cisco-voip] Disaster Recovery Plan CUCM 7.1

Hello group
 
we are working on a disaster plan for our CUCM 7.1 Cluster. We operate our cluster in two locations.
If we have to rebuild the publisher, we have a spare hardware server, install the CUCM Software and restore the backup from the SFTP backup server.
 
However, how do I license this server, and how fast do I get the new license for the rebuilt publisher?
Are there any documents describing the steps to rebuild a publisher with the licensing steps?
 
Thanks Reto

_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
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/20100202/00ac6389/attachment.html>