4.5. NEC NEAX 2400 ICS and NEAX 2000 IVS PBXs

• 4.5.1. NEC NEAX 2400 ICS and NEAX 2000 IVS PBXs Programming Requirements
• Transfers
• Message Waiting Indicator (MWI)
• Call Progress Analysis
• Telephone Type Assignment
• 4.5.2. Using the D/42-NE2 Board with an NEC PBX
• 4.5.3. Flexible Line Keys (16)
• Reading LED Indicators on the Flexible Line Keys
• Example
• Pressing Flexible Line Keys
• 4.5.4. Feature Keys (5)
• Reading LED Indicators on the Feature Keys
• Example
• Pressing Feature Keys
• 4.5.5. MIC/ICM Indicators
• Reading MIC/ICM LED Indicators
• Example
• 4.5.6. Alphanumeric Display
• Example
• Called/calling Number ID (within the PBX)
• Example
• 4.5.7. Setting the Message Waiting Indicator
• Example
• 4.5.8. Transfer a Call
• Example

The NEAX 2400 ICS and 2000 IVS are full-featured PBXs that can provide thousands of ports and many PBX voice and data features. The PBXs use digital signaling to control their station sets and digitized voice.

The D/42-NE2 board has four channels that are connected to ports on the PBX. Both PBXs have many standard features that are supported by the D/42-NE2, such as:

• direct inward dialing (DID)
• hands free operation
• speed dialing
• hunt groups
• message waiting indication
• user programmable feature keys
• called/calling number identification
• call forwarding.

4.5.1. NEC NEAX 2400 ICS and NEAX 2000 IVS PBXs Programming Requirements

There are specific switch programming requirements for using a D/42-NE2 with a NEAX 2400 ICS or NEAX 2000 IVS PBX. You must ensure that these features (described below) are set exactly (and assigned to the right keys) so that the D/42-NE2 and the Unified API function correctly.

Transfers

Allow the ports connected to the D/42-NE2 permission to use the transfer key.

Message Waiting Indicator (MWI)

The default access dial strings for the D/42-NE2 are set to **9 (on) and ##9 (off). If the PBX has not been set to use these dial strings, you must:

use the d42_setparm( ) function to change D4BD_MSGACCESSON and D4BD_MSGACCESSOFF to the dial string programmed on the PBX ,

or

change the PBX access dial string to **9 (on) and ##9 (off).




Call Progress Analysis

If your application does not use Call Progress Analysis, there is a possibility that under some load conditions your application may receive a busy signal when going off-hook. Depending on your switch configuration, the PBX can only provide a fixed number of simultaneous dial tones. Refer to the Voice Features Guide for MS-DOS (contained in the Voice Software Reference for MS-DOS - Volume 1) for more information about Call Progress Analysis.

Telephone Type Assignment

Ports connected to the D/42-NE2 should be configured as if they were connected to a Dterm Series III telephone.

Call Transfer

To transfer a call using the dial( ) function, the Transfer Key (TRF) must be enabled on the port connected to the D/42-NE2.

Incoming calls to the hunt group can be forwarded by either blind transfers or supervised transfers. If you intend to use blind transfers in a Voice Mail/Auto Attendant environment, the stations receiving the transfers must be programmed to forward calls to the pilot station in the hunt group on Ring/No Answer and Busy. If the stations are not configured this way, any calls transferred back to the PBX because of Ring/No Answer or Busy will not be able to be placed in a mailbox. The Voice Mail/Auto Attendant application can use called/calling number ID to determine how to answer calls transferred back to the PBX.

If you intend to use supervised transfers in a Voice Mail/Auto Attendant environment, the stations receiving the transfers must be programmed not to forward calls to the pilot station in the hunt group on Ring/No Answer and Busy. The Voice Mail/Auto Attendant application can use call progress analysis to determine how to answer calls that could not be forwarded.

4.5.2. Using the D/42-NE2 Board with an NEC PBX

The D/42-NE2 uses different firmware depending on which switch it is connected to (Electra Professional Level II KTS or the NEAX 2400 ICS and NEAX 2000 IVS PBXs). During software installation, you will be asked to choose the type of NEC switch connected to your D/42-NE2 board (KTS or PBX). The installation program will install the appropriate files. Refer to the documentation that contains the software installation procedures for more information.

The D/42-NE2 board performs functions available to a Dterm Series III telephone set (see Figure 17). A Dterm Series III telephone set uses LED indicators to show line key status (on the line keys), function key status (on the function keys), and an LCD display to show user prompts and messages (above the line keys). The D/42-NE2 can:

• transfer calls
• set the message waiting indicator
• read the LCD display
• read LED indicators
• read the called/calling number ID
• press buttons.

