4.3. Northern Telecom Norstar KSU

• 4.3.1. Norstar KSU Switch Programming Requirements
• 4.3.2. Using the D/42-NS Board
• 4.3.3. Programmable Memory Buttons (10)
• Reading LCD Indicators
• Example 1
• Pressing Memory Buttons Keys
• 4.3.4. Display Buttons
• Reading Display Button Prompts
• Example-2
• Pressing Display Buttons
• 4.3.5. Dual Memory Buttons
• Example
• Pressing Dual Memory Buttons
• 4.3.6. Alphanumeric Display
• Example-1
• Called/calling Number ID (within the KSU)
• Example-2
• 4.3.7. Setting the Message Waiting Indicator
• Example
• 4.3.8. Transferring a Call
• Example

The Norstar Modular product family includes the Compact Key Service Unit (KSU) and the expandable Modular KSU. The D/42-NS can be used with either of these switches. The KSUs use digital signaling to control their station sets and digitized voice. KSUs use plug-in station modules to connect to station sets, and trunk modules to connect to trunk lines.

The D/42-NS board has four channels that are connected directly to a station module in a Northern Telecom KSU. The KSU switch has many standard features that are supported by the D/42-NS, 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.3.1. Norstar KSU Switch Programming Requirements

There are specific switch programming requirements for using a D/42-NS with a Norstar Modular or Compact KSU. You must ensure that these features are set exactly (and assigned to the right keys) so that the D/42-NS and the Unified API function correctly.

Table 10 lists the menu structure used when configuring a Norstar Modular/Compact KSU (with DR5 installed). The shaded areas indicate the actual menu items to change in order to use the KSU with a D/42-NS. 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 answr 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 10. Norstar KSU Configuration Requirements (DR5)

Memory Buttons 00 through 03 must be programmed as follows:

Memory Button 00	Handsfree/mute
Memory Button 01	Intercom
Memory Button 02	Unasigned
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 10, 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 10, A. 2. (f)]. To assign Memory Button 03 to Transfer press:

4.3.2. Using the D/42-NS Board

The D/42-NS board performs functions available to a M7310 telephone set (see Figure 13). An M7310 telephone set uses two LCD displays to show key status (between the line keys) and user prompts and messages (above the display buttons). The D/42-NS can:

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

Figure 13. Northern Telecom M7310 Telephone

4.3.3. Programmable Memory Buttons (10)

There are 10 Programmable Memory Buttons located below the display on the M7310 telephone - see Figure 13. These keys are configured either during KSU installation or by the user (using the telephone set or the D/42-NS). The Line, Intercom, Answer, and Handsfree buttons are assigned during KSU configuration and cannot be programmed the user. There is an LCD Indicator associated with each Memory Button. The LCD Indicators are triangular and can take on one of the five states listed in Table 11.

Table 11. M7310 LCD Indicator States

NOTE:

Ihold appears only on the phone where the call was put on hold. Other phone sets are prevented from picking up the call.

Uhold appears on all extension showing the same line. Any phone set can pick up the call.




Reading LCD Indicators

The D/42-NS 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 (10 bytes) in an application buffer. Bytes 0-9 contain the indicator status for Memory Buttons 00-09, respectively (see Table 12).

Table 12. M7310 Direct Key Dialing Strings for Memory Buttons

Example 1

An application uses the d42_indicators( ) function to retrieve the current data for the LCD Indicators on a given channel on a D/42-NS. The data placed in the application buffer is shown below. If the data for byte 1 is 0x01, the triangular indicator for Memory Button 1 is on. Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_indicators( ) function.

Pressing Memory Buttons Keys

The D/42-NS can "press" any of its Memory Button 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 Memory Button on the M7310 telephone is assigned a dial string sequence (refer to Table 12). By using the dial( ) function and the appropriate dial string, the D/42-NS can press any Memory Button.

4.3.4. Display Buttons

There are three Display Buttons located below the LCD display - see Figure 13. 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 Button Prompts

