1. Manuals
  2. Brands
  3. Dialogic Manuals
  4. Computer Hardware
  5. M7324
  6. User manual

Dialogic M7324 User Manual

Pbx integration board
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
®
Dialogic
PBX Integration
Board User's Guide
Copyright © 1999-2008 Dialogic Corporation
05-1277-010

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the M7324 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Dialogic M7324

Summary of Contents for Dialogic M7324

  • Page 1 ® Dialogic PBX Integration Board User’s Guide Copyright © 1999-2008 Dialogic Corporation 05-1277-010...

  • Page 2: Copyright And Legal Notice

    Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with Dialogic.

  • Page 3: Table Of Contents

    3.3.2. Functional Description ... 32 3.3.3. Configurations... 34 3.3.4. Software Support... 34 4. PBX Systems... 37 4.1. Avaya Definity PBXs... 37 4.1.1. Avaya Switch Programming Requirements ... 37 ® 4.1.2. Using the Dialogic PBX Integration Board... 39 4.1.3. Programmable Feature Keys ... 41...
  • Page 4 4.1.8. Transferring a Call... 50 4.2. Siemens ROLM PBX... 52 4.2.1. Siemens ROLM Programming Requirements ... 52 ® 4.2.2. Using the Dialogic PBX Integration Board... 54 4.2.3. Programmable Feature Keys ... 55 4.2.4. Alphanumeric Display... 59 4.2.5. Setting the Message Waiting Indicator... 62 4.2.6.
  • Page 5 ® 4.6.2. Using the Dialogic PBX Integration Board... 140 4.6.3. Programmable Feature Keys ... 142 4.6.4. Alphanumeric Display... 144 4.6.5. Setting the Message Waiting Indicator... 147 4.6.6. Transferring a Call... 148 4.7. NEC NEAX 2000/2400 PBXs and Electra Elite KTS ... 150 4.7.1.
  • Page 6 ® Dialogic PBX Integration Board User’s Guide...

  • Page 7: List Of Tables

    Table 25. M7324 LCD Indicator States ... 122 Table 26. M7324 Direct Key Dialing Strings for Memory Keys... 122 Table 27. M7324 Direct Key Dialing Strings for Display Keys ... 126 Table 28. Called/Calling Number ID Data for the Nortel Norstar ... 128 Table 29.
  • Page 8 ® Dialogic PBX Integration Board User’s Guide Table 34. DTerm III Series LCD Indicator States ... 153 Table 35. DTerm III Series LCD Indicator States (Upper Nibble) ... 154 Table 36. DTerm Series III Direct Key Dialing Strings for Feature Keys... 155 Table 37.
  • Page 9 Figure 11. Mitel Superset 420 Display Keys ... 94 Figure 12. Nortel M7324 Telephone... 121 Figure 13. M7324 Display Keys ... 125 Figure 14. M7324 Message Waiting Display ... 131 Figure 15. Nortel M2616 Telephone... 141 Figure 16. NEC DTerm Series III Telephone ... 152...
  • Page 10 ® Dialogic PBX Integration Board User’s Guide...

  • Page 11: How To Use This Manual

    This manual includes information relevant to those choosing to use a Private ® Branch Exchange (PBX) or Key Telephone System (KTS) with a Dialogic Integration Board. A PBX is a privately owned, mini version of a telephone company’s central office (CO) switch. Grouped with PBXs are KTSs, which are generally smaller versions of a PBX that provide direct access to CO telephone lines.

  • Page 12: Pbx Models Covered In This Manual

    ROLM CBX 9005, 9006 and 9715 Hicom 150, North America and 300, North America Telephone Emulations 7434 (4-wire) 8434 (2-wire) Superset 420 (DNIC) Superset 430 (DNIC) Superset 430 (DNIC) DTerm Series III M7324 M7324 M2616 ROLMphone 400 (RP400) Optiset E...

  • Page 13: Documentation Conventions

    1.4. Documentation Conventions The following documentation conventions are used throughout this manual: • When terms are first introduced, they are shown in italic text. • Data structure field names and function parameter names are shown in boldface, as in maxsec. •...

  • Page 14: Dialogic Voice Hardware Covered By This Manual

    PBXs. It provides the basic voice and call processing ® capabilities of Dialogic D/4x voice hardware, and adds hardware and firmware that can ease integration with supported PBXs. Refer to the Dialogic Programming Guide for more information on voice and call processing. ® The Dialogic PBX integration hardware models covered by this manual include ®...

  • Page 15: When To Use This Manual

    For example, D/xxx refers to all models of the Dialogic voice hardware, and D/8x refers to all 8-channel models of the Dialogic hardware. 1.6. When to Use This Manual ® This Dialogic PBX Integration Board User’s Guide contains information for those choosing to configure and use specific PBX hardware with Dialogic Integration Boards.
  • Page 16 ® Dialogic PBX Integration Board User’s Guide...

  • Page 17: Introduction To Pbxs And Ktss

    2. Introduction to PBXs and KTSs A PBX, or private branch exchange, is a telephone system that is usually installed in a business. It provides service among many extensions within the business as well as outside lines. Typically, PBXs are used when a large number of extensions are needed.
  • Page 18 ® Dialogic PBX Integration Board User’s Guide may be sent outside the PBX if outside networks also use digital circuits; however, they are usually converted back to analog voice signals. PBXs use control information to instruct their station sets to perform specific functions such as setting the message waiting indicator and call transfer.

  • Page 19: Supervised Call Transfer

    PBX and that can take advantage of call control elements. Below is a list of PBX features and functions currently supported by Dialogic PBX Integration Boards. Note, however, that KTSs and hybrid systems may support only some of these features.

  • Page 20: Blind Call Transfer

    ® In a supervised transfer, an incoming call answered by a channel on a Dialogic PBX Integration Board will only be transferred after the PBX Integration Board establishes a connection with another station (the call is not released to the PBX).

  • Page 21: Caller Id

    An application can perform blind transfers without special integration tools. ® However, if using a Dialogic PBX Integration Board and the Dialogic API to access the called number ID from the PBX, the application can differentiate between: • a new call coming in that needs to be processed: “Hello and thank you for calling Dialogic Corporation.”...

  • Page 22: Called Number Id

    ® Through use of a Dialogic PBX Integration Board and the Dialogic API, an application can read the called number ID (the trunk line) and route the call depending on which extension receives the call. If the call is received on trunk line 01 it will be routed to the extension for Program A.

  • Page 23: Positive Disconnect Supervision

    In both cases, a disconnect message, not a loop current drop, is sent to the called extension. Standard analog voice boards do not interpret disconnect messages because these messages are usually digital. Dialogic can, however, detect disconnect messages and send a disconnect event to an application where it can be used by standard voice programming mechanisms for handling call termination.

  • Page 24: In-Band Signaling

    ID from within the switch, ANI digits from the CO, hook state, time and length of call, name assigned to the extension, and message ® waiting notification. With a Dialogic PBX Integration Board, this information can be passed “unprocessed” to the application. This means that the same data that is sent to the display is captured by the PBX Integration Board.

  • Page 25: Pressing" Keys

    (e.g., transfer, hold, speaker phone, speed dial, or connect to ® trunk lines). Since a Dialogic PBX Integration Board can emulate a station set, applications can “press” these keys. If the station set can be used to program Feature Keys, an application can also control the assignment of programmable keys.
  • Page 26 ® Dialogic PBX Integration Board User’s Guide...

  • Page 27: Pbx Integration Overview

    When a PBX integration system is initialized, firmware is downloaded from the host PC to the firmware RAM and DSP memory on the Dialogic Integration Board. This downloadable firmware gives the board its intelligence and enables feature enhancement and upgrades.
  • Page 28 • generate tones - DTMF, MF, or an application defined signal or dual tone The PBX Integration Board functions as a Dialogic specialized PBX circuitry replacing the analog front end. The PBX Integration Board performs features available on a Dialogic well as emulates phones connected to a PBX.

  • Page 29: Pbx Integration Features Supported

    ® Dialogic PBX Integration Boards incorporate both circuitry and firmware to integrate applications with specific PBXs. The Dialogic the PBX Integration Board, enables programmers to more easily develop a single application capable of supporting multiple manufacturers’ PBXs. The Unified API also enables applications to access the important digital information sent between a PBX and its station sets.
  • Page 30 ASCII text. By capturing and processing this data, an application can “see” what is on the display. This can help determine the state of the Dialogic Board. Also, if ANI and DNIS digits are available through the PBX, the CO caller ID can be obtained.

  • Page 31: Dialogic Pbx Integration Board Description

    If used with one of the supported PBXs, the PBX Integration Board can provide a flexible platform for developing integrated computer telephony applications. Developers can integrate current Dialogic Integration Board with few software modifications and create efficient applications for the PBX by offering value-added features.

  • Page 32: Functional Description

    Feature Keys and LCD displays for accessing and employing advanced features of the compatible PBXs. Each of the four or eight line interfaces on Dialogic receive voice and control data from the connected PBX. The voice data is compressed by a DSP using one of the available encoding methods and then sent to the host PC to be stored.

  • Page 33: Figure 1. Dialogic

    A system-wide, TDM signal sharing bus, called CT Bus, is also provided for the exchange of signal streams with other resource boards, signal transport boards, or other interfaces. In addition to having all the standard features of a Dialogic ® Dialogic...

  • Page 34: Configurations

    ® Dialogic PBX Integration Board User’s Guide computer to SRAM and DSP memory when the Dialogic ® is started. Dialogic Springware firmware offers several features, including speed control, volume control, global tone detection, and positive voice detection. Global tone detection allows applications to detect special intercept tones, fax tones, modem tones, and non-standard PBX or user-defined tones, such as those used in international networks.
  • Page 35 3. PBX Integration Overview additional tools and examples that allow developers who choose to do so to create complex multi-channel voice applications.

  • Page 37: Pbx Systems

    4.1. Avaya Definity PBXs The Avaya Definity product family includes the Definity 75 (4-wire) and the Definity G3 (2-wire) PBXs. The Dialogic used with either of these switches. The PBXs use digital signaling to control their station sets and digitized voice.

  • Page 38: Table 1. Avaya Definity Configuration Example

    ® Dialogic PBX Integration Board User’s Guide Table 1 lists the structure used if configuring an Avaya Definity PBX. For details about programming an Avaya PBX, refer to the appropriate Avaya manual. The following are examples of the switch settings: Table 1.

  • Page 39: Using The Dialogic Pbx Integration Board

    Caller ID Requirement The extension number must be included in the name field of the extension. This requires PBX programming. ® 4.1.2. Using the Dialogic PBX Integration Board ® The Dialogic PBX Integration Board can perform functions available to Avaya 7434 (4-wire) and 8434 (2-wire) telephone sets (see Figure 3).

  • Page 40: Figure 2. Avaya 7434 Telephone

    ® Dialogic PBX Integration Board User’s Guide Conf Drop Message Figure 2. Avaya 7434 Telephone on/off Transfer Hold Select Feature Buttons Indicators...

  • Page 41: Programmable Feature Keys

    Keys found on the Avaya 7434 and 8434 telephones. These keys are configured either during installation or by the user (using the telephone set or ® the Dialogic PBX Integration Board). There are two LED indicators associated with each Feature Button. The PBX Integration Board can also emulate four Avaya Functions Keys: Transfer Conference, Drop, and Hold.

  • Page 42: Table 2. Avaya 7434 And 8434 Led Indicator States

    Reading LED Indicators ® The Dialogic 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.
  • Page 43 Byte Key Description Feature Button 03 Feature Button 04 Feature Button 05 Feature Button 06 Feature Button 07 Feature Button 08 Feature Button 09 Feature Button 10 Feature Button 11 Feature Button 12 Feature Button 13 Feature Button 14 Feature Button 15 Feature Button 16 Feature Button 17 Feature Button 18...
  • Page 44 Example An application uses the d42_indicators( ) function to retrieve the current data for the LED indicators on a given channel on a Dialogic 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.

  • Page 45: Avaya Function Keys

    The Dialogic PBX Integration Board can “press” any of the Avaya 7434 or 8434’s Feature Keys using the dx_dial( ) function. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys. Each Feature Button on the 7434 and 8434 telephones is...

  • Page 46: Display Keys

    The Dialogic PBX Integration Board can respond to a prompt and “press” the appropriate Display Key using the dx_dial( ) function. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys. Each Display Key on the Avaya 8434 telephone is...
  • Page 47 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 Called/Calling Number ID (within the PBX) ® If receiving a call on a Dialogic PBX Integration Board from another extension, the PBX sends calling number ID data (by default, the extension...

  • Page 48: Table 6. Called/Calling Number Id Data For The Avaya Definity

    ) 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 Dialogic Reference for more information about using d42_gtcallid( ) function.

  • Page 49: Setting The Message Waiting Indicator

    Example An application uses the d42_gtcallid( ) function to retrieve the calling number ID for a call received on a specified channel on a Dialogic Board. The calling number ID data and corresponding ASCII values are shown below. text bb 2 2 4 _ 2 2 1...

  • Page 50: Transferring A Call

    By using the dx_dial( ) function and the appropriate dial string, the PBX Integration Board can transfer a call to any extension connected to the ® switch. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys.
  • Page 51 4. PBX Systems Completing the Transfer To complete a call (supervised or blind), press the transfer key again with dx_dial(&), where & acts as a key press of the transfer key. The application must handle the on-hook state after completing the transfer. Aborting the Transfer A transferred call can be aborted at any time (prior to completing the transfer) by pressing the appropriate appearance key where the original call resides.

  • Page 52: Siemens Rolm Pbx

    PBX Integration Board with a Siemens ROLM PBX. Pay attention to set these features exactly (and assigned to the right keys) so that the PBX Integration Board and the Dialogic • All PBX Integration Board ports on a ROLM system must be programmed as ROLMphone 400 telephones.
  • Page 53 • XFER (transfer) must be programmed on Feature Key 38. • MWI (Message Waiting Indication) mechanisms are different with ROLM CBX 9006 (or ROLM integration on the Hicom 300) and ROLM CBX 9005 PBX. For ROLM CBX 9006 PBX or ROLM integration on the Hicom 300 For the ROLM CBX 9006 PBX or ROLM integration on Hicom 300, the following programming requirements apply: •...

  • Page 54: Using The Dialogic Pbx Integration Board

    If the port is disconnected and connected again, the application does not receive any other carrier loss and gain events. ® 4.2.2. Using the Dialogic PBX Integration Board ® The Dialogic PBX Integration Board performs functions available to a...

  • Page 55: Programmable Feature Keys

    4, there are 40 Feature Keys located below the display on the ROLMphone 400 telephone. These keys are configured either during PBX installation or by the user (using the telephone set or the Dialogic Integration Board). The CLEAR, SPEAKER, MUTE, XFR, and LINE keys are assigned during PBX configuration and cannot be user programmed.

  • Page 56: Table 7. Rolmphone 400 Led Indicator States

    Reading LED Indicators ® The Dialogic 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 LED indicator data (37 bytes) in an application buffer.

  • Page 57: Table 8. Rolmphone 400 Direct Key Dialing Strings For Feature Keys

    Table 8. ROLMphone 400 Direct Key Dialing Strings for Feature Byte Key Description Feature Key 09 - LINE Feature Key 08 Feature Key 07 Feature Key 06 - CLEAR (flash) Feature Key 05 Feature Key 04 Feature Key 03 Feature Key 02 Feature Key 01 - MAILBOX Feature Key 15 Feature Key 14...
  • Page 58 Example An application uses the d42_indicators( ) function to retrieve the current data for the LED indicators on a given channel on a Dialogic Board. The data placed in the application buffer is shown below. If the least significant byte of the data for byte 00 is 0x01 (0x61 AND 0x0f = 0x01 in the figure below), the circular indicator for Feature Key 09 is on.

  • Page 59: Alphanumeric Display

    The Dialogic PBX Integration Board can “press” any of the ROLMphone 400 Feature Keys using the dx_dial( ) function. Refer to the Dialogic Integration Software Reference for more information about dialing programmable keys. Each Feature Key on the ROLMphone 400 telephone is...
  • Page 60 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 Dialogic PBX Integration Software Reference for more information about using the d42_display( ) function.

  • Page 61: Table 9. Called/Calling Number Id Data For The Rolm

    Example An application uses the d42_gtcallid( ) function to retrieve the calling number ID for a call received on a specified channel on a Dialogic Board. The calling number ID data and corresponding ASCII values are shown below.

  • Page 62: Setting The Message Waiting Indicator

    The Dialogic 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 Dialogic Reference for more information about dialing programmable keys. NOTE:...

  • Page 63: Transferring A Call

    By using the dx_dial( ) function and the appropriate dial string, the PBX Integration Board can transfer a call to an extension connected to the ® switch. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys.
  • Page 64 ® Dialogic PBX Integration Board User’s Guide Aborting the Transfer A transferred call can be aborted at any time (prior to completing the transfer) by pressing the appropriate appearance key where the original call resides. The application can perform this only in a supervised transfer mode. For example, if the original call resided on the first appearance (Feature Key 09), dialing dx_dial(<ESC>KA) will bring the original caller back to an active...

  • Page 65: Siemens Hicom Pbx

    The Siemens Hicom is a full-featured PBX 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 Dialogic Board has either four or eight channels that can be connected directly to a station module in a Siemens Hicom.
  • Page 66 Dialogic PBX Integration Board User’s Guide without scrolling the display. This technique is not followed by the Dialogic PBX Integration Board. The PBX Integration Board requires the following special programming for MWI operation. This is to be done by the PBX administrator in the PBX (that is, it cannot be done from a phone).

  • Page 67: Using The Dialogic Pbx Integration Board

    10. Press the Select OptiGuide key again to exit. 11. Repeat the above procedure for the Key 03 to set the MWL_OFF functionality, using a different dial string. ® 4.3.2. Using the Dialogic PBX Integration Board ® The Dialogic PBX Integration Board performs functions available to an...

  • Page 68: Figure 5. Siemens Optiset E Telephone With The Hicom 150

    ® Dialogic PBX Integration Board User’s Guide 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 •...

  • Page 69: Programmable Feature Keys

    Keys located below the display on the Optiset E telephone. These keys can be configured either during PBX installation or by the user (using the telephone ® set or the Dialogic PBX Integration Board). There is an LED indicator 4. PBX Systems...

  • Page 70: Table 10. Optiset E Led Indicator States

    Reading LED Indicators ® The Dialogic 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.

  • Page 71: Table 12. Optiset E Direct Key Dialing Strings For Feature Keys With Hicom

    Example An application uses the d42_indicators( ) function to retrieve the current data for the LED indicators on a given channel on a Dialogic Board. The data placed in the application buffer is shown below. If the data 4. PBX Systems Dial String <ESC>KI...

  • Page 72: Alphanumeric Display

    The Dialogic PBX Integration Board can “press” any of the Optiset E Feature Keys using the dx_dial( ) function. Refer to the Dialogic Integration Software Reference for more information about dialing programmable keys. Each Feature Key on the Optiset E telephone is assigned...
  • Page 73 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 Dialogic PBX Integration Software Reference for more information about using the d42_display( ) function.

  • Page 74: Table 13. Called/Calling Number Id Data For The Hicom

    ) 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 Dialogic Reference for more information about using d42_gtcallid( ) function.

  • Page 75: Setting The Message Waiting Indicator

    The Dialogic 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 Dialogic Reference for more information about dialing programmable keys. NOTE:...
  • Page 76 MWI OFF operation, the application must set the MWI ON and MWI OFF feature access codes using the d42_setparm( ) function. Otherwise, MWI operation can not be done by the Dialogic ® PBX Integration Board can PBX Integration Software Reference for ®...
  • Page 77 PBX Integration Software Reference for more information on the d42_setparm( ) function and the D4BD_MSGACCESSON and D4BD_MSGACCESSOFF parameters. With the Hicom 300 PBX, the Dialogic 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;...

  • Page 78: Figure 7. Optiset E Message Waiting Display With Hicom 150

    Figure 7. Optiset E Message Waiting Display with Hicom 150 With the Hicom 300, an application uses the d42_indicators( ) function to retrieve the LED indicators data for a specified channel on the Dialogic Integration Board to determine if a message is waiting. The LED indicators data is shown below.

  • Page 79: Transferring A Call

    By using the dx_dial( ) function and the appropriate dial string, the PBX Integration Board can transfer a call to any extension connected to the ® switch. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programming keys.
  • Page 80 ® Dialogic PBX Integration Board User’s Guide Aborting a Transfer A transferred call can be aborted at any time (prior to completing the transfer) by pressing the OptiGuide key. The application can perform this only in a supervised transfer mode. Abort the transfer using dx_dial(<ESC>KM), which presses the OptiGuide key.

  • Page 81: Mitel Superswitch Pbxs

    Mitel PBXs use digital signaling to control its station sets and digitized voice. Digital Network Interface Circuit (DNIC) Line Cards provide an interface between the station sets and the switch. The Dialogic has four or eight channels that can be connected to a Mitel DNIC Line Card.
  • Page 82 PBX Integration Board with a Mitel Superswitch. Pay attention to set these features exactly (and assigned to the right keys) so that the PBX Integration Board and the Dialogic The PBX uses Class of Service (COS) to determine which features are available to an extension.
  • Page 83 Mitel SX-50 PBX Programming Requirements for using MWI: If you are using a Mitel SX-50 and wish to use the set Message Waiting Indicators (MWI) feature, the Dialogic Auxiliary Attendant capabilities, and a line key must be set to act as the Attendant Console MWI.
  • Page 84 Personal Key 10 should store the MWI OFF feature access code and Personal Key 11 should store the MWI ON feature access code (see 1. Connect the extension (that will be connected to the Dialogic Integration Board) to a Mitel Superset 430 phone. Repeat the steps for all extensions that would be connected to the board.
  • Page 85 For SX-2000 PBXs and a SuperSet 430 phone: a) Press the desired personal key (10 or 11). b) Press the Change key soft-key. c) Press the Speed Call soft-key. d) Enter the MWI Feature Access code (for key 10 – MWI OFF, for 11- MWI ON).

  • Page 86: Using The Dialogic Pbx Integration Board

    ® Dialogic PBX Integration Board User’s Guide ® 4.4.2. Using the Dialogic PBX Integration Board ® The Dialogic PBX Integration Board emulates functions available to the following phones: • Superset 420 telephone. This emulation can be used with an SX-50 PBX.

  • Page 87: Figure 8. Mitel Superset 420 Telephone

    Personal Keys Message Superkey Trans/Conf Speaker Microphone Volume Redial Tone Contrast Volume Cancel Tone Contrast Figure 8. Mitel Superset 420 Telephone 4. PBX Systems Line Indicators Main Display Display Keys Function Keys...

  • Page 88: Programmable Personal Keys For Mitel Superset Emulation

    Keys that are not configured can be defined by the user (using the telephone ® set or the Dialogic PBX Integration Board) as speed dial or Feature Keys. There is an LCD Line Indicator associated with each Personal Key. The LCD...

  • Page 89: Table 15. Mitel Superset 420/430 Lcd Line Indicator States

    Unknown Reading LCD Line Indicators ® The Dialogic PBX Integration Board can determine the state of its Line Indicators by using the d42_indicators( ) function to retrieve the LCD Indicators data. This function places the Line Indicator data (12 bytes) in an application buffer.

  • Page 90: Table 17. Mitel Superset 430 Lcd Line Indicators

    ® Dialogic PBX Integration Board User’s Guide Byte Key Description Personal Key 10 Personal Key 11 Table 17. Mitel Superset 430 LCD Line Indicators (with SX-200 and SX-2000) and Dial Strings Byte Key Description Personal Key 00 Personal Key 01...

  • Page 91: Figure 10. Mitel Superset 420/430 Lcd Line Indicator

    Example An application uses the d42_indicators( ) function to retrieve the current data for the LCD Line Indicators for a given channel on a Dialogic Integration Board. The data placed in the application buffer is shown below. If the data for byte 07 (ANDed with 0x0f) is 0x02, the indicator corresponding to the Feature Key 07 is indicating ringing (see ®...

  • Page 92: Function Keys

    (refer to By using the dx_dial( ) function and the appropriate dial string, the PBX Integration Board can dial any of its function keys. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys.

  • Page 93: Display (Soft) Keys

    Reading Display Key Prompts: ® The Dialogic 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.

  • Page 94: Call Forwarding

    Display Key 00 Display Key 01 Display Key 02 ® Refer to the Dialogic PBX Integration 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 application buffer is shown below.
  • Page 95 ® The Dialogic PBX Integration Board can respond to a prompt and “press” the appropriate Display Key using the dx_dial( ) function. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys. As shown in Superset 420/430 telephones is assigned a dial string sequence.

  • Page 96: Alphanumeric Display

    ® Dialogic PBX Integration Board User’s Guide Table 20. Mitel Superset 420 Direct Key Dialing Strings for Display Dial String Key Description <ESC>Ka Left Softkey <ESC>Kb Middle Softkey <ESC>Kc Right Softkey Table 21. Mitel Superset 430 Direct Key Dialing Strings for Display...
  • Page 97 ) with a buffer size of 160 for Mitel Superset 430 phones • d42_display( ) for Mitel Superset 420 phones ® Refer to the Dialogic PBX integration Software Reference for more information about using the d42_display( ) and d42_displayex( ) functions. 4. PBX Systems...
  • Page 98 Example An application uses the dx_dial( ) function to press the “SuperKey” key and “Display Key 1” for “Yes” on a specified channel on the Dialogic Integration Board to display the call forwarding extension. The d42_display( ) function can then be used to retrieve the display data and verify that a call forwarding extension has not been programmed.

  • Page 99: Table 22. Called/Calling Number Id Data For The Mitel Superset

    Refer to the Dialogic Reference for more information about using d42_gtcallid( ) function. The contents of the called/calling number ID are shown in by the receiver of the call). Table 22. Called/Calling Number ID Data for the Mitel Superset...
  • Page 100 ) function so that your application will maintain functionality across different manufacturers’ switches. ® The Dialogic PBX Integration Board attempts to get the caller ID information from one of the valid Mitel CPID displays that could be used to extract the caller ID information.

  • Page 101: Setting The Message Waiting Indicator

    The Dialogic 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 Dialogic Reference for more information about dialing programmable keys. NOTE:...

  • Page 102: Transferring A Call

    By using the dx_dial( ) function and the appropriate dial string, the PBX Integration Board can transfer a call to any extension connected to the ® switch. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys.
  • Page 103 Completing the Transfer To complete a call (supervised or blind), one of the following methods can be applicable: • Press the Softkey labeled Release Me. If Superset 430 telephones are used with an SX-200 PBX, this can be done using dx_dial(<ESC>Kb), which is equivalent to pressing the top middle soft key.

  • Page 104: Nortel Norstar And Nortel Bcm

    PBXs use plug-in station modules to connect to station sets, and trunk modules to connect to trunk lines. The Business Communications Manager (BCM) product family includes the BCM50, BCM200, BCM400, and BCM1000. The Dialogic Board can be used with any of these PBXs. ®...

  • Page 105: Nortel Norstar Programming Requirements

    Nortel Norstar (with DR5 or later revision installed). The shaded areas indicate the actual menu items to change if using the KSU with a Dialogic For details about programming a Norstar KSU, refer to the appropriate Norstar manual.
  • Page 106 ® Dialogic PBX Integration Board User’s Guide Menu Option/Default Value Line type: Public Prime set: 21 *Extension number assignment is system dependent. Aux. ringer: Y Auto privacy: Y 2. Line Access a) Show set: Enter extension b) Line assignment (no changes required)
  • Page 107 Menu Option/Default Value 4. Direct-Dial (no changes required) 5. Capabilities a) Dialing filters (no changes required) b) Rem access pkgs (no changes required) c) Set abilities Show set: Enter extension (1) Set filter:02 (2) Line/set filters (no changes required) (3) Set lock:None (4) Full handsfree: N (5) Auto handsfree: N (6) HF answerback: Y...
  • Page 108 ® Dialogic PBX Integration Board User’s Guide Menu Option/Default Value e) COS passwords (no changes required) 6. Service Modes a) Control sets Show line: Enter line # (1) Line001: (2) Line002: Through (3) Line008: (4) Name1:Night (a) Setting:Manual (b) Trunk answer:Y...
  • Page 109 Dialogic (DCM). On Linux systems, this is selected in the configuration file /usr/dialogic/cfg/dialogic.cfg.) This firmware boots the board ports into voice mail mode. Therefore, it can be beneficial for the programming of any MICS system to be carefully reviewed to verify that no more than 16 ports are connected in voice mail mode.
  • Page 110 Redirect Ring: Y ATS Settings: Default (option not available on all switches) Name: Set to fit needs User Preferences: Model: M7324 (set automatically) Button Programming: B1 – B12: Blank B13 – B20, B22 – B24: Default B21: Transfer (Feature 70)
  • Page 111 Options not listed in this section can be set as needed for the NOTES: 1. subscribers. 2. If the d42_getcallidex( ) function is being implemented, then the first port of the Dialogic the prime set for a line in order to differentiate between an 4. PBX Systems ®...
  • Page 112 Programming the Dialogic PBX Integration port as prime set is shown below. 3. Assign ring only to the first port of the Dialogic D/42JCT-U Board for lines that are to be answered by the board, that is, direct into voice mail.
  • Page 113 Step 1: Clear Memory NOTE: If the DID card is already attached and functional, please proceed to the next section. If a memory clear is needed, proceed as follows: 1. Reset the power; unplug and plug in the power cord. 2.
  • Page 114 ® Dialogic PBX Integration Board User’s Guide Step 3: Program the Target Line In this example, the target line number is Line 145. The following programming will route the incoming DID call to extension 222, which is a D/82 port, if the digits 222 are received in the target line 145.

  • Page 115: Nortel Bcm Programming Requirements

    There are several specific programming requirements that apply if using a ® Dialogic PBX Integration Board with the Nortel BCM. Some are optional features, whereas others are mandatory. The mandatory programming requirements allow the PBX Integration Board to work correctly.

  • Page 116: Table 24. Bcm Configuration Requirements

    Template Name: Edit name, as required Set Model: Multiple CallPilot Voice Messaging Add a CallPilot subscriber mailbox?: No Line Access Prime Line: I/C Intercom Keys: 2 Line Pool Access Pool: <Add> as required New Value General M7324 Edit as required...
  • Page 117 Aux ringer: N Allow redirect: N Redirect Ring: Y 4. PBX Systems New Value ® The Dialogic PBX Integration Board supports up to two lines, and they should be configured as “Appearance&Ring.” When configured as “Appearance&Ring,” up to two lines are supported per phone.
  • Page 118 Dialing Options: <Standard dial> Language: <English> Contrast: <4> Ring Type: <1> Perform Button Programming: <No> Button Programming – M7324 Button 01: <Blank> Button 02: <Blank> Button 03: <Blank> Button 04: <Blank> New Value Configure as required. In the wizard, the typical use of these fields is to enter the Voicemail DN.
  • Page 119 Menu Option/Default Value Button 05: <Blank> Button 06: <Blank> Button 07: <Blank> Button 08: <Blank> Button 09: <Blank> Button 10: <Blank> Button 11: <Blank> Button 12: <Blank> Button 13: <Feature> <Call Forward (F4)> Button 14: <Feature> <Speed Dial (F0)> Button 15: <Feature> <Last Number Redial (F5)>...

  • Page 120: Using The Dialogic Pbx Integration Board

    PBX Integration Board performs functions available to a M7324 telephone set (see Figure 12). An M7324 telephone set uses three LCD displays. Two are 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).

  • Page 121: Programmable Memory Keys

    12, the M7324 has 24 Programmable Memory Keys located to the right of the display. These keys can be configured either during PBX installation or by the user (using the telephone set or the Dialogic Integration Board). The Line, Intercom, Answer, and Handsfree keys are assigned during PBX configuration and cannot be user programmed.

  • Page 122: Table 25. M7324 Lcd Indicator States

    ) 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 26).
  • Page 123 An application uses the d42_indicators( ) function to retrieve the current data for the LCD indicators on a given channel on a Dialogic 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.

  • Page 124: Display Keys

    PBX Integration Board can “press” any of the M7324 Memory Keys using the dx_dial( ) function. Refer to the Dialogic 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 26).

  • Page 125: Figure 13. M7324 Display Keys

    PBX Integration Board can respond to a prompt and “press” the appropriate Display Key using the dx_dial( ) function. Refer to the Dialogic PBX Integration 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 the appropriate dial string, the PBX Integration Board can press any of its Display Keys.

  • Page 126: Alphanumeric Display

    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 Dialogic PBX Integration Software Reference for more information about using the d42_display( ) function.
  • Page 127 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Called/Calling Number ID (within the PBX) ® If receiving a call on a Dialogic 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.

  • Page 128: Table 28. Called/Calling Number Id Data For The Nortel Norstar

    ® Dialogic PBX Integration Board User’s Guide The contents of the called/calling number ID (as seen by the receiver of the call) are shown in Table 28 (for the Nortel Norstar) and in Nortel BCM). Table 28. Called/Calling Number ID Data for the Nortel Norstar...

  • Page 129: Setting The Message Waiting Indicator

    Example An application uses the d42_gtcallid( ) function to retrieve the calling number ID for a call received on a specified channel on a Dialogic Board. The calling number ID data and corresponding ASCII values are shown below. text bb 2 2 1 _ 2 2 4...
  • Page 130 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 Dialogic for more information about using the d42_display( ) function.

  • Page 131: Transferring A Call

    32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Message for you Figure 14. M7324 Message Waiting Display 4.5.8. Transferring a Call ® The Dialogic PBX Integration Board can transfer calls using the dx_dial( ) function.
  • Page 132 ® Dialogic PBX Integration Board User’s Guide answer. Because of this capability, supervised transfer is a comparatively preferred call transfer method. There are three different ways to perform a transfer operation, namely: • & transfer • Display key press transfer •...
  • Page 133 4. PBX Systems right Display key (which is Display Key 02) and <ext> is the PBX extension to which you are transferring the call. Completing the Transfer To complete a call (supervised or blind) the application must go on-hook. Another way to complete the transfer is with dx_dial(<ESC>KR), where <ESC>KR acts as a key press (which is Display Key 02, the far-right display key).

  • Page 134: Called Id On Forwarded Calls

    ® Dialogic PBX Integration Board User’s Guide <ESC>KR acts as a key press (which is Display Key 02, the far-right display key). Aborting the Transfer A transferred call can be aborted at any time (prior to completing the transfer) by pressing the appropriate appearance key where the original call resides.
  • Page 135 This check is only made whenever d42_gtcallid( ) and d42_gtcallidex( ) are called. The directory maps the phone name to the associated extension. If all the phone names are extensions, then this feature can be disabled. The directory must be sorted based on the phone name, in descending order; phone names are case sensitive.
  • Page 136 ® Dialogic PBX Integration Board User’s Guide On the first tier, the administrator can select either a D82/D42 port or the “skip” option: • D82/D42 port: This can be any inactive port that is available for use on the host. Extbuilder will use this port to call the specified extension, when it is building the directory.
  • Page 137 • Delete: Remove an entry from the directory. This command does not require a D82/D42 port to be specified. • Update: Update an existing entry in the directory. Similar to the Add command, the Name field is only required if the “skip” option was selected.
  • Page 138 ® Dialogic PBX Integration Board User’s Guide The parameter list for batch mode is: • /s=<ext1>-<ext2> : this field is required. Specify the beginning extension (ext1) and the ending extension (ext2). • /b=<port to use> : this field is required. Extbuilder will use this port to call out.

  • Page 139: Nortel Meridian 1

    PBX Integration Board with a Meridian 1. Pay attention to set these features exactly (and assigned to the right keys) so that the PBX Integration ® Board and the Dialogic Unified API can function correctly. Table 30 lists the menu structure used when configuring a Nortel Meridian 1.

  • Page 140: Using The Dialogic Pbx Integration Board

    KEY 10 KEY 11 KEY 12 KEY 13 KEY 14 KEY 15 ® 4.6.2. Using the Dialogic PBX Integration Board ® The Dialogic PBX Integration Board performs functions available to a M2616 telephone set (see Figure 15). 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).

  • Page 141: Figure 15. Nortel M2616 Telephone

    ® The Dialogic 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 Hold Figure 15. Nortel M2616 Telephone 4.

  • Page 142: Programmable Feature Keys

    Reading LCD Indicators ® The Dialogic 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.

  • Page 143: Table 32. 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 Dialogic 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 ®...

  • Page 144: Alphanumeric Display

    The Dialogic PBX Integration Board can “press” any of the M2616 Feature Keys using the dx_dial( ) function. Refer to the Dialogic Software Reference for more information about dialing programmable keys. Each Feature Key on the M2616 telephone is assigned a dial string sequence...
  • Page 145 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 Dialogic PBX Integration Software Reference for more information about using the d42_display( ) function.

  • Page 146: Table 33. Called/Calling Number Id Data For The Meridian 1

    ) 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 Dialogic Reference for more information about using d42_gtcallid( ) function.

  • Page 147: Setting The Message Waiting Indicator

    Example An application uses the d42_gtcallid( ) function to retrieve the calling number ID for a call received on a specified channel on a Dialogic Board. The calling number ID data and corresponding ASCII values are shown below. text bb 2 2 1 _ 2 2 4...

  • Page 148: Transferring A Call

    By using the dx_dial( ) function and the appropriate dial string, the PBX Integration Board can transfer a call to any extension connected to the ® switch. Refer to the Dialogic PBX Integration Software Reference for more information about dialing programmable keys.
  • Page 149 4. PBX Systems Completing the Transfer To complete a call (supervised or blind), press the transfer key again with the dx_dial(&), where & acts as a key press of the transfer key. The application must handle the on-hook state after completing the transfer. Aborting the Transfer A transferred call can be aborted at any time (prior to completing the transfer) by pressing the appropriate appearance key where the original call resides.

  • Page 150: Nec Neax 2000/2400 Pbxs And Electra Elite Kts

    PBX Integration Board User’s Guide 4.7. NEC NEAX 2000/2400 PBXs and Electra Elite KTS ® The Dialogic PBX Integration Board has either four or eight channels that can be connected directly to a station module in either a NEC PBX or a NEC KTS.

  • Page 151: Using The Dialogic Pbx Integration Board

    Allow the ports connected to the Dialogic to use the transfer key. Message Waiting Indicator (MWI): The default access dial strings for the Dialogic to **9 (on) and ##9 (off). If the PBX has not been set to use these dial strings, you must: •...

  • Page 152: Figure 16. Nec Dterm Series Iii Telephone

    ® Dialogic PBX Integration Board User’s Guide MIC/ICM Indicators PQRS OPER HOLD Function Keys Figure 16. NEC DTerm Series III Telephone As indicated in Figure 16, there are: • 16 Flexible Line keys located on the top portion of the phone below the LCD display •...

  • Page 153: Flexible Line Keys

    4.7.3. Flexible Line Keys There are 16 Flexible Line keys located on the top of the DTerm Series III telephone as shown in Figure 16. These keys are configured by the system programmer to perform many different functions. When programming the telephone, the Flexible Line keys are used to select the programming mode or sub-mode.

  • Page 154: Table 35. Dterm Iii Series Lcd Indicator States (Upper Nibble)

    Steady on (green) Reading LCD Indicators on Flexible Line Keys ® The Dialogic 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.

  • Page 155: Table 36. Dterm Series Iii 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 Dialogic Board. The data placed in the application buffer is shown below. If the data for byte 1 is 0x0F, the indicator for Flexible Line key 2 is green and on. Refer ®...
  • Page 156 The Dialogic PBX Integration Board can “press” any of its Flexible Line keys using the dx_dial( ) function. Refer to the Dialogic Software Reference for more information about dialing keys. Each Flexible Line key on the DTerm Series III telephone is assigned a dial string sequence...

  • Page 157: Function Keys

    Bytes 18-23 (excluding byte 20, which is not used) contain the LED indicator status for Feature keys (see ® to the Dialogic PBX Integration Software Reference for more information about using the d42_indicators( ) function.

  • Page 158: Mic And Icm Led Indicators

    Example An application uses the d42_indicators( ) function to retrieve the current data for the LCD indicators on a given channel on a Dialogic Board. The data placed in the application buffer is shown below. If the data for byte 23 is 0x07, the indicator for SPKR is red and on. Refer to the ®...

  • Page 159: Alphanumeric Display

    LCD indicators on a given channel on a Dialogic Board. The data placed in the application buffer is shown below. If the data for byte 24 is 0x07, the indicator for ICM is on. Refer to the Dialogic Integration Software Reference for more information about using the d42_indicators( ) function.
  • Page 160 32 33 34 35 36 37 38 39 40 41 42 42 44 45 46 47 Called/Calling Number ID (within the PBX) ® If receiving a call on a Dialogic 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.

  • Page 161: Table 38. Called/Calling Number Id Data For The Nec (Dterm Iii)

    Example An application uses the d42_gtcallid( ) function to retrieve the calling number ID for a call received on a specified channel on a Dialogic Board. The calling number ID data and corresponding ASCII values are shown below.

  • Page 162: Setting The Message Waiting Indicator

    The Dialogic 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 Dialogic Reference for more information about dialing programmable keys. NOTE:...
  • Page 163 Reading the State of the PBX Integration Board MWI Indicator ® The Dialogic PBX Integration Board can determine the state of its own Message Waiting Indicator using the d42_indicators( ) function to read the...

  • Page 164: Transferring A Call

    Dialogic PBX Integration Board User’s Guide LED indicators data. Byte 17 contains the Message Waiting indicator status (0x00 is off; 0x70 is on). Refer to the Dialogic 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 a Dialogic to determine if a message is waiting.

  • Page 165: Primary Appearance Location Note

    answer. Because of this capability, supervised transfer is a comparatively preferred call transfer method. Initiating the Transfer Once in a connected call, you can initiate a transfer with dx_dial(&,<ext>), where & acts as a key press of the transfer key and <ext> is the PBX extension to which you are transferring the call.
  • Page 166 ® Dialogic PBX Integration Board User’s Guide using the d42_setparm( ) function with the D4CH_LC_LAMP parameter. ® Refer to the Dialogic PBX Integration Software Reference for more information on the d42_setparm( ) function and the D4CH_LC_LAMP parameter.

  • Page 167: Appendix A - Technical Specifications

    Telephone Interface Support Avaya 7434 (4-wire), Avaya 8434 (2-wire), Siemens ROLMphone 400, Siemens Optiset E, Mitel Superset 420, Mitel Superset 430, Nortel M7324, Nortel M2616 Connectors 36-position mini D cable plug Power Requirements +5 VDC 3.3 A at 5 volts per board Operating temperature 0ºC to +50ºC...
  • Page 168 ® Dialogic PBX Integration Board User’s Guide Safety & EMI Certifications United States FCC part 68 does not apply Canada CSO3 does not apply ® Dialogic PBX Integration Board Firmware Specifications* Audio Signal Transmit -12.5 dBm0 (weighted average)** Receive range -42 to +2.5 dBm...
  • Page 169 Signal/noise ratio 10 dB (referenced to lowest amplitude tone) Talk off Detects 0 digits while monitoring Mitel speech tape #CM7291. Detects less than 10 digits while monitoring Bellcore TR-TSY-000763 standard speech tapes (LSSGR requirements specify detecting no more than 470 total digits). MF Tone Detection: MF digits 0 to 9, KP, ST, ST1, ST2, ST3...
  • Page 170 ® Dialogic PBX Integration Board User’s Guide...

  • Page 171: Glossary

    Glossary Analog Signal A continuously variable signal. Voice signals on telephone lines are usually analog (i.e., transmitted electronically in a form analogous to the spoken form). A representation of an analog signal is a sine wave. The “operator” of a phone system console. Usually directs Attendant incoming calls to the proper person or department.
  • Page 172 ® Dialogic PBX Integration Board User’s Guide A term used to describe a telephone system that has Hybrid System attributes of both Key Systems and PBXs. Usually means that incoming lines (trunks) appear on the phone set, and outbound calls require the use of an access code (typically a “9”).
  • Page 173 Time Division Multiplex - A technique used for transmitting separate data, voice, or video messages simultaneously over one phone line by interleaving elements of each message in fast time sequences. Another way of saying plus and minus, or positive and Tip and Ring ground, in electrical circuits.
  • Page 174 ® Dialogic PBX Integration Board User’s Guide...

  • Page 175: Index

    Index Adaptive Differential Pulse Code Modulation, 28 ASR. See Automatic Speech Recognition automated attendant, 17, 25, 32, 171 Automatic Speech Recognition, 32 Avaya Definity Alphanumeric Display, 46 Display Keys, 46 LED Indicators, 42 Message Waiting Indicator, 49 pressing Display Keys, 46 pressing Function Keys, 45 pressing Programmable Feature Keys, 45...
  • Page 176 ® Dialogic PBX Integration Board User’s Guide Nortel Norstar KSU, 124, 125, 126, 129, 131 Siemens Hicom, 72, 73, 75 Siemens ROLM, 59, 60, 62, 63, 64 dialing sequences Avaya Definity 7434, 8434, 42 Nortel Meridian 1, 143 Nortel Norstar, 122...
  • Page 177 Message Waiting Indicator, 129 pressing Display Keys, 125 pressing Programmable Memory Keys, 124 Programmable Memory Keys, 121 transfer calls, 120, 131, 134 PBX, 17 PCM. See Adaptive Differential Pulse Code Modulation, See Pulse Code Modulation primary appearance location NEC, 165 Private Branch Exchange.

Table of Contents

Save PDF