The Electra Professional Level II is comprised of a Key System Unit and plug-in modules. It is a fully digital Key Telephone System (KTS) that can support up to 56 CO/PBX lines. The KTS use digital signaling to control its station sets and digitized voice. The KTS has five interface slots, each of which can support up to eight ports (total of 40 ports). The Expansion KSU has three interface slots to allow you to add 16 ports (total of 56 ports).
The D/42-NE2 board has four channels that are connected to ports on the KTS. The Electra Professional Level II KTS switch has many standard features that are supported by the D/42-NE2, such as:
4.4.1. NEC Electra Professional Level II Programming RequirementsThere are specific switch programming requirements for using a D/42-NE2 with a NEC Electra Professional Level II KTS. You must ensure that these features are set exactly (and assigned to the right keys) so that the D/42-NE2 and the Unified API function correctly.
Ports (or connectors) on the KTS are numbered starting at 01. Ports 01 and 02 are used to program the KTS and cannot be connected to a D/42-NE2. When programming, port numbers are used, not station numbers (3-digit extension numbers). The following procedure assumes that you are using a Dterm Series III phone set connected to port 1 or 2.
Enter the Programming mode by pressing FNC, HOLD, #, 0, *.
Telephone Type AssignmentAll D/42-NE2 channels connected to the KTS must be set to Digital Voice Mail. To set the Telephone:
If the D/42-NE2 does not function after this procedure, ensure that the KTS software is at least revision 5.0.
Station Number AssignmentIn order for a KTS port to function properly, it must be assigned a station number.
To assign a Station Number:
Intercom Ring PatternThe Intercom Ring Pattern must be set to Pattern B (default) and the Intercom Tone set to Tone A (default) for Call Progress Analysis to perform accurately. To set the intercom Ring Pattern:
Voice Mail/Auto Attendant Application ConsiderationsWhen using the D/42-NE2 in a Voice Mail/Auto Attendant environment, the following items must be considered:
Setting Up a Hunt Group
A hunt group is used to enable the D/42-NE2 to answer multiple incoming calls. The hunt group contains all the station numbers connected to the D/42-NE2 and is configured in a circular fashion so that when one station is busy, the next available station will receive the incoming call. To create a hunt group do the following:
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 KTS 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 KTS.
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.4.2. Using the D/42-NE2 Board with the NEC KTSThe 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 16). 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:
Figure 16. NEC Dterm Series III Telephone (KTS)

