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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] Cisco TMS will also set the endpoint to contact the Cisco TMS server every 15 minutes. This will be the heartbeat that allows for communication between the Cisco TMS server and the remote system, and any change that is done on the remote system or in Cisco TMS will be synchronized through this heartbeat. Cisco TMS Administration Guide Page 15 of 37 Support for remote systems Adding a remote system to Cisco TMS A system already added to Cisco TMS The easiest way to add a remote system to Cisco TMS is to first have the system registered in Cisco TMS before you bring it home. Before you unplug it, go to Edit Settings in the Settings tab for the system and click Enforce Management Settings. If the system will be behind a firewall that is not open or doesn't have HTTP or HTTPS ports opened up, you also have to go to the Connection tab on that endpoint and change System Connectivity to Behind Firewall. Cisco TMS will then set the management address on that system to Cisco TMS external management address. When the system is plugged in at home, the system will then send a boot event to Cisco TMS and from then on the system will be available from Cisco TMS. A system not added to Cisco TMS If you want to use an endpoint that has not been added to Cisco TMS before it is plugged in at the remote location, you will need to set the external management address of Cisco TMS on the endpoint. This can be automatically done by the DHCP server (see section Configuring the DHCP server) or manually on the endpoint. With F5. x and L4. 1 this must be done using telnet, while F6. x and L4. 2 (and newer) have this in the endpoint's menu: 1. Type telnet <ip-address of the endpoint> (This can be displayed on the endpoint by pressing the Up arrow and then the Left arrow. ) Type password if needed 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. This configuration is correct by default, but if it has changed, type `xConfiguration ExternalManager Path: "tms/public/external/management/systemmanagementservice. asmx"' Type bye When this has been set, the endpoint will send a register event to Cisco TMS, and when Cisco TMS receives this and notices that the system is not already in Cisco TMS, it will add it to a list. 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. 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. 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). [. . . ] During the installation of Cisco TMS the sa account on the SQL server is automatically chosen to create and access the database. A different account can be specified by choosing the Custom installation. The account used to run and upgrade Cisco TMS must have db_owner permissions to the tmsng database, while a user that also has access to master. mdf is required for creating the tmsng database the first time. Symptoms Cisco TMS does not load and/or you get a stack trace declaring that the SQL server is unavailable: SQL Server does not exist or access denied is displayed How to fix Make sure that the SQL server is running. This can be done by checking the SQL agent of the server, or going into services and verify that the MSSQLSERVER service is running. [. . . ]