Solved: TMS shows VC endpoints as NO HTTP RESPONSE

devraj123 · ‎08-08-2016

Hi All,

TMS shows telepresence endpoints units as Status NO HTTP RESPONSE

After upgrading successfully 100 TP endpoints to firmware 7.3.6 with TMS version 14.5 .

few endpoints showing status as no http respose under TMS----endpoints section.
- even can not book conference with those affected devices showing status " no http response" | individually all working fine.
Please see snapshot.

Note: They just cannot be seen from the TMS. I can ping them from TMS server fine.:

Devraj

Nick Halbert-Lillyman · ‎08-09-2016

Is TMS running on Windows 2008/R2?

If so, one of the more recent TC versions removed support for TLS version 1.0. Windows Server 2008 and 2008 R2 have TLS 1.1 and 1.2 off by default, you need to enable them (google it, just needs something changed in the registry).

View solution in original post

Zac Colton · ‎08-10-2016

There is a difference between "no http response" and "no https response". The comments already added to this thread are making reference to the removal of TLS1.0 support within TC7.3.6. If on https is enables on the endpoint, TMS will need to be at least 15.0 for TMS to use TLS1.1 and TLS1.2. For these versions of TLS to be used, the base OS needs to support it *and* TMS will need to be configured for medium-high security level. There are caveats using the higher security levels. In the upcoming TMS release of 15.3, the medium security level (lowest level possible) TLS1.0, 1.1, and 1.2 will be available.

Now in regards to your issue, you are reporting a "no http response". SInce this is only for some devices, and you are not yet at a TMS version that supports TLS 1.1 or higher, you should first verify that http is enabled on the devices. You should also confirm that there haven't been a recent network changes. A few tests of manually enforcing management settings from TMS and taking some packet captures should provide some additional information to get you moving in the right direction.

View solution in original post

Patrick Sparkman · ‎08-09-2016

Try upgrading to TMS 15.x, some people have experienced similar issues with TMS 14.x with their endpoints, and after upgrading the issue went away.

Patrick Sparkman · ‎08-10-2016

Something also for you to check, you might be running into an issue documented here: TMS Reports 'No HTTP response' for a System.

Aman Soi · ‎08-10-2016

Hi Dev,

you can refer the link

https://supportforums.cisco.com/discussion/13021751/no-https-response-tc736-and-ce810

regds,

aman

Nick Halbert-Lillyman · ‎08-09-2016

Is TMS running on Windows 2008/R2?

If so, one of the more recent TC versions removed support for TLS version 1.0. Windows Server 2008 and 2008 R2 have TLS 1.1 and 1.2 off by default, you need to enable them (google it, just needs something changed in the registry).

Zac Colton · ‎08-10-2016

There is a difference between "no http response" and "no https response". The comments already added to this thread are making reference to the removal of TLS1.0 support within TC7.3.6. If on https is enables on the endpoint, TMS will need to be at least 15.0 for TMS to use TLS1.1 and TLS1.2. For these versions of TLS to be used, the base OS needs to support it *and* TMS will need to be configured for medium-high security level. There are caveats using the higher security levels. In the upcoming TMS release of 15.3, the medium security level (lowest level possible) TLS1.0, 1.1, and 1.2 will be available.

Now in regards to your issue, you are reporting a "no http response". SInce this is only for some devices, and you are not yet at a TMS version that supports TLS 1.1 or higher, you should first verify that http is enabled on the devices. You should also confirm that there haven't been a recent network changes. A few tests of manually enforcing management settings from TMS and taking some packet captures should provide some additional information to get you moving in the right direction.