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.
The 2020 IT Blog Awards, hosted by Cisco, is now open for submissions through October 16. Submit your blog, vlog or podcast today. For more information, including category details, the process, past winners and FAQs, check out: https:...
We have CUCM and CUC (v12.5) which has been directly registered to Cisco's Smart Licensing, but today's I noticed this error from RTMT "Smart Licensing Authorization Renewal Failure". I tried to force the re-authroization and re-registration and now it sa...
Hello I have a Cisco 7841 3pcc Phone, if I specify a custom ringtone and try to play it, it is spit out in the log> Bad parameter in Ring File field: w = tftp: //192.168.220.120/TEST.rawand the standard sound plays.-----------4047 ERR Jan 17 16: 15: 33...