This feature selects the behaviour of the IPSMGW when a SIP Message request is received.
Feature cheat sheet
| Feature Name | Network Operator Data | Used in PlanId(s) | Stateful or Stateless | POJO Feature or SBB Feature |
|---|---|---|---|---|
IPSMGWDetermineIsSMSOverIP |
No |
Any |
Stateless |
POJO |
Statistics
IPSMGWDetermineIsSMSOverIP 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 → IPSMGWDetermineIsSMSOverIP
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.ipsmgw,vendor=OpenCloud,version=3.1.0].SbbID[name=sentinel.ipsmgw,vendor=OpenCloud,version=3.1.0].feature.IPSMGWDetermineIsSMSOverIP"
| Name | Description |
|---|---|
IsSMSOverIP |
Incremented when a SIP MESSAGE’s Content-Type is |
SentSuccess |
Incremented when a 'success' final response is sent (e.g. 202) |
SentError |
Incremented when a 'error' final response is sent (e.g. 403) |
SessionIsMOFSM |
Incremented when MESSAGE’s RP-DATA direction is from MobileStation to Network |
Behaviour
If the SIP Message Request body does not include an SMS, the default product configuration has the IP-SM-GW act as a Routing B2BUA, thereby sending the SIP Message request towards the S-CSCF.
The Content-Type header is checked to see if it is application/vnd.3gpp.sms, and if so this indicates that the request is SMS over IP related. The session state field IsSMSOverIP set to true.
If the Content-Type header does not match the feature finishes execution.
Next the body of the SIP Message Request is parsed as an RP Message. If parsing is unsuccessful the feature sends a 403 response, increments the SentError statistic and finishes execution.
Assuming that parsing is successful, the feature then checks the RP Message Type Indicator for directionality of MS to Network.
If the direction is Network to MS it is a message type that the IP-SM-GW does not process, so the feature finishes execution and the IP-SM-GW will act as a Routing B2BUA.
Assuming the direction is MS to Network, the following occurs:
-
if the RP Message Type indicates RP-DATA, the feature sets the Sentinel Selection Key’s PlanID field to the value "MOFSM". This corresponds to the MO Submission Flows, and Mobile Originated Features.
-
if the RP Message Type indicates RP-SMMA, the feature sets the Sentinel Selection Key’s PlanID field to the value "SMMA". This corresponds to the Short Message Memory Available Flows.
-
if the RP Message Type indicates RP-ACK, or RP-ERROR, the feature sets the Sentinel Selection Key’s PlanID field to the value "MTFSM_DR". This corresponds to the Delivery Report portion of the MT Delivery Flows.
