Updates:
Status: Accepted
Owner: [email protected]
Cc: [email protected] [email protected] [email protected]
Labels: -Type-Defect Type-Enhancement Version-1.0.0.BETA2
Comment #1 on issue 126 by [email protected]: ss7/cap not possible to
get correct dialog state in
CAPServiceCircuitSwitchedCallListener.onCAPMessage
http://code.google.com/p/jss7/issues/detail?id=126
Hello!
Some remarks:
- CAPServiceCircuitSwitchedCallListener.onCAPMessage() is not the best
event for recieved message listerning. Use specail events for this. For
example for initialDP message - use "onInitialDPRequest(InitialDPRequest
ind)" method.
- you can recognize which TCAP message carries a CAP message by events
onDialogDelimiter() (TC-BEGIN and TC-CONTINUE cases) or onDialogClose()
(TC-END case). But these events are invoked after onCAPMessage() or
onInitialDPRequest().
- capDialogImpl.getState() is generally for internal usage. It is not a
good idea to use it.
- " move the
capDialogImpl.setState(CAPDialogState.Expunged);
before the
processComponents(capDialogImpl, comps);" - is not a good idea too
For solving your problem I suggest to introduce a getter into a CAPDialog:
TCAPMessageType CAPDialog getTCAPMessageType();
and
enum TCAPMessageType { TC-BEGIN, TC-CONTINUE, TC-END, TC-ABORT }
This getter can be used in onCAPMessage() and onInitialDPRequest() methods.
WDYT?
