Table Of Contents../index.html

About This Information

Release Overview

System Requirements

New Features

Supported Hardware

Separately Orderable Products

Installation and Configuration

Release Documentation

Master Feature List

Copyright Notice

System Release 5.1 for Linux

Release Guide

Copyright © 2002 Intel Corporation

05-1672-001


Top Of PageAbout This Information

This section describes the purpose and intended audience for this documentation. Here are the sections contained:


Top Of PagePurpose

This release guide provides information about the system release that has been shipped along with this documentation.


Top Of PageIntended Audience

This release guide is intended for the following type of customers:


Top Of PageHow to Use This Information

This information is designed so that information can be found quickly. Major sections include:


Top Of PageRelated Information

See the following for additional information:


Top Of PageRelease Overview


Top Of PageWhat's New In This Release?

This release guide addresses the highlights of System Release (SR) Version 5.1 for Linux. SR 5.1 introduces Conferencing, Continuous Speech Processing (CSP), Transaction Record, Internet Coders, and TrueSpeech* support on our higher-density DM3TM products, enabling developers to deploy industry leading media-processing solutions that utilize the enhanced functionality, density, scalability and availability of our board-level products.

SR 5.1 is designed to enable customers focused on the service providers and high-end enterprise with the tools they need to create new and enhanced applications and solutions for their current and next generation network products. Current SR 5.0 developers can utilize the advanced functionality and new features contained in SR 5.1 in their current development environments with little down time.

SR 5.1 includes all of the hardware and software included in System Release 5.0 plus additional new hardware and software features.

Application developers can develop applications using R4 APIs such as Voice, Fax, and GlobalCall for both SpringWare and DM3 boards.


Top Of PageNew Products and Features List

This release introduces new products and features in the following areas:


Top Of PageSystem Requirements

The basic requirements to install and run this system release are described in the following categories:

NOTE:

