Dialogic DSI SPCI Network Interface Boards manual Configuration and Operation, Overview

Page 19

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

4 Configuration and Operation

4.1Overview

Prior to performing software configuration, the user should gain an appreciation of:

•the flexibility of the protocol stack,

•the run-time options that exist,

•the mechanisms used to select particular features.

This section gives an overview of these aspects.

The user should also consult the Software Environment Programmer’s Manual, which describes the basic principles of modules and message passing.

4.1.1System Structure

The SS7 software running on the board communicates with an application running on the main CPU of the host computer. The physical interface to the board uses the PCI bus. All communication with the board is handled by a device driver and the messages passing to and from the board are managed by a process (ssds) that runs on the host computer.

In addition to running the application on the host computer, the user may, depending on the size of the overall system and the network topology, elect to also run some of the SS7 protocol modules on the host. In such cases, the interface between the application and the SS7 protocol software remains identical. This allows for easy migration from a small system contained on a single board to a large system distributed over many boards with minimal changes to the application. When a protocol is run on the host, it is necessary to purchase and install a Software License on the host.

The table illustrates some possible system configurations for a telephony system.

Table 7: Typical Telephony Systems Configurations

 

Small System

Medium System

Large System

Software running on

MTP2

MTP2

MTP2

the board

MTP3

MTP3

 

 

ISUP / TUP

 

 

 

 

 

 

Software running on

User Application

ISUP / TUP

MTP3

Host Computer

 

User Application

ISUP / TUP

 

 

 

User Application

Number of boards

Single

Single signaling

Multiple

 

 

board (additional

 

 

 

boards may

 

 

 

support voice only)

 

 

 

 

 

19

Page 18 Page 20
Image 19
Page 18 Page 20
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 SettingsStarting the Windows Device Driver Files Installed on a System Running WindowsName Description Clearing Windows 2000 Install Wizard Installing Development Package for Linux Software Installation 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 using the s7mgt utility Protocol ConfigurationProtocol Configuration Using Individual Messages Page Parameter Description Board Information DiagnosticsBoard Diagnostics Hardware Parameters Parameters are as described belowUsing the CT bus Watchdog TimerGeographic Addressing Static Initialization Switching ModelExample Code Building and Sending Sclisten Dynamic OperationMSG Page Program Execution under Windows Program ExecutionTo 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 Message Reference General Configuration MessagesHardware Control Messages Message Summary MTP Interface MessagesEvent Indication Messages Message Summary Table0x3e18 SSD Reset Request General Configuration MessagesNumboards Board Reset RequestStatus 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 MessageValue Mnemonic Meaning Field Name Meaning Type Mgtmsgrbrdinfo 0x6f0d SrcSPCI2S 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 FawClearmask RaigenRaigen Description Parameter Description Aisgen LIU Control RequestField Name Meaning Type Liumsgcontrol 0x7e35 Loopmode Diagnostic loop back mode taken from the following tableLoopmode 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 MeaningLocalstream If a parameter is not required, it must be set to zeroLocalslot Sourceslot SourcestreamCT bus speed Source Slot Range Destslot DeststreamParameter Description Busspeed Configure Clock RequestField 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 IndicationParameter Description Event Code 7 MTP2 Q.752 Event IndicationEvent 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 Description1 SS7BOARD Command Configuration Command ReferencePhysical 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 SecondlsIsup Parameters Global Isup ConfigurationMTP User Part Isup Circuit Group Configuration Variant CicmaskUserinst OpcGlobal configuration parameters for the TUP module Global TUP ConfigurationTUP Parameters Configuration parameters for a group of TUP circuits TUP Circuit Group Configuration107 Description Command Line OptionsHost Utilities SsdsS7mgt Kconfig fileMmodule 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