Dialogic DSI SPCI Network Interface Boards manual Msg

Page 30

4 Configuration and Operation

#include

"pack.h"

/*

Prototypes for rpackbytes */

#include

"ss7_inc.h"

/*

Message & module definitions */

/*

*Macro to generate the value for use in the rsp_req field of the

*message header in order to request a confirmation message:

*/

 

#define RESPONSE(module)

(((unsigned short) 1) << ((module) & 0x0f))

/*

*Function to drive an SCbus / CT bus timeslot

*onto a timeslot on a PCM port:

*/

int listen_to_scbus(board_id, liu_id, timeslot, sc_channel)

int board_id;

/* board_id

(0, 1,

2 ...) */

int liu_id;

/* PCM port

id (*/

 

int timeslot;

/* Timeslot

on the

PCM port (1 .. 31) */

int sc_channel;

/* SCbus / CT bus channel number */

{

 

 

 

 

MSG

*m;

 

 

 

u8

*pptr;

 

 

 

/*

*Allocate a message (and fill in type, id, rsp_req & len):

*/

if ((m = getm(MVD_MSG_SC_LISTEN, 0, RESPONSE(OUR_MOD_ID), MVDML_SCLIS)) != 0)

{

pptr = get_param(m); memset(pptr, 0, m->len);

/*

*Enter the parameters in machine independent format:

*/

rpackbytes(pptr, MVDMO_SCLIS_liu_id, (u32)liu_id, MVDMS_SCLIS_liu_id);

rpackbytes(pptr, MVDMO_SCLIS_timeslot, (u32)timeslot, MVDMS_SCLIS_timeslot);

rpackbytes(pptr, MVDMO_SCLIS_sc_channel, (u32)sc_channel, MVDMS_SCLIS_sc_channel);

m->hdr.dst = MVD_TASK_ID;

30

Page 29 Page 31
Image 30
Page 29 Page 31
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 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 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 Protocol Configuration using the s7mgt utilityProtocol Configuration Using Individual Messages Page Parameters are as described below Board Information DiagnosticsBoard Diagnostics Hardware Parameters 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 Message Summary Table MTP Interface MessagesEvent Indication Messages Message Summary0x3e18 General Configuration Messages SSD Reset RequestBoard Reset Request NumboardsStatus 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 TextField Name Meaning Type Mgtmsgrbrdinfo 0x6f0d Src Value Mnemonic MeaningSPCI2S 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 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 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 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 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 State7 MTP2 Q.752 Event Indication Parameter Description Event CodeEvent 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 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 Reserved1, reserved2 MTP Global ConfigurationMTP Parameters OptionsMTP Signaling Link MTP Link SetSlc LinkidLinkref BlinkNormls MTP RouteDpc Blink Serial PortSecondls UserpartmaskGlobal Isup Configuration Isup ParametersMTP User Part Isup Circuit Group Configuration Opc CicmaskUserinst VariantGlobal TUP Configuration Global configuration parameters for the TUP moduleTUP Parameters TUP Circuit Group Configuration Configuration parameters for a group of TUP circuits107 Ssds Command Line OptionsHost Utilities 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