Previous PageTable Of Contents../index.htmlIndexNext Page


1.1. SCbus Routing Function Overview

The SCbus routing functions comprise network /resource (nr_) SCbus convenience functions and individual SCbus routing functions. For most routing applications, the following network/resource SCbus convenience functions should suffice. The SCbus convenience functions include all of the functionality of the individual SCbus routing functions.

nr_scroute( )

  Makes half or full duplex connection between two Dialogic devices.

nr_scunroute( )

  Breaks half or full duplex connection between two Dialogic devices.

The network/resource SCbus convenience functions are not part of the voice library. Their C source code is provided in a separate file called sctools.c in <install drive>:\<install directory>\dialogic\sctools directory.

The individual SCbus routing functions provide the ability to program each phase of connecting or disconnecting the receive channel of a device to the transmit channel of another device or to build your own convenience functions. These individual SCbus routing functions can be characterized by their prefix and by their suffix.

The prefix of the individual SCbus routing functions identify the type of device to which the function applies:

ag_

  analog device (loop-start interface)

dt_

  digital device(T-1 or E-1 digital service interface)

dx_

  voice device

fx_

  FAX device

ms_

  MSI device

The suffix of the individual SCbus routing functions identify the operation or task performed by the function:

_getctinfo( )

  Returns information about a device (analog device, voice device, digital device, or other technology device). This function is not used for routing.

_getxmitslot( )

  Returns the SCbus time slot information into an SC_TSINFO structure that includes the number of the SCbus time slot connected to the transmit channel of the specified device.

_listen( )

  Connects the listen (receive) channel of the specified device to an SCbus time slot.

_unlisten( )

  Disconnects the listen (receive) channel of the specified device from an SCbus time slot.

The individual SCbus functions described in this reference are:

ag_getctinfo( )

  returns information about analog device

ag_getctinfo( )

  returns information about analog device

ag_getxmitslot( )

  returns SCbus time slot information into an SC_TSINFO structure that includes the number of the SCbus time slot connected to the analog transmit channel

ag_listen( )

  connects analog receive (listen) channel to an SCbus time slot

ag_unlisten( )

  disconnects analog receive (listen) channel from SCbus time slot

dt_getctinfo( )

  returns information about digital interface device

dt_getxmitslot( )

  returns SCbus time slot information into an SC_TSINFO structure that includes the number of the SCbus time slot connected to the digital transmit channel

dt_listen( )

  connects digital receive (listen) channel to an SCbus time slot

dt_unlisten( )

  disconnects digital receive (listen) channel from SCbus time slot

dx_getctinfo( )

  returns information about voice device

dx_getxmitslot( )

  returns SCbus time slot information into an SC_TSINFO structure that includes the number of the SCbus time slot connected to the voice transmit channel

dx_listen( )

  connects receive voice (listen) channel to an SCbus time slot

dx_unlisten( )

  disconnects voice receive (listen) channel from SCbus time slot

fx_getxmitslot( )

  returns SCbus time slot information into an SC_TSINFO structure that includes the number of the SCbus time slot connected to the FAX transmit channel

fx_listen( )

  connects FAX receive (listen) channel to an SCbus time slot

fx_unlisten( )

  disconnects FAX receive (listen) channel from SCbus time slot

ms_getxmitslot( )

  returns SCbus time slot information into an SC_TSINFO structure that includes the number of the SCbus time slot connected to the MSI station

ms_listen( )

  connects MSI receive station to an SCbus time slot

ms_unlisten( )

  disconnects a MSI station from 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