I would assume it should be fine, as the codec isn't changing, just the software version it's running and any new features it might introduce. You might find some things are missing in TMS, such as configuration templates might not have any new configuration fields that might have been introduced with newer codec software after whatever date TMS 13.2 was released.
According to the Interop Guide, the versions that were tested against TMS13.2.1 were TC4 and TC5.
Chances are that things will work fine, but newer features may not be available. You may also hit some problems depending on how you have your systems configured - we had some here with scheduling (CSCum50651 and CSCum50686) with anything TC6 or higher.
Wayne -- Please remember to rate responses and to mark your question as answered if appropriate.
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...