We recently upgraded our TMS from 13.1.1 to 13.2.2. Since then, when we power up a room for a VTC, the CODEC does not register, none of the persistent settings for that endpoint were applied during start up. We have to manually apply them by selecting the endpoint in Navigator, then Force Refresh, then Persistent settings and click Save, then Force Refresh once again and then the endpoint is fully registered and we can add the endpoint to the VTC. When we power the endpoint down and bring it back up, we have to do this process all over again. This issue did not exist when we were on TMS 13.1.1.
Have there been any other changes in your environment? Software upgrades on endpoints / enabling or disabling https on IIS / etc...
HTTP has to be disabled. We currently have two TC software version, 99% of our endpoints are on TC 5.0.1, the others (two) are on TC 6.0.2 (latest JITC approved for US Gov’t)
Can you please provide more info on which type of endpoints you are using, and which (if not all) of the persistent settings are not being applied?
We have C60’s and EX90’s. The E164 alias, H323 ID, Gatekeeper IP among a couple more. We have to go to Navigator, select the system, go the Settings > Persistent Settings ( all of the entries on the right hand side is filled in correctly, there are no entries on the left hand side) click save, perform a Force Refresh and the endpoint will come up fine so add into a call.
There were some issues with applying persistent settings to endpoints fixed in the newer (14.x) release of TMS - are you able to upgrade again to a recent version of TMS (14.3.1 is the latest).
That is an option that is being discussed, but for a different reason other than this matter.
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: email@example.com 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 ...