Persistent Settings not being applied

[Manuel Lopez]

  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.

Any thoughts?                

[Wayne DeNardi]

Have there been any other changes in your environment? Software upgrades on endpoints / enabling or disabling https on IIS / etc...

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?

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).

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.

[Manuel Lopez]

Good morning,

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.

Thanks for getting back to me on this.

Have a Happy Thanksgiving.

[daleritc]

In TMS 13.2, we introduced the following feature:

Enable HTTPS access to the Cisco TMS Website (Windows 2008)

See the release note for furthe info about this feature:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/release_note/Cisco_TMS_Release_Note_13-2.pdf

As he mentions not having Http enabled, and he says this didn't occur in TMS 13.1., then this could be related to his issue...if he's running TMS on a Win 2008 server.

But is this only happening on one EP? If so, then a trace between the TMS and this EP could/would be telling ;)

Cheers,
Dale


Sent from Cisco Technical Support iPad App