I am desiging a large enterprise IPT network. I have been working on CCM since the 2.4 days shortly after Cisco purchased the Selsius product. I have always used the rule of thumb that 500 sites is the limit for a single cluster. The other day I had an engineer tell me I am wrong. I know the technology changes but who is right. I have design two clusters for 814 sites with ICL to connect them. If a couple of you IPT vets tell me I am wrong I will bow down to the newbee.
I would not necessarly look at the number of sites to determine number of clusters as sites may vary in size, and you may have a customer with 10 phones per site with no additional applicaions. I would rather look at the total number of devices in the cluters, number of GWs, extenal applications i.e. IPCC, etc.
Doing it for so long I am sure you know the limits, especially between the advertised marketing numbers and realistic environment CCM can handle.
I guess what I am trying to convey is not to set a hard coded number for sites, but analyze the whole environent instead.
I guess when I think of sites I look at it from the voice gateways since each site will have SRST and and will be setup as a VG weather it be MGCP or H323.
The other issue I guess is Unity servers only supporting 3000 MB per server.
800 + sites seem like a lot of sites for one cluster to handle not only from size perspective but resources on the servers them selves.
It is only about 3000 - 4000 phones. I have done 3000 + user deployment with less sites like 30 or 100 sites. 800 makes me think a little more about what this solution can truly handle with one cluster.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...