3 Installation

Table 4: Files Installed on a System Running Windows®

Name

Description

gctlib.lib

Library to be linked with user's application (Microsoft*).

 

 

gctlibb.lib

Library to be linked with user's application (Borland*).

 

 

INC

Sub-directory containing include files.

 

 

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

 

servcfg.exe

 

gctserv.exe

 

mtpsl.exe

 

upe.exe

 

 

 

The installation process automatically installs the device driver so the setup program must be allowed to reboot the target machine when it has finished installing the package.

Installation is now complete, although the device driver is not yet running. The files the user needs to use, have been installed in the installation directory. It is recommended that the user does not modify any files in this directory, but instead creates a working directory into which all the necessary files are copied.

If the machine is a development machine without any target boards, then no further installation is required.

3.3.2Starting the Windows® Device Driver

The device driver is initially installed as "Manual", it must therefore be manually started by a user with Administrator privilege using the following procedure:

1)Select the Control Panel (Start Æ Settings Æ Control Panel).

2)Select the "System" icon. In the "system properties" select the "Hardware" tab and then select "Device manager". A tree of device nodes is presented.

3)From the toolbar select "View Æ ShowHiddenDevices": Open the "Non Plug and Play Drivers" device node branch. The "Septel" driver should be displayed. If the board was not present at install of the Development Package the device node may not be visible, this issue can be resolved by starting the driver interface at a command prompt using the command:

12

Page 12
Image 12
Dialogic DSI SPCI Network Interface Boards Starting the Windows Device Driver, Files Installed on a System Running Windows

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.