Swop the hardware , its quite unusual for router to lock completely , normally when they have trouble they just reload themselves after a crashdump so if it was me i would do that first.
Second if it is a bug and cisco don't know if it yet i would try and find an iOS that does work , its pain but try each release going back one by one, hopefully eventually you should find one that works.
We are having the same issue with a customer, do keep us posted.
The latest IOS supported by Verizon is 12.4(20)T4. Rolling back to this will not help you. We are still expiriencing the exact same problem with this IOS as well as with the previous IOS we were running 12.4(20)T2. Customer had been running this setup with absolutely no reported issues on UCM 4.x for months (almost a year). The only thing that has changed here is the upgrade to UCM7.0. I'm glad I came across this post since we were informed to upgrade to 22T but obviously this is not going to help us out. When the router does lock up and become unresponsive we are unable to capture any information by way of EEM script due to high CPU utilization, so we have absolutely no idea what is going on. We see the SCCP application is overwelming the CPU resources, but this is it. Memory swap on the router has not resolved the issue so we do not believe it is a hardware issue.
We have also noticed the skinny output you have reported.
Another interesting issue is that not only are we using the CUBE as a DSP farm and for software MTP resources but we also have another 3845 sharing the skinny resource load as well. This gateway has NOT crashed, so it seems to me that:
1. UCM 7.0.x is sending a message that is causing the gateway to crash since 4.x never caused this problem.
2. The SIP stack must be involved here, because our other DSP farm hasnt crashed ever (and its been over 2 months)
Anyone else having the issue? Cisco has filed a bug ID for our issue stating a 15.x release fixes the issue, however, I dont see how that can be determined given such limited evidence.
I believe an interim image maybe in the works but I would imagine for one this takes some time and I havent heard back regarding the release the image will be based on, but I have only just recently replied to the CSE with this question.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...