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 allowlist. |