This feature
analyses the contents of an incoming Tcap Message to determine if it contains a SINGLE_COMPONENT_TYPE or MULTIPLE_COMPONENT_TYPES.
Feature cheat sheet
| Feature Name | Network Operator Data | Used in PlanId(s) | Stateful or Stateless | POJO Feature or SBB Feature |
|---|---|---|---|---|
DetermineTcapMessageComponents |
No |
N/A |
Stateless |
POJO |
Session Output variables
The feature sets the following fields in Session State
| Session State variable name | Variable type | Comments |
|---|---|---|
TcapMessageComponents |
Enum |
possible values, |
Behaviour
The feature checks if the trigger message is a TCAP Message,if it is then it analyses the components to determine if the Tcap Message
contains either a SINGLE_COMPONENT_TYPE or MULTIPLE_COMPONENT_TYPES (TCOperationResult and TCOperationInvoke) and sets a session state field. The
value of the session state field can then be used subsequently in feature scripts to select which features to run. The following excerpt demonstrates
how the feature and session state field can be used in feature scripts.
SRI4SM_SipThirdPartyAccess_PartyRequest:
FeatureScriptSrc: featurescript SipThirdPartyAccessPartyRequest {
run IPSMGWMapProxy
run DetermineTcapMessageComponents
if session.TcapMessageComponents.MULTIPLE_COMPONENT_TYPES {
run IPSMGWGenerateMTCorrelationId
run IPSMGWStoreRoutingInfoCassandra mode "store"
run IPSMGWAdjustRoutingInfoResponse
} else {
run IPSMGWStoreRoutingInfoCassandra mode "store"
}
}