Previous Page Table Of Contents../index.html IndexNext Page


3.2.  Dialogic Configuration Manager

The open architecture of the SCbus provides the framework for configuring SCSA products or devices from different manufacturers so that all SCSA products installed in a system work together.

The Dialogic Configuration Manager (DCM) adds the SCX160 SCxbus Adapter board and any newly installed SCSA boards to the system configuration. The Dialogic Configuration Manager (DCM) detects the presence of an SCX160 board in the system and prompts the user to configure the SCX160 Board. If the node has not previously been configured, or if a change was made to the system configuration, select Yes to configure the SCX160 Board.

The configuration of each node depends on the previously configured nodes (lower numbered) in the system. The Dialogic SCX160 Configuration program uses the requirements file and the information about the other nodes that is stored in the Map file and generated by the Master Assignment Program to determine the following:

The Dialogic SCX160 Configuration program helps you to determine the number of data streams that need to be allocated to the node. More SCbus time slots than are required for the currently installed boards can be allocated to reserve the time slots for future use. If additional time slots are reserved, then additional boards may be added to these nodes without reconfiguring the system, until you run out of reserved SCbus time slots.

The Dialogic Service needs to be started at each node after installing the software and then running the Dialogic Configuration Manager (DCM). Starting the Dialogic Service automatically initiates the following functions:

The following sections describe the information received by the requirements file and how the Master Assignment Program uses this information to allocate time slots.

The following information is output to the requirements file:

This information is used by the Master Assignment Program to calculate the number of time slots required by the node, as described in the following section.

The Master Assignment Program reads all SCbus time slot requirements information stored in the Requirements file, adds up the time slot requirements, reads the starting (base) data stream from the Global or Local Map file, and then allocates SCbus transmit time slots in non-overlapping sets or bundles of 64. Each bundle of 64 time slots is handled as a data stream (DS0 through DS15) by the SCX160 SCxbus Adapter. The SCX160 SCxbus Adapter maps the SCbus transmit data streams onto corresponding numbered SCxbus data streams, and vice-versa, so that all SCbus transmit time slots are available to all PC hosts connected to the SCxbus. No data streams or time slots are switched by the SCX160 SCxbus Adapter.

The Master Assignment Program then calls each Time Slot Assignment Program and passes the following arguments:

The Master Assignment Program then waits for notification that all Time Slot Assignment Programs executed and ran successfully.

The Time Slot Assignment Programs disconnect all SCbus time slots in a node and then connect each device transmit channel to an SCbus transmit time slot in accordance with the time slot information received from the program. A single Time Slot Assignment Program may assign SCbus transmit time slots to different types of SCbus products.

The assignment of SCbus (and concurrently SCxbus) transmit time slots uses a common mechanism to ensure that each device transmit channel in each node is assigned to a unique SCbus transmit time slot from 0 through 1023 for a total of 1024 transmit time slots per system. SCbus time slots are assigned at each Dialogic Service startup.

CAUTION


Do not manually execute the product group's Time Slot Assignment Programs. To do so could cause two transmit channels to be assigned to a time slot. Hardware can be damaged if two boards transmit on the same SCbus time slot.



Previous PageTable Of ContentsTop Of PageIndexNext Page

Click here to contact Dialogic Customer Engineering

Copyright 2001, Dialogic Corporation
All rights reserved
This page generated February, 2002