Dialogic DSI SPCI Network Interface Boards manual Geographic Addressing, Watchdog Timer

Page 27

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

4.5Geographic Addressing

Geographic Addressing allows the logical position of a board (or board_id) in a system to remain the same irrespective of the addition or removal of other boards on the PCI bus. Two address modes are supported:

•PCI address mode – (default) addressing determined by enumerating boards on the PCI bus at boot time (i.e., the default order found by the operating system).

•Switch address mode - determined by a 16 position ADDR switch on the board.

The configuration of Geographic Addressing is controlled by command line parameters to the ssds utility. See section 8.1 ssds for details.

4.6Watchdog Timer

An optional host to board watchdog timer may be configured. This allows the board to detect a failure of the host software. If such a condition is detected, then the board goes into a reset state. This prevents a condition whereby the software on the host has stopped running but the boards still presents an "in- service" condition to the remote end.

This functionality is controlled by command line parameters to the ssds utility. See section 8.1 ssds for details.

4.7Using the CT bus

The SPCI2S and SPCI4 boards support two or four T1/E1 Line Interface Units and a CT bus interface (H.100) respectively. The on-board signaling processor handles the SS7 signaling timeslots whilst the remaining circuits (voice or data bearer circuits) are passed to the CT bus for distribution to other boards.

All communication between the application and the board is message-based. Initial configuration is usually handled by the configuration utility s7_mgt, which takes commands from the text file (config.txt) and generates all the necessary configuration messages for the board. Subsequent operation is entirely message driven, messages being passed in both directions between the board and the application.

One of the roles of the application is to control the dynamic switching between the CT bus and the T1/E1 line interfaces. This section provides details of how to interface with the CT bus, including the initial (static) configuration and the subsequent (dynamic) switching.

The operation of the CT bus switching interface is described in terms of the SCbus switching model using the messages MVD_SC_DRIVE_LIU, MVD_MSG_SC_LISTEN and MVD_MSG_SC_FIXDATA and config.txt commands LIU_SC_DRIVE and SCBUS_LISTEN.

27

Page 26 Page 28
Image 27
Page 26 Page 28
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 SettingsFiles 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 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 Protocol Configuration using the s7mgt utilityProtocol Configuration Using Individual Messages Page Parameter Description Board Information DiagnosticsBoard Diagnostics Hardware Parameters Parameters are as described belowWatchdog 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 Message Summary MTP Interface MessagesEvent Indication Messages Message Summary Table0x3e18 SSD Reset Request General Configuration MessagesBoard Reset Request NumboardsStatus 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 MessageField Name Meaning Type Mgtmsgrbrdinfo 0x6f0d Src Value Mnemonic MeaningSPCI2S 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 FawRaigen 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 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 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 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 Indication7 MTP2 Q.752 Event Indication Parameter Description Event CodeEvent 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 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 Options MTP Global ConfigurationMTP Parameters Reserved1, reserved2MTP Link Set MTP Signaling LinkBlink LinkidLinkref SlcBlink Serial Port MTP RouteDpc NormlsUserpartmask SecondlsGlobal Isup Configuration Isup ParametersMTP User Part Isup Circuit Group Configuration Variant CicmaskUserinst OpcGlobal TUP Configuration Global configuration parameters for the TUP moduleTUP Parameters Configuration parameters for a group of TUP circuits TUP Circuit Group Configuration107 Description Command Line OptionsHost Utilities SsdsKconfig 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