• 4.4.1. MITEL SUPERSWITCH Programming Requirements
• MITEL SX Requirements for using MWI
• 4.4.2. Using the PBX Integration Board
• 4.4.3. Programmable Personal Keys
• Reading LCD Line Indicators
• Pressing Personal Keys
• 4.4.4. Function Keys
• Pressing Function Keys
• 4.4.5. Display Keys
• Reading Display Key Prompts
• Pressing Display Keys
• 4.4.6. Alphanumeric Display
• Called/Calling Number ID (within the PBX)
• 4.4.7. Setting the Message Waiting Indicator
• 4.4.8. Transferring a Call

4.4. MITEL SUPERSWITCH PBXs

MITEL PBXs use digital signaling to control its station sets and digitized voice. Digital Network Interface Circuit (DNIC) Line Cards provide an interface between the station sets and the switch.

The PBX Integration board has four or eight channels that are connected to a MITEL DNIC Line Card. The PBX Integration board can be used with the SX-50, SX-200ML, and SX-2000 PBXs. These MITEL PBXs have many standard features that are supported by the PBX Integration board, 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.4.1. MITEL SUPERSWITCH Programming Requirements

There are specific switch programming requirements for using a PBX Integration board with a MITEL SUPERSWITCH. You must ensure that these features are set exactly (and assigned to the right keys) so that the PBX Integration board and the Unified API function correctly.

The PBX uses Class of Service (COS) to determine which features are available to an extension. The features available to an extension are shown in the telephone set's LCD Features display. Any feature not in the COS will not be displayed.

MITEL SX Requirements for using MWI

If you are using a MITEL SX and wish to use the set Message Waiting Indicators (MWI) feature, the PBX Integration board must enable Auxiliary Attendant capabilities, and a line key must be set to act as the Attendant Console MWI. To configure MWI on a MITEL SUPERSWITCH:

• Enable Auxiliary Attendant capabilities
• Configure Personal Key 02 (see Figure 8) to act as to act as an Attendant Console Message Waiting Indicator key.

See MITEL manuals for more information on programming a SUPERSWITCH.

Configure a COS to have enhanced Auxiliary Attendant capabilities

1. From an attendant console, enter Programming Mode.
2. Enter the Command Number corresponding to the COS to which you want to add Auxiliary Attendant capabilities. Use commands 121 through 129 for COS 1 through COS 9. For example, if you want to change COS 9, use Command Number 129.
3. Set register 7, field "d" (Auxiliary Attendant Position) to 1 (enable Auxiliary Attendant Position).for the desired COS (1 - 9). The illustration below shows the Auxiliary Attendant feature enabled on COS 9.

4. Exit the Programming Mode.

For more information, see the MITEL SUPERSWITCH manuals.

Programming a Personal Key to act as an Attendant Console MWI key

1. On a 420/430 Superset phone, press the SuperKey.
2. Press the "No" Display Key until the display screen shows "Personal Keys," then press the "Yes" Display Key.
3. Press Personal Key 02, which is the third key from the bottom right.
   4. If the screen shows that Personal Key 02 is programmed differently than as the MWI, press the "Change" Display Key.
5. Press the "No" Display Key until the screen shows: "Att. func keys," then press the "Yes" Display Key.
6. After the screen shows "Dial feature No," use the keypad to enter the number "10" for message waiting.
7. After the display screen shows "10 = msg wait," press the "Save" Display Key to confirm and exit.

To determine the current setting of a Feature key, press the SUPERKEY and then press the Feature Key you want to check. The display shows the name of the feature programmed.

4.4.2. Using the PBX Integration Board

The PBX Integration board performs functions available to a SUPERSET 400 Series telephone sets. As shown in Figure 8, a SUPERSET 420 telephone set uses two LCD displays to show line status (next to the line keys) and user prompts (above the soft keys):

• transfer calls
• set the message waiting indicator
• read the LCD alphanumeric display
• read the LCD features display
• read the LCD prompts display
• read LCD line indicators
• read the calling number ID
• press keys.

Figure 8. MITEL SUPERSET 400 Series Telephone

4.4.3. Programmable Personal Keys

