MAP protocol: support of sending TC-Result-NL for recommended operations

[vetss]

TCAP segmentation of MAP protocol has a following option:

C.2.3 TC-Result-NL A Result component may be segmented into one or several Result-Not-Last components followed by a Result-Last component. As specified in subclause 15.6.3, the MAP user parameter shall be split so that each segment is compatible with the type defined for the parameter of the result of the associated operation. Note that this segmentation mechanism runs the risk that the message carrying the Result-Last component arrives before the message carrying a Result-Not-Last component which results in failure. The use of SCCP class 1 "Sequence guaranteed", which raises the chance of in sequence delivery, is recommended.

So the idea iis for MAP operations that allows it we need to add some flag when an operation response sending that force of sending of TC-Result-NL instead of TC-Result-Last TCAP component. We can send several TC-Result-NL components and finally one TC-Result-Last.

Here is a list of operations that are needed to update:

MAP V3:

• AnyTimeModificationRes
• AnyTimeSubscriptionInterrogationRes
• SendRoutingInfoRes

MAP V1:

• SentParameterList

not recommended (but allowed):

MAP V3:

• PrepareHO-Res
• PrepareHO-Res
• ProvideSubscriberInfoRes
• AnyTimeInterrogationRes

MAP V2:

• SendIdentificationRes
• SendAuthenticationInfoRes
• PrepareHO-Res

[vetss]

Fixed by: https://github.com/RestComm/jss7/commit/f10e56044872bdcbd5df00781d5dc94842e5cfc8