VCS fails when presented with AES 256k Key for Traversal call. If your experiencing this now, did you just upgrade to MOVI 4.7? Customers running prior to X7.1 which upgraded MOVI are experiencing this now.
One last thing to verify. We are planning to upgrade the VCS to 7.2.1 to match the VCS-E. We are still on TMS 13.1.2 and upgrading the VCS to 7.2.1 which uses the TMS Provisioning Extension. We use Movi and I believe 7.2.1 still supports the TMS agent legacy? Will there be any negative affects if we stay on TMS 13.1.2 and upgrade to 7.2.1?
If I remember correctly, I would need to uncheck the "Enable TMS Agent Data Replication" option in VCS page in TMS then proceed with the upgrade?
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...