Specifications

4 Integration Technical Note
©June 2003 Ericsson Enterprise AB NEC NEAX 2000/2400 MCI
EN/LZT 108 6656 R1A
Critical Application Considerations
Known limitations or conditions within the telephone system and OneBox that
affect the integration performance are listed here. General recommendations are
provided when ways to avoid these limitations exist.
No error or alarm condition is generated on either the NEAX or the
OneBox system when the MCI datalink is disrupted.
Calls to stations in Do Not Disturb (DND) will forward to OneBox as busy
forwarded calls. For this reason, it is recommended that subscribers not use
DND and the announce busy feature of OneBox at the same time.
OneBox subscribers without telephones must not have the MWI feature
enabled in their mailboxes.
Use only analog PBX linecards that support open loop disconnect signaling.
Calls to any UCD group within the same tenant are reported to the MCI port
and to OneBox. Data packets from non-OneBox UCD groups will generate
errors in OneBox. To avoid invalid UCD data being sent to OneBox,
program the UCD hunt group for OneBox into a separate tenant of the
NEAX.
OneBox voice ports must be members of the UCD group to receive calling-
and called-party information from the MCI port.
Do not enable the Message Waiting Set capability for station users. End users
must have Message Waiting and Message Reminder Set disabled. If both
OneBox and end users are able to set and clear message waiting (MW),
conflict and confusion will result.
Additional Considerations for NEAX 2000
The pilot number of the OneBox UCD group may be a phantom number.
However, if a phantom number is used, callers transferred from the
attendant console to voice mail will first hear a prompt explaining that
extension XXXX (the phantom pilot number) does not answer before
playing the main greeting.