3Com NBX 100 Примечание к выпуску - Страница 11
Просмотреть онлайн или скачать pdf Примечание к выпуску для Шлюз 3Com NBX 100. 3Com NBX 100 11 страниц. Business telephone
Также для 3Com NBX 100: Примечание к выпуску (8 страниц), Краткое справочное руководство (2 страниц), Инструкции по обновлению программного обеспечения (4 страниц), Краткое справочное руководство (2 страниц), Краткое справочное руководство (2 страниц)
Печатать страницу
3Com NBX Networked Telephony Systems, NBX R6.0.14 Release Notes
calls an ACD group. The agent who answers the call sees the number the customer is calling from
and the portion of the customer's name that can fit on the display. The remainder of the name is
truncated. After a few seconds, the display panel of the agent's telephone is refreshed and shows just
the name of the customer. If the name is too long to fit on one line, it appears on two lines. This
behavior is normal for displaying Caller ID information. However, when a Supervisory Monitoring
session is initiated on that call or the mode of an existing Supervisory Monitoring session is changed,
the Caller ID information is refreshed, which means that it once again displays the customer's number
and the portion of the name that fits on the display, and then changes to display just the name.
(ID 29520 and ID 24504)
In the user portal of the NBX NetSet utility, the System Group Settings > Supervisory Monitoring tab
shows that a user can be monitored even when the Supervisory Monitoring feature is disabled
system-wide. (ID 45928)
TAPI (NBXTSP)
If you invoke the ALCD Text feature several times on the same call almost simultaneously, not all of
the LINE_REPLY messages are returned. Currently, the NBXTSP keeps one pending LINE_REPLY
per function invocation. (ID 29533 and ID 25028)
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 29535)
In the following situation the NBXTSP will be unable to perform operations on an extension.
Set up extension 1001 to point to a 3103 Manager's Telephone.
Begin a TAPI application.
Open a line to extension 1001 and perform some operation like making a call.
Finish using the application.
Use the NBX NetSet utility to reassign extension 1001 to a different NBX phone.
Open the application again.
Attempt to make a call.
At this point, nothing happens because extension 1001 is still known to be a 3103 phone. You must
restart the Telephony service to set up the phone objects properly in the new configuration. (ID 29541)
NBXTSP handles only one conference call per extension at a time. The NBXTSP can hold only one
conference call handle. Through TAPI, while the second conference call can be set up and held, the
first conference call can no longer be retrieved. Attempting to do so results in the call handle for the
second conference call being returned and the first conference call is lost. (ID 29556)
The lineGetDevStatus() function does not show the number of active and held calls for a SIP device
monitored via TAPI. (ID 33148).
In some cases, when a monitored extension receives an incoming call from a VTL extension and then
transfers that call to another VTL extension, an application may not receive confirmation that the
transfer was completed (for example, an IDLE notification). (ID 29928)
VTLs
If you have a VTL connection between a system running R5.0.x and another system running R6.0, a
call that is transferred to voice mail over the VTL connection might experience a shortened beep or no
beep at all after the prompt to record a message. (ID 33317)
Page 11