When you read the trace data from your components after running the
tp_trace_receiver command, you may notice that messages are getting sent in fragments, and each fragment has an sendRoutingInfo for SM (SRI-SM) before it, rather that one unified SRI-SM for the concatenated message. See example below:
You may wish to know why the SRI-SM is before each fragment.
Please note that having an SRI-SM before each fragment of the message is the normal behavior as the RTR can route and deliver each message individually in a MO-MT routing path.
If the traffic is routed to AMS the message can be delivered using TCAP segmentation and the MMS (more-message-to-send) flag, which will result in one SRI-SM before the MT delivery of all the fragments in a single TCAP dialogue.
For more details, please refer to the section 18.4.9 TCAP Segmentation for Outgoing MTFSM on Page 362 and section 188.8.131.52 Caching Scenario When Delivery Is Attempt From AMS on Page 385 of the attached RTR Operator Manual.