03-26-2025 12:36 AM
03-26-2025 02:59 AM
Appreciate the heads up. Please share the defect ID from your TAC case when they provide it.
03-26-2025 03:08 AM
I would recommend opening a case with TAC and filing a de facto report, if the Miracast is breaking on the latest version.
03-26-2025 07:03 AM
Yeah, I tried to file a bug report with TAC, they were less than helpfull and told me to contact my supplier instead.
03-26-2025 07:55 AM
Push back if you have regular SMARTnet contract on that serial number. The only valid reason for them to brush you off would be the absence of a support contract or if your partner sold a variation of the regular offer where they are required to take first call to triage and then escalate to Cisco if needed.
Escalation path:
03-30-2025 09:45 PM
If I look in Control Hub our stable version is 11.26 and it was released in the beginning of March. Based on this the 11.24 version should have been released in January 2025.
03-31-2025 12:57 AM
Thank you, but as stated earlier this is for on-prem, released 07-Mar-2025
03-31-2025 03:03 AM
What I shared is also for on-prem, updated from cloud.
03-31-2025 03:21 AM
Yes but that requires Webex Edge for Devices which, while ideal, may not be possible for the OP (e.g., air gapped environments or another ecosystem such as Zoom Node Conference Room Connector).
AFAIK the OP has two choices: push back on TAC or wait and hope it works again in the next release published to Cisco.com. Personally, I’d choose the former.
03-31-2025 04:00 AM
I tried to push back against TAC and CCed the manager this time.
Engineer just copy pasted her earlier responce once again.
I contacted our supplier/reseller as well just now asking why for the first time since 2008 TAC has an issue with me contacting them.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide