[cisco-voip] Subject: IP phones in Disaster Recovery Site
Ovidiu Popa
ovidiu at romandie.com
Tue Jun 1 18:53:41 EDT 2010
Many thanks ...
Lots of good suggestions. Now I just need to find the time to test it in
a lab and choose the best solution for my customer.
Thanks again.
Ovidiu
Dennis Heim wrote:
> If you maintain the same phone types (exact model), then you could do an update (SQL) to push the new device names. When DR is to be activated just push the script and your group of phones would be active, and then do the exact opposite to revert. This would have no impact on DLUs.
>
> Dennis Heim
> Network Voice Engineer
> CDW Advanced Technology Services
> 11711 N. Meridian Street, Suite 225
> Carmel, IN 46032
>
> 317.569.4255 Office
> 317.569.4201 Fax
> 317.694.6070 Cell
> dennis.heim at cdw.com
> cdw.com/content/solutions/unified-communications/
>
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
> Sent: Tuesday, June 01, 2010 9:58 AM
> To: Ovidiu at romandie.com
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Subject: IP phones in Disaster Recovery Site
>
> With the assumption that the migration is to a new model and/or protocol this could entail DLU changes, even using the same database record (ie migrating a 7940 to a 7970 would require an extra DLU).
>
> For updating the same device without BAT you just change the device name to reference the new mac address. I don't know off the top of my head if a BAT custom file update can change device name, but that may work for you.
>
> Either way I'd recommend lots of testing with a single phone so you know exactly what you can and cannot do. Don't just go by the docs, verify for yourself what will and won't work.
>
> -Ryan
>
> On May 31, 2010, at 9:33 AM, Ovidiu at romandie.com wrote:
>
>
>> BAT + Phone migration looks interesting but with several limitations.
>>
>> Extract from CUCM System Guide
>>
>> The Phone Migration window allows you to migrate feature, user, and
>> line configuration for a phone to a different phone. You can migrate
>> data to a different phone model or to the same phone model that runs a
>> different protocol.
>> ...
>>
>> Before you can migrate phone configuration to a new phone, consider
>> the following information:
>> - The new phone uses the same existing database record as the original
>> phone, so migrating the phone configuration to the new phone removes
>> the configuration for the original phone from Cisco Unified
>> Communications Manager Administration/the Cisco Unified Communications
>> Manager database
>> - Before you migrate the phone configuration to a new phone, ensure
>> that you have enough device license units for the new phone ...
>>
>>
>> Questions:
>>
>> - different phone model or different protocol I wonder if this is a
>> hard requirement. Can we use it to migrate from a SCCP
>> 7962 to another SCCP 7962 if the first phone is dead?
>>
>> - "ensure that you have enough device license units for the new phone"
>> This one is tricky... Imagine that Autoregistration is disabled, if
>> the new phone uses the same existing database record as the original
>> phone I don't see why we need additional DLU's. The new phone would
>> register and the old one will get rejected. That works only if it's a
>> simple swap of the MAC address in the Database.
>>
>>
>> Has anyone used this and wants to share his experience ?
>>
>> Any other ideas are welcomed.
>>
>> Thanks
>> Ovidiu
>>
>>
>> En réponse à "Ovidiu at romandie.com" <ovidiu at romandie.com> :
>>
>>> ------------------ Début du message d'origine --------------------
>>>
>>> Yes, the cluster is available. DR is for a couple hundreds IP phone
>>> that are on the DR site and have to be available for use as soon as
>>> the DR is launched.
>>>
>>>
>>> En réponse à "Jason Aarons (US)" <jason.aarons at us.didata.com>
>>> :
>>>
>>>> ------------------ Début du message d'origine
>>>>
>>> --------------------
>>>
>>>> In your DR scenario is the Publisher available?
>>>>
>>>> -----Original Message-----
>>>> From: cisco-voip-bounces at puck.nether.net
>>>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed
>>>> Leatherman
>>>> Sent: Monday, May 31, 2010 8:49 AM
>>>> To: Ovidiu at romandie.com
>>>> Cc: cisco-voip at puck.nether.net
>>>> Subject: Re: [cisco-voip] Subject: IP phones in Disaster Recovery
>>>> Site
>>>>
>>>> I would like the BAT option myself.. have a file ready to go and
>>>> uploaded, and if you need to execute the DR plan, just go in and
>>>> schedule it to import immediately. Either way you are going
>>>>
>>> to
>>>
>>>> have to
>>>> touch call manager to make it work, even if its just unchecking some
>>>> box somewhere to make phones active. This way your just
>>>>
>>> going
>>>
>>>> in and
>>>> doing 1 thing in BAT instead of touching each DR phone individually.
>>>> Should be easier to document for your plan too.
>>>>
>>>> On Mon, May 31, 2010 at 6:01 AM, Ovidiu at romandie.com
>>>> <ovidiu at romandie.com> wrote:
>>>>
>>>>> Hi everyone
>>>>>
>>>>> Looking for the best way to provision Disaster Recovery IP
>>>>>
>>>> phones in
>>>>
>>>>> CUCM 7. We have to provision real phones but without
>>>>>
>>>> consuming
>>>>
>>>>> DLUs or not many in any case.
>>>>>
>>>>> Seen a while back in one of the presentations a check-box
>>>>>
>>>> that said
>>>>
>>>>> the phone is not active and hence does not consume DLUs.
>>>>>
>>> Is
>>>
>>>> this
>>>>
>>>>> usable in this case? (Didn't have a lot of time to google
>>>>>
>>>> it)
>>>>
>>>>> There's a BAT Phone migration option but have never used
>>>>>
>>>> it...
>>>>
>>>>> What are you guys using? Any pitfalls I should avoid?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Ovidiu
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>
>>>> --
>>>> Ed Leatherman
>>>>
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>>
>>>> -----------------------------------------
>>>> Disclaimer:
>>>>
>>>> This e-mail communication and any attachments may contain
>>>> confidential and privileged information and is for use by
>>>>
>>> the
>>>
>>>> designated addressee(s) named above only. If you are not
>>>>
>>> the
>>>
>>>> intended addressee, you are hereby notified that you have received
>>>> this communication in error and that any use or reproduction
>>>>
>>> of
>>>
>>>> this email or its contents is strictly prohibited and may be
>>>> unlawful. If you have received this communication in error, please
>>>> notify us immediately by replying to this message and
>>>>
>>> deleting
>>>
>>>> it
>>>> from your computer. Thank you.
>>>> ------------------- Fin du message d'origine
>>>>
>>> ---------------------
>>>
>>>
>>>
>>>
>>> ------------------- Fin du message d'origine ---------------------
>>>
>>
>> _______________________________________________
>> 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
>
>
More information about the cisco-voip
mailing list