1.8.  Analog Display Services Interface (ADSI)

Analog Display Services Interface (ADSI) is a Bellcore standard that defines a protocol used to transmit data to display-based, ADSI-compliant telephones.

For many years, Dialogic provided one-way ADSI support through the dx_play( ) and dx_playf( ) functions. This ADSI support enabled developers to use Dialogic boards to make ADSI servers that work with ADSI phones and to support ADSI features such as visual Voice Mail. This is referred to as the "older" implementation of one-way ADSI (for details on this older method, see the dx_play( ) function in the Voice Software Reference: Programmer's Guide).

The newer implementation of ADSI offers several enhancements and is supported through the dx_RxIottData( ), dx_TxIottData( ), and dx_TxRxIottData( ) functions. This implementation is referred to simply as "ADSI Support" or "Two-Way ADSI" and includes the following features:

• Transmit to On-Hook ADSI phones: Allows messages to be sent to an ADSI phone when the phone is either On-Hook or Off-Hook.
• Two-Way Frequency Shift Keying (FSK): Allows users to send and receive character or binary data at 1200 bits/second between the server and compatible devices, such as certain ADSI phones with keyboards. The two-way FSK feature supports applications such as off-line Email editing and sending FSK Caller ID data to a customer premise equipment (CPE) device through an MSI/SC board.

This newer Dialogic ADSI support provides for both two-way and one-way ADSI transmission and is the recommended method for implementing either one-way or two-way ADSI in an application program. The older one-way ADSI support can be used but is not the recommended method. See Section 9.5.3.  Modifying Older One-Way ADSI Applications for information on converting from the older to the newer method for using ADSI.

Click here to contact Dialogic Customer Engineering