Dialogic DSI SPCI Network Interface Boards manual Message Reference

Page 46

6 Message Reference

Bit 13 is set to 1 to cause the board to drive the CT_NETREF1 clocks on the CT bus. The highest priority in-sync line interface is used as a clock source. If this bit is set to zero then CT_NETREF1 clock is not driven.

All other bits are reserved and must be set to zero.

l2_flags - level 2 flags

Bit 1 is set to 1 for ANSI operation or zero for ITU-T operation. Bit 3 is set to 1 for ANSI operation or zero for ITU-T operation.

Bit 5 is set to 1 to cause Link Status Signal Units (LSSU) to have a two octet status field. Usually this bit is set to zero, and LSSUs have a single octet status field.

All other bits are reserved for future use and must be set to zero.

max_sif_len - maximum Signaling Information Field length

The maximum Signaling Information Field length in octets that is permitted over the signaling link. Usually set to 272 although it may be set to 62 for inter-working with switches that do not support 272 octet messages.

l3_flags - level 3 flags

Bit 0 is set to 1 to disable the level 3 discrimination function (allowing the signaling point to receive all messages irrespective of the destination point code contained in the message) or zero to allow the discrimination function to function normally.

Bit 1 is set to 1 to disable sub-service field (SSF) discrimination. If this bit is set to zero, received MSUs whose ssf values do not match the configured ssf value are discarded.

Bit 8 is set to 1 to select ANSI operation or zero for ITU-T operation.

Bit 9 is set to 1 to select ANSI style 24 bit point codes in the MTP routing label or zero to select ITU-T style 14 bit point codes. This bit must be set to 1 if ANSI operation is selected.

Bit 10 is set to 1 for ANSI operation or zero for ITU-T operation. Bit 11 is set to 1 for ANSI operation or zero for ITU-T operation. All other bits are reserved for future use and must be set to zero.

Note: For ANSI operation bits 8, 9, 10, and 11 must all be set to 1.

pc - point code

The pure binary representation of this signaling point code. Must be in the range 0 to 16383 for 14 bit point code operation, or 0 to 16777215 for 24 bit point code operation.

ssf - sub-service field

The value used in the sub-service field of all messages generated by level 3. Must be in the range 0 to 15. For ANSI operation, the 2 least significant bits must be set to 1.

46

Page 45 Page 47
Image 46
Page 45 Page 47
Contents Dialogic DSI Spci Network Interface Boards MarchCopyright and Legal Notice Contents Configuration Command Reference Message ReferenceTables Host Utilities 108Revision History Introduction Related DocumentationCapability SpecificationProduct Identification License ButtonsProtocol Dimensioning CapacityInstallation IntroductionBoard Option Switch / Link Settings Hardware configurationSoftware Installation for Windows 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 Files Installed on a System Running Linux Device Drivers from Source CodeVerifying Device Driver Loading Software Installation for SolarisInstalling the Development Package for Solaris An example message isFiles Installed on a System Running Solaris Solaris 10 Additional CommandsNon-serviced interrupts reports Solaris 9 Interface Name CheckingSystem has to be rebooted to force the change to take effect Removing the Development Package for SolarisOverview Configuration and OperationTypical Telephony Systems Configurations System StructureIsdn User Part Following abbreviations are used in the tableHost Processes and Utilities 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 the s7mgt utility Protocol ConfigurationProtocol Configuration Using Individual Messages Page Parameters are as described below Board Information DiagnosticsBoard Diagnostics Hardware Parameters Parameter DescriptionUsing the CT bus Watchdog TimerGeographic Addressing Switching Model Static InitializationDynamic Operation Example Code Building and Sending SclistenMSG Page Program Execution under Windows Program ExecutionTo run the system within the current console, enter Program Execution under Linux To run it in the background enterProgram Execution under Solaris Developing a User ApplicationNmake /f ctu.mnt Message Reference General Configuration MessagesHardware Control Messages Message Summary Table MTP Interface MessagesEvent Indication Messages Message Summary0x3e18 General Configuration Messages SSD Reset RequestNumboards Board Reset RequestStatus Response Codefile Parameter Description BoardtypePhyid RunmodeBoard Status Indication FormatDescription Event Type Board Configuration RequestField Name Meaning Type MGTMSGCONFIG0 0x7F10 Src Value MeaningMaxsiflen Isolated from the other boards using the CT bus. The CT bus Parameter DescriptionMessage Reference Bit Data Rate Value Description Major revision identifier for the object being queried General Module Identification MessageParameter Description Majrev MinrevRead Board Info Request Message TextValue Mnemonic Meaning Field Name Meaning Type Mgtmsgrbrdinfo 0x6f0d SrcSPCI2S or SPCI4 board Swb BoardrevSwa PrommajrevHardware Control Messages LIU Configuration RequestField Name Meaning Type Liumsgconfig 0x7e34 Dst Mvdtaskid RspreqLine coding technique taken from the following table LiutypeLinecode FrameformatFaw CrcmodeBuildout 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 LIU State Request Offset Size Name StateCurrent state of the LIU from the following table LIU CT bus Initialization RequestParameter Description State State DescriptionTsmask Parameter Description LiuidScchannel 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 0x7e1fLocalstream If a parameter is not required, it must be set to zeroLocalslot Sourceslot SourcestreamCT bus speed Source Slot Range Deststream DestslotParameter Description Busspeed Configure Clock RequestField Name Meaning Type Mvdmsgcnfclock 0x7e20 Src Pllclksrc Value Clock ModeClkmode 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 StatusParameter Description Completion Status Result of initial configuration coded as followsClock Event Indication Field Name Meaning Type Mvdmsgclkind 0x0e23 SrcParameter Description Event ID Status field in the message header is coded as follows LIU Status IndicationLiustatus 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 StateParameter Description Event Code 7 MTP2 Q.752 Event IndicationEvent Code is coded as shown in the following table Onset of signaling link congestion Excessive delay of acknowledgementExcessive error rate Suerm Abatement of signaling link congestion8 MTP3 Q.752 Event Indication Offset Size Name Len Event specific parametersValue Mnemonic Paramter Description Mtpevajspok1 SS7BOARD Command Configuration Command ReferencePhysical Interface Parameters 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 Reserved1, reserved2 MTP Global ConfigurationMTP Parameters OptionsMTP Signaling Link MTP Link SetSlc LinkidLinkref BlinkNormls MTP RouteDpc Blink Serial PortSecondls UserpartmaskIsup Parameters Global Isup ConfigurationMTP User Part Isup Circuit Group Configuration Opc CicmaskUserinst VariantGlobal configuration parameters for the TUP module Global TUP ConfigurationTUP Parameters TUP Circuit Group Configuration Configuration parameters for a group of TUP circuits107 Ssds Command Line OptionsHost Utilities DescriptionS7mgt Kconfig fileMmodule id 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