Ad-Hoc conference with Conductor and CUCM shows on hold
I have a MRGL setup that has conductor in in (CUCM 10.5). I place a call between an SX80 and an MX300. From either endpoint, if I add in a third party from either endpoint, an ad-hoc conference does get created and all parties are successfully conferenced together, but for some reason both the SX80 and MX300 have message on the display that they have a call on hold. Is that by design? Is there a way to disable that notification?
Could you advise the version and type of bridge being used and if it is behind a conductor, and the version of TC code on the endpoints? I haven't seen this behavior but I'd like to test it if possible.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...