©2008 LifeSize Communications. All rights reserved.
August 6, 2008
6
Feature Support or Limitation
Case sensitive features The following features in the LifeSize Gatekeeper Administrator web
interface are case sensitive:
•The search function in the Endpoints tab
•E-mail forwarding/fallback rules
Known Issues and Workarounds
The following table lists known issues and their solutions or workarounds, if available.
Issue/Problem Description/Workaround
Changing default installation
port causes part of interface
to not function properly.
Changing the default LifeSize Gatekeeper installation port (port 80) causes
the Product Family Entry Point web interface to not operate properly.
IP address of NIC used for
generating license key must
be enabled.
When working with two NIC cards in your server, do not disable the IP
address belonging to the NIC that was used for generating the license key.
Line Hunting fails when two
or more Gateways are
registered to the LifeSize
Gatekeeper, and one
returns a
destinationRejection reason
in the Release Complete
message.
Line Hunting fails when two or more Gateways are registered to the
LifeSize Gatekeeper, and one of the Gateways returns a
destinationRejection reason in the Release Complete message. In such
cases, the LifeSize Gatekeeper attempts to connect calls only through the
Gateway which returns the Release Complete message and ignores other
registered Gateways.
SNMP trap resent when
Master and Slave Gatekeeper
licenses are not identical.
The gkAlterNoRedundancy SNMP trap is cleared and resent approximately
every 30 seconds if the Master and Slave Gatekeeper licenses are not
identical.
Authentication does not work
when LifeSize Gatekeeper
connects to LDAP server
without a password.
When the LifeSize Gatekeeper connects to the LDAP server without a
password (as an anonymous user), the authentication process does not
operate.
Gatekeeper check boxes
appear unchecked. When a Neighbor Gatekeeper has two zone prefixes, Gatekeeper check
boxes appear unchecked when you re-edit inter-zone rules.
Reduce bandwidth feature
not supported with more than
one zone.
The reduce bandwidth feature is not supported when working with more
than one zone.
With prefix stripping
disabled, devices register
using a number that begins
with the zone prefix.
When prefix stripping is disabled, devices can register with the LifeSize
Gatekeeper using only a number that begins with the zone prefix.
Inconsistent bandwidth
reporting. Bandwidth reporting through the LifeSize Gatekeeper is inconsistent. In the
Call Control tab and the CDR, the bandwidth displayed is full duplex. In the
Bandwidth Policy section and in the Inter-zone Bandwidth Rules dialog
box (both accessed through the BW Policy tab), the bandwidth displayed is
half duplex.
Viewing log files through the
FTP server with Windows
2003.
You cannot view log files through the FTP server when working with
Windows 2003. To solve this problem, enable an anonymous user in the IIS
settings.
