<div>You can also extract route plan report as numplan.csv and it would give you all CSS, partions , Call Park , meet me and DN configured on your existing system</div>
<div> </div>
<div>Aman<br><br></div>
<div class="gmail_quote">On Wed, Aug 12, 2009 at 9:36 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div style="FONT-FAMILY: Verdana; COLOR: #000000; FONT-SIZE: 10pt">In 4.1(3) you can export device information in BAT. It provides a complete data dump. <br>
<div class="im"><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Wes Sisk" <<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>><br>To: "Mike O" <<a href="mailto:mikeeo@msn.com" target="_blank">mikeeo@msn.com</a>><br>
</div>
<div>
<div></div>
<div class="h5">Cc: <a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>, <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>Sent: Wednesday, August 12, 2009 10:35:36 AM GMT -05:00 US/Canada Eastern<br>
Subject: Re: [cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0<br><br>nope, no export natively in 4.1<br><br>On Wednesday, August 12, 2009 10:13:48 AM , Mike O <a href="mailto:mikeeo@msn.com" target="_blank"><mikeeo@msn.com></a> wrote:<br>
<blockquote>Wes,<br> <br>With only 50 users am I better off just rebuilding from scratch? All I really need are users and Phone/MAC addresses. Can I export them in 4.1?<br> <br>Thanks,<br> <br>Mike<br> <br>
<hr>
Date: Wed, 12 Aug 2009 10:04:48 -0400<br>From: <a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a><br>To: <a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>; <a href="mailto:mikeeo@msn.com" target="_blank">mikeeo@msn.com</a><br>
Subject: Re: [cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0<br><br>MANY variables:<br>how many times upgraded<br>how many interim versions were run<br>what native or 3rd party tools attempted to modify the database<br>
who attempted directly editing the database<br>how many dbl/iis problems have been encountered? Unfortunately transactions were not strictly enforced so when problems occured there were partial commits to the database<br>
Is enterprise LDAP integration used? This is probably the largest contributor to errors. When objects move in the enterprise there is no change notification to CM (unity tried but CN from AD appears rather unreliable) so CM ends up with numerous broken pointers in the database.<br>
<br>The other systemic problem is that 4.x enforced business rules via DBL rather than directly in the database. Think of having a guard in front of your storage room, but your storage room has no shelves. Users must verify with the guard but once inside they have free reign and very little structure.<br>
<br>/Wes<br><br>On Wednesday, August 12, 2009 9:07:05 AM , Lelio Fulgenzi <a href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a> wrote:<br>
<blockquote>
<div style="FONT-FAMILY: Verdana; COLOR: rgb(0,0,0); FONT-SIZE: 10pt">well, this doesn't sound promising. what kind of garbage exists in 4.x databases?<br><br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Wes Sisk" <a href="mailto:wsisk@cisco.com" target="_blank"><wsisk@cisco.com></a><br>
To: "Mike O" <a href="mailto:mikeeo@msn.com" target="_blank"><mikeeo@msn.com></a><br>Cc: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>Sent: Wednesday, August 12, 2009 8:49:47 AM GMT -05:00 US/Canada Eastern<br>
Subject: Re: [cisco-voip] Migrating from CM 4.1.3 to Cisco BE 7.0<br><br>imho. run DMA. it it works for you then that is the shortest path.<br>if DMA reports errors that you cannot easily repair then stare and compare.<br>
<br>dma has improved significantly and even better with 7.1. however, there is so much garbage possible in 4.x databases that the migration tool simply cannot always be accurate.<br>/wes<br><br>On Tuesday, August 11, 2009 9:12:39 PM , Mike O <a href="mailto:mikeeo@msn.com" target="_blank"><mikeeo@msn.com></a> wrote:<br>
<blockquote>
<div><font size="2" face="Arial">I have to migrate about 50 users/phone, whats the best way? DMA or start from scratch? </font></div><pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre></blockquote><br><br>_______________________________________________ cisco-voip mailing list <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a> </div>
</blockquote><br></blockquote><br></div></div></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>