Figure 17. NEC Dterm Series III Telephone (NEC PBX)

4.5.3. Flexible Line Keys (16)

There are 16 Flexible Line keys located on the top of the Dterm Series III telephone - see Figure 17. These keys are configure by the system programmer to perform many different functions. When programming the telephone, the Flexible Line keys are used to select the programming mode or sub-mode. There is a two-color LED Indicator associated with each Flexible Line key. The LEDs can take on one of the states listed in Table 20.

Table 20. LED Indicator Status Data for the Dterm Series III (PBX)

Reading LED Indicators on the Flexible Line Keys

The D/42-NE2 can determine the state of the LED Indicators on the Flexible Line keys by using the d42_indicators( ) function to retrieve the LED Indicators data. This function places the LED Indicator data (26 bytes) in an application buffer. Bytes 0-15 contain the indicator status for Flexible Line Keys 01-16, respectively - see Table 21.

NOTE:

The total length of the LED Indicators data is 26 bytes and represents the 24 LED Indicators on a Dterm Series III telephone. Two bytes (16 and 20) are not used.

Table 21. Flexible Line Key Indicators for the Dterm Series III (PBX)

Example

An application uses the d42_indicators( ) function to retrieve the current data for the LED Indicators on a given channel on a D/42-NE2. The data placed in the application buffer is shown below. If the data for byte 1 is 0x0F, the indicator for Flexible Line Key 2 is green and on. Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

NOTE:

You can determine if an indicator is red or green by checking if bit 3 is 0 (red) or 1 (green). The example below shows the binary data for On and Wink.

           Bit    7 6 5 4 3 2 1 0  
On (0x07 red)     0 0 0 0 0 1 1 1  
On (0x0F green)   0 0 0 0 1 1 1 1  
Wink (0x02 red)   0 0 0 0 0 0 1 0  
Wink (0x0A green) 0 0 0 0 1 0 1 0




Pressing Flexible Line Keys

The D/42-NE2 can "press" any of its Flexible Line Keys using the dial( ) function. Refer to the D/42 Series Software Reference for your particular operating system for more information about dialing programmable keys. Each Flexible Line Key on the Dterm Series III telephone is assigned a dial string sequence (refer to Table 21). By using the dial( ) function and the appropriate dial string, the D/42-NE2 can press any Flexible Line Key.

4.5.4. Feature Keys (5)

There are five Feature Keys located next to the dial pad keys (FNC, CNF, LNR/SPD, SPKR, and ANS). There is a two-color LED Indicator associated with each Feature Key. The LED Indicators can take on any one of the states listed in Table 20.

Reading LED Indicators on the Feature Keys

The D/42-NE2 can determine the state of its LED Indicators on the Feature Keys by using the d42_indicators( ) function to read the LED Indicators data. This function places the LED Indicator data (26 bytes) in an application buffer. Bytes 18-23 (byte 20 is not used) contain the LED indicator status for the Feature Keys (see Table 22). Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

Table 22. Feature Key Indicators for the Dterm Series III (PBX)

Example

An application uses the d42_indicators( ) function to retrieve the current data for the LED Indicators for a given channel on a D/42-NE2. The data placed in the application buffer is shown below. If the data for byte 23 is 0x07, the indicator for SPKR is red and on. Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

Pressing Feature Keys

The D/42-NE2 can "press" any of its Feature Keys using the dial( ) function. Refer to the D/42 Series Software Reference for your particular operating system for more information about dialing programmable keys. Each Feature Key on the Dterm Series III telephone is assigned a dial string sequence (refer to Table 22). By using the dial( ) function and the appropriate dial string, the D/42-NE2 can press any Feature Key.

4.5.5. MIC/ICM Indicators

The MIC and ICM indicators are located between the Flexible Line keys and the keypad. In normal operation these indicators show the status of the microphone and the intercom. During programming, these indicators are used as prompts. The MIC and ICM LED indicators can take on any one of the red states (0x00 - 0x07) listed in Table 20.

Reading MIC/ICM LED Indicators

The D/42-NE2 can determine the state of its MIC and ICM LED indicators by using the d42_indicators( ) function to read the LED Indicators data. This function places the LED Indicator data (26 bytes) in an application buffer. Bytes 24 and 25 contain the indicator status for MIC and ICM indicators. Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

Example

An application uses the d42_indicators( ) function to retrieve the current data for the LED Indicators on a given channel on a D/42-NE2. The data placed in the application buffer is shown below. If the data for byte 24 is 0x07, the indicator for MIC is on. Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

4.5.6. Alphanumeric Display

The alphanumeric display is a two row 32-digit LCD that is used to show the activity of the phone. Some examples are:

• date and time
• feature names
• error messages
• called/calling identification
• phone status
• line selection.

