..

SS7L Starting failed : CAMEL Charging - PLEASE HELP!.

..

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

SS7L Starting failed : CAMEL Charging - PLEASE HELP!.

  • Hi,

    I'm getting the highlighted error when i start the gctload, Please help me on this, as i'm new to the SS7 configurations. It would be really appreciated.

    Board details :

    http://www.dialogic.com/en/products/signaling-and-ss7-components/signaling-boards/ss7ldh4.aspx

    The purpose of this card is for CAMEL Charging over the E1, we are running the board on trial mode and failed to debug the below set of errors with their status, Please help us to resolve this.

     

    The e1 details are as follows.:

    DPC = 504 - 01f8 - f801 (flip)

    OPC = 913 - 0391  - 9103 (flip)

    SLC = 0

    Timeslot = 16

    *   CalledPartyNumber   = 9779843791702f = 799748731907f2 = Confirm = 799748731907f2 (Giving MSISDN instead of GT for testing.)

    *    CallingPartyNumber  = 9779851179265f = 799758119762f5 = Confirm = 799758119762f5   (Giving MSISDN instead of GT for testing..)

    -------------------------Log----------------------------------------------

    [-----------@NT1 SEPTEL.6.6]$ ./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 0x4d
    Created LOCAL module Id 0x3d
    Created LOCAL module Id 0x33
    Created LOCAL module Id 0x14
    Created LOCAL module Id 0x5d
    Created LOCAL module Id 0x22
    Created LOCAL module Id 0x6d
    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
    (22363)gctload: Verification started.
    (22363)gctload: Verification complete.
    (22363)gctload: Process (22364)'./ssdl' - forked by gctload
    (22363)gctload: Process (22365)'./tim_lnx' - forked by gctload
    (22363)gctload: Process (22366)'./tick_lnx' - forked by gctload
    (22363)gctload: Process (22367)'./s7_mgt' - forked by gctload
    (22363)gctload: Process (22368)'./s7_log' - forked by gctload
    (22363)gctload: Process (22369)'./HSTBIN/sccp' - forked by gctload
    (22363)gctload: Process (22370)'./HSTBIN/tcap' - forked by gctload
    (22363)gctload: Process (22371)'./HSTBIN/inap' - forked by gctload
    (22363)gctload: Process (22372)'./HSTBIN/mtp3' - forked by gctload
    (22363)gctload: Initialisation complete.

    SS7 TCAP started in trial mode.
    S7_log : mod ID=0xef, options=0xaf0d, max_param_len=320
    This binary will terminate after 1 hour.
    SS7 INAP started in trial mode.
    This binary will terminate after 1 hour.
    SS7 MTP3 started in trial mode.
    This binary will terminate after 1 hour.
    S7_MGT Tx: M-I0000-t7680-i0000-fcf-d20-s00-r8000-p200000cf70637337332e6463310000000000000000000010
    S7_log : Writing log file s7log.txt
    SS7 SCCP started in trial mode.
    This binary will terminate after 1 hour.
    S7_log : Writing PCAP log file s7log.pcap
    SS7 ssdl started in trial mode.
    This binary will terminate after 1 hour.
    ssdl: 16 boards
    S7_MGT Rx: M-I0000-t3680-i0000-f20-dcf-s00-r0000-p200000cf70637337332e6463310000000000000000000010
    S7_MGT Tx: M-I0000-t7681-i0000-fcf-d20-s00-r8000-p0020000000002e2f44432f7373372e6463370000000000000002
    ssdl[0]: ss7ld
    ssdl[0]: requesting board reset
    S7_MGT Rx: M-I0000-t3681-i0000-f20-dcf-s00-r0000-p0020000000002e2f44432f7373372e6463370000000000000002
    ssdl[0]: reset complete
    ssdl[0]: initialising board
    ssdl[0]: initialised
    ssdl[0]: code download requested
    ssdl[0]: download complete
    ssdl[0]: run requested
    ssdl[0]: running
    ssdl[0]: configuring board
    ssdl[0]: configured
    ssdl[0]: board ready
    S7_MGT Rx: M-I0000-t06a0-i0000-f20-dcf-s60-r0000-p00200000
    S7_MGT Tx: M-I0000-t06a0-i0000-f20-def-s60-r0000-p00200000
    S7_MGT Tx: M-I0000-t6111-i0000-fcf-d8e-s00-r8000-p00000000000000000000000000000000000000000000000000000000
    S7_MGT Tx: M-I0000-t6f0d-i0000-fcf-d8e-s00-r8000-p000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    S7_MGT Tx: M-I0000-t7f10-i0000-fcf-d8e-s00-r8000-p00030000000100000110c0000000000000000000800000000000000000000000800000000000000000000000800000000000000000000000800000000000000000000000
    S7L:2014-03-14 16:40:48.009 I0000 M t06a0 i0000 f20 def s60 p00200000
    S7_MGT Rx: M-I0000-t2111-i0000-f8e-dcf-s00-r0000-p000002017373372e6463370000000000000000000000000000000000
    S7_MGT Code file identification: board_id 0 'ss7.dc7' V2.01
    S7_MGT Rx: M-I0000-t2f0d-i0000-f8e-dcf-s00-r0000-p200300000500000000000000000000000000000000000000000002000000524339323036323800000000000000000000000000000000000000000000
    S7_MGT Board identification: board_id 0
        Board type: 32 (SS7LD)
        Hardware revision: 3
        RAM size: 32M byte
        ADDR switch: 5
        Board serial number: RC920628
        Current temperature: 0 degrees C
        Maximum temperature: 0 degrees C
    S7L:2014-03-14 16:40:49.049 I0000 M t0e23 i0000 f10 ddf s03
    S7L:2014-03-14 16:40:49.049 I0000 M t0e23 i0000 f10 ddf s05
    S7L:2014-03-14 16:40:50.049 I0000 M t0e23 i0000 f10 ddf s04
    S7L:2014-03-14 16:40:51.049 I0000 M t0e23 i0000 f10 ddf s01
    S7_MGT Rx: M-I0000-t3f10-i0000-f8e-dcf-s00-r0000-p00030000000100000110c0000000000000000000800000000000000000000000800000000000000000000000800000000000000000000000800000000000000000000000
    S7_MGT Tx: M-I0000-t7e34-i0000-fcf-d10-s00-r8000-p05010101009b9f000000000104000000000001000000000000000000000000000000000000000000
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 AIS
    S7_MGT Rx: M-I0000-t3e34-i0000-f10-dcf-s00-r0000-p05010101009b9f000000000104000000000001000000000000000000000000000000000000000000
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 REMOTE ALARM
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 SYNC LOSS
    S7_MGT Tx: M-I0000-t7f17-i0000-fcf-d8e-s00-r8000-p00000000000000000000000000000010000000000000000000000000000000000000000000000000
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 PCM LOSS
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 AIS CLEARED
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 REMOTE ALARM CLEARED
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 IN SYNC
    S7L:2014-03-14 16:40:52.329 I0000 LIU Status : id=0 PCM OK
    S7_MGT Rx: M-I0000-t3f17-i0000-f8e-dcf-s00-r0000-p00000000000000000000000000000010000000000000000000000000000000000000000000000000
    S7_MGT Tx: M-I0000-t7203-i0000-fcf-d71-s00-r8000-p000022008eef01100032002800000000000401c2012c000c0052000500010037000f000a0001008200000028003c0050001e00320046002d00410055
    S7L:2014-03-14 16:40:52.369 I0000 Level 2 State : id=0 OUT OF SERVICE
    S7_MGT Rx: M-I0000-t3203-i0000-f71-dcf-s00-r0000-p000022008eef01100032002800000000000401c2012c000c0052000500010037000f000a0001008200000028003c0050001e00320046002d00410055
    S7_MGT Tx: M-I0000-t7300-i0000-fcf-d22-s00-r8000
    S7_MGT Rx: M-I0000-t3300-i0000-f22-dcf-s00-r0000
    S7_MGT Tx: M-I0000-t7303-i0000-fcf-d22-s00-r8000-p000422ef00000001000000000020000400ef00000000000000000033000000000000000000000000
    S7_MGT Rx: M-I0000-t3303-i0000-f22-dcf-s00-r0000-p000422ef00000001000000000020000400ef00000000000000000033000000000000000000000000
    S7_MGT Tx: M-I0000-t7310-i0000-fcf-d22-s00-r8000-p000001f8000100010003000c00000391
    S7_MGT Rx: M-I0000-t3310-i0000-f22-dcf-s00-r0000-p000001f8000100010003000c00000391
    S7_MGT Tx: M-I0000-t7311-i0000-fcf-d22-s00-r8000-p00000071000000060000000000000000
    S7_MGT Rx: M-I0000-t3311-i0000-f22-dcf-s00-r0000-p00000071000000060000000000000000
    S7_MGT Tx: M-I0000-t7312-i0000-fcf-d22-s00-r8000-p000001f800000000000000200000000000000000000000000000000000000000
    S7_MGT Rx: M-I0000-t3312-i0000-f22-dcf-s00-r0000-p000001f800000000000000200000000000000000000000000000000000000000
    S7_MGT Tx: M-I0000-t731f-i0000-fcf-d22-s00-r8000-p000001f8
    S7_MGT Rx: M-I0000-t331f-i0000-f22-dcf-s00-r0000-p000001f8
    S7L:2014-03-14 16:40:52.371 I0000 MTP Event : point code=000001f8
     Destination unavailable
    S7_MGT Boot complete
    S7L:2014-03-14 16:41:27.033 I0000 M t0e23 i0000 f10 ddf s02

     

     

    ------------------system.txt--------------------------------------------------

    * Essential modules running on host:
    *
    LOCAL           0x20            * ssd/ssds/ssdh - Board interface task
    LOCAL           0x00            * tim_xxx - Timer task
    * Optional modules running on the host:
    *
    LOCAL           0xcf            * s7_mgt - Management/config task
    LOCAL           0xef            * s7_log - Display and logging utility
    LOCAL           0x4d            * Dialogic
    * Modules that optionally run on the host:
    LOCAL          0x3d            * SPCI
    LOCAL          0x33            * SCCP module
    LOCAL          0x14            * TCAP module
    LOCAL          0x5d            * INAP module
    LOCAL          0x22            * MTP3 module
    LOCAL          0x6d            * CAMEL Appln 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

    NUM_MSGS 4000

    * REDIRECT  0x21 0x20
    *
    * Now start-up all local tasks:
    *   (For PCCS6 start-up use ssd,
    *   for SPCI4/SPCI2S/CPM8 start-up use ssds and
    *   for SS7HD boards use ssdh)
    *
    FORK_PROCESS ./ssdl -d -o3 -a5 -t
    FORK_PROCESS  ./tim_lnx
    FORK_PROCESS  ./tick_lnx
    FORK_PROCESS  ./s7_mgt -d
    FORK_PROCESS  ./s7_log -m0xef -fs7log.txt -ps7log.pcap -td -n20 -s10240
    FORK_PROCESS  ./HSTBIN/sccp -t
    FORK_PROCESS  ./HSTBIN/tcap -t
    FORK_PROCESS  ./HSTBIN/inap -t -m0x5d
    FORK_PROCESS  ./HSTBIN/mtp3 -t

    -----------------------------------------------------------------------------

     

    -------------------------------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.
    *
    ********************************************************************************

    *
    * For SS7HD PCI boards:
    * SS7_BOARD <board_id> <board_type> <flags> <code_file> <run_mode>
    SS7_BOARD  0 SS7LD 0x0001  ./DC/ss7.dc7  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  504  1  0x0000  913  0x0c
    *
    * 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 SPCI4 / SPCI2S / CPM8 boards:
    MTP_LINK  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  504 0  0x0020
    *
    * Define any user provided Layer 4 protocol:
    * MTP_USER_PART <service_ind> <module_id>
    MTP_USER_PART  0x03  0x33

    *
    *MTP_TRACE 0x20 2 0
    *
    * ISUP parameters:
    *
    * Configure ISUP module:
    * ISUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts>
    *ISUP_CONFIG  0  0  0x00  0x0435  2  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  910  0x01  0x01  0x3fffffff  0x001c  0  0x4d 14455 0x8  0  0x00
    *ISUP_CFG_CCTGRP  1  14461  0x01  0x21  0x3fffffff  0x001c  0  0x4d  14455 0x8
    *0  0x00
    *
    ********************************************************************************

     

  • Now after remote PC is up the s7log goes as below, But the messages still coming, are they normal ??

    S7L:2014-03-14 19:56:56.303 I0000 M t0e23 i0000 f10 ddf s03

    S7L:2014-03-14 19:56:56.303 I0000 M t0e23 i0000 f10 ddf s05

    S7L:2014-03-14 19:56:57.323 I0000 M t0e23 i0000 f10 ddf s04

    S7L:2014-03-14 19:56:58.283 I0000 M t0e23 i0000 f10 ddf s01

    S7_MGT Rx: M-I0000-t3f10-i0000-f8e-dcf-s00-r0000-p00030000000100000110c0000000000000000000800000000000000000000000800000000000000000000000800000000000000000000000800000000000000000000000

    S7_MGT Tx: M-I0000-t7e34-i0000-fcf-d10-s00-r8000-p05010101009b9f000000000104000000000001000000000000000000000000000000000000000000

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 AIS

    S7_MGT Rx: M-I0000-t3e34-i0000-f10-dcf-s00-r0000-p05010101009b9f000000000104000000000001000000000000000000000000000000000000000000

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 REMOTE ALARM

    S7_MGT Tx: M-I0000-t7f17-i0000-fcf-d8e-s00-r8000-p00000000000000000000000000000010000000000000000000000000000000000000000000000000

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 SYNC LOSS

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 PCM LOSS

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 AIS CLEARED

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 REMOTE ALARM CLEARED

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 IN SYNC

    S7L:2014-03-14 19:56:59.543 I0000 LIU Status : id=0 PCM OK

    S7_MGT Rx: M-I0000-t3f17-i0000-f8e-dcf-s00-r0000-p00000000000000000000000000000010000000000000000000000000000000000000000000000000

    S7_MGT Tx: M-I0000-t7203-i0000-fcf-d71-s00-r8000-p000022008eef01100032002800000000000401c2012c000c0052000500010037000f000a0001008200000028003c0050001e00320046002d00410055

    S7L:2014-03-14 19:56:59.583 I0000 Level 2 State : id=0 OUT OF SERVICE

    S7_MGT Rx: M-I0000-t3203-i0000-f71-dcf-s00-r0000-p000022008eef01100032002800000000000401c2012c000c0052000500010037000f000a0001008200000028003c0050001e00320046002d00410055

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

    S7_MGT Rx: M-I0000-t3300-i0000-f22-dcf-s00-r0000

    S7_MGT Tx: M-I0000-t7303-i0000-fcf-d22-s00-r8000-p000422ef00000001000000000020000400ef00000000000000000033000000000000000000000000

    S7_MGT Rx: M-I0000-t3303-i0000-f22-dcf-s00-r0000-p000422ef00000001000000000020000400ef00000000000000000033000000000000000000000000

    S7_MGT Tx: M-I0000-t7310-i0000-fcf-d22-s00-r8000-p000001f8000100010003000c00000391

    S7_MGT Rx: M-I0000-t3310-i0000-f22-dcf-s00-r0000-p000001f8000100010003000c00000391

    S7_MGT Tx: M-I0000-t7311-i0000-fcf-d22-s00-r8000-p00000071000000060000000000000000

    S7_MGT Rx: M-I0000-t3311-i0000-f22-dcf-s00-r0000-p00000071000000060000000000000000

    S7_MGT Tx: M-I0000-t7312-i0000-fcf-d22-s00-r8000-p000001f800000000000000200000000000000000000000000000000000000000

    S7_MGT Rx: M-I0000-t3312-i0000-f22-dcf-s00-r0000-p000001f800000000000000200000000000000000000000000000000000000000

    S7_MGT Tx: M-I0000-t731f-i0000-fcf-d22-s00-r8000-p000001f8

    S7L:2014-03-14 19:56:59.585 I0000 MTP Event : point code=000001f8

    Destination unavailable

    S7_MGT Rx: M-I0000-t331f-i0000-f22-dcf-s00-r0000-p000001f8

    S7_MGT Tx: M-I0000-tc30a-i0000-fcf-d22-s00-r8000

    S7_MGT Rx: M-I0000-t830a-i0000-f22-dcf-s00-r0000

    S7_MGT Boot complete

    S7L:2014-03-14 19:57:00.563 I0000 Level 2 State : id=0 INITIAL ALIGNMENT

    S7L:2014-03-14 19:57:01.503 I0000 Level 2 State : id=0 ALIGNED READY

    S7L:2014-03-14 19:57:01.543 I0000 Level 2 State : id=0 IN SERVICE

    S7L:2014-03-14 19:57:01.604 I0000 MTP Event : linkset_id/link_ref=0000 Changeback

    S7L:2014-03-14 19:57:01.604 I0000 MTP Event : linkset_id=00 Link set recovered

    S7L:2014-03-14 19:57:01.604 I0000 MTP Event : linkset_id=00 Adjacent SP accessible

    S7L:2014-03-14 19:57:01.604 I0000 MTP Event : point code=000001f8

    Destination available

  • above Issue is Solved, Can someone please share a sample IDP packet, indicating all fields.. Would be really appreciated.

    thanks.