..

Problem in running the septel card in monitoring mode

..

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 in running the septel card in monitoring mode

  • Hi,

    I have a septel SPCI card. I want to run the card in monitoring mode.

    I have made the required changes in config.tx.

    When I select the <runmode> mon it gives the following error when I run gctload –d

     

    SEPTELCP_BOARD: Unexpected runmode MON

     

    When I select the <runmode> mtp it works fine.

     

    Kindly tell why it is giving the following error.

     

    Here is the complete output of gctload -d

     

    D:\septel>gctload -d

    Reading from system configuration file: 'system.txt'

    Created LOCAL module Id 0x20

    Created LOCAL module Id 0x0

    Created LOCAL module Id 0xef

    Created LOCAL module Id 0xcf

    Created LOCAL module Id 0x4d

    Created LOCAL module Id 0x5d

    Created LOCAL module Id 0x23

    Redirect module Id 0x22 to module Id 0x20

    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 0xdf to module Id 0xef

    (2604)gctload: Process (1004)'ssds.exe' - forked by gctload

    (2604)gctload: Process (2464)'tim_nt.exe' - forked by gctload

    (2604)gctload: Process (2268)'tick_nt.exe' - forked by gctload

    (2604)gctload: Process (1016)'s7_mgt.exe' - forked by gctload

    (2604)gctload: Process (2524)'s7_log.exe' - forked by gctload

    (2604)gctload: Process (2632)'isp_nt.exe' - forked by gctload

    (2604)gctload: Initialisation complete

     

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

    S7_log : Writing log file log.txt

    SEPTELCP_BOARD: Unexpected runmode MON

    Parse error(s) in config.txt

  • **************** Config.txt *************************

    *
    * Configure individual boards:
    * For Septel cP / PCI boards:
    * SEPTELCP_BOARD <board_id> <flags> <code_file>
    *SEPTELCP_BOARD  0  0x0043  ss7.dc3
    SEPTELPCI_BOARD  0  0x0001  MONITOR.dc3 mon

    * Send Monitor messages to s7_log module

    MONITOR_LINK 0 0 0 0 1 0xef 0 0 0x00

    *
    *
    * 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  0  0
    *LIU_CONFIG  0  1  5  1  1  1
    *
    *LIU_SC_DRIVE 0  0  512  0xfffefffe
    *LIU_SC_DRIVE 0  1  552  0xfffefffe
    *
    * MTP Parameters:
    * MTP_CONFIG <reserved> <reserved> <options>
    MTP_CONFIG  0 0  0x0000
    *
    * Define linksets:
    * MTP_LINKSET <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>
    MTP_LINKSET  0  1591 1  0x0000 9865 0x08
    *
    * Define signaling links:
    * MTP_LINK <link_id> <linkset_id> <link_ref> <slc> <board_id> <blink> <stream> <timeslot> <flags>
    * (Note: For Septel ISA (PCCS6) boards the first LIU port is stream=16
    * whilst for Septel cP / PCI boards the first LIU port is stream=0)
    MTP_LINK  0  0  0  0  0  0  0  16  0x0006
    *MTP_LINK  0  0  0  0  0  0  0x83  16  0x0006
    *
    * Define a route for each remote signaling point:
    * MTP_ROUTE <dpc> <linkset_id> <user_part_mask>
    MTP_ROUTE  1591 0  0x0020
    *
    * Define any user provided Layer 4 protocol:
    * MTP_USER_PART <service_ind> <module_id>
    * MTP_USER_PART  0x03  0x23
    *
    *
    * Configure ISUP module:
    *ISUP_CONFIG <res1> <res2> <user_id> <options> <num_grps> <num_ccts>
    *ISUP_CONFIG  0  0  0x2d  0x0435  1  32
    ISUP_CONFIG  0  0  0x4d  0x0474  1  32
    *[dkB1]
    ISUP_CFG_CCTGRP 0 1591 0x01 0x01 0x7fff7fff 0x001c 0 0x4d 9865 0x8 0 0x00
    *
    ISUP_TRACE 0xffffffff 0xffffffff 0xffffffff
    *

     

    ********************* System.txt *****************************

    *
    * Essential modules running on host:
    *
    LOCAL  0x20  * ssd/ssds - Board interface task
    LOCAL  0x00  * tim_nt - Timer task
    LOCAL  0xef  * s7_log - SS7 message display task
    *
    * Optional modules running on the host:
    *
    LOCAL  0xcf  * s7_mgt - Management/config task
    LOCAL  0x4d  * Dialogic SS7 services
    LOCAL   0x3d   * upe - Example user part task
    LOCAL   0x5d   * upe - Example user part task
    *LOCAL   0x6d   * upe - Example user part task
    LOCAL   0x23  * ISUP

    *
    * Modules running on the board (all redirected via ssd):
    *
    REDIRECT 0x22 0x20 * MTP3 module
    REDIRECT 0x71 0x20 * MTP2 module
    REDIRECT 0x10 0x20 * CT bus/Clocking control module
    REDIRECT 0x8e 0x20 * On-board management module
    *
    * Redirection of status indications:
    *
    REDIRECT 0xdf 0xef * LIU/MTP2 status messages -> s7_log
    *REDIRECT 0xef 0x2d * Other indications -> upe

    FORK_PROCESS    ssds.exe -d
    FORK_PROCESS    tim_nt.exe
    FORK_PROCESS    tick_nt.exe
    FORK_PROCESS    s7_mgt.exe -d
    *FORK_PROCESS    s7_mgt.exe -i0x4d
    FORK_PROCESS    s7_log.exe -m0xef -o0xff1f -flog.txt
    FORK_PROCESS isp_nt.exe -m0x23

  • hi all,

     I was using the older version of septel. that's why i was getting the error in MON mode.

    Now i have downloaded the new version of septel. Now there is no error while running gctload exe.

    But the problem is this i am not getting boot complete message in Monitoring mode after running gctload exe.

    Kindly Tell.

     

    Thanks.

     

  • Hi Vishal,

    If you havn't identified the cause of this issue, could you please provide me with your output from gctload when it starts up, upto and including the timer expiry. This should allow me to assist you further.

    With Kind Regards

    Alan Phillips.

  • Hi Alan,

    Thanks for Reply.

    I have made the changes in the config.txt for the monitor mode

    ****************** config.txt ********************

    SEPTELCP_BOARD 0 0x0043 monitor.dc3 mon

    LIU_CONFIG 0 0 5 1 1 1

    * Send Monitor messages to s7_log module

    MONITOR_LINK 0 0 0 0 16 0xef 0 0 0x00

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

    with this config file, i am getting boot complete message.

    Now i have two servers(main app. server & monitoring server) both have septel card installed on it.

    i have to monitor the main app. link.

    the main app. server is running in mtp mode & monitoring server is running in mon mode

    i have taken a parallel link from the main app. link  & connected to the monitoring mode.

    But by doing this my main app. link goes down.

    I know there is a sync. issue.

    I know i can't take a parallel link from an existing one. 

    can u tell me how can i create a circuit or configure a link in monitoring mode without effecting the main traffic ?

    Thanks a lot. 

    Regards,

    Vishal Dhingra

  • Could you please expand on what you mean by connecting the monitoring point in parellel to the signalling link. Are you using a monitoring point to achieve this? If so, is attnenuated (high impednace), or are you connecting through some other method, for example, using baluns to break out monitior the transmit and recieve paths.

    Thanks.

    With Kind Regards

  • Hi Alan,

    I have a cat5 cable whose one end is connected to DP side(switch end) like 5-5-2 and the other end is connected my main app. server.

    I have taken the second cat5 cable whose one is connected to same DP port like 5-5-2 and the other end is connected to my monitoring server.

    In this way i have taken a taken a parallel link from the existing one. 

    Thanks.

  • Hi sir,

    I am connecting the monitoring link as i told you.

    My problem is still there.

    kindly tell something to solve this problem.

    kindly reply.

    Thanks.

  • Hi all,

    Kindly Reply.

    I am waiting.

    Thanks,

    Vishal Dhingra