..

TCPEV_DLG_REQ_DISCARD in SRISM REQ

..

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

TCPEV_DLG_REQ_DISCARD in SRISM REQ

  • Can U find error in the following message. It is failing in TCAP

     

     M-tc7e2-i0001-f2d-d15-s00-p01010443200306020c032e0c0012041989480045590b0906070400000100140200
    M-tc7e0-i0001-f2d-d15-s00-p010e01010f079119196789686910010011079119894800455900
    M-tc7e2-i0001-f2d-d15-s00-p0500

     

     

    logs are:


    S7L:I0000 T 0001845b M tcf00 i0000 f22 d81 s00 pc18c830b0311f0112233445566778899aabbccddeeff
    S7L:I0000 T 0001845b M t8f01 i0000 f81 d22 s00 pc12e0ce30021f0112233445566778899aabbccddeeff
    S7L:I0000 T 000184da M tc7e2 i0001 f2d d15 s00 p01010443200306020c032e0c0012041989480045590b0906070400000100140200
    S7L:I0000 T 000184da M tc7e0 i0001 f2d d15 s00 p010e01010f079119196789686910010011079119894800455900
    S7L:I0000 T 000184da M tc781 i000c f15 d14 s00 p080301010402001e011fa11d02010102012d301580079119196789686981010082079119894800455900
    S7L:I0000 T 000184da M tc781 i000c f15 d14 s00 p080301010402001e011fa11d02010102012d301580079119196789686981010082079119894800455900
    S7L:I0000 T 000184da M tc7e2 i0001 f2d d15 s00 p0500
    S7L:I0000 T 000184da M tc783 i000c f15 d14 s00 p020601020704432003060d0ba1090607040000010014020e1d281b060704000001010101a010a00e800c032e0c00120419894800455900
    S7L:I0000 T 000184da M tc783 i000c f15 d14 s00 p020601020704432003060d0ba1090607040000010014020e1d281b060704000001010101a010a00e800c032e0c00120419894800455900
    S7L:I0000 T 000184da M t8784 i000c f14 d15 s00 p060f017e00
    S7L:I0000 TCAP Maintenance event : TCPEV_DLG_REQ_DISCARD
    S7L:I0000 T 000184da M t8784 i000c f14 d15 s00 p060f017e00
    S7L:I0000 T 000184da M t87e3 i0001 f15 d2d s00 p090901000c010100

     

     

    My config.txt is

    *
    * Configure individual boards:
    * For PCCS6 boards:
    *  PCCS6_BOARD <port_id> <board_id> <num_pcm> <flags> <code_file>
    * For SPCI4, SPCI2S, CPM8, SS7HD PCI (SS7HDP) and SS7HD cP (SS7HDC) boards:
    *  SS7_BOARD <board_id> <board_type> <flags> <code_file> <run_mode>
    SS7_BOARD 0 SS7HDP 0x0003 ss7.dc4 MTP *$ hw_type=SS7HDP4TE
    *
    * Configure individual E1/T1 interfaces:
    * LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format>
    *            <crc_mode> [<build_out>]
    LIU_CONFIG 0 0 5 1 1 1
    *
    * MTP parameters:
    *
    * MTP_CONFIG <reserved> <reserved> <options>
    MTP_CONFIG  0  0  0x00040004
    *
    * Define linksets:
    * MTP_LINKSET <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>
    MTP_LINKSET 0 908 1 0x0000 3118 0xc
    *
    * 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.
    MTP_LINK 0 0 0 0 0 0-0 0 16 0x0006
    *
    * Define a route for each remote signaling point:
    * MTP_ROUTE <dpc> <norm_ls> <user_part_mask> <flags> <second_ls>
    MTP_ROUTE 908 0 0x0008 0x0000 0
    MTP_ROUTE 800 0 0x0008 0x0000 0
    * MTP_TRACE 0xf 0xc01 0x1fffe0
    MTP_TRACE 0x20 2 0

    * SCCP Parameters:
    * SCCP_CONFIG   <local_spc>     <ssf>   <options>
    SCCP_CONFIG     3118            0xc     0x00050102

    * Enable SCCP traces:
    * SCCP_TRACE <op_evt_mask> <ip_evt_mask> <non_prim_mask>
    SCCP_TRACE 0x3 0x7 0x3

    * Define Remote Signaling Points:
    * SCCP_SSR      <ssr_id>        RSP     <remote_spc>    <flags> <pc_mask>
    SCCP_SSR        1               RSP     908             0       0x0000
    SCCP_SSR        2               RSP     800             0       0x0000

    * Define Local Sub-Systems:
    * SCCP_SSR      <ssr_id>        LSS     <local_ssn>     <module_id> <flags> <protocol>
    SCCP_SSR        3               LSS     0x00            0x2d            0       MAP

    * Define Remote Sub-Systems:
    * SCCP_SSR <ssr_id>     RSS     <remote_spc>    <remote_ssn> <flags>
    SCCP_SSR        4       RSS     908             0x08            0
    SCCP_SSR        5       RSS     800             0x06            0

    * TCAP Parameters:
    * TCAP_CONFIG <base_ogdlg_id> <nog_dialogues> <base_icdlg_id>
    *             <nic_dialogues> <options> <dlg_hunt> [<addr_format>]
    TCAP_CONFIG 0x0 8192 0x8000 8192 0x0000 0 0

    * Enable TCAP traces:
    * TCAP_TRACE <op_evt_mask> <ip_evt_mask> <non_prim_mask>
    TCAP_TRACE 0x7 0xf 0x0

    * MAP Parametes:
    * MAP_CONFIG <options>
    MAP_CONFIG 0x0

    * Enable MAP traces:
    * MAP_TRACE <op_evt_mask> <ip_evt_mask> <non_prim_mask>
    MAP_TRACE 0xf 0xf 0x15

     

     

     

     

    Please reply.

     

  • Hi

    MAP is sending just a Destination Address parameter, but not a Originating Address.

    TCAP needs both so you need to define a default Originating Address in TCAP, using message TCP_MSG_DEF_PARAM, 0x7781 and parameter TCPPN_ORIG_ADDR, 0x08

    Colin

  • or

    specify an Originating Address in the MAP dialogue Open Request message !

    Colin

  • How stupid am I !

    Thanx Colin.