I just finished a Cisco IPT Implementation in the HQ of one of our customers and studing the possibility of going through the other sites in 20 different cities in 4 different countries. In the HQ we have full blown CallManager. I am doing the design for the next site which has about 150 users/IP Phones. At the begining, I was thinking of a centrilized solution but now I am studing the possibility of using the distributed Call Processing by putting a CME and CUE in order to minimuze the bandwidth utilization (Voicemail, MOH etc). Curently, the maximum available bandwidth is a T1 and it's already at 70% of utilization. Please advice if there's a bether approch.
There are pros/cons to have a distributed and centralized. Since your bandwidth is low, you can purchase CMEs then use H323 trunks between the two sites and limit calls between sites. But you will have to manage another CME,etc. Since you do not have the bandwidth for 150 you will need to look at your pros/cons of having distributive model. There are ways to centrally manage CMEs through one "dashboard" or interface. but you lose some functionality of having a centralized IPT system.
MOH can be loaded on SRST routers, so that is not a problem. (by pass multicast and streams through the T1, etc)
If you centralized at 70 percent, you are limiting your calling ablity through the T1 for voicemail, Callhandlers, etc. My calcs say you have 450k of bandwidth for calls. Possibly it might work, but you are on the very very edge of maxing out your T1.
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...