Adding a remote Codian MCU to TMS

[Maulik Shah]

Hello

  Working with a client of ours that wants to trial TMS as they have Codian MCUs and Tandberg EPs, however they have a somewhat unique setup that am not sure if it will work. The TMS is on a trial basis and is hosted in the office but their MCUs are in a Colo which have a security separation between them (TMS cannot be installed in the Colo for now). The issue is SNMP is not allowed between the office and Colo currently, working with the security guys on this but it may take a while. The question was - is there a way to remotely adminster the Codian MCU with TMS (13.2.1)? All docs I saw stated TMS discovers MCU via SNMP (

http://www.cisco.com/en/US/docs/telepresence/infrastructure/articles/mcu_tms_configure_work_together_kb_288.shtml) but I also see TMS supports remote / SOHO devices. Is there a way to make the Codian register in the same way as below:

4. Type xConfiguration ExternalManager Address: “<dns name of the TMS server>”. If you are using a proxy, type the dns name of the proxy server instead.

5. This configuration is correct by default, but if it has changed, type ‘xConfiguration ExternalManager Path: “tms/public/external/management/systemmanagementservice.asmx

If not is there any other way to add the MCU statically in TMS instead of discovering MCU?

Another question was they have changed the admin interface on MCU to be port 8080 instead of 80 (for security reasons) - will that work with the TMS? How does TMS know this information?

Appreciate any tips. Thanks

[Magnus Ohm]

Hi, when you say that the tms is on trial basis does it have a releasekey and trial option keys? Or does it actually say "Trial" in the bottom right corner?

SNMP is used to manage the old classic systems and to faster discover systems on the network but its not required.

If the unit is accessible from the tms on its http interface you should be able to add it. However i dont know how much use it will be if its Behind firewall, tms wont be able to manage it. The port 8080 is a port tms does not use to manage its systems. It uses 80 or 443 so by changing the port to 8080 makes it unmanageable by tms on http. Changing the port does not add that much security :) you could try https.

The bottom line is that if the unit is behind firewall and tms's http communication is not working then managing the system in tms would be pointless. Tms is always recommended to have full access to the mcu. Regular endpoints can be behind firewall as tms will tell the mcu to dial the endpoints in a conference scenario. But then tms needs to be able to send http traffic on port 80 or 443 to the mcu and vice versa.

/Magnus

Sent from Cisco Technical Support iPhone App

[Maulik Shah]

Thanks Magnus for the response. I meant it has the trial in bottom right corner - what is the difference in the 2?

So how does the TMS know about the MCU or vice versa from a discovery standpoint. I think I can convince the security guys to allow HTTPS (443) bidirectionally but what am not sure is how to tell MCU the TMS IP and send a request or have the TMS add an MCU? If I go to Add Systems / Add Room / Equipment - the type options are Room, Digital Camera, Projector, DVD player, Document Camera, VCR, Laptop, Video Camera, Other Equipment.

Thanks in advance

[Magnus Ohm]

Hi,

You just go to add systems and type the mcu ip address. Check the "add non snmp systems. But in the tms
network settings you need to enable secure communication only mode. You also need to make sure tms is listening on https. Trial version has very limited functionality. Some are provided with timed licenses to be able to see te additional functionality. But this is something cisco sales is arranging.

/magnus

Sent from Cisco Technical Support iPhone App