I would register the phones and gateways at both sites to a single host, move the free host to the new site, move its phones and gateway to the new site and have them register to it (at this point, only site-to-site dialing and voicemail will be down.), then move the other host and its phones/gateway to the new site. Anyway, there are a dozen ways to do it and all of them involve some kind of outage. Don't get tricky and try to change IP addresses between the old and new sites and you'll be fine - move your phone network and get it up and operational so that the sites have telephony. If you work with someone who knows everything and starts insisting that the subnets need to be changed at the new sites, tell them to recreate the subnets only for telephony and you can work on changing the voice network addressing scheme some other time. 99.99 percent of the time moves like these turn into disasters when the engineer decide to get fancy at the wrong time. Keep it simple.
And no, do NOT "rebuild the cluster". Shut hosts down gracefully, move them, and make sure the new sites can ping each other when you put the hosts in the new networks. On Mon, Sep 14, 2009 at 9:23 PM, Michael Ciarfello <mciarfe...@iplogic.com>wrote: > Yea, that works. You don't even have to stop the servivces, just shut > down the server and move it. > > It's up to you if you want to change the CallManager group to gracefully > re-register the phones and gateways to the PUB before turning the SUB off. > If you have H323 gateways, you might want to test if they are still taking > calls (you have preference command to both CCM's, the voice class h323 > command is working properly, etc. > > When it's time to move the PUB, you might want to make sure you take a > COUPLE of bars backups in case something gets damaged. > > You should have a testing plan and run through it after you turn the SUB > off and before you take it away. > ------------------------------ > *From:* Arun Kumar [arunv...@gmail.com] > *Sent:* Tuesday, September 15, 2009 12:16 AM > *To:* Michael Ciarfello > *Cc:* Nara Shikamaru; ccie_voice@onlinestudylist.com > > *Subject:* Re: [OSL | CCIE_Voice] Moving IP Telephony Setup > > thanks, I'll take care of this valuable information but for my setup do I > really need to break the cluster ? I'm thinking just stop all the services > on SUB and then take the SUB offline and move to new office and connect in > same LAN as both office's are connected and have IP Addressing scheme. Once > SUB is offline take the PUB offline (during off hours, so my SUB will be > able to handle that call volume) and move to new location. > > thanks > > On Tue, Sep 15, 2009 at 9:31 AM, Michael Ciarfello <mciarfe...@iplogic.com > > wrote: > >> Don't forget that when the PUB is down, people won't get user-facing >> features such as MWI, call forward all, etc. >> That functionality doesn't start until 6.1. Call Forward all might be >> required for a receptionist who call forwards to a Unity CallHandler for >> after hours support, etc. You can probably wait until after hours, then do >> a BAT export, then look through the CSV file in a spreadsheet program and >> see who has call forward all set. >> >> You stated you didn't have CTI dependent applications such as IPCC. >> That's good becasue of the very-low round trip time dependency. The IPCC >> pepople would also require the PUBlisher to login and change state. >> >> If Unity is UM. Make sure your Unity and Exchange move according to the >> Unity Design document. Those have to be on the same 100Mb LAN usually with >> AD and Domains and Global Catalog positioning properly, otherwise you will >> get weird Unity issues. Your MS people might want to move the users to a >> mailstore at the new location where the new Unity server will be placed. >> >> To break the cluster, you will have to delete all the dependent objects in >> CCMAdmin then finally delete the system-> server object. Don't know if >> that's all required. You will have to change the IPAddress when you move it >> to your new location. CallManager 5.x had a BUNCH of database sync issues. >> I've had TAC in the Linux shell performing database commands once. Another >> engineer for another customer spent Thanksgiving holiday (and a couple other >> night downtimes) at a customer site fighting through database issues. Might >> want to upgrade to at least 6.1 first. >> >> >> ------------------------------ >> *From:* ccie_voice-boun...@onlinestudylist.com [ >> ccie_voice-boun...@onlinestudylist.com] On Behalf Of Arun Kumar [ >> arunv...@gmail.com] >> *Sent:* Monday, September 14, 2009 10:55 PM >> *To:* Nara Shikamaru >> *Cc:* ccie_voice@onlinestudylist.com >> *Subject:* Re: [OSL | CCIE_Voice] Moving IP Telephony Setup >> >> Hi Nara, >> >> Thanks for your input. I'm thinking to just stop the SUB (All Services and >> then shutdown the system) and then move the SUB to another office (let me >> know if any better way to do this ? or how can I break the Cluster ?). Plug >> back SUB and will make sure PUB is reachable then will do the same with PUB. >> Later I'll move my Unity. >> >> Please let me know your thoughts on this or any better way to do this. >> >> Thanks >> Arun >> >> On Tue, Sep 15, 2009 at 4:30 AM, Nara Shikamaru <shikam...@kagadis.com>wrote: >> >>> Arun, >>> What do you mean by "rebuild the cluster"? If you have a pub at one >>> site and a sub at the other, you probably have each site's phone register >>> locally to their own host (eliminating the need for SRST for the most >>> part.) The only thing that's affected when you move the hosts is intrasite >>> dialing between the two buildings and voicemail/call handlers will be >>> unavailable. This is pretty much a matter of making sure that the IP >>> schemes are not changed at each new site so that you don't have to go >>> through anything like change IP addresses on CUCM and Unity - which can be >>> done but is something that I would stay from when time is short in a move >>> like this. Just recreate your subnets and VLANs, make sure both sites can >>> talk to each other, then move your equipment. >>> >>> When you port your new numbers to the new circuits, hopefully you're >>> going to be staying with the same carrier and that they're aware that time >>> is of the essense once your voice gateway at the new site is up. >>> >>> On Mon, Sep 14, 2009 at 11:31 AM, Arun Kumar <arunv...@gmail.com>wrote: >>> >>>> Hi All, >>>> >>>> I know this may be not the right place but I know here are many experts >>>> so please provide your valuable feedback: >>>> >>>> My HQ Setup: >>>> >>>> 1. One Cisco 3825 Voice Gateway >>>> 2. Two CCM 5.x Servers >>>> 3. 1 Unity 5.x >>>> >>>> we're shifting the office and assigned the task to move the IP Telephony >>>> to other office( both the office's are connected via MPLS 10 MB Links) with >>>> *Zero downtime*. Please let me know how can I go about it ? >>>> >>>> This is what I thought: >>>> >>>> 1. Break the CCM Cluster and move Subscriber to other office >>>> 2. Configure Cluster over the WAN again >>>> 3. Break the Cluster again and Move the PUB to new office and rebuild >>>> the cluster >>>> 4. Move the Unity Server ( I don't think I can have Zero downtime) >>>> 5. Got New Line with same DID range in new office (not operational yet) >>>> 6. Configure other 3825 VG and make it Live and take the Original VG >>>> Down >>>> >>>> >>>> please provide your valuable suggestion on moving this ? Please let me >>>> know if you need any other info. >>>> >>>> Cheers >>>> Arun >>>> >>>> >>>> _______________________________________________ >>>> For more information regarding industry leading CCIE Lab training, >>>> please visit www.ipexpert.com >>>> >>>> >>> >>> >>> -- >>> -Shikamaru >>> >> >> > -- -Shikamaru
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
