Dialogic DSI SPCI Network Interface Boards manual Switching Model, Static Initialization

Page 28

4 Configuration and Operation

4.7.1Switching Model

The basic switching model assumes that at system initialization all incoming T1/E1 timeslots and all resource board output timeslots are connected up to channels on the CT bus and that these connections are never changed. This has the advantage that once the on-board CT bus drivers have been set up they are never changed so the chances of inadvertently causing CT bus conflict is minimized. It also means that the user can predict the exact CT bus channels where any input timeslot can be located and this in turn can assist with fault diagnosis and general system test.

It is also possible to generate fixed patterns on any T1/E1 output timeslots to provide the correct idle pattern for presentation to the network on all circuits where there is no active call.

Having completed the system initialization, all drives to the CT bus are set up. Then, on a dynamic (call by call) basis, the connectivity must be modified when a new call arrives and when it finishes.

When a new call arrives, the application, in general, needs to initiate two listen commands. One command causes the resource to listen to the appropriate CT bus channel to hear the incoming voice path and the other causes the T1/E1 interface to listen to the output from the resource board to generate the outgoing voice path.

When a call clears, the application needs to initiate generation of the fixed idle pattern towards the network operation (and may wish to connect an idle pattern to the resource board).

4.7.2Static Initialization

Static initialization is handled by the s7_mgt utility. For each T1/E1 line interface unit, user must include an LIU_SC_DRIVE command in the config.txt file. The syntax for this command is detailed in appendix A.

The LIU_SC_DRIVE command has several parameters. board_id and

liu_id together uniquely identify the affected line interface unit. sc_channel is the channel number of the first channel on the CT bus that is to be used for timeslots from the specified LIU. ts_mask is a mask identifying which timeslots on the T1/E1 interface are carrying voice circuits (as opposed to signaling) and therefore need to be connected to the CT bus. The least significant bit of ts_mask must always be zero when driving from an T1/E1 interface.

As an example, consider a two board system where the first board has 4 E1 ports and the second board has 4 T1 ports. We allow the first 512 CT bus channels to be used by other boards in the system and therefore start at sc_channel 512.

28

Image 28
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 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 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 using the s7mgt utility Protocol ConfigurationProtocol Configuration Using Individual Messages Page Board Information Diagnostics Board Diagnostics Hardware ParametersParameters are as described below 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 MTP Interface Messages Event Indication MessagesMessage Summary Table Message Summary0x3e18 General Configuration Messages SSD Reset RequestNumboards Board Reset RequestStatus 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 TextValue Mnemonic Meaning Field Name Meaning Type Mgtmsgrbrdinfo 0x6f0d SrcSPCI2S 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 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 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 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 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 StateParameter Description Event Code 7 MTP2 Q.752 Event IndicationEvent 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 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 MTP Global Configuration MTP ParametersReserved1, reserved2 OptionsMTP Signaling Link MTP Link SetLinkid LinkrefSlc BlinkMTP Route DpcNormls Blink Serial PortSecondls UserpartmaskIsup Parameters Global Isup ConfigurationMTP User Part Isup Circuit Group Configuration Cicmask UserinstOpc VariantGlobal configuration parameters for the TUP module Global TUP ConfigurationTUP Parameters TUP Circuit Group Configuration Configuration parameters for a group of TUP circuits107 Command Line Options Host UtilitiesSsds 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.