Helpful Hints - Polycom PictureTel 140 Release Note

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.
You describe LM1's and LM2's topology as containing segments 140.240.112.0 and *.*.*.* (Out-
Of-Zone) with a subnet mask of 255.255.255.0. A LiveLAN may register to either LiveManager.
You can "divide" the subnet between the two LiveManagers by describing the topology a little
differently.
Describe LM1's topology as containing segments *.*.*.* (OOZ) and 140.240.112.0 with a subnet
mask of 255.255.255.128. Describe LM2's topology as containing segments *.*.*.* (OOZ) and
140.240.112.128 with a subnet mask of 255.255.255.128. Now, by using this topology, all
LiveLANs with an IP address ending in 128 or higher may register only to LM2 and LiveLANs
with IP address ending in 127 or lower may register only to LM1. Calls between LiveLANs on the
140.240.112.xxx subnet between the two zones will be correctly managed with respect to
bandwidth.

Helpful Hints

1. File Pruning By Age - Entries in the log files (
than seven days are automatically deleted from the files.
2. Gateway Prefixes - Gateway Dialing Prefix support has been enhanced to support H.323
version 2 gateway features. LiveManager 4.01 provides mapping of a "User Prefix" to a
gateway prefix supplied by a registered gateway or to the "Default Prefix" which you
specify. See the PictureTel 140 LiveManager Installation and Administrator's Guide for
further information.
3. Saving UI Edits - In the Web UI, click the "
made on the current page to disk. Otherwise, the edits will not be read and you will lose
them when you navigate to a different page or log off or terminate the browser. You can
verify that your changes were accepted by clicking on the "
page. Your changes should still be visible.
4. Updating Status and Log Files - When you view the Status and Log Files, you view each
of them in a separate browser session. To view the most recent information, click on the
browser
Refresh
5. Recalling Opened Status and Log Files - When you open a Status or Log Files browser
and minimize it or send it to the background, you must select it on the taskbar to bring it to
the foreground. Clicking on the UI page's Status or Log Files buttons will not bring it to the
foreground.
6. UI Access Across Subnets - When using the Web UI in a browser on an NT system, if you
log onto a LiveManager server that is on a different subnet and are unable to successfully
access the status or log files, you may be experiencing an NT access violation. You will have
to log onto the server to let it authenticate you. Go to START->FIND->COMPUTER-
>{computer name}. This will prompt you for a username and password. Type in your
username and password. If you are able to successfully log on, you should now be able to
click on the Status or Log Files to view those files. You may experience similar symptoms if
or button.
Reload
events.txt, events.txt.v, raslog.txt
" button to save the changes you've
Submit to Disk
Refresh From Disk
) which are older
" button on each