I n t e g r a t i o n Te c h n i c a l N o t e NEC NEAX 2000/2400 MCI
Integration ii Te c h n i c a l Note Edition Note This is the first edition of the NEC NEAX 2000/2400 MCI Integration Technical Note. Information in this document applies to OneBox UM systems with Version 3.0 or later. Copyright Not Notice ice NEC NEAX 2000/2400 MCI EN/LZT 108 6656 R1A © Ericsson Enterprise AB 2003. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.
Integration Te c h n i c a l Note iii Table of Contents Overview....................................................................................................................................... 1 References.......................................................................................................................................................... 2 Features Supported by this Integration.....................................................................................................
Integration iv Te c h n i c a l Note This page is intentionally left blank.
Integration Te c h n i c a l Note 1 Overview This Integration Technical Note (ITN) is written for dealers who are experienced with OneBox UM® and are familiar with its procedures and terminology. It also assumes that you are familiar with the features and programming of the NEC NEAX 2000 IVS or NEC NEAX 2400 IMX telephone system.
Integration 2 Te c h n i c a l Note References More current information may be available from the following documents: • Installing OneBox • Administering OneBox Features Supported by this Integration Tables 1 and 2 list the features supported with the NEC NEAX MCI integration. Table 1.
Integration Te c h n i c a l Note 3 Table 2.
Integration 4 Te c h n i c a l Note 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.
Integration Te c h n i c a l Note 5 Additional Considerations for NEAX 2400 • Do not assign a phantom number as the pilot number of the UCD group. Instead, assign the first port of the UCD group as the pilot number. Use of a phantom pilot number does not allow data to be sent to the MCI port. • The MCI interface must be programmed to use the Feature 2 Application format. • Direct calls from the attendant console to OneBox are not reported to the MCI port.
Integration 6 Te c h n i c a l Note Installation Requirements Review the following information before performing any of the procedures in this document. To successfully install this integration, you must meet the installation requirements for the telephone system and for OneBox.
Integration Te c h n i c a l • Note 7 One loop-start station for each OneBox port to be configured Use 16LCQ or 16LCBE cards, or their equivalent, because of their ability to provide open loop-current disconnect signaling. The LCQ card provides a fixed 128-194 ms. open on disconnect and the LCBE card has a programmable open loop duration. OR • A PA-24DTR digital trunk interface configured as T1 loop-start stations, which will provide up to 24 channels to OneBox.
Integration 8 Te c h n i c a l Note Programming the NEC NEAX 2000 IVS Follow the recommendations and programming examples in this section to program the NEAX 2000 IVS for integration with OneBox. Programming examples show commands and parameters that are necessary for integration; they do not represent PBX programming in its entirety. The installing technician should be familiar with programming the telephone system.
Integration Te c h n i c a l Note 9 Data Programming for MCI Use the commands listed below to program and define the MCI data port for VMS. 1. Command Code CM08: ST+08+DE+025+DE+0+EXE (Provide MSG display message) ST+08+DE+443+DE+0+EXE (Provide VMS with MCI) ST+08+DE+444+DE+0+EXE (Provide MW control from VMS with MCI) ST+08+DE+376+DE+0+EXE (Provide MW over CCIS if used) 2. Command Code CM90. Assign the data to provide the MW lamp on a Dterm, if required. ST+9000+DE+My Line No. +,+Key No. DE+F1005+EXE 3.
Integration 10 Te c h n i c a l Note Table 3. CMD001: Assigning the Port 3 Attribute Data to the MCI port First Data Description Second Data Value 20 Baud 5 9600 21 Stop Bit 0 1 22 Data Length 1 8 23 Parity 0 None 80 Function 24 MCI Programming the Analog VMS Ports for OneBox Program extension numbers to the single-line ports that will be used as OneBox voice ports. Choose an easily remembered number for the pilot number of the UCD group that subscribers will dial for OneBox.
Integration Te c h n i c a l Note 11 3. Command Code CM15: Modify the OneBox Service Class Restriction group that was programmed in CM12. It is not necessary to change default settings other than those listed in Table 4. ST+15YY/YYY+DE+SERVICE RESTRICTION CLASS A/B/C (00-15)+DE+DATA (1 digit)+EXE Table 4.
Integration 12 Te c h n i c a l Note Programming the UCD Group for OneBox Ports Create a UCD group, assign a UCD pilot number, and assign the OneBox ports to the group in ascending order. If necessary, program the OneBox UCD group into a tenant separate from all other non-MCI UCD groups to prevent OneBox from receiving invalid MCI packets from other non-related UCD groups in the same tenant. A maximum of sixty stations can be assigned.
Integration Te c h n i c a l Note 13 Programming the Subscriber Stations Program the subscriber stations for use with OneBox. Allow forwarding types relevant to your application and enable Message Waiting/Message Reminder capability for each subscriber. To prevent conflicts and confusion, only OneBox should have the set and clear message-waiting capability. Disable message-waiting set/clear capabilities on all subscriber stations. 1. Command Code CM15.
Integration 14 Te c h n i c a l Note Programming the NEC NEAX 2400 IMX Follow the recommendations and programming examples in this section to program the NEAX 2400 IMX for integration with OneBox. Programming examples show commands and parameters that are necessary for integration; they do not represent PBX programming in its entirety. The installing technician should be familiar with programming the telephone system.
Integration Te c h n i c a l Note 15 Programming the MCI Port Use the ASYD command to assign system data necessary for the MCI port. Follow the recommendations in Table 6 to program the system data necessary to configure the MCI port for OneBox. Table 6.
Integration 16 Te c h n i c a l Note Programming the UCD Group Use the ASHU command to assign the OneBox ports to a UCD station hunt group. If necessary, program the OneBox UCD group into a tenant separate from all other non-MCI UCD groups to prevent OneBox from receiving invalid MCI packets from other non-related UCD groups. A maximum of 20 ports may be included in any UCD group.
Integration Te c h n i c a l Note 17 Configuring OneBox Once the telephone system is programmed, you must configure OneBox for the integration. During setup, you’ll need the following information, specific to this integration, to configure OneBox. 1. In the Installation Configuration dialog box, enter the name of your site in the Site Name box, the mailbox length in digits in the Mailbox Length box, and the first extension number for the first line in the First Extension box.
Integration 18 Te c h n i c a l Note Completing the Integration Now you are ready to finish installing OneBox UM. See the guides Installing OneBox and Administering OneBox, or refer to the OneBox online help system, for instructions. For general information on integrations, you may also wish to consult “Integrating OneBox with the Telephone System,” in the guide Installing OneBox, and the topic “Integrate the Telephony Server with the telephone system,” in the online help system.
