Yeah, I saw that could be done. My question then is this: If I did that, does a potential customer just buy a CME bundle and tie the two or three CMEs together somehow? How would you guys do something like this? CME at the main site, with the need for SRST at remotes. Would you just do a CME at each site and tie them together? Youre thoughts are appreciated.
SRST is mostly for CM fallback and not meant to do the full processing that CME does with ephones and other options. I'd have multiple CME's at each site with dial-peers pointing to the extensions at the other sites. You could also do one CM cluster and the remote site routers would be set up for SRST in case of WAN failover.
I agree...Assuming you have a Centralize CM design, then you will have SRST at the remote site. However, you will need to check with the customer's Cisco acct team on this as I've heard that this is part of the CM license, and not related to the CME since VoIP is not being used with CME unless there is a fallback so licence still resides with CM and not CME.
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...