TMS 14.5 and Conductor deployment cascading issue

[William McDonough]

Hello all,

we have had a successful conductor deployment for about a year now and a few months ago we were able to cascade between the telepresence servers.  We were on 14.4.1 (TMS) and 2.4x for conductors.  Cascade was fine but as soon as we moved to tms 14.5 cascading is now failing.  Has anyone run into this or know of a change that would cause this feature to stop?

Thanks

Liam

[Anas Abueideh]

Hi,

do you have TP servers or MCU ?

TP servers are not supported for cascading

HTH

Anas

don't forget to rate the helpful posts

[George Thomas]

Cascading of TP servers is supported in the latest version of TP server.

[Anas Abueideh]

can you share me the link ?

[George Thomas]

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/ts/release_note/Cisco-TelePresence-Server-Software-Release-Notes-4-0-2-8.pdf

[William McDonough]

It is definitely allowed in my deployment, we are remotely managed.  We were successfully cascading up until this upgrade.  Not sure where you are getting that it is not support as it says it right in the release notes on page 17 at the top.  

Support for cascaded conferences
Note: This feature is only available in the remotely managed mode of TelePresence Server operation. It is not
available in the locally managed mode.

With that said does anyone have a remotely managed deployment with multiple TPS (4.0), conductor (2.4) and TMS (14.5) that is actually cascading?  We have no changed any settings since the upgrade yet the cascade is now broken.