It is possible that when you run the
tp_trace_receiver command in order to trace data from your components, you find that the sent messages are fragmented, for instance:
You may wish to know whether this implies that the system is using MAP v1 instead of MAP v3 as configured.
tp_trace_receivercommand writes the trace data to a PCAP file, which can be examined in a software such as WireShark, as demonstrated in the example above.
- Please note that the fact that message is fragmented in 3 segments is related to the length of the user data and the Data Coding Scheme (DCS) used which indicates UCS-2 coding standard. The message fragmentation is not an indication that the system is using MAP v1.
- You can confirm that your system is using the MAP v3 by checking the Application Context names under the Transaction Capabilities Application Part (TCAP) in the trace file.
- Click on any of the message fragments, or the SRI-SM for any of the message fragments.
- Then note the application-context-name under dialogueResponse in the TCAP, for example:
the application context name (shortMsgMT-RelayContext-v3) indicates that MAP v3 is being used.
- Note that if you check the SRI-SM instead of the message fragment itself, the application context name will be shortMsgGatewayContext-v3: