Using Cisco end point in MTR mode and custom integration

[BristolBen]

Hi,

I have a client wishing to use Cisco end points for their UC in MTR mode, and also integrate it as much as they can with the room control systems (Crestron).

I have seen in RoomOS for Collab Devices (cisco.com) there are several xapi commands that appear they should work in MTR mode, such as xpi.Command.Call.Disconnect(); which should hang up the call.

Has anyone actually used the xapi integration on a live Cisco MTR end point, and how succesful were you?

Also, the client has expressed an interest in custom pages for the MTR, such as you get with Crestron Flex and Qsys integration.  With a navigator panel in 'standard' Cisco mode you can add pages to the touch panel, but can you do anything like this when in MTR mode?  I have seen you can swipe in from the right on the Navigator to bring up some addtional Cisco controls above and beyond what MTR offers, but can you add extras, and do the in built ones report back to the xapi in any way?

Thanks for any help or guidance anyone can provide!

Ben.

[sveistef]

in MTR-mode, you can add custom buttons on the control panel (The panel you swipe in from right), but you're right, Cisco cannot change the Microsoft controlled UI inside the MTR application.

When it comes to xAPIs, your source of knowledge is the best source, and the documentation is correct. However, it may not have the effect you're expecting.
Yes, we can now do xcommand Dial, but what that will do is set up a call from the underlying RoomOS layer, not from within the MTR application. We also have the closely related xCommand Webex Join and xCommand Zoom Join apis working in the same way from this layer. The effect is that the xAPI also also cannot hang up an MTR call, as it is operating outside the MTR container itself.

From an integration standpoint however, integrating with qsys etc is fully possible, as the RoomOS layer is responsible for media going into and coming out of the container, so we're able to control all of this with xAPI, and the container is none the wiser we did anything. A good example is the "Share source" button in the control panel, that allow you to select what input to share. That is RoomOS routing a different physical input into the container as the source for content sharing.

How this helps your understanding of the inner workings of RoomOS, and that it will help you do you want and need.