The D/42-NS 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 Buttons is as follows:

Refer to the D/42 Series Software Reference for your particular operating system for more information about using the d42_display( ) function.

Example-2

An application uses the d42_display( ) function to retrieve the prompt data displayed for Display Button 00 shown in Figure 14. 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 Button 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 14. Example M7310 Display Buttons

Pressing Display Buttons

The D/42-NS can respond to a prompt and "press" the appropriate Display Button 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 Display Button on the M7310 telephone is assigned a dial string sequence (refer to Table 13). By using the dial( ) function and the appropriate dial string, the D/42-NS can press any of its Display Buttons.

Table 13. M7310 Direct Key Dialing Strings for Display Buttons

4.3.5. Dual Memory Buttons

There are 12 Dual Memory Buttons located on top of the M7310 telephone - refer to Figure 13. Each Dual Memory Button can be programmed to perform two different functions (using the Shift key). Dual Memory Buttons can be programmed by the user (or by the D/42-NS) to perform any valid feature available to a phone set.

Example

An application can assign "Do not Disturb" (DND) to Dual Memory Button 00 (DMB 00), then verify that it was programmed correctly. The following functions are performed:

1. Program Dual Memory Button 00 using the dial( ) function and the appropriate dial string (<ESC>KN, <ESC>KK, <ESC>KD, <ESC>KS, <ESC>KN, <ESC>KA, <ESC>KF) to press the following keys:

2. Determine when programming is complete using the d42_display( ) function to retrieve the display data, then read the information for the top row (first 16 characters) of the display. When programming is complete, the message Programmed appears in the display. The data placed in the application buffer is shown below. Data in bytes 00 through 15 indicate that the word Programmed is displayed.

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

3. Verify that Dual Memory Button 00 was programmed correctly by using the dial( ) function and the appropriate dial string (<ESC>KN, <ESC>KK, <ESC>KA, <ESC>KS) to press the following keys:

4. Use the d42_display( ) function to retrieve the display data, then read the information for the top row (first 16 characters) of the display. When the button query is complete, the message Do Not Disturb appears in the display. The data placed in the application buffer is shown below. Data in bytes 00 through 15 indicate that the words Do Not Disturb are displayed.

byte

data

byte

data

byte

5. Exit the button query by using the dial( ) function and the appropriate dial string (<ESC>KP) to press Display Button 00 under the EXIT prompt - see Figure 14.

Pressing Dual Memory Buttons

The D/42-NS can "press" any of its Dual Memory Button 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 Dual Memory Button on the M7310 telephone is assigned a dial string sequence (refer to Table 14). By using the dial( ) function and the appropriate dial string, the D/42-NS can press any Dual Memory Button.

Table 14. M7310 Direct Key Dialing Strings for Dual Memory Buttons

4.3.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
• Display Button 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 D/42-NS 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 D/42 Series Software Reference for your particular operating system for more information about using the d42_display( ) function.

Example-1

An application uses the 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 3.

byte

data

byte

data

byte

Called/calling Number ID (within the KSU)

When receiving a call on a D/42-NS from another extension, the KSU 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 KSU 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 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 15 (as seen by the receiver of the call).

Table 15. Called/calling Number ID Data for the Norstar KSU

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 transferred 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-2

An application uses the d42_gtcallid( ) function to retrieve the calling number ID for a call received on a specified channel on a D/42-NS. The calling number ID data and corresponding ASCII values are shown below.

data

byte

text

data

byte

4.3.7. Setting the Message Waiting Indicator

The D/42-NS can set the Message Waiting display (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:

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

The D/42-NS 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 D/42 Series Software Reference for your particular operating system 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 D/42-NS to determine if a message is waiting - see Figure 15. 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 15. M7310 Message Waiting Display

4.3.8. Transferring a Call

The D/42-NS can transfer calls using the dial( ) function. By using the dial( ) function and the appropriate dial string (&,<extension>), the D/42-NS 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 (<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 D/42-NS 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 KSU 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 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