3com NBX 100 Release note

Brand: 3com

Model: NBX 100

Type: Release note

This manual is also suitable for

Release Notes for NBX

Release R5.0.6

(Maintenance Release)

September 2, 2005

NBX V3000

SuperStack3

NBX V5000

NBX 100

Applications in Release R5.0 .......................................................................................................................2

Problems Corrected in This Release............................................................................................................2

Known Anomalies and Considerations in Release R5.0.6...........................................................................4

CAUTION: 3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Card can have their flash

memory corrupted if you remove power from the cards or remove the cards from the NBX chassis while

they are receiving their download after a system upgrade. (TT ID 5306)

License Note: NBX R5.0 is a major release of system software and requires a chargeable license key to

enable it. This license key is pre-installed on new systems at no charge. If you are upgrading the software

of an existing system, you must purchase and enter an NBX 5.0 license key into the NBX NetSet™ utility to

fully enable the R5.0 software. The system allows you to install the R5.0 license key prior to or after you

install the R5.0 software on the system. If you are running any previous release of NBX system software,

you need only purchase the R5.0 license to upgrade. If you already have an R5.0 license, you do not need

a new license key to install and run R5.0.6. For complete upgrade instructions, see the NBX System

Software Upgrade Instructions available on the NBX Resource pack CD or from the Support and

Downloads area of www.3com.com (upgr_nbx50.pdf).

NBX Call Reports Note: The Call Data Record format has changed at NBX R5.0. If you are using NBX

Call Reports R4.3 or lower, and you want to continue to use NBX Call Reports to view calling data, you

must uninstall NBX Call Reports, purge existing call data, and then install NBX Call Reports R5.0. For

detailed instructions, see the NBX System Software Upgrade Instructions.

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may be registered in other countries.

3Com, the 3Com logo, NBX, and SuperStack are registered trademarks and NBX NetSet and pcXset are trademarks of 3Com

Corporation. Other brand and product names may be registered trademarks or trademarks of their respective holders.

Rev NBX-All – September 2005

3Com NBX Networked Telephony Systems Release Notes for R5.0.6 Page 2

Applications in Release R5.0.6

NBX R5.0.6 contains these optional applications:

• NBX Complement Attendant Software R5.0.4 • NBX TAPI Service Provider R5.0.3

• NBX Call Reports R5.0.4 • NBX Palm Dialer R1.1.3

• NBX ConneXtions Gateway R4.0.1 • 3Com Network Supervisor V4.0.1

• NBX pcXset™ Soft Telephone R5.0.4

• NBX Desktop Call Assistant R5.0.3

• NBX Media Driver R5.0.4 • 3Com Telephone Local Configuration

Application R1.0

Problems Corrected in This Release

Automated Attendant

• Time dependent greetings now work when they are set to be active only on Thursdays. (ID 24859)

Automatic Call Distribution

• The ACD groups list that appears in the NBX NetSet utility is now sorted numerically instead of being

sorted according to the order in which the groups were created. (ID 24496)

Complement Attendant Software

• Complement Attendant Software (CAS) no longer reports a license failure error when there is a valid

license in effect. (ID 24527)

• Initiating a conference call too quickly after applying an account code can no longer cause CAS to

suspend operations. (ID 24115)

• Double clicking the Release button while a call is active no longer causes an error. (ID 24544)

• A call can no longer be placed in an indeterminate state during a transfer if the original caller hangs up

before the transfer operation can complete. (ID 24444)

• CAS now loads the entire user directory instead of just the first 300 users. (ID 24675)

• A checkbox now appears during installation to allow you to choose whether CAS will start automatically

each time the host computer is started. (ID 24491)

• A transfer or conference no longer fails while the results of a Send MWI, (Message Waiting Indicator),

Cancel MWI, or Assign Account Code are being displayed on the phone’s display panel. (ID 24550)

Call Coverage

• The Call Forwarding feature no longer causes “Feature Failed“ to appear on the telephone’s display

panel even though the operation completed successfully. (ID 23408)

• Call Forward Constraint now works correctly when the forwarding extension has a primary Bridged

Station Appearance. (ID 24229)

• The NBX system can no longer suspend operations when you have telephones forwarded in a loop and

the Do Not Disturb feature enabled. (ID 23550)

3Com NBX Networked Telephony Systems Release Notes for R5.0.6 Page 3

• During installation on a computer that is running Windows XP Pro SP2, a Windows File Protection

message no longer appears. (ID 24511)

Documentation

• The NBX Administrator’s Guide no longer includes the 3105 Attendant Console as a device supported by

the 3Com Telephone Local Configuration application. The application works with the 3100 Entry

Telephone only. (ID 24484)

• References to the Supervisory Monitoring feature in the NBX Administrator’s Guide no longer include the

claim that a supervisor can monitor a 911 emergency call. The updated version of the NBX

Administrator’s Guide has “Published August 2005” on the cover. (ID 25081)

Feature Codes

• Invoking Feature Code 971 no longer occasionally causes the NBX system to suspend operations.

(ID 24854)

Hunt Groups and Calling Groups

• Missed or answered calls into a Hunt Group now appear in a telephone’s Call Log. (ID 24716)

• You can no longer specify a hunt group’s extension as its own Personal or System Operator extension.

For example, the hunt group on extension 4000 cannot use extension 4000 as its Personal or System

Operator destination. (ID 24263)

Message Waiting Indicator to Phone

• MWI no longer causes the system to suspend operations under these conditions:

MWI Retrieve and MWI Cancel functions are mapped to telephone access buttons.

You press the MWI Retrieve button and select the option to delete ALL.

While the system is prompting you to confirm your selection, you press the MWI cancel button.

(ID 24896)

NBX Digital Line Cards

