techguru69
IS-IT--Management
4.2.13 has been released AFTER the initial 4.3.3 release... hmmm. Anyone know what's up with this release?
thx.
thx.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Anyone have details on 4.2.13 release? 1
- Thread starter techguru69
- Start date
- Status
-
1
- #2
GoTellBigDaddy
Vendor
Release Notes for Release 4.2.13
• SuperStack? 3 NBX? Networked Telephony Solution
• NBX 100 Communications System
NOTICE: NBX software release R4.2.12 fully supports 3Com eXchange Call Center software version 4.33.00. See the 3Com eXchange Call Center release notes for upgrade information.
CAUTION: Be aware that, if you are upgrading your NBX system software from the Beta testing version to the final released version of R4.2, Beta versions of these hardware components will no longer be supported:
• 3Com Model 3102 Business Telephone
• Single-port Analog Terminal Adapter (3C10400)
(IDs 3965, 3966, and 3967)
NOTICE: Before you can upgrade your existing NBX system to Release 4.2 software, you must first upgrade to Release 4.1 or a more recent release. See the NBX Administrator’s Guide for details.
NOTICE: Starting with Release 4.2, the NBX system software requires a license. Upgrades from previous releases must be done with this requirement in mind. See page 5 of these release notes and the NBX Administrator’s Guide for details.
CAUTION: After you upgrade to Release 4.2 from a previous release, you must back up the licenses on your NBX system. If you do not back up the licenses and the system disk is lost for any reason, you will not be able to restore your licenses after you replace the system disk.
NOTICE:
• The SuperStack 3 NBX system is shipped with a 4-digit dial plan. If you import a 3-digit plan, you must manually specify any 3-digit extension ranges that are not set by the imported plan.
• The NBX 100 is shipped with a factory default 3-digit dial plan. If you import a 4-digit plan, you must manually specify any 4-digit extension ranges that are not set by the imported plan.
CAUTION: If you use the 3Com SuperStack II Advanced Redundant Power Supply as a backup power supply for the SuperStack 3 NBX Gateway Chassis, the Gateway Chassis can contain no more than two Analog Terminal Cards (3C10117 or 3C10117A). There is insufficient power for a third or a fourth ATC, and the NBX system will not operate properly. Any other NBX cards except the Network Call Processor Card can be configured in the remaining two slots.
This restriction does not apply to the new 3C10117C Analog Terminal Card. (ID 1313)
CAUTION: 3Com suggests that you connect no more than 50 TAPI clients to any one NBX system. For more than 50 TAPI client connections, 3Com recommends that you install the Microsoft Remote TSP software on a Windows NT PC.
NEW FEATURES IN RELEASE 4.2
New 3Com Model 3102 Business Telephone
The 3Com Model 3102 Business Telephone is a new design of the Business Telephone. It shares the same core capabilities as previous models with a number of improvements to its appearance and design, including:
• Headset Jack – You can connect a headset directly to the Model 3102 Business Telephone. A programmable button on the telephone enables or disables headset operation.
• The phone has an enhanced full-duplex speakerphone with superior voice quality.
• The new, one-piece stand offers 15- to 45-degree desk adjustments as well as a wall-mount position.
• All 18 programmable buttons include a status light (LED).
• Replaceable bottom bezels will be offered for localization of button names.
New Model of the Single-Port Analog Terminal Adapter (3C10400)
The new model operates with all of the same features as the previous models, plus these two new capabilities:
• Power over Ethernet (PoE) – The new model can supply power to devices that are compliant with the IEEE 802.3af standard.
• Diagnostic Port – The new model has a 9-pin RS232 connector (DB9) to which you can connect your PC using the appropriate cable and a terminal emulation software package such as Hyperterm.
Progress Indicators
During backup or restore your NBX database, or during your upgrade of the NBX system software, you now see progress bars in the NBX NetSet™ utility. Also, you can now cancel a backup or upgrade operation that is in progress.
Saving the Most Recent Backup File
You can now click a button on the Operations > Manage Data tab to save the most recent backup file. This shortcut enables you to save the most recent backup file to more than one location without performing another backup.
System Alert While a File System Check Is Being Performed
During a reboot operation, if a file system check (FSCK) is required, the NBX system now alerts you to this fact by flashing the Call Processor S1 and S2 status lights in an alternating pattern.
Enhanced Caller ID Information
When a call is forwarded, redirected, or transferred to you, the display panel on your NBX Telephone now shows caller ID information for the original caller and for the person who is forwarding, redirecting, or transferring the call to you.
NBX System Settings
Some NBX system settings have moved to a new Audio Settings screen (NBX NetSet > System Configuration > System Settings > Audio Settings). The new screen includes these configurable settings:
• System-Wide Silence Suppression
• System-Wide Silence Suppression on VTL Calls
• Audio Compression on VTL Calls
• NBX Handset Acoustic Echo Suppression (new setting)
• Analog Line Cards Additional Echo Suppression (new setting)
• Digital Line Cards Additional Echo Suppression (new setting)
See implementation instructions on the screen.
Enhanced Status of Analog Line Card Ports
The status screen for Analog Line Card Ports now includes information about the most recent five completed calls.
D-Channel Status Information for ISDN PRI
If you have a Digital Line Card configured for ISDN PRI operation, the Span Status screen in the NBX NetSet utility now includes status information about the D channel. You can verify whether the D channel is Online, Offline, or in an Unknown state.
Remote NBX Device Behind a Home Router or Firewall
You can now have a single NBX device such as an NBX Telephone in your home if you connect to the Internet through certain home router devices. See the testing report at the end of these Release Notes, and Chapter 3 in the NBX Administrator’s Guide.
Telnet
You can now establish a telnet session between your PC and the NBX system. This ability, which requires administrator login ID and password, can be turned on or off by the system administrator. By default, this setting is turned off.
Purging Voicemail
When you purge your NBX database, you now have the option of purging all voicemail from the NBX system. Later, if you restore your database from a prior backup, you can choose whether or not to restore voicemail if it is included in the backup.
Redirecting TAPI Calls
A TAPI Route Point is a virtual device (new in R4.2) that you can create using the NBX NetSet utility. It has an extension and can receive and queue multiple simultaneous calls for application-driven redirection to other telephone numbers. A SuperStack 3 NBX system allows up to 400 calls to be queued by TAPI Route Points. An NBX 100 system allows 50 calls to be queued.
You can configure TAPI Route Points to accept internal and external calls and queue them until they can be redirected by TAPI or until the calls time out. Calls that are redirected go to a destination specified by TAPI applications that are external to the NBX system. Calls that time out are sent to the call coverage point of the TAPI Route Point. TAPI Route Points can be useful if you are using the NBX system in a call center environment.
Calls to other devices that can be monitored by TAPI, such as Analog Terminal Adapters, Analog Terminal Card ports, NBX Telephones, and Hunt Groups can also be redirected by TAPI-enabled applications.
IP-on-the-Fly Licensing
All NBX systems are now shipped with the license for IP-on-the-Fly enabled. Users no longer need to purchase an IP-on-the-Fly license.
APPLICATIONS IN RELEASE 4.2
In addition to the Release 4.2 system software, Release 4.2 contains these applications:
• NBX Complement Attendant Software R4.2.4 • NBX TAPI Service Provider R4.2.10
• NBX Call Reports R4.2.2 • NBX Palm Dialer R1.1.3
• NBX ConneXtions Gateway R4.0.1 • 3Com Network Supervisor V4.0.1
• NBX Media Driver R4.2.4
(formerly WAV Driver) • NBX Desktop Call Assistant R4.2.2
(formerly TAPI Dialer)
• NBX pcXset? Soft Telephone R4.2.2
For all applications, see the 3Com Partner Access website or the NBX FTP site for the most up-to-date versions.
LICENSE ANNOUNCEMENTS
UPGRADING TO RELEASE 4.2 OF NBX® NETWORKED TELEPHONY SOLUTIONS
AND
INSTALLING THE 3COM® MODEL 3102 BUSINESS PHONE
NBX Release 4.2 is the first NBX software release that requires a license key to activate it, and the
3Com Model 3102 Business Telephone is the first 3Com Telephone that requires a license key to install it.
• To ensure a trouble-free upgrade to R4.2 for your NBX system, follow either Procedure A or Procedure B, described in this document.
• To install the 3Com Model 3102 Business Telephone, follow the instructions in “Installing the License Key for Model 3102 NBX Business Telephones,” later in this License Announcements section.
PROCEDURE A: INSTALLING THE R4.2 LICENSE KEY
BEFORE YOU UPGRADE (RECOMMENDED)
1. Purchase the R4.2 License Key from your 3Com NBX Voice-Authorized Partner.
2. If your NBX system is running a software release earlier than R4.1, first upgrade to any released version of R4.1 before you attempt to upgrade to R4.2.
Note: Before R4.1, the NBX system software did not recognize the R4.2 license as valid.
After you upgrade to R4.1, you can install the license key for R4.2 and the system accepts it.
3. After your system is running on R4.1, follow these steps to install the license key for R4.2:
a) Log in to the NBX NetSet™ utility using the administrator login ID and password.
b) Select Operations > Licenses > Add License.
c) Type the license key into the text box and click OK. The screen displays “License Unknown.”
4. Obtain the R4.2 software upgrade file and load it onto your NBX system. Then follow these steps:
a) In the NBX NetSet utility, select Operations > Software Upgrade > Browse and locate the software upgrade file. Then click Upgrade.
Wait until you see a system message that indicates that the upgrade file has been
successfully loaded. Typically, the process is complete in 30 minutes or less.
b) In the NBX NetSet utility, select Operations > Reboot/Shutdown.
c) From the Select version: list, select the R4.2 release that you just loaded and click Reboot.
Wait until you see a system message that indicates that the reboot operation has been
successfully completed. Typically, the process is complete in 30 minutes or less.
d) To verify that the system is now running R4.2, in the NBX NetSet utility, select
Reports > System Data. In the Runtime column, verify that the System item shows
R4.2.x, where x is the specific version of R4.2 that you loaded.
e) Save your newly updated License file by selecting Operations > Licenses > Backup Licenses.
PROCEDURE B: INSTALLING THE R4.2 LICENSE KEY
AFTER YOU UPGRADE
If you upgrade the system software to R4.2 before you install the license key:
• The NBX system advises you that you must install the license key or reboot to a
previous release that required no license.
• You can perform no NBX NetSet Admin tasks such as Move, Add, or Modify, except to enter the
license key or reboot to a previous release.
• NBX system users can make and receive internal and external calls.
• Users see “NO LICENSE” in the display panel of their telephones whenever their telephones
are active, for instance, when they pick up the handset to make or answer a call.
To install the license key:
1. Purchase the R4.2 license key from your 3Com NBX Voice-Authorized Partner.
2. Log in to the NBX™ NetSet utility using the administrator login ID and password.
3. Select Operations > Licenses > Add License, type the license key into the text box, and click OK.
4. Save your newly updated License file by selecting Operations > Licenses > Backup Licenses.
After you click OK, the R4.2 system becomes fully operational. You can now perform normal administration tasks in the NBX NetSet utility.
INSTALLING THE LICENSE KEY FOR
MODEL 3102 NBX BUSINESS TELEPHONES
Unlike other 3Com NBX Telephones, before you can discover any Model 3102 NBX Business
Telephones on an NBX system, you must install the appropriate license key.
For full instructions on installing telephones on an NBX system, see Chapter 3: Telephones
and Attendant Consoles in the NBX Installation Guide, which you can find on the
NBX Resource Pack CD or on the Main Menu window of the NBX NetSet utility.
To install the license key:
1. In the NBX NetSet utility, select Operations > Licenses > Add License.
2. Type the license key into the text box.
To verify that the new license key has been accepted:
3. Select Operations > Licenses. Verify that a license for Model 3102 Business Telephones is included in the list of licenses.
4. Save your newly updated License file by selecting Operations > Licenses > Backup Licenses.
Note: You do not need to reboot the NBX system for the new 3102 license key to take effect.
PROBLEMS CORRECTED SINCE RELEASE 4.2.7
ID numbers in parentheses are for internal 3Com use only.
3Com eXchange Call Center
• Previously, when there was an idle agent on the system, occasionally calls were not routed to an available agent and were not counted as queued. This problem no longer occurs. (ID 4602)
• If someone is connected to the Auto Attendant and makes a call to a hunt group, the person answering the call now sees the hunt group number on the LINECALLINFO line in the telephone’s display panel. (ID 4941)
• If "Handsfree on Transfer" is enabled system-wide, an external call that is redirected to an agent after being queued to an NBX TAPI Route Point extension no longer initiates Hands Free mode if the agent has enabled the Hands Free feature on the telephone. Hands Free mode applies only to internal calls. (ID 5096)
3Com Telephones
• In the telephone directory that appears on a 3Com telephone’s display panel, names that begin with lower-case letters, now appear in proper alphabetic order. Previously, all names beginning with upper-case letters appeared first in the list, followed by names beginning with lower-case letters.
(ID 5000)
Analog Terminal Card
• A caller now hears audio from a conferenced IP telephone under these conditions:
• A call is placed from analog telephone A to analog telephone B, both of which are connected to a 3C10117C Analog Terminal Card on NBX system A.
• NBX system A uses IP On-the-Fly and both telephone A and telephone B are Ethernet (layer 2) telephones.
• The caller conferences a third telephone into the call. The third telephone is on the same subnetwork as NBX system A, but is an IP (layer 3) telephone connected to NBX system B.
• NBX system B is on a different subnetwork than NBX system A.
• Previously, the caller on telephone A did not hear any audio from the IP telephone connected to NBX system B.
(ID 4895)
AudioCodes Gateways
• A caller no longer hears ringing instead of being immediately connected to a voice menu under these conditions:
• The call was placed from a SIP telephone connected to an AudioCodes box.
• The AudioCodes box was connected to an NBX system through an ISDN PRI line.
• The NBX system was connected to the Public Switched Telephone Network (PSTN) through an ISDN PRI line.
• The call destination was on the PSTN.
(ID 4903)
Automated Attendant
• If an Automated Attendant menu record becomes corrupted for any reason, the NBX system now boots properly and corrects the corruption. Previously, the corruption causes a system interruption during the boot process. (ID 5188)
• If, after recording an Auto Attendant prompt, you hang up the telephone without pressing the pound key (#), the voice mail port that you were using is properly returned to service. Previously, if you failed to press the pound key the voice mail port became unavailable for use. (ID 5198)
Automatic Backup
• Previously, if you used the automatic database backup tool and enabled the checkbox to include voice mail in the backup, voice mail was not included in subsequent backups. To include voice mail in the backups, you had to enable the check box a second time. Now, enabling the checkbox once is sufficient. (ID 5308)
Call Transfer
• If user A attempts to transfer a call to user B when user B was on a call, the message “On A Call” now properly appears in the display panel on user A’s telephone. Previously, this message did not appear. (ID 4926)
Caller ID
• When an NBX system is connected to some Northern Telecom DMS100 voice switches, caller ID information is now properly received from the telephone company equipment. (IDs 3990 and 3991)
• The system administrator can now select the way in which Caller ID information is transmitted from an NBX system to the Public Switched Telephone Network (PSTN) for forwarded or transferred trunk-to-trunk calls. Before NBX release R4.1.77, a call to an NBX system that was forwarded or transferred to an outgoing trunk contained the Caller ID information of the forwarding party, not the originating party. In NBX release R4.1.77 and later releases, a forwarded or transferred trunk-to-trunk call contains the Caller ID information of the originating party. However, some PSTNs do not connect calls unless the Caller ID information matches the forwarding telephone’s ID. Customers who want to send the forwarding party Caller ID on forwarded or transferred trunk-to-trunk calls must consult their CSO representative for the instructions on how to make a change to the nboss.cfg file. (ID 4929)
Citel and Analog Telephones
• On an analog telephone connected to an NBX system with a Citel Gateway board, a caller who enters Feature Codes 403 through 408 now properly sees a “Not Supported” message in the display panel of the telephone. Previously, the caller inappropriately heard an error tone and the display panel flashed, but did not contain the appropriate message. (ID 4766)
Digital Line Cards
• If, in the NBX NetSet interface, you reconfigure the IP settings on a Digital Line Card and change only the default gateway address, the change now occurs. Previously, such a change did not occur unless at least one other parameter was also changed. (ID 4608)
• Previously, if an incoming call contained a user-to-user Information Element that was empty, the NBX system inappropriately generated an error message. No message is now generated because this situation is allowed according to the specification. (ID 4905)
• On some trunk-to-trunk call transfers, if the called number was busy, the NBX system disconnected the call instead of playing the busy tone for the caller. The system now appropriately plays the busy tone. (ID 4995)
• In the ISDN PRI stack, the Progress Indicator Information Element now contains the correct information. (ID 4999)
• If a call arrives at an NBX system on any Digital Line Card channel and is routed to any outgoing channel that is not in service (on either a Digital Line Card or an Analog Line Card), the caller now properly hears a busy signal. Previously, the caller heard ringing but the call was never answered.
(ID 5007)
• If a call was made over an E1 channel to a fax machine but the caller did not hang up after the fax machine disconnected, subsequent calls were connected to the fax audio and users heard clicking. This no longer occurs. (ID 5166)
Error Logs
• The following error message no longer appears inappropriately in the Nboss error log file:
TermSession E 2004 : LastNumDialed by diverting party is NULL - SendCallState() will not contain szDivertingPartyDialedNum information
(ID 4653)
Hunt Groups
• Previously, an incoming call to a hunt group that contained Caller ID information caused system memory partition errors and, potentially, a system halt under these conditions:
• The call was not answered
• The call coverage point of the first hunt group was another hunt group
This problem has been resolved. (ID 5338)
• Previously, a call could not be answered under these conditions:
• The call was made to a linear hunt group, all members of which were busy,
• The call forwarding point of the hunt group was the same hunt group or another hunt group.
This issue has been resolved. (ID 5345)
IMAP E-Mail Client
• If you use the NBX Forward application software to forward e-mail from the NBX system to one or more IMAP e-mail clients, the NBX system no longer experiences a memory leak. (ID 4506)
NBX System Log Files
• Messages beginning with “Q931 Utils” no longer appear in the NBX system log files. These messages were previously added to the log filess to help debug a problem and were never removed after the problem was resolved. (ID 4930)
NBX System Software
• A memory leak that occurred when an NBX system was connected through an AudioCodes gateway to a Unified Messaging System has been fixed. (ID 4839)
NBX Telephones
• Previously, if the router that was being used by NBX telephones used Virtual Router Redundancy Protocol (VRRP) and that router failed, traffic from the telephones continued to work but traffic to the telephones failed. Now, traffic in both directions flows properly. (ID 5103)
NBX Voice Messaging
• Callers who have more than 100 voicemail messages can now listen to any of the messages using their PC. Previously, they could listen to only the first 99 messages on their PCs but to all messages using their telephones. (ID 4504)
• Callers who create and send a voicemail message to a distribution list that contains their own names no longer see an incorrect time duration for the message. Also, when those callers listen to the message, they no longer hear “The following message cannot be delivered to mailbox number xxxx.;” (ID 4829)
• Previously, if you includes a greeting-only voice mailbox in a distribution list for voice mail messages and you sent a voice mail message to the list, you received a message indicating that the greeting-only mailbox was full. Now you properly receive a message saying that you cannot send voice mail to a greeting-only voice mailbox. (ID 4853)
Off-Site Notification
• Off-Site Notification no longer fails if, prior to the time of an Off-Site Notification message being sent by the NBX system, the default Class of Service groups “Default User Group” and “Super User Group” were deleted. (ID 4726)
• If an off-site notification attempt failed, the NBX system was not waiting before making the second attempt, even if there was a timer value configured. The system now waits until the timer expires before making the next attempt. (ID 5260)
Virtual Tie Lines (VTLs)
• CLIR Next and CLIR All functions now work on VTL calls. (ID 4584)
• If a caller on a SuperStack 3 NBX system places a VTL hopoff call to an NBX 100 system, and the destination number is not valid, the VTL connection is now properly disconnected. Previously, a timing problem caused the VTL connection to remain in an unusable state. (ID 4834)
• A caller now properly hears a busy signal under these conditions:
• A call is placed from NBX system A over VTL to NBX system B.
• The call hops off from NBX system B over an ISDN PRI line to an external telephone number.
• The number being called is busy.
Previously, the caller heard ringing. (ID 4939)
• Previously, if you placed a VTL call from an NBX 100 system to a SuperStack 3 NBX system and then hopped off onto an ISDN PRI line, the telephone that you called received two calls. One was the correct call and the other contained no audio. The no-audio call no longer occurs. (ID 5318)
PROBLEMS CORRECTED SINCE RELEASE 4.2.6
ID numbers in parentheses are for internal 3Com use only.
• Under very heavy network traffic conditions, telephones sometimes did not successfully receive software downloads. That problem has been resolved. (ID 4684)
TAPI Route Points
• Previously, the TAPI software could handle up to 256 simultaneous calls. Now, TAPI Route Points can handle up to 400 simultaneous calls on a SuperStack 3 NBX system, as designed. (ID 4320)
• During the initialization of a TAPI Route Point, the maximum number of extensions is no longer limited to 19 instead of 400. (ID 4498)
PROBLEMS CORRECTED SINCE RELEASE 4.1.72
ID numbers in parentheses are for internal 3Com use only.
Analog Line Card
• When external calls arrive on any port of a 3C10114C Analog Line Card, callers can now successfully enter digits on their telephones in order to access voice mail, the auto attendant, and other NBX system features. Previously, in some cases, the DTMF tones from the telephones were not properly detected by the 3C10114C card. (ID 4033)
• The 3C10114C Analog Line Cards now properly connect to all telephone company central office equipment. Previously, in a few cases, these cards failed to connect. (IDs 4305 and 4306)
Attendant Console (See also Message Waiting Indicator)
• Under these conditions, the status light on a Model 1105 Attendant Console no longer continues to blink after a conference call has been completed:
• A call arrives over an ISDN PRI line and is answered by a receptionist who uses an Attendant Console and an NBX Telephone.
• The receptionist adds a third person to the conference call using a VTL connection to another NBX system.
• The receptionist places the call on hold.
• While the call is on hold, the other two people hang up. (IDs 4204 and 4205)
Call Pickup
• On an analog telephone, if you pick up a call to another telephone that is a member of your call pickup group, you can now use the flash hook feature to put the call on hold and obtain dial tone. (ID 2586)
Call Detail Reports (CDR)
• The Help for CDR no longer indicates that internal calls (from one internal extension to another) are recorded. (ID 4383)
Call Transfer
• If your call is transferred to one of these entities:
• Phantom mailbox
• Telephone on which the Do Not Disturb feature has been activated
• Greeting-only mailbox
you now hear the full, recorded greeting. Previously, depending on the timing of the transfer, you might have heard only a portion or none of the greeting. (IDs 2644, 2799, and 4104)
Dial Plan
• NBX systems now properly adhere to the minimum digits specified in the dial plan configuration file. Previously, for example, if the minimum digits number is 8, you could still dial 91 and get an outside trunk connection. (ID 4156 and 4157)
Digital Line Cards
• Incoming calls over T1, ISDN PRI, or ISDN BRI lines that are routed to a fax machine that is not connected to an NBX Analog Terminal Card port or to an NBX Analog Terminal Adapter now work properly. Previously, if the fax machine was external to any NBX system and the call reached it through a hop-off mechanism, the call was not switched to fax mode. (ID 3626)
• A call can now be routed from an NBX system over a T1 line to a VCX V7000 system. (ID 3879)
• Software that relates to ISDN PRI and ISDN BRI Digital Line Card operation has been updated to obtain product certification in Italy. The changes also enable customers in other European countries to redial an outside number by incorporating the leading 0 in the redial string. (ID 3896)
• You can now configure an ISDN PRI line so that a rerouted call no longer appears to be an internal call under these conditions:
• The original call is routed over an ISDN PRI line from one NBX system to a second NBX system that is running the 3Com V7300 IP Telephony Application Suite.
• The call is then routed back to the original NBX system over the ISDN PRI line.
(ID 4080)
Find Me Follow Me (on the 3Com V7300 IP Telephony Application Suite)
• A caller now hears all of the Find-Me-Follow-Me prompts under these conditions:
• The call arrives at the NBX system over an ISDN PRI line.
• The call is forwarded to an AudioCodes gateway and then on to a 3Com VCX V7000 system.
• The VCX V7000 system has the Find-Me-Follow-Me feature activated.
Previously, synchronization problems between the systems caused the Find-Me-Follow-Me prompts to start playing before the caller was connected. (ID 3964)
Greeting-Only Mailbox
• If you forward a voicemail message to a greeting-only mailbox, you now hear an appropriate error message indicating that a greeting-only mailbox cannot accept voicemail messages. Previously, the error message indicated that the greeting-only mailbox was full and could not accept the voicemail message for that reason. (ID 4309)
Message Waiting Indicator (MWI)
• You can now set up an MWI on an NBX Telephone or Attendant Console for a phantom mailbox on an NBX system with the 3Com V7300 Applications Suite. (ID 4079)
• If you create an MWI for an extension on another NBX telephone and on an NBX Attendant Console, both lights now properly turn off when all messages are deleted from the voice mailbox. Previously, the light on the NBX Attendant Console stayed on. (ID 4109)
• An MWI light on an NBX Telephone or an NBX Attendant Console now properly stays on after a user accesses the associated button-mapping screen in the NBX NetSet utility. Previously, the MWI light on the telephone or Attendant Console turned off when a user opened and closed the button mapping screen, even without making any changes. (ID 4183)
NBX Devices Configured Behind a Home Router/Firewall
• If an NBX device is:
• Initially connected directly to an NBX system (Layer 2 connection)
• Configured as a low bandwidth device
• Subsequently placed behind a home router/firewall
the NBX NetSet utility no longer lists the device as a low bandwidth device. (ID 3893)
NBX NetSet Utility
• All pages in the NBX NetSet utility now display the appropriate title. (ID 3350)
NBX System Software
• Call log information is now written to memory properly. Previously, in some cases, the information was written improperly with the result that the tNetTask suspended operation. (ID 3632)
• You can now define the appropriate time zone on NBX systems operating in Saudi Arabia and the United Arab Emirates. (ID 3929)
NBX Telephones
• NBX Telephones now receive time updates and system state messages from the NBX system when multicast bin 0 (zero) is used for system state multicast messages. (ID 3197)
• If a user’s PC is connected to the LAN through an NBX Telephone, high levels of network traffic and PC activity no longer interfere with the normal operation of the NBX Telephone. (ID 3913)
• A PC no longer loses its network connection under these conditions:
• You connect the PC to an NBX Telephone that has a 3C model number ending in “B.”
• The PC uses a Mecer PCMCIA network card (Model LF560-TX).
(IDs 4322 and 4323)
Phantom Mailbox
• A phantom mailbox now works properly when it is configured on an NBX system with the 3Com V7300 IP Telephony Applications Suite that is connected to an NBX system by a VTL connection. Previously, messages were not forwarded properly to the phantom mailbox by the NBX system.
(ID 4180)
3Com V7300 IP Telephony Applications Suite
• See ID 4079, under the Message Waiting Indicator topic, earlier in this section.
• See ID 4048, under the Virtual Tie Line topic, next.
• See ID 3964, under the Find Me Follow Me topic, earlier in this section.
• You can now use the 3Com V7300 "Find Me Follow Me" application on the NBX system because the NBX code now includes an updated configuration file. (ID 4138)
Virtual Tie Lines (VTLs)
• When a call arrives at NBX System A over a T1 line and is immediately forwarded to a user extension on NBX System B over a VTL connection, the caller now properly hears the voice mail greeting of the user on NBX System B. (ID 3605)
• You can now make a call over a VTL line to another NBX system that is running the 3Com V7300 IP Telephony Applications Suite. However, the person receiving the call does not see caller ID information. (ID 4048)
• A caller no longer hears a voice mailbox greeting twice under these conditions:
• A call is transferred over a VTL from telephone A1 on NBX System A to telephone B1 on NBX System B
• The call is transferred to telephone A2 on System A
• The call is not answered, and it goes to the voice mailbox for telephone A2.(ID 4270)
KNOWN ANOMALIES AND CONSIDERATIONS IN RELEASE 4.2.13
ID numbers in parentheses are for internal 3Com use only.
Analog Terminal Cards and Analog Terminal Adapters
• Configuring an ATA device (either a Single-Port Analog Terminal Adapter or a port on an Analog Terminal Card) for fax operation optimizes the performance for inbound and outbound faxes and you should expect lower quality voice calls on that port. If you make a voice call using the ATA device (that is, if you use the telephone portion of the fax machine), the quality of the audio may be affected. If you make a VTL call using the ATA device, the audio may be unusable. If you configure the port for voice calls, the performance is not optimized for faxes. (ID 3096)
Browser Issues
• If you click the Help button on any screen in the NBX NetSet utility and then close the Help window and click the Help button again, sometimes the Help window does not contain all of the information.
(ID 3118)
Workaround for ID 3118: Close and reopen the Help window.
• A user who uses Microsoft Internet Explorer as the NBX NetSet browser may receive an error message that “Page cannot be located” along with the error number 800C0007. (ID 3120)
Workaround for ID 3120:
1. From the Microsoft Internet Explorer Tools menu or the View menu (depending on your version of Internet Explorer), select Internet Options.
2. Click the Advanced tab, and scroll to HTTP1.1 Settings.
3. Clear the two checkboxes titled “Use HTTP1.1” and “Use HTTP1.1 through proxy connections.”
4. Reboot the PC.
Call Park
• When a user is performing certain functions related to Call Park, the user’s telephone may temporarily lose the date and time on the telephone display panel. Examples:
• The user parks a call on a Call Park extension that is already in use.
• The user tries to park a call on an invalid Call Park extension.
• The user has parked two calls and the timer expires on one of them.
(ID 2543)
• If you change the name of a Call Park extension using the NBX NetSet utility and then a user parks and unparks a call, the old name of the extension appears in the display panel of the user’s telephone. (ID 2630)
Call Reports
• The Help for Call Reports does not match the updated screen that is associated with viewing a report. The following changes apply:
• Step 2 should read “On the Report menu, click View Standard Reports or View Custom Reports. Another dialog box appears.”
• A new step 3 should read “In the Select a report to view dialog box, select the particular report that you want to view and then click View Report.”
• The current step 3 should be renumbered to step 4.
(ID 1009)
Call Transfer
• The Central Office Busy Tone and Central Office Error Tone signals are not properly handled in either of these conditions:
• A user tries to transfer a call to an external number over an analog telephone line, but the number is busy or the user dialed an invalid number. If the user hangs up, the party being transferred hears the busy tone or error tone. Instead, the call should return to the user’s telephone.
• A user tries to add an external party to a conference call over an analog telephone line, but the number is busy or the user dialed an invalid number. If the user presses and releases the hook switch, the busy tone or error tone is included in the conference call. Instead, the attempted connection should be dropped.
(ID 1727)
Caller ID
• If you configure a telephone extension as the Auto Ext of an Analog Line Card port and enable the Do Not Disturb feature on the telephone, calls that arrive on the Analog Line Card port are routed immediately to voice mail. Because the caller ID information is passed from the CO only after the first ring, there is no caller ID information available to the NBX system, and the call is recorded in the call logs as a missed call with no caller ID. (ID 2043)
Complement Attendant Software (CAS) Application
• Using CAS, a user can answer a call and place it on hold but then cannot retrieve the call using the unhold function. (ID 2673)
Dial Plan
• If timed route entries overlap in the dial plan, the NBX system does not detect the problem and alert you. (ID 993)
Hunt Groups and Calling Groups
• On an NBX system with a large number of users, if you transfer users between the Non-member and the Member list in a hunt group, the transfer can take several minutes to finish. (ID 2205)
• If you select several hundred users to be included in a hunt group that you are creating, the transfer of these names into the hunt group takes several minutes to finish. (ID 3150)
• If you create a hunt group for a number of fax machines, an outside caller who calls the auto attendant and tries to leave a message in the hunt group voice mailbox is disconnected.
(IDs 4171 and 4185)
Workaround for IDs 4171 and 4185: Set the value of the per-device timeout (NBX NetSet > Hunt Groups > Modify) to 11 or greater.
IP-on-the-Fly
• On the CD and in the code, the Help topics for IP-on-the-Fly incorrectly state that this feature requires a license. That is no longer true. (ID 4680)
NBX Desktop Call Assistant (DCA) Software (formerly TAPI Dialer)
• If a caller uses the DCA to dial a number that includes a main number, some commas, and an extension number (for example, 7223232,,,361), the number appears in the display panel on the user’s NBX Telephone without the commas and extension number. (IDs 1700 and 3272)
• If a user uses the DCA to park a call on a call park extension that is already in use, the call is not parked and the user is not notified. When the call park timeout period elapses, the call rings back to the user, who can then park the call on another call park extension. (ID 3087)
• If you log in without administrator privileges and install the NBX Desktop Call Assistant software, an error message inappropriately indicates that you cannot install the product because the UninstallShield software is currently running. The message should inform you that you need administrator privileges to perform the installation. (ID 3262)
• If the DCA software is running on a PC that has Windows NT 4.0 installed on it, you can add a range of Call Park extensions, but you cannot add a single Call Park extension. (ID 4457)
NBX Devices Configured Behind a Home Router/Firewall
• If you have an NBX device configured behind a D-Link DI-640 router, the port to which the device is attached may periodically become disabled. (ID 3927)
Workaround for ID 3927: Disconnect the NBX device, reboot the D-Link router, and reconnect the NBX device.
• If you have an NBX device configured behind a 4-port LinkSys Cable/DSL plus Voice Router and you change the port to which the device is connected or you change the IP address of the device, the NBX device can no longer communicate with the host NBX system. (ID 3928)
Workaround for ID 3928: Remove and reapply power to the LinkSys router.
• If you send a VPIM message to an NBX device that is configured behind a home router/firewall, the VPIM software does not use the correct IP address. (ID 3960)
• If the home router/firewall device does not provide sufficient bandwidth, audio quality may be negatively affected for the NBX device behind it. Examples:
• An asymmetric DSL router with the slower speed configured too low.
• Multiple calls over the same channel (either a multiport NBX device or an NBX Business Telephone that has more than one active call).
(ID 3983)
• If you change the configuration on a 3Com OfficeConnect Internet Firewall DMZ (3C16771) to alter the Network Addressing Mode from "NAT with DHCP Client" to "NAT enabled" (or to reverse this change), the change does not take effect until you remove and reapply power to the NBX device behind the firewall. (ID 4378)
NBX Palm Dialer Application
• The NBX Palm Dialer application supports only versions 3.5 and 4.1 of the Palm Operating System.
• If, under the following conditions, you use a Palm Personal Digital Assistant (PDA) with version 3.5.2 of the Palm Operating System:
• You are on a call
• You try to set up a conference call or to transfer the existing call
then the error message “make call first / no resources” appears in the display panel of your 3Com Business Telephone, and the status light associated with the next System Appearance button remains lit until you next remove and reapply power to the telephone. (IDs 743 and 3163)
NBX System Software
• The Auto SaveCore function begins operation properly when a task has been suspended but fails to restart the shell. (ID 3697)
• In System Settings > Regional Settings > Advanced, the Israel and Russia entries in the list should show English for the manuals. They are not translated into Hebrew or Russian. (ID 4000)
NBX TAPI Service Provider Software (NBXTSP)
• The Remote TAPI Service Provider software does not work with the Microsoft Windows XP Home operating system. It does work properly with the XP Professional version. (ID 4387)
• The Remote TAPI Service Provider software does not work with the Microsoft Windows 98 operating system. That operating system does support the TCMSetup command. (ID 4388)
• If a TAPI call is blind transferred to an invalid extension, the NBX system attempts to disconnect the call. The attempt fails, and the call continues to show a status of CONNECTED. (ID 4499)
NBX Telephones
• NBX Telephones with a 3Com order number ending in the letter “B” (3C10281B, 3C10226B, 3C10228IRB) have a port labeled “10101” on the underside of the telephone. This port is not usable. Do not connect anything to this port. (ID 3093)
• On an NBX system with the Italian regional pack installed for voice prompts, a user who logs into voice mail and then presses 9 to hear more options hears prompt number 4 incorrectly speak of how to log out of the mailbox. The prompt should speak about Off-Site Notification. (ID 2942)
• When you set up a Time Dependent Greeting (NBX Messaging > Auto Attendant > Menu Tree > TD Greeting), the NBX system ignores the setting “Use System Wide Greetings.” As a result, the appropriate morning, afternoon, and evening greetings are not played before the Time Dependent Greeting. (ID 3242)
NBX Voice Messaging
• If a user listens to a voice mail message and presses 7 to move backward in the message, the system should replay the message starting at a point 5 seconds earlier. Instead, it goes back approximately 1 second the first time that the user presses 7, and 5 to 6 seconds the second time. (ID 1780)
• If you use the Call Logs on your NBX Telephone while you are listening to one of your voice mail messages, the messaging system behavior is not predictable. For example, the message you are listening to may be deleted or saved, or you may hear the time and date stamp information for the message. (ID 3796)
Off-Site Notification
• Off-Site Notification is not supported over VTL connections. (ID 996)
• If you have Off-Site Notification enabled, someone sends an e-mail message to your voice mailbox, and you attempt to listen to the e-mail message from your telephone, the voice prompt correctly informs you that the message is not a voice mail message and advises you to access it from your PC. However, the Off-Site Notification message that you receive in e-mail has no attachment and no contents; it should contain advisory information similar to the voice prompt’s advice. (ID 1279)
• If you have at least one saved voice mail message in your mailbox, and, in Off-Site Notification, you have configured the first two notification methods to send you e-mail, the NBX system attaches a new voice mail message to only the first off-site notification e-mail, not to the second one. (ID 1786)
• If you configure e-mail as your first and second method of off-site notification, you receive the first e-mail notification with the voice message attached but the second e-mail message has no attachment. (ID 3144)
Polycom Telephony Equipment
• If a 3Com Polycom Telephone is located behind a home router or firewall device, the time and date information in the display panel is updated only when certain external events occur. For example, when you make or receive a call, the display panel information, including the time and date information, is updated. (ID 3910)
Virtual Tie Lines (VTLs)
• Under these conditions, a user on an NBX system hears no ring back signal:
• A user on NBX System A calls a user on NBX System B using a VTL connection.
• The user on System B blind conferences someone on NBX System C into the call, also using a VTL connection.
• The user on System A hears no ring back signal.
(ID 2787)
• If an external call is forwarded from one NBX system to another over a VTL connection before the Central Office equipment provides caller ID information, the caller ID information may not be sent over the VTL connection to update the destination telephone’s display panel. (ID 3996)
• Under these conditions, a call is not properly transferred to voicemail and the caller hears dead air:
• An external call arrives at an NBX system that is running R4.2 system software.
• The call is blind transferred over a VTL line to a second NBX system that is running R4.1.4 or R4.1.21 system software.
• The call is not answered.
(ID 4423)
Voice Profile for Internet Mail (VPIM)
• If a VPIM message cannot be delivered on the first attempt and is queued for a later retry, the number of messages successfully delivered to external recipients is incorrect in the VPIM Statistics window (NBX NetSet > NBX Messaging > VPIM > Statistics). (ID 1111)
• Under some conditions, the VPIM Statistics indicate that a higher-than-actual number of calls were successfully delivered. (ID 3258)
PUTTING A REMOTE NBX® TELEPHONE BEHIND A HOME ROUTER OR FIREWALL: TESTING REPORT FROM THE 3COM VOICE QUALITY ASSURANCE TEAM
You can now have a single NBX device such as an NBX Telephone in your home if you connect to the Internet through certain home router devices.
3Com Firewall/Router Models
Models that have been fully tested and qualified by 3Com Quality Assurance against NBX Release 4.2:
• 3Com OfficeConnect® Cable/DSL Secure Gateway (3CR856-95)
• 3Com OfficeConnect Internet Firewall DMZ (3C16771)
• 3Com OfficeConnect Wireless 11g Cable/DSL Gateway (3CRWE554G72)
Models that share the same code base as one of the fully tested models, but they have not been explicitly tested against NBX Release 4.2:
• 3Com OfficeConnect Internet Firewall 25 (3C16770) — same code as 3C16771
• 3Com OfficeConnect Wireless 11b Cable/DSL Gateway (3CRWE553172) — same code as 3CRWE554G72
Models that were 1) tested previously but found to have performance problems; 2) now have software to resolve the problem on but 3) have not been fully retested to verify resolution:
• 3Com OfficeConnect Cable/DSL Gateway (3C857-US)
• 3Com OfficeConnect Wireless Cable/DSL Gateway (3CRWE52196)
Third-Party Firewall/Router Models
Models that have been tested against NBX Release 4.2:
• D-Link Express EtherNetwork 4-Port Ethernet Broadband Router (DI-604)
Problems of stability and robustness. See the description for PRB 3927.
• LinkSys EtherFast Cable/DSL & Voice Router (BEFN2PS4)
Problems of stability and robustness. See the description for PRB 3928.
• Netgear 4-Port Cable/DSL Router with 10/100 Mbps Switch (RP614NA)
Did not work.
• Netgear 4-Port Cable/DSL ProSafe Firewall/Print Server (FR114PNA)
Configuration problems.
Documentation Comments
As we work to make the documentation easier for you to use, we invite you to send us your feedback on errors that you find in the books and Help systems, and also on areas that you would like to see explained more fully.
Please send your documentation comments to us at the following address:
Voice_TechComm_Comments@3com.com
IMPORTANT: As always, please address all questions about the NBX hardware and software to your 3Com NBX Voice-Authorized Partner.
Thank you.
Copyright ? 2004, 3Com Corporation. All Rights Reserved.
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 26-August-2004
• SuperStack? 3 NBX? Networked Telephony Solution
• NBX 100 Communications System
NOTICE: NBX software release R4.2.12 fully supports 3Com eXchange Call Center software version 4.33.00. See the 3Com eXchange Call Center release notes for upgrade information.
CAUTION: Be aware that, if you are upgrading your NBX system software from the Beta testing version to the final released version of R4.2, Beta versions of these hardware components will no longer be supported:
• 3Com Model 3102 Business Telephone
• Single-port Analog Terminal Adapter (3C10400)
(IDs 3965, 3966, and 3967)
NOTICE: Before you can upgrade your existing NBX system to Release 4.2 software, you must first upgrade to Release 4.1 or a more recent release. See the NBX Administrator’s Guide for details.
NOTICE: Starting with Release 4.2, the NBX system software requires a license. Upgrades from previous releases must be done with this requirement in mind. See page 5 of these release notes and the NBX Administrator’s Guide for details.
CAUTION: After you upgrade to Release 4.2 from a previous release, you must back up the licenses on your NBX system. If you do not back up the licenses and the system disk is lost for any reason, you will not be able to restore your licenses after you replace the system disk.
NOTICE:
• The SuperStack 3 NBX system is shipped with a 4-digit dial plan. If you import a 3-digit plan, you must manually specify any 3-digit extension ranges that are not set by the imported plan.
• The NBX 100 is shipped with a factory default 3-digit dial plan. If you import a 4-digit plan, you must manually specify any 4-digit extension ranges that are not set by the imported plan.
CAUTION: If you use the 3Com SuperStack II Advanced Redundant Power Supply as a backup power supply for the SuperStack 3 NBX Gateway Chassis, the Gateway Chassis can contain no more than two Analog Terminal Cards (3C10117 or 3C10117A). There is insufficient power for a third or a fourth ATC, and the NBX system will not operate properly. Any other NBX cards except the Network Call Processor Card can be configured in the remaining two slots.
This restriction does not apply to the new 3C10117C Analog Terminal Card. (ID 1313)
CAUTION: 3Com suggests that you connect no more than 50 TAPI clients to any one NBX system. For more than 50 TAPI client connections, 3Com recommends that you install the Microsoft Remote TSP software on a Windows NT PC.
NEW FEATURES IN RELEASE 4.2
New 3Com Model 3102 Business Telephone
The 3Com Model 3102 Business Telephone is a new design of the Business Telephone. It shares the same core capabilities as previous models with a number of improvements to its appearance and design, including:
• Headset Jack – You can connect a headset directly to the Model 3102 Business Telephone. A programmable button on the telephone enables or disables headset operation.
• The phone has an enhanced full-duplex speakerphone with superior voice quality.
• The new, one-piece stand offers 15- to 45-degree desk adjustments as well as a wall-mount position.
• All 18 programmable buttons include a status light (LED).
• Replaceable bottom bezels will be offered for localization of button names.
New Model of the Single-Port Analog Terminal Adapter (3C10400)
The new model operates with all of the same features as the previous models, plus these two new capabilities:
• Power over Ethernet (PoE) – The new model can supply power to devices that are compliant with the IEEE 802.3af standard.
• Diagnostic Port – The new model has a 9-pin RS232 connector (DB9) to which you can connect your PC using the appropriate cable and a terminal emulation software package such as Hyperterm.
Progress Indicators
During backup or restore your NBX database, or during your upgrade of the NBX system software, you now see progress bars in the NBX NetSet™ utility. Also, you can now cancel a backup or upgrade operation that is in progress.
Saving the Most Recent Backup File
You can now click a button on the Operations > Manage Data tab to save the most recent backup file. This shortcut enables you to save the most recent backup file to more than one location without performing another backup.
System Alert While a File System Check Is Being Performed
During a reboot operation, if a file system check (FSCK) is required, the NBX system now alerts you to this fact by flashing the Call Processor S1 and S2 status lights in an alternating pattern.
Enhanced Caller ID Information
When a call is forwarded, redirected, or transferred to you, the display panel on your NBX Telephone now shows caller ID information for the original caller and for the person who is forwarding, redirecting, or transferring the call to you.
NBX System Settings
Some NBX system settings have moved to a new Audio Settings screen (NBX NetSet > System Configuration > System Settings > Audio Settings). The new screen includes these configurable settings:
• System-Wide Silence Suppression
• System-Wide Silence Suppression on VTL Calls
• Audio Compression on VTL Calls
• NBX Handset Acoustic Echo Suppression (new setting)
• Analog Line Cards Additional Echo Suppression (new setting)
• Digital Line Cards Additional Echo Suppression (new setting)
See implementation instructions on the screen.
Enhanced Status of Analog Line Card Ports
The status screen for Analog Line Card Ports now includes information about the most recent five completed calls.
D-Channel Status Information for ISDN PRI
If you have a Digital Line Card configured for ISDN PRI operation, the Span Status screen in the NBX NetSet utility now includes status information about the D channel. You can verify whether the D channel is Online, Offline, or in an Unknown state.
Remote NBX Device Behind a Home Router or Firewall
You can now have a single NBX device such as an NBX Telephone in your home if you connect to the Internet through certain home router devices. See the testing report at the end of these Release Notes, and Chapter 3 in the NBX Administrator’s Guide.
Telnet
You can now establish a telnet session between your PC and the NBX system. This ability, which requires administrator login ID and password, can be turned on or off by the system administrator. By default, this setting is turned off.
Purging Voicemail
When you purge your NBX database, you now have the option of purging all voicemail from the NBX system. Later, if you restore your database from a prior backup, you can choose whether or not to restore voicemail if it is included in the backup.
Redirecting TAPI Calls
A TAPI Route Point is a virtual device (new in R4.2) that you can create using the NBX NetSet utility. It has an extension and can receive and queue multiple simultaneous calls for application-driven redirection to other telephone numbers. A SuperStack 3 NBX system allows up to 400 calls to be queued by TAPI Route Points. An NBX 100 system allows 50 calls to be queued.
You can configure TAPI Route Points to accept internal and external calls and queue them until they can be redirected by TAPI or until the calls time out. Calls that are redirected go to a destination specified by TAPI applications that are external to the NBX system. Calls that time out are sent to the call coverage point of the TAPI Route Point. TAPI Route Points can be useful if you are using the NBX system in a call center environment.
Calls to other devices that can be monitored by TAPI, such as Analog Terminal Adapters, Analog Terminal Card ports, NBX Telephones, and Hunt Groups can also be redirected by TAPI-enabled applications.
IP-on-the-Fly Licensing
All NBX systems are now shipped with the license for IP-on-the-Fly enabled. Users no longer need to purchase an IP-on-the-Fly license.
APPLICATIONS IN RELEASE 4.2
In addition to the Release 4.2 system software, Release 4.2 contains these applications:
• NBX Complement Attendant Software R4.2.4 • NBX TAPI Service Provider R4.2.10
• NBX Call Reports R4.2.2 • NBX Palm Dialer R1.1.3
• NBX ConneXtions Gateway R4.0.1 • 3Com Network Supervisor V4.0.1
• NBX Media Driver R4.2.4
(formerly WAV Driver) • NBX Desktop Call Assistant R4.2.2
(formerly TAPI Dialer)
• NBX pcXset? Soft Telephone R4.2.2
For all applications, see the 3Com Partner Access website or the NBX FTP site for the most up-to-date versions.
LICENSE ANNOUNCEMENTS
UPGRADING TO RELEASE 4.2 OF NBX® NETWORKED TELEPHONY SOLUTIONS
AND
INSTALLING THE 3COM® MODEL 3102 BUSINESS PHONE
NBX Release 4.2 is the first NBX software release that requires a license key to activate it, and the
3Com Model 3102 Business Telephone is the first 3Com Telephone that requires a license key to install it.
• To ensure a trouble-free upgrade to R4.2 for your NBX system, follow either Procedure A or Procedure B, described in this document.
• To install the 3Com Model 3102 Business Telephone, follow the instructions in “Installing the License Key for Model 3102 NBX Business Telephones,” later in this License Announcements section.
PROCEDURE A: INSTALLING THE R4.2 LICENSE KEY
BEFORE YOU UPGRADE (RECOMMENDED)
1. Purchase the R4.2 License Key from your 3Com NBX Voice-Authorized Partner.
2. If your NBX system is running a software release earlier than R4.1, first upgrade to any released version of R4.1 before you attempt to upgrade to R4.2.
Note: Before R4.1, the NBX system software did not recognize the R4.2 license as valid.
After you upgrade to R4.1, you can install the license key for R4.2 and the system accepts it.
3. After your system is running on R4.1, follow these steps to install the license key for R4.2:
a) Log in to the NBX NetSet™ utility using the administrator login ID and password.
b) Select Operations > Licenses > Add License.
c) Type the license key into the text box and click OK. The screen displays “License Unknown.”
4. Obtain the R4.2 software upgrade file and load it onto your NBX system. Then follow these steps:
a) In the NBX NetSet utility, select Operations > Software Upgrade > Browse and locate the software upgrade file. Then click Upgrade.
Wait until you see a system message that indicates that the upgrade file has been
successfully loaded. Typically, the process is complete in 30 minutes or less.
b) In the NBX NetSet utility, select Operations > Reboot/Shutdown.
c) From the Select version: list, select the R4.2 release that you just loaded and click Reboot.
Wait until you see a system message that indicates that the reboot operation has been
successfully completed. Typically, the process is complete in 30 minutes or less.
d) To verify that the system is now running R4.2, in the NBX NetSet utility, select
Reports > System Data. In the Runtime column, verify that the System item shows
R4.2.x, where x is the specific version of R4.2 that you loaded.
e) Save your newly updated License file by selecting Operations > Licenses > Backup Licenses.
PROCEDURE B: INSTALLING THE R4.2 LICENSE KEY
AFTER YOU UPGRADE
If you upgrade the system software to R4.2 before you install the license key:
• The NBX system advises you that you must install the license key or reboot to a
previous release that required no license.
• You can perform no NBX NetSet Admin tasks such as Move, Add, or Modify, except to enter the
license key or reboot to a previous release.
• NBX system users can make and receive internal and external calls.
• Users see “NO LICENSE” in the display panel of their telephones whenever their telephones
are active, for instance, when they pick up the handset to make or answer a call.
To install the license key:
1. Purchase the R4.2 license key from your 3Com NBX Voice-Authorized Partner.
2. Log in to the NBX™ NetSet utility using the administrator login ID and password.
3. Select Operations > Licenses > Add License, type the license key into the text box, and click OK.
4. Save your newly updated License file by selecting Operations > Licenses > Backup Licenses.
After you click OK, the R4.2 system becomes fully operational. You can now perform normal administration tasks in the NBX NetSet utility.
INSTALLING THE LICENSE KEY FOR
MODEL 3102 NBX BUSINESS TELEPHONES
Unlike other 3Com NBX Telephones, before you can discover any Model 3102 NBX Business
Telephones on an NBX system, you must install the appropriate license key.
For full instructions on installing telephones on an NBX system, see Chapter 3: Telephones
and Attendant Consoles in the NBX Installation Guide, which you can find on the
NBX Resource Pack CD or on the Main Menu window of the NBX NetSet utility.
To install the license key:
1. In the NBX NetSet utility, select Operations > Licenses > Add License.
2. Type the license key into the text box.
To verify that the new license key has been accepted:
3. Select Operations > Licenses. Verify that a license for Model 3102 Business Telephones is included in the list of licenses.
4. Save your newly updated License file by selecting Operations > Licenses > Backup Licenses.
Note: You do not need to reboot the NBX system for the new 3102 license key to take effect.
PROBLEMS CORRECTED SINCE RELEASE 4.2.7
ID numbers in parentheses are for internal 3Com use only.
3Com eXchange Call Center
• Previously, when there was an idle agent on the system, occasionally calls were not routed to an available agent and were not counted as queued. This problem no longer occurs. (ID 4602)
• If someone is connected to the Auto Attendant and makes a call to a hunt group, the person answering the call now sees the hunt group number on the LINECALLINFO line in the telephone’s display panel. (ID 4941)
• If "Handsfree on Transfer" is enabled system-wide, an external call that is redirected to an agent after being queued to an NBX TAPI Route Point extension no longer initiates Hands Free mode if the agent has enabled the Hands Free feature on the telephone. Hands Free mode applies only to internal calls. (ID 5096)
3Com Telephones
• In the telephone directory that appears on a 3Com telephone’s display panel, names that begin with lower-case letters, now appear in proper alphabetic order. Previously, all names beginning with upper-case letters appeared first in the list, followed by names beginning with lower-case letters.
(ID 5000)
Analog Terminal Card
• A caller now hears audio from a conferenced IP telephone under these conditions:
• A call is placed from analog telephone A to analog telephone B, both of which are connected to a 3C10117C Analog Terminal Card on NBX system A.
• NBX system A uses IP On-the-Fly and both telephone A and telephone B are Ethernet (layer 2) telephones.
• The caller conferences a third telephone into the call. The third telephone is on the same subnetwork as NBX system A, but is an IP (layer 3) telephone connected to NBX system B.
• NBX system B is on a different subnetwork than NBX system A.
• Previously, the caller on telephone A did not hear any audio from the IP telephone connected to NBX system B.
(ID 4895)
AudioCodes Gateways
• A caller no longer hears ringing instead of being immediately connected to a voice menu under these conditions:
• The call was placed from a SIP telephone connected to an AudioCodes box.
• The AudioCodes box was connected to an NBX system through an ISDN PRI line.
• The NBX system was connected to the Public Switched Telephone Network (PSTN) through an ISDN PRI line.
• The call destination was on the PSTN.
(ID 4903)
Automated Attendant
• If an Automated Attendant menu record becomes corrupted for any reason, the NBX system now boots properly and corrects the corruption. Previously, the corruption causes a system interruption during the boot process. (ID 5188)
• If, after recording an Auto Attendant prompt, you hang up the telephone without pressing the pound key (#), the voice mail port that you were using is properly returned to service. Previously, if you failed to press the pound key the voice mail port became unavailable for use. (ID 5198)
Automatic Backup
• Previously, if you used the automatic database backup tool and enabled the checkbox to include voice mail in the backup, voice mail was not included in subsequent backups. To include voice mail in the backups, you had to enable the check box a second time. Now, enabling the checkbox once is sufficient. (ID 5308)
Call Transfer
• If user A attempts to transfer a call to user B when user B was on a call, the message “On A Call” now properly appears in the display panel on user A’s telephone. Previously, this message did not appear. (ID 4926)
Caller ID
• When an NBX system is connected to some Northern Telecom DMS100 voice switches, caller ID information is now properly received from the telephone company equipment. (IDs 3990 and 3991)
• The system administrator can now select the way in which Caller ID information is transmitted from an NBX system to the Public Switched Telephone Network (PSTN) for forwarded or transferred trunk-to-trunk calls. Before NBX release R4.1.77, a call to an NBX system that was forwarded or transferred to an outgoing trunk contained the Caller ID information of the forwarding party, not the originating party. In NBX release R4.1.77 and later releases, a forwarded or transferred trunk-to-trunk call contains the Caller ID information of the originating party. However, some PSTNs do not connect calls unless the Caller ID information matches the forwarding telephone’s ID. Customers who want to send the forwarding party Caller ID on forwarded or transferred trunk-to-trunk calls must consult their CSO representative for the instructions on how to make a change to the nboss.cfg file. (ID 4929)
Citel and Analog Telephones
• On an analog telephone connected to an NBX system with a Citel Gateway board, a caller who enters Feature Codes 403 through 408 now properly sees a “Not Supported” message in the display panel of the telephone. Previously, the caller inappropriately heard an error tone and the display panel flashed, but did not contain the appropriate message. (ID 4766)
Digital Line Cards
• If, in the NBX NetSet interface, you reconfigure the IP settings on a Digital Line Card and change only the default gateway address, the change now occurs. Previously, such a change did not occur unless at least one other parameter was also changed. (ID 4608)
• Previously, if an incoming call contained a user-to-user Information Element that was empty, the NBX system inappropriately generated an error message. No message is now generated because this situation is allowed according to the specification. (ID 4905)
• On some trunk-to-trunk call transfers, if the called number was busy, the NBX system disconnected the call instead of playing the busy tone for the caller. The system now appropriately plays the busy tone. (ID 4995)
• In the ISDN PRI stack, the Progress Indicator Information Element now contains the correct information. (ID 4999)
• If a call arrives at an NBX system on any Digital Line Card channel and is routed to any outgoing channel that is not in service (on either a Digital Line Card or an Analog Line Card), the caller now properly hears a busy signal. Previously, the caller heard ringing but the call was never answered.
(ID 5007)
• If a call was made over an E1 channel to a fax machine but the caller did not hang up after the fax machine disconnected, subsequent calls were connected to the fax audio and users heard clicking. This no longer occurs. (ID 5166)
Error Logs
• The following error message no longer appears inappropriately in the Nboss error log file:
TermSession E 2004 : LastNumDialed by diverting party is NULL - SendCallState() will not contain szDivertingPartyDialedNum information
(ID 4653)
Hunt Groups
• Previously, an incoming call to a hunt group that contained Caller ID information caused system memory partition errors and, potentially, a system halt under these conditions:
• The call was not answered
• The call coverage point of the first hunt group was another hunt group
This problem has been resolved. (ID 5338)
• Previously, a call could not be answered under these conditions:
• The call was made to a linear hunt group, all members of which were busy,
• The call forwarding point of the hunt group was the same hunt group or another hunt group.
This issue has been resolved. (ID 5345)
IMAP E-Mail Client
• If you use the NBX Forward application software to forward e-mail from the NBX system to one or more IMAP e-mail clients, the NBX system no longer experiences a memory leak. (ID 4506)
NBX System Log Files
• Messages beginning with “Q931 Utils” no longer appear in the NBX system log files. These messages were previously added to the log filess to help debug a problem and were never removed after the problem was resolved. (ID 4930)
NBX System Software
• A memory leak that occurred when an NBX system was connected through an AudioCodes gateway to a Unified Messaging System has been fixed. (ID 4839)
NBX Telephones
• Previously, if the router that was being used by NBX telephones used Virtual Router Redundancy Protocol (VRRP) and that router failed, traffic from the telephones continued to work but traffic to the telephones failed. Now, traffic in both directions flows properly. (ID 5103)
NBX Voice Messaging
• Callers who have more than 100 voicemail messages can now listen to any of the messages using their PC. Previously, they could listen to only the first 99 messages on their PCs but to all messages using their telephones. (ID 4504)
• Callers who create and send a voicemail message to a distribution list that contains their own names no longer see an incorrect time duration for the message. Also, when those callers listen to the message, they no longer hear “The following message cannot be delivered to mailbox number xxxx.;” (ID 4829)
• Previously, if you includes a greeting-only voice mailbox in a distribution list for voice mail messages and you sent a voice mail message to the list, you received a message indicating that the greeting-only mailbox was full. Now you properly receive a message saying that you cannot send voice mail to a greeting-only voice mailbox. (ID 4853)
Off-Site Notification
• Off-Site Notification no longer fails if, prior to the time of an Off-Site Notification message being sent by the NBX system, the default Class of Service groups “Default User Group” and “Super User Group” were deleted. (ID 4726)
• If an off-site notification attempt failed, the NBX system was not waiting before making the second attempt, even if there was a timer value configured. The system now waits until the timer expires before making the next attempt. (ID 5260)
Virtual Tie Lines (VTLs)
• CLIR Next and CLIR All functions now work on VTL calls. (ID 4584)
• If a caller on a SuperStack 3 NBX system places a VTL hopoff call to an NBX 100 system, and the destination number is not valid, the VTL connection is now properly disconnected. Previously, a timing problem caused the VTL connection to remain in an unusable state. (ID 4834)
• A caller now properly hears a busy signal under these conditions:
• A call is placed from NBX system A over VTL to NBX system B.
• The call hops off from NBX system B over an ISDN PRI line to an external telephone number.
• The number being called is busy.
Previously, the caller heard ringing. (ID 4939)
• Previously, if you placed a VTL call from an NBX 100 system to a SuperStack 3 NBX system and then hopped off onto an ISDN PRI line, the telephone that you called received two calls. One was the correct call and the other contained no audio. The no-audio call no longer occurs. (ID 5318)
PROBLEMS CORRECTED SINCE RELEASE 4.2.6
ID numbers in parentheses are for internal 3Com use only.
• Under very heavy network traffic conditions, telephones sometimes did not successfully receive software downloads. That problem has been resolved. (ID 4684)
TAPI Route Points
• Previously, the TAPI software could handle up to 256 simultaneous calls. Now, TAPI Route Points can handle up to 400 simultaneous calls on a SuperStack 3 NBX system, as designed. (ID 4320)
• During the initialization of a TAPI Route Point, the maximum number of extensions is no longer limited to 19 instead of 400. (ID 4498)
PROBLEMS CORRECTED SINCE RELEASE 4.1.72
ID numbers in parentheses are for internal 3Com use only.
Analog Line Card
• When external calls arrive on any port of a 3C10114C Analog Line Card, callers can now successfully enter digits on their telephones in order to access voice mail, the auto attendant, and other NBX system features. Previously, in some cases, the DTMF tones from the telephones were not properly detected by the 3C10114C card. (ID 4033)
• The 3C10114C Analog Line Cards now properly connect to all telephone company central office equipment. Previously, in a few cases, these cards failed to connect. (IDs 4305 and 4306)
Attendant Console (See also Message Waiting Indicator)
• Under these conditions, the status light on a Model 1105 Attendant Console no longer continues to blink after a conference call has been completed:
• A call arrives over an ISDN PRI line and is answered by a receptionist who uses an Attendant Console and an NBX Telephone.
• The receptionist adds a third person to the conference call using a VTL connection to another NBX system.
• The receptionist places the call on hold.
• While the call is on hold, the other two people hang up. (IDs 4204 and 4205)
Call Pickup
• On an analog telephone, if you pick up a call to another telephone that is a member of your call pickup group, you can now use the flash hook feature to put the call on hold and obtain dial tone. (ID 2586)
Call Detail Reports (CDR)
• The Help for CDR no longer indicates that internal calls (from one internal extension to another) are recorded. (ID 4383)
Call Transfer
• If your call is transferred to one of these entities:
• Phantom mailbox
• Telephone on which the Do Not Disturb feature has been activated
• Greeting-only mailbox
you now hear the full, recorded greeting. Previously, depending on the timing of the transfer, you might have heard only a portion or none of the greeting. (IDs 2644, 2799, and 4104)
Dial Plan
• NBX systems now properly adhere to the minimum digits specified in the dial plan configuration file. Previously, for example, if the minimum digits number is 8, you could still dial 91 and get an outside trunk connection. (ID 4156 and 4157)
Digital Line Cards
• Incoming calls over T1, ISDN PRI, or ISDN BRI lines that are routed to a fax machine that is not connected to an NBX Analog Terminal Card port or to an NBX Analog Terminal Adapter now work properly. Previously, if the fax machine was external to any NBX system and the call reached it through a hop-off mechanism, the call was not switched to fax mode. (ID 3626)
• A call can now be routed from an NBX system over a T1 line to a VCX V7000 system. (ID 3879)
• Software that relates to ISDN PRI and ISDN BRI Digital Line Card operation has been updated to obtain product certification in Italy. The changes also enable customers in other European countries to redial an outside number by incorporating the leading 0 in the redial string. (ID 3896)
• You can now configure an ISDN PRI line so that a rerouted call no longer appears to be an internal call under these conditions:
• The original call is routed over an ISDN PRI line from one NBX system to a second NBX system that is running the 3Com V7300 IP Telephony Application Suite.
• The call is then routed back to the original NBX system over the ISDN PRI line.
(ID 4080)
Find Me Follow Me (on the 3Com V7300 IP Telephony Application Suite)
• A caller now hears all of the Find-Me-Follow-Me prompts under these conditions:
• The call arrives at the NBX system over an ISDN PRI line.
• The call is forwarded to an AudioCodes gateway and then on to a 3Com VCX V7000 system.
• The VCX V7000 system has the Find-Me-Follow-Me feature activated.
Previously, synchronization problems between the systems caused the Find-Me-Follow-Me prompts to start playing before the caller was connected. (ID 3964)
Greeting-Only Mailbox
• If you forward a voicemail message to a greeting-only mailbox, you now hear an appropriate error message indicating that a greeting-only mailbox cannot accept voicemail messages. Previously, the error message indicated that the greeting-only mailbox was full and could not accept the voicemail message for that reason. (ID 4309)
Message Waiting Indicator (MWI)
• You can now set up an MWI on an NBX Telephone or Attendant Console for a phantom mailbox on an NBX system with the 3Com V7300 Applications Suite. (ID 4079)
• If you create an MWI for an extension on another NBX telephone and on an NBX Attendant Console, both lights now properly turn off when all messages are deleted from the voice mailbox. Previously, the light on the NBX Attendant Console stayed on. (ID 4109)
• An MWI light on an NBX Telephone or an NBX Attendant Console now properly stays on after a user accesses the associated button-mapping screen in the NBX NetSet utility. Previously, the MWI light on the telephone or Attendant Console turned off when a user opened and closed the button mapping screen, even without making any changes. (ID 4183)
NBX Devices Configured Behind a Home Router/Firewall
• If an NBX device is:
• Initially connected directly to an NBX system (Layer 2 connection)
• Configured as a low bandwidth device
• Subsequently placed behind a home router/firewall
the NBX NetSet utility no longer lists the device as a low bandwidth device. (ID 3893)
NBX NetSet Utility
• All pages in the NBX NetSet utility now display the appropriate title. (ID 3350)
NBX System Software
• Call log information is now written to memory properly. Previously, in some cases, the information was written improperly with the result that the tNetTask suspended operation. (ID 3632)
• You can now define the appropriate time zone on NBX systems operating in Saudi Arabia and the United Arab Emirates. (ID 3929)
NBX Telephones
• NBX Telephones now receive time updates and system state messages from the NBX system when multicast bin 0 (zero) is used for system state multicast messages. (ID 3197)
• If a user’s PC is connected to the LAN through an NBX Telephone, high levels of network traffic and PC activity no longer interfere with the normal operation of the NBX Telephone. (ID 3913)
• A PC no longer loses its network connection under these conditions:
• You connect the PC to an NBX Telephone that has a 3C model number ending in “B.”
• The PC uses a Mecer PCMCIA network card (Model LF560-TX).
(IDs 4322 and 4323)
Phantom Mailbox
• A phantom mailbox now works properly when it is configured on an NBX system with the 3Com V7300 IP Telephony Applications Suite that is connected to an NBX system by a VTL connection. Previously, messages were not forwarded properly to the phantom mailbox by the NBX system.
(ID 4180)
3Com V7300 IP Telephony Applications Suite
• See ID 4079, under the Message Waiting Indicator topic, earlier in this section.
• See ID 4048, under the Virtual Tie Line topic, next.
• See ID 3964, under the Find Me Follow Me topic, earlier in this section.
• You can now use the 3Com V7300 "Find Me Follow Me" application on the NBX system because the NBX code now includes an updated configuration file. (ID 4138)
Virtual Tie Lines (VTLs)
• When a call arrives at NBX System A over a T1 line and is immediately forwarded to a user extension on NBX System B over a VTL connection, the caller now properly hears the voice mail greeting of the user on NBX System B. (ID 3605)
• You can now make a call over a VTL line to another NBX system that is running the 3Com V7300 IP Telephony Applications Suite. However, the person receiving the call does not see caller ID information. (ID 4048)
• A caller no longer hears a voice mailbox greeting twice under these conditions:
• A call is transferred over a VTL from telephone A1 on NBX System A to telephone B1 on NBX System B
• The call is transferred to telephone A2 on System A
• The call is not answered, and it goes to the voice mailbox for telephone A2.(ID 4270)
KNOWN ANOMALIES AND CONSIDERATIONS IN RELEASE 4.2.13
ID numbers in parentheses are for internal 3Com use only.
Analog Terminal Cards and Analog Terminal Adapters
• Configuring an ATA device (either a Single-Port Analog Terminal Adapter or a port on an Analog Terminal Card) for fax operation optimizes the performance for inbound and outbound faxes and you should expect lower quality voice calls on that port. If you make a voice call using the ATA device (that is, if you use the telephone portion of the fax machine), the quality of the audio may be affected. If you make a VTL call using the ATA device, the audio may be unusable. If you configure the port for voice calls, the performance is not optimized for faxes. (ID 3096)
Browser Issues
• If you click the Help button on any screen in the NBX NetSet utility and then close the Help window and click the Help button again, sometimes the Help window does not contain all of the information.
(ID 3118)
Workaround for ID 3118: Close and reopen the Help window.
• A user who uses Microsoft Internet Explorer as the NBX NetSet browser may receive an error message that “Page cannot be located” along with the error number 800C0007. (ID 3120)
Workaround for ID 3120:
1. From the Microsoft Internet Explorer Tools menu or the View menu (depending on your version of Internet Explorer), select Internet Options.
2. Click the Advanced tab, and scroll to HTTP1.1 Settings.
3. Clear the two checkboxes titled “Use HTTP1.1” and “Use HTTP1.1 through proxy connections.”
4. Reboot the PC.
Call Park
• When a user is performing certain functions related to Call Park, the user’s telephone may temporarily lose the date and time on the telephone display panel. Examples:
• The user parks a call on a Call Park extension that is already in use.
• The user tries to park a call on an invalid Call Park extension.
• The user has parked two calls and the timer expires on one of them.
(ID 2543)
• If you change the name of a Call Park extension using the NBX NetSet utility and then a user parks and unparks a call, the old name of the extension appears in the display panel of the user’s telephone. (ID 2630)
Call Reports
• The Help for Call Reports does not match the updated screen that is associated with viewing a report. The following changes apply:
• Step 2 should read “On the Report menu, click View Standard Reports or View Custom Reports. Another dialog box appears.”
• A new step 3 should read “In the Select a report to view dialog box, select the particular report that you want to view and then click View Report.”
• The current step 3 should be renumbered to step 4.
(ID 1009)
Call Transfer
• The Central Office Busy Tone and Central Office Error Tone signals are not properly handled in either of these conditions:
• A user tries to transfer a call to an external number over an analog telephone line, but the number is busy or the user dialed an invalid number. If the user hangs up, the party being transferred hears the busy tone or error tone. Instead, the call should return to the user’s telephone.
• A user tries to add an external party to a conference call over an analog telephone line, but the number is busy or the user dialed an invalid number. If the user presses and releases the hook switch, the busy tone or error tone is included in the conference call. Instead, the attempted connection should be dropped.
(ID 1727)
Caller ID
• If you configure a telephone extension as the Auto Ext of an Analog Line Card port and enable the Do Not Disturb feature on the telephone, calls that arrive on the Analog Line Card port are routed immediately to voice mail. Because the caller ID information is passed from the CO only after the first ring, there is no caller ID information available to the NBX system, and the call is recorded in the call logs as a missed call with no caller ID. (ID 2043)
Complement Attendant Software (CAS) Application
• Using CAS, a user can answer a call and place it on hold but then cannot retrieve the call using the unhold function. (ID 2673)
Dial Plan
• If timed route entries overlap in the dial plan, the NBX system does not detect the problem and alert you. (ID 993)
Hunt Groups and Calling Groups
• On an NBX system with a large number of users, if you transfer users between the Non-member and the Member list in a hunt group, the transfer can take several minutes to finish. (ID 2205)
• If you select several hundred users to be included in a hunt group that you are creating, the transfer of these names into the hunt group takes several minutes to finish. (ID 3150)
• If you create a hunt group for a number of fax machines, an outside caller who calls the auto attendant and tries to leave a message in the hunt group voice mailbox is disconnected.
(IDs 4171 and 4185)
Workaround for IDs 4171 and 4185: Set the value of the per-device timeout (NBX NetSet > Hunt Groups > Modify) to 11 or greater.
IP-on-the-Fly
• On the CD and in the code, the Help topics for IP-on-the-Fly incorrectly state that this feature requires a license. That is no longer true. (ID 4680)
NBX Desktop Call Assistant (DCA) Software (formerly TAPI Dialer)
• If a caller uses the DCA to dial a number that includes a main number, some commas, and an extension number (for example, 7223232,,,361), the number appears in the display panel on the user’s NBX Telephone without the commas and extension number. (IDs 1700 and 3272)
• If a user uses the DCA to park a call on a call park extension that is already in use, the call is not parked and the user is not notified. When the call park timeout period elapses, the call rings back to the user, who can then park the call on another call park extension. (ID 3087)
• If you log in without administrator privileges and install the NBX Desktop Call Assistant software, an error message inappropriately indicates that you cannot install the product because the UninstallShield software is currently running. The message should inform you that you need administrator privileges to perform the installation. (ID 3262)
• If the DCA software is running on a PC that has Windows NT 4.0 installed on it, you can add a range of Call Park extensions, but you cannot add a single Call Park extension. (ID 4457)
NBX Devices Configured Behind a Home Router/Firewall
• If you have an NBX device configured behind a D-Link DI-640 router, the port to which the device is attached may periodically become disabled. (ID 3927)
Workaround for ID 3927: Disconnect the NBX device, reboot the D-Link router, and reconnect the NBX device.
• If you have an NBX device configured behind a 4-port LinkSys Cable/DSL plus Voice Router and you change the port to which the device is connected or you change the IP address of the device, the NBX device can no longer communicate with the host NBX system. (ID 3928)
Workaround for ID 3928: Remove and reapply power to the LinkSys router.
• If you send a VPIM message to an NBX device that is configured behind a home router/firewall, the VPIM software does not use the correct IP address. (ID 3960)
• If the home router/firewall device does not provide sufficient bandwidth, audio quality may be negatively affected for the NBX device behind it. Examples:
• An asymmetric DSL router with the slower speed configured too low.
• Multiple calls over the same channel (either a multiport NBX device or an NBX Business Telephone that has more than one active call).
(ID 3983)
• If you change the configuration on a 3Com OfficeConnect Internet Firewall DMZ (3C16771) to alter the Network Addressing Mode from "NAT with DHCP Client" to "NAT enabled" (or to reverse this change), the change does not take effect until you remove and reapply power to the NBX device behind the firewall. (ID 4378)
NBX Palm Dialer Application
• The NBX Palm Dialer application supports only versions 3.5 and 4.1 of the Palm Operating System.
• If, under the following conditions, you use a Palm Personal Digital Assistant (PDA) with version 3.5.2 of the Palm Operating System:
• You are on a call
• You try to set up a conference call or to transfer the existing call
then the error message “make call first / no resources” appears in the display panel of your 3Com Business Telephone, and the status light associated with the next System Appearance button remains lit until you next remove and reapply power to the telephone. (IDs 743 and 3163)
NBX System Software
• The Auto SaveCore function begins operation properly when a task has been suspended but fails to restart the shell. (ID 3697)
• In System Settings > Regional Settings > Advanced, the Israel and Russia entries in the list should show English for the manuals. They are not translated into Hebrew or Russian. (ID 4000)
NBX TAPI Service Provider Software (NBXTSP)
• The Remote TAPI Service Provider software does not work with the Microsoft Windows XP Home operating system. It does work properly with the XP Professional version. (ID 4387)
• The Remote TAPI Service Provider software does not work with the Microsoft Windows 98 operating system. That operating system does support the TCMSetup command. (ID 4388)
• If a TAPI call is blind transferred to an invalid extension, the NBX system attempts to disconnect the call. The attempt fails, and the call continues to show a status of CONNECTED. (ID 4499)
NBX Telephones
• NBX Telephones with a 3Com order number ending in the letter “B” (3C10281B, 3C10226B, 3C10228IRB) have a port labeled “10101” on the underside of the telephone. This port is not usable. Do not connect anything to this port. (ID 3093)
• On an NBX system with the Italian regional pack installed for voice prompts, a user who logs into voice mail and then presses 9 to hear more options hears prompt number 4 incorrectly speak of how to log out of the mailbox. The prompt should speak about Off-Site Notification. (ID 2942)
• When you set up a Time Dependent Greeting (NBX Messaging > Auto Attendant > Menu Tree > TD Greeting), the NBX system ignores the setting “Use System Wide Greetings.” As a result, the appropriate morning, afternoon, and evening greetings are not played before the Time Dependent Greeting. (ID 3242)
NBX Voice Messaging
• If a user listens to a voice mail message and presses 7 to move backward in the message, the system should replay the message starting at a point 5 seconds earlier. Instead, it goes back approximately 1 second the first time that the user presses 7, and 5 to 6 seconds the second time. (ID 1780)
• If you use the Call Logs on your NBX Telephone while you are listening to one of your voice mail messages, the messaging system behavior is not predictable. For example, the message you are listening to may be deleted or saved, or you may hear the time and date stamp information for the message. (ID 3796)
Off-Site Notification
• Off-Site Notification is not supported over VTL connections. (ID 996)
• If you have Off-Site Notification enabled, someone sends an e-mail message to your voice mailbox, and you attempt to listen to the e-mail message from your telephone, the voice prompt correctly informs you that the message is not a voice mail message and advises you to access it from your PC. However, the Off-Site Notification message that you receive in e-mail has no attachment and no contents; it should contain advisory information similar to the voice prompt’s advice. (ID 1279)
• If you have at least one saved voice mail message in your mailbox, and, in Off-Site Notification, you have configured the first two notification methods to send you e-mail, the NBX system attaches a new voice mail message to only the first off-site notification e-mail, not to the second one. (ID 1786)
• If you configure e-mail as your first and second method of off-site notification, you receive the first e-mail notification with the voice message attached but the second e-mail message has no attachment. (ID 3144)
Polycom Telephony Equipment
• If a 3Com Polycom Telephone is located behind a home router or firewall device, the time and date information in the display panel is updated only when certain external events occur. For example, when you make or receive a call, the display panel information, including the time and date information, is updated. (ID 3910)
Virtual Tie Lines (VTLs)
• Under these conditions, a user on an NBX system hears no ring back signal:
• A user on NBX System A calls a user on NBX System B using a VTL connection.
• The user on System B blind conferences someone on NBX System C into the call, also using a VTL connection.
• The user on System A hears no ring back signal.
(ID 2787)
• If an external call is forwarded from one NBX system to another over a VTL connection before the Central Office equipment provides caller ID information, the caller ID information may not be sent over the VTL connection to update the destination telephone’s display panel. (ID 3996)
• Under these conditions, a call is not properly transferred to voicemail and the caller hears dead air:
• An external call arrives at an NBX system that is running R4.2 system software.
• The call is blind transferred over a VTL line to a second NBX system that is running R4.1.4 or R4.1.21 system software.
• The call is not answered.
(ID 4423)
Voice Profile for Internet Mail (VPIM)
• If a VPIM message cannot be delivered on the first attempt and is queued for a later retry, the number of messages successfully delivered to external recipients is incorrect in the VPIM Statistics window (NBX NetSet > NBX Messaging > VPIM > Statistics). (ID 1111)
• Under some conditions, the VPIM Statistics indicate that a higher-than-actual number of calls were successfully delivered. (ID 3258)
PUTTING A REMOTE NBX® TELEPHONE BEHIND A HOME ROUTER OR FIREWALL: TESTING REPORT FROM THE 3COM VOICE QUALITY ASSURANCE TEAM
You can now have a single NBX device such as an NBX Telephone in your home if you connect to the Internet through certain home router devices.
3Com Firewall/Router Models
Models that have been fully tested and qualified by 3Com Quality Assurance against NBX Release 4.2:
• 3Com OfficeConnect® Cable/DSL Secure Gateway (3CR856-95)
• 3Com OfficeConnect Internet Firewall DMZ (3C16771)
• 3Com OfficeConnect Wireless 11g Cable/DSL Gateway (3CRWE554G72)
Models that share the same code base as one of the fully tested models, but they have not been explicitly tested against NBX Release 4.2:
• 3Com OfficeConnect Internet Firewall 25 (3C16770) — same code as 3C16771
• 3Com OfficeConnect Wireless 11b Cable/DSL Gateway (3CRWE553172) — same code as 3CRWE554G72
Models that were 1) tested previously but found to have performance problems; 2) now have software to resolve the problem on but 3) have not been fully retested to verify resolution:
• 3Com OfficeConnect Cable/DSL Gateway (3C857-US)
• 3Com OfficeConnect Wireless Cable/DSL Gateway (3CRWE52196)
Third-Party Firewall/Router Models
Models that have been tested against NBX Release 4.2:
• D-Link Express EtherNetwork 4-Port Ethernet Broadband Router (DI-604)
Problems of stability and robustness. See the description for PRB 3927.
• LinkSys EtherFast Cable/DSL & Voice Router (BEFN2PS4)
Problems of stability and robustness. See the description for PRB 3928.
• Netgear 4-Port Cable/DSL Router with 10/100 Mbps Switch (RP614NA)
Did not work.
• Netgear 4-Port Cable/DSL ProSafe Firewall/Print Server (FR114PNA)
Configuration problems.
Documentation Comments
As we work to make the documentation easier for you to use, we invite you to send us your feedback on errors that you find in the books and Help systems, and also on areas that you would like to see explained more fully.
Please send your documentation comments to us at the following address:
Voice_TechComm_Comments@3com.com
IMPORTANT: As always, please address all questions about the NBX hardware and software to your 3Com NBX Voice-Authorized Partner.
Thank you.
Copyright ? 2004, 3Com Corporation. All Rights Reserved.
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 26-August-2004
- Thread starter
- #3
techguru69
IS-IT--Management
Thanks!
Any idea why they released it after 4.3.x?
Any idea why they released it after 4.3.x?
GoTellBigDaddy
Vendor
NBX software release R4.2.12 fully supports 3Com eXchange Call Center software version 4.33.00. See the 3Com eXchange Call Center release notes for upgrade information.
Seems to be a patch for the Call Center, there's some holes in 4.3.3; 4.2.7; 4.2.x
Seems to be a patch for the Call Center, there's some holes in 4.3.3; 4.2.7; 4.2.x
- Status
Similar threads
