3Com NBX Networked Telephony Systems Release Notes for R5.0.6
Page 7
TAPI (NBXTSP)
•
Only one conference call at a time may be made on an extension via TAPI. Using a 3Com telephone, a
user can create a conference call, place the conference call on hold, and then create a second
conference call. The user can then switch back and forth between the conference calls by putting one or
the other on hold. Using TAPI, a user can set up a second conference call, but the first conference call
can no longer be retrieved. (ID 22726)
•
The Application LCD Text (ALCD) feature allows a TAPI application to replace part of the display on a
LCD-equipped 3Com phone with a string. An ALCD string should be sent only when a call is offering,
proceeding, or connected. However, a “success message” (NBXUPDATELCDFORCALL_COMPLETED)
is erroneously returned by the NCP to the TAPI application when the phone is in DIALTONE state. The
NCP should return NBXUPDATELCDFORCALL_NOTONCALL instead. (ID 24908)
•
Original CallerID information does not replace ALCD text when a Menu is active on the telephone display
panel. For example:
The system sends an ALCD Text string to a user on an active call.
The user interacts with the menu interface on the display panel and then finishes using the menu.
When the user exits from the menu system on the phone, the ALCD text appears on the display panel
instead of the original CallerID. (ID 24905)
•
If you park a call from a 3103 Manager’s Telephone and then unpark that call from the same telephone,
ALCD text does not appear on the telephone’s display panel. (ID 25008)
•
When the NBXTSP initializes, it can be out of sync with the NBX system that it is monitoring and result in
a call being active on an extension but undetected by the PC. Both physical telephones and WAV phones
can be subject to this condition. (ID 25027)
•
If you invoke the ALCD Text feature several times on the same call almost simultaneously, not all of the
LINE_REPLY messages will be returned. Currently, the NBXTSP keeps one pending LINE_REPLY per
function invocation. (ID 25028)
Telephones
•
To upgrade an NBX system to R5.0 software, you must start from NBX Release R4.2.7 or higher. If you
upgrade from R4.2.6 or an earlier release, and then later reboot to that earlier release, newer 3Com
telephones become disabled and the error message "checksum error" appears in the telephone display
panel. See the
NBX System Software Upgrade Instructions
for detailed information on upgrading your
system. (TT ID 5291)
•
3Com 3103 Manager’s Telephones and 3100 Entry Telephones cannot communicate over layer 3 (IP)
with telephones that are connected to the NBX system through a Citel (Legacy Link) Gateway for Nortel
Norstar Card or a Citel (Legacy Link) Gateway for Meridian Card. The call will be connected but the
phone will not receive audio from the 3Com phone phone. (ID 24671)
•
Telephones that are connected to the NBX system through a Citel (Legacy Link) Gateway Card do not
play the tones that indicate that a Supervisory Monitoring session has been activated. (ID 24472)
•
A 3Com Telephone can display invalid messages on the display panel under the following conditions:
An Account Code is active.
The user initiates a conference call with an external number or transfers a call to an external number.
If the user tries to complete the blind conference or transfer without first entering an Account code, an
“invalid” message appears and the user is prompted to “Make Call First.” That message times out and
then another message prompts the user for an Account Code. If the user then enters an Account Code,
the call is completed. (ID 24636)
