Dialogic DSI SPCI Network Interface Boards manual Following abbreviations are used in the table

Page 20

4 Configuration and Operation

The following abbreviations are used in the table:

MTP2

Message Transfer Part – Level 2

MTP3

Message Transfer Part – Level 3

ISUP

ISDN User Part

TUP

Telephony User Part

In all cases, the process called ssds (SS7 Software Driver) must be run on the host computer. This handles message transfer between the host and the board using the device driver.

To define which protocol modules run on the host, edit the text file system.txt.

Run the program gctload, which reads the system configuration parameters from the file system.txt and starts up the selected processes bringing the system into operation.

For further details of gctload, refer to the Software Environment

Programmer’s Manual.

The following processes for use on the host are included in the distribution. All must be run on the host with the exception of s7_mgt, s7_log, and

s7_play, which are optional:

Table 8: Host Processes and Utilities

Name

Description

gctload

Process to initialize the system environment and start up all other related

 

processes running on the host, deriving the configuration from a text file

 

(system.txt).

 

 

ssds

Process to interface with the device driver for passing messages to and from

 

the board(s) and for downloading software to the board(s).

 

 

tick_nt

Protocol timer process to send periodic “tick” notification to the tim_xxx

tick_lnx

process which in turn handles protocol timers.

tick_sol

 

 

 

tim_nt

Process to receive periodic tick notification from tick_xxx and handle protocol

tim_lnx

timers for all other processes.

tim_sol

 

 

 

s7_mgt

Process to perform single shot protocol configuration for all protocol modules,

 

deriving the configuration parameters from a text file (config.txt). This process

 

is optional. As an alternative to using it, the user may elect to perform

 

protocol configuration by sending messages directly to the other modules in

 

the system.

 

 

s7_log

Utility process to allow messages received from the protocol stack to be

 

logged to a text file. This is useful for diagnostic purposes.

 

 

s7_play

Utility process used to generate messages from a text file and send them into

 

the system.

 

 

20

