3Com NBX Networked Telephony Systems Release Notes for R5.0.6
Page 5
•
The first time you start CAS after installing it, a TAPI error message may appear.
You should click OK, and then restart CAS. If the error occurs again, uninstall and then reinstall the
NBXTSP to clear the error. (ID 24934)
Database Restore
•
An NBX100 system will allow you to import a database that is too large, for example a database backup
that was taken from an NBX V3000 or SuperStack 3 NBX V5000 system. However, if the database is too
large, the system could hang on reboot. (ID 22747)
Desktop Call Assistant
•
You cannot use a phone that is associated with a computer running DCA to invoke the Message Waiting
Indicator (MWI) or the Supervisory Monitoring features. (ID 24167 and 24168)
•
When installing the .NET framework version 1.1 on a Windows XP system, if you have changed your
Start menu to the Windows Classic start menu, the .NET framework install might terminate unexpectedly
with a general error. If this problem occurs, reset your Start menu to the Windows XP Start menu and run
the installation program again. After a successful installation, you can return to using the Windows
Classic Start menu.
NBX Call Reports (Call Data Recording)
•
Call data is incomplete under these conditions:
User A calls User B.
User A transfers User B to an External number.
User B and the External number are connected.
NBX Call Reports generates three records. The record for the step 1 (User A calls User B) is correct. The
records for the next two steps contain incomplete data. (ID 24408)
NBX Digital Line Cards
•
Digital Line Cards 3C10165D (E1) and 3C10116D (T1) do not support DHCP Option 184, which is used
by NBX devices to receive the IP address of the Network Call Processor. See the
NBX Administrator’s
Guide
for complete information on how to configure IP address information for these Digital Line Cards.
(ID 5109)
•
3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Cards do not support DHCP lease times
of less than 20 minutes.
•
T1.231 and TR 54016 Near End performance data does not accurately report severely errored framing
events. A severely errored framing event is reported when the number of framing bit errors exceeds 2 in
one second, which causes a greater number of severely errored framing events to be reported than
actually exist. (ID 3687)
