3Com ExecutiveAssistant V6.00 Release Notes

2
Known Anomalies and Limitations related to
Version 6.00
The known issues associated with this release are as follows:
• If upgrading your server to EA 6.0 then you must upgrade your client
machines to EA 6.0 as well.
• The EA client program at the user’s station restarts itself when a second
voice prompt is attempted to play back before the first prompt is finished.
(ID 53356)
• When setting up a conference call via the 3Com NBX phone, the Caller ID
displays on the 3Com NBX phone LCD; however, as the call transitions
from a conference call to a non-conference call as a result of the call's
initial extension using the NBX Drop Conference feature, the LCD display
of the originating party will display the Media Port extension instead of the
original Caller ID. (ID 48125)
Workaround for ID 48125: To re-display the caller ID, the original user
should transitions his phone between handset and speakerphone, or on-
hold to off-hold. This is not an issue if using the Star-One/Star-Two feature
to add and remove parties from a conference.
• EA will work with the NBX running in SIP mode but only interfacing with
3Com phones via TAPI and using 3Com Media Driver Licenses. 3Com
SIP phones are not supported.
Star-One/Star-Two
• If the number entered by the party pressing Star-One is not valid, or if
there are no more Media Ports available, then the function fails
• If Star-One is pressed on an NBX phone on the same NBX as EA, then
the other parties do not hear the DTMF tones. If it is pressed from a
phone outside of that NBX, then the other parties hear the DTMF tones for
Star-One or Star-Two, but not the subsequent tones that are dialed after
Star-One
• After 12 parties in a single conference, latency will start to grow upon each
subsequent caller added.
In-And-Out
• Do not pause more than 2.5 seconds between any two digits when
entering the number
General Recording/Monitoring Functionality