User manual POLYCOM LIVEMANAGER 3.1.007 RELEASE NOTES

[. . . ] You may optionally install the Web enabling package during the install process. The LiveManager Service can be started or stopped using the Windows NT Services Control Panel like any other Windows NT Service. I. Web Enabling Package Install Option Before you can install the Web Enabling Package (WEP) on your NT server or workstation, you must have installed the following two services: · Window NT WWW Service -- IIS (Internet Information Service) or Peer Web Service · Microsoft Active Server Page -- Found on your Windows NT service pack 3 CD If, during installation, you select to install the WEP and the above two services are not detected, the WEP will not be installed. II. Installation Notes NOTE 1: Attempting to install LiveManager 3. 1 after canceling out of the install program may result in an error message stating that there is not enough disk space. [. . . ] Extended Name Resolution Extended Name Resolution is yet another method to resolve an alias to an IP address. This method uses the network's DNS (Dynamic Naming Service) to provide the translation. Click on the Advanced button in the Call Control section of the LiveManager console. . Click Extended Name Resolution in the Advanced Call Control dialog box. Web Enabling Package The Web Enabling Package (WEP) provides you with remote Web browser access to certain LiveManager status and statistics files that would normally be viewed through the LiveManager console. You can view the Endpoint List, Events Log, Status Log, and optionally, the Active Connections List and Historical Calls Log. Prior to installing the WEP, you must have installed the following services on your NT workstation or NT server: 1. Internet Information Service (server) OR Peer Web Service (workstation) 2. Microsoft Active Server Page The IIS or Peer Web Service software is found on your NT server/workstation distribution CD. The Active Server Page software is found on your Windows NT service pack 3 CD. You have the choice of installing all of it, part of it or none of it. If you want to install all options, including access to call information files, select the Web Enabling Package and Call Information checkboxes in the Install Options screen during the installation process. If you want to access only the status files (no call information) deselect the Call Information checkbox. If you do not want to install any of the WEP, deselect the Web Enabling Package checkbox. Note: If the IIS / Peer Web Service or Active Server Page services are not detected during the installation process, the WEP will not be installed. As part of the WEP install process, you will be asked for contact information about the individual designated to administer the LiveManager Service. This information includes the following: · · Location Contact Person · · Phone Number Alias The alias is a name for the LiveManager installation directory. The default alias for the LiveManager installation directory is "livemgr. " After the contact information is entered and installation is successfully completed, you may use the web browser to access certain LiveManager status and statistics files. To use LiveManager's WEP feature, start your web browser and navigate to the following location: http://[host name]/[alias]/livemgr. asp Example: You installed LiveManager with the WEP option on host N112H202 and you specified the alias to be "gatekeeper. " Your URL (Uniform Resource Locator) is: http://N112H202/gatekeeper/livemgr. asp IV. New LiveGateway Console Application A new LiveGateway console application provides you with remote access to gateway status and partial configuration capability. [. . . ] NT Service Packs It is highly recommended that you run the NT system with the latest Service Pack from Microsoft. At the time these Release Notes were written, the latest version was NT Service Pack 3. IV. Multiple LiveManagers On The Same Subnet In the unlikely event that you need to install more than one LiveManager on the same subnet be aware that bandwidth management will not limit Out-Of-Zone calls between LiveLANs on that subnet. You will need to manipulate the subnet descriptor and subnet mask in such a way as to virtually divide the subnet. For example, suppose you install two LiveManagers, LM1 and LM2, on subnet 140. 240. 112. xxx. [. . . ]