Book1 Security Level

Disconnect the network

Reason for disconnection Failure scenario Reason for failure
element
The last call of the calling user has not been released yet,
AS AS sends 403 rejection with warning value "User is busy"
and the user initiates a second call, but the AS refuses.
403 Forbidden SCSCF sends 403 rejection with warning value "Number Analysis
SCSCF The called number is wrong.
Failed"
AS sends a 403 rejection with the warning value "internal error", and The user initiates a multi-party call, but the AS does not sign
AS
the called to field is "sip:[email protected]..." the service, and the AS refuses.
486 Busy Here UE or MGCF UE or MGCF issued a 486 rejection The called user is in a call
603 decline UE The called UE sends a 603 rejection The called user refused
SCC AS sends 480 messages with warning value "No appropriate The user switches before the ringing occurs, causing the call
AS
session for SRVCC/eSRVCC" to fail
The called party is a CS domain user, and call forwarding
AS SCCAS issued 480 with reason "channel type not implemented"
occurs during which aSRVCC occurs on the calling party.
CS domain disconnection, disconnection message REL with cause: 16
480 Temporarily Unavailable MGCF MGCF converts it to 480 and issues
Normal call clearing or 19 No answer from user
In fact, the connection has not been disconnected. SCCAS
The SCSCF replies 480 after receiving the SCCAS domain selection or HSS thinks that the user is in 4G, but the user status on
SCSCF result as the IMS domain, and the AS goes to the CS for roaming, and SCSCF is unregistered. After AS returns to invite, SCSCF
the called CSFB is connected. returns to 480, and AS goes to CS to take roaming again
and is called CSFB.
The 183 message sent by the SCP AS was accompanied by "P-Early-
SCP AS Media: sendrecv", and then it sent 487 to disconnect. The called The virtual short number dialed by the caller is incorrect.
number is a short number
SCC AS first issued 480 disconnection without warning and reason,
The user switches before the ringing occurs, causing the call
SCSCF SCSCF then issued 487 disconnection with warning value "CSCF
to fail
released the session because of USER DEREGISTRATION"
During the connection, the caller was dropped by 2\3G paging, which
caused the caller SCSCF to be disconnected, with the cause value Need to check whether the caller’s TCSI is signed to the
487 Request Terminated SCSCF
"SCSCF released the session because of PERMANENT anchor AS
TERMINATION".
The called is an IMS user from another province, and the other
ICSCF in other provinces province ICSCF returns 487 to disconnect, with the reason value "User The other user is busy
busy"
The called party is a CS user. After media negotiation is completed
and the calling UE responds with a 200 OK to update, the SAE-GW
SAE-GW EPC domain disconnection
sends a 487 disconnect to the UE with a warning "Cancel received on
initial invite" and sends a cancle to the SBC.
Mostly, the calling UE responds with 200 OK after receiving the
Since most of the terminals are VOLTE terminals that have
update, and then sends out a 580 after a few seconds. It can be seen
UE not been officially released, it is judged as the terminal
from the platform that the bearer establishment of both parties has
cause.
been successful.
After the called party replies to 183, a dedicated load is established, There is a patch on the EPC side to fix this problem. Before
and X2 switching occurs at the same time, and then the called party the patch is upgraded, this problem is judged to be a conflict
UE
replies to 580 after receiving the update with the warning value "Glare between the EPC test establishment special load and the X2
580 Precondition Failure
condition". switching process.
The called party is a CS user, and the calling party undergoes a
bSRVCC handover. After the MGCF forwards the 183 message to the
calling party, the calling party does not respond to prack. After the
MGCF Caused by SRVCC before the caller rings
MGCF retransmits the 183 several times, the timer expires and
releases the 580 disconnection with Warning: "16
sipsl_nc_sipi_bearer_time_out ."
The called party is 1259023+short number, and the calling party uses
one-phone dual-number service. The IAM message sent under VOLTE It was preliminarily judged to be a problem of cooperation
MGCF to the one-phone dual-number platform does not respond. After the between the Nokia West End Office and the one-machine
timeout, the platform returns a REL message and the MGCF forwards dual-number business.
it to 504.
The called party is a CS user. The calling party did not respond to
504 Gateway Time-out
prack after receiving the 183, or the calling party did not respond with
The call is affected by the wireless side environment,
MGCF 200 OK after receiving the update. After the MGCF retransmits the
resulting in no response timeout release.
183 several times, the timer expires and releases, and a 504
disconnect is issued.
Called CS user, MGCF did not receive APM after forwarding IAM, The CS domain process is abnormal, which leads to
MGCF
MGCF issued 504 disconnect after timeout disconnection.
The bSRVCC before the ringing occurs, and then SCCAS issues a
AS The bSRVCC before the ringing caused the disconnection
404 disconnection with the warning "Alerting switch release split call."

The called is an abnormal number, MGCF directly returns 404, Q850

MGCF The called number is abnormal and the call is disconnected.
Cause is "Unallocated (unassigned) number", and then AS plays.

The PSBC in other provinces is not equipped with a full

