Dialogic DSI SPCI Network Interface Boards manual Parameter Description Error Code

Page 85

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

Parameter Description:

Error Code

The Error Code is coded as shown in the following table:

Value

Mnemonic

ID

Description

0x31

S7E_RESET_ERR

 

MTP2 Failed to initialize.

 

 

 

 

0x33

S7E_POOL_EMPTY

l2_llid

No free buffers in MTP2 transmit pool.

 

 

 

 

0x34

S7E_TX_FAIL

l2_llid

Failed to send LSSU/FISU to driver.

 

 

 

 

0x35

S7E_HDR_ERR

l2_llid

No room to add level 2 header, SU not

 

 

 

transmitted.

 

 

 

 

0x36

S7E_LEN_ERR

l2_llid

Length Error, SU not transmitted.

 

 

 

 

0x37

S7E_MSU_SEND

l2_llid

Failed to send SU to lower layer, protocol

 

 

 

should handle retransmission.

 

 

 

 

0x39

S7E_BAD_PRIM

l2_llid

MTP2 unable to accept primitive.

 

 

 

 

0x3a

S7E_BAD_LLID

l2_llid

Invalid l2_llid in HDR structure.

 

 

 

 

0x3b

S7E_MEM_ERR

l2_llid

MTP2 memory allocation error.

 

 

 

 

0x3c

S7E_RTVL_ERR

l2_llid

MTP2 failure to perform retrieval.

 

 

 

 

0x51

MTP_BAD_PRIM

0

MTP3 unable to accept primitive.

 

 

 

 

0x52

MTP_POOL_EMPTY

0

No free frames in MTP3 transmit pool.

 

 

 

 

0x53

MTP_TX_FAIL

0

MTP3 failed to send MSU to lower layer.

 

 

 

 

0x54

MTP_LEN_ERR

0

MSU too long for buffer.

 

 

 

 

0x55

MTP_SLT_FAIL

link_id

Signaling link test failure.

 

 

 

 

0x57

MTP_TALLOC_ERR

0

MTP3 Failed to allocate T_FRAME.

 

 

 

 

0x58

MTP_BAD_ID

0

Invalid ID in message HDR.

 

 

 

 

0x59

MTP_MALLOC_ERR

0

MTP3 unable to allocate MSG.

 

 

 

 

0x5a

MTP_BSNT_FAIL

link_id

Failure to retrieve BSNT.

 

 

 

 

0x5b

MTP_RTV_FAIL

link_id

Retrieval failure.

 

 

 

 

0x5c

MTP_BAD_FSN

link_id

Erroneous FSN in COA.

 

 

 

 

0x5d

MTP_BAD_COO

link_id

COO received after changeover complete.

 

 

 

 

0x5e

MTP_SNMM_ERR

0

Internal software error.

 

 

 

 

0x5f

MTP_SLTM_ERR

0

Internal software error.

 

 

 

 

0x60

MTP_NO_COA

link_id

Failed to receive COA.

 

 

 

 

0x61

MTP_NO_CBA

link_id

Failed to receive CBA.

 

 

 

 

0x66

MTP_TIM_ERR

timer ref

MTP3 attempt to re-use active timer resource.

 

 

 

 

0x67

MTP_RRT_OVRFLW

 

Messages discarded due to overflow of Re-

 

 

 

Routing buffer.

 

 

 

 

0x68

MTP_FLUSH_FAIL

link_id

MTP3 failed to receive Flush Ack from level 2.

 

 

 

 

0x69

MTP_FLUSH_L2

link_id

MTP2 transmission buffers flushed (due to

 

 

 

RPO).

 

 

 

 

85

Page 84 Page 86
Image 85
Page 84 Page 86
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 WindowsStarting 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 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 using the s7mgt utility Protocol ConfigurationProtocol Configuration Using Individual Messages Page Board Diagnostics Hardware Parameters Board Information DiagnosticsParameters are as described below Parameter DescriptionUsing 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 Event Indication Messages MTP Interface MessagesMessage Summary Table Message Summary0x3e18 SSD Reset Request General Configuration MessagesNumboards Board Reset RequestStatus 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 MessageValue Mnemonic Meaning Field Name Meaning Type Mgtmsgrbrdinfo 0x6f0d SrcSPCI2S 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 NfawClearmask 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 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 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 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 IndicationParameter Description Event Code 7 MTP2 Q.752 Event IndicationEvent 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 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 MTP Parameters MTP Global ConfigurationReserved1, reserved2 OptionsMTP Link Set MTP Signaling LinkLinkref LinkidSlc BlinkDpc MTP RouteNormls Blink Serial PortUserpartmask SecondlsIsup Parameters Global Isup ConfigurationMTP User Part Isup Circuit Group Configuration Userinst CicmaskOpc VariantGlobal configuration parameters for the TUP module Global TUP ConfigurationTUP Parameters Configuration parameters for a group of TUP circuits TUP Circuit Group Configuration107 Host Utilities Command Line OptionsSsds DescriptionS7mgt 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