As seen in Figure 8, there are 12 Personal Keys located on the top-right portion of SUPERSET 400 telephones. Some of these keys are configured when the PBX is programmed to select preassigned lines. Keys that are not configured can be defined by the user (using the telephone set or the PBX Integration board) as speed dial or Feature Keys. There is an LCD Line Indicator associated with each Personal Key. The LCD Indicators are triangular and can take on one of the six states listed in Table 14.

Table 14. MITEL SUPERSET 400 Series LCD Line Indicator States

Reading LCD Line Indicators

The PBX Integration board can determine the state of its Line Indicators by using the d42_indicators( ) function to retrieve the LCD Indicators data. This function places the Line Indicator data (12 bytes) in an application buffer. Bytes 0-11 contain the indicator status for Feature Keys 00-11, respectively (see Table 15).

Table 15. MITEL SUPERSET 400 Series LCD Line Indicators and Dial Strings

*line, speed dial, or feature access

Example

An application uses the d42_indicators( ) function to retrieve the current data for the LCD Line Indicators for a given channel on a PBX Integration board. The data placed in the application buffer is shown below. If the data for byte 07 is 0x02, the indicator corresponding to the Feature Key 07 is indicating ringing (see Figure 9). Refer to the PBX Integration board Software Reference for more information about using the d42_indicators( ) function.

Figure 9. MITEL SUPERSET LCD Line Indicator

Pressing Personal Keys

The PBX Integration board can "press" any of the MITEL SUPERSET Personal Keys using the dx_dial( ) function. Refer to the PBX Integration board Software Reference for more information about dialing programmable keys. Each Personal Key on the MITEL SUPERSET telephone is assigned a dial string sequence (refer to Table 15). By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can press any Personal Key.

4.4.4. Function Keys

As shown in Figure 8, there are a number of Function Keys found to the left of the dial key pad on the MITEL SUPERSET telephones. The PBX Integration board can emulate these keys to perform various operational functions.

Pressing Function Keys

The PBX Integration board can "press" any of its function key using the dx_dial( ) function. Each function key on SUPERSET 400 series telephones is assigned a dial string sequence (refer to Table 16 and Table 17 ). By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can dial any of its function keys. Refer to the PBX Integration board Software Reference for more information about dialing programmable keys.

Table 16. MITEL SUPERSET 420 Direct Key Dialing Strings for Function Keys

Dial String	Key Description
<ESC>KM	Message Key
<ESC>KN	SuperKey
<ESC>KO	Cancel
<ESC>KP	Microphone
<ESC>KQ	Hold
<ESC>KR	Redial
<ESC>KS	Speaker
<ESC>KT	Trans/Conf
<ESC>KU	V/T/C up
<ESC>KV	V/T/C down

Table 17. MITEL SUPERSET 430 Direct Key Dialing Strings for Function Keys

Dial String	Key Description
<ESC>KM	Message Key
<ESC>KN	SuperKey
<ESC>KO	Not Used
<ESC>KP	Microphone
<ESC>KQ	Hold
<ESC>KR	Applications
<ESC>KS	Speaker
<ESC>KT	Not Used
<ESC>KU	V/T/C up
<ESC>KV	V/T/C down

4.4.5. Display Keys

As shown in Figure 8, there are three Display Keys or Soft Keys located below the LCD display on the MITEL SUPERSET 420 telephone. These keys are associated with specific prompts shown on the LCD display depending on the current state of the phone.

NOTE:

This information applies to the SUPERSET 420 only. The PBX Integration board cannot detect the Display Key prompts on the SUPERSET 430. The PBX Integration board can, however, "press" the Display Keys on both telephones. See Pressing Display Keys below.

Reading Display Key Prompts

The PBX Integration board can determine which of its prompts are currently displayed by using the d42_display( ) function to retrieve display data and read the information for the bottom row (last 16 characters). The total length of the display data is 32 bytes. The data location for the Display Key prompts is as follows:

Refer to the PBX Integration board Software Reference for more information about using the d42_display( ) function.

Example

An application uses the d42_display( ) function to retrieve the prompt data displayed for Display Key 00, as shown in Figure 10. The data placed in the application buffer is shown below. Data in bytes 16 through 31 indicate that the prompts Yes and No are displayed below Display Keys 00 and 02, respectively.

NOTE:

Bytes 00-15 represent the top row of the display. Bytes 16-31 represent the bottom row of the display.

byte

data

byte

data

byte

Figure 10. MITEL SUPERSET 420 Display Keys

Pressing Display Keys