• Digital Line Cards 3C10165D (E1) and 3C10116D (T1) no longer apply VLAN tags to audio packets that

are addressed to a remote phone when IP VLAN is disabled. (ID 24592)

NBX Media Driver

pcXset Soft Telephone Client

• pcXset Soft Telephone Client has been updated with new graphics. (ID 24100)

Regional Settings

• The Regional Settings for documentation for Israel and Russia now display the correct description,

English. NBX documentation is not available in Hebrew or Russian. (ID 24366)

TAPI (NBXTSP)

• The new call forward features available in NBX 5.0 (Call Forward All, Call Forward Busy, and Call

Forward No Answer) can now be accessed from TAPI applications. (ID 24500 and 24501).

• A line dropped by TAPI lineDrop() on a line that was opened manually on a 3Com Cordless Telephone

will now stay dropped. For example:

3Com NBX Networked Telephony Systems Release Notes for R5.0.6 Page 4

Generate a Call from TAPI

When the call is connected, press the SA button to talk.

Drop the call from TAPI.

The call is now dropped — a new call handle is no longer opened. (ID 24764)

• When the called party invokes a feature code, the same reason code (0x28) is no longer always returned.

(ID 24393)

• TAPI applications can now use the NBX-specific Application LCD (ALCD) Text feature. This feature

allows an application to replace the first line of a LCD-equipped NBX phone with an ASCII string, while a

call is in progress, to, for example, replace caller ID displayed caller ID information. More information can

be found in the readme.txt document located in C:\Program Files\3Com\NBX\NBX TSP. (ID 24463)

• When using supervisory monitoring, attempting to drop a supervisor's call from TAPI using lineDrop no

longer results in a brief delay before the line actually drops. (ID 24760)

• The LINEGETCALLINFO structure returned by the TAPI function lineGetCallInfo() will now include the

number of the trunk over which an outgoing call is routed. In earlier NBXTSP releases, this value was

reported as unknown. (ID 24820)

Telephones and Line Cards

• A 3Com 3101 Basic Telephone or a 3102 Business Telephone that is attached to a PC through its switch

port no longer locks up during periods of heavy network traffic. (ID 24832)

• The NBX system will no longer occasionally suspend processing when a 3102 Manager’s Telephone

uses Supervisory Monitoring, Message Waiting Indicator to the Phone, or Call Forward All. (ID 24971)

• Telephones connected through Legacy Link or Citel Gateway cards now appear in 3Com Network

Supervisor. (ID 22963)

• The NBX NetSet utility no longer allows you to associate a primary bridged extension on a 3103

Manager’s Telephone to an attendant console. (ID 24027)

• A 3103 Manager’s Telephone no longer generates unexpected button sequences. (ID 24844)

• It is no longer possible for an NBX 100 to suspend operations when a user repeatedly presses the

Directory button or the Call Logs button on a 3103 Manager’s Telephone. (ID 25053)

• Echo is no longer heard on calls through the Analog Line Card port on the V3000 Analog (3C10600A)

and through the ports on the 3C10114C Analog Line Card. (ID 24612)

Known Anomalies and Considerations in Release R5.0.6

Complement Attendant Software

• If you installed Complement Attendant Software but not NBXTSP, you are prompted to launch CAS after

installation is complete. When you launch CAS, an error occurs because it detects that CAS is already

running. To clear the error, shut down CAS and restart it. (ID 24521)

• You cannot use a phone that is associated with a computer running Complement Attendant Software

(CAS) to invoke the Message Waiting Indicator (MWI) feature. (ID 24193)

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)

3Com NBX Networked Telephony Systems Release Notes for R5.0.6 Page 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)

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)

3Com NBX Networked Telephony Systems Release Notes for R5.0.6 Page 8

• The Directory that you access from the display panel of a 3103 Manager’s Telephone does not always

display the extension of a user with long first and last name. (24685)

• The Hold, Transfer, and Conference buttons can stop working on a 3103 Manager’s Telephone during

the following conditions:

Place a call from 3103 phone to another phone.

Press the soft key for the Actions icon on the right to display the Actions menu.

Press the soft key for the system appearance button on the left.

The Actions menu screen disappears but the Hold, Transfer, and Conference buttons may stop working

and the Actions menu option will disappear.

The same situation can occur if you press the system appearance button while you have Directory menu

or the MWI Retrieve menu active on 3103 Manager’s Telephone. (ID 25060)

• The user directory that you can access on a 3Com telephone’s display panel is not being updated

dynamically. For example, if an administrator uses the NBX NetSet utility to add or change a user record,

the directory may not display that change until after the NBX system has been restarted. The change

should be available as soon as the administrator completes the operation. (ID 24973)

VTL Connections

• If a Primary Bridged Station Appearance drops off from a conference call that is being carried by a Virtual

Tie Line (VTL) connection, the other two parties on the conference might lose audio or experience on

way audio. For example:

Ext. 1003 on NBX-Chicago

Ext. 1011 on NBX-Chicago (Primary BSA)

Ext. 2050 on NBX-Dallas

1. Ext. 1003 on NBX-Chicago makes a VTL call to Ext. 2050 on NBX-Dallas.

2. Ext. 2050 on NBX-Dallas conferences in Ext. 1011 on NBX-Chicago while the extension is ringing (a

blind conference).

3. Ext. 1011 on NBX-Chicago picks the call.

4. Ext. 1011 on NBX-Chicago drops the call; the conference call is still active on the other two

extensions, but those extensions have no audio or one way audio.

(ID 25123)

3com NBX 100 Release note

Brand: 3com

Model: NBX 100

Type: Release note

This manual is also suitable for

Download PDF

report

3com NBX 100 Release note

This manual is also suitable for

3com NBX 100 Release note

Related papers

Other documents