Yes, we are doing a new install at the moment, and we are getting the exact same error with the exact version. Does anyone know what needs to be done to correct this? If we figure it out, we will update this post.
FYI, we got this fixed after working with TAC. They told us there was a bug for 4.1.3 (CSCsj37299) and had us install ES127. Once we installed the ES, Bat 5.1(4d) was installed and this fixed the problem. As a note, you need to uninstall your current version of BAT before applying the ES.
Is it possible to install BAT 5.1(4d) without installing the ES127 for CCM 4.1(3)? I think this has probably been addressed in 4.1(3)SR7 now, but SR7 doesn't yet appear on the CRS compatibility matrix.
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...