..

Problem starting septel service (SS7HDP board)

..

Developer Group

Developer Group
Connect with thousands of other developers to brainstorm ideas, share best practices and tips - or just chat about the latest emerging technologies making noise in the field. And of course, get the most up-to-date service and support news from Dialogic.
Dialogic SS7 and SIGTRAN Signalling

Problem starting septel service (SS7HDP board)

  • Hi everyone!

    My name is André and i am having some problems with my ss7hdp driver.

    I have about 10 ss7hdp boards over my clients but i have 2 boards that i cant start my septel service.

    Looking on the web, i found this http://www.ivrsworld.com/ivr-tips/step-by-step-instruction-to-install-dialogic-spci4spci2-boards/ who says that my issue can be caused by the verion of dpkwin.exe.

    I tried to find so hard olders versions of this software but i only found 3 (4.02, 5.03 and the newest 6.42) but with all i have the same problem "cant find service name" after starting the septel service.

    Does everyone know how to fix by other way or have another version of dpkwin?

    If it helps, this boards are from 2006 (cant get any support anymore =(  ).

    Tnks

  • can you share the output of gctload -d while s7_mgt has also the -d option in the system.txt?

  • Sorry i am new on this configuration.

    You wanted me to configure my system.txt  with this line:

     

    FORK_PROCESS s7_mgt.exe -d

     

    and output this comand:

     

    C:\Septel>gctload -d

    Reading from system configuration file: 'system.txt'

    Created LOCAL module Id 0x20

    Created LOCAL module Id 0x0

    Created LOCAL module Id 0xcf

    Created LOCAL module Id 0xef

    Created LOCAL module Id 0x2d

    Redirect module Id 0x71 to module Id 0x20

    Redirect module Id 0x10 to module Id 0x20

    Redirect module Id 0x8e to module Id 0x20

    Redirect module Id 0x22 to module Id 0x20

    Redirect module Id 0xdf to module Id 0xef

    (784)gctload: Process (688)'tim_nt.exe' - forked by gctload

    (784)gctload: Process (756)'tick_nt.exe' - forked by gctload

    (784)gctload: Process (1816)'s7_mgt.exe' - forked by gctload

    (784)gctload: Process (1804)'s7_log.exe' - forked by gctload

    (784)gctload: Process (1796)'upe.exe' - forked by gctload

    (784)gctload: Initialisation complete

    S7_MGT Tx: M-I0000-t7300-i0000-fcf-d22-s00

    UPE: User Part Example. Copyright (C) 1995-2003 Intel Corporation

    =================================================================

    14 bit point code selected.


    Requires the following entry in config.txt:

    MTP_USER_PART 0x0a 0x2d



    S7_log : mod ID=0xef, options=0xaf0d

    S7_MGT: Timer expired during startup

     

     

    Is that correct?

     

  • you have something wrong in your system file.

    it doesn't look like the s7_mgt is forked at all.

    post your system and config files.

  • #### config.txt  ######

    ********************************************************************************

    *

    * Example Protocol Configuration File (config.txt) for use with

    * Intel(R) NetStructure(TM) SS7 Boards.

    *

    * Boards supported are PCCS6, SPCI4, SPC2S, CPM8 and the SS7HD range.

    * (note, not all boards are supported on all operating system).

    *

    * This file needs to be modified to suit individual circumstances.

    * Refer to the relevant Programmer's Manuals for further details.

    *

    ********************************************************************************

    *

    *

    * Configure individual boards:

    * For PCCS6 boards:

    * PCCS6_BOARD <port_id> <board_id> <num_pcm> <flags> <code_file>

    *PCCS6_BOARD  0  0  0  0x0043  mtp76.dc2

    *

    * For SPCI4 / SPCI2S boards:

    * SEPTELPCI_BOARD <board_id> <flags> <code_file> <run_mode>

    *SEPTELPCI_BOARD  0  0x0043  ss7.dc3 MTP

    *

    * For CPM8 boards:

    * SEPTELCP_BOARD <board_id> <flags> <code_file> <run_mode>

    *SEPTELCP_BOARD   0  0x0043  ss7.dc3 MTP

    *

    * For SS7HD PCI boards:

    * SS7_BOARD <board_id> <board_type> <flags> <code_file> <run_mode>

    *SS7_BOARD  0 SS7HDP 0x0043  ss7.dc4  MTP2

    *

    * For SS7HD cP boards:

    * SS7_BOARD <board_id> <board_type> <flags> <code_file> <run_mode>

    *SS7_BOARD  0 SS7HDC 0x0043  ss7.dc4  MTP2

    *

    *

    * Configure individual E1/T1 interfaces:

    * LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format>

    *            <crc_mode>

    LIU_CONFIG  0  0  5  1  1  1

    *

    *

    * MTP parameters:

    *

    * MTP_CONFIG <reserved> <reserved> <options>

    MTP_CONFIG  0  0  0x00000000

    *

    * Define linksets:

    * MTP_LINKSET <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>

    MTP_LINKSET  0  1  2  0x0000  2  0x08

    *

    * Define signaling links:

    * MTP_LINK <link_id> <linkset_id> <link_ref> <slc> <board_id> <blink>

    *          <stream> <timeslot> <flags>

    * Note 1: For PCCS6 boards the first LIU port is stream=16 whilst for other

    * boards the first LIU port is stream=0.

    * Note 2: The SS7HD board requires a compound parameter for blink of the form

    * sp_id-sp_channel.

    *

    * For PCCS6 boards:

    *MTP_LINK  0  0  0  0  0  0    16  16  0x0006

    * For SPCI4 / SPCI2S / CPM8 boards:

    *MTP_LINK  0  0  0  0  0  0    0   16  0x0006

    * For SS7HD boards:

    *MTP_LINK  0  0  0  0  0  0-0  0   16  0x0006

    *

    * Define a route for each remote signaling point:

    * MTP_ROUTE <dpc> <linkset_id> <user_part_mask>

    MTP_ROUTE  1  0  0x0020

    *

    * Define any user provided Layer 4 protocol:

    * MTP_USER_PART <service_ind> <module_id>

    *MTP_USER_PART  0x0a  0x2d

    *

    *

    * ISUP parameters:

    *

    * Configure ISUP module:

    * ISUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts>

    *ISUP_CONFIG  0  0  0x1d  0x0435  4  64

    *

    * Configure ISUP circuit groups:

    * ISUP_CFG_CCTGRP <gid> <dpc> <base_cic> <base_cid> <cic_mask> <options>

    *                       <user_inst> <user_id> <opc> <ssf> <variant> <options2>

    *ISUP_CFG_CCTGRP  0  1  0x01  0x01  0x7fff7fff  0x001c  0  0x1d  2  0x8  0  0x00

    *

    *

    *  TUP parameters:

    * Configure TUP module:

    * TUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts>

    *TUP_CONFIG  0  0  0x1d  0x8141  4  64

    *

    * Define TUP circuit groups:

    * TUP_CFG_CCTGRP <gid> <dpc> <base_cic> <base_cid> <cic_mask> <options>

    *                      <user_inst> <user_id> <opc> <ssf>

    *TUP_CFG_CCTGRP  0  1  0x01  0x01  0x7fff7fff  0x0030  0  0x1d  2  0x08

    *

    ********************************************************************************

    ####   system.txt  ########### ******************************************************************** * * Example System Configuration File (system.txt) for use with the  * Windows Development Package for Intel(R) NetStructure(TM) SS7 Boards * * Edit this file to reflect your configuration. * ******************************************************************** * * Essential modules running on host: * LOCAL           0x20            * ssd/ssds/ssdh - Board interface task LOCAL 0x00 * tim_nt - Timer task * * Optional modules running on the host: * LOCAL 0xcf * s7_mgt - Management/config task LOCAL           0xef            * s7_log - Display and logging utility   LOCAL 0x2d * upe - Example user part task * * Modules that optionally run on the host * *LOCAL 0x23 * ISUP module *LOCAL 0x4a * TUP module *LOCAL 0x33 * SCCP module *LOCAL 0x14 * TCAP module *LOCAL 0x22 * MTP3 module * * Essential modules running on the board (all redirected via ssd): * REDIRECT 0x71 0x20 * MTP2 module (except SS7HD boards) * REDIRECT      0x81    0x20    * MTP2 module_id for SP 0 (SS7HD boards only) * REDIRECT      0x91    0x20    * MTP2 module_id for SP 1 (SS7HD boards only) * REDIRECT      0xe1    0x20    * MTP2 module_id for SP 2 (SS7HD boards only) * REDIRECT      0xf1    0x20    * MTP2 module_id for SP 3 (SS7HD boards only) REDIRECT        0x10    0x20    * CT bus/Clocking control module REDIRECT 0x8e 0x20 * On-board management module * * Modules that optionally run on the board (all redirected via ssd): * * REDIRECT 0x23 0x20 * ISUP module * REDIRECT 0x4a 0x20 * TUP module * REDIRECT 0x33 0x20 * SCCP module * REDIRECT 0x14 0x20 * TCAP module REDIRECT 0x22 0x20 * MTP3 module * * Redirection of status indications: * REDIRECT 0xdf 0xef * LIU/MTP2 status messages -> s7_log * * Now start-up all local tasks: *   (For PCCS6 start-up use ssd.exe and ssd_poll.exe, *   for SPCI4/SPCI2S/CPM8 start-up use ssds.exe and *   for SS7HD boards use ssdh.exe) * * FORK_PROCESS ssd.exe * FORK_PROCESS ssd_poll.exe * FORK_PROCESS ssds.exe * FORK_PROCESS ssdh.exe FORK_PROCESS tim_nt.exe FORK_PROCESS tick_nt.exe FORK_PROCESS s7_mgt.exe -d FORK_PROCESS s7_log.exe FORK_PROCESS upe.exe * * ********************************************************************************
  • at a first view the board configuration is commented in the config.txt

     

  • I uncomented that line and now i got this:

     

     

    C:\Septel>gctload -d

    Reading from system configuration file: 'system.txt'

    Created LOCAL module Id 0x20

    Created LOCAL module Id 0x0

    Created LOCAL module Id 0xcf

    Created LOCAL module Id 0xef

    Created LOCAL module Id 0x2d

    Redirect module Id 0x71 to module Id 0x20

    Redirect module Id 0x10 to module Id 0x20

    Redirect module Id 0x8e to module Id 0x20

    Redirect module Id 0x22 to module Id 0x20

    Redirect module Id 0xdf to module Id 0xef

    (356)gctload: Process (752)'ssdh.exe' - forked by gctload

    (356)gctload: Process (1776)'tim_nt.exe' - forked by gctload

    (356)gctload: Process (2028)'tick_nt.exe' - forked by gctload

    (356)gctload: Process (1668)'s7_mgt.exe' - forked by gctload

    (356)gctload: Process (836)'s7_log.exe' - forked by gctload

    (356)gctload: Process (1392)'upe.exe' - forked by gctload

    (356)gctload: Initialisation complete


    S7_log : mod ID=0xef, options=0xaf0d

    S7_MGT Tx: M-I0000-t7680-i0000-fcf-UPE: User Part Example. Copyright (C) 1995-20

    03 Intel Corporation

    d20-=================================================================

    s0014 bit point code selected.


    Requires the following entry in config.txt:

    -p(24)MTP_USER_PART 0x0a 0x2d


    200000cf70637337332e6463310000000000000000000010

    S7_MGT Rx: M-I0000-t3680-i0000-f20-dcf-s00-p(24)200000cf70637337332e646331000000

    0000000000000010

    S7_MGT Tx: M-I0000-t7681-i0000-fcf-d20-s00-p(26)0003000000007373372e646334000000

    00000000000000000002

    S7_MGT Rx: M-I0000-t3681-i0000-f20-dcf-s02-p(26)0003000000007373372e646334000000

    00000000000000000002

    S7_MGT: Timer expired during startup