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.
SummaryUCCX 15 upgrades are not the upgrade binary's fault when they fail. Ten specific operational gaps account for nearly every upgrade that slips its change window or leaves services broken post-switch. This article documents each landmine, the ob...
SIP Cause Code 96 is one of the most common inter-working cause codes observed on CUCM-to-CUBE trunks, and also one of the most misleading. It does not tell you what went wrong - it tells you that something one side expected in a message was missing ...
SummaryCUCM Mixed Mode is not a single switch. Enabling it at the cluster level does not automatically secure every layer of the UC stack. This article walks the ten verification points that determine whether Mixed Mode is actually protecting your en...
Most Cisco UC environments I walk into have some segments of their voice network encrypted and others wide open. The SIP trunk to Unity Connection might be TLS, but the voice gateway talking to the carrier is unencrypted UDP/5060 and RTP. Or the pho...
Installing RTMT 12-14 Versions on Windows 11 requires Java releasesjdk 1.8_0 101, jdk 1.8_0 102; I installed 4 total versions including jdk 11.0.15.1 and jre 1.8.0_341.You must however follow these steps first in order for the install to work otherw...
the .jar tool is partner-gated with a password, and even then it only handles entity extraction (Agents, Teams, CSQs, Skills, Phonebooks). The actual call flow translation — which is where every UCCX migration gets stuck — isn't covered by that tool ...
The tool is read-only entity extraction only. It pulls "Agents, Teams, CSQs, Skills, Phonebooks" — the configuration entities, not the call flows. The hard part of any UCCX migration (rewriting the call flow logic into Webex CC's Flow Designer) is ex...
This behavior appears to be connected to how "Auto Collapse Into Line Key" interacts with the active-call display on the phone. Per Cisco's documented description of the feature in the 8800 (sorry I could not find a specific 9800 reference) Series MP...
Going back through this — you're right. The Cisco SIPREC docs I can pull up are all SIP-to-SIP through CUBE B2BUA. The media-class examples are VoIP dial-peer scenarios, not POTS. I was reasoning from the general config model rather than something Ci...