This page presents summaries and links to more detailed descriptions of Sentinel IP Short Message Gateway (IPSMGW) features.
Common features
These are common features that are used in several flows
| Feature | What it does |
|---|---|
instructs the Sentinel core to accept the incoming dialog. |
|
is responsible for building a Call Detail Record that reflects the actions taken whilst processing a session. |
|
records various information from incoming messages needed by the AVP CDR feature. |
|
uses information from the incoming TCAP message request or Sh Push Notification Result to determine the MSISDN and set it in session state |
|
uses information from the incoming TCAP message request or Sh Push Notification Result and sets the plan ID in the Sentinel selection key in Session State field. The plan ID affects which features will run for the call on the current AS instance. |
|
sets the session state field |
|
selects the behaviour of the IPSMGW when a SIP Message request is received. |
|
analyses the contents of an incoming Tcap Message to determine if it contains a |
|
analyses the contents of an incoming Tcap Message to determine if it contains SRIForSM result SUCCESS or FAILURE (AbsentSubscriber). |
|
sets the network operator element of the Sentinel selection key |
|
defines immediate event charging of MO- and MT-FSMs delivered over the PS and CS networks for Sentinel as an IPSMGW. |
|
clears all pending requests and ends all legs. |
|
determines Mobile Country Code (MCC), Mobile Network Code (MNC), and ISO Country Code values for the subscriber. |
|
uses an MSISDN to fetch the IMSI from the HLR via a SendRoutingInfoForSMRequest |
|
proxies MAP messages between two network elements, typically a Serving MSC (SMSC) and an MSC. |
|
modifies outbound messages sent between two network elements, typically a Serving MSC (SMSC) and an MSC. |
|
uses an IMSI to send a ReadyForSM to the HLR and handles the response |
|
instructs the Sentinel core to reject the incoming dialog. |
|
rejects OpenRequests from SCCP addresses it does not recognize based on a provisioned whitelist. |
Mobile Originated Features
These features relate to the SMS Submission path from the UE to the network.
| Feature | What it does |
|---|---|
submits an SMS Over IP request to the SMSC. |
|
updates the Orig-Address of outbound MAP MT-ForwardSM requests to allow CAP charging of the session. |
|
sends an SMS Submit Report to an SMS over IP capable UE |
Mobile Terminated Features
These features relate to the SMS Delivery path from the network to the UE.
| Feature | What it does |
|---|---|
modifies the MSC address in Send Routing Info For SM responses to be the configured address of the IPSMGW. This ensures that subsequent MAP MT Forward Short Message requests are sent to the IPSMGW. |
|
stores SMS Routing information retrieved from an HLR in Cassandra. The stored data includes additional correlation information. |
|
retrieves Circuit Switched routing information from the Cassandra Database and stores it into session state. |
|
reads Third Party Registration information stored in the Cassandra Database, and writes it into session state. |
|
delivers an SMS encapsulated in SIP (SMS Over IP) to the UE |
|
delivers a Short Message towards the MSC or SGSN, performing TCAP application context negotiation as necessary |
|
generates a correlation IMSI when responding to a SRI request. It uses the Correlation Resource Adaptor to allocate an IMSI based on the MCC and MNC. |
|
increments (or creates) a row in the Cassandra cluster for the current MSISDN, to be used as the RP Message Reference, writing the value into session state. |
|
links incoming SIP delivery reports with the sentinel session that the delivery report is responding to. |
Preserve Call Id Over B2BUA
The SIP B2BUA feature can be configured to preserve the Call-ID header across both legs of a B2BUA’d session. Certain MT flows
require the correlation of an incoming request with an existing IP-SM-GW session. This is achieved using the In-Reply-To header of
the incoming request. Depending on network configuration this may require the preservation of the Call-ID header when B2BUA’ing the
MESSAGE request onwards. By default and in typical deployments, this behavior is not configured. It should only be configured if
required. For more information on this configuration option read the B2BUA Feature Configuration
documentation.
Short Message Memory Available Features
These features relate to the Short Message Memory Available Submission path from the UE to the network. This occurs when the UE indicates that it has memory available to receive short messages, having previously indicated that it did not have available memory.
| Feature | What it does |
|---|---|
extracts the MSISDN from a SMMA message, then sends an RP-ACK to the SMMA request |
Registrar features
These features relate to Third Party Registration
| Feature | What it does |
|---|---|
sets a session state field based on the presence of the “+g.3gpp.smsip” parameter in first party SIP Register request Contact headers and the subscriber MSISDN session state field. |
|
sends a MAP AnyTimeModification request to HLR to set the IP-SM-GW address and set active flag to true when a user registers. |
USSI features
These features relate to processing USSI requests.
| Feature | What it does |
|---|---|
analyses an incoming INVITE request to determine if it is a USSI request. |
|
handles the SIP side of the USSI conversation. |
|
converts USSD text to/from encoded forms |
|
generates and sends a USSD request to an HLR, and handles the result |
