In the current client configuration, they have an MCU integrated into the VCS topology to support multi-point Jabber/Movi Video calls. Their new requirement is to enabled multi-point calls for Jabber (Windows) clients registered to their CUCM.
I was hoping to avoid the requirement for two MCUs. Make sense?
I had similar question about this previously and I don't believe it can be done because you can't really partition the MCU resources and CUCM don't have any settings to limit how much MCU resources that it can use.
So if you register an MCU to both VCS and CUCM, they will both compete for resources and for the reasons I stated above, either the VCS or CUCM will soon be out of resources.
If you want to allow adhoc multi-point Jabber calls, I suggest you use Cisco 2900 routers with PVDM3 and register them as a video resource under CUCM instead.
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...