This feature uses an IMSI to send a ReadyForSM to the HLR and handles the response
Feature cheat sheet
Feature Name | Network Operator Data | Used in PlanId(s) | Stateful or Stateless | POJO Feature or SBB Feature |
---|---|---|---|---|
IPSMGWReadyForSMRegistration |
No |
register |
Stateless |
SBB |
Session Input variables
The feature reads the following fields in Session State
Session State variable name | Variable type | Comments |
---|---|---|
IMSI |
String |
The IMSI to use in the ReadyForSM operation |
SRI4SMResult |
enum |
Indicates if the SendRoutingInfoForSM request has succeeded. Allowed values are |
Session Output variables
The feature sets the following fields in Session State
Session State variable name | Variable type | Comments |
---|---|---|
ReadyForSMResult |
enum |
Indicates if the ReadyForSM request has succeeded. Allowed values are |
ReadyForSMError |
TcapError |
The TcapError received in response to the ReadyForSM |
Statistics
IPSMGWReadyForSMRegistration 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 → IPSMGWReadyForSMRegistration
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.ipsmgw,vendor=OpenCloud,version=2.5.1].SbbID[name=sentinel.ipsmgw,vendor=OpenCloud,version=2.5.1].feature.IPSMGWReadyForSMRegistration"
Name | Description |
---|---|
SentReadyForSM |
Incremented when the ReadyForSM message is successfully sent to the HLR |
FailedToSendReadyForSM |
Incremented when the ReadyForSM message fails to be sent to the HLR |
RequestSuccessful |
Incremented when receiving a successful response from the HLR |
RequestFailed |
Incremented when a failure response or timeout is received from the HLR leg |
NoIMSIAvailable |
Incremented when the IMSI was not available from session state |
SRI4SMFailed |
Incremented when the SendRoutingInfoForSMRequest failed and the feature cannot do anything as a result |
InvalidTrigger |
Incremented when then trigger is not a SIP REGISTER message |
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 |
---|---|---|
HlrAddress |
String |
Address of the HLR send the ReadyForSM request, used when establishing the MAP dialog if |
UseMsisdnAsHlrAddress |
Boolean |
Address the outbound HLR leg using a GT address formed from the subscriber MSISDN, instead of using the configured |
SentinelOriginatingAddress |
String |
Address of Sentinel used when establishing the MAP dialog |
InvokeTimeout |
int |
The timeout in milliseconds for the response from HLR. Used in the TCAP layer for the invoke timeout. Default is 5000 |
Using MSISDN as HLR Address
The Ready For SM Registration feature can optionally address the HLR leg using a GT address formed from the inbound subscriber MSISDN, as opposed to using the destination addresses configured in the IPSMGWMapProxyConfigProfileTable
profile table described above.
This behaviour can be enabled or disabled by setting the UseMsisdnAsHlrAddress
attribute in the Shared Configuration Profile
.
MAP Application Context
The feature uses MAP Application Context mwdMngtContext_v2_ac
.
This application context was added in GSM MAP Phase 2.
Behaviour
When triggered on a REGISTER request, the feature checks that an IMSI is present in session state field named IMSI. It then initiates a ReadyForSM operation to the HLR with an alert
reason of MS Present
.
When the ReadyForSM operation completes, the feature sets the ReadyForSMResult
session state field based on the response, SUCCESS
if the ReadyForSM operation is successful,
FAILED
if the ReadyForSM operation returns an error or a timeout. It also sets the ReadyForSMError
session state field with the TcapError if the response was a failure.