• 4.6.1. Nortel Meridian 1 Programming Requirements
• 4.6.2. Using the PBX Integration Board
• 4.6.3. Programmable Feature Keys
• Reading LCD Indicators
• Pressing Feature Keys
• 4.6.4. Alphanumeric Display
• Called/Calling Number ID (within the PBX)
• 4.6.5. Setting the Message Waiting Indicator
• 4.6.6. Transferring a Call

4.6. Nortel Meridian 1

The Nortel Meridian 1 is a full-featured PBX that can provide thousands of ports and many PBX voice and data features. The Meridian 1 uses digital signaling to control its station sets and digitized voice. The PBX uses 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 Meridian 1. 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.6.1. Nortel Meridian 1 Programming Requirements

There are specific switch programming requirements for using a PBX Integration board with a Meridian 1. 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.

Table 26 lists the menu structure used when configuring a Nortel Meridian 1. For details about programming a Meridian 1, refer to the appropriate Meridian 1 manual.

The M-1 ports should be configured as a M2616 telephone with a display as follows:

Table 26. Nortel Meridian 1 Configuration Requirements

4.6.2. Using the PBX Integration Board

The PBX Integration board performs functions available to a M2616 telephone set (see Figure 14). An M2616 telephone set uses two LCD displays to show key status (between the line keys) and 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 14. Nortel M2616 Telephone

4.6.3. Programmable Feature Keys

As illustrated in Figure 14, there are 16 Programmable Feature Keys located below the display on the M2616 telephone. These keys are configured either during PBX installation or by the user (using the telephone set or the PBX Integration board). The Line, Program, and Handsfree keys are assigned during PBX configuration and cannot be user programmed. There is an LCD Indicator associated with each Feature Key. The LCD Indicators are triangular and can take on one of the six states listed in Table 27.

Table 27. M2616 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 (16 bytes) in an application buffer. Bytes 00-15 contain the indicator status for Feature Keys 00-15, respectively (see Table 28).

Table 28. M2616 Direct Key Dialing Strings for Feature 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. The data placed in the application buffer is shown below. If the data for byte 1 is 0x01, the triangular indicator for Feature Key 1 is on. Refer to the PBX Integration board Software Reference for more information about using the d42_indicators( ) function.

Pressing Feature Keys

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

4.6.4. Alphanumeric Display

The alphanumeric display is a two row, 48-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

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 (48 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 to press keys dial extension number 1045. 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 24 characters) of the display is checked. Data in bytes 00 through 05 indicate that extension 1045 is being dialed.

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

Table 29. Called/Calling Number ID Data for the Meridian 1

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.6.5. 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. Call the dx_dial( ) function.
   The dial string is <ESCO>,<extention>,<ESCO>

<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. Call the dx_dial( ) function.
   The dial string is <ESCF>,<extention>,<ESCF>

<ESCF> means Escape character followed by F.

We strongly recommend using the pause character (comma) in the dial string for MWI manipulation for Nortel Meridian switch in order to avoid unpredictable result under load.

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 16 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.6.6. 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