Dialogic DSI SPCI Network Interface Boards manual Solaris 9 Interface Name Checking

Page 17

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

On successful completion of the installation procedure, the following message is displayed, and the user needs to reboot the system.

Installation of DKseptel was successful.

The following files (or similar) are transferred into the /opt/DKseptel directory.

Note: Additional files relating to other products in the range are installed at the same time.

Table 6: Files Installed on a System Running Solaris

Name

Description

libgctlib.so

Library to be linked with user's application.

libgctlib.so.1

 

libgctlib.so.1.0.1

 

 

 

INC

Sub-directory containing header files for use with user’s application.

 

 

system.txt

Example system configuration file.

 

 

config.txt

Example protocol configuration file.

 

 

gctload.exe

Executables for use as described elsewhere in this manual.

ssds.exe

 

tick_sol.exe

 

tim_sol.exe

 

s7_mgt.exe

 

s7_log.exe

 

upe.exe

 

 

 

3.5.2Solaris 9 - Interface Name Checking

To use the package under Solaris 9, interface name checking must be disabled. This is done by adding the following line to the /etc/system file:

set sunddi_netifname_constraints=0

The driver will not start properly if this line is not added.

3.5.3Solaris 10 - Additional Commands

Customers using Solaris 10 must perform the following additional commands after installing the package:

cd/opt/DKseptel chown root ssdh chmod +s ssdh

Note: The commands should be executed by a user with super-user permissions.

3.5.4Non-serviced interrupts reports

Some systems exhibit problems due to non-serviced interrupts being reported by the system. The problem can result in large numbers of event reports that can impact the system performance.

The DSI SPCI Board drivers included in this package include an optional work-around to eliminate these problems.

17

Page 16 Page 18
Image 17
Page 16 Page 18
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 WindowsName Description Files Installed on a System Running WindowsStarting the Windows Device Driver Clearing Windows 2000 Install Wizard Removing Development Package for Windows Software Installation for LinuxInstalling Development Package for Linux 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 Individual Messages Protocol ConfigurationProtocol Configuration using the s7mgt utility Page Board Diagnostics Hardware Parameters Board Information DiagnosticsParameters are as described below Parameter DescriptionGeographic Addressing Watchdog TimerUsing the CT bus Static Initialization Switching ModelExample Code Building and Sending Sclisten Dynamic OperationMSG Page To run the system within the current console, enter Program ExecutionProgram Execution under Windows To run it in the background enter Program Execution under LinuxDeveloping a User Application Program Execution under SolarisNmake /f ctu.mnt Hardware Control Messages General Configuration MessagesMessage Reference Event Indication Messages MTP Interface MessagesMessage Summary Table Message Summary0x3e18 SSD Reset Request General Configuration MessagesStatus Response Board Reset RequestNumboards 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 MessageSPCI2S or SPCI4 board Field Name Meaning Type Mgtmsgrbrdinfo 0x6f0d SrcValue Mnemonic Meaning 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 Description RaigenClearmask Field Name Meaning Type Liumsgcontrol 0x7e35 LIU Control RequestParameter Description Aisgen Loopmode Description Diagnostic loop back mode taken from the following tableLoopmode 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 MeaningLocalslot If a parameter is not required, it must be set to zeroLocalstream CT bus speed Source Slot Range SourcestreamSourceslot Destslot DeststreamField Name Meaning Type Mvdmsgcnfclock 0x7e20 Src Configure Clock RequestParameter Description Busspeed 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 IndicationEvent Code is coded as shown in the following table 7 MTP2 Q.752 Event IndicationParameter Description Event Code 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 DescriptionPhysical Interface Parameters Configuration Command Reference1 SS7BOARD Command 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 SecondlsMTP User Part Global Isup ConfigurationIsup Parameters Isup Circuit Group Configuration Userinst CicmaskOpc VariantTUP Parameters Global TUP ConfigurationGlobal configuration parameters for the TUP module Configuration parameters for a group of TUP circuits TUP Circuit Group Configuration107 Host Utilities Command Line OptionsSsds DescriptionMmodule id Kconfig fileS7mgt 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