This feature determines Mobile Country Code (MCC), Mobile Network Code (MNC), and ISO Country Code values for the subscriber.
This data can then be included in Credit Control Requests (CCR)s by mappers and Call Detail Records (CDR)s by the AVP CDR feature.
This feature is an extension of the Sentinel SIP Extract Network Info feature. It implements the same behaviour as that feature for SIP message triggers, but also includes behaviour for dealing with TCAP message triggers.
Feature cheat sheet
Feature Script Name |
IPSMGWExtractNetworkInfo |
---|---|
Call-Type |
Orig or Term |
Session Plan |
default, MOFSM, SMMA, MTFSM_PS_CS, MTFSM_CS_PS, MTFSM_PS, MTFSM_DR, MTFSM_CS |
Execution Points |
Post_SipAccess_SubscriberCheck, Post_SubscriptionSubscriberCheck, Post_SipTransaction_SubscriberCheck, Post_SipThirdPartyAccess_SubscriberCheck |
Network Operator Config |
Yes |
Subscriber Config |
No |
POJO or SBB |
POJO |
Feature FSMs |
None |
Feature Parameters |
None |
SAS Support |
Yes |
RA Entity Links |
None |
Session State Inputs and Outputs
This feature uses all of the session state fields of its parent feature. For a list of these, see that features documentation.
In addition, it uses the following fields:
Statistics
IPSMGWExtractNetworkInfo 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 → IPSMGWExtractNetworkInfo
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.IPSMGWExtractNetworkInfo"
Name | Type | Description |
---|---|---|
Started |
Counter |
Incremented when the feature is triggered. |
FailedToStart |
Counter |
Incremented when the feature fails to start. |
FailedDuringExecution |
Counter |
Incremented when the feature fails while executing. |
IssuedWarning |
Counter |
Incremented when the feature issues a warning. |
TimedOut |
Counter |
Incremented when the feature times out during execution. |
AccessNetworkMccMncFoundInTrigger |
Counter |
Incremented when access network MCCs and MNCs are found in the triggering message. |
AccessNetworkMccMncFoundInRegistrationData |
Counter |
Incremented when access network MCCs and MNCs are found in registration data. |
CellularNetworkMccMncFoundInTrigger |
Counter |
Incremented when access network MCCs and MNCs are determined from a Cellular-Network header on the triggering message. |
UnableToDetermineAccessNetworkMccMnc |
Counter |
Incremented when access network MCCs and MNCs cannot be determined. |
VisitedNetworkMccMncFoundInRegistrationData |
Counter |
Incremented when the visited network MCC and MNC are found in registration data. |
VisitedNetworkMccMncFoundInTrigger |
Counter |
Incremented when the visited network MCC and MNC are found in trigger. |
UnableToDetermineVisitedNetworkMccMnc |
Counter |
Incremented when the visited network MCC and MNC cannot be determined. |
IsoCountryCodeFoundFromHeader |
Counter |
Incremented when an ISO country code is extracted directly from an access network info header. |
IsoCountryCodeFoundFromMccMnc |
Counter |
Incremented when an ISO country code is determined from an MCC and MNC value. |
IsoCountryCodeFoundFromHomeNetworkConfig |
Counter |
Incremented when an ISO country code is determined from home network configuration in Sentinel. |
UnableToDetermineAccessNetworkIsoCountryCode |
Counter |
Incremented when an ISO country code cannot be determined. |
IgnoringTrigger |
Counter |
Incremented when trigger is not a TCAP message or SIP request. |
TcapTrigger |
Counter |
Incremented when the feature is triggered on a TCAP message. |
SipRequestTrigger |
Counter |
Incremented when the feature is triggered on a SIP request. |
ImsiMccMncFound |
Counter |
Incremented when MCC and MNC is found in IMSI. |
UnableToDetermineImsiMccMnc |
Counter |
Incremented when an MCC and MNC for the IMSI cannot be determined. |
Configuration
This feature uses the same configuration profiles as the Extract Network Info feature. See:
Behaviour
SIP Request Triggers
When triggered by a SIP request, this feature will execute its parent feature’s behaviour as described here: Extract Network Info - Behaviour
TCAP Message Triggers
The IPSMGWExtractNetworkInfo feature extracts MCCs and MNCs from:
-
The access and visited network info headers found in registration records. This requires the Registration Lookup From Cassandra feature to run before this feature.
-
The
IMSI
. This requires the Fetch IMSI feature to run before this feature.
The resulting information is recorded in session state for use by the AVP CDR Feature feature when writing a CDR, as well as the charging features when forming charging requests.
The following OpenCloud extension AVPs are used to communicate MCC and MNC information in CCRs and CDRs:
-
OC-ACCESS-NETWORK-MCC-MNC
-
OC-VISITED-NETWORK-MCC-MNC
-
OC-IMSI-NETWORK-MCC-MNC
-
3GPP-IMSI-NETWORK-MCC-MNC
For Sentinel AVP definitions, please refer to Sentinel AVP Definitions in the Sentinel Administration guide.