1.2. Media Loads and Routing Configurations
Media loads are pre-defined sets of features supported by certain DM3 boards. A media load is downloaded to a board by choosing a configuration file set that supports that particular media load.
Most feature sets are numbered (for example, 1, 2, 9b) for identification purposes and each media load supports a different combination of features. Examples of media features include speed control, volume control, transaction recording, silence compressed record (SCR) and conferencing. For a complete list of features supported by each media load, consult the Release Guide accompanying your Dialogic System Software.
R4 on DM3 supports two types of routing configurations, fixed and flexible routing. With fixed routing, the resource devices (voice/fax) and network interface devices are permanently coupled together in a fixed configuration. Only the network interface time slot device has access to the CT Bus. With flexible routing, the resource devices (voice/fax) and network interface devices are independent, which allows exporting and sharing of the resources. All resources have access to the CT Bus. Except on some IntelŪ DialogicŪ Integrated (DI) Series boards, media loads support flexible routing. For a complete discussion on fixed and flexible routing, see the Compatibility Guide for the Dialogic R4 API on DM3 Products.
For a list of CONFIG files supported by each board, see the CONFIG file tables listed in Chapter 3, Boards and Applicable CONFIG File Sections.
MediaSpan Media Loads
- QuadSpan, DualSpan, and Voice Resource media load configuration files are identified by having an mlx prefix, where x represents the specific media load. Configuration files that do not begin with the mlx prefix do not support media loads and do not support flexible routing. For example, on a DM/V960A-4T1-cPCI board using the T-1 ISDN 4ESS protocol:
IPLink Media Loads
IPLink media loads and routing configurations are identified as follows:
- For example, on a DM/IP301-1E1-PCI-100BT board using the E-1 ISDN NET5 protocol:
Fax and VFN Media Loads
- Fax and VFN media load configuration files are identified by having an fn3 or a vfn3 prefix, respectively. Configuration files that do not begin either of these prefixes do not support media loads and do not support flexible routing. For example, on a DM/VF240-1T1-PCI board using the T-1 ISDN DMS protocol:
Dialogic Integrated Series Media Loads
- Dialogic Integrated (DI) Series media load 1 configuration files do not contain any media load identifier in the file name. For media loads greater than 1 (for example, media load 4), the media load configuration files are identified by having an mlx suffix, where x represents the specific media load. For example, on a DI/0408-LS-A-R2 board:
- Configuration files that do not contain an mlx prefix may or may not support media load 1. For example:
- For a complete list of media loads supported on each DI board, consult the Release Guide accompanying your Dialogic System Software.
Click here to contact Telecom Support Resources
Copyright 2003, Intel Corporation