Page 19 Page 21
Image 20
Page 19 Page 21
Contents Dialogic DSI Spci Network Interface Boards MarchCopyright and Legal Notice Contents Configuration Command Reference Message ReferenceTables Host Utilities 108Revision History Introduction Related DocumentationSpecification Product IdentificationCapability License ButtonsProtocol Dimensioning CapacityInstallation IntroductionHardware configuration Software Installation for WindowsBoard Option Switch / Link Settings Installing Development Package for WindowsName Description Files Installed on a System Running WindowsStarting the Windows Device Driver Clearing Windows 2000 Install Wizard Removing Development Package for Windows Software Installation for LinuxInstalling Development Package for Linux Files Installed on a System Running Linux Device Drivers from Source CodeSoftware Installation for Solaris Installing the Development Package for SolarisVerifying Device Driver Loading An example message isSolaris 10 Additional Commands Non-serviced interrupts reportsFiles Installed on a System Running Solaris Solaris 9 Interface Name CheckingSystem has to be rebooted to force the change to take effect Removing the Development Package for SolarisConfiguration and Operation Typical Telephony Systems ConfigurationsOverview System StructureFollowing abbreviations are used in the table Host Processes and UtilitiesIsdn User Part Telephony User PartSystem Configuration System Configuration File SyntaxGenerating a System Configuration File For Linux, these Forkprocess commands are mandatory For Solaris, these Forkprocess commands are mandatoryProtocol Configuration Using Individual Messages Protocol ConfigurationProtocol Configuration using the s7mgt utility Page Board Information Diagnostics Board Diagnostics Hardware ParametersParameters are as described below Parameter DescriptionGeographic Addressing Watchdog TimerUsing the CT bus Switching Model Static InitializationDynamic Operation Example Code Building and Sending SclistenMSG Page To run the system within the current console, enter Program ExecutionProgram Execution under Windows Program Execution under Linux To run it in the background enterProgram Execution under Solaris Developing a User ApplicationNmake /f ctu.mnt Hardware Control Messages General Configuration MessagesMessage Reference MTP Interface Messages Event Indication MessagesMessage Summary Table Message Summary0x3e18 General Configuration Messages SSD Reset RequestStatus Response Board Reset RequestNumboards Parameter Description Boardtype PhyidCodefile RunmodeBoard Status Indication FormatBoard Configuration Request Field Name Meaning Type MGTMSGCONFIG0 0x7F10 SrcDescription Event Type Value MeaningMaxsiflen Isolated from the other boards using the CT bus. The CT bus Parameter DescriptionMessage Reference Bit Data Rate Value Description General Module Identification Message Parameter Description MajrevMajor revision identifier for the object being queried MinrevRead Board Info Request Message TextSPCI2S or SPCI4 board Field Name Meaning Type Mgtmsgrbrdinfo 0x6f0d SrcValue Mnemonic Meaning Boardrev SwaSwb PrommajrevLIU Configuration Request Field Name Meaning Type Liumsgconfig 0x7e34Hardware Control Messages Dst Mvdtaskid RspreqLiutype LinecodeLine coding technique taken from the following table FrameformatCrcmode BuildoutFaw NfawRaigen Description RaigenClearmask Field Name Meaning Type Liumsgcontrol 0x7e35 LIU Control RequestParameter Description Aisgen Loopmode Description Diagnostic loop back mode taken from the following tableLoopmode LIU Read Configuration Request LIU Read Control Request LIU State Request Offset Size Name StateLIU CT bus Initialization Request Parameter Description StateCurrent state of the LIU from the following table State DescriptionParameter Description Liuid ScchannelTsmask Field Name Meaning Type Mvdmsgscdriveliu 0x7e18 SrcValue Mnemonic Description 0xff None Setup failed ModeCT bus Listen Request Offset Size Name Liuid Timeslot ScchannelTimeslot MvipinvalidtimeslotFixed Data Output Request Offset Size Name Liuid Timeslot PatternReset Switch Request PatternCT bus Connect Request Field Name Meaning Mvdmsgscconnect 0x7e1fLocalslot If a parameter is not required, it must be set to zeroLocalstream CT bus speed Source Slot Range SourcestreamSourceslot Deststream DestslotField Name Meaning Type Mvdmsgcnfclock 0x7e20 Src Configure Clock RequestParameter Description Busspeed Value Clock Mode ClkmodePllclksrc Value Bus speed No changeValue NETREF1 clock Mode Ref1modeConfigure Clock Priority Request Field Name Meaning Type Mvdmsgclockpri 0x7e21 SrcParameter Description Liunpri Event Indication Messages 2 s7mgt Completion Status Indication Parameter Description Board StatusResult of initial configuration coded as follows Clock Event IndicationParameter Description Completion Status Field Name Meaning Type Mvdmsgclkind 0x0e23 SrcParameter Description Event ID LIU Status Indication LiustatusStatus field in the message header is coded as follows Field Name Meaning Type Mvdmsgliustatus 0x0e01 Liuid SrcError Indication Value Mnemonic StateParameter Description Error Code Error Code is coded as shown in the following table6 MTP2 Level 2 State Indication Parameter Description Link StateEvent Code is coded as shown in the following table 7 MTP2 Q.752 Event IndicationParameter Description Event Code Excessive delay of acknowledgement Excessive error rate SuermOnset of signaling link congestion Abatement of signaling link congestion8 MTP3 Q.752 Event Indication Offset Size Name Len Event specific parametersValue Mnemonic Paramter Description MtpevajspokPhysical Interface Parameters Configuration Command Reference1 SS7BOARD Command Bit CT Bus Clocking Mode Liuconfig Command Runmode Protocols selected to Run on the BoardCrcmode CRC mode taken from the following table Frameformat Frame format taken from the following tableLiuscdrive Command BoardidScbuslisten Command MTP Global Configuration MTP ParametersReserved1, reserved2 OptionsMTP Signaling Link MTP Link SetLinkid LinkrefSlc BlinkMTP Route DpcNormls Blink Serial PortSecondls UserpartmaskMTP User Part Global Isup ConfigurationIsup Parameters Isup Circuit Group Configuration Cicmask UserinstOpc VariantTUP Parameters Global TUP ConfigurationGlobal configuration parameters for the TUP module TUP Circuit Group Configuration Configuration parameters for a group of TUP circuits107 Command Line Options Host UtilitiesSsds DescriptionMmodule id Kconfig fileS7mgt Example Inotify module id

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