[cisco-voip] COBRA

Wed Apr 29 17:18:01 EDT 2009

But either way, why doesn't it bring over the COS?

On Wed, Apr 29, 2009 at 4:09 PM, Jason Aarons (US)
<jason.aarons at us.didata.com> wrote:
> They should watch the COBRAS help videos on ciscounitytools.com.  Doesn't have to be clean..They should have had you map us CoS old to new.
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan Charles
> Sent: Wednesday, April 29, 2009 4:35 PM
> To: Matthew Linsemier
> Cc: Beck, Christopher; Jeremy Rogers; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] COBRA
>
> COBRAS was run with TAC on the phone and they emphasized that it had
> to be a clean Unity...
>
> On Tue, Apr 28, 2009 at 3:33 PM, Matthew Linsemier
> <mlinsemier at apassurance.com> wrote:
>> That's weird because we did a migration from 4.1 to 7.0 and PIN's were
>> preserved just fine.  Class of service was also preserved, as long as you
>> had a class of service of the same name created on the new Unity server.  If
>> not, COBRAS would ask you to map those subscribers with missing class of
>> services to another class of service.
>>
>> Make sure you have the latest COBRAS when you are doing your export and
>> import.
>>
>> Matt
>>
>>
>> On 4/28/09 4:05 PM, "Jonathan Charles" <jonvoip at gmail.com> wrote:
>>
>>> Yes, and it is inaccurate... we found that PINs and Classes of Service
>>> were just disregarded.... from Unity 4.1 to 7.0
>>>
>>>
>>> Jonathan
>>>
>>> On Tue, Apr 28, 2009 at 12:51 PM, Pat Hayes <pat-cv at wcyv.com> wrote:
>>>> Be sure to read the help file on ciscounitytools. It outlines
>>>> specifically what is and is not backed up along with the caveats.
>>>>
>>>> On Mon, Apr 27, 2009 at 10:43 AM, Jonathan Charles <jonvoip at gmail.com> wrote:
>>>>> Yes and no...
>>>>>
>>>>> Just be aware of some caveats...
>>>>>
>>>>> First off, not all info is migrated.
>>>>>
>>>>> Second, you will need to remove subscriber properties from AD beforehand.
>>>>>
>>>>> Third, some of the information not migrated is a surprise... (in the
>>>>> one I did Saturday, PINs and all the classes of service got wiped
>>>>> out...)
>>>>>
>>>>>
>>>>>
>>>>> Jonathan
>>>>>
>>>>> On Wed, Apr 22, 2009 at 2:59 PM, Jeremy Rogers
>>>>> <Jeremy.Rogers at ip-soft.net> wrote:
>>>>>> I will make sure of that.  Its just good to know!  That will save me some
>>>>>> time.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jeremy Rogers
>>>>>>
>>>>>> Network Management
>>>>>>
>>>>>> IPsoft, Inc.
>>>>>>
>>>>>> Jeremy.Rogers at ip-soft.net
>>>>>>
>>>>>> Phone: 888.IPSOFT8
>>>>>>
>>>>>> http://www.ipsoft.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: Beck, Christopher [mailto:CBeck at usg.com]
>>>>>> Sent: Wednesday, April 22, 2009 3:58 PM
>>>>>> To: Jeremy Rogers; cisco-voip at puck.nether.net
>>>>>> Subject: RE: [cisco-voip] COBRA
>>>>>>
>>>>>>
>>>>>>
>>>>>> YEP!!!
>>>>>>
>>>>>>
>>>>>>
>>>>>> Works great.  I just used it to consolidate 3 unity system onto 1 unity
>>>>>> connection cluster.
>>>>>>
>>>>>>
>>>>>>
>>>>>> There are some rules to live by, so definitely read the documentation.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Chris Beck
>>>>>>
>>>>>> IT Lead - Voice Technologies
>>>>>>
>>>>>> USG Corporation
>>>>>>
>>>>>> 312-436-4541 (office)
>>>>>>
>>>>>> 312-730-5524 (Mobile)
>>>>>>
>>>>>> 312-672-4541 (FAX)
>>>>>>
>>>>>> cbeck at usg.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: cisco-voip-bounces at puck.nether.net
>>>>>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jeremy Rogers
>>>>>> Sent: Wednesday, April 22, 2009 2:55 PM
>>>>>> To: cisco-voip at puck.nether.net
>>>>>> Subject: [cisco-voip] COBRA
>>>>>>
>>>>>>
>>>>>>
>>>>>> Can I use the COBRA tool to pull information from two separate Unity
>>>>>> servers
>>>>>> and put it on one that is replacing the other two?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Jeremy Rogers
>>>>>>
>>>>>> Network Management
>>>>>>
>>>>>> IPsoft, Inc.
>>>>>>
>>>>>> Jeremy.Rogers at ip-soft.net
>>>>>>
>>>>>> Phone: 888.IPSOFT8
>>>>>>
>>>>>> http://www.ipsoft.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Confidentiality Notice: This email is intended for the sole use of the
>>>>>> intended recipient(s) and may contain confidential, proprietary or
>>>>>> privileged information. If you are not the intended recipient, you are
>>>>>> notified that any use, review, dissemination, copying or action taken based
>>>>>> on this message or its attachments, if any, is prohibited. If you are not
>>>>>> the intended recipient, please contact the sender by reply email and
>>>>>> destroy
>>>>>> or delete all copies of the original message and any attachments. Thank
>>>>>> you.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>> CONFIDENTIALITY STATEMENT
>> This communication and any attachments are CONFIDENTIAL and may
>> be protected by one or more legal privileges. It is intended
>> solely for the use of the addressee identified above. If you
>> are not the intended recipient, any use, disclosure, copying
>> or distribution of this communication is UNAUTHORIZED. Neither
>> this information block, the typed name of the sender, nor
>> anything else in this message is intended to constitute an
>> electronic signature unless a specific statement to the
>> contrary is included in this message. If you have received this
>> communication in error, please immediately contact me and delete
>> this communication from your computer. Thank you.
>>
> _______________________________________________
> 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.
>