The Unity 3.1(6) upgrade is not going to be a single file. It is going to upgrade the entire body of code. It is possible that a hot fix was created for your defect prior to 3.1(6) being released. If you give me the defect ID I can tell you. If one was created you can apply it and only the files affected by the defect will be replaced. If one was not created you will need to do the full upgrade to 3.1(6) to get the defect resolved.
Yes there is a hotfix for this defect so you won't need to upgrade to 3.1(6). Please open a case with TAC and ask the engineer for 3.1(5)ES39 and have them link your case to this defect. They can get the hotfix for you.
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...
[toc:faq]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 discusse...