Dialogic DSI SPCI Network Interface Boards manual Device Drivers from Source Code

Page 15

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
Image 15
Page 14 Page 16
Contents March Dialogic DSI Spci Network Interface BoardsCopyright and Legal Notice Contents Message Reference Configuration Command ReferenceHost Utilities 108 TablesRevision History Related Documentation IntroductionLicense Buttons SpecificationProduct Identification CapabilityCapacity Protocol DimensioningIntroduction InstallationInstalling Development Package for Windows Hardware configurationSoftware Installation for Windows Board Option Switch / Link SettingsFiles Installed on a System Running Windows Starting the Windows Device DriverName Description Clearing Windows 2000 Install Wizard Software Installation for Linux Installing Development Package for LinuxRemoving Development Package for Windows Device Drivers from Source Code Files Installed on a System Running LinuxAn example message is Software Installation for SolarisInstalling the Development Package for Solaris Verifying Device Driver LoadingSolaris 9 Interface Name Checking Solaris 10 Additional CommandsNon-serviced interrupts reports Files Installed on a System Running SolarisRemoving the Development Package for Solaris System has to be rebooted to force the change to take effectSystem Structure Configuration and OperationTypical Telephony Systems Configurations OverviewTelephony User Part Following abbreviations are used in the tableHost Processes and Utilities Isdn User PartSystem Configuration File Syntax System ConfigurationGenerating a System Configuration File For Solaris, these Forkprocess commands are mandatory For Linux, these Forkprocess commands are mandatoryProtocol Configuration Protocol Configuration using the s7mgt utilityProtocol Configuration Using Individual Messages Page Parameter Description Board Information DiagnosticsBoard Diagnostics Hardware Parameters Parameters are as described belowWatchdog Timer Using the CT busGeographic Addressing Static Initialization Switching ModelExample Code Building and Sending Sclisten Dynamic OperationMSG Page Program Execution Program Execution under WindowsTo run the system within the current console, enter To run it in the background enter Program Execution under LinuxDeveloping a User Application Program Execution under SolarisNmake /f ctu.mnt General Configuration Messages Message ReferenceHardware Control Messages Message Summary MTP Interface MessagesEvent Indication Messages Message Summary Table0x3e18 SSD Reset Request General Configuration MessagesBoard Reset Request NumboardsStatus Response Runmode Parameter Description BoardtypePhyid CodefileFormat Board Status IndicationValue Meaning Board Configuration RequestField Name Meaning Type MGTMSGCONFIG0 0x7F10 Src Description Event TypeMaxsiflen Parameter Description Isolated from the other boards using the CT bus. The CT busMessage Reference Bit Data Rate Value Description Minrev General Module Identification MessageParameter Description Majrev Major revision identifier for the object being queriedText Read Board Info Request MessageField Name Meaning Type Mgtmsgrbrdinfo 0x6f0d Src Value Mnemonic MeaningSPCI2S or SPCI4 board Prommajrev BoardrevSwa SwbDst Mvdtaskid Rspreq LIU Configuration RequestField Name Meaning Type Liumsgconfig 0x7e34 Hardware Control MessagesFrameformat LiutypeLinecode Line coding technique taken from the following tableNfaw CrcmodeBuildout FawRaigen ClearmaskRaigen Description LIU Control Request Parameter Description AisgenField Name Meaning Type Liumsgcontrol 0x7e35 Diagnostic loop back mode taken from the following table LoopmodeLoopmode Description LIU Read Configuration Request LIU Read Control Request Offset Size Name State LIU State RequestState Description LIU CT bus Initialization RequestParameter Description State Current state of the LIU from the following tableField Name Meaning Type Mvdmsgscdriveliu 0x7e18 Src Parameter Description LiuidScchannel TsmaskMode Value Mnemonic Description 0xff None Setup failedOffset Size Name Liuid Timeslot Scchannel CT bus Listen RequestMvipinvalidtimeslot TimeslotOffset Size Name Liuid Timeslot Pattern Fixed Data Output RequestPattern Reset Switch RequestCT bus Connect Request Mvdmsgscconnect 0x7e1f Field Name MeaningIf a parameter is not required, it must be set to zero LocalstreamLocalslot Sourcestream SourceslotCT bus speed Source Slot Range Destslot DeststreamConfigure Clock Request Parameter Description BusspeedField Name Meaning Type Mvdmsgcnfclock 0x7e20 Src Value Bus speed No change Value Clock ModeClkmode PllclksrcRef1mode Value NETREF1 clock ModeField Name Meaning Type Mvdmsgclockpri 0x7e21 Src Configure Clock Priority RequestParameter Description Liunpri Event Indication Messages Parameter Description Board Status 2 s7mgt Completion Status IndicationField Name Meaning Type Mvdmsgclkind 0x0e23 Src Result of initial configuration coded as followsClock Event Indication Parameter Description Completion StatusParameter Description Event ID Field Name Meaning Type Mvdmsgliustatus 0x0e01 Liuid Src LIU Status IndicationLiustatus Status field in the message header is coded as followsValue Mnemonic State Error IndicationError Code is coded as shown in the following table Parameter Description Error CodeParameter Description Link State 6 MTP2 Level 2 State Indication7 MTP2 Q.752 Event Indication Parameter Description Event CodeEvent Code is coded as shown in the following table Abatement of signaling link congestion Excessive delay of acknowledgementExcessive error rate Suerm Onset of signaling link congestionOffset Size Name Len Event specific parameters 8 MTP3 Q.752 Event IndicationMtpevajspok Value Mnemonic Paramter DescriptionConfiguration Command Reference 1 SS7BOARD CommandPhysical Interface Parameters Bit CT Bus Clocking Mode Runmode Protocols selected to Run on the Board Liuconfig CommandFrameformat Frame format taken from the following table Crcmode CRC mode taken from the following tableBoardid Liuscdrive CommandScbuslisten Command Options MTP Global ConfigurationMTP Parameters Reserved1, reserved2MTP Link Set MTP Signaling LinkBlink LinkidLinkref SlcBlink Serial Port MTP RouteDpc NormlsUserpartmask SecondlsGlobal Isup Configuration Isup ParametersMTP User Part Isup Circuit Group Configuration Variant CicmaskUserinst OpcGlobal TUP Configuration Global configuration parameters for the TUP moduleTUP Parameters Configuration parameters for a group of TUP circuits TUP Circuit Group Configuration107 Description Command Line OptionsHost Utilities SsdsKconfig file S7mgtMmodule id Inotify module id Example

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