1. Manuals
  2. Brands
  3. Dialogic Manuals
  4. Network Card
  5. DSI SPCI Network Interface Boards
  6. Programmer's manual

Dialogic DSI SPCI Network Interface Boards Programmer's Manual

Dialogic dsi spci network interface boards programmer's manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
®
Dialogic
DSI SPCI Network Interface Boards
Programmer's Manual
March 2009
U03HSP
www.dialogic.com

Advertisement

Table of Contents
loading

Related Manuals for Dialogic DSI SPCI Network Interface Boards

Summary of Contents for Dialogic DSI SPCI Network Interface Boards

  • Page 1 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual March 2009 U03HSP www.dialogic.com...
  • Page 2 WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.

  • Page 3: Table Of Contents

    Program Execution ... 32 Program Execution under Windows Program Execution under Linux ... 33 Program Execution under Solaris ... 34 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 ® ... 11 ® ... 11 ® Device Driver ... 12 ®...
  • Page 4 Contents Developing a User Application ... 34 Message Reference ... 36 Overview ... 36 6.1.1 General Configuration Messages ... 36 6.1.2 Hardware Control Messages ... 36 6.1.3 MTP Interface Messages ... 37 6.1.4 Event Indication Messages ... 37 6.1.5 Message Summary Table ... 37 General Configuration Messages ...
  • Page 5 Table 8: Typical Telephony Systems Configurations ... 19 Table 9: Host Processes and Utilities ... 20 Table 10: Board Diagnostics – Hardware Parameters ... 26 Table 11: Message Summary ... 37 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 ® ... 12...

  • Page 6: Revision History

    Updated to Dialogic documented new “bundled” license button set and corresponding run modes. 20-Mar-09 Clarification to ISUP-S and TUP-S protocol dimensioning. Note: Current software and documentation supporting Dialogic Interface Boards is available at: http://www.dialogic.com/support/helpweb/signaling Description ® ® 2000, Linux and Solaris added.

  • Page 7: Introduction

    The boards provide a suitable hardware platform for running the Dialogic DSI protocol for realizing Signaling System Number 7 signaling nodes. The boards can be used under any of the following operating systems: Windows 2000, Windows document the term "Windows...

  • Page 8: Specification

    2 Specification Specification Product Identification The product designations are as follows: ® • Dialogic ® • Dialogic and two serial interfaces Throughout this manual the term "SPCI" is used to refer (individually and/or collectively, depending on context) to either or both such type of boards.

  • Page 9: Capacity

    Number of Link Sets Run Mode MTP3 ISUP-S TUP-S ISUP ISUP-L TUP-L ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Monitoring √ √ ISUP, TUP (Small) √ ISUP, TUP (Regular) √ ISUP, TUP (Large) Capacity Maximum Maximum...

  • Page 10: Installation

    The Development Package, Code File and the User Part Development Package may be obtained by downloading it from the Dialogic website at: http://www.dialogic.com/support/helpweb/signaling. They must be copied onto the target host machine maintaining binary file integrity;...

  • Page 11: Hardware Configuration

    The following files (or similar) are transferred to the installation directory. Note that a number of additional files relating to other products in the range are installed at the same time. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Geographic Addressing ® is distributed electronically. The Windows®.

  • Page 12: Starting The Windows

    3 Installation Table 4: Files Installed on a System Running Windows gctlib.lib gctlibb.lib system.txt config.txt gctload.exe ssds.exe 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.

  • Page 13: Clearing Windows 2000 Install Wizard

    5) Reboot the system. The "Install Wizard" window will no longer be presented for the device. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 ® 2000 Install Wizard Settings Control Panel).

  • Page 14: Removing Development Package For Windows

    3 Installation 3.3.4 Removing Development Package for Windows Prior to installing a new version of the Development Package for Windows the previous package must be removed as follows. This procedure requires a user with Administrator privilege. 1) Select the Control Panel (Start 2) Select "Add/Remove Programs".

  • Page 15: Device Drivers From Source Code

    Under some versions of Linux a warning similar to the following is generated: warning: changing search order for system directory. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Description Library to be linked with user's application. Example system configuration file.

  • Page 16: Verifying Device Driver Loading

    The system log is displayed using the command: dmesg | more An example message is: sptpci V1.06 Copyright (C) 2000-2007 Dialogic Corporation. All rights reserved. Using major device number 127. sptpci Device Id 0 @ Bus: 1 Device: 9 Function: 0 Software Installation for Solaris The Development Package for Solaris is distributed electronically.

  • Page 17: Solaris 9 - Interface Name Checking

    The DSI SPCI Board drivers included in this package include an optional work-around to eliminate these problems. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Description Library to be linked with user's application. Sub-directory containing header files for use with user’s application.

  • Page 18: Removing The Development Package For Solaris

    3 Installation To enable this functionality the following line must be added to the /etc/system file: set sptpci:spt_claimint=1 The system has to be rebooted to force the change to take effect. 3.5.5 Removing the Development Package for Solaris The Development Package for Solaris is removed using the package removal utility: pkgrm <dpksol32 / dpksol64>...

  • Page 19: Configuration And Operation

    Table 7: Typical Telephony Systems Configurations Software running on the board Software running on Host Computer Number of boards ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Small System Medium System MTP2 MTP2 MTP3 MTP3 ISUP / TUP...

  • Page 20: Table 9: Host Processes And Utilities

    4 Configuration and Operation The following abbreviations are used in the table: MTP2 Message Transfer Part – Level 2 MTP3 Message Transfer Part – Level 3 ISUP ISDN User Part Telephony User Part In all cases, the process called ssds (SS7 Software Driver) must be run on the host computer.

  • Page 21: System Configuration

    REDIRECT commands to cause messages generated for modules not running locally to be redirected via a module that is running locally. c) FORK_PROCESS commands advising gctload of any processes that need to be started locally. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5...

  • Page 22: Generating A System Configuration File

    4 Configuration and Operation The full syntax of each command is listed in the Software Environment Programmer’s Manual. An example system.txt file is shown below: * Example system.txt for the Development Package for Windows®. * Edit this file to reflect your configuration. * Essential modules running on host: LOCAL LOCAL...
  • Page 23 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 LOCAL 0xcf * s7_mgt - Management/config task LOCAL 0x2d * upe - Example user part task LOCAL 0x3d * s7_log - Prints messages to screen/file After the LOCAL declarations, REDIRECT commands are added for modules that run on the board so that messages destined for these modules are transported via ssds (module_id = 0x20) and the device driver, to the board.

  • Page 24: Protocol Configuration

    4 Configuration and Operation Protocol Configuration The Development Package contains a protocol configuration utility, s7_mgt which performs initialization of all the software modules running on the signaling board. It reads the protocol configuration data from a text file called config.txt and provides a quick and flexible method of configuring the protocol modules without the need to write software for that purpose.
  • Page 25 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 To configure the board using individual messages, the following sequence must be used. (The format of all the messages is described in Section 5 of this manual): 1) Build and send an SSD Reset Message.

  • Page 26: Board Information Diagnostics

    4 Configuration and Operation Board Information Diagnostics To assist in diagnosis of configuration problems and reporting hardware details when encountering problems, a diagnostic display feature is available in s7_mgt. When s7_mgt is run with the –d command line option, a diagnostic display of board hardware parameters is generated in this format following configuration of the board.

  • Page 27: Geographic Addressing

    The operation of the CT bus switching interface is described in terms of the SCbus switching model using the messages MVD_SC_DRIVE_LIU, MVD_MSG_SC_LISTEN and MVD_MSG_SC_FIXDATA and config.txt commands LIU_SC_DRIVE and SCBUS_LISTEN. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 ssds ssds for details. for details.

  • Page 28: Switching Model

    4 Configuration and Operation 4.7.1 Switching 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.

  • Page 29: Dynamic Operation

    #include "libc.h" #include "sysgct.h" ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 * 30 E1 voice ccts on ts 1..15 & * 30 E1 voice ccts on ts 1..15 & * 30 E1 voice ccts on ts 1..15 &...
  • Page 30 4 Configuration and Operation #include "pack.h" #include "ss7_inc.h" * 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) * 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;...
  • Page 31 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 m->hdr.src = OUR_MOD_ID; * Call GCT_set_instance to route the message to the * correct board and GCT_send to send the message. * If GCT_send returns non-zero release the message.

  • Page 32: Program Execution

    5 Program Execution Program Execution This chapter describes how to start the software running. It assumes that the software has already been installed and the configuration files system.txt and config.txt have been modified accordingly. Refer to previous sections if unsure. There are three main stages to get a new application up and running although the procedure may vary slightly depending on the operating system.

  • Page 33: Program Execution Under Linux

    ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Program Execution under Linux Ensure the device driver has been installed and the system configuration file (system.txt) has been modified according to the system requirements to select the correct protocols etc.

  • Page 34: Program Execution Under Solaris

    5 Program Execution Program Execution under Solaris Ensure the device driver has been installed and the system configuration file (system.txt) has been modified according to the system requirements to select the correct protocols etc. Ensure the code file has been copied to the directory containing the SS7 binaries.
  • Page 35 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 gctlib.lib (Windows® using Microsoft compiler) gctlibb.lib (Windows® using Borland compiler) gctlib.lib (Linux) gctlib.lib (Solaris) Some simple example programs are supplied to illustrate the techniques for interfacing to the protocol stack although they are not intended to show a real application.

  • Page 36: Message Reference

    Message Reference Overview This section describes the individual messages that may be sent to and received from the Dialogic messages are sent by the user's application software whilst others are sent by utility programs such as the configuration utility s7_mgt.

  • Page 37: Mtp Interface Messages

    0x3312 0x3680 0x3681 0x3e00 0x3e15 0x3e17 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Description Error Indication MTP2 Level 2 State Indication MTP2 Q.752 Event Indication MTP3 Q.752 Event Indication Board Status Indication LIU Status Indication Clock Event Indication...
  • Page 38 6 Message Reference 0x3e18 0x3e1f 0x3e20 0x3e21 0x3e34 0x3e35 0x3f10 0x5e37 0x5e38 0x5e39 0x6111 0x6f0d 0x7680 0x7681 0x7e00 0x7e15 0x7e17 0x7e18 0x7e1f 0x7e20 0x7e21 0x7e34 0x7e35 0x7f10 0x830a 0x830b Confirmation of MVD_MSG_SC_DRIVE_LIU Confirmation of MVD_MSG_SC_CONNECT Confirmation of MVD_MSG_CNFCLOCK Confirmation of MVD_MSG_CLK_PRI Confirmation of LIU_MSG_CONFIG Confirmation of LIU_MSG_CONTROL Confirmation of MGT_MSG_CONFIG0...

  • Page 39: General Configuration Messages

    Parameter Description: mgmt_id The module_id of the management module, to which ssd sends board status indications. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning SSD_MSG_RESET (0x7680) Sending module's module_id SSD_TASK_ID (0x20) used to request a confirmation...

  • Page 40: Board Reset Request

    6 Message Reference num_boards The maximum number of boards that ssd is required to manage. This must not exceed 16. Status Response The confirmation message (if requested) indicates success by status of zero. On error, the following value can be found in the status message confirmation.
  • Page 41 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Description: This message is used during initialization (or re-configuration) by the application to reset a board and download the code file that contains the operating software for the board.

  • Page 42: Board Status Indication

    6 Message Reference Run Mode Value See section 2.3.2 the DSI SPCI Boards. Status Response The confirmation message (if requested) indicates success by status of zero. No status values indicating errors are defined. 6.2.3 Board Status Indication Synopsis Message sent to the application on completion of the reset and download sequence or on detection of a board status event.

  • Page 43: Board Configuration Request

    Field Name type rsp_req hclass status err_info Offset Size ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MGT_MSG_CONFIG0 (0x7F10) Sending module's module_id MGMT_TASK_ID (0x8e) used to request a confirmation Status Response (if confirmation requested) PARAMETER AREA...
  • Page 44 6 Message Reference Description: This message must be the first message sent to the DSI SPCI Board once the SS7 software is running. It is used to configure all modules on the board for operation. The message contains signaling point codes for this signaling point and the adjacent signaling point(s), flags to permit various level 1, level 2, and level 3 run-time options to be selected and the physical link parameters.
  • Page 45 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 If the board is not licensed to run the requested software configuration, status value of 0xfe is returned. Parameter Description: flags - Global flags Bit 0 is set to 1 to indicate that the user does not wish to use signaling software.
  • Page 46 6 Message Reference Bit 13 is set to 1 to cause the board to drive the CT_NETREF1 clocks on the CT bus. The highest priority in-sync line interface is used as a clock source. If this bit is set to zero then CT_NETREF1 clock is not driven. All other bits are reserved and must be set to zero.
  • Page 47 (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: linkn ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Data Rate 64kbps 56kbps 48kbps Serial Port Cannot be used for a serial port.
  • Page 48 6 Message Reference 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. linkn_slc - Signaling link code The signaling link code for the link, which must be in the range 0 to 15. The signaling link code must be agreed with the administration at the other end of the link and must be unique within a link set.

  • Page 49: General Module Identification Message

    Parameter Description: maj_rev Major revision identifier for the object being queried. min_rev Minor revision identifier for the object being queried. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning GEN_MSG_MOD_IDENT (0x6111) Sending module_id on-board management task (0x8e) used to request a confirmation Status Response –...

  • Page 50: Read Board Info Request Message

    Read Board Info Request Message Synopsis Message used to request basic board information. This message may be sent to several Dialogic ® Dialogic DSI SPCI Network Interface Boards are described below. ® DSI SS7 Boards, but only the parameters relevant to the...
  • Page 51 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Format MESSAGE HEADER Field Name Meaning type MGT_MSG_R_BRDINFO (0x6f0d) Sending module_id MGMT_TASK_ID (0x8e) rsp_req used to request a confirmation hclass status Status Response (if confirmation requested) err_info PARAMETER AREA...
  • Page 52 6 Message Reference board_rev The DSI SPCI Board hardware revision number. The setting of the board's rotary switch labeled "Boot". Note: The switch should be set to 8. Geographic addressing switch setting, that is, the address at which the board appears when the -o3 feature of ssds is used.

  • Page 53: Hardware Control Messages

    Offset Size ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning LIU_MSG_CONFIG (0x7e34) liu_id Sending Module ID MVD_TASK_ID (0x10) used to request a confirmation Status Response (if confirmation requested)0 PARAMETER AREA...
  • Page 54 6 Message Reference Description: This message is sent to the DSI SPCI Board to configure the operating mode a line interface unit. All configuration parameters must be supplied in the message (it is not possible to modify individual operating parameters in isolation).
  • Page 55 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 frame_format E1 double frame (E1 only). E1 CRC4 multiframe (E1 only). D3/D4 (Yellow alarm = bit 2 in each channel) (T1 only). ESF (Yellow alarm in data link channel) (T1 only).
  • Page 56 6 Message Reference rai_gen The (initial) mode used to generate the Remote Alarm Indication (Yellow Alarm) taken from the following table. The user may subsequently modify the setting of the outgoing RAI alarm using the LIU_MSG_CONTROL message. rai_gen clear_mask For use with T1 interfaces and line_code mode 3 (AMI with Zero Code Suppression) to disable zero code suppression on selected channels.

  • Page 57: Liu Control Request

    The confirmation message (if requested) indicates success by status of zero. Parameter Description: ais_gen The mode used to generate the Alarm Indication Signal (Blue Alarm) taken from the following table: ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning LIU_MSG_CONTROL (0x7e35) liu_id Sending Module ID...
  • Page 58 6 Message Reference ais_gen rai_gen The mode used to generate the Remote Alarm Indication (Yellow Alarm) taken from the following table: rai_gen loop_mode The diagnostic loop back mode taken from the following table: loop_mode Status Response The confirmation message (if requested) indicates success by status of zero. On error, the following status values can be found in the confirmation message.

  • Page 59: Liu Read Configuration Request

    The confirmation message (if requested) indicates success by status of zero. On error, the following status value can be found in the confirmation message. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning LIU_MSG_R_CONFIG (0x5e37) liu_id...

  • Page 60: Liu Read Control Request

    6 Message Reference Value 0x01 0x02 0x03 6.3.4 LIU Read Control Request Synopsis: Message sent by the application to read back the current LIU control options from the DSI SPCI Board. Message Format: Field Name type rsp_req hclass status err_info Offset Description: This message is sent to the DSI SPCI Board to read back the current control...

  • Page 61: Liu State Request

    The user should always request a confirmation message. This indicates success by status of zero and contains the current state in the parameter area of the message. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Description Invalid framer ID. Invalid message length.

  • Page 62: Liu Ct Bus Initialization Request

    6 Message Reference Parameter Description: state The current state of the LIU from the following table: State Status Response The confirmation message (if requested) indicates success by status of zero. On error, the following status values can be found in the confirmation message.
  • Page 63 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Message Format: MESSAGE HEADER Field Name Meaning type MVD_MSG_SC_DRIVE_LIU (0x7e18) Sending Module ID MVD_TASK_ID (0x10) rsp_req used to request a confirmation hclass status Status Response (if confirmation requested) err_info...
  • Page 64 6 Message Reference Timeslots containing SS7 signaling processed by the signaling processor on the DSI SPCI Board should not be included in the timeslot mask. Usually, the mask should be set to include all bearer (voice) timeslots but no signaling timeslots.

  • Page 65: Ct Bus Listen Request

    SCBUS_LISTEN command in the config.txt file. However, this only sets up a static configuration and still requires the user application to control any dynamic connections. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MVD_MSG_SC_LISTEN (0x7e17)
  • Page 66 6 Message Reference Parameter Description: liu_id The identifier of the T1/E1 Line Interface Unit in the range 0 to one less than the number of LIUs fitted. This parameter can also be set to the special value 0x83 to select the signaling processor instead of an LIU. In this case, timeslots 0 ...

  • Page 67: Fixed Data Output Request

    The identifier of the T1/E1 Line Interface Unit in the range 0 to one less than the number of LIUs fitted. Note: For the SPCI2S, valid values for the LIU identifiers are 2 and 3. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MVD_MSG_SC_FIXDATA (0x7e15) Sending Module ID...

  • Page 68: Reset Switch Request

    6 Message Reference timeslot The timeslot number on the T1/E1 line interface unit on which the fixed data is transmitted. The valid range for timeslot is 1 to 31 for an E1 interface and 1 to 24 for a T1 interface. pattern The value of the fixed data to be generated.

  • Page 69: 6.3.10 Ct Bus Connect Request

    ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Description: This message is sent to the DSI SPCI Board to reset the state of the digital cross connect switch in accordance with the configuration set using the DSI SPCI Board configuration message.
  • Page 70 6 Message Reference Message Format: Field Name type rsp_req hclass status err_info Offset Description: This message is sent to the DSI SPCI Board to control the CT bus switch. Several different actions can be performed depending on the value of the mode parameter, these are CT bus to local bus connection, local bus to CT bus connection, duplex connection between CT bus, and local bus and duplex connection between local bus timeslots.
  • Page 71 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Mode local st local ts source st If a parameter is not required, it must be set to zero. local_stream The local stream defines which local stream to use for all the modes of operation.
  • Page 72 6 Message Reference mode = 2 : Make a simplex connection from a timeslot on the local bus to a timeslot on the CT bus. Using parameters local_stream, local_slot, dest_stream and dest_slot, to specify the local and CT bus timeslots respectively.
  • Page 73 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 dest_stream The destination stream references which of the CT bus streams is used as a destination for the data. The parameter takes values in the range 0…31. dest_slot The destination slot references the CT bus timeslot to which a local stream timeslot can be connected or disconnected.

  • Page 74: 6.3.11 Configure Clock Request

    6 Message Reference 6.3.11 Configure Clock Request Synopsis: Message sent to a DSI SPCI Board to configure the clocking mode for the board. Message Format: Field Name type rsp_req hclass status err_info Offset Description: This message is used to control the on-board clock circuitry. It allows the user to select the CT bus clocking mode and the reference clock sources for the local and bus reference clocks.
  • Page 75 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Value No change 4.096 MHz (Reserved for future use) 8.192 MHz clk_mode This parameter determines the clocking mode for the DSI SPCI Board, the permissible values are as follows:...
  • Page 76 6 Message Reference The PLL clock is used as the reference when acting as CT bus Primary Master. If the clock is to be recovered from one of the line interfaces then the highest-priority in sync line interface is used as the reference. Each line interface is assigned a priority: by default liu_id=0 is the highest priority and liu_id=7 the lowest.

  • Page 77: 6.3.12 Configure Clock Priority Request

    If no interfaces are in sync, the board remains in "holdover" mode, based on the last valid clock that was recovered. The confirmation message (if requested) indicates success by status of zero. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MVD_MSG_CLOCK_PRI (0x7e21)
  • Page 78 6 Message Reference Parameter Description: liun_pri The relative priority for each LIU using the values taken from the following table: Value 1 … 32 Status Response The confirmation message (if requested) indicates success by status of zero. On error, the following status value can be found in the confirmation message.

  • Page 79: Event Indication Messages

    Description: This message is used to convey the status of a board reset operation (whether success of failure) to the user. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning SSD_MSG_STATE_IND (0x06a0) board_id SSD_TASK_ID (0x20)

  • Page 80: S7_Mgt Completion Status Indication

    6 Message Reference Parameter Description: Board Status Value Mnemonic 0x60 SSDSI_RESET 0x62 SSDSI_FAILURE 0x64 SSDSI_BRD_RMVD 0x65 SSDSI_BRD_INS 0x66 SSDSI_LIC_FAIL 0x67 SSDSI_LIC_CRP 0x70 SSDSI_BCONG_CLR 0x71 SSDSI_BCONG_ON 0x72 SSDSI_DIS_CLR 0x73 SSDSI_DIS_ON 0x74 SSDSI_FAIL 6.4.2 s7_mgt Completion Status Indication Synopsis: Message issued by s7_mgt on completion of initial configuration sequence. Message Format: Field Name type...

  • Page 81: Clock Event Indication

    Message issued by the board to indicate on-board clocking related events. Message Format: Field Name type rsp_req hclass status err_info ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Meaning MESSAGE HEADER Meaning MVD_MSG_CLK_IND (0x0e23) MVD_TASK_ID 0xdf Event ID (see below) Reserved for future use...
  • Page 82 6 Message Reference Description: This message is issued by the board to indicate events within the on-board clocking circuitry. Parameter Description: Event ID This field specifies the event that caused the indication to be generated: event_id Description PLL entered hold-over mode Issued by boards acting as primary or secondary clock master when its nominated clock reference becomes unavailable.

  • Page 83: Liu Status Indication

    The identity of the Line Interface Unit to which the status indication applies. liu_status The status field in the message header is coded as follows: ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MVD_MSG_LIU_STATUS (0x0e01)

  • Page 84: Error Indication

    6 Message Reference Value Mnemonic LIUS_SYNC_LOSS LIUS_IN_SYNC LIUS_AIS LIUS_AIS_CLRD LIUS_REM_ALARM LIUS_REM_ALM_CLRD LIUS_PCM_LOSS LIUS_PCM_OK LIUS_FRAME_SLIP LIUS_BER5_OCRD LIUS_BER5_CLRD LIUS_BER3_OCRD LIUS_BER3_CLRD 6.4.5 Error Indication Synopsis: Message issued to management to advise of errors or unexpected events occurring within the protocol software. Message Format: Field Name type rsp_req...

  • Page 85: Error Code

    ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Parameter Description: Error Code The Error Code is coded as shown in the following table: Value Mnemonic 0x31 S7E_RESET_ERR 0x33 S7E_POOL_EMPTY 0x34 S7E_TX_FAIL 0x35 S7E_HDR_ERR 0x36 S7E_LEN_ERR 0x37 S7E_MSU_SEND...

  • Page 86: Mtp2 Level 2 State Indication

    6 Message Reference 6.4.6 MTP2 Level 2 State Indication Synopsis: Indication issued by the board every time the level 2 link state control state machine changes state. Message Format: Field Name type rsp_req hclass status err_info Description: This message is issued by the MTP2 module every time a change of state takes place at level 2.

  • Page 87: Mtp2 Q.752 Event Indication

    • a proving failure (prefixed S7P_). Parameter Description: Event Code The Event Code is coded as shown in the following table: ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MGT_MSG_SS7_EVENT (0x0202) l2_llid MTP2 module id...
  • Page 88 6 Message Reference Value Mnemonic S7F_STOP Stop request received S7F_FIBR_BSNR Abnormal FIBR/BSNR S7F_EDA Excessive delay of acknowledgement S7F_SUERM Excessive error rate (SUERM) S7F_ECONG Excessive congestion S7F_SIO_RXD Unexpected SIO received S7F_SIN_RXD Unexpected SIN received S7F_SIE_RXD Unexpected SIE received S7F_SIOS_RXD SIOS received S7G_CONG Onset of signaling link congestion S7G_CONG_CLR...

  • Page 89: Mtp3 Q.752 Event Indication

    • linkset is indicated as linkset_id, (size = 1). • point code is a 4 byte value, (size = 4). ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 MESSAGE HEADER Meaning MGT_MSG_MTP_EVENT (0x0301) MTP3 module id Management module id...
  • Page 90 6 Message Reference Value MTPEV_CO MTPEV_CB MTPEV_REST MTPEV_RPO MTPEV_RPO_CLR MTPEV_CONG MTPEV_CONG_CLR MTPEV_CONG_DIS MTPEV_LS_LOST MTPEV_LS_OK MTPEV_DEST_LOST MTPEV_DEST_OK MTPEV_AJSP_LOST MTPEV_AJSP_OK Mnemonic Paramter link Changeover link Changeback link Restoration commenced link Remote processor outage link Remote processor outage cleared link Signaling link congestion link Congestion cleared link...

  • Page 91: Configuration Command Reference

    Bit 6 and 7 together select the initial clocking mode for the CT bus as shown in the following table. The clocking mode can subsequently modified dynamically using the MVD_MSG_CNFCLOCK message: ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 SS7_BOARD <board_id> <board_type> <flags> <code_file> <run_mode> SS7_BOARD 0 SPCI4 0x0043 ss7.dc3 ISUP-L ®...
  • Page 92 CT bus. Initially the board recovers from clock set A, though will switch over automatically to recover from clock set B if set A fails. ® DSI SPCI Network Interface Boards all use the...

  • Page 93: Liu_Config Command

    ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Protocols selected to Run on the Board for details of the capacity for modules running on...
  • Page 94 7 CONFIGURATION COMMAND Reference liu_type <line_code> The line coding technique taken from the following table: line_code <frame_format> The frame format taken from the following table: frame_format <crc_mode> The CRC mode taken from the following table: crc_mode Description Disabled (used to deactivate a LIU). In this mode the LIU does not produce an output signal.

  • Page 95: Liu_Sc_Drive Command

    30 timeslots used for voice circuits, ts_mask should be set to the value 0xfffefffe. For a T1 interface with signaling on timeslot 24, ts_mask should be set to the value 0x00fffffe. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5...

  • Page 96: Scbus_Listen Command

    7 CONFIGURATION COMMAND Reference <mode> This parameter allows the user to select how the CT bus channels are allocated. Usually (mode=1) the first timeslot connected to the CT bus is connected to sc_channel and each subsequent timeslot that is selected is connected to the next CT bus channel.

  • Page 97: Mtp Parameters

    RPO the signaling link is taken out of service and restoration commenced. This bit is usually set to 1. Bit 20 used in conjunction with bit 9 to select point codes (see above). ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Bit 20 Point Code 14-bit 16-bit...

  • Page 98: Mtp Link Set

    7 CONFIGURATION COMMAND Reference Bit 21 is set to 1 for use in Japanese networks; otherwise it must be set to zero. All other bits are reserved for future use and must be set to zero. Note: For ANSI operation bits 8, 9, 10, 11, and 18 must all be set to 1. 7.2.2 MTP Link Set Syntax:...
  • Page 99 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 <link_id> The link’s unique logical link identity. It must be in the range 0 to one less than the total number of signaling links supported. <linkset_id> The logical identity of the link set to which the link belongs. The linkset must already have been configured using the MTP_LINKSET command.

  • Page 100: Mtp Route

    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.
  • Page 101 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 a) The only link set used to reach the destination. b) The preferred link set used to reach the destination. c) One of a pair of links sets forming a combined link set.

  • Page 102: Mtp User Part

    7 CONFIGURATION COMMAND Reference 7.2.5 MTP User Part Syntax: Example: Configuration of a local user part module (other than a user part which has its own config command in config.txt). <si> The service indicator. <module_id> The module id of the user process. Note: This command must not be used when the corresponding configuration commands are used (ISUP_CONFIG, TUP_CONFIG etc) as these commands automatically...

  • Page 103: Isup Circuit Group Configuration

    <base_cid> The logical id for the first circuit in the circuit group. It must lie in the range 0 to one less than the number of circuits supported. ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5...
  • Page 104 7 CONFIGURATION COMMAND Reference <cic_mask> A 32 bit mask with bits set to indicate which circuits are to be allocated to the circuit group. Bit zero must always be set as it represents the base_cic/base_cid. Subsequent bits represent the subsequent circuits. Note that ANSI circuit groups are not permitted to contain more than 24 circuits.

  • Page 105: Tup Parameters

    Optional parameter for use when operating in dual resilient configuration. This parameter is the module_id of the "partner" TUP module (equivalent to the "ucic_id" field in the TUP Configure Request message as documented in the TUP Programmer’s Manual). ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5...

  • Page 106: Tup Circuit Group Configuration

    7 CONFIGURATION COMMAND Reference 7.4.2 TUP Circuit Group Configuration Syntax: Example: The configuration parameters for a group of TUP circuits. <gid > The group id of the circuit group in the range 0 to one less than the number of groups supported. <dpc>...
  • Page 107 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 <ssf> The value to be used in the sub-service field of all TUP messages for this circuit group. <variant> This field is reserved for future use and must be set to zero.

  • Page 108: Host Utilities

    Host Utilities This section describes some of the utilities that can be used with the ® Dialogic DSI SPCI Network Interface Boards. See the software environment Programmer's Manual for details of the gctload, tim, tick, s7_log and s7_play utilities. ssds 8.1.1...

  • Page 109: S7_Mgt

    ID of 0xcf. The module ID assigned must have a corresponding LOCAL entry in the system.txt file and must not be in use by any other process on the host. ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5 Protocol Configuration Using for more information.

  • Page 110: Example

    8 Host Utilities -i<notify module id> The module to which an indication is sent when the configuration is complete. Enable diagnostic tracing. 8.2.4 Example To run the s7_mgt utility as module ID 0xdf with the file my_config.txt as its configuration file and notifying the module 0xef on completion, the command s7_mgt -m0xdf -kmy_config.txt -i0xef...
  • Page 111 ® Dialogic DSI SPCI Network Interface Boards Programmer's Manual Issue 5...

Table of Contents