TMS and Far End Camera Control

[cashta001]

We recently started using TMS to automate calls for our Telepresence classes.

Prior to using TMS, our MX700 users had access to Far End Camera control on our MX300 G2s using the Touch 10. Once TMS started controlling the calling, users lost that functionality.

TMS has the endpoints dialing out via Conductor (SIP) to the meeting rooms.

Is it possible for a user on a MX700 to control the camera on a MX300 G2 when the endpoints are connected to a meeting room via TMS?

Some additional details
TMS version: 15.3.0
VCS-C and VCS-E version: 8.6
CUCM version: 11.5.1.11900-26

Endpoints Affected
MX700 version: ce8.2.1.e9daf06
MX300 G2 version: ce8.2.0.d66bc59

[Patrick Sparkman]

You mention Conductor, can you tell us what conference bridge you're using, it is an MCU or TelePresence Server?

Can you tell us more about how you were connecting your conferences prior to and after integrating TMS?

TMS shouldn't have any impact on FECC support, it would be the conference bridge and endpoints that would determine that.  If you're using TelePresence Server with Conductor, from my experience, FECC isn't supported.

[cashta001]

We are running a TelePresence Server 7010.

Endpoints were dialing each other directly prior to utilizing TMS. They were not dialing into a bridge.

Hopefully FECC support will be added in a future release.

Appreciate the insight.

[Patrick Sparkman]

The TelePresence Server 7010 last date of software support was back in June 2016, so no new software will be released for it.  Matter of fact all the hardware based TelePresence Servers have had their EOS announcements made.

TelePresence Server EOS/EOL Notices

Regarding the TelePresence Server software itself, development of that is also slowing down as active development is now being put toward Cisco Meeting Server, which is the conferencing solution going forward.