• 4.1.1. Lucent Switch Programming Requirements
• Port Number Settings
• Message Waiting Light Settings
• 4.1.2. Using the PBX Integration Board
• 4.1.3. Programmable Feature Keys
• Reading LED Indicators
• Pressing Feature Keys
• 4.1.4. Lucent Function Keys
• Pressing Function Keys
• 4.1.5. Display Keys
• Pressing Display Keys
• 4.1.6. Alphanumeric Display
• Called/Calling Number ID (within the PBX)
• 4.1.7. Setting the Message Waiting Indicator
• 4.1.8. Transferring a Call

4. PBX Systems

4.1. Lucent Definity PBXs

The Lucent Definity product family includes the Definity 75/85 (4-wire) and the
Definity G3 (2-wire) PBXs. 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.

A PBX Integration board has either four or eight channels that are connected directly to a station module in a Lucent PBX. The PBX 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.1.1. Lucent Switch Programming Requirements

There are specific switch programming requirements for using a PBX Integration board with a Lucent Definity PBX. You must ensure that the PBX is configured properly so that the PBX Integration board functions correctly.

Port Number Settings

Each board in a Lucent PBX is assigned a port number. The number of ports vary according to the board type (2-wire or 4-wire). A 2-wire board has 16 ports, while the 4-wire boards has eight.

Table 1 lists the structure used when configuring Lucent Definity PBX. For details about programming a Lucent PBX, refer to the appropriate Lucent manual.

The following are examples of the switch settings:

Table 1. Lucent Definity Configuration Example

Slot#	Board Type	Telephone Type	Extension Numbers	Port Settings
3	TN2181 2-wire	8434D	1000-1015	01A0301-01A0316
4	TN2181 2-wire	8434D	1016-1031	01A0401-01A0416
5	TN754B 4-wire	7434D	1032-1039	01A0501-01A0508
6	TN754B 4-wire	7434D	1040-1047	01A0601- 01A0608
7	TN754B 4-wire	7434D	1048-1055	01A0701-01A0708
8	TN754B 4-wire	7434D	1056-1063	01A0801-01A0808

The settings above should be tailored according to the your specific needs.

Message Waiting Light Settings

You must make certain settings from a Lucent management terminal to ensure that Message Waiting Indicator (MWI) features work correctly.

1. Login to switch from a management terminal.
2. Type command `CH STAT <ext>` where ext is the extension of a PBX Integration board port.

   On the Lucent phone sets, go to the Button Assignments page and set button 33 to `lwc-store' and button 34 to `lwc-cancel'.

NOTE:

If these features are programmed into any other button, they must be removed, as there may be only one occurrence of these features per extension.

3. Repeat as necessary for other extensions.

4.1.2. Using the PBX Integration Board

The PBX Integration board performs functions available to Lucent 7434 (4-wire) and 8434 (2-wire) telephone sets (see Figure 2 and Figure 3). These telephone sets use two LED displays per Feature Button to show status (next to the Feature Buttons) and an LCD display to show user prompts and messages (above the display buttons). The PBX Integration board can:

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

Figure 2. Lucent 7434 Telephone

Figure 3. Lucent 8434 Telephone

4.1.3. Programmable Feature Keys

As illustrated in Figure 2 and Figure 3, there are 34 Programmable Feature Keys found on the Lucent 7434 and 8434 telephones. These keys are configured either during installation or by the user (using the telephone set or the PBX Integration board). There are two LED Indicators associated with each Feature Button. The PBX Integration board can also emulate four Lucent Functions Keys: Transfer Conference, Drop, and Hold.

As mentioned above, each line or Feature Key actually has two indicator lights. The red indicator tells the user that the line is being used or that the line will be the one used when the handset is lifted. The green indicator (bottom on the 8434 and right on the 7434) tells the user that the line or feature is in use. In other words, when you pick up the handset or press a Feature Key, the green indicator goes on. When a call is on hold, the green indicator for that line flashes and the red indicator goes off. The red light is either off or on (a value of eight [0x08] indicates ON), while the green light has six possible values. The status of the indicators is obtained by bitwise-ANDing the returned value from the green light with the value from the red light (green light value + red light value). In other words, the value for a line indicator in use with a call would be nine--0x08 (for red light on) + 0x01 (for green light on). The status conditions for each byte of the green light are defined as follows:

Table 2. Lucent 7434 and 8434 LED Indicator States

Reading LED Indicators

The PBX Integration board can determine the state of its LED Indicators by using the d42_indicators( ) function to retrieve the LED Indicators data. This function places the Line Indicator data (34 bytes) in an application buffer. Bytes 1-34 contain the indicator status for Memory Keys 00-33, respectively (see Table 3).

Table 3. Lucent 7434 and 8434
Direct Key Dialing Strings for Feature Keys

Example

An application uses the d42_indicators( ) function to retrieve the current data for the LED Indicators on a given channel on a PBX Integration board. The data placed in the application buffer is shown below. If the data for byte 19 is 0x09 and byte 28 is 0x03, the red and green indicators are on for Feature Button 19 indicating that the line is in use for a call, and the green indicator for Memory Button 28 is flashing, indicating that the call is on hold.

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

Pressing Feature Keys

The PBX Integration board can "press" any of the Lucent 7434 or 8434's Feature Keys using the dx_dial( ) function. Refer to the PBX Integration Software Reference for more information about dialing programmable keys. Each Feature Button on the 7434 and 8434 telephones is assigned a dial string sequence (refer to Table 3). By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can press any Feature Button.

4.1.4. Lucent Function Keys

Lucent telephones also include Function Keys that the PBX Integration board can emulate to perform various functions. PBX Integration board can emulate four Lucent Functions Keys: Transfer, Conference, Drop, and Hold.

Pressing Function Keys

The PBX Integration board can "press" Lucent telephone Function Keys using the dx_dial( ) function. The Function Keys on the Lucent 7434 and 8434 telephones assigned a dial string sequence are listed in Table 4. By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can dial these four Lucent Function Keys. Refer to the PBX Integration board Software Reference for more information about dialing programmable keys.

Table 4. Lucent 7434 and 8434 Direct Key Dialing Strings for Function Keys

Dial String	Key Description
<ESC>Ki	Hold
<ESC>Kj	Drop
<ESC>Kk	Transfer
<ESC>Kl	Conference

4.1.5. Display Keys

As shown in Figure 3, there are five 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). The PBX Integration board cannot use the two bottom, right-most Keys, Prev and Next.

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 Lucent 8434 telephone is assigned a dial string sequence (refer to Table 5). By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can press any of its first seven Display Keys.

Table 5. 8434 Direct Key Dialing Strings for Display Keys

4.1.6. Alphanumeric Display

The alphanumeric display is a two row, 50-digit LED 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 LED 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_displayex( ) function. The function places the display data (50 bytes) in an application buffer. Refer to the PBX Integration board Software Reference for more information about using the d42_displayex( ) function.

Example

An application uses the dx_dial( ) function and the appropriate dial string to press keys to dial extension number 1045. 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 (last 25 characters) of the display is checked. Data in bytes 00 through 05 indicate that extension 1045 is being dialed.

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

Table 6. Called/Calling Number ID Data for the Lucent Definity

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_displayex( ) 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.1.7. Setting the Message Waiting Indicator

The PBX Integration board can set the Message Waiting Indicator (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 Indicator using the d42_indicators( ) function to retrieve the LED Indicators data. Byte 34 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 LED indicators data is shown below. The data 0x00 shows that the MWI indicator is off (there are no messages waiting).

4.1.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; 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