Dialogic DSI SPCI Network Interface Boards Starting the Windows Device Driver, Name Description

Page 12

3 Installation

Table 4: Files Installed on a System Running Windows®

Name

Description

gctlib.lib

Library to be linked with user's application (Microsoft*).

 

 

gctlibb.lib

Library to be linked with user's application (Borland*).

 

 

INC

Sub-directory containing include files.

 

 

system.txt

Example system configuration file.

 

 

config.txt

Example protocol configuration file.

 

 

gctload.exe

Executables for use as described elsewhere in this

ssds.exe

manual.

s7_mgt.exe

 

s7_log.exe

 

s7_play.exe

 

tick_nt.exe

 

tim_nt.exe

 

servcfg.exe

 

gctserv.exe

 

mtpsl.exe

 

upe.exe

 

 

 

The installation process automatically installs the device driver so the setup program must be allowed to reboot the target machine when it has finished installing the package.

Installation is now complete, although the device driver is not yet running. The files the user needs to use, have been installed in the installation directory. It is recommended that the user does not modify any files in this directory, but instead creates a working directory into which all the necessary files are copied.

If the machine is a development machine without any target boards, then no further installation is required.

3.3.2Starting the Windows® Device Driver

The device driver is initially installed as "Manual", it must therefore be manually started by a user with Administrator privilege using the following procedure:

1)Select the Control Panel (Start Æ Settings Æ Control Panel).

2)Select the "System" icon. In the "system properties" select the "Hardware" tab and then select "Device manager". A tree of device nodes is presented.

3)From the toolbar select "View Æ ShowHiddenDevices": Open the "Non Plug and Play Drivers" device node branch. The "Septel" driver should be displayed. If the board was not present at install of the Development Package the device node may not be visible, this issue can be resolved by starting the driver interface at a command prompt using the command:

12

Page 11 Page 13
Image 12
Page 11 Page 13
Contents Dialogic DSI Spci Network Interface Boards MarchCopyright and Legal Notice Contents Configuration Command Reference Message ReferenceTables Host Utilities 108Revision History Introduction Related DocumentationSpecification Product IdentificationCapability License ButtonsProtocol Dimensioning CapacityInstallation IntroductionHardware configuration Software Installation for WindowsBoard 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 Files Installed on a System Running Linux Device Drivers from Source CodeSoftware Installation for Solaris Installing the Development Package for SolarisVerifying Device Driver Loading An example message isSolaris 10 Additional Commands Non-serviced interrupts reportsFiles Installed on a System Running Solaris Solaris 9 Interface Name CheckingSystem has to be rebooted to force the change to take effect Removing the Development Package for SolarisConfiguration and Operation Typical Telephony Systems ConfigurationsOverview System StructureFollowing abbreviations are used in the table Host Processes and UtilitiesIsdn User Part 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 Protocol Configuration using the s7mgt utilityProtocol Configuration Using Individual Messages Page Board Information Diagnostics Board Diagnostics Hardware ParametersParameters are as described below Parameter DescriptionWatchdog Timer Using the CT busGeographic Addressing Switching Model Static InitializationDynamic Operation Example Code Building and Sending SclistenMSG Page Program Execution Program Execution under WindowsTo 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 General Configuration Messages Message ReferenceHardware Control Messages MTP Interface Messages Event Indication MessagesMessage Summary Table Message Summary0x3e18 General Configuration Messages SSD Reset RequestBoard Reset Request NumboardsStatus Response Parameter Description Boardtype PhyidCodefile RunmodeBoard Status Indication FormatBoard Configuration Request Field Name Meaning Type MGTMSGCONFIG0 0x7F10 SrcDescription Event Type Value MeaningMaxsiflen Isolated from the other boards using the CT bus. The CT bus Parameter DescriptionMessage Reference Bit Data Rate Value Description General Module Identification Message Parameter Description MajrevMajor revision identifier for the object being queried MinrevRead Board Info Request Message TextField Name Meaning Type Mgtmsgrbrdinfo 0x6f0d Src Value Mnemonic MeaningSPCI2S or SPCI4 board Boardrev SwaSwb PrommajrevLIU Configuration Request Field Name Meaning Type Liumsgconfig 0x7e34Hardware Control Messages Dst Mvdtaskid RspreqLiutype LinecodeLine coding technique taken from the following table FrameformatCrcmode BuildoutFaw 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 LIU State Request Offset Size Name StateLIU CT bus Initialization Request Parameter Description StateCurrent state of the LIU from the following table State DescriptionParameter Description Liuid ScchannelTsmask 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 0x7e1fIf a parameter is not required, it must be set to zero LocalstreamLocalslot Sourcestream SourceslotCT bus speed Source Slot Range Deststream DestslotConfigure Clock Request Parameter Description BusspeedField Name Meaning Type Mvdmsgcnfclock 0x7e20 Src Value Clock Mode ClkmodePllclksrc 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 StatusResult of initial configuration coded as follows Clock Event IndicationParameter Description Completion Status Field Name Meaning Type Mvdmsgclkind 0x0e23 SrcParameter Description Event ID LIU Status Indication LiustatusStatus field in the message header is coded as follows 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 State7 MTP2 Q.752 Event Indication Parameter Description Event CodeEvent Code is coded as shown in the following table Excessive delay of acknowledgement Excessive error rate SuermOnset of signaling link congestion Abatement of signaling link congestion8 MTP3 Q.752 Event Indication Offset Size Name Len Event specific parametersValue Mnemonic Paramter Description MtpevajspokConfiguration Command Reference 1 SS7BOARD CommandPhysical 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 MTP Global Configuration MTP ParametersReserved1, reserved2 OptionsMTP Signaling Link MTP Link SetLinkid LinkrefSlc BlinkMTP Route DpcNormls Blink Serial PortSecondls UserpartmaskGlobal Isup Configuration Isup ParametersMTP User Part Isup Circuit Group Configuration Cicmask UserinstOpc VariantGlobal TUP Configuration Global configuration parameters for the TUP moduleTUP Parameters TUP Circuit Group Configuration Configuration parameters for a group of TUP circuits107 Command Line Options Host UtilitiesSsds DescriptionKconfig file S7mgtMmodule 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