The two groups of errors (MIU and Conversation) are not related. The Conversation errors showed up because there is esentially there has been an infinite loop programmed in Unity (Call Handler A goes to Call Handler B, and Call Handler B goes right back to Call Handler A--or something like that).
The MIU error could very well cause a Unity port to burn, but it should not cause all Unity ports to burn. When it is mentioned that "Unity" stops working, does that mean that Unity does not answer, Unity answers to fail safe, or calls directed to Unity go no-answer?
Whatever the case, you should probably contact TAC about this.
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: email@example.com 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 ...