We are planning to have a remote site with around 30 users.
The one way latency from our datacentre (where our CUCM servers are located) and the remote site is around 160ms.
What would you suggest for our remote site -? centralized deployment or a distributed set-up with a CME at the remote site?
When I check the cisco SRND, I dont see any hardcore latency limit suggestions for remote site deployments.
I find the following lines "The influence of latency on design varies, based on the type of Unified Communications service considered for remote deployment. If a voice service is hosted across a WAN where the one-way latency is 200 ms, for example, users might experience issues such as delay-to-dialtone or increased media cut-through delays" from http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/8x/uc8x/models.html"
What criteria should I have for deciding the deployment model?
First of all would like to suggest to reduce your one-way latency of 200 ms. Because,The telephone industry standard specified in ITU-T G.114 recommends the maximum desired one-way delay be no more than 150 milliseconds. With a round-trip delay of 300 milliseconds or more, users may experience annoying talk-over effects.
Keeping in mind the above point, will recommend you to have Distributed deployment with call processing server as CME as you have only 30 users now unless and until you reduce your one-way latency.
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.