Cisco Cisco ASR 5000

Page of 9109
  Call Control Profile Configuration Mode 
local-cause-code-mapping peer-node-unknown  ▀   
 
Command Line Interface Reference, StarOS Release 18  ▄  
 
   
2021 
local-cause-code-mapping peer-node-unknown 
Configures the reject cause code to send to a UE when peer node resolution is not successful. 
Product
 
MME 
Privilege
 
Administrator 
Mode
 
Exec > Global Configuration > Call Control Profile Configuration 
configure > call-control-profile profile_name
 
Entering the above command sequence results in the following prompt: 
[local]host_name(config-call-control-profile-profile_name)# 
Syntax
 
local-cause-code-mapping peer-node-unknown emm-cause-code { eps-service-not-allowed-in-
this-plmn | network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | 
roaming-not-allowed-in-this-tracking-area | tracking-area-not-allowed } 
 
remove local-cause-code-mapping peer-node-unknown  
remove local-cause-code-mapping peer-node-unknown
 
Removes the configured cause code mapping. 
peer-node-unknown emm-cause-code { eps-service-not-allowed-in-this-plmn | 
network-failure | no-suitable-cell-in-tracking-area | plmn-not-allowed | roaming-
not-allowed-in-this-tracking-area | tracking-area-not-allowed }
 
Specifies the EPS Mobility Management (EMM) cause code to return when the peer node resolution is not 
successful. 
 
eps-service-not-allowed-in-this-plmn
 
 
network-failure
 
 
no-suitable-cell-in-tracking-area
 
 
plmn-not-allowed
 
 
roaming-not-allowed-in-this-tracking-area
 
 
tracking-area-not-allowed
 
Usage 
Use this command to configure the cause code returned to a UE when peer node resolution is not successful. 
By default, the MME sends the UE the #9 - MS identity cannot be derived by the network cause code 
when encountering this condition.  
During processing of a TAU REQUEST, the resolution of a peer MME that had allocated the temporary 
identity that is signaled to the UE takes several steps in the MME. This resolution can be done based on DNS