• 4.3.1. Siemens Hicom Programming Requirements
• Siemens Hicom 150E
• Siemens Hicom 300E
• 4.3.2. Using the PBX Integration Board
• 4.3.3. Programmable Feature Keys
• Reading LED Indicators
• Pressing Feature Keys
• 4.3.4. Alphanumeric Display
• Called/Calling Number ID (within the PBX)
• 4.3.5. Setting the Message Waiting Indicator
• 4.3.6. Transferring a Call

4.3. Siemens Hicom PBX

The Siemens Hicom are a full-featured PBXs that can provide thousands of ports and many PBX voice and data features. The Hicom uses digital signaling to control its station sets and digitized voice.

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

There are specific switch programming requirements for using a PBX Integration board with a either a Siemens Hicom 150E or a Hicom 300E PBX. This allows the D./82JCT-U to correctly emulate a Optiset E telephone. Note that the programming is quite different for the two Hicom PBXs supported, so 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.

Siemens Hicom 150E

When the Hicom 150E is used with Optiset E phones (see Figure 5), the top three programmable keys on the right must be programmed as General Call, Send Message, and Consultation keys, respectively. If these keys are not programmed in this manner, loop current detection, CPID, & (transfer) key, and message waiting will not work. This programming can be accomplished using the following instructions:

1. On the Siemens Optiset E phone, press the Service Menu key, which is the top left programmable key.
2. Press the Scroll Forward key (>) repeatedly to scroll through the choices until the display screen shows "*91 prog feature key," and then press the Select OptiGuide key (the key with the check mark).
3. Press the top right programmable key.
4. After the screen displays the current assignment for the key, press the Select OptiGuide key to change the assignment.
5. Press the Scroll Forward key repeatedly to scroll through the choices until the display screen shows "General call key," and then press the Select OptiGuide key.
6. Press the Select OptiGuide key again to save and exit.
7. Repeat the above procedure for the second and third programmable key on the top right, programming the second key as the "Send message" key and the third key as the "Consultation" key.

Siemens Hicom 300E

When the Hicom 300E is used with Optiset E phones (see Figure 6), the top two programmable keys (Key 00 and 01) on the left must be programmed as Mailbox and Callback, respectively. Key 02 must be configured to dial the message waiting lamp on (MWL_ON) string. Key 03 must be configured to dial the message waiting lamp off (MWL_OFF) string. This programming allows an application to use the specified dial string to turn the MWL on and off. In addition, Key 07 must be programmed as the Consultation (transfer) key. Keys 08-12 must be programmed as Line keys, with Key 12 programmed as the General Call Key, which provides the off-hook indicator. Refer to Figure 5 and Table 11 for specific Key locations and set-up requirements.

If these keys are not programmed in this manner, loop current detection, CPID, & (transfer) key, and message waiting will not work.

To configure Keys 02 and 03 for the MWL functionality, use the following instructions:

1. Need a button programmed as PROG in the PBX
2. Program DDS keys on button 02 and 03 in the button table of the PBX
3. Press the Scroll Forward key (>) repeatedly to scroll through the choices Siemens Optiset E phone to reach the Program/Service option on the display.
4. Press the Select OptiGuide key (the key with the check mark) to select.
5. Press the Select OptiGuide key again when 1-Change destinations appears on the display.
6. Press the Scroll Forward key once to scroll to the 2-Redial option and then press the Select OptiGuide key to select.
7. Press Key 02 (third from the top left, see Figure 6 below) to set the dial string for MWL_ON.
8. Enter the dial string you wish to use with your Optiset 300E for MWL_ON (for example, #*8)
9. Press the Select OptiGuide key again to save.
10. Press the Select OptiGuide key again to exit.
11. Repeat the above procedures for the Key 03 to set the MWL_OFF functionality, using a different dial string.

4.3.2. Using the PBX Integration Board

The PBX Integration board performs functions available to a Optiset E telephone set (see Figure 5 and Figure 6). An Optiset E telephone set uses an LED displays to show key status (next to the keys) and user prompts and messages on the display to provide various options. The PBX Integration board can:

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

Figure 5. Siemens Optiset E Telephone with the Hicom 150E

Figure 6. Siemens Optiset E Telephone with the Hicom 300E

4.3.3. Programmable Feature Keys

As illustrated in Figure 5 and Figure 6 , there are 12 Programmable Feature Keys located below the display on the Optiset E telephone. These keys are configured either during PBX installation or by the user (using the telephone set or the PBX Integration board). When using the Optiset E with the Hicom 150E, for example, the Service Menu, Redial, Mute, Speaker, General Call, Send Message, Consultation, and Release keys are assigned during PBX configuration and cannot be user programmed. There is an LED Indicator associated with each key. The LED Indicators are rectangular and can take on one of the six states listed in Table 10.

Table 10. Optiset E 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 (12 bytes) in an application buffer. Bytes 0-11 contain the indicator status for Feature Keys 00-11, respectively (see Table 11 and Table 12).

Table 11. Optiset E Direct Key Dialing Strings for Feature Keys with Hicom 150E

Table 12. Optiset E Direct Key Dialing Strings for Feature Keys with Hicom 300E

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 1 is 0x01, the rectangular 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 Optiset E 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 Optiset E telephone is assigned a dial string sequence (refer to Table 11 and Table 12). By using the dx_dial( ) function and the appropriate dial string, the PBX Integration board can press any Feature Key.

4.3.4. Alphanumeric Display

The alphanumeric display is a two row, 48-character LCD that is used to show the activity of the phone. Some examples are:

• date and time
• feature names
• text messages
• 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. 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 03 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 13 (as seen by the receiver of the call).

Table 13. 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.3.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, 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.

With the Hicom 150E PBX, 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 47 are used for the message waiting prompt and displays Messages received: 1 and View messages? Refer to the PBX Integration board Software Reference for more information about using the d42_display( ) function.

With the Hicom 300E PBX, 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 00 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

With the Hicom 150E, 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 , as shown in Figure 7 below.

NOTE:

Bytes 00-23 represent the top row of the display. Bytes 24-47 represent the bottom row of the display.

byte

data

byte

data

byte

Figure 7. Optiset E Message Waiting Display with Hicom 150E

With the Hicom 300E, 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 0x01 shows that the MWI indicator is on (there are messages waiting).

4.3.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 she 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