The data used to display information in the LCD alphanumeric display is in ASCII format. When the station set is not in use, the display shows the date and time. The content of the display is changed automatically (e.g., receiving an incoming call, making an outgoing call, or activating a feature).

The D/42-NE2 can retrieve the information on the alphanumeric display by using the d42_display( ) function. The function places the display data (32 bytes) in an application buffer. Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_display( ) function.

Example

An application uses the dial( ) function and the appropriate dial string to press keys to enter the programming mode. The d42_display( ) function is then used to retrieve the display data and verify that the program mode has started. The display data is shown below.

byte

data

byte

data

byte

Called/calling Number ID (within the PBX)

When receiving a call on a D/42-NE2 from another extension, the PBX sends calling number ID data (by default, the extension number of the telephone placing the call) to the station set between the first and second rings. The station set processes the data and sends an ID message to the display. The calling number ID data sent from the PBX to the station set differs from the calling number ID data presented on the display.

When placing a call to another extension, the called number ID (by default, the extension of the telephone being called) is shown in the display.

Both the calling and called number IDs can be read using the d42_gtcallid( ) function. The d42_gtcallid( ) function retrieves the called/calling number ID message sent from the KSU to the station set, not the data sent to the display. Refer to the D/42 Series Software Reference for your particular operating system for more information about using d42_gtcallid( ) function.

The contents of the called/calling number ID is shown in Table 23 (as seen by the receiver of the call).

Table 23. Called/calling Number ID Data for the NEC NEAX 2400 ICS and NEAX 2000 IVS PBXs

Call Route	Called/calling Number ID Data
Call received from trunk line 1	_0-1000
Call received from station set 201	_201
Call originally received on trunk line 1, then transferred to station set 200	200_0-1000
Call originally received by extension 200, the transferred to extension 203	203_200

NOTE:

The called/calling number ID can also be obtained using the d42_display( ) function, however, you should use the d42_gtcallid( ) function so that your application will maintain functionality across different manufacturers' switches.

Example

An application uses the d42_gtcallid( ) function to retrieve the called/calling number ID for a call received on a specified channel on a D/42-NE2. The called/calling number ID data is shown below.

data

byte

text

data

byte

4.5.7. Setting the Message Waiting Indicator

The D/42-NE2 can set the Message Waiting Indicator (on or off) on another extension using the dial( ) function and the appropriate dial string. Refer to the D/42 Series Software Reference for your particular operating system for more information about dialing programmable keys.

NOTE:

The Message Waiting Indicator can also be set using the dial( ) function and appropriate dial string to press the Flexible Line Key assigned to send messages (MSG), however, you should use the dial( ) function as described so that your application will maintain functionality across different manufacturers' switches.

The D/42-NE2 can determine the state of its Message Waiting Indicator using the d42_indicators( ) function to read the LED Indicators data. Byte 17 contains the Message Waiting indicator status (0x00 is off; 0x07 is on). Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

Example

An application uses the d42_indicators( ) function to retrieve the LED Indicators data for a specified channel on the D/42-NE2 to determine if a message is waiting. The LED indicators data is shown below. The data 0x00 shows that the MWI indicator is off (there are no messages waiting).

4.5.8. Transfer a Call

The D/42-NE2 can transfer calls using the dial( ) function. By using the dial( ) function and the appropriate dial string (&,<extension>), the D/42-NE2 can transfer a call to any extension connected to the switch. Refer to the D/42 Series Software Reference for your particular operating system for more information about dialing programmable keys.

NOTE:

The transfer function can be performed using the dial( ) function and the appropriate dial string to press the Flexible Line Key assigned to transfer however, you should use the &,<extension> dial string so your application will maintain functionality across different manufacturers' switches.

The D/42-NE2 can perform both supervised and blind transfers (refer to Sections 2.1. Supervised Call Transfer and 2.2. Blind Call Transfer). When a blind transfer is performed, the PBX controls where the call is routed if the called extension is busy or does not answer. When a supervised transfer is performed, your application can implement call progress analysis and called/calling number ID to intelligently control where the call is routed and what type of message is played if the called extension is busy or does not answer. Because of this capability, supervised transfer is the preferred method.

Example

An application answers an incoming call and plays a greeting message prompting the caller to enter the extension they wish to reach (the caller enters 221). Using the dial( ) function with the dial string (&,221), the application attempts to transfer (supervised) the call to extension 221. Call progress analysis is used to determine if extension 221 is answered, busy, or there is no answer. If extension 221 answers, the application hangs up and the transfer is complete. If the extension is busy or not answered, the application reconnects to the incoming call and plays a message asking the caller to choose between accessing voice mail or transferring to the operator.

Click here to contact Dialogic Customer Engineering