This feature sends an SMS Submit Report to an SMS over IP capable UE
Feature cheat sheet
| Feature Name | Network Operator Data | Used in PlanId(s) | Stateful or Stateless | POJO Feature or SBB Feature |
|---|---|---|---|---|
IPSMGWMOSubmitReport |
Yes |
MOFSM |
Stateless |
POJO |
Statistics
MOSubmitReport 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 → IPSMGWMOSubmitReport
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.ipsmgw,vendor=OpenCloud,version=4.1].SbbID[name=sentinel.ipsmgw,vendor=OpenCloud,version=4.1].feature.IPSMGWMOSubmitReport"
| Name | Description |
|---|---|
ErrorSendingMessage |
Incremented when the feature fails to send SIP MESSAGE containing smsSubmitReport |
SentAck |
Incremented when the feature sends one RP-ACK in the SIP MESSAGE |
SentError |
Incremented when the feature sends one RP-ERROR in the SIP MESSAGE |
ReceivedOk |
Incremented when the feature receives the successful response for the MESSAGE request |
ReceivedError |
Incremented when the feature receives non-successful response for the MESSAGE request |
Configuration
The feature is configured with configuration scoped according to a Sentinel Selection Key.
The Profile Table used to hold feature configuration is Shared Configuration Profile.
The following attributes are used:
| 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
The feature is triggered after the MO Submission feature has finished.
The feature checks session state to determine the outcome of MO Submission to the SMSC.
In the case that MO Submission was successful it formulates a SIP Message request containing an RP-ACK towards the initiating UE. In the case that there were parsing or other issues in MO Submission it formulates a SIP Message request containing an RP-ERROR towards the initiating UE (SM-over-IP sender).
The details of these requests are as follows.
Generic header setting
Regardless of whether or not the Submit Report towards the UE (SM-over-IP sender) indicates a successful or failed submission attempt the following headers are set
| Header | Setting or manipulation |
|---|---|
Request URI |
Contains a public user identity of the SM-over-IP sender |
Route header |
Set to the I-CSCF URI, with the loose routing parameter added |
Content-Type |
set to "application/vnd.3gpp.sms" |
It reads the P-Asserted-Identity, P-Preferred-Identity and From headers of the original SMS over IP Message request in order to set the Request URI of the Submit Report.
Creation of an RP-ACK Submit report
In addition to the generic header setting, an RP-ACK Submit report sets headers as follows
| Header | Setting or manipulation |
|---|---|
P-Asserted-Identity |
Contains the SIP URI of the IP-SM-GW |
Request-Disposition |
set to "fork" |
Message body |
Contains an RP-ACK in content transfer encoding of type "binary" |
The RP Message Reference in the RP-ACK matches the Message Reference in the RP-Submit.
Creation of an RP-ERROR Submit report
In addition to the generic header setting, an RP-ERROR Submit report sets the body of the SIP Message request to contain an RP-ERROR, with content transfer encoding of type "binary".
The RP Message Reference in the RP-ERROR matches the Message Reference in the RP-Submit.
The setting of the RP-ERROR’s RPCause value is as follows
| Source error cause | RP Error Cause value |
|---|---|
Could not parse the SMS body from the SM-over-IP sender |
PROTOCOL_ERROR |
MO Forward SM resulted in TC_UserAbort |
NETWORK_OUT_OF_ORDER |
MO Forward SM resulted in TC_ProviderAbort |
NETWORK_OUT_OF_ORDER |
MO Forward SM resulted in an InvokeTimeout |
NETWORK_OUT_OF_ORDER |
MO Forward SM error MAPErrors.facilityNotSupported |
REQUESTED_FACILITY_NOT_IMPLEMENTED |
MO Forward SM error MAPErrors.systemFailure |
NETWORK_OUT_OF_ORDER |
MO Forward SM error MAPErrors.unexpectedDataValue |
SEMANTICALLY_INCORRECT_MESSAGE |
MO Forward SM error Delivery Failure with Delivery Failure Cause of memoryCapacityExceeded |
MEMORY_CAPACITY_EXCEEDED |
MO Forward SM error Delivery Failure with Delivery Failure Cause of equipmentProtocolError |
PROTOCOL_ERROR |
MO Forward SM error Delivery Failure with Delivery Failure Cause of equipmentNotSM_Equipped |
REQUESTED_FACILITY_NOT_IMPLEMENTED |
MO Forward SM error Delivery Failure with Delivery Failure Cause of unknownServiceCentre |
UNASSIGNED_NUMBER |
MO Forward SM error Delivery Failure with Delivery Failure Cause of sc_Congestion |
CONGESTION |
MO Forward SM error Delivery Failure with Delivery Failure Cause of invalidSME_Address |
SHORT_MESSAGE_TRANSFER_REJECTED |
MO Forward SM error Delivery Failure with Delivery Failure Cause of subscriberNotSC_Subscriber |
UNIDENTIFIED_SUBSCRIBER |
