The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Local Cause Code Mapping provides the operator with the flexibility to configure a preferred GMM cause code to be sent to the UE in response to various failures, such a MAP failures. This section identifies the various cause code mapping optionsand how they are configured.
Local Cause Code Mapping provides the operator with the flexibility to configure a preferred GMM cause code to be sent to the UE in response to various failures, such a MAP failures. This section identifies the various cause code mapping optionsand how they are configured.
This feature enables the operator to configure (map) preferred failure code information to send to the UE in reject messages.
Prior to release 16, the operator could map a preferred GMM reject cause code for the SGSN to send to a UE in place of MAP cause 'roaming not allowed' for MAP failures and to map a preferred GMM reject cause code to be sent in a RAU Reject for inbound peer SGSN address resolution failures.
Beginning with release 16, additional local cause code mapping is possible:
Each mapping of a cause code is configured slightly differently. Each is illustrated below.
The following configures the SGSN to include a preferred GMM cause code, in Reject messages to the UE, in place of MAP failure cause 'unknown-subscriber' for MAP failures and inbound RAU context transfer failures. Optionally, the Operator can map a specific GMM cause code if the SGSN receives additional MAP failure diagnostic information.
configure
call-control-profile profile_name
local-cause-code-mapping map-cause-code { roaming-not-allowed gmm-cause-code gmm-cause | unknown-subscriber { gmm-cause-code gmm-cause | map-diag-info { gprs-subscription-unknown gmm-cause-code gmm_cause | imsi-unknown gmm-cause-code gmm_cause } } }
end Notes:
Mapping is performed in the call control profile.
Run the show call-control-profile full name profile_name command and review the output. Look for the following lines to confirm the mapping configuration
Mapped Gmm Cause code for MAP cause Unknown Subscriber : <gmm-cause-if-configured>
MAP cause Unknown Subscriber with Diag Info Gprs Subscription Unknown : <gmm-cause-if-configured>
MAP cause Unknown Subscriber with Diag Info Imsi Unknown : <gmm-cause-if-configured> This configuration uses the existing rau-inter command in the call control profile configuration mode. There is a new keyword configures a GMM failure cause code to be sent in a RAU Reject to the UE due to context transfer failures.
configure
call-control-profile profile_name
rau-inter ctxt-xfer-failure failure-code fail_code
end Notes:
For more information about these commands, refer to the Command Line Interface Reference.
Mapping is performed in the call control profile.
Run the show call-control-profile full name profile_name command and review the output. Look for the following lines to confirm the mapping configuration
RAU Inter- Failure Code For Peer Sgsn Address Resolution : <gmm-cause>
RAU Inter- Failure Code For Context Transfer : <gmm-cause> The following procedures illustrates the commands used to configure SM cause codes to override the default cause codes sent in Deactivate PDP Request due to GTPC path failure. It is up to the person entering the configuration to determine which of the 4 cause codes should be the new cause code.
configure
call-control-profile profile_name
local-cause-code-mapping path-failure sm-cause-code { insufficient-resources | network-failure | reactivation-requested | regular-deactivation }
end Mapping is performed in the call control profile.
Run the show call-control-profile full name profile_name command and review the output. Look for the following lines to confirm the mapping configuration
Mapped SM Cause Code For Path Failure : <sm-cause> 
Feedback