TMS saves the full routing and dial strings at time of scheduling the meeting. This means, that if later you change the dial strings on a conference host that has future scheduled meetings, then those saved routes will no longer be valid.
All versions of TMS including up to v14.3.2, would have required you to press edit on each scheduled meeting and do nothing more than Save. TMS would determine that the resource route logic was no longer valid and correct the routing logic.
TMS v14.4 (released on 09 May 2014) sports a new Conference Diagnostics tool.
This new feature allows administrators to identify and fix problems with existing conferences, and is particularly useful in the case of dial plan or infrastructure changes to your deployment, such as replacing a bridge.
When the diagnostics are run, Cisco TMS checks the following for all future scheduled conferences:
That all participants exist in the database.
That the route is valid: that all participants are still routable.
The auto-correct feature attempts to fix selected conferences automatically, taking action such as rerouting the conference, or removing invalid participants.
For further information see the Web Help for the Conference Diagnostics page in Cisco TMS.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...