Hi,
I am writing a module to monitor ss7 messages for MTU/MTR application in sigtran environment. Here is what i have done:
1 Disabled s7_log.exe from system.txt file
2 I have my own module that will read messages from module 0xef queue.
I am successfuly able to read messages from 0xef queue and now i want process these messages to write ss7 logs in my own customized way. The problem is that for certian messages i am unable to find description in the documentation like:
-t32da from d2 to ef
Can anyone help me find out description of this message.
Also i assume that c7_log.exe only receive's messages and doesnt send back any messages to any ss7 layer protocols. Please correct me if i am wrong
BR//
Shahzad
The 0x4000 bit is often flipped to show the difference between request and response, so 0x32DA would be the response to 0x72DA. If you look up 0x72DA in the M3UA Programmer's Manual, you'll find the answer.
As far as I know, s7_log does not send messages back to the layer modules. I have used this technique myself of creating a custom 's7_log' module to receive the log messages.
hi Martyn,
Need ur help . I am trying to use s7_log utility for capture messages but output is blank 1.e I dont see any messages on the screen . Also tried following instructions by enabling / disabling trace masks but result is still the same. I am using a DMV 1200 card . Pl let me know anything incorrect found in the config . My system.txt details are as given below
********************************************************************** 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 taskLOCAL 0x00 * tim_nt - Timer task** Optional modules running on the host:*LOCAL 0xcf * s7_mgt - Management/config taskLOCAL 0xef * s7_log - Display and logging utility LOCAL 0x2d * upe - Example user part taskLOCAL 0x4d * GCSS7 - Example Global Call** Modules that optionally run on the host**LOCAL 0x23 * ISUP module*LOCAL 0x4a * TUP moduleLOCAL 0x33 * SCCP moduleLOCAL 0x14 * TCAP moduleLOCAL 0x15 * MAP 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 moduleREDIRECT 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 moduleREDIRECT 0x22 0x20 * MTP3 module** Redirection of status indications:*REDIRECT 0xdf 0xef * LIU/MTP2 status messages -> s7_log*REDIRECT 0xdf 0x4d * LIU/MTP2 status messages -> s7_log*NUM_MSGS 64000** 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.exeFORK_PROCESS ssds.exe * FORK_PROCESS ssdh.exe -dFORK_PROCESS tim_nt.exeFORK_PROCESS tick_nt.exeFORK_PROCESS s7_mgt.exe *-i0x4d*FORK_PROCESS s7_log.exe -td -fss7log1.txtFORK_PROCESS s7_log.exe -pss7log11.pcapFORK_PROCESS Forker.exe*FORK_PROCESS sccp_nt.exe -t*FORK_PROCESS tcp_nt.exe -t*FORK_PROCESS map_nt.exe -t*
Thanks & regards
HAresh
To get messages going into the log, you also have to set trace masks on a protocol module (such as MTP3). Some of the more common ones can be switched on via commands in CONFIG.TXT, or else you can send a message to the module using s7_play.
There are quite a few articles that describe tracing in detail here.
