• 4.5.1. Nortel Norstar Programming Requirements
• 4.5.2. Using the PBX Integration Board
• 4.5.3. Programmable Memory Keys
• Reading LCD Indicators
• Pressing Memory Keys
• 4.5.4. Display Keys
• Reading Display Key Prompts
• Pressing Display Keys
• 4.5.5. Alphanumeric Display
• Called/Calling Number ID (within the PBX)
• 4.5.6. Setting the Message Waiting Indicator
• 4.5.7. Transferring a Call

4.5. Nortel Norstar

The Norstar product family includes the Compact version and the expandable Modular model. The PBX Integration board can be used with either of these switches. The PBXs use digital signaling to control their station sets and digitized voice. PBXs use plug-in station modules to connect to station sets, and trunk modules to connect to trunk lines.

The PBX Integration board has either four or eight channels that are connected directly to a station module in a Nortel Norstar. The switch has 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.5.1. Nortel Norstar Programming Requirements

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

Table 21 lists the menu structure used when configuring a Nortel Norstar (with DR5 or later revision installed). The shaded areas indicate the actual menu items to change in order to use the KSU with a PBX Integration board. For details about programming a Norstar KSU, refer to the appropriate Norstar manual.

The table only shows the configuration for one trunk line (001) and one extension (221). If you are using more than one trunk line, configure each trunk line the same. If you are using more than one extension, ensure that all the extensions are configured the same with the exception of the Forward on busy and Forward no answer options. For these menu items, the first extension should be forwarded to the second extension and the second extension should be forwarded to the third extension, and so on. The last extension should be forwarded back to the first extension.

Table 21. Norstar Configuration Requirements (DR5)

Table 21. Norstar Configuration Requirements (DR5) - (Cont.)

Table 21. Norstar Configuration Requirements (DR5) - (Cont.)

Memory Keys 00 through 03 must be programmed as follows:

Memory Button 00	Handsfree/mute
Memory Button 01	Intercom
Memory Button 02	Intercom
Memory Button 03	Transfer (Feature 70)

To determine the current setting of a Memory Button, press

then press the Memory Button you want to check. The display shows the name of the feature programmed.

Memory Button 00 is automatically assigned as the Handsfree/mute key when Full Handsfree is set to Y [refer to Table 21, B. 5. (c) (4)]. Memory Button 01 is automatically set as the Intercom key when the number of intercom keys is set to 1 [refer to Table 21, A. 2. (f)]. To assign Memory Button 03 to Transfer press:

4.5.2. Using the PBX Integration Board

The PBX Integration board performs functions available to a M7324 telephone set (see Figure 11). An M7324 telephone set uses three LCD displays. Two is used to show key status indicators (between the line keys), while the other display is used for user prompts and messages (above the display keys). The PBX Integration board can:

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

Figure 11. Nortel M7324 Telephone

4.5.3. Programmable Memory Keys

As illustrated in Figure 11, the M7324 has 24 Programmable Memory Keys located to the right of the display . These keys are configured either during PBX installation or by the user (using the telephone set or the PBX Integration board). The Line, Intercom, Answer, and Handsfree keys are assigned during PBX configuration and cannot be user programmed. There is an LCD Indicator associated with each Memory Button. The LCD Indicators are triangular and can take on one of the six states listed in Table 22.

Table 22. M7324 LCD Indicator States

Reading LCD Indicators

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

Table 23. M7324 Direct Key Dialing Strings for Memory Keys

Example

An application uses the d42_indicators( ) function to retrieve the current data for the LCD Indicators on a given channel on a PBX Integration board. In the M7324 example shown below, data has been placed in the application buffer. If the data for byte 1 is 0x01, the triangular indicator for Memory Button 1 is on. Refer to the PBX Integration board Software Reference for more information about using the d42_indicators( ) function.

Pressing Memory Keys

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

4.5.4. Display Keys

As shown in Figure 11, there are three Display Keys located below the LCD display. These keys are associated with specific prompts shown on the LCD display depending on the current state of the phone (shown on the bottom row of the LCD display).

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 Keys 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 12. The data placed in the application buffer is shown below. Data in bytes 16 through 20 indicate that the prompt EXIT is displayed below Display Key 00.

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 12. M7324 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. Each Display Key on the M7324 telephone is assigned a dial string sequence (refer to Table 24). By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can press any of its Display Keys.

Table 24. M7324 Direct Key Dialing Strings for Display Keys

4.5.5. 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
• Display Key prompts.

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 alphanumeric display using the d42_display( ) function. The function places the display data (32 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 and the appropriate dial string (ESC>KN, <ESC>KK, <ESC>KA, <ESC>K3) to press keys to display which feature is assigned to Memory Button 03. Then, the d42_display( ) function is used to retrieve the display data and place it in an application buffer (shown below). The information for the top row (first 16 characters) of the display is checked. Data in bytes 00 through 15 indicate that Transfer is assigned to Memory Button 03.

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 25 (as seen by the receiver of the call).

Table 25. Called/Calling Number ID Data for the Nortel Norstar

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.5.6. Setting the Message Waiting Indicator

The PBX Integration board can set the Message Waiting display (on or off) on another extension using the dx_dial( ) function and the appropriate dial string. Refer to the PBX Integration board Software Reference for more information about dialing programmable keys.

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 display using the d42_display( ) function to retrieve the display data. Bytes 00 through 15 are used for the message waiting prompt and will display Message for you. 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 display data for a specified channel on the PBX Integration board to determine if a message is waiting (see Figure 13). The display data is shown below.

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 13. M7324 Message Waiting Display

4.5.7. 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 (<ESC>KN, <ESC>KH, <ESC>KA; or <ESC>KN70) to press Feature 70. This method does not depend on Memory Button 03 being programmed correctly; 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 the 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 a 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