The user roams out of the province, and the PANI in the invite sent by LAMAP relationship, or the user still uses the PSBC in the
the roaming place PSBC to the province does not have the area code, province without re-establishing the PDN connection when
SCSCF
SCP does not do the short number translation, SCSCF sends 404 to the user leaves the province, and cannot correspond to the
disconnect, with the warning "Route Address Not Found" LAMAP. This scenario requires an upgrade of the MME and
PGW configuration. The group is advancing nationwide.
404 not found
There is data on ENUM, but no data on AS\HSS. When VOLTE calls
this user, when ICSCF checks HSS, HSS returns LIA with user In this case, you need to check the subscription data on the
ICSCF
unknown, and the caller hears the blank tone. ICSCF issues a 404 user AS\HSS
disconnect with warning "Route Address" Not Found".
The user dialed the short number, but did not sign SCPAS, and the
In this case, the user’s IFC contract data needs to be
SCSCF long and short number could not be translated. SCSCF sent a 404 for
checked
disconnection with the warning "Route Address Not Found".
After receiving the invite, the AS replies with a warning: "Get basic The data on the VOLTE AS is abnormal, the user will be
AS
data failed". restored after turning on and off the machine
The calling party initiates a video call, the called number is abnormal,
AS and the AS sends a 404 rejection with a Q850 cause: "Invalid number The called number is abnormal.
format (address incomplete)" or "Unallocated (unassigned) number".

5/27/2022 Huawei Proprietary - Restricted Distribution Page1of2

 Book1 Security Level

The calling party initiates a video call, the called number is abnormal,
AS and AS sends 484 to reject, with Q850 cause: "Invalid number format The called number is abnormal.
(address incomplete)"
The called number is abnormal, SCSCF sends 484 to disconnect, with
SCSCF The called number is abnormal.
484 Address Incomplete Q850 cause as "Invalid number format (address incomplete)".
When the called number is normal, the CSFB fails to fall back on the
called side and there is no response after the timeout, or the called
MGCF An abnormal disconnection occurred in the CS domain.
side does not return an ACM message, the MGCF sends a 484
message to the IMS domain to disconnect after the timeout.
The called party is a VOLTE user, and the called party shuts down.
When the called SCC AS queries the HSS, the HSS replies with 5001
HSS The called is turned off.
(user unknown), and the SCC AS issues a 480 disconnection with the
5001 warning: "The callee is not registered".
DIAMETER_ERROR_USER_UNKNO The called party is a CS user and turned off. Because the user has
WN services such as intra-city courier services, the calling SCP will query
HSS the called HSS for its domain selection information, the HSS will reply The called is turned off.
5001, and then the call will be sent to the CS domain, and the CS
domain will return to the ACM for playback.
After VoLTE AS and SCSCF exchange the Update message, the
terminal does not respond with 200 ok, and the 6s timer on the VoLTE
AS Terminal or wireless side problem.
AS device is triggered, and the VoLTE AS first 408 time out is
disconnected
After the calling VOLTE user initiates a call, the calling SCC AS issues
Need to check the user's AS subscription data or registration
AS a 500 disconnection with the warning "query adb failed", and no user
status.
data is queried in the VOLTE AS.
The called party did not receive the prack after receiving the 183
message from the invite, and PSBC sent out 500 to disconnect after
PSBC The calling terminal or wireless side problem.
repeated 183 retransmission without receiving the prack reply, with the
500 Internal Server Error warning "No Prack received for the sent 1XX".
MGCF sends out 500 to disconnect, with warning "release mgcf and
MGCF cs. ims should send tone based on status code.", it means that CS An abnormal disconnection occurred in the CS domain.
domain paging has no response, etc.
VoLTE users dial some short numbers, because the IMS domain Because IMS cannot distinguish the call source information
cannot distinguish the calling source information and add the area of the host and add the area prefix, the call is disconnected
Gateway bureau prefix, which causes the gateway office number to be disconnected during the analysis of the gateway office number. After the
during the analysis. The 500 message carries the Warning code "0 group issues the VOLTE short number data specification,
RELEASE FROM CC!". the solution will be produced.
CS domain sends REL with "Network out of order" or "Bearer
MGCF An abnormal disconnection occurred in the CS domain.
capability not authorized" cause value, MGCF forwards it to 500.
The called number is a fixed-line number from another province, and
the VoLTE user’s caller’s invite contains line b information. The remote
The failure caused by the parameter coordination between
IMS fixed-line phone does not support this field, and the call is
UE VOLTE terminal and IMS fixed-line terminal can be solved
rejected; after receiving the 488, the mobile phone drops back to 23G
after the group promotes SBC to filter line B.
and then initiates the call. The user does not perceive the first time
488 Not Acceptable Here failure.
The called number translation in Enum points to the ICSCF of VOBB,
and the user has no data in the fixed-line HSS, which causes the
The ENUM subscription data of the called number needs to
ICSCF ICSCF to fail to check HSS and the call fails. This may be caused by
be checked.
the user's contract with the enterprise communication assistant and the
data is not cleaned up.

5/27/2022 Huawei Proprietary - Restricted Distribution Page2of2