Status: Accepted
Owner: [email protected]
CC: [email protected], [email protected]
Labels: Type-Defect Priority-Medium Component-SS7 Roadmap-Fix
Version-2.0.0.BETA4
New issue 203 by [email protected]: Bad processing of linkedId
parameters in TCAP, MAP and CAP stacks
http://code.google.com/p/jss7/issues/detail?id=203
Now linkedId is by mistake associated with invokeId for received invokes.
But linkedId must be associated with invokeId for SENT invokes.
This need updating:
- TCAP stack DialogImpl.processOperationsState():
in case of Invoke incoming with set linkedId we need to check if a
corresponded Invoke is present in "this.operationsSent[index]".
If yes we have to put this sent Invoke into a special new field
"private Invoke linkedInvoke;" for processing in TCAP users (MAP, CAP)
- MAPProviderImpl and CAPProviderImpl.processComponents() :
remove a special processing of "linkedId" by
if (linkedId != null) {
// linkedId exists Checking if the linkedId exists
if (!mapDialogImpl.checkIncomingInvokeIdExists(linkedId)) {
and replcase it by checking new linkedInvoke field
