Dialogic DSI SPCI Network Interface Boards manual MTP Route, Dpc, Normls, Blink Serial Port

Page 100

7 CONFIGURATION COMMAND Reference

Bit 2 is set to 1 to cause a signaling link test (in accordance with ITU-T Q.707

/ANSI T1.111.7) to be carried out every 30 seconds. Note that this bit is ignored unless bit 1 is also set to 1.

Bit 8 is used to select the MTP2 error correction mode. It is set to 1 to select PCR (Preventive Cyclic Retransmission) operation or zero for the Basic Method of Error Correction.

Bit 11 is set to 1 to select 56kbit/s operation for the link or zero for 64kbit/s operation.

Note: When using a serial port, 56kbit/s operation is only supported when the clock is applied externally.

Bit 13 is only used when the link has been configured to run over a serial port. If set to 1 an external clock is used (Receive clock). If set to zero an internal clock (Transmit clock) is used. If the link has not been configured to run over a serial port, this bit must be set to zero.

Bit 14 is set to 1 to use a serial port rather than a PCM timeslot for this link. In this mode the stream and timeslot parameters for this link are ignored (and must be set to zero). If this bit is set to zero, the link uses the specified stream and timeslot. The serial port used by the signaling processors for each link is fixed, according to the following table:

Blink

Serial Port

0

B

 

 

1

A

 

 

2

Cannot be used for a serial port.

 

 

3

Cannot be used for a serial port.

 

 

Bit 15 is set to 1 to disable the link or zero to enable the link.

All other bits are reserved for future use and must be set to zero.

7.2.4MTP Route

Syntax:

MTP_ROUTE <dpc> <norm_ls> <user_part_mask>

 

<flags> <second_ls>

Example:

MTP_ROUTE 567 0 0x0020 0x0000 0

Configuration of a route for use with one or more user parts.

<dpc>

The point code of the remote signaling point for which this command is configuring routing data. It may be either an adjacent point code or a point code accessible via an adjacent Signaling Transfer Point.

<norm_ls>

The linkset_id of the normal link set used to reach the specified destination. The norm_ls must be a linkset_id that has already been configured using the MTP_LINKSET command. The normal link set may be any of the following:

100

Image 100 Dialogic DSI SPCI Network Interface Boards manual MTP Route, Dpc, Normls, Blink Serial Port
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.