Dialogic DSI SPCI Network Interface Boards manual Liuconfig Command

Page 93

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

run_mode

Protocols selected to Run on the Board

DTI

Digital Trunk Interface only, no protocol software. This mode does NOT

 

require the use of a software license button).

 

 

MTP2

MTP2 protocol only.

 

 

MTP

MTP3 plus MTP2 protocols.

 

 

ISUP-S

ISUP, small version, plus all MTP.

 

 

ISUP

ISUP, regular version, plus all MTP.

 

 

ISUP-L

ISUP, large version, plus all MTP.

 

 

TUP-S

TUP, small version, plus all MTP.

 

 

TUP

TUP, regular version, plus all MTP.

 

 

TUP-L

TUP, large version, plus all MTP.

 

 

DTI

Digital Trunk Interface only, no protocol software. This mode does NOT

 

require the use of a software license button).

 

 

MTP2

MTP2 protocol only.

 

 

MTP

MTP3 plus MTP2 protocols.

 

 

See section 2.3.2 Capacity for details of the capacity for modules running on the DSI SPCI Boards.

7.1.2LIU_CONFIG Command

Syntax:

LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code>

 

<frame_format> <crc_mode>

Example:

LIU_CONFIG 0 0 5 1 1 1

This command is used during initialization to configure the operating parameters for a T1/E1 line interface unit.

<board_id>

The logical identity of the board in the range from 0 to one less than the number of boards supported.

<liu_id>

The identifier of the T1/E1 Line Interface Unit in the range from 0 to one less than the number of interfaces supported.

Note: For the SPCI2S, valid values for the LIU identifiers are 2 and 3.

<liu_type>

The physical type of interface according to the following table: (note that this must be selected by the user to be appropriate for the actual hardware fitted otherwise an error status is returned).

93

Page 92 Page 94
Image 93
Page 92 Page 94
Contents March Dialogic DSI Spci Network Interface BoardsCopyright and Legal Notice Contents Message Reference Configuration Command ReferenceHost Utilities 108 TablesRevision History Related Documentation IntroductionProduct Identification SpecificationCapability License ButtonsCapacity Protocol DimensioningIntroduction InstallationSoftware Installation for Windows Hardware configurationBoard Option Switch / Link Settings Installing Development Package for WindowsFiles 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 LinuxInstalling the Development Package for Solaris Software Installation for SolarisVerifying Device Driver Loading An example message isNon-serviced interrupts reports Solaris 10 Additional CommandsFiles Installed on a System Running Solaris Solaris 9 Interface Name CheckingRemoving the Development Package for Solaris System has to be rebooted to force the change to take effectTypical Telephony Systems Configurations Configuration and OperationOverview System StructureHost Processes and Utilities Following abbreviations are used in the tableIsdn User Part Telephony 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 Board Diagnostics Hardware Parameters Board Information DiagnosticsParameters are as described below Parameter DescriptionWatchdog 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 Event Indication Messages MTP Interface MessagesMessage Summary Table Message Summary0x3e18 SSD Reset Request General Configuration MessagesBoard Reset Request NumboardsStatus Response Phyid Parameter Description BoardtypeCodefile RunmodeFormat Board Status IndicationField Name Meaning Type MGTMSGCONFIG0 0x7F10 Src Board Configuration RequestDescription Event Type Value MeaningMaxsiflen Parameter Description Isolated from the other boards using the CT bus. The CT busMessage Reference Bit Data Rate Value Description Parameter Description Majrev General Module Identification MessageMajor revision identifier for the object being queried MinrevText Read Board Info Request MessageField Name Meaning Type Mgtmsgrbrdinfo 0x6f0d Src Value Mnemonic MeaningSPCI2S or SPCI4 board Swa BoardrevSwb PrommajrevField Name Meaning Type Liumsgconfig 0x7e34 LIU Configuration RequestHardware Control Messages Dst Mvdtaskid RspreqLinecode LiutypeLine coding technique taken from the following table FrameformatBuildout CrcmodeFaw NfawRaigen 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 RequestParameter Description State LIU CT bus Initialization RequestCurrent state of the LIU from the following table State DescriptionScchannel Parameter Description LiuidTsmask Field Name Meaning Type Mvdmsgscdriveliu 0x7e18 SrcMode 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 Clkmode Value Clock ModePllclksrc Value Bus speed No changeRef1mode 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 IndicationClock Event Indication Result of initial configuration coded as followsParameter Description Completion Status Field Name Meaning Type Mvdmsgclkind 0x0e23 SrcParameter Description Event ID Liustatus LIU Status IndicationStatus field in the message header is coded as follows Field Name Meaning Type Mvdmsgliustatus 0x0e01 Liuid SrcValue 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 Excessive error rate Suerm Excessive delay of acknowledgementOnset of signaling link congestion Abatement 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 MTP Parameters MTP Global ConfigurationReserved1, reserved2 OptionsMTP Link Set MTP Signaling LinkLinkref LinkidSlc BlinkDpc MTP RouteNormls Blink Serial PortUserpartmask SecondlsGlobal Isup Configuration Isup ParametersMTP User Part Isup Circuit Group Configuration Userinst CicmaskOpc VariantGlobal TUP Configuration Global configuration parameters for the TUP moduleTUP Parameters Configuration parameters for a group of TUP circuits TUP Circuit Group Configuration107 Host Utilities Command Line OptionsSsds DescriptionKconfig 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