12.1(5)YE4 is the latest/greatest version for the Catalyst 4224. Looks like at this point, your best bet would be to capture some of these call attempts in Call Manager traces or debugs, and open a TAC case. If you're using the 4224 as an MGCP gateway, you'll use the Call Manager traces per http://www.cisco.com/warp/public/788/AVVID/cm_trace.html . If you're using the 4224 has an H.323 gateway, capture the call attempts with DEBUG ISDN Q931. Either way, if you have the captures (along with SHOW VERSION and SHOW RUN) ready when you open your case, it'll move quicker.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...