Dialogic® DSI SPCI Network Interface Boards Programmer's Manual Issue 5

Table 5: Files Installed on a System Running Linux

Name

Description

gctlib.lib

Library to be linked with user's application.

 

 

system.txt

Example system configuration file.

 

 

config.txt

Example protocol configuration file.

 

 

gctload.exe

Executables for use as described elsewhere in this

ssds.exe

manual.

s7_mgt.exe

 

s7_log.exe

 

s7_play.exe

 

tick_nt.exe

 

tim_nt.exe

 

upe.exe

 

 

 

INC

Sub-directory containing header files for use with user’s

 

application.

 

 

SPCI_CPM_DRIVER

Source code for the SPCI Network Interface Board

 

drivers.

 

The procedure to build and install these is described in

 

section 3.4.2.

 

 

3.4.2Device Drivers from Source Code

When the package is unloaded the source code for the driver for the DSI SPCI Boards is found in the subdirectory named SPCI_CPM_DRIVER. This source code must be built for the required Kernel version as described below.

Abuild script, named build_spci_cpm.sh, is included in this subdirectory. To build the driver, run this script.

This build script assumes a suitable environment for building Kernel modules is available. This must include the appropriate Kernel include files being found

at: /usr/src/linux-`uname -r`/include.

(e.g., /usr/src/linux-2.4.7-10/include). If these are not found, the build will fail.

Some Linux installations do not create a system source directory with the required name, for example some SMP kernels do not create a directory with the required smp suffix. If this is the case, then a softlink needs to be created to give an appropriate path to the system header files. For example:

cd /usr/src

ln –s linux-2.4.27 linux-2.4.27smp

Some later version of Linux uses a revised format for the remap_page_range parameters (for example Red Hat Linux Kernel Versions greater than 2.4.20 require this revised format). The build script supports an optional new_remap parameter. If this parameter is set, the compile uses the revised format.

The build script supports an optional clean parameter that removes the driver and all intermediate files.

Under some versions of Linux a warning similar to the following is generated:

warning: changing search order for system directory.

15

Page 14 Page 16
Page 15
Image 15
Dialogic DSI SPCI Network Interface Boards Device Drivers from Source Code, Files Installed on a System Running Linux
Page 14 Page 16

DSI SPCI Network Interface Boards specifications

Dialogic DSI SPCI Network Interface Boards are highly advanced and versatile communication solutions tailored for the demands of modern telephony and multimedia applications. These boards are designed to efficiently process voice, data, and signaling, making them an essential component for businesses looking to enhance their communication capabilities.

One of the standout features of the Dialogic DSI SPCI boards is their ability to handle multiple telephony protocols. This flexibility allows users to connect to various network types, whether PSTN, VoIP, or legacy systems, ensuring seamless interoperability. The boards support industry-standard protocols such as ISDN, SS7, and SIP, enabling integrated communication across diverse platforms.

The technology behind the Dialogic DSI SPCI boards incorporates state-of-the-art digital signal processing (DSP). This powerful DSP architecture provides efficient encoding and decoding of voice and video signals, leading to enhanced call quality and reduced latency. Moreover, the DSP technology supports advanced codecs, ensuring that voice communication is clear and intelligible, even over bandwidth-limited connections.

Another significant characteristic of these boards is their scalability. Organizations can start with a single board and expand their telecommunication capabilities as their needs grow. This scalability makes them suitable for a wide range of applications, from small businesses to large enterprises, allowing for easy integration into existing infrastructures.

In addition to their powerful processing capabilities, Dialogic DSI SPCI boards also prioritize reliability and robustness. They are designed with a focus on fault tolerance, ensuring that telephony services remain uninterrupted even in the event of hardware failure. This resilience is critical for mission-critical applications where downtime can lead to significant revenue loss.

Furthermore, the boards feature extensive application development support. Developers can leverage the Dialogic API and various development kits to create custom telephony applications that meet specific business requirements. This programmability opens the door to innovative solutions, such as interactive voice response (IVR) systems, automated call distribution (ACD), and customer relationship management (CRM) integration.

In summary, Dialogic DSI SPCI Network Interface Boards are a cornerstone for organizations looking to innovate their telecommunication systems. With their support for multiple protocols, advanced DSP technology, scalability, reliability, and development support, these boards empower businesses to optimize their communication strategies and adapt to the evolving landscape of digital interaction.
Top Page Image Contents