Darren,

I would say that is a really complicated question an the answer depends on many things like WAN infrastructure, gateway locations, what types of extra services you run, what other types of traffic share the WAN and the list goes on. You may want to check out the CUCM SRND for some basic guidance:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/models.html

Chris

Darren T. Manners wrote:

I have question to pose. We have 23 colleges. Each college tends to run its own call manager. Our systems office was asking me what drawbacks are there to having a single call manager and subscriber at the systems office and everyone else feeding off of this? Each site will have srst….but what about functionality , presence, video, responder etc etc…Latency is about 20ms..

Im trying to find out if there is any reason NOT to…so from my perspective im looking for problems to not go to that solution. Each site has about 400-600 phones. Any help is appreciated.

Darren

*Information Security** Officer**
**Mountain Empire Community College **
***/CCIE (SEC) # 18929, CISSP (#85782), CCSP, GIAC GCIA/ ****/(#0849) GCIH (#1348) GCWN (#0467) CCVP, MCSE, ASE HP, CCA/****//**

****

**Tel: 276 523 2400 ext 226 **


**Email: ****[email protected]** <blocked::mailto:[email protected]>** ***
***www.mecc.edu** <blocked::http://www.mecc.edu/>** **

/7/4/2009
Darren T. Manners
[email protected]
http://www.mecc.edu/

/CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information or otherwise be protected by law. Any access, use, disclosure or distribution of this email message by anyone other than the intended recipient(s) is unauthorized and prohibited. If you are not an intended recipient (or an agent acting on an intended recipients behalf), please contact the sender by reply e-mail and immediately destroy all copies of the original message. Virus scanning is recommended on all email attachments. /

//



Reply via email to