User manual TANDBERG TELEPRESENCE MANAGEMENT SUITE ADMININSTRATION GUIDE 13.0

[. . . ] Cisco TelePresence Management Suite Administration Guide D13741. 12 December 2010 Cisco TMS Administration Guide Page 1 of 37 Table of Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 ISDN zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Area code rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] However, if Automatic System Discovery Mode for SoHo has been enabled, the system will be added in the default folder specified in the Administrative Tools > Configuration > Network Settings. Setting an endpoint in public If your system is in public, not behind a firewall or behind a firewall that has opened up the HTTP or HTTPS ports, it is advised to change the system connectivity on the system to Reachable on Public Internet. This way it will also be possible for Cisco TMS to set up calls where the endpoint is calling out, and not only being called to. Booking A booking in Cisco TMS including remote systems can be done like any other booking. However, as Cisco TMS is not able to communicate directly to a remote system that is behind a firewall, it is not possible for Cisco TMS to ask the endpoint to initiate a call. The endpoint must therefore be dialed into. If two or more systems that are behind a firewall would like to call each other, then an internal system with multisite must be included in the call. Phonebooks The phonebook will work in the same way as if the system was located on a LAN. When the endpoint is requesting the phonebook, it will send the request to the Cisco TMS server where Cisco TMS creates the . xml file and sends it back to the endpoint as the response. Cisco TMS Administration Guide Page 16 of 37 Support for remote systems Software upgrade Software upgrade on remote systems is set up in the same way as software upgrade on internal systems. However, the mechanism used to upgrade the system is different. When you have scheduled the upgrade, Cisco TMS will say that the upgrade went successfully. What has happened is that Cisco TMS has put the upgrade on hold until it gets a boot event from the system. When Cisco TMS gets this boot event, it will see that an upgrade has been scheduled for that system. On the reply to the boot event, Cisco TMS will send the endpoint a URL where it can get the software package. This URL is defined in Administrative Tools > Network > General Network Settings. It is recommended that the directory is left to the default (tms/public/data/software) as this is where Cisco TMS populates its list of packages from (Systems > System Upgrade > Software Manager). In other words, if you provide a different URL, you might end up scheduling an upgrade with a package found in the list that is not found in the URL specified. Statistics and monitoring The statistics and monitoring of the remote systems will be made up the same way as systems that are on the LAN, by sending event traps to Cisco TMS. As for retrieving status and detailed call information (`status. xml' and `history. xml'), these are sent every 15 minutes. The configuration of the system (`configuration. xml') will be sent on demand (Clicking Force Refresh in Cisco TMS) or when doing changes in Cisco TMS. Ad hoc calls will not be shown for systems behind a firewall as the TMSLiveService service is not able to contact the system to get information about the call. Cisco TMS configuration To allow for the remote systems to communicate with the Cisco TMS server, Cisco TMS needs to be reachable from the remote system. There are several ways that this can be done: Alternative: Description Put the Cisco TMS in public Put the Cisco TMS in DMZ Use a proxy This option provides less security, and makes the Cisco TMS vulnerable for attacks directly over the Internet. This option provides a bit more security. Port 80 (HTTP) needs to be open in the firewall to allow for incoming traffic. This option provides the best security without having to have two separate Cisco TMS servers, and is set up by having the proxy forward to the Cisco TMS server requests that are made to the management address path of the Cisco TMS server. · · · /tms/public/external/management/systemmanagementservice. asmx /tms/public/feedback/code. aspx /tms/public/external/phonebook/phonebookservice. asmx Have two Cisco TMS servers, one on the inside and one in DMZ talking to the same database · /tms/public/feedback/postdocument. aspx This will allow you to add and manage the internal and external systems seamlessly, but requires some extra configuration of firewalls and the external Cisco TMS server. [. . . ] Run an osql script towards the database and see if it returns any data. This script will return the number of systems in the Cisco TMS database: · Depending on the SQL configuration, run one of the commands below from the Cisco TMS server itself. · · osql -E -d tmsng -Q "select count(*) from objsystem" osql -E -S . \SQLTMS -d tmsng -Q "select count(*) from objsystem" Cisco TMS Administration Guide Page 34 of 37 Troubleshooting the Cisco TMS components Verify that the information Cisco TMS uses to connect to the database is correct. This information was historically only stored in the registry, but is now also stored encrypted in the web. config file. [. . . ]