Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi everyone,I'm interested in hearing about your real-world experiences with Cisco products. There are so many solutions available across networking, security, collaboration, and cloud management, and I'd love to know which ones have made the biggest...
Hi everyone,I hope you are all doing well. I am working on customizing the look of a page and I need some help with override styles in the Cisco Community theme. I’m having trouble figuring out how to safely apply custom CSS so that it does not confl...
Based on the symptoms you've described, this appears to be a hardware failure rather than a software defect.If the power supply is already showing as "Bad" (red PS OK LED and show environment power reporting Disabled/Bad), a software upgrade is unlik...
A couple of things stand out from your description.First, the fact that on-prem can reach the VMX LAN IP and the spoke VM can reach the VMX WAN IP, but not the VMX LAN IP, suggests the issue is likely inside the Azure networking path rather than Auto...
It is not likely to be a phone hardware problem as it is a user/extension problem and not a configuration issue that is stored on the phone and is only a thing of the past. Some suggestions: Check if an MWI On was sent, and an MWI Off was not receive...
If DND wasn't enabled as a softkey, it's unlikely its users enabled it. This has been observed when there is a configuration problem from CUCM or a problem with the features synced. Here are a couple of things to look for: Ensure that the device is c...
This sounds more like a call flow or SIP signaling issue than a CUBE hardware conference problem, especially since you've reproduced the same behavior with Ribbon and AudioCodes SBCs. That tends to rule out the SBC itself.I'd start by checking whethe...