The PBX Integration board can respond to a prompt and "press" the appropriate Display Key using the dx_dial( ) function. Refer to the PBX Integration board Software Reference for more information about dialing programmable keys. As shown in Table 18 and Table 19, each Display Key on the SUPERSET 400 series telephones is assigned a dial string sequence. By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can press any of its Display Keys.

Table 18. MITEL SUPERSET 420 Direct Key Dialing Strings for Display Keys

Table 19. MITEL SUPERSET 430 Direct Key Dialing Strings for Display Keys

4.4.6. Alphanumeric Display

The alphanumeric display is a 32-or 80-digit LCD that is used to show:

• date and time when the extension is idle
• SuperKey instructions and Softkey labels during programming and feature access
• call status
• messaging information
• telephone system error messages
• saved numbers (speed dialing)
• saved number for redial
• timed reminder setting
• call forward type and destination
• calling number ID
• trunk line ID

The data used to display information in the LCD alphanumeric display is in ASCII format. When the telephone is not in use, the display normally 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 PBX Integration board can retrieve the information on its display using the d42_display( ) function. The function places the display data (32 or 80 bytes) in an application buffer. Refer to the PBX Integration board Software Reference for more information about using the d42_display( ) function.

Example

An application uses the dx_dial( ) function to press the "SuperKey" key and "Display Key 1" for "Yes" on a specified channel on the PBX Integration board to display the call forwarding extension. The d42_display( ) function is then used to retrieve the display data and verify that a call forwarding extension has not been programmed. The display data is shown below.

byte

data

byte

data

byte

Called/Calling Number ID (within the PBX)

When receiving a call on a PBX Integration board 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 retrieved using the d42_gtcallid( ) )function. The d42_gtcallid( ) function retrieves the called/calling number ID message sent from the PBX to the station set, not the data sent to the display. Refer to the PBX Integration board Software Reference for more information about using d42_gtcallid( ) function.

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

Table 20. Called/Calling Number ID Data for the Hicom

Call Route	Called/Calling Number ID Data
Call received from trunk line 1	_0-1
Call received from station set 221	_221
Call originally received on trunk line 1, then transferred to station set 223	223_0-1
Call originally received by extension 221, then forwarded to extension 224	224_221

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 calling number ID for a call received on a specified channel on a PBX Integration board. The calling number ID data and corresponding ASCII values are shown below.

data

byte

text

data

byte

4.4.7. Setting the Message Waiting Indicator

The PBX Integration board can set the Message Waiting Indicator (ON or OFF) on another extension using the dial( ) function and the appropriate dial string, as described in the PBX Integration board Software Reference for your particular operating system.

NOTE:

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

MWI On

The recommended technique to turn on the MWI in this switch, using dx_dial( ) with the dial string is:

1. Go Off Hook using dx_sethook( )
2. Call the dx_dial( ) function. The dial string is <ESCO><extention><ESCO> (Optional pause character may be used)
3. Go On hook using the dx_sethook( ) again

<ESCO> means Escape character followed by O.

MWI Off

The recommended technique to turn off the MWI in this switch, using dx_dial( ) with the dial string is:

1. Go Off Hook using dx_sethook( )
2. Call the dx_dial( ) function. The dial string is <ESCF><extention><ESCF> (Optional pause character may be used)
3. Go On hook using the dx_sethook( ) again

<ESCF> means Escape character followed by F.

The PBX Integration board can determine the state of its Message Waiting Indicator using the d42_indicators( ) function to retrieve the LED Indicators data. Byte 13 contains the Message Waiting indicator status (0x00 is off; 0x01 is on). Refer to the PBX Integration board Software Reference 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 PBX Integration board to determine if a message is waiting. The indicators data is shown below. The data 0x01 shows that the MWI indicator is on (there are messages waiting).

4.4.8. Transferring a Call

The PBX Integration board can transfer calls using the dx_dial( ) function. By using the dx_dial( ) function and the appropriate dial string (&,<extension>), the PBX Integration board can transfer a call to any extension connected to the switch. Refer to the PBX Integration board Software Reference for more information about dialing programmable keys.

NOTE:

The transfer function can be performed using the dx_dial( ) function and the appropriate dial string to press the Trans/Conf soft key; however, you should use the &,<extension> dial string so your application will maintain functionality across different manufacturers' switches.

The PBX Integration board 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 dx_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