This feature extracts the MSISDN from a SMMA message, then sends an RP-ACK to the SMMA request
Feature cheat sheet
| Feature Name | Network Operator Data | Used in PlanId(s) | Stateful or Stateless | POJO Feature or SBB Feature |
|---|---|---|---|---|
IPSMGWSMMAResonse |
No |
SMMA |
Stateless |
POJO |
Feature parameters
The Handle SMMA feature supports the following parameters that may be passed in a feature execution script run statement:
| Name | Allowed Values | Description |
|---|---|---|
mode |
|
This is used to determine what action the feature should take when run. |
Session Input variables
The feature reads the following fields in Session State
| Session State variable name | Variable type | Comments |
|---|---|---|
SRI4SMResult |
enum |
Indicates if the SendRoutingInfoForSM request has succeeded. Allowed values are |
SRI4SMError |
TcapError |
The TcapError received in response to the SendRoutingInfoForSMRequest |
ReadyForSMResult |
enum |
Indicates if the ReadyForSM request has succeeded. Allowed values are |
ReadyForSMError |
TcapError |
The TcapError received in response to the ReadyForSM |
Session Output variables
The feature sets the following fields in Session State
| Session State variable name | Variable type | Comments |
|---|---|---|
MSISDN |
String |
The MSISDN to be used by the Fetch IMSI feature |
Statistics
IPSMGWSMMAResponse statistics are tracked by the sentinel.ipsmgw SBB
and can be found under the following parameter set in REM:
SLEE-Usage → sentinel.ipsmgw service → sentinel.ipsmgw SBB → feature → IPSMGWSMMAResponse
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.ipsmgw,vendor=OpenCloud,version=2.9.0].SbbID[name=sentinel.ipsmgw,vendor=OpenCloud,version=2.9.0].feature.IPSMGWSMMAResponse"
| Name | Description |
|---|---|
SavedMSISDN |
Incremented when the MSISDN has been extracted from the incoming SIP MESSAGE |
SentRPACK |
Incremented when the RP-ACK message is successfully sent to the I-CSCF |
FailedToSendRPACK |
Incremented when the RP-ACK message fails to be sent to the I-CSCF |
SentRPError |
Incremented when the RP-ERROR message is successfully sent to the I-CSCF |
FailedToSendRPError |
Incremented when the RP-ERROR message fails to be sent to the I-CSCF |
FailedToPrepareSIPMessage |
Incremented when we unable to prepare a SIP MESSAGE for the RP-ACK or RP-ERROR to be sent in |
NoPAIAvailable |
Incremented when the |
Configuration
The feature is configured with configuration scoped according to a Sentinel Selection Key.
The Profile Table used to hold feature configuration is IPSMGWSharedConfigProfileTable.
The following attributes are available
| Attributes | Type | Meaning |
|---|---|---|
ICSCFURI |
String |
The I-CSCF SIP URI that will be used to route outbound SIP MESSAGE requests (see SIP Transports and Routing) |
Behaviour
When run with mode prepare and the trigger is a SIP MESSAGE that contains a SMMA, the feature will send a 202 response, then attempt to derive an MSISDN from the 'P-Asserted-Identity' header.
The feature will also use the incoming SIP MESSAGE to prepare the responding SIP MESSAGE request that will contain either the RP-ACK or RP-ERROR.
This response is prepared but not sent.
When run with mode send and the trigger is a TCAP response the feature
checks the SRI4SMResult, SRI4SMError, ReadyForSMResult, and
ReadyForSMError session state fields and sends the RP response based on
their values.
If both SRI4SMResult and ReadyForSMResult indicate success it will send an
RP-ACK. If either one of them indicates failure it will map the TCAP error to
an RP-ERROR cause based on the table below:
| TCAP error | RP-ERROR cause |
|---|---|
|
|
|
|
|
|
|
|
|
|
Any other value |
|
The prepared SIP Message request is then sent.
If the session state fields indicate that the SendRoutingInfoForSM and/or ReadyForSM operations have not been attempted then the feature will not do anything.
