- ページ 6
電話 3Com NBX V5000 Chassis - SuperStack 3 NBX V5000 ChassisのPDF リリースノートをオンラインで閲覧またはダウンロードできます。3Com NBX V5000 Chassis - SuperStack 3 NBX V5000 Chassis 8 ページ。 Business telephone
3Com NBX V5000 Chassis - SuperStack 3 NBX V5000 Chassis にも： クイック・リファレンス・マニュアル (2 ページ)
ページを印刷する
3Com NBX Networked Telephony Systems Release Notes for R5.0.6
•
On a system where Trunk-to-Trunk transfers are enabled, a caller that dials into the NBX system from the
PSTN and is then transferred to an integrated voice response (IVR) system over a PRI connection,
cannot select options on that IVR system. The NBX system does not correctly transmit the DTMF tones
that are sent when the caller presses buttons on the phone. This issue exists only in R4.1.71 and higher
releases. A workaround exists for this issue. However, the workaround causes a different issue if the call
is forwarded to a 3Com V3700 Unified Messaging System. For information on the workaround, contact
the 3Com Customer Service Organization. (ID 3696)
•
3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Cards do not support the NBX IP On-the
Fly feature. If your system uses IP On-the-Fly, then you must assign a static IP address to the card or
use DHCP to assign an IP address to the card, even if the card will be installed on the same subnet as
the NCP. (ID 3700)
•
If you enable System Settings > Audio Settings > Digital Line Cards Additional Echo Suppression, the
new setting does not take effect until you reboot the line cards. (ID 24570)
NBX System Software
•
The SuperStack 3 NBX V5000 cannot load a DSP patch if the,/htfs0/tmp/patch/Platform.cfg file exists and
contains "Legacy". (ID 25036)
Hunt Groups and Calling Groups
•
Linear hunt group behavior is inconsistent when the hunt group members are bridged extensions. This
example of a four-member hunt group illustrates the behavior:
1000 is first in the hunt group and it is a primary bridged extension.
1001 is second in the hunt group and it is the first secondary bridged extension of 1000.
1002 is third in the hunt group and it is the second secondary bridged extension of 1000.
1003 is fourth in the hunt group and it is the third secondary bridged extension of 1000.
A call to the hunt group extension rings extension 1000. The bridged station appearances on all
secondaries ring and light up, and the call is forwarded to the voice mail of the hunt group if no one
answers the call. If you remove the secondary bridge on extension 1002, a call to the hunt group rings
extension 1000, and the bridges 1001 and 1003 ring and light up. Then 1002 rings as a member of the
hunt group. Then 1003 rings as a member of the hunt group. If no one answers, the call is transferred to
the voicemail of the hunt group. (ID 3664)
•
Warning code 712b can appear on a telephone's display panel when a VTL call is forwarded back to a
hunt group on the system from where the call was forwarded. (ID 24742)
Supervisory Monitoring
•
If the customer's Caller ID information cannot be displayed on one line on the display panel of an agent's
telephone, a Supervisory Monitoring session initiated by a manager may be apparent to the agent due to
the refresh behavior of the telephone display panel. For example, a customer with a long name 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 24504)
Page 6