4.4.3. Flexible Line Keys (16)There are 16 Flexible Line keys located on the top of the Dterm Series III telephone - see Figure 16. These keys are configured 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 16.
Table 16. LED Indicator Status Data for the Dterm Series III (KTS)
Binary |
Value (Hex) |
Description |
0000 0000 |
0x00 |
off |
0000 0001 |
0x01 |
flutter (red) |
0000 0010 |
0x02 |
wink (red) |
0000 0011 |
0x03 |
rapid wink (red) |
0000 0100 |
0x04 |
interrupted rapid wink (red) |
0000 0101 |
0x05 |
interrupted wink (red) |
0000 0110 |
0x06 |
interrupted unlit (red) |
0000 0111 |
0x07 |
steady on (red) |
0000 1001 |
0x09 |
flutter (green) |
0000 1010 |
0x0A |
wink (green) |
0000 1011 |
0x0B |
rapid wink (green) |
0000 1100 |
0x0C |
interrupted rapid wink (green) |
0000 1101 |
0x0D |
interrupted wink (green) |
0000 1110 |
0x0E |
interrupted unlit (green) |
0000 1111 |
0x0F |
steady on (green) |
Reading LED Indicators on the Flexible Line KeysThe D/42-NE2 can determine the state of its LED Indicators on the Flexible Line keys by using the d42_indicators( ) function to retrieve the LED Indicators data. This function places the LED Indicators data (26 bytes) in an application buffer. Bytes 0-15 contain the indicator status for Flexible Line Keys 01-16, respectively - see Table 17.
Table 17. Flexible Line Key Indicators for the Dterm Series III (KTS)
Byte |
Description |
Dial Code |
0 |
Flexible Line Key 1 |
<ESC>KW |
1 |
Flexible Line Key 2 |
<ESC>KX |
2 |
Flexible Line Key 3 |
<ESC>KY |
3 |
Flexible Line Key 4 |
<ESC>KZ |
4 |
Flexible Line Key 5 |
<ESC>Ka |
5 |
Flexible Line Key 6 |
<ESC>Kb |
6 |
Flexible Line Key 7 |
<ESC>Kc |
7 |
Flexible Line Key 8 |
<ESC>Kd |
8 |
Flexible Line Key 9 |
<ESC>Ke |
9 |
Flexible Line Key 10 |
<ESC>Kf |
10 |
Flexible Line Key 11 |
<ESC>Kg |
11 |
Flexible Line Key 12 |
<ESC>Kh |
12 |
Flexible Line Key 13 |
<ESC>Ki |
13 |
Flexible Line Key 14 |
<ESC>Kj |
14 |
Flexible Line Key 15 |
<ESC>Kk |
15 |
Flexible Line Key 16 |
<ESC>Kl |
ExampleAn 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 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.

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 KeysThe 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 17). By using the dial( ) function and the appropriate dial string, the D/42-NE2 can press any Flexible Line Key.
4.4.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 16.
Reading LED Indicators on the Feature KeysThe D/42-NE2 can determine the state of its LED Indicators on the Feature 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 18-23 (byte 20 is not used) contain the LED Indicator status for the Feature Keys (see Table 18). Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.
Table 18. Feature Key Indicators for the Dterm Series III (KTS)
Byte |
Description |
Dial Code |
18 |
CNF key LED |
<ESC>KI |
19 |
FCN key LED |
<ESC>KL |
20 |
not used |
|
21 |
LNR/SPD key LED |
<ESC>KH |
22 |
ANS key LED |
<ESC>KM |
23 |
SPKR key LED |
<ESC>KN |
ExampleAn 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 KeysThe 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 18). By using the dial( ) function and the appropriate dial string, the D/42-NE2 can press any Feature Key.
4.4.5. MIC/ICM LED IndicatorsThe 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 16.
Reading MIC/ICM LED IndicatorsThe D/42-NE2 can determine the state of its MIC and ICM LED indicators 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 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.
ExampleAn 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 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.4.6. Alphanumeric DisplayThe alphanumeric display is a two row 32-digit LCD that is used to show the activity of the phone. Some examples are:
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 its 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.
ExampleAn 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.
data |
20 50 52 4F 47 52 41 4D 00 4D 4F 44 45 20 20 20 |
byte |
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
|
| |
data |
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 |
byte |
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
data |
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx |
byte |
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 |
Called/calling Number ID (within the KTS)When receiving a call on a D/42-NE2 from another extension, the KTS 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 KTS 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 retrieved using the d42_gtcallid( ) function. The d42_gtcallid( ) function retrieves the called/calling number ID message sent from the KTS 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 19 (as seen by the receiver of the call).
Table 19. Called/calling Number ID Data for the NEC Electra Professional Level II
Call Route |
|
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 |
ExampleAn 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.
text |
bb 2 0 0 _ 2 0 3 |
|
data |
20 32 30 30 5F 32 30 33 xx xx xx xx xx xx xx xx |
xx xx xx xx xx xx xx xx |
byte |
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
16 17 18 19 20 21 22 23 |
text |
||
data |
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx |
xx xx xx xx xx xx xx xx |
byte |
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
40 41 42 43 44 45 46 47 |
4.4.7. Setting the Message Waiting IndicatorThe 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.
The D/42-NE2 can determine the state of its Message Waiting Indicator using the d42_indicators( ) function to retrieve 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.
ExampleAn 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.4.8. Transferring a CallThe 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.
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 KTS 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.
ExampleAn 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
Copyright 1999, Dialogic Corporation