I have the below setup to support video conferencing. I have SX20 and cisco jabber registered to call manager (as SIP). I have MX3000 endpoints are registered to VCS as H323 ID. we Have conductor and MCU to support video conferencing.
there are 2 templates for confernecing: Meetme and ad hoc.
Meet me conferencing is working perfectly
ad hoc conference is not working. I am trying it from cisco jabber in CUCM, it falls always audio conference.
Conductor is added to call manager and registered. added to media resource group.
SIP trunks are added for meet me and ad hoc conference.
do you have any idea why the ad hoc is not working ?
SX20: TC 7.1.2
One more thing. SX20 doesn't have the softkey to add participant to the call
I would say to properly use the adhoc functionality of CUCM you should have the video endpoints registered to CUCM. Maybe a MTP is added in your call flow which causes it to end up as a audio only call or maybe an other issue with your media resource groups.
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...