3Com NBX V3000 Analog Release Note - Page 9
Browse online or download pdf Release Note for Switch 3Com NBX V3000 Analog. 3Com NBX V3000 Analog 11 pages. Ip telephony solution
Also for 3Com NBX V3000 Analog: Release Note (8 pages), Upgrade Information (2 pages), Quick Reference Manual (2 pages), Release Note (4 pages), Datasheet (4 pages), Instruction Sheet (2 pages)
Print Page
3Com NBX Networked Telephony Systems, NBX R6.0.14 Release Notes
User B will reach the auto attendant and be prompted for the destination extension. However, the
Auto Attendant will not recognize any digits entered by User B.
(ID 45809)
Auto Discovery
Occasionally, the Auto Discovery process will not fully initialize a telephone. The device will appear in
the device list in the NBX NetSet utility, but the device does not have an extension number. Typically,
this issue occurs only with an empty database during initial configuration of a system To fix this issue,
use the NBX NetSet utility to remove the device and then run the Auto Discovery process again.
remove it (ID 33183)
Business Hours
There is 1 minute difference between the time for which you set a Business Hours setting and when
that setting actually goes into effect. For example, if you create an ACD Group that uses the System
Business Hours, which are set to be Open from 9 AM to 5 PM and with Lunch from noon until 1 PM,
the actual Open hours will end at 5:01 PM and the Lunch hour will end at 1:01 PM. (ID 38713)
Call Logs
Call Detail Records show a 1 in the CallComplete field for busy/unanswered calls. (ID 33388)
Caller ID
On a system where two or more SIP-mode NBX systems are tied together as trusted interfaces, Caller
ID information is not always accurate. For example, a call from NBX A goes to a phone on NBX B.
Then the system A caller transfers the call to a different extension on NBX system B. The caller ID on
both displays the caller ID of the SIP trusted interface. (ID 33157)
Call Transfer
CFA: FEATURE FAILED appears on the telephone display panel if the phone has been included in its
own coverage path. (An endless loop has been created.) For example, phone 100 has Call Forward
All enabled and set to forward calls to phone 101. Phone 101 has CFA enabled and set to forward all
calls to phone 102. Phone 102 is set to send calls to voicemail after 6 rings. If no one in the coverage
path answers a call to phone 100, after a few rings at phone 102, the display panel on phone 100
shows FEATURE FAILED. The same result occurs if phone 102 has CFA enabled and set to forward
calls to phone 100. (ID 24731)
If the Transfer Timeout value is less than the destination extension's Forward to Voice Mail value, a
transferred call can get disconnected. (ID 32223)
IP Conferencing Server
If you call into an NBX system over a PRI line and attempt to connect to an IP Conferencing system
conference, you hear the conference attendant, but when the attendant transfers you to the
conference, you sometimes hear MOT, but you never get connected to the conference. To avoid this
issue, do not enable music-on-transfer. (ID 46083)
Music-on-Hold
NBX is sending Music-on-Hold (MOH) traffic to the music multicast group, which causes excessive
network traffic. To work around this issue, after a system reboot, you must disable and then enable
MOH, System-Wide Settings > Enable Features System-Wide. Note that if Music-on-Transfer (MOT)
is enabled, it becomes disabled when you disable MOH. Be sure to enable MOT after you disable and
then enable MOH. (ID 46150)
Page 9