Updates:
Status: Started
Comment #1 on 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
There are two operations in CAP that can be refered by a linked Invoke
operation:
- playAnnouncement = 47
- promptAndCollectUserInformation = 48
a linked Invoke operation for them can be:
- specializedResourceReport = 49
There is an operation in MAP that can be refered by a linked Invoke
operation:
- registerPassword = 17
a linked Invoke operation for it can be:
- getPassword = 18
(these operations have not been implemented yet)
Made changes:
- in SpecializedResourceReportRequest added:
public Long getLinkedId();
public void setLinkedId(Long val);
public Invoke getLinkedInvoke ();
public void setLinkedInvoke (Invoke val);
- CAPDialogCircuitSwitchedCall.addSpecializedResourceReportRequest_Cap*():
added "Long linkedId" parameter
- MAP/CAPServiceBaseImpl: added method
public long[] getLinkedOperationList(long operCode)
This method must be overridden by MAP/CAP services that accept linked
opetarions.
- TCAP Component: added extra methods
public Invoke getLinkedInvoke();
public void setLinkedInvoke(Invoke val);
linkedInvoke is filled in TCAP layer in DialogImpl.processOperationsState()
method
Unit tests are added and some bugs have been removed.
