i've a client looking at deploying CME at 5 locations (Site A,B,C,D,E where A is the HQ), with each site sustaining around 10 employees. The sites wud be connected via a Hub(Site A) & Spokes (Sites B,C,D,E) topology, where each site sustains a 2MB leased line to the HQ.
I've browsed thru the ciscopress CME book and found tt they had recommended a TANDEM design, whereby the HQ CME will act as proxy for the various dial-peers for inter-site calls, rather than having all the dial-peers configured per CME site.
Any recommendations from folks who had successfully deployed multisite CME/CUE?
I would suggest using a gatekeeper for dial plan resolution between remote sites. The hub site router can be the GK, as every site has only one link going to the remote and use PSTN as backup to call between the sites.
Thanks for the suggestion. I'm not exactly familiar with the concept of gatekeeper. So does it mean I need to get the gatekeeper license for the ISR router, and at the same time, it operates as bas a CME & a gatekeeper? Or do I need to get a gatekeeping appliance?
At the hub site you might have CME on a router. That router can act as the gatekeeper for your dialplan resolution. You define voip dialpeers at each remote site for inter office calls and rather than having different voip dial-peers pointing to each other for every other office you want to call, you just specify
session target ras under the each voip dial-peer. This will tell each remote branch router to consult with the GK as to how to reach the destination number. This reduces the configuration required on each remote branch router(adhoc) for calling each other.
You can even condense all your VOIP dial-peers required at each branch to just one dial-peer matching multiple branches and point it to RAS.
I have a siliar situation, the only difference is that i have a centralized callmanager cluseter and 10 remote sites with ccme and unity express. Will i loose any fuctionililty if i put all the dialpeers at remote ccme sites to the central GK interms of call transfer, etc.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.