Please refer to the RedHat website (http://www.redhat.com) for additional information about system requirements.


Top Of PageHardware Requirements

Hardware requirements are broken down into the following groups:

The recommended hardware configuration for this release is:

The minimum hardware configuration for this release is:

To develop computer telephony solutions with DM3 products requires:


Top Of PageSystem Software Requirements

NOTE:
For instructions on how to apply this Errata, refer to http://www.redhat.com/support/resources/howto/kernel-upgrade/kernel-upgrade.html

NOTE:
The ucd-snmp project was recently renamed net-snmp. The rpm names are likely to change in the future.

Top Of PageNew Features

The new features introduced in this release are broken out into the following categories:


Top Of PageAdministrative Software Features

The following new Administration features are available in this release:

The following new administrative commands are available:

NOTE:
For further information about these commands, see the System Release 5.1 for Linux Software Installation Guide.

This release supports controlled Like for Like Replacement of any DM3 CompactPCI (cPCI) board. This feature allows you to physically remove a DM3 cPCI board from the system and replace it with an identical device model without shutting down the Dialogic System Service. In order to utilize this capability, the board must be pre-configured and restarted after replacement.

NOTE:
For more information about this feature, see the System Release 5.1 for Linux Software Installation Guide.

Selective Startup Mode provides the ability to continue initializing a group (or set) of DM3 boards regardless of a single board failure. This means that download and initialization of the system will continue to occur even when 1 or more DM3 boards fail to initialize properly. Some Examples:

In those cases where the DM3 board is acting as the clock master in a mixed system, if no DM3 board is able to provide clock (i.e., all fail to download), then the SpringWare boards will fail to initialize as well. In all other cases, the SpringWare boards will not be affected by the failure of a DM3 board to initialize.

In those cases where the SpringWare board is acting as the clock master in a mixed system, if no SpringWare board is able to provide clock (i.e., all fail to download), then the DM3 boards will fail to initialize as well. In all other cases, the DM3 will not be affected by the failure of a SpringWare board to initialize.

However, if in the mixed system one of the SpringWare boards is Master Clock capable, and all of the DM3 boards have failed to start, the system will continue to initialize the other SpringWare boards.

This capability is enabled only for those systems with at least two DM3 boards.

BoardWatch now offers MIB (Management Information Base) modules for DS1 and ISDN:

NOTE:
Please refer to the BoardWatch User's Guide for Linux for more information regarding this feature.

SRL Device Mapper functions are contained in the SRL Device Mapper Library Interface (SDM API), a subset of the Dialogic Standard Runtime Library for Linux (SRL). They return information about the structure of the system, such as a list of all the virtual boards on a physical board. The SDM API works for any component that exposes R4 devices.

The SRL Device Mapper functions return information about the structure of the system based upon the following conventions:

The SRL Device Mapper functions and the information they return are listed below.

NOTES:
1: The SDM API provides a set of atomic transforms, such as a list of all virtual boards on a physical board. For more complicated transforms, such as information about all the sub devices on a physical board, combine multiple SRL Device Mapper functions.
2: For more detailed information about the SRL Device Mapper Library Interface, see the Voice Software Reference: Standard Runtime Library for Linux.

Top Of PageHardware Product Features

The following new hardware features are being introduced in this release:

NOTE:
For descriptions of the boards contained in this release, please refer to the Supported Hardware section.

The following fax boards are supported in this release:

DM3 Fax provides the following features:

NOTE:
See the DM3 Diagnostic Utilities Reference Guide for more information.
NOTE:
See the R4 on DM3 section under Software Features for a list of new features supported.

The DM3 VFN Series consists of integrated T-1 and E-1 boards providing a full span of feature-rich voice and fax processing in a single PCI slot. The availability of 24/30 universal voice and fax channels on each DM3 VFN Series board ensures that applications will be able to process any incoming or outgoing voice and/or fax transaction at any time, provided there is an open channel. Four DM3 VFN products may be combined in a single chassis, enabling applications to support up to 120 channels of high-performance voice and fax.

The following new integrated voice, fax and network boards are supported in this release:

The new features associated with DM3 VFN are:

NOTE:
See the R4 on DM3 section under Development Software Features for a list of features supported with this API. You can also refer to the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux.
NOTE:
See the DM3 Protocol Support Table in the Installation and Configuration section for a list of supported protocols and pcd files.
NOTE:
BoardWatch 5.1.1 does not support single board start/stop for SpringWare boards but it does for DM3 boards.

The DM3 IPLink platform allows a "voice over IP" call to be connected via the DM3 platform to the SCbus. Using IPLink boards equipped with a PSTN network front end, you can build a single board digital IP - PSTN gateway application. Adding additional SCbus boards for analog connectivity or station interface and technologies such as conferencing, voice recognition, or text-to-speech makes a variety of applications possible.

The following IPLink boards with a 100 BaseT Ethernet connectors are introduced in this release:

The following features are new to this Linux system release:

NOTE:
See the DM3 Protocol Support Table in the Installation and Configuration section for a list of supported protocols.

The following new features are available for the first time in this release and are described in detail below:

GlobalCall Support for IP and PSTN

GlobalCall API now supports writing voice over IP applications when using the Embedded H.323 stack (NetTSP). GlobalCall support for split call control applications is not available in this release.

NOTE:
See the GlobalCall IP Technology User's Guide for a complete description of how to use the GlobalCall library for voice over IP applications.

IPLink declares only maximum capabilities per coder in the Fast Start Element (FSE) when in Fast Start mode. If IPLink receives an FSE in the SETUP message and the capabilities do not match, it switches to the Slow Start procedure and opens an H.245 session, and retries capability negotiation with all the possible coder attributes. Fast Start may be disabled by the H323_PrmForceSlowStart parameter.

The H323_PrmForceSlowStart parameter disables the H.323 Fast Start and forces the gateway to use the call establishment procedure as in H.323 Rev. 1. This parameter must be manually added to the FCD file.

NOTE:
See the DM3 IPLink User's Guide for a description of this parameter and the DM3 Configuration File Reference for information about how to modify configuration parameters.

The IP Media Library is an R4 compatible library for controlling media on IP devices (ipvs_*.pcd). Host-based call control applications that use call control stacks other than those supplied with IPLink use this library for application development.

The IP Media Library supports:

NOTE:
See the IP Media API Software Reference for a complete description of the library.

This release allows the application to define the ReleaseCompleteReason, selecting either Q.931 Cause or H.225.0 ReleaseCompleteReason as its disconnect reason mechanism.

A new parameter, prmStandardDisconnectReasonEnabled, has been added to the FCD file to allow the application to select how to implement the disconnect reason mechanism.

NOTE:
See the DM3 IPLink User's Guide for a description of this parameter.

The following IPLink demo is included in this release:

Applications can modify the Type of Service byte in the IP header of the transmitted datagrams to improve the mobility of the UDP/TCP packets.

NOTE:
See the DM3 IPLink User's Guide for a complete description.

The following paragraphs describe new time parameters:

Flexible Routing is now available for all IPLink protocols. PCD files are identified by "evr" (exportable voice resources) in the file name.

NOTE:
See the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux for more information about Flexible Routing.

This release supports the following hardware:

NOTE:
Limitations exist with the DM/V2400 product that application developers need to be aware of. For complete information, refer to the support website: http://support.dialogic.com/releases/unix51/linux51

DM3 MediaSpan products offer the following new features:

NOTE:
See the DM3 Protocol Support Table in the Installation and Configuration section for a list of supported protocols.

For the media features that are supported as part of various Media Load configurations, see the DM3 Media Loads section under Installation and Configuration for more information on supported configurations:

NOTE:
For specific information regarding which MediaSpan boards support which coders and features, please refer to the DM3 Media Load Table and DM3 Protocol Support Table both found in the Installation and Configuration section of this guide.
NOTE:
For information about using the R4 DCB API for conferencing, see the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux.
NOTE:
See the R4 on DM3 section under the Software Features section for a list of the features supported by R4 on DM3 including a definition of Flexible Routing.

The Dialogic High Density Station Interface (HDSI) is an open-architecture platform for computer telephony that integrates large-scale switching and voice processing resources under a single hardware and software architecture. Dialogic offers the High Density Station Interface solution in both PCI and Compact PCI (cPCI) configurations, which provide the industry's highest density analog station connectivity in a single computer chassis slot.

The HDSI is a Dialogic assembly consisting of either an HDSI-PCI board with H.100 compliant CT Bus connectivity, or an HDSI-cPCI board assembly (including a cPCI Baseboard and a Rear I/O Module) with H.110 compliant CT Bus connectivity, connected to a Station Interface Box (SIB). (The CT Bus provides switching between trunks and stations and also allows expansion for additional Dialogic network and resource boards.) Utilizing just one computer chassis slot, this solution can support up to 120 stations with tone detection and generation, and FSK Caller ID transmission.

The Dialogic Station Interface Box is a single unit that supports 48 stations in the base model configuration. However, the SIB is a modular unit that is designed to accept Dialogic plug-in components to accommodate 72, 96, and 120 stations. The SIB features a "hot swap" capability, which allows you to break and re-establish connections to the HDSI-PCI board (or to the HDSI-cPCI board assembly) without powering down or rebooting the system.

Dialogic supports the following hardware (Dialogic HDSI hardware package including an HDSI board and the SIB) for use with an HDSI system:

Telephones

Although standard analog telephones will work, they may not support caller ID compatibility. The following telephones have been tested and are supported by HDSI in this release:

The HDSI series of products provide the following features and benefits:

This product utilizes the Dialogic R4 on DM3 interface to provide support for the existing Dialogic Modular Station Interface (MSI) R4 API, as well as the Voice (dx_) R4 API (for tone detection and generation).

NOTES:
1: For more detailed information about the Dialogic High Density Station Interface, refer to the High Density Station Interface Series Hardware Installation Guide.
2: For more information about Voice API restrictions, refer to the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux.

The following countries are supported on the HDSI/1200:

NOTE:
See the section on MSI Boards Country Specific Parameter Files for information on configuring these boards to comply with country-specific settings.

The following new SpanPlus resource boards have been added in this release:

The following new features have been added to this board:

This board has the same features as the standard D/82JCT-U board, but offers 4 channels rather than 8.

Contains the following features:

This is a 4-channel analog loop-start product with a CT Bus interface. The D/41JCT-LS now supports CSP (Continuous Speech Processing) and DSP-based Fax.

This is a 4-channel analog loop-start product with a CT Bus interface. This product now supports CSP (Continuous Speech Processing) and enhanced DSP-based Fax.


Top Of PageDevelopment Software Features

The following new software features are being introduced in this release:

Continuous Speech Processing (CSP) is software that supports development of host-based automatic speech recognition (ASR) applications on specific Dialogic boards. It provides many features such as high-performance echo cancellation, voice energy detection, barge-in, voice event signaling, pre-speech buffering, full-duplex operation and more.

The CSP software consists of library functions, device drivers, firmware, and sample demonstration programs.

In this release, CSP is supported on the J-series SpringWare-based products and specific DM3 boards.

NOTE:
To run CSP on DM3 boards, please refer to the DM3 Media Loads section.

The following features are available on SpringWare boards:

The following SpringWare boards support CSP:

NOTE:
Please refer to the Supported Hardware section of this release guide for detailed information regarding these boards.

CSP supports the same features as SpringWare plus the following new features on DM3:

The following DM3 hardware now supports CSP:

NOTE:
Limitations exist with the DM/V2400 product that application developers need to be aware of. For complete information, refer to the support website: http://support.dialogic.com/releases/unix51/linux51
NOTES:
1: Please refer to the Supported Hardware section of this release guide for detailed information regarding these boards.
2: For more information on CSP, see the Continuous Speech Processing documentation set.

The following new features are supported:

NOTE:
DSP-Based Fax (also known as DSP Fax) and CSP are mutually exclusive except on the D/41JCT-LS and VFX/41JCT-LS. Please refer to the SpringWare Support Matrix found in the Hardware Features section of the Master Features for a table showing how this feature, ISDN and CSP work together.
NOTE:
The fax resource manager is firmware functionality that shields the user from having to keep track of which specific channels have fax capability. It provides fax resources/support on any channel, at any time, as long as there are fewer than the maximum number of fax resources currently being used.
NOTE:
14.4 Kbps receive and enhanced error correcting schemes are only available when enhanced DSP-Based Fax is being used. Currently, only the VFX/41JCT-LS has this capability.

The boards that are supported by this product are:

NOTES:
1: Please refer to the Supported Hardware section for detailed information regarding these boards.
2: Please refer to the Master Features section for a table describing channel support for DSP-Based Fax.

The following new features are supported on DM3 in this release:

The following new features are only supported on SpringWare in this release:

NOTE:
This is supported for DM3 IPLink using NetTSC and the embedded RadVision H.323 stack.
NOTE:
This is supported for DM3 IPLink using NetTSC and the embedded RadVision H.323 stack.
NOTE:
This feature is used by ISDN BRI and IP.
NOTES:
1: See the GlobalCall Application Development Guide for more information regarding this demo.
2: See the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux for more information regarding what is supported under SpringWare and what is supported on DM3..

The following SpringWare boards have been tested in this release:

NOTE:
Not all boards in each family are tested. If one board in a family has been tested, the behavior of other boards in the same family is expected to be the same.

GlobalCall supports PSTN interfaces on DM3 boards (including the DI series of boards and IPLink boards). However, GlobalCall does not support the following:

Limited H.100 support for SpringWare products as follows:

All JCT SpringWare boards support H.100 in this release.

The IP Media Library is an R4 compatible library for controlling media on IP devices (ipvs_*.pcd). Host-based call control applications that use call control stacks other than those supplied with IPLink use this library for application development.

The IP Media Library supports:

NOTE:
See the IP Media API Software Reference for a complete description of the library.
NOTE:
See the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux for additional information.

The following new features are supported:

NOTE:
This release of the R4 API on DM3 does not have provisions for administrative services such as Clock Fallback, and other features not currently supported by the R4 APIs.

The "Exportable Voice Resources" and "Shareable Fax Resources" features are referred to as flexible routing. This terminology will be used going forward. The following support features for fixed and flexible routing are available in this release:

EXAMPLES OF ROUTING TERMINOLOGY

NOTE:
The following paragraph refers to chapters found in the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux.

This release provides support for two types of routing configuration: fixed and flexible. Fixed routing, which was the only configuration available in previous system releases containing R4 on DM3, is a restricted routing, whereas flexible routing is compatible with the routing capabilities in the R4 API.
Since the routing configuration affects the routing capability and resource management features that are supported, both routing configurations are documented in the Compatibility Guide. The routing information in the Compatibility Guide is presented under the assumption that flexible routing will be used. However, because fixed routing is an option, information on fixed routing is provided.

R4 on DM3 supports two types of routing configuration:

New support for Call Waiting supplementary service is provided for ISDN BRI according to CCITT Q.953 and ETS 300 058-1 specifications. This support allows a user to be notified of an incoming call (as per basic call procedures) with an indication that no information channel is available. The user then has the choice of accepting, rejecting or ignoring the incoming waiting call. Note that the support for sending a call waiting call is also provided for the Network Switch side of protocols. See the updated ISDN Software Reference for Dialogic R4 API usage (i.e. cc_MakeCall, cc_WaitCall, cc_GetChanId) for more information regarding this capability.

NOTE:
For NTT protocol users, the API cc_SetInfoElem( ) has to be used to override the default Channel ID IE content. This is required to comply with NTT specifications that stipulate the first reply to the SETUP message has to identify the B-channel on which the call is later conducted.

This feature is supported on the following hardware:

The following BRI features are supported:

Each BRI is configurable as a TE (station) or as an NT (PSTN)

The drivers for this release are SMP safe, and this release will function on an SMP machine. This release provides SMP support with all Dialogic activity having affinity to one processor


Top Of PageDiagnostic and Utilities Features

The following new or enhanced diagnostic utilities are being introduced in this release:

This utility exercises the Antares platform at the Application/System level. This is source code that is used as sample/example/demo code. This release adds the following:

The dm3post diagnostic tool, sometimes referred to as "POST On-Demand," can perform diagnostics on a stopped board at any time to detect and isolate possible hardware faults. This can enable you to locate and diagnose faulty boards.

This feature is an interactive diagnostic program that uses diagnostic firmware to test the functionality of Dialogic hardware. UDD relies on configuration files used by the Dialogic generic downloader: any board supported by UDD that is listed in the configuration file will appear on the initial UDD screen. For each supported board, UDD presents a list of tests that can be selected, deselected, and executed a specified number of times. The tests available are specific to each type of board. The following boards are supported by UDD in this release::


Top Of PageSupported Hardware

The following categories of hardware products are supported in this release:


Top Of PageMedia with Interface Products

The supported Media with Interface Products are described in the following categories:


Top Of PageMedia Products

The supported media products are described in the following categories:

NOTE:
Limitations exist with the DM/V2400 product that application developers need to be aware of. For complete information, refer to the support website: http://support.dialogic.com/releases/unix51/linux51

Top Of PageNetwork Interface Products

The supported network interface products are described in the following categories:

All of the boards listed in this table support ringing.


Top Of PageSeparately Orderable Products

This section describes separately orderable products that are not part of the system release but are required to perform some of the functions supported by the system release:


Top Of PageGlobalCall Protocols Version 2.00 Package

The GlobalCall Protocols Version 2.00 package includes the following protocols for use on the PSTN interfaces of SpringWare boards:

PDK protocols provide the ability to use many of the new GlobalCall API features included in this system release and provide for future protocol feature compatibility with DM3 protocols to be released in the future.

The GlobalCall Protocols Version 2.00 Package contains:

NOTE:
The GlobalCall Protocols Version 2.00 package can be downloaded from the Dialogic Telecom Support Resources Support web site at: http://support.dialogic.com/releases/protocols/gcprotocols20

Top Of PageInstallation and Configuration

The Installation and Configuration section provides information about the following topics:


Top Of PageInstalling Hardware

Install the boards in the chassis according to the instructions on the Quick Install card included with each board.


Top Of PageConfiguring Hardware

Configure the boards you will be using in your system according to the instructions in System Release 5.1 for Linux Software Installation Guide.


Top Of PageInstalling or Uninstalling Software

Follow the instructions in the System Release 5.1 for Linux Software Installation Guide.


Top Of PageConfiguring Software

This section contains specific information for configuring various types of software applications:

For information about DM3 diagnostic and debugging tools, see the DM3 Diagnostics Utilities Reference.

A good way to get started and see how IPLink applications work is to run the following demos based on the GlobalCall R4 API:

These can be found at:: .../dialogic/demos/ipt/gc_demos.

NOTE:
See the DM3 IPLink User's Guide for Linux for more information about this product. Also the IPT Media Gateway Demo User's Guide for information about the demo.

With DM3 Fax products, you develop applications using the Dialogic R4 API. Therefore, you should first refer to the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux.

The term Dialogic R4 API (Dialogic System Software Release 4 Application Programming Interface) is used to identify the well-established and time-proven Dialogic interface used for creating computer telephony applications tailored to Dialogic hardware products. The Compatibility Guide describes the R4 API support for DM3 products. This guide provides information about porting to DM3 products using the R4 APIs as well as migrating existing applications for SpringWare products to DM3 products.

Once you have read the Compatibility Guide, you should refer to the Fax Software Reference.

With DM3 MediaSpan products, you develop applications using the Dialogic R4 API. Therefore, you should first refer to the Compatibility Guide for the Dialogic R4 API on DM3 Products for Linux.

Once you have read the Compatibility Guide, you should refer to the Voice Software Reference. This comprehensive guide and function reference for the R4 API includes the Features Guide for Linux, Programmer's Guide for Linux, and Standard Runtime Library for Linux.

For information about call control software features provided by the GlobalCall API, see the following documents:

For information about the SCbus and SCbus routing, see the SCbus Routing Guide.

The media loads provided for this release are mainly supported on the DM3 MediaSpan product line. However, there is some limited Media Load support for the DM3 IPLink products as well. They are as follows:

Media Load

Boards Supported

1 - Basic Voice*

DM/IP481-2T1-PCI-100BT

DM/IP601-2E1-PCI-100BT

2 - Enhanced Voice

DM/IP241-1T1-PCI-100BT

DM/IP301-1E1-PCI-100BT

DM/IP481-2T1-cPCI-100BT

DM/IP601-2E1-cPCI-100BT

DM/IP601-cPCI-100BT

* Only PCM play/record should be used with this Media Load on these boards.

There are new PCD/FCD files for different media loads - a media load consists of Product Configuration Description (PCD) and Feature Configuration Description (FCD) files and associated firmware loads, which are downloaded to each DM3 board. The PCD/FCD files are customized by feature set as well as by protocol. The feature sets are available in different media loads as shown in the following table. In most cases, the PCD/FCD file names will indicate the associated media load and protocol, for example, ml2_qsa_4ess.pcd. A complete list of all PCD/FCD file names for all boards is given in the DM3 Protocol Support table. Here are descriptions of the media loads that are being supported in this release.

Media Load

Description

1

Basic Voice

  • Provides play, record
  • Provides digit generation (for DTMF and MF digits)
  • Provides digit detection (for DTMF only)
  • All half duplex voice operations
  • Supported Coders:
    • 64Kbps & 48Kbps G.711 PCM VOX and WAV
    • 24Kbps & 32Kbps OKI ADPCM VOX and WAV
    • 88/176Kbps Linear PCM VOX and WAV
  • Speed Control on 8KHz coders
  • Volume Control
  • GTG/GTD
  • dx_dial() can be used for call analysis (post connect only)
  • Transaction Record
  • All call control features when using a board with a network interface

1b

2-Way FSK

  • Basic Voice (Media Load 1) plus ADSI/2-way FSK

2

Enhanced Voice

  • Basic Voice (Media Load 1) plus:
  • CSP
  • Enhanced Coders:
    • G.726 at 32K
    • GSM (TIPHON and MS)
  • Silence Compressed Record:
    • G.711
    • ADPCM
    • G.726

6

Ultra Voice

  • Enhanced Voice (Media Load 2) and TrueSpeech coder

9b

Conferencing

Resource

  • Conferencing only resource load. It is very much like a traditional DCB with added conferencing capabilities like Echo Cancellation.
  • Conferencing with Echo Cancellation and basic DTMF and basic tariff tone support.
  • Conferencing (up to 60 conferences per DCB DSP device)
  • No Voice channels
  • Adds 16 ms Echo Cancellation

10

Voice and Conferencing

  • Enhanced Voice (Media Load 2) plus Conference Resource:
  • Conferencing and Voice devices are independent. This Media Load instantiates both enhanced voice devices as well as DCB DSP conferencing resources.

The following table shows product configurations based on these media loads:

 

Media Load

Board

Basic Voice

(1)

Two Way FSK

(1b)

Enhanced Voice

(2)

Ultra Voice

(6)

Voice/ Conf

(10)

Conf Resource

(9b)

QuadSpan PCI/cPCI

120 E-1

96 T-1

         

QuadSpan A PCI

 

120 E-1

96 T-1

120 E-1

96 T-1

120 E-1

96 T-1

 

120 Conf

QuadSpan A cPCI

 

120 E-1

96 T-1

120 E-1

96 T-1

   

120 Conf

DualSpan A PCI

   

60 E-1

48 T-1

60 E-1

48 T-1

60/60 E-1

48/60 T-1

 

DualSpan A cPCI

   

60 E-1

48 T-1

 

60/60 E-1

48/60 T-1

 

DM/V2400A PCI

240

     

60/60

120 Conf

DM/V2400A cPCI

240

     

120/60

120 Conf

IPLink DualSpan PCI

60 E-1

48 T-1

         

IPLink SingleSpan PCI

   

30 E-1

24 T-1

     

IPLink DualSpan cPCI

   

60 E-1

48 T-1

     

For information about using and configuring the DM3 GlobalCall resource protocols, see the DM3 Configuration File Reference.

Below are listed the protocols and PCD files supported for each of the following products:

The table below shows the protocols on specific DM3 Fax boards and the corresponding PCD file that is downloaded to the board.

fn = used for fixed routing

fn3 = used for flexible routing

Model

Protocol

PCD File

DM/F240-PCI (and cPCI)

 

fax24

DM/F300-PCI (and cPCI)

 

fax30

DM/F240-1T1-PCI

Robbed bit

fn_t1

fn3_t1

 

4ESS

fn_isdn_4ess

fn3_isdn_4ess

 

5ESS

fn_isdn_5ess

fn3_isdn_5ess

 

DMS

fn_isdn_dms

fn3_isdn_dms

 

NTT

fn_isdn_ntt

fn3_isdn_ntt

 

NI2

fn_isdn_ni2

fn3_isdn_ni2

 

QSIG (T1)

fn_isdn_qsigt1

fn3_isdn_qsigt1

DM/F300-1E1-PCI

R2MF

fn_r2mf

fn3_r2mf

 

NET5

fn_isdn_net5

fn3_isdn_net5

 

QSIG (E1)

fn_isdn_qsige1

fn3_isdn_qsige1

The table below shows the protocols on specific DM3 VFN boards and the corresponding PCD file that is downloaded to the board.

vfn = used for fixed routing

vfn3 = used for flexible routing

Model

Protocol

PCD File

DM/VF240-T1-PCI

Robbed bit

vfn_t1
vfn3_t1

 

4ESS

vfn_isdn_4ess

vfn3_isdn_4ess

 

5ESS

vfn_isdn_5ess

vfn3_isdn_5ess

 

DMS

vfn_isdn_dms

vfn3_isdn_dms

 

NTT

vfn_isdn_ntt

vfn3_isdn_ntt

 

NI2

vfn_isdn_ni2

vfn3_isdn_ni2

 

QSIG (T1)

vfn_isdn_qsigt1

vfn3_isdn_qsigt1

DM/VF300-E1-PCI

R2MF

vfn_r2mf

vfn3_r2mf

 

NET5

vfn_isdn_net5

vfn3_isdn_net5

 

QSIG (E1)

vfn_isdn_qsige1

vfn3_isdn_qsige1

DM3 IPLink PCD File Naming Convention

xxxx _yyy_#zzzzK_tttv_www

xxxx:

ipt = embedded call control, both signaling and media on board

ipvs = split call control, only media control on board

yyy:

evr = Exportable Voice Resources (Flexible Routing)

#zzzz:

# - number of PSTN connections on product

zzzz - PSTN protocol supported by PSTN interface

K = configuration where PSTN is disabled and an off-board PSTN is used through the CT Bus

r = resource only

ttt:

DSP type on product:

311

v:

Default of nothing is PCI, otherwise c = cPCI

www:

Example:

ipt_evr_cas_311 indicates:

The table below shows the protocols on specific IPLink boards and the corresponding PCD file that is downloaded to the board.

Model

Protocol

PCD File

DM/IP601-cPCI-100BT

Resource only

ipt_evr_r_311c
ipvs_evr_r_311c

DM/IP241-1T1-PCI-100BT

4ESS

ipt_evr_isdn_4ess_311
ipvs_evr_isdn_4ess_311

 

5ESS

ipt_evr_isdn_5ess_311
ipvs_evr_isdn_5ess_311

 

DMS

ipt_evr_isdn_dms_311
ipvs_evr_isdn_dms_311

 

NI2

ipt_evr_isdn_ni2_311
ipvs_evr_isdn_ni2_311

 

NTT

ipt_evr_isdn_ntt_311
ipvs_evr_isdn_ntt_311

 

QSIG (T1)

ipt_evr_isdn_qsigt1_311
ipvs_evr_isdn_qsigt1_311

 

CAS

ipt_evr_cas_311
ipvs_evr_cas_311

 

none

iptk_t1_311
ipvsk_t1_311

DM/IP301-1E1-PCI-100BT

NET5

ipt_evr_isdn_net5_311
ipvs_evr_isdn_net5_311

 

QSIG (E1)

ipt_evr_isdn_qsige1_311
ipvs_evr_isdn_qsige1_311

 

R2MF

ipt_evr_r2mf_311

ipvs_evr_r2mf_311

 

none

iptk_e1_311
ipvsk_e1_311

DM/IP481-2T1-PCI-100BT

4ESS

ipt_evr_2isdn_4ess_311
ipvs_evr_2isdn_4ess_311

 

5ESS

ipt_evr_2isdn_5ess_311
ipvs_evr_2isdn_5ess_311

 

DMS

ipt_evr_2isdn_dms_311
ipvs_evr_2isdn_dms_311

 

NI2

ipt_evr_2isdn_ni2_311
ipvs_evr_2isdn_ni2_311

 

NTT

ipt_evr_2isdn_ntt_311
ipvs_evr_2isdn_ntt_311

 

QSIG (T1)

ipt_evr_2isdn_qsigt1_311
ipvs_evr_2isdn_qsigt1_311

 

CAS

ipt_evr_2cas_311
ipvs_evr_2cas_311

DM/IP481-2T1-cPCI-100BT

4ESS

ipt_evr_2isdn_4ess_311c
ipvs_evr_2isdn_4ess_311c

 

5ESS

ipt_evr_2isdn_5ess_311c
ipvs_evr_2isdn_5ess_311c

 

DMS

ipt_evr_2isdn_dms_311c
ipvs_evr_2isdn_dms_311c

 

NI2

ipt_evr_2isdn_ni2_311c
ipvs_evr_2isdn_ni2_311c

 

NTT

ipt_evr_2isdn_ntt_311c
ipvs_evr_2isdn_ntt_311c

 

QSIG (T1)

ipt_evr_2isdn_qsigt1_311c
ipvs_evr_2isdn_qsigt1_311c

 

CAS

ipt_evr_2cas_311c
ipvs_evr_2cas_311c

DM/IP601-2E1-PCI-100BT

NET5

ipt_evr_2isdn_net5_311

ipvs_evr_2isdn_net5_311

 

QSIG (E1)

ipt_evr_2isdn_qsige1_311

ipvs_evr_2isdn_qsige1_311

 

R2MF

ipt_evr_2r2mf_311

ipvs_evr_2r2mf_311

DM/IP601-2E1-cPCI-100BT

NET5

ipt_evr_2isdn_net5_311c
ipvs_evr_2isdn_net5_311c

 

QSIG (E1)

ipt_evr_2isdn_qsige1_311c
ipvs_evr_2isdn_qsige1_311c

 

R2MF

ipt_evr_2r2mf_311c
ipvs_evr_2r2mf_311c

The table below shows the protocols available to specific DualSpan and QuadSpan boards and the corresponding PCD files that should be downloaded to the board.

NOTE:
See the section on DM3 Media Loads for what features are supported by each Media Load. Also, only those beginning with mlx support flexible routing, the others (e.g., qs2) use fixed routing.

QuadSpan Series A Voice Boards

Model

Protocol

PCD File

DM/V960A-4T1-PCI

4ESS

ml2_qsa_4ess

ml6_qsa_4ess

ml1b_qsa_4ess

 

5ESS

ml2_qsa_5ess

ml6_qsa_5ess

ml1b_qsa_5ess

 

DMS

ml2_qsa_dms

ml6_qsa_dms

ml1b_qsa_dms

 

QSIG (T1)

ml2_qsa_qsigt1

ml6_qsa_qsigt1

ml1b_qsa_qsigt1

 

NTT

ml2_qsa_ntt

ml6_qsa_ntt

ml1b_qsa_ntt

 

NI2

ml2_qsa_ni2

ml6_qsa_ni2

ml1b_qsa_ni2

 

CAS

ml2_qsa_t1

ml6_qsa_t1

ml1b_qsa_t1

 

Conference resource load

ml9b_qsa_t1

DM/V1200A-4E1-PCI

R2MF

ml2_qsa_r2mf

ml6_qsa_r2mf

ml1b_qsa_r2mf

 

QSIG (E1)

ml2_qsa_qsige1

ml6_qsa_qsige1

ml1b_qsa_qsige1

 

NET5

ml2_qsa_net5

ml6_qsa_net5

ml1b_qsa_net5

 

Conference resource load

ml9b_qsa_e1

 

Clear Channel

ml2_qsa_ts16

DM/V960A-4T1-cPCI

4ESS

ml2_qs2_4ess

qs2_isdn_4ess

ml1b_qs2_4ess

 

5ESS

ml2_qs2_5ess

qs2_isdn_5ess

ml1b_qs2_5ess

 

DMS

ml2_qs2_dms

qs2_isdn_dms

ml1b_qs2_dms

 

QSIG (T1)

ml2_qs2_qsigt1

qs2_isdn_qsigt1

ml1b_qs2_qsigt1

 

NTT

ml2_qs2_ntt

qs2_isdn_ntt

ml1b_qs2_ntt

 

NI2

ml2_qs2_ni2

qs2_isdn_ni2

ml1b_qs2_ni2

 

CAS

ml2_qs2_t1

qs2_t1

ml1b_qs2_t1

 

Conference resource load

ml9b_qs2_t1

DM/V1200A-4E1-cPCI

R2MF

ml2_qs2_r2mf

qs2_r2mf

ml1b_qs2_r2mf

 

QSIG (E1)

ml2_qs2_qsige1

qs2_isdn_qsige1

ml1b_qs2_qsige1

 

NET5

ml2_qs2_net5

qs2_isdn_net5

ml1b_qs2_net5

 

Conference resource load

ml9b_qs2_e1

 

Clear Channel

ml2_qs2_ts16

DualSpan Series A Voice Boards

Model

Protocol

PCD File

DM/V480A-2T1-PCI

4ESS

ml2_dsa_4ess

ml6_dsa_4ess

ml10_dsa_4ess

 

5ESS

ml2_dsa_5ess

ml6_dsa_5ess

ml10_dsa_5ess

 

DMS

ml2_dsa_dms

ml6_dsa_dms

ml10_dsa_dms

 

QSIG (T1)

ml2_dsa_qsigt1

ml6_dsa_qsigt1

ml10_dsa_qsigt1

 

NTT

ml2_dsa_ntt

ml6_dsa_ntt

ml10_dsa_ntt

 

NI2

ml2_dsa_ni2

ml6_dsa_ni2

ml10_dsa_ni2

 

CAS

ml2_dsa_t1

ml6_dsa_t1

ml10_dsa_t1

DM/V600A-2E1-PCI

R2MF

ml2_dsa_r2mf

ml6_dsa_r2mf

ml10_dsa_r2mf

 

QSIG (E1)

ml2_dsa_qsige1

ml6_dsa_qsige1

ml10_dsa_qsige1

 

NET5

ml2_dsa_net5

ml6_dsa_net5

ml10_dsa_net5

 

Clear Channel

ml2_dsa_ts16

DMV/V480A-2T1-cPCI

4ESS

ml2_ds2_4ess

ml10_ds2_4ess

 

5ESS

ml2_ds2_5ess

ml10_ds2_5ess

 

DMS

ml2_ds2_dms

ml10_ds2_dms

 

QSIG (T1)

ml2_ds2_qsigt1

ml10_ds2_qsigt1

 

NTT

ml2_ds2_ntt

ml10_ds2_ntt

 

NI2

ml2_ds2_ni2

ml10_ds2_ni2

 

CAS

ml2_ds2_t1

ml10_ds2_t1

DM/V600A-2E1-cPCI

R2MF

ml2_ds2_r2mf

ml10_ds2_r2mf

 

QSIG (E1)

ml2_ds2_qsige1

ml10_ds2_qsige1

 

NET5

ml2_ds2_net5

ml10_ds2_net5

 

Clear Channel

ml2_ds2_ts16

QuadSpan Voice Boards

Model

Protocol

PCD File

DM/V480-4T1-PCI

DM/V480-4T1-cPCI

4ESS

4x2_isdn_4ess

ml1_4x2_4ess

 

5ESS

4x2_isdn_5ess

ml1_4x2_5ess

 

DMS

4x2_isdn_dms

ml1_4x2_dms

 

QSIG (T1)

4x2_isdn_qsigt1

ml1_4x2_qsigt1

 

NTT

4x2_isdn_ntt

ml1_4x2_ntt

 

NI2

4x2_isdn_ni2

ml1_4x2_ni2

 

CAS

4x2_t1

ml1_4x2_t1

DM/V600-4E1-PCI

DM/V600-4E1-cPCI

R2MF

4x2_r2mf

ml1_4x2_r2mf

 

QSIG (E1)

4x2_isdn_qsige1

ml1_4x2_qsige1

 

NET5

4x2_isdn_net5

ml1_4x2_net5

DM/V960-4T1-PCI

DM/V960-4T1-cPCI

4ESS

qs_isdn_4ess

ml1_qs_4ess

 

5ESS

qs_isdn_5ess

ml1_qs_5ess

 

DMS

qs_isdn_dms

ml1_qs_dms

 

QSIG (T1)

qs_isdn_qsigt1

ml1_qs_qsigt1

 

NTT

qs_isdn_ntt

ml1_qs_ntt

 

NI2

qs_isdn_ni2

ml1_qs_ni2

 

CAS

qs_t1

ml1_qs_t1

DM/V1200-4E1-PCI

DM/V1200-4E1-cPCI

R2MF

qs_r2mf

ml1_qs_4ess

 

QSIG (E1)

qs_isdn_qsige1

ml1_qs_qsige1

 

NET5

qs_isdn_net5

ml1_qs_net5

 

Clear Channel

ml1_qs_ts16

QuadSpan DTI Boards (with Tone Processing)

Model

Protocol

PCD File

DM/T960-4T1-PCI

DM/T960-4T1-cPCI

4ESS

4xt_isdn_4ess

mn_4xt_4ess

 

5ESS

4xt_isdn_5ess

mn_4xt_5ess

 

DMS

4xt_isdn_dms

mn_4xt_dms

 

QSIG (T1)

4xt_isdn_qsigt1

mn_4xt_qsigt1

 

NTT

4xt_isdn_ntt

mn_4xt_ntt

 

NI2

4xt_isdn_ni2

mn_4xt_ni2

 

CAS

4xt_t1

mn_4xt_t1

DM/T1200-4E1-PCI

DM/T1200-4E1-cPCI

R2MF

4xt_r2mf

mn_4xt_r2mf

 

QSIG (E1)

4xt_isdn_qsige1

mn_4xt_qsige1

 

NET5

4xt_isdn_net5

mn_4xt_net5

QuadSpan DTI Boards (without Tone Processing)

Model

Protocol

PCD File

DM/N960-4T1-PCI

DM/N960-4T1-cPCI

4ESS

4x0_isdn_4ess

 

5ESS

4x0_isdn_5ess

 

DMS

4x0_isdn_dms

 

QSIG (T1)

4x0_isdn_qsigt1

 

NTT

4x0_isdn_ntt

 

NI2

4x0_isdn_ni2

DM/N1200-4E1-PCI

DM/N1200-4E1-cPCI

QSIG (E1)

4x0_isdn_qsige1

 

NET5

4x0_isdn_net5

QuadSpan Resource Only Boards

Model

Protocol

PCD File

DM/V2400A-PCI

N/A

ml1_pcires

ml9b_pcires

ml10_pcires

DM/V2400A-cPCI

N/A

ml1_cpcires

ml9b_cpcires

ml10_cpcires

NOTE:
Limitations exist with the DM/V2400 product that application developers need to be aware of. For complete information, refer to the support website: http://support.dialogic.com/releases/unix51/linux51

Since HDSI does not have a PSTN interface, there are no protocols such as T1 CAS. The table is for the hardware characteristics of telephones from different countries. Refer to the MSI Boards Country Specific Parameter File table below for the country codes.

Model

Protocol

PCD File

DM/V1200-4E1

T1(CAS)

(country)_hdsi

DM/V1200-4E1

T1(CAS)

(country)_hdsi_96_play_rec

In order to enable DSP-based Fax boards that are not pre-enabled, you must download special firmware files. Please look at the following sections found in the Master Features section for the following information:

Dialogic System Software allows you to configure MSI/SC-Global and MSI/PCI-Global boards to comply with country-specific settings for telephone line impedance and gain control.

MSI-Global country-specific parameter files follow an xx_msig.prm naming convention, where xx is the two-letter ISO country code.

NOTE:
Although the ISO Codes below are listed in upper case, please keep in mind that Linux is case sensitive. Therefore, be sure to enter these codes in lower case when specifying a parameter file..

Below are the ISO country codes. Those marked with an "*" are supported in this release:

Country

ISO Code

Afghanistan

AF

Albania

AL

Algeria

DZ

American Samoa

AS

Andorra

AD

Angola

AO

Anguilla

AI

Antarctica

AQ

Antigua and Barbuda

AG

Argentina

AR

Armenia

AM

Aruba

AW

Australia*

AU

Austria*

AT

Azerbaijan

AZ

Bahamas

BS

Bahrain

BH

Bangladesh

BD

Barbados

BB

Belarus

BY

Belgium*

BE

Belize

BZ

Benin

BJ

Bermuda

BM

Bhutan

BT

Bolivia

BO

Bosnia and Herzegovina

BA

Botswana

BW

Bouvet Island

BV

Brazil

BR

British Indian Ocean Territory

IO

Brunei darussalam

BN

Bulgaria

BG

Burkina Faso

BF

Burundi

BI

Cambodia

KH

Cameroon

CM

Canada

CA

Cape Verde

CV

Cayman Islands

KY

Central African Republic

CF

Chad

TD

Chile

CL

China

CN

Christmas Islands

CX

Cocos (Keeling) Islands

CC

Colombia

CO

Comoros

KM

Congo

CG

Cook Islands

CK

Costa Rica

CR

Croatia

HR

Cuba

CU

Cyprus

CY

Czech Republic

CZ

Denmark*

DK

Djibouti

DJ

Dominica

DM

Dominican Republic

DO

East Timor

TP

Ecuador

EC

Egypt

EG

El Salvador

SV

Equatorial Guinea

GQ

Eritrea

ER

Estonia

EE

Ethiopia

ET

Falkland Islands (Malvinas)

FK

Faroe Islands

FO

Fiji

FJ

Finland

FI

France*

FR

France, Metropolitan

FX

French Guiana

GF

French Polynesia

PF

French Southern Territories

TF

Gabon

GA

Gambia

GM

Georgia

GE

Germany*

DE

Ghana

GH

Gibraltar

GI

Greece

GR

Greenland

GL

Grenada

GD

Guadeloupe

GP

Guam

GU

Guatemala

GT

Guinea

GN

Guinea-Bissau

GW

Guyana

GY

Haiti

HT

Heard Island and Mc Donald Islands

HM

Honduras

HN

Hong Kong*

HK

Hungary

HU

Iceland

IS

India

IN

Indonesia

ID

Iran (Islamic republic of)

IR

Iraq

IQ

Ireland*

IE

Israel

IL

Italy*

IT

Ivory Coast

CI

Jamaica

JM

Japan*

JP

Jordan

JO

Kazakhstan

KZ

Kenya

KE

Kiribati

KI

Korea, Democratic people's Republic of

KP

Korea, Republic of

KR

Kuwait

KW

Kyrgyzstan

KG

Lao people's democratic republic

LA

Latvia

LV

Lebanon

LB

Lesotho

LS

Liberia

LR

Libyan Arab Jamahiriya

LY

Liechtenstein

LI

Lithuania

LT

Luxembourg*

LU

Macau

MO

Madagascar

MG

Malawi

MW

Malaysia*

MY

Maldives

MV

Mali

ML

Malta

MT

Marshall islands

MH

Martinique

MQ

Mauritania

MR

Mauritius

MU

Mayotte

YT

Mexico*

MX

Micronesia (Federated States of)

FM

Moldava, Republic of

MD

Monaco

MC

Mongolia

MN

Montserrat

MS

Morocco

MA

Mozambique

MZ

Myanmar

MM

Namibia

NA

Nauru

NR

Nepal

NP

Netherlands*

NL

Netherlands Antilles

AN

New Caledonia

NC

New Zealand*

NZ

Nicaragua

NI

Niger

NE

Nigeria

NG

Niue

NU

Norfolk Islands

NF

Northern Mariana Islands

MP

Norway*

NO

Oman

OM

Pakistan

PK

Palau

PW

Panama

PA

Papua New Guinea

PG

Paraguay

PY

Peru

PE

Philippines

PH

Pitcairn

PN

Poland

PL

Portugal*

PT

Puerto Rico

PR

Qatar

QA

Reunion

RE

Romania

RO

Russia Federation

RU

Rwanda

RW

Saint Helena

SH

Saint Kitts and Nevis

KN

Saint Lucia

LC

Saint Pierre et Miquelon

PM

Saint Vincent and the Grenadines

VC

Samoa

WS

San Marino

SM

Sao Tome and Principe

ST

Saudi Arabia

SA

Senegal

SN

Seychelles

SC

Sierra Leone

SL

Singapore*

SG

Slovakia

SK

Slovenia

SI

Solomon Islands

SB

Somalia

SO

South Africa*

ZA

South Georgia and the South Sandwich Islands

GS

Spain*

ES

Sri Lanka

LK

Sudan

SD

Suriname

SR

Svalbard and Jan Mayen

SJ

Swaziland

SZ

Sweden

SE

Switzerland*

CH

Syria Arab Republic

SY

Taiwan, Province of China

TW

Tajikistan

TJ

Tanzania, United Republic Of

TZ

Thailand

TH

Togo

TG

Tokelau

TK

Tonga

TO

Trinidad and Tobago

TT

Tunisia

TN

Turkey

TR

Turkmenistan

TM

Turks and Caicos Islands

TC

Tuvalu

TV

Uganda

UG

Ukraine

UA

United Arab Emirates

AE

United Kingdom*

GB

United States*

US

United States Minor Outlying Islands

UM

Uruguay

UY

Uzbekistan

UZ

Vanuatu

VU

Vatican City State (Holy See)

VA

Venezuela

VE

Viet nam

VN

Virgin Islands (British)

VG

Virgin Islands (U.S.)

VI

Wallis and Futuna Islands

WF

Western Sahara

EH

Yemen

YE

Yugoslavia

YU

Zaire

ZR

Zambia

ZM

Zimbabwe

ZW

Non-Facility-Associated Signaling (NFAS) uses a single ISDN PRI D channel to provide signaling and control for up to 10 ISDN PRI lines. Normally, on an ISDN PRI line, one D channel is used for signaling and 23 B channels (bearer channels) are used for transferring information. In an NFAS configuration, therefore, one D channel can support the signaling and control for up to 239 B channels. The trunk that provides the signaling is called the primary D channel. The trunks that use all 24 channels as B channels are called NFAS trunks.

See the DM3 Configuration File Reference for detailed configuration information.


Top Of PageRelease Documentation

All the documentation referenced in this Release Guide can be ordered through Dialogic Software Distribution. You can also view or print from the Adobe® PDF files or view the HTML versions supplied with this system release.

System Release 5.1 for Linux provides documentation in the following categories:

NOTES:
1: An asterisk (*) next to a document title indicates that the document has been updated since the last release.
2: We are moving our documentation to a new Intel format. During this transition period, some documents will be in the new format, while others will remain in the old format. For example, in this release, the Continuous Speech Processing (CSP) documents are in the new Intel format. When the transition period is completed in subsequent releases, all documents will be in the new Intel format.

Top Of PageSystem Release Software Documentation

The following system release documentation is provided with this release:


Top Of PageAdministrative Software Documentation

The following administrative software documentation is provided with this release:


Top Of PageDevelopment Software Documentation

The following development software documentation is provided with this release:


Top Of PageDiagnostic and Utilities Software Documentation

The following diagnostics and utilities software is provided in System Release 5.1 for Linux:


Top Of PageMaster Feature List

The features previously enabled for the Linux operating system and still supported in this release, are organized into the following categories:


Top Of PageAdministrative Software Features

Although many of our SpringWare products were pre-enabled (e.g., DSP-based Fax and Continuous Speech Processing), some of the older boards may need to be enabled through our licensing facility. In those cases, please refer to the Dialogic Technical Support website at http://support.dialogic.com for specific information.


Top Of PageHardware Product Features

The previous release of Linux software only supported SpringWare boards. The following tables show how these SpringWare boards support various software features and firmware loads.

NOTE:
The D/480JCT-T1 and D/600JCT-E1 are intended to support an ISDN firmware load on one span and a CSP firmware load on the other span. This gives the user a full span of ISDN interface with a full compliment of CSP.

NOTES:
1: The spcsp.fwl file can only be used with T1 boards; the spe1csp.fwl can only be used with E1 boards.
2: The spfax.fwl is also supported on the DualSpan boards. As with the single span boards, loading this firmware file will yield 4 fax channels per span.

The table below shows the SpringWare products that support major voice features and include onboard network interfaces:

Product

Voice

Call Progress

Tone

Network Interface

D/80SC

Y

Y

Y

-

D/120JCT-LS

Y

Y

Y

Y

D/160SC

Y

Y

Y

-

D/240SC

Y

Y

Y

-

D/320SC

Y

Y

Y

-

D/160SC-LS

Y

Y

Y

Y

D/240SC-T1

Y

Y

Y

Y

D/240PCI-T1

Y

Y

Y

Y

D/240JCT-T1

Y

Y

Y

Y

D/300SC-E1

Y

Y

Y

Y

D/300PCI-E1

Y

Y

Y

Y

D/300JCT-E1

Y

Y

Y

Y

DTI/240SC

-

-

-

Y

DTI/300SC

-

-

-

Y

LSI/81SC

-

Y

Y

Y

LSI/161SC

-

Y

Y

Y

DTI/241SC

-

Y

Y

Y

DTI/301SC

-

Y

Y

Y

D/240SC-2T1

Y

Y

Y

Y

D/480SC-2T1

Y

Y

Y

Y

D/480JCT-2T1

Y

Y

Y

Y

D/300SC-2E1

Y

Y

Y

Y

D/600SC-2E1

Y

Y

Y

Y

D/600JCT-2E1

Y

Y

Y

Y

DTI/480SC

-

-

-

Y

DTI/600SC

-

-

-

Y

D/320SC-IDPD

Y

Y

Y

-

D/240SC-T1-IDPD

Y

Y

Y

Y

D/300SC-E1-IDPD

Y

Y

Y

Y

D/160SC-LS-IDPD

Y

Y

Y

Y

NOTE:
Global DPD boards have an -IDPD suffix. Throughout the documentation in this release, these boards are generally referred to by their generic designation without the -IDPD suffix

The table below shows the DM3 products that support major voice features and include onboard network interfaces:

 Board

Voice

Call Progress

Tone

Network Interface

DM/F240-PCI

 

     

DM/F240-cPCI

       

DM/F240-1T1-PCI

 

Y

Y

Y

DM/F300-PCI

       

DM/F300-cPCI

       

DM/F300-1E1-PCI

 

Y

Y

Y

DM/VF240-1T1-PCI

Y

Y

Y

Y

DM/VF300-1E1-PCI

Y

Y

Y

Y

DM/IP241-1T1-PCI-100BT

Y

Y

Y

 

DM/IP301-1E1-PCI-100BT

Y

Y

Y

 

DM/IP481-2T1-PCI-100BT

Y

Y

Y

 

DM/IP601-2E1-PCI-100BT

Y

Y

Y

 

DM/IP481-2T1-cPCI-100BT

Y

Y

Y

 

DM/IP601-2E1-cPCI-100BT

Y

Y

Y

 

DM/IP601-cPCI-100BT

Y

 

Y

 

DM/N960-4T1-PCI

     

Y

DM/N960-4T1-cPCI

     

Y

DM/N1200-4E1-PCI

     

Y

DM/N1200-4E1-cPCI

     

Y

DM/T960-4T1-PCI

 

Y

Y

Y

DM/T960-4T1-cPCI

 

Y

Y

Y

DM/T1200-4E1-PCI

 

Y

Y

Y

DM/T1200-4E1-cPCI

 

Y

Y

Y

DM/V480-4T1-PCI

Y

Y

Y

Y

DM/V480-4T1-cPCI

Y

Y

Y

Y

DM/V600-4E1-cPCI

Y

Y

Y

Y

DM/V600-4E1-PCI

Y

Y

Y

Y

DM/V960-4T1-PCI

Y

Y

Y

Y

DM/V960-4T1-cPCI

Y

Y

Y

Y

DM/V1200-4E1-PCI

Y

Y

Y

Y

DM/V1200-4E1-cPCI

Y

Y

Y

Y

DM/V480A-2T1-PCI

Y

Y

Y

Y

DM/V480A-2T1-cPCI

Y

Y

Y

Y

DM/V600A-2E-PCI

Y

Y

Y

Y

DM/V600A-2E1-cPCI

Y

Y

Y

Y

DM/V960A-4T1-PCI

Y

Y

Y

Y

DM/V960A-4T1-cPCI

Y

Y

Y

Y

DM/V1200A-4E1-PCI

Y

Y

Y

Y

DM/V1200A-4E1-cPCI

Y

Y

Y

Y

DM/V2400A-PCI

Y

Y

Y

Y

DM/V2400A-cPCI

Y

Y

Y

Y

The table below shows which SpringWare products have been tested and are known to work with a DM3 product family.

Board

DM3 IPLink

DM3 MediaSpan

DM3 Fax

D/4-PCI

     

D/80SC

YES

YES

 

D/80PCI

YES

YES

YES

D/160SC

YES

   

D/160SC-HS

YES

   

D/240SC

YES

YES

YES

D/320SC

YES

YES

YES

D/320PCI

YES

YES

YES

D/320SC-IDPD

     

D/640SC

YES

 

YES

D/21E

     

D/41ESC

YES

YES

YES

D/41EPCI

YES

   

D/41H

     

D/41JCT-LS

     

DCB/320SC

YES

YES

YES

DCB/640SC

YES

 

YES

DCB/960SC

YES

   

MSI/80SC-Global

     

MSI/160SC-Global

   

YES

MSI/240SC-Global

   

YES

MSI/80PCI-Global

     

MSI/160PCI-Global

     

HDSI/PCI

     

HDSI/cPCI

     

PC-CS6

     

VFX/40ESC plus

YES

YES

 

VFX/40PCI

YES

   

VFX/41JCT-LS

     

DTI/240SC

     

DTI/241SC

YES

 

YES

DTI/480SC

YES

YES

YES

DTI/481SC

YES

YES

YES

DTI/300SC

YES

YES

YES

DTI/301SC

YES

YES

YES

DTI/600SC

YES

YES

YES

DTI/601SC

YES

YES

YES

LSI/81SC

YES

   

LSI/161SC

YES

   

D/240SC-T1

YES

 

YES

D/240SC-T1-IDPD

     

D/240SC-2T1

     

D/480SC-2T1

YES

YES

 

D/240PCI-T1

YES

YES

 

D/240JCT-T1

   

YES

D/300SC-E1

YES

YES

 

D/300SC-E1-IDPD

     

D/300SC-2E1

YES

   

D/600SC-2E1

YES

 

YES

D/300PCI-E1

YES

   

D/300JCT-E1

YES

YES

YES

D/480JCT-2T1

     

D/600JCT-2E1

     

D/80SC-4LS

     

D/160SC-8LS

     

D/160SC-LS

YES

YES

YES

D/160SC-LS-IDPD

     

D/120JCT-LS

YES

YES

YES

BRI/80SC

     

BRI/160SC

     

BRI/80PCI

YES

YES

YES

BRI/160PCI

 

YES

 

D/42JCT-U

     

D/82JCT-U

     

SCX160

     

Antares 3000/60-PCI

YES

YES

YES

Since testing was still going on at the time this guide was finalized, please look in the Release Update accompanying this release for this information..


Top Of PageDevelopment Software Features

The following categories of software features were provided previously and are still supported in this release:

NOTE:
Refer to the GlobalCall API Software Reference for additional information.
NOTE:
ICAPI, Analog and PDKRT protocols are separately orderable. The GlobalCall CDP Reference for PDK Protocols is also found on the GlobalCall Protocols CD-ROM.

All ANAPI, ICAPI, and PDKRT protocols are configurable using GlobalCall CDP (Country-Dependent Parameters) files. In addition, PDKRT protocol site-specific configuration can be set using SDP (Site-Dependent Parameters) files.

In the previous release for Linux, GlobalCall, its associated call control libraries, and supported protocols were available only as static libraries or objects. In this release, support for shared libraries is provided to simplify the building of applications in a Linux environment.

The benefits of shared libraries include:

  1. Removal of the ancountry.c and country.c files. You no longer need to manually configure the ancountry.c or country.c files for each protocol to be linked into the application. The ANAPI or ICAPI protocol is automatically located when the gc_Open( ) function is called.
  2. The application is not required to link against any of the call control libraries. When the gc_Start( ) function is called, the libraries are automatically loaded.
  3. Stub libraries are not used. While the gc_Start( ) function is executing, if a call control library file is not found, it is considered a stub library. There are no separate stub libraries.

The table below shows the library files that are to be linked against a GlobalCall application.

Filenames for Call Control Libraries

Call Control Library

Shared Library Filenames

ANAPI

libanapi.so

GC ISDN

libgcis.so

ICAPI

libicapi.so

PDKRT

libpdkrt.so

The order in which the files should be included is as follows:

  1. libgc.so - Linking this file is mandatory. Use the -lgc argument to the system linker.
  2. libdxxx.so - Required only if your application uses R4 voice library functions directly, for example, dx_play( ).
  3. libdti.so - Required only if your application uses R4 network library functions directly, for example, dt_getparm( ). Using network functions directly in a GlobalCall application is not recommended.
  4. libsrl.so - Required only if your application uses R4 SRL library functions directly, for example, sr_enbhdlr( ).
NOTE:
Caution: For System Release 5.1 for Linux, you must use protocols from the GlobalCall Protocol Package CDROM, which contains shared library versions of all protocols for each operating system that GlobalCall supports. Previously released
static protocol modules are not supported.

Below are the SpringWare boards supported in this release and what protocols may be used:


Product


Bus


Analog

E-1
CAS

T-1
Robbed Bit

E-1
ISDN

T-1
ISDN

D/41EPCI

PCI

Yes

-----

-----

-----

-----

D/41ESC

ISA

Yes

-----

-----

-----

-----

D/160SC-LS

ISA

Yes

-----

-----

-----

-----

D/120JCT-LS

PCI

Yes

-----

-----

-----

-----

D/240SC

ISA

-----

-----

Yes

-----

-----

D/300PCI-E1

PCI

-----

Yes

-----

Yes

-----

D/300JCT-E1

PCI

-----

Yes

-----

Yes

-----

D/300SC-E1

ISA

-----

Yes

-----

Yes

-----

D/300SC-2E1

ISA

-----

Yes

-----

Yes

-----

D/600SC-2E1

ISA

-----

Yes

-----

Yes

-----

D/320SC

ISA

-----

Yes

-----

-----

-----

D/640SC

ISA

-----

Yes

-----

Yes

-----

DTI/300SC

ISA

-----

Yes**

-----

Yes

-----

DTI/301SC

ISA

-----

Yes

-----

Yes

-----

D/240PCI-T1

PCI

-----

-----

Yes

-----

Yes

D/240JCT-T1

PCI

-----

-----

Yes

-----

Yes

D/240SC-T1

ISA

-----

-----

Yes

-----

Yes

D/240SC-2T1

ISA

-----

-----

Yes

-----

Yes

D/480SC-2T1

ISA

-----

-----

Yes

-----

Yes

D/480JCT-2T1

PCI

-----

-----

Yes

-----

Yes

DTI/240SC

ISA

-----

-----

Yes**

-----

Yes

DTI/241SC

ISA

-----

-----

Yes

-----

Yes

DTI/480SC

ISA

-----

-----

Yes**

-----

Yes

DTI/481SC

ISA

-----

-----

Yes

-----

Yes

DTI/600SC

ISA

-----

Yes**

-----

Yes

-----

DTI/601SC

ISA

-----

Yes

-----

Yes**

-----

D/600JCT-2E1

PCI

-----

Yes

-----

Yes

-----

D/41JCT-LS

PCI

Yes

       

VFX/41JCT-LS

PCI

Yes

       

NOTES:
1: ** A voice resource is required for this interface.
2: Not all boards are compatible with all protocols. For additional information, please consult your sales representative.

The PBX Integration products (D/82JCT-U and D/42JCT-U) provide the following PBX integration features:

NOTE:
Refer to the SCbus Routing Software Reference for Linux for additional information.

This release supports the SCbus routing that has the following features:

NOTE:
Refer to the Dialogic Audio Conferencing Software Reference for Linux for additional information.

The features provided by Dialogic Audio Conferencing are:

NOTE:
Refer to the MSI Software Reference for additional information.

This modular station interface for analog equipment enables conferencing and:

NOTE:
Refer to the Fax Software Reference for additional information.

The features supported by DSP Fax are:

NOTE:
14.4 Kbps receive and enhanced error correcting schemes are available when enhanced DSP-Based Fax is being used. Currently, only the VFX/41JCT-LS has this capability.

The following table shows information regarding the boards and channels that support DSP-Based Fax.

Board

Chan

Chan

Chan

Chan

Chan

Chan

Chan

Chan

Fax Resource Channels Enabled

D/41JCT-LS

1-4

-

-

         

4

VFX/41JCT-LS*

1-4

-

-

         

4

D/120JCT-LS

1-8

9-12

-

         

2+2

D/42JCT-U

1-4

             

2

D/82JCT-U

1-8

             

2

D/240JCT

1-8

9-16

17-24

         

2+2

D/300JCT

1-8

9-14

15-22

23-30

       

2+2

D/320-JCT

1-8

9-16

17-24

25-32

       

2+2+2+2

D/160-JCT

1-8

9-16

           

2+2

D/480JCT-2T1

1-8

9-16

17-24

25-32

33-40

41-48

   

2+2+2+2

D/600JCT-2E1

1-8

9-14

15-22

23-30

31-38

39-44

45-52

53-60

2+2+2+2

* Only the VFX/41JCT-LS supports enhanced fax.

All Channels that support DSP-based Fax enablement are highlighted in gray.

The 2+2 mapping indicates that each channel in gray can support 2 fax resources except D/41JCT-LS and VFX/41JCT-LS boards.

D/41JCT-LS and VFX/41JCT-LS support 4 fax resources (i.e.,1 resource for each channel).

D/120JCT-LS supports 2 fax resources on channels 1-8 and 2 fax resources on channels 9-12.

The following table shows the data transmission and reception encoding schemes that can be used with the basic and enhanced fax feature:

Basic Fax

Enhanced Fax

MH

MH

MR

MR

 

MMR

 

ECM

VFX features for transmit and receive are as follows:

NOTE:
Refer to the ISDN Software Reference for additional information.

The following table lists all of the ISDN functions that are currently documented in the ISDN Software Reference. The table indicates which functions are supported for BRI/SC Version 3.00, BRI/PCI and PRI ISDN Package5.

ISDN API Functions

BRI/SC

BRI/PCI

PRI ISDN

cc_AcceptCall( )

YES

YES

YES

cc_AnswerCall( )

YES

YES

YES

cc_CallAck( )

YES

YES

YES

cc_CallProgress( )

YES

YES

YES

cc_CallState( )

YES

YES

YES

cc_CauseValue( )

YES

YES

YES

cc_Close( )

YES

YES

YES

cc_CRN2LineDev( )

YES

YES

YES

cc_DropCall( )

YES

YES

YES

cc_GetANI( )

YES

YES

YES

cc_GetBChanState( )

YES

YES

YES

cc_GetBilling( )

   

YES

cc_GetCallInfo( )

YES

YES

YES

cc_GetCES( )

YES

YES

 

cc_GetCRN( )

YES

YES

YES

cc_GetDChanState( )

   

YES

cc_GetDLinkCfg( )

 

YES

 

cc_GetDLinkState( )

 

YES

YES

cc_GetDNIS( )

YES

YES

YES

cc_GetEvtMsk( )

YES

YES

YES

cc_GetFrame( )

YES

YES

YES

cc_GetInfoElem( )

YES

YES

YES

cc_GetLineDev( )

YES

YES

YES

cc_GetMoreDigits( )

YES

YES

YES

cc_GetNetCRV( )

YES

 

YES

cc_GetNonCallMsg( )

YES

YES

YES

cc_GetParm( )

YES

YES

YES

cc_GetParmEx( )

YES

 

YES

cc_GetSAPI( )

YES

YES

 

cc_GetSigInfo( )

YES

YES

YES

cc_GetUsrAttr( )

   

YES

cc_GetVer( )

YES

YES

YES

cc_HoldAck( )

YES

 

YES (1)

cc_HoldCall( )

YES

 

YES (1)

cc_HoldRej( )

YES

 

YES (2)

cc_MakeCall( )

YES

YES

YES

cc_Open( )

YES

YES

YES

cc_PlayTone( )

YES

YES

 

cc_ReleaseCall( )

YES

YES

YES

cc_ReleaseCallEx( )

YES

YES

YES

cc_ReqANI( )

   

YES

cc_Restart( )

YES

YES

YES

cc_ResultMsg( )

YES

YES

YES

cc_ResultValue( )

YES

YES

YES

cc_RetrieveAck( )

YES

 

YES (1)

cc_RetrieveCall( )

YES

 

YES (1)

cc_RetrieveRej( )

YES

 

YES (2)

cc_SetBilling( )

   

YES

cc_SetCallingNum( )

YES

YES

YES

cc_SetChanState( )

   

YES

cc_SetDChanCfg( )

YES

YES

 

cc_SetDLinkCfg( )

 

YES

 

cc_SetDLinkState( )

 

YES

 

cc_SetEvtMask( )

YES

YES

YES

cc_SetInfoElem ( )

YES

YES

YES

cc_SetMinDigits( )

YES

YES

YES

cc_SetParm( )

YES

YES

YES

cc_SetParmEx( )

YES

YES

YES

cc_SetUsrAttr( )

YES

YES

YES

cc_SndFrame( )

YES

YES

YES(3)

cc_SndMsg

YES

YES

YES

cc_SndNonCallMsg( )

YES

YES

YES

cc_StartTrace( )

YES

YES

YES

cc_StopTone( )

YES

YES

 

cc_StopTrace( )

YES

YES

YES

cc_TermRegister
Response( )

YES

YES

 

cc_ToneRedfine( )

YES

YES

 

cc_WaitCall( )

YES

YES

YES

NOTES:
1: Supported only for the DPNSS and Q.SIG PRI protocols.
2: Supported only for the Q.SIG PRI protocol.
3: Not supported for the Q.SIG PRI protocol.

The following PRI features are supported:

The following PRI protocols are supported:

Protocol (for SpringWare Products)

Firmware

Equipment Type

AT&T 4ESS custom switch
TR41449/TR41459

4ESS

TE

T-1 Network Emulation
TR41449/TR41459

NT1

NT

AT&T 5ESS custom switch
505-900-322

5ESS

TE

National ISDN-2 Bellcore Special Report SR-NWT-002343

NI2

TE

Northern Telecom custom switch
A211-1 and A211-4

DMS/100 and DMS/250

TE

Japanese National ISDN INS-Net 1500

NTT

TE

French National ISDN VN3

VN

TE

French National ISDN VN3

VNNT

NT

Euro-ISDN ETSI300-102

CTR4

TE

Euro-ISDN ETSI300-102

NE1

NT

British National BTNR-190-1985

DASS2

TE

Australian National ISDN
TS-0141 1990

TPH

TE

Australian National ISDN
TS-0141 1990

TPHNT

NT

Q.SIG ISO 11572, ISO 11574

QTE

TE

Q.SIG ISO 11572, ISO 11574

QNT

NT

German National ISDN

1TR6

TE

British Private Branch Exchange DASS2 extension

DPNSS (separately orderable)

A and B side

Euro-ISDN
ETSI300-102 for T-1

ETU

TE

Euro-ISDN
ETSI300-102 for T-1

ETN

NT

Q.SIG ECMA-142/143 for T-1

QTU

TE

Q.SIG ECMA-142/143 for T-1

QTN

NT

TE = Terminal Equipment

NT = Network Termination

R4 Network Interface support is provided by the Digital Network Interface (DTI) Library which provides the following features:

Antares products provide the following features:

NOTE:
Refer to the Voice Software Reference for additional information.

The dictation support features include:

The play features include:

The following restrictions apply:
- GSM and G.726 do not support Silence Compressed Record
- GSM and G.726 do not support Speed Control - When you play a voice file recorded in GSM or G.726, you must specify the format (this is necessary even for the WAVE GSM files, although WAVE files can normally be played without specifying the format because the format is stored in the file header)

This release supports the recording of data to any combination of data files, memory or custom devices with selectable Automatic Gain Control (AGC) (on/off) and/or preceding tone (on/off) at the following bit rates and voice coder types:

NOTE:
See http://support.dialogic.com/appnotes/ecr.htm for additional information about SCR and Echo Cancellation.

The following table shows which voice coders and encoding formats are supported with each SpringWare board.




Product


Mu-Law
PCM
6K, 8K


A-Law
PCM
6K, 8K


Mu-Law
PCM
11K


A-Law/
PCM
11K

Linear
(Raw)
PCM
6K, 8K


ADPCM
(OKI)
6K, 8K




ADSI

MS

GSM




G.726

D/4-PCI

YES

YES

YES

YES

YES

YES

YES

   

D/41H

YES

 

YES

 

YES

YES

YES

   

D/80SC

YES

YES

YES

YES

YES

YES

YES

   

D/80-PCI

YES

YES

YES

YES

YES

YES

YES

   

D/160SC

YES

YES

YES

YES

YES

YES

YES

   

D/240SC

YES

YES

YES

YES

YES

YES

YES

   

D/320SC

YES

YES

YES

YES

YES

YES

YES

   

D/320-PCI

YES

YES

YES

YES

YES

YES

YES

   

D/640SC

YES

YES

YES

YES

YES

YES

YES

   

D/21E

YES

YES

YES

YES

YES

YES

YES

   

D/41EPCI

YES

YES

YES

YES

YES

YES

YES

   

D/41ESC

YES

YES

YES

YES

YES

YES

YES

   

D/41JCT-LS

YES

YES

YES

YES

YES

YES

YES

YES

YES

VFX/40ESCplus

YES

YES

YES

YES

YES

YES

YES

   

VFX/40PCI

YES

YES

     

YES

YES

   

VFX/41JCT-LS

YES

YES

YES

YES

YES

YES

YES

YES

YES

D/160SC-LS

YES

YES

YES

YES

YES

YES

YES

   

D/120JCT-LS

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/240JCT-T1

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/300JCT-E1

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/480JCT-2T1

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/600JCT-2E1

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/42JCT-U

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/82JCT-U

YES

YES

YES

YES

YES

YES

YES*

YES

YES

D/300PCI-E1

YES

YES

YES

YES

YES

YES

YES

   

D/300SC-E1

YES

YES

YES

YES

YES

YES

YES

   

D/300SC-2E1

YES

YES

YES

YES

YES

YES

YES

   

D/600SC-2E1

YES

YES

YES

YES

YES

YES

YES

   

D/240PCI-T1

YES

YES

YES

YES

YES

YES

YES

   

D/240SC-T1

YES

YES

YES

YES

YES

YES

YES

   

D/240SC-2T1

YES

YES

YES

YES

YES

YES

YES

   

D/480SC-2T1

YES

YES

YES

YES

YES

YES

YES

   

BRI/2VFD

YES

YES

     

YES

YES

   

D/80SC-4LS

YES

YES

     

YES

YES

   

D/160SC-8LS

YES

YES

     

YES

YES

   

NOTE:
*Two-way FSK for ADSI (both transmit and receive) is not supported currently on the JCT products.

Top Of PageDiagnostic Utilities, Remote Adminstration, and Sample Programs

The Digital Private Network Signaling System (DPNSS) is an ISDN protocol that is commonly used in a network of Private Branch eXchanges (PBXs). DPNSS provides the following features:

ISDIAG is a diagnostics package that can be used with BRI and PRI applications. It is part of the DialView Suite (see R4 ISDN Features). ISDIAG provides the following features:

NOTES:
1: Refer to the Using BoardWatch Guide for additional information.
2: BoardWatch 5.1.1 does not support single board start/stop for SpringWare boards but it does for DM3 boards.

Sample demo programs are provided in the <install drive>./<install directory>/Dialogi/\samples folder for the following technologies:

NOTE:
* indicates the demo programs may require special enablement. See your Dialogic Sales representative for additional information.

Top Of PageCopyright Notice

Copyright © 2002 Intel Corporation. All Rights Reserved.

Information in this document is provided in connection with Intel® products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel® products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications.

Intel may make changes to specifications and product descriptions at any time, without notice.

This document as well as the software described in it is furnished under license and may only be used or copied in accordance with the terms of the license. The information in this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Intel Corporation. Intel Corporation assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document.

Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without express written consent of Intel Corporation.

Some names, products, and services mentioned herein are the trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Other names and brands may be claimed as the property of others.

Publication Date: January, 2002

Part Number: 05-1672-001

Intel Corporation
Telecommunications and Embedded Group
1515 Route 10
Parsippany NJ 07054
U.S.A.

For Technical Support, visit the Dialogic support website at:
http://support.dialogic.com

For Sales Offices and other contact information, visit the main Dialogic website at:
http://www.dialogic.com


Table Of ContentsTop Of Page

Click here to contact Dialogic Customer Engineering

Copyright 2002, Intel Corporation
All rights reserved
This page generated January, 2002