Hi All, Just to give you all an update on this:
With everyone's valuable info and other info, migrated whole setup of IP Telephony (6 Servers + 3 VG Transcoders + Couples of GW MGCP / H323) to new site and downtime was very less 15-20 min. In new site I kept the same subnet and ip addressing scheme as earlier so it made my life really easy and yesterday completed this whole migration and everything is seems to be working fine. So again thanks very much everyone for your valuable feedback and suggestion. Thanks Arun On Thu, Sep 24, 2009 at 5:55 AM, Michael Ciarfello <[email protected]>wrote: > IPCC SRND. 4.5, but it hasn't changed. See page 3.1 for the IPCC / CTI > requirement. > > http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_4_5/srnd/crs4.5srnd.pdf > > Other than that, change the JTAPI and RMJTapi groups so that the primary > CTI server ponts to the CCM server that is moved and were you will move the > IPCC server to. You may have to change the device pool all the CTI ports > are pointing to so that the CallManager group has listed first the CCM > server that already moved. You might want to create a new DP that has only > the CCM that already moved. You don't want it (CTI / JTAPI / RMJTAPI) > failing over to the distant CCM server. > > I think that's it. Let me (us) know if you have additional questions. > > > ------------------------------ > *From:* Arun Kumar [[email protected]] > *Sent:* Wednesday, September 23, 2009 10:42 AM > > *To:* Michael Ciarfello > *Cc:* Nara Shikamaru; [email protected] > *Subject:* Re: [OSL | CCIE_Voice] Moving IP Telephony Setup > > Hi Michael, > > Can you please provide me any link what re-configuration I need to do in > IPCC to make the setup successful. > > Thanks > Arun > > > On Wed, Sep 23, 2009 at 7:23 PM, Michael Ciarfello <[email protected] > > wrote: > >> IPCC must be co-located on the same LAN (simplicity. Read the IPCC SRND >> for full details, I think 45MB would be enough) as the CTI server it >> connectes to. SO move the IPCC and reconfig if necessary to connect it to >> the CCM that moved. >> ------------------------------ >> *From:* Arun Kumar [[email protected]] >> *Sent:* Wednesday, September 23, 2009 7:46 AM >> *To:* Nara Shikamaru >> *Cc:* Michael Ciarfello; [email protected] >> >> *Subject:* Re: [OSL | CCIE_Voice] Moving IP Telephony Setup >> >> Hi All, >> >> I've started my move and so far moved successfully, one Unity 5 and CCM 5 >> but I've to move my IPCC Servers also (version 5) and IP's are changed now. >> I've moved Unity and CCM and tested with New IP Changes works fine but I'm >> not sure on IPCC Move, what needs to be done on IPCC Servers, CCM Side ? so >> if anyone can give some guidance or link to some doc on this will be really >> helpful as without this I'll not be able to move my CCM PUB. >> >> Thanks for you all your valuable suggestions. >> >> Regards >> Arun >> >> >> >> On Tue, Sep 15, 2009 at 11:32 AM, Arun Kumar <[email protected]> wrote: >> >>> Nara thanks very much I'll surely take these things into the >>> consideration before going for any move. >>> >>> Cheers >>> >>> >>> On Tue, Sep 15, 2009 at 11:14 AM, Nara Shikamaru >>> <[email protected]>wrote: >>> >>>> 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 < >>>> [email protected]> 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 [[email protected]] >>>>> *Sent:* Tuesday, September 15, 2009 12:16 AM >>>>> *To:* Michael Ciarfello >>>>> *Cc:* Nara Shikamaru; [email protected] >>>>> >>>>> *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 < >>>>> [email protected]> 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:* [email protected] [ >>>>>> [email protected]] On Behalf Of Arun Kumar [ >>>>>> [email protected]] >>>>>> *Sent:* Monday, September 14, 2009 10:55 PM >>>>>> *To:* Nara Shikamaru >>>>>> *Cc:* [email protected] >>>>>> *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 < >>>>>> [email protected]> 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 >>>>>>> <[email protected]>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
