Академический Документы
Профессиональный Документы
Культура Документы
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
2012-10-20
First Edition
SJ-20120828144226-019|2012-10-20 (R1.0)
Contents
About This Manual ......................................................................................... I
Chapter 1 Call Failure Causes................................................................... 1-1
1.1 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified ..................... 1-1
1.2 ERR_SPS_RLSA_BSSAP_TE_T3230................................................................. 1-2
1.3 ERR_SPS_RLSA_BSSAP_TE_Tassignment ....................................................... 1-2
1.4 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect .................................. 1-3
1.5 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder................................. 1-4
1.6 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup ........................................................... 1-4
1.7 ERR_SPS_RLSA_BSSAP_TE_T303 .................................................................. 1-5
1.8 ERR_SPS_RLSA_BSSAP_TE_Txxp ................................................................... 1-6
1.9 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr ................ 1-7
1.10 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing............... 1-7
1.11 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy....................... 1-8
1.12 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing .............. 1-9
1.13 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed ........................................... 1-9
1.14 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail.............................................. 1-10
1.15 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer.....................1-11
1.16 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit .....................................1-11
1.17 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail ....... 1-12
1.18 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful ....... 1-13
1.19 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentServi
ce .................................................................................................................. 1-14
1.20 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption............. 1-14
1.21 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef ........................ 1-15
1.22 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail ................................. 1-15
1.23 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure ......... 1-16
1.24 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailur
e.................................................................................................................... 1-16
1.25 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved ............................... 1-17
1.26 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad .................................... 1-17
1.27 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange ......................................... 1-18
1.28 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId .................................. 1-19
1.29 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable ............................. 1-19
1.30 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId ........... 1-20
I
SJ-20120828144226-019|2012-10-20 (R1.0)
II
SJ-20120828144226-019|2012-10-20 (R1.0)
III
SJ-20120828144226-019|2012-10-20 (R1.0)
IV
SJ-20120828144226-019|2012-10-20 (R1.0)
1.120 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNEL_P
OWER ........................................................................................................... 1-71
1.121 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FCH_G
ATING ........................................................................................................... 1-72
1.122 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_PILOT
_GATING....................................................................................................... 1-73
1.123 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PUNC_
MODE ........................................................................................................... 1-74
1.124 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN ....... 1-74
1.125 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STEP_S
IZE ................................................................................................................ 1-75
1.126 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PUNC_
MODE ........................................................................................................... 1-76
1.127 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_SET
POINT ........................................................................................................... 1-77
1.128 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_PAT
TERN ............................................................................................................ 1-77
1.129 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_FR
AME_TYPE.................................................................................................... 1-78
1.130 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVAL
ID .................................................................................................................. 1-79
1.131 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALI
D ................................................................................................................... 1-80
1.132 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL ........... 1-80
1.133 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_N
SDUs............................................................................................................. 1-81
1.134 ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure ...................... 1-81
1.135 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_AbisdrCon
nectProccess_AbisdrConnectMsgProccess...................................................... 1-82
1.136 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOReqC
ellIsExisted..................................................................................................... 1-82
1.137 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExiste
d.................................................................................................................... 1-82
1.138 ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPrioritySe
rvice .............................................................................................................. 1-83
1.139 ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriorit
y.................................................................................................................... 1-83
VI
SJ-20120828144226-019|2012-10-20 (R1.0)
3.13 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstReleas
e_FSCHExistedCellReleasebyRCM................................................................... 3-7
3.14 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant ................. 3-7
3.15 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease .................... 3-7
3.16 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant ........ 3-8
3.17 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CLHRl
sInd ................................................................................................................. 3-9
3.18 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_
FSCHExistedCellReleasebyRCM .................................................................... 3-10
3.19 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_
RSCHExistedCellReleasebyRCM .................................................................... 3-10
3.20 SDM_Find_Fail_NoFCHLeg.............................................................................3-11
3.21 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH ........................3-11
3.22 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH........................ 3-12
3.23 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch................................ 3-12
3.24 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb ........................ 3-12
3.25 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail....................... 3-13
3.26 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail....................... 3-14
3.27 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Remov
edSCH........................................................................................................... 3-15
3.28 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCHReso
urceExtension ................................................................................................ 3-15
3.29 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch .............................. 3-16
3.30 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration ......................... 3-16
VII
SJ-20120828144226-019|2012-10-20 (R1.0)
4.10 ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSRCallSetu
p...................................................................................................................... 4-5
4.11 ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState.............. 4-5
4.12 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_atCellInfoIsInvalid...... 4-5
4.13 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIsNot
Matched........................................................................................................... 4-6
4.14 ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq .................................................. 4-6
4.15 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestReceive
d...................................................................................................................... 4-6
4.16 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived ........... 4-7
4.17 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived ..................... 4-7
4.18 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired ...................... 4-7
4.19 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired................. 4-8
4.20 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHOA
dd.................................................................................................................... 4-8
4.21 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHODr
op.................................................................................................................... 4-8
4.22 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemiHOA
dd.................................................................................................................... 4-9
4.23 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSCHExis
t....................................................................................................................... 4-9
4.24 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState.......... 4-9
4.25 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState.............. 4-10
4.26 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention ........ 4-10
4.27 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure ....... 4-10
4.28 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResourceAv
ailable.............................................................................................................4-11
4.29 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable ..........4-11
4.30 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped...........4-11
4.31 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked...........4-11
4.32 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable ......... 4-12
4.33 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut..................... 4-12
4.34 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified ................ 4-12
4.35 SOFTADD_CELL_ERROR ............................................................................. 4-13
4.36 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion .............. 4-13
4.37 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq .................................... 4-14
4.38 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchRep
ort.................................................................................................................. 4-15
4.39 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion ...... 4-16
VIII
SJ-20120828144226-019|2012-10-20 (R1.0)
IX
SJ-20120828144226-019|2012-10-20 (R1.0)
4.74 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCS
HConstructAmdfFCHSetup ............................................................................. 4-34
4.75 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHan
dlerAbisdfBTSSetup ....................................................................................... 4-35
4.76 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck_
SoftHandoffLegNoInvalid ................................................................................ 4-36
4.77 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_MC
DHSaveToCommonData................................................................................. 4-36
4.78 ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error ..................... 4-37
Glossary .......................................................................................................... I
X
SJ-20120828144226-019|2012-10-20 (R1.0)
Intended Audience
This manual is intended for:
l
l
Summary
Causes
Chapter 2, Call Drop
Causes
Chapter 3, Call Release
Causes
Chapter 4, Handoff
Failure Causes
Chapter 5, Registration
Failure Causes
Chapter 6, Other Failure
Causes
Describes the causes of call drop failures and the handling measures.
Describes the causes of call release failures and the handling measures.
Related Documentation
The following documentation is related to this manual:
l
SJ-20120828144226-019|2012-10-20 (R1.0)
II
SJ-20120828144226-019|2012-10-20 (R1.0)
Chapter 1
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified
Failure Cause
During call setup, the MSC sends a ClearCommand message to release the
call. The cause is unknown.
Failure Analysis
Possible Solution
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified
MSCClearCommand
ClearCommandCauseA
ClearCommandCauseCause_A_CallProcessing
Layer30x1fBSC
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unsp
ecified
1-1
SJ-20120828144226-019|2012-10-20 (R1.0)
1.2 ERR_SPS_RLSA_BSSAP_TE_T3230
Failure Name
ERR_SPS_RLSA_BSSAP_TE_T3230
Failure Analysis
Possible Solution
ERR_SPS_RLSA_BSSAP_TE_T3230
BSSAPMSCCMServiceRequestPagingResponse
SccpConnectT3230
1.
2.
1.3 ERR_SPS_RLSA_BSSAP_TE_Tassignment
Failure Name
Failure Analysis
ERR_SPS_RLSA_BSSAP_TE_Tassignment
When a mobile station originates a call or is called, the BSSAP sends an
EV_S_AvfServiceAssignment message to the Data Service Management
Platform (DSMP), but fails to receive an EV_S_AvrAssignmentComplete
message or EV_S_AvrAssignmentFailure message from the DSMP before
timer Tassignment expires.
The possible failure causes are as follows:
1. Timer Tassignment expires too early.
2. The DSMP is configured with too many instances (more than the
number of DSMP instances that can be supported).
3. DSMP CPU utilization is too high.
4. SDM activation expires.
Handling Measure
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_BSSAP_TE_Tassignment
BSSAPDSMPEV_S_AvfServiceAssignment
DSMPEV_S_AvrAssignmentCompleteEV_S_AvrAssignmentFailureBSSAP
Tassignment:
Tassignment
DSMPDSMP
DSMPCPU
SDM
1.
CMPTassignment6000 6
2.
RMPDSMPDSMP
DSMP
3.
DSMPCPUDSMP
4.
SDMSDUCHMBSC
BTS
SDU
1.4 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDis
connect
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect
Failure Analysis
Possible Solution
The mobile station did not assign numbers correctly on the MSC side.
1. Use a database probe to verify that the signaling point state on the
CMP is 0.
2. Verify that the BSC and the MSC are configured with local and peer
SSNs (0, 1, and 254).
3. Verify that the IMSI and ESN of the mobile station distribute numbers
correctly on the MSC side.
4. Verify that the cell CI in the call origination message CMServiceRequest
is configured correctly on the MSC side.
1-3
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect
MSCCMServiceRequestPagingResponse
SccpDisconnectSCCP
SSN
MSC
CIMSCCI
1.
CMP0
2. BSCMSCSSN01254
3.
IMSIESNMSC
4.
CMServiceRequestCIMSC
1.5 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSRelea
seOrder
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder
Failure Analysis
When a call is set up, the mobile station initiates a release on the control
channel.
Possible Solution
No troubleshooting is required.
ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder
1.6 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup
Failure Name
ERR_SPS_RLSA_BSSAP_TE_Tfchsetup
Failure Cause
1-4
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
When a call is set up, the timer Tfchsetup on CMP expires. The BSC
sends an AbisdfBTSSetup message to BTS to request the fundamental
channel establishment, but the AbisdrBTSSetupAck message that indicates
fundamental channel establishing is successful or unsuccessful is not
received from BTS.
The possible failure causes are as follows:
l
Possible Solution
ERR_SPS_RLSA_BSSAP_TE_Tfchsetup
Tfchsetup
BSCBTSAbisdfBTSSetup
BTS
AbisdrBTSSetupAckCMPTfchsetup
Tfchsetup50005
BTS
CCMCPU
1.
Tfchsetup
5000
2.
BTSCEFO
3. CCMCPUCCMCPU
1.7 ERR_SPS_RLSA_BSSAP_TE_T303
Failure Name
ERR_SPS_RLSA_BSSAP_TE_T303
Failure Cause
1-5
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Possible Solution
1. Verify that the timer T303 on the CMP is set to the default value 6000
(6 seconds).
2. T303 indicates that the MSC side has a problem in processing the call.
Use MSC tools to locate the failure causes.
ERR_SPS_RLSA_BSSAP_TE_T303
T303
MSCCMServiceRequestPagingResponse
MSCAssignmentRequest
CMPT303
T303
MSC
1.
CMPT30360006
2. MSCMSCT303MSC
MSC
1.8 ERR_SPS_RLSA_BSSAP_TE_Txxp
Failure Name
ERR_SPS_RLSA_BSSAP_TE_Txxp
Failure Cause
Failure Analysis
Handling Measure
1. Check the setting of timer Txxp on the CMP. The default value is 6
seconds.
2. Locate the call failure causes on the MSCe side.
1-6
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_BSSAP_TE_Txxp
Txxp
CallHandlerMSCe
A1rAssignmentCompletApTxxp
MSCeA1pfBearerUpdateRequest
TxxpMSCeA1pfBearerUpdateRequest
Txxp
MSCe
1.
CMPTxxp6
2. MSCeTxxpMSCe
MSCe
1.9 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNe
tAddrByLogicAddr
Failure Name
ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr
Failure Cause
Failure to retrieve the board network address based on the logical board
address.
Failure Analysis
When the BSC sends messages to the BTS, it invokes the database
interface to retrieve the BTS address. If it fails to invoke, the failure cause
will be reported.
Handling Measure
ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr
BSCBTSBTS
AbisAbis
1.10 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_CallProcessing
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing
1-7
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
When a call is set up, the BSC receives a ClearCommand message from
the MSC.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing
MSC
MSCCallProcessing(0x09)
ClearCommand
MSC
MSC
1.11 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_UserBusy
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy
Failure Cause
When a call is set up, the BSC receives a ClearCommand message sent
from the MSC, and the cause value in the CauseLayer3 field carried by
this message is 0x11, which indicates that the called user is busy. This
is a normal release.
Failure Analysis
Handling Measure
No troubleshooting is required.
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy
BSCMSCClearCommand
CauseLayer30x11,
1-8
SJ-20120828144226-019|2012-10-20 (R1.0)
1.12 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_NormalClearing
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing
Failure Cause
When a call is set up, the BSC receives a ClearCommand message sent
from the MSC, and the cause value in the CauseLayer3 field carried by this
message is 0x10, which indicates it is a normal release.
Failure Analysis
The possible failure cause is as follows: the release is initiated on the MSC
side.
Handling Measure
No troubleshooting is required.
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing
BSCMSCClearCommand
CauseLayer30x10
MSC
1.13 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed
Failure Name
ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed
Failure Cause
When a call is set up, the BSSAP module detects that the instance number
is used during instance number distribution.
Failure Analysis
Possible Solution
ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed
BSSAP
BSSAP
1-9
SJ-20120828144226-019|2012-10-20 (R1.0)
1.14 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
When a call is set up, the BSC sends an AbisdfBTSSetup message to the
BTS to request the BTS to establish a fundamental channel. However,
all the cells in the AbisdrBTSSetupAck returned by the BTS fail to be
established.
Failure Analysis
Possible Solution
FO shortage.
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
BSCBTSAbisdfBTSSetupBTS
BTSAbisdrBTSSetupAck
CECE
WASH
FO
UID
1-10
SJ-20120828144226-019|2012-10-20 (R1.0)
1. AbisdrBTSSetupAck
2.
0x5101CE
0x5102CE
0x5103CE
0x5105WalshCode
0x5106UID
CE
3.
4.
UID
5.
CHMCE
6.
BSCBTS
1.15 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_NoAnswer
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer
Failure Cause
When a call is set up, the BSC receives a ClearCommand message sent
from the MSC, and the cause value in the CauseLayer3 field carried by this
message is 0x13, which indicates it rings without an answer. This is normal.
Failure Analysis
Handling Measure
No troubleshooting is required.
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer
BSCMSCClearCommand
CauseLayer30x13
MSC
1.16 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetC
ircuit
Failure Name
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit
Failure Cause
1-11
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
The CIC state on the MSC side and that on the BSC side are different.
The CIC code on the MSC side and that on the BSC side are different.
1. Verify that the CIC state on the MSC side and that on the BSC side
are consistent.
2. Verify that the PCM codes on both the MSC and BSC sides are
consistent with the E1 cable.
Further
Troubleshooting
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit
MSC
MSCBSCCIC
MSCBSCCIC
1.
MSCBSCCIC
2.
MSCBSCPCME1
3.
MSC
1.17 ERR_SPS_RLSA_BSSAP_FchSetup_SendChanne
lAssignment_AllBtsFail
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail
Failure Cause
When a call is set up, the Extended Channel Assignment Message to all
BTS fails to be sent.
Failure Analysis
1-12
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail
ECAM/CAM
ECAM/CAM
ECAMPN/
ECAM
ECAMabpm/hgm
BSCBSC
1.
2.
1.18 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_HandoffSuccessful
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful
When a call is being set up or during a call, if a ClearCommand message
sent from the MSC is received, the cause value carried in ClearCommand is
"hard handoff is successful".
Failure Analysis
Handling Measure
If the failure occurs when a call is being set up, contact MSC maintenance
personnel for troubleshooting.
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful
MSCClearCommandClearCommand
MSCClear Command
1-13
SJ-20120828144226-019|2012-10-20 (R1.0)
MSC
1.19 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_SemiConcurrentService
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrent
Service
Failure Cause
When a call is set up, during the forward fundamental channel establishment,
the ClearCommand message sent from the MSC is received, and the cause
value carried in ClearCommand is "pseudo concurrent service".
Failure Analysis
When the data service is started, there is a new voice incoming call. The
MSC sends a ClearCommand message to request the MS to enter Dormant
state.
Handling Measure
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentSer
vice
MSCClearCommand
ClearCommand
MSCClearCommandMSDormant
MSC
1.20 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_I
nvalidServiceOption
Failure Name
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption
Failure Cause
The Service Option (SO) carried in the call origination message is invalid.
Failure Analysis
Handling Measure
Determine what the SO is in the call origination message and if the terminal
is old or faulty.
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption
1-14
SJ-20120828144226-019|2012-10-20 (R1.0)
SO
SOSOSO
SO
1.21 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_S
ccpId2CallRef
Failure Name
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef
Failure Cause
When an SCCP connection number is added into the HASH entry of the
call reference number, the Hash operation fails.
Failure Analysis
Handling Measure
Check the fault probe and take measures after identifying the cause.
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef
SCCPHASHHash
Hash
1.22 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsPar
aFail
Failure Name
ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail
Failure Cause
The 97D test fails to obtain the MSID of the terminated call.
Failure Analysis
Handling Measure
Save fault probe information and contact the local ZTE office.
ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail
97DMSId
1-15
SJ-20120828144226-019|2012-10-20 (R1.0)
1.23 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComm
and_EquipmentFailure
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure
Failure Cause
When a call is set up, the MSC sends a ClearCommand message to release
the call, and the failure cause is equipment failure.
Failure Analysis
The MSC has an internal problem, and contact MSC maintenance personnel
for troubleshooting.
Possible Solution
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure
MSCClearCommand
MSCMSC
1.24 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_AuthenticationFailure
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFai
lure
Failure Cause
When a call is set up, the MSC sends a ClearCommand message to release
the call due to authentication failure.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailu
re
MSCClearCommand
MSC
1-16
SJ-20120828144226-019|2012-10-20 (R1.0)
1.25 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreR
emoved
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved
Failure Cause
During call setup, the channel board detects that the RCM sends an
EV_S_AbisdrTargetRemovalRequest message to the BSSAP to release the
call. After receiving the message, the BSSAP releases the call.
Failure Analysis
Possible Solution
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved
RCMRCM
BSSAPEV_S_AbisdrTargetRemovalRequestBSSAP
Tassingment6
Abis
1.
2.
Abis
3.
BTS
4.
1.26 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTabl
eBad
Failure Name
ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad
Failure Cause
During data service setup, SPCF is not detected in the normal state.
Failure Analysis
No RP link is available.
No UPCF is available.
1-17
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad
SPCF
PCF
RP
UPCF
1.
PCF
2.
PCFPDSNPDSN
3.
UPCF
1.27 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange
Failure Name
ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange
Failure Cause
During call setup, the mobile station is beyond the RTD distance limit of
the cell.
Failure Analysis
Handling Measure
The distance between the MS and the BTS is out of the specified range.
ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange
RTD
1.
2.
RTD
OMC
RTD
1-18
SJ-20120828144226-019|2012-10-20 (R1.0)
1.28 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOff
iceId
Failure Name
ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId
Failure Cause
The network has multiple signaling points, and the correct office direction
number fails to be selected.
Failure Analysis
1. The data service paging response cannot select the correct office
direction number.
2. The voice originating call and paging response, data service originating
call, and other service paging and paging response cannot select the
correct office direction number.
Handling Measure
1. Verify that the office direction selection switch for data paging response
(DataPagingRspOfficeIdSelect) is set correctly.
2. Verify that the selection switch for common office direction
(CallOfficeIdSelect) is set correctly.
ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId
1. DataPagingRspOfficeIdSelect
2.
CallOfficeIdSelect
1.29 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeU
navailable
Failure Name
ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable
Failure Cause
The network has multiple signaling points. The state of the selected office
direction is abnormal and results in call failure.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable
1-19
SJ-20120828144226-019|2012-10-20 (R1.0)
1.30 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignR
eq_InvalidMSCOfficeId
Failure Name
ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId
Failure Cause
The network has multiple signaling points. The office direction number in
the A1fAssignmentRequest message is wrong.
Failure Analysis
Handling Measure
Save the signaling track, service observation, and fault probe, and contact
the R&D personnel for troubleshooting.
ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId
A1fAssignmentRequest
1.31 ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOr
der
Failure Name
ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder
Failure Cause
During call setup, the terminal refuses the forward message from the BSC.
Failure Analysis
If the user is called while preparing to dial at the fixed station, the
terminal will refuse the ECAM/CAM messages.
Possible Solution
ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder
1-20
SJ-20120828144226-019|2012-10-20 (R1.0)
ECAM/CAM
1.32 ERR_SPS_RLSA_BSSAP_Other_Encode_A1Ms
gInBSC
Failure Name
ERR_SPS_RLSA_BSSAP_Other_Encode_A1MsgInBSC
Failure Cause
Failure Analysis
Handling Measure
1.33 ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMs
gInBSC
Failure Name
ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMsgInBSC
Failure Cause
Failure Analysis
The coding failure may result from an error in the type, assignment mode,
format or length of the air interface message.
Handling Measure
1.34 ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMs
gInBSC
Failure Name
ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMsgInBSC
Failure Cause
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
The decoding failure may result from an error in the type, format or length of
the air interface message.
Handling Measure
The failure results from an incorrect air interface message. If the failure
occurs occasionally, no troubleshooting is required.
If the failure occurs frequently, contact terminal maintenance personnel for
troubleshooting.
1.35 ERR_SPS_RLSA_BSSAP_TE_Ta1_4
Failure Name
ERR_SPS_RLSA_BSSAP_TE_Ta1_4
Failure Cause
Failure Analysis
After an A1rReset message is sent to the MSC, the MSC does not respond
before the Ta1_4 timer expires. The A1rReset message is retransmitted 30
times at most, and then the system enters the normal operating status.
Handling Measure
1.36 ERR_SPS_RLSA_BSSAP_PoorPilot
Failure Name
ERR_SPS_RLSA_BSSAP_PoorPilot
Failure Cause
Failure Analysis
When the Reject Weak Pilot switch is enabled, the system will report the
exception if the pilot strength carried in the originating call message is lower
than the threshold set in the OMC.
Handling Measure
Verify that the setting of the threshold is reasonable. If the exception occurs
frequently, check the local signal or contact the local ZTE office.
1.37 ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHM
sg_AllBtsFail
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHMsg_AllBtsFail
Failure Cause
Failure Analysis
The failure may result from intermittent bit error bursts over the Abis link.
Handling Measure
Check the Abis link. If it is abnormal, contact the local ZTE office.
1-22
SJ-20120828144226-019|2012-10-20 (R1.0)
1.38 ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo
Failure Name
ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo
Failure Cause
A failure occurs when the database EV_D_S_GetLinkAndLacNumByModule_V interface is invoked to get the signaling link message.
Failure Analysis
Handling Measure
1.39 ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier
Failure Name
ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier
Failure Cause
Failure Analysis
Handling Measure
1.40 ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdC
ellIdCrId
Failure Name
ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdCellIdCrId
Failure Cause
Failure Analysis
Handling Measure
1.41 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tw
aitorder
Failure Name
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder
Failure Cause
Failure Analysis
If frame number checking is enabled, the BTS and the BSC have
different clocks.
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder
MS
BTSBSC
1.
2.
CHMSDU
3.
ABPMBSC
4.
BTS
BTSBSC
GPSBTSBSCGCM
5.
ABPMDTBDSM
1.42 ERR_SPS_RLSA_BSSAP_Other_DifferenceInFw
dOrRevRC
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_Other_DifferenceInFwdOrRevRC
During a call test, the forward RC handoff judgment and reverse RC handoff
judgment of the fundamental channel are different.
Failure Analysis
The RC that is configured for the call test and its SO do not match.
1-24
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
1.43 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNF
ailure
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure
Failure Cause
Failure Analysis
Handling Measure
Further
If the problem persists, capture the call failure signaling and contact the
Troubleshooting
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure
MSMS
BSSVTC
1.
2. BSSVTC
8K+EVRC
3.
4.
1.44 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tp
cfinfol3
Failure Name
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3
1-25
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
During data service call setup, after the A8 link is established, the DSPM
sends an Abaf_PCFInfoL3 message to the SDM, but fails to receive a
response in Tpcfinfol3 (3s), and timer Tpcfinfol3 expires.
Failure Analysis
Possible Solution
1. Verify that the setting of timer Tpcfinfol3 on the DSMP board is correct
(default value: 3 s).
2. Verify that the corresponding SDU operates properly, and there is no
abnormal reset or switchover.
3. Ensure correct version and proper operation of the SDU.
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3
A8DSPMSDMAbaf_PCFInfoL3
Tpcfinfol33 sTpcfinfol3
Tpcfinfol3
SDU
1. DSMPTpcfinfol33 s
2.
SDU
3.
SDU
1.45 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_T
fschbstreq
Failure Name
Failure Cause
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq
In FSCH establishment, after the BSC sends a BurstRequest message,
the BurstResponse message from the BTS is not received, and timer
Tfschbstreq expires.
Failure Analysis
Possible Solution
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq
FSCHBSCBurstRequestTfschbstreq
BTSBurstResponse
1-26
SJ-20120828144226-019|2012-10-20 (R1.0)
Abis
1.
Tfschbstreq500 ms
2.
3. CCMABPMDTBDSM
1.46 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PD
SNDenied_Reason_Unspecified
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Uns
pecified
Failure Cause
During data service call setup, the A8 link setup fails. When the cause value
that the PDSN brings to the DSPM is 0x80, the failure cause is reported by
the DSPM.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Un
specified
A8PDSNDSPM
0x80DSPM
A10
PCF
A10
1.47 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8
setup
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup
Failure Cause
During data service call setup, the A8 link establishment expires: The
DSPM sends an A9SetupA8 message to the PCF, but fails to receive a reply
message in Ta8setup (3 s).
1-27
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Possible Solution
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup
A8DSPMA9SetupA8
PCFTa8setup3 s
OMCPCF IP
PCF
1. DSMPTa8setup3 s
2.
OMCPCF IP
3.
PCF
1.48 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDS
NDenied_Reason_Administratively_Pohibited
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_
Administratively_Pohibited
Failure Cause
During data service call setup, the A8 link setup fails when the cause value
that the PDSN brings to the DSPM is 0x81, and the failure cause is reported
by the DSPM.
Failure Analysis
Handling Measure
1-28
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_Ad
ministratively_Pohibited
A8PDSNDSPM
0x81DSPM
A10
PCF
A10
1.49 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCF
Denied_PDSN_Resource_Unavailable
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resour
ce_Unavailable
Failure Cause
During data service call setup, the A8 link setup fails. The cause value that
the PCF brings to the DSPM is that the PDSN resource is unavailable.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resour
ce_Unavailable
A8PCFDSPM
PDSN
A10
PDSN
1.
A10
2.
PDSN
1.50 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SC
HHOnUmrSCHRequestMsg_FCHNotExisted
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques
tMsg_FCHNotExisted
1-29
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
The data service fundamental channel receives a message from the SCH
for setup.
Failure Analysis
The possible failure cause is as follows: The call origination flow has not
finished.
Handling Measure
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques
tMsg_FCHNotExisted
1.51 ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_
SCHHOnFwdAllBurstResponse_NoCommitedCell
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstR
esponse_NoCommitedCell
Failure Cause
Failure Analysis
Shortage of BTS resources, such as CE, power, Walsh code, and UID.
Handling Measure
Analyze the current traffic of this BTS and check the occupancy of all
resources. If the occupancy state accords with traffic capacity, the resource
shortage is the failure cause of setting up the supplementary channel. If the
occupancy state is greatly different from the traffic capacity,
1. Verify that this BTS operates properly and the version is correct.
2. Verify that the resources are not blocked and the resource state is
correct.
3. If the above are normal, maybe the resources such as CE, power,
Walsh code, and UID are occupied by other requests.
ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstR
esponse_NoCommitedCell
BSCBTS
BTSCEWalshUID
1-30
SJ-20120828144226-019|2012-10-20 (R1.0)
BTS
1.
BTS
2.
3.
4.
1.52 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnAcrBSCAddChannelItemAck_AddChannel
ItemFailed
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddCha
nnelItemAck_AddChannelItemFailed
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddCha
nnelItemAck_AddChannelItemFailed
ENTRY3
BLOCK4
COLLISION5
UID7
1.
ABPMIBBE
2.
1-31
SJ-20120828144226-019|2012-10-20 (R1.0)
1.53 SDM_Activate_Fail_AcquirePreambleFail_Normal
Failure Name
Failure Analysis
SDM_Activate_Fail_AcquirePreambleFail_Normal
The MS capture fails; The BSC has not received Preamble sent by the MS
before timeout, but Idle frames can be received. There are many reasons for
this fault. Any problem in the system can cause failure in MS capture, such
as wrong CHM version, inconsistency in parameters for the MS and those
of the base station, long code error, inconsistent RC, and PN offset error.
Possible Solution
SDM_Activate_Fail_AcquirePreambleFail_Normal
BSCPreamble
Idle
CHM
RCPN
1.
CHM
2.
3.
RB_FWDCECE
4.
CE
1.54 SDM_Activate_Fail_AcquirePreambleFail_NoRe
vFrm
Failure Name
SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm
Failure Analysis
The BSC cannot receive the reverse traffic frame sent by the BTS before
the timer expires. There are many possible causes:
Possible Solution
The channel list is incorrectly added on either the BTS or the BSC.
SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm
1-32
SJ-20120828144226-019|2012-10-20 (R1.0)
BTSBSC
BSCBTS
Abis
BTSBSC
1.
Abis
2.
BSCBTS
3.
CHMCE
1.55 SDM_Find_Fail_WaitConfigVTCTimeout
Failure Name
SDM_Find_Fail_WaitConfigVTCTimeout
Failure Cause
After SDM activation, the SDM does not receive the EV_S_AbafStartVocoderCoding message sent by the DSPM before the timer expires.
Failure Analysis
SDM_Find_Fail_WaitConfigVTCTimeout
1-33
SJ-20120828144226-019|2012-10-20 (R1.0)
SDMDSPMSDM
EV_S_AbafStartVocoderCoding
l
BS
BSBS
BSBSRC
EV_S_AbafStartVocoderCodingSDM
1.
EV_S_UmfBSOrder
EV_S_UmrMSOrder
2.
MSBSMS
BS
3.
EV_S_AbafStartVocoderCoding
DSPM
1.56 SDM_Find_Fail_WaitConfigRLPTimeout
Failure Name
SDM_Find_Fail_WaitConfigRLPTimeout
Failure Analysis
Handling Measure
SDM_Find_Fail_WaitConfigRLPTimeout
SDMEV_S_AbafPCFInfoL3
1.57 SDM_Link_Fail_RSCHLegLinkFail
Failure Name
SDM_Link_Fail_RSCHLegLinkFail
Failure Analysis
The RSCH leg does not receive the frames sent from the reverse channel
in 18 s.
Handling Measure
1. Check the signaling and verify that the CHM has released the leg.
2. Verify that the reverse link has no problem.
3. Check CHM statistics for frame receiving and sending.
1-34
SJ-20120828144226-019|2012-10-20 (R1.0)
SDM_Link_Fail_RSCHLegLinkFail
18 s
1.
CHM
2.
3.
CHM
1.58 SDM_Activate_Fail_InitVocoderFail
Failure Name
SDM_Activate_Fail_InitVocoderFail
Failure Cause
Failure Analysis
Handling Measure
1. If the SDU board utilization ratio is too high, add an additional new
board.
2. If the SDU board is normal but the fault persists, contact the local ZTE
office.
SDM_Activate_Fail_InitVocoderFail
SDMSDUCPU
1.
SDUSDU
2.
SDU
1.59 SDM_OprVocoder_Fail_WaitStartVocoderCodin
gAckTimeOut
Failure Name
SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut
Failure Cause
The SDM cannot receive an ACK message from the VTC after sending a
startVocoderCoding message to the VTC.
Failure Analysis
Handling Measure
SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut
1-35
SJ-20120828144226-019|2012-10-20 (R1.0)
SDMVTCstartVocoderCodingVTCACK
startVocoderCoding
ACK
1.60 SDM_Activate_Fail_MsgParaFail
Failure Name
SDM_Activate_Fail_MsgParaFail
Failure Cause
Handling Measure
Check the SDM fault probe message to locate the wrong parameter(s).
Check the AbafActivateSDM message in signaling tracing to locate the
fault and determine whether Layer 3 is incorrectly written or it is an SDM
process problem.
SDM_Activate_Fail_MsgParaFail
SDMAbafActivateSDM
SDM
AbafActivateSDMSDM
1.61 DBS_STASTIC_FWDFCHCE_REVCE_LACK
Failure Name
DBS_STASTIC_FWDFCHCE_REVCE_LACK
Failure Cause
When the MS originates a call or is called, the basic channel fails to be set
up due to inadequate forward or reverse CEs.
Failure Analysis
Possible Solution
DBS_STASTIC_FWDFCHCE_REVCE_LACK
MSCE
1-36
SJ-20120828144226-019|2012-10-20 (R1.0)
CE
1.
2.
RB_FWDCECE0CE
INDEX0~31
3.
RB_REVCECE0CE
INDEX64~95
4.
CE
1.62 DBS_STASTIC_FWDFCHCE_LACK
Failure Name
DBS_STASTIC_FWDFCHCE_LACK
Failure Cause
When the MS originates a call or is called, the basic channel fails to be set
up due to inadequate forward CEs on the 5K channel board.
Failure Analysis
Possible Solution
DBS_STASTIC_FWDFCHCE_LACK
MS5KCE
CE
1.
2.
RB_FWDCECE
3.
CE
1.63 DBS_STAT_WALSHCODE_LACK
Failure Name
DBS_STAT_WALSHCODE_LACK
Failure Cause
Failure Analysis
Possible Solution
DBS_STAT_WALSHCODE_LACK
1-37
SJ-20120828144226-019|2012-10-20 (R1.0)
MSWALSHCODE
WALSHCODE
1.
2.
WALSHCODE
1.64 DBS_STAT_UID_LACK
Failure Name
DBS_STAT_UID_LACK
Failure Cause
Failure Analysis
Possible Solution
DBS_STAT_UID_LACK
MSIPUID
1.
2.
R_UIDLeftBandWidth9
1.65 DBS_STAT_NO_RESOURCE_LACK
Failure Name
DBS_STAT_NO_RESOURCE_LACK
Failure Cause
Failure Analysis
Possible Solution
DBS_STAT_NO_RESOURCE_LACK
1-38
SJ-20120828144226-019|2012-10-20 (R1.0)
1.66 FCH_NUMBER_TWO
Failure Name
FCH_NUMBER_TWO
Failure Cause
When a supplementary channel is being set up, the subscriber has two
basic data channels.
Failure Analysis
Possible Solution
FCH_NUMBER_TWO
1.
BTS
2.
DSPMRCM
1.67 ARRIVE_TIME_ERROR
Failure Name
ARRIVE_TIME_ERROR
Failure Cause
Failure Analysis
Possible Solution
ARRIVE_TIME_ERROR
1-39
SJ-20120828144226-019|2012-10-20 (R1.0)
Abis
BTSBSC
1.
BTSBSC
2.
Abis
1.68 NO_SYSTEM_TIME
Failure Name
NO_SYSTEM_TIME
Failure Cause
When the supplementary channel resources are being reserved, the CCM
DBS has no system time.
Failure Analysis
The HIRS platform does not send the system time to the CCM because
of instantaneous CHM failure.
l
Possible Solution
The IP platform SCS does not send the system time to the DBS.
Locate the failure cause by checking the fault probe, and then troubleshoot
accordingly.
NO_SYSTEM_TIME
CCM DBS
HIRSCHMCCM
IPSCSDBS
1.69 NO_AVAILABLE_REV_CE
Failure Name
NO_AVAILABLE_REV_CE
Failure Cause
Failure Analysis
Handling Measure
NO_AVAILABLE_REV_CE
CE
CE
1-40
SJ-20120828144226-019|2012-10-20 (R1.0)
1.70 FO_NOT_ENOUGH
Failure Name
FO_NOT_ENOUGH
Failure Cause
Failure Analysis
Handling Measure
FO_NOT_ENOUGH
FCH
FCH
1.71 CE_NOT_ENOUGH
Failure Name
CE_NOT_ENOUGH
Failure Cause
Failure Analysis
Possible Solution
CE_NOT_ENOUGH
CE
CE
1.72 WALSHCODE_NOT_ENOUGH
Failure Name
WALSHCODE_NOT_ENOUGH
1-41
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
Failure Analysis
Too many forward supplementary channels are set up and the Walsh code
is insufficient.
Possible Solution
WALSHCODE_NOT_ENOUGH
Walsh
Walsh
1.73 BEFORE_CPS
Failure Name
BEFORE_CPS
Failure Cause
Failure Analysis
The possible failure cause is as follows: The system clocks of the BTS
and the BSC are inconsistent.
Handling Measure
BEFORE_CPS
BTSBSC
GCM
1.74 UIDWIDTH_NOT_ENOUGH
Failure Name
UIDWIDTH_NOT_ENOUGH
Failure Cause
Failure Analysis
Possible Solution
UIDWIDTH_NOT_ENOUGH
1-42
SJ-20120828144226-019|2012-10-20 (R1.0)
UID
Abis
1.75 RS_NOT_EXIST
Failure Name
RS_NOT_EXIST
Failure Cause
Failure Analysis
Handling Measure
No troubleshooting is required.
RS_NOT_EXIST
RS
A
BAFCH
FCHRS
1.76 ALLOCATE_UID_ERROR
Failure Name
ALLOCATE_UID_ERROR
Failure Cause
Failure Analysis
Possible Solution
ALLOCATE_UID_ERROR
UID
UID
UID
1-43
SJ-20120828144226-019|2012-10-20 (R1.0)
1.77 BSC_CICFROMMSC_ERR
BSC_CICFROMMSC_ERR
AMSCCIC
MSCCICBSC
Failure Name
BSC_CICFROMMSC_ERR
Failure Cause
Failure Analysis
The CIC that is assigned by the MSC is not available on the BSC side.
Handling Measure
1.78 HO_STAT_SERVICE_FORBID
Failure Name
HO_STAT_SERVICE_FORBID
Failure Cause
Failure Analysis
During call access, the data service forbids it to access the voice carrier or
the voice service forbids it to access the data carrier.
Handling Measure
For voice service, check switch 78 and the attribute of the carrier to be
accessed. For data service, check switch 80 and the attribute of the carrier
to be accessed.
1.79 ERR_SPS_RLSA_RCM_DBAccFail_FCHResour
ceAllocate
Failure Name
ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate
Failure Cause
Failure Analysis
FO is not enough.
1-44
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
2. After confirming the failure cause, verify that the CHM board is normal
(the chip-set and CE are normal).
3. If the CHM and CCM are normal, it is possible that the resource is
hung up.
ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate
MS
CE
Walsh
FO
UID
1.
EV_S_AbisdrBTSSeupAck
2.
0x5064CE
0x5065CE
0x5066CE
CE
3.
CHMCCM
1.80 ERR_SPS_RLSA_RCM_PCALL_OtherReason_C
EC_REMOVEREQ
Failure Name
Failure Analysis
ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ
During the call process, the CHM board requests to release the current
call after detecting no frame in the forward channel (the default time is 6
s), meaning the CHM does not receive the SDU forward frame, and the
procedure is released. The possible failure causes are as follows:
l
1-45
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ
6 s
CHM6sSDU
IPMAC
Key
SDM
VTCDSP
1.
SDM
2.
IPMAC
3.
DSP
1.81 ERR_SPS_RLSA_RCM_FCH_TimerExpired_Tco
nnExpired
Failure Name
ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired
Failure Analysis
During call setup, the Abis interface timer expires when resources are being
set up. This starts the call release procedure and results in call failure.
The timer is triggered after the BTS assigns the radio resource and service
address and informs the BSC. If a BSC Ack message is not received before
the timer expires, the BTS starts the release procedure.
The reason for the BTS not receiving the Ack message is link and message
blocking and wrong message contents on the BTS.
Possible Solution
ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired
1-46
SJ-20120828144226-019|2012-10-20 (R1.0)
Abis
Tconnb4 sBTS
BSCBSCAck
BTS
BTSAckBTS
1.
2.
Abis
BTSBSCAbisdrConnect
AbisdfBTSSetuptAbisConnectInfo
1.82 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddC
hannelFail
Failure Name
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail
Failure Analysis
During call setup, this failure occurs when the IP platform BTS adds a
channel table. The possible reason is that too many channel tables are
added at one time.
Handling Measure
1. If the problem occurs in ordinary voice, verify that the channel table
is not hung up.
2. If the problem occurs during data service procedure, it is normal.
3. If no call adds many channel tables at one time (ordinary voice), it
indicates that the resource is hung up. Contact the local ZTE office.
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail
IPBTS
1.
2.
1.83 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_Tfsc
hNotifyExpired
Failure Name
ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired
1-47
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
During data service, the timer expires before the notification message of
database resource reservation is received.
Handling Measure
Verify that the voice traffic is not too heavy. If this case occurs frequently,
contact the local ZTE office.
ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired
1.
2.
1.84 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRe
questAbisConnect_SameTimeCellInSameGroupIn
DiffSetupFlow
Failure Name
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Sam
eTimeCellInSameGroupInDiffSetupFlow
Failure Analysis
During a call, multiple cells in the same leg are not allowed to set up FCHs
in multiple procedures. This results in resource setup failure.
Possible Solution
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Sam
eTimeCellInSameGroupInDiffSetupFlow
FCH
1.85 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_Main
Entry_MAbisdMsgDispatch
Failure Name
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgD
ispatch
Failure Analysis
During call setup, the main RCM process fails to forward messages to the
Handler process.
l
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
If the number of calls at one time is more than the upper limit of process
quantity, the failure is normal (upper limits: HIRS CCM is 300, BDM is
75, and IP CCM is 600). If the number of calls is fewer and this problem
occurs, the probable cause is that the OSS has changed the upper limit of
processes. In this case, contact the local ZTE office.
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgD
ispatch
RCMHandler
RCM
RCMHandler
1.86 ERR_SPS_RLSA_RCM_FCH_OtherReason_MReq
uestAbisConnect_ServiceRestrict
Failure Name
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Ser
viceRestrict
Failure Analysis
During handoff, because the service type for handoff is among the restricted
service of the destination cell, the cell handoff fails. The service types
include voice, data, PTT enhanced calls, and private calls.
Handling Measure
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Ser
viceRestrict
PTT
1-49
SJ-20120828144226-019|2012-10-20 (R1.0)
1.87 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_Burst
Request_ConnInSetup
Failure Name
Failure Analysis
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup
During forward supplementary channel setup, there is another concurrent
setup flow, causing the channel setup failure.
Handling Measure
Finish setting up the previous scheduling before starting the next one.
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup
1.88 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Burst
Request_SaveToGroupedCellInfoSet_CellNumIsZ
ero
Failure Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroup
edCellInfoSet_CellNumIsZero
Failure Analysis
Handling Measure
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroup
edCellInfoSet_CellNumIsZero
BurstRequestCI
1-50
SJ-20120828144226-019|2012-10-20 (R1.0)
1.89 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_
atTchStatusInSemiSoft_AbisdfBurstCommit
Failure Name
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstCommit
Failure Analysis
Handling Measure
No troubleshooting is required.
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstCommit
1.90 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddC
hannelFail
Failure Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail
Failure Analysis
During call setup, adding a channel table on the BTS side fails. The
probable cause is that a large number of channel tables are being added
at the same time. The problem normally occurs during the data service
supplementary channel setup process. If the problem occurs for the voice
service, the probable cause is that the channel table is suspended.
Handling Measure
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail
IPBTS
1.
2.
1-51
SJ-20120828144226-019|2012-10-20 (R1.0)
1.91 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Burst
Commit_GetConnRecordByGroupId
Failure Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRe
cordByGroupId
Failure Analysis
Handling Measure
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRe
cordByGroupId
BurstCommit
Abis
1.92 BSC_NO_CIC
Failure Name
BSC_NO_CIC
Failure Cause
Failure Analysis
Possible Solution
2. Verify that the DT board to which the CIC corresponds operates properly
and its version is correct.
3. Verify that the E1 physical connection to which the CIC corresponds is
correct.
4. Verify that the CIC resource is manually blocked in dynamic
management.
1-52
SJ-20120828144226-019|2012-10-20 (R1.0)
5. Verify that the CIC resource quantity meets the requirements of traffic
capacity.
BSC_NO_CIC
CIC
CICCICCICCIC
1.
ACIC
l
APCMPCM
PCM
CICDTRMP
2.
CICDT
3.
CICE1
4.
CIC
5.
CIC
1.93 POWER_NOT_ENOUGH
Failure Name
POWER_NOT_ENOUGH
Failure Cause
Inadequate power.
Failure Analysis
Possible Solution
POWER_NOT_ENOUGH
2X
OMC
1-53
SJ-20120828144226-019|2012-10-20 (R1.0)
1.94 BSC_NO_SE
Failure Name
BSC_NO_SE
Failure Cause
Failure Analysis
Possible Solution
BSC_NO_SE
SE
SESDUSESE
1.
1XSDU
2.
SDU
3.
APRTPSDU
4.
SDUINDEX
5.
SE
1.95 BSC_NO_VE
Failure Name
BSC_NO_VE
Failure Cause
Failure Analysis
Possible Solution
1. Verify that the resource frame where the CIC is located is configured
correctly with corresponding quantity of VTC boards.
2. Verify that the VTC board operates properly and the CPU/DSP version
is correct.
3. Verify that the VTC board and INDEX status is normal in dynamic
management.
4. Verify that the VE resource quantity meets the requirements of traffic
capacity.
1-54
SJ-20120828144226-019|2012-10-20 (R1.0)
BSC_NO_VE
VE
VEVTCVEVE
1.
CICVTC
2.
VTCCPU/DSP
3.
VTCINDEX
4.
VE
1.96 BSC_NO_IWF
Failure Name
BSC_NO_IWF
Failure Cause
Failure Analysis
Handling Measure
BSC_NO_IWF
IWF
IWFIWFIWFIWF
1.
IWFBCIC
CICIWFB
2.
IWFBCPU/DSP
3.
IWFBINDEX
4.
IWF
1.97 BSC_DSPM_NO_INSTANCE
Failure Name
BSC_DSPM_NO_INSTANCE
Failure Cause
1-55
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Possible Solution
BSC_DSPM_NO_INSTANCE
DSPM
DSPMDSPMDSPMDSPM
1.
DSPMDSPM
2.
DSPMMP
3.
DSPM
4.
DSPM
1.98 BSC_NO_RTPPORT
Failure Name
BSC_NO_RTPPORT
Failure Cause
Failure Analysis
Handling Measure
1. In the case of external RTP, verify that the IPI board and RTP port are
correctly configured.
2. Verify that the IPI board where RTP port is located operates properly
and its version is correct.
3. Verify that the status of RTPPORT resource is normal during dynamic
management.
4. Verify that the RTPPORT resource quantity meets the requirements of
traffic capacity.
BSC_NO_RTPPORT
RTPPORTRTP
1-56
SJ-20120828144226-019|2012-10-20 (R1.0)
RTPPORTRTPRTPPORT
1. RTPIPIRTP
2.
RTPIPI
3.
RTPPORT
4.
RTPPORT
1.99 BSC_NO_VALID_RMP
Failure Name
BSC_NO_VALID_RMP
Failure Cause
Failure Analysis
Possible Solution
BSC_NO_VALID_RMP
RMP
RMPRMPRMP
1.
RMP
2.
RMPMP
3.
RMP
1.100 ERR_SPS_RLSA_RCM_FCH_FunCallFail_Han
dlerAbisdfConnectAck_MCSHConstructAmdfFC
HSetup
Failure Name
ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup
Failure Analysis
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup
OMC
1.101 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MH
andlerTCHfTSSetup_MHandlerAbisdfBTSSetup
Failure Name
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup
Failure Analysis
During call setup or handoff, an error occurs in handling the call setup or
handoff message .
Handling Measure
1. In the case that the BTS is in graceful degradation mode, when the BTS
receives the call setup or handoff message from the BSC, the BTS
reports the failure message. It is a normal case.
2. The RCM does not support concurrent setup flows. If the RCM receives
another call setup or handoff message during the leg setup process, the
RCM reports the failure message. If the problem occurs occasionally,
no troubleshooting is required.
3. If the BSSAP or DSPM handoff type is incorrect, the failure message is
also reported. If the problem occurs occasionally, no troubleshooting
is required.
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup
1-58
SJ-20120828144226-019|2012-10-20 (R1.0)
1.
BSC
2. RCM
3. BSSAPDSPM
1.102 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect
_HandleAbisdfConnectAck_SoftHandoffLegNoIn
valid
Failure Name
ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid
Failure Analysis
During call setup or handoff process, the leg number leg in the
AbisdfConnectAck message exceeds the maximum allowed value. A call
supports up to 12 legs. If the leg number exceeds 12, a call failure may
be caused.
Handling Measure
ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid
AbisdfConnectAck
1212
1.103 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHa
ndlerAbisdfBTSSetup_MCDHSaveToCommonData
Failure Name
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData
Failure Analysis
1-59
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
If the a few such problems occur, ignore them. If a lot of such problems
occur, contact the local office of ZTE Corporation.
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData
1.
2.
CICI
1.104 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_CE_IN_USED
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED
Failure Cause
During FCH setup, the CE is hung up and results in FCH channel setup
failure.
Failure Analysis
Possible Solution
1. If the CPU usage ratio is too high, block some CSM daughter cards.
2. Check the SDH transmission.
3. Check the clock module.
4. Allocate some control channels to other boards.
5. If the problem persists, reset the CHM.
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED
CESCE
CPU
UB
IP6HIRS4
CES
1-60
SJ-20120828144226-019|2012-10-20 (R1.0)
1.
CPU
2.
3.
4.
5.
CHM
1.105 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SET
UP_RCV_CEM_REJECT
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT
Failure Cause
During FCH setup, after the CEC layer sends the FCH setup message
to the CEM layer, the CEM layer rejects the message, causing the FCH
setup failure.
Failure Analysis
There is a problem with the CES code, and the resources are not
released.
l
Possible Solution
1. If the CPU usage of the CHM is too high, block some daughter cards.
2. Check the clock module.
3. Assign specific control channels to the other boards.
4. If the measures above do not work, reset the CHM.
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT
CECCEMCEM
CPU
UB
CES
1.
CPU
2.
3.
4.
CHM
1-61
SJ-20120828144226-019|2012-10-20 (R1.0)
1.106 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETU
P_CREATE_PROCESS
Failure Name
ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS
Failure Cause
Failure Analysis
Possible Solution
ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS
V_Create
1.
2.
1.107 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP
_OUTPUT_MSG_TO_CALLHNDL
Failure Name
ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_
CALLHNDL
Failure Cause
In the case of FCH setup, the CallMain process fails to send message to the
Callhandler process.
Failure Analysis
Handling Measure
Version error.
ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_
CALLHNDL
CallMainCallhandler
V_OutputBySrc
1-62
SJ-20120828144226-019|2012-10-20 (R1.0)
1.
2.
1.108 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETU
P_RCV_CEM_RSP_TIMER_OUT
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TI
MER_OUT
Failure Cause
During FCH setup, after the CEC layer sends the FCH setup message
to the CEM layer, the CEM layer response times out, causing the FCH
setup failure.
Failure Analysis
There is a problem with the CES code, and the resources are not
released.
l
Handling Measure
1. If the CPU ultilization of the CHM is too high, block some daughter cards.
2. Check the clock module.
3. Assign specific control channels to the other boards.
4. If the above measures do not work, reset the CHM.
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TI
MER_OUT
CECCEMCEM
CPU
UB
CES
1.
CPU
2.
3.
4.
CHM
1-63
SJ-20120828144226-019|2012-10-20 (R1.0)
1.109 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_POINTER_NULL
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER
_NULL
Failure Cause
During FCH setup, the structure pointer is a null pointer in the CES
verification channel setup command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER
_NULL
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.110 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_HANDOFF_TYPE
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF
_TYPE
Failure Cause
During FCH setup, the handoff type is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.
Failure Analysis
1-64
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF
_TYPE
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.111 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_SECTOR_NUM
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_N
UM
Failure Cause
During FCH setup, the number of sectors is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_N
UM
CES
1-65
SJ-20120828144226-019|2012-10-20 (R1.0)
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.112 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_PARAM_FWD_RC
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC
Failure Cause
During FCH setup, the forward channel RC type is incorrect in the CES
verification channel setup command, causing the FCH setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC
CESRC
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.113 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_PARAM_REV_RC
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC
1-66
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
During FCH setup, the reverse channel RC type is incorrect in the CES
verification channel setup command, causing the FCH setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC
CESRC
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.114 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETU
P_PARAM_SECTOR_ID
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID
Failure Cause
During FCH setup, the sector ID is incorrect in the CES verification channel
setup command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID
CESID
1-67
SJ-20120828144226-019|2012-10-20 (R1.0)
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.115 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_SECTOR_ISNOT_ACTIVE
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I
SNOT_ACTIVE
Failure Cause
During FCH setup, the sector is not activated in the CES verification channel
setup command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I
SNOT_ACTIVE
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1-68
SJ-20120828144226-019|2012-10-20 (R1.0)
1.116 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_EARLIESTPNOFFSET
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIEST
PNOFFSET
Failure Cause
During FCH setup, EPN is incorrect in the CES verification channel setup
command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIEST
PNOFFSET
CESEPN
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.117 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_WALSH_INDEX
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_
INDEX
Failure Cause
During FCH setup, the WALSH code is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.
Failure Analysis
1-69
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_
INDEX
CESWalsh
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.118 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SET
UP_PARAM_CE_INDEX
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX
Failure Cause
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX
CESCEIndex
CHMCCM
CES
1-70
SJ-20120828144226-019|2012-10-20 (R1.0)
1.
2.
CHM
3.
CCM
1.119 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_FRAME_OFFSET
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_O
FFSET
Failure Cause
During FCH setup, the frame offset is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_O
FFSET
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.120 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_CHANNEL_POWER
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNE
L_POWER
1-71
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNE
L_POWER
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.121 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_PARAM_REV_FCH_GATING
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FC
H_GATING
Failure Cause
During FCH setup, the reverse FCH gating mode is incorrect in the CES
verification channel setup command, causing the FCH setup failure.
Failure Analysis
Handling Measure
1-72
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FC
H_GATING
CESFCH
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.122 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SET
UP_PARAM_REV_PILOT_GATING
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_P
ILOT_GATING
Failure Cause
During FCH setup, the reverse pilot channel gating mode is incorrect in the
CES verification channel setup command, causing the FCH setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_P
ILOT_GATING
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1-73
SJ-20120828144226-019|2012-10-20 (R1.0)
1.123 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_FPC_PUNC_MODE
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PU
NC_MODE
Failure Cause
During basic channel setup, the forward power control mode is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PU
NC_MODE
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.124 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SET
UP_PARAM_FPC_GAIN
Failure Name
Failure Cause
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN
During basic channel setup, the forward power control gain is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.
Failure Analysis
1-74
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.125 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_FPC_STEP_SIZE
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STE
P_SIZE
Failure Cause
During basic channel setup, the forward power control setp is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STE
P_SIZE
CES
1-75
SJ-20120828144226-019|2012-10-20 (R1.0)
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.126 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_RPC_PUNC_MODE
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PU
NC_MODE
Failure Cause
During basic channel setup, the reverse power control mode is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PU
NC_MODE
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1-76
SJ-20120828144226-019|2012-10-20 (R1.0)
1.127 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETU
P_PARAM_REV_PC_SETPOINT
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_
SETPOINT
Failure Cause
During basic channel setup, the reverse out loop setting values are incorrect
in the CES verification channel setup command, causing the failure in
setting up the basic channel.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_
SETPOINT
CES
(SetPoint)
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.128 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_REV_PC_PATTERN
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC
_PATTERN
Failure Cause
During basic channel setup, the reverse power control mode is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.
1-77
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC
_PATTERN
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.129 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_TRAFFIC_FRAME_TYPE
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_
FRAME_TYPE
Failure Cause
During FCH setup, the frame type is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.
Failure Analysis
Handling Measure
1-78
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_
FRAME_TYPE
CES
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.130 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_
DEST_IP_ADRR_INVALID
Failure Name
CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVA
LID
Failure Cause
During FCH setup, the destination IP address carried in the CES channel
setup verification command is incorrect, causing the FCH setup failure.
Failure Analysis
Handling Measure
CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVA
LID
CESIP
CHMCCM
CES
1.
2.
CHM
3.
CCM
1-79
SJ-20120828144226-019|2012-10-20 (R1.0)
1.131 CEMERROR_CALLHNDL_TCH_SETUP_PARAM
_DSCP_PRIIS_INVALID
Failure Name
CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID
Failure Cause
During FCH setup, the DSCP priority carried in the CES channel setup
verification command is incorrect, causing the FCH setup failure.
Failure Analysis
Handling Measure
CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID
CESDSCP
CHMCCM
CES
1.
2.
CHM
3.
CCM
1.132 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_CEMCTRL_NULL
Failure Name
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL
Failure Cause
During FCH setup, the pointer to the class CEMCTRL object fails to be
obtained, causing the FCH setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL
1-80
SJ-20120828144226-019|2012-10-20 (R1.0)
CEMCTRL
CES
1.
CHM
2.
CHM
1.133 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Con
nectref_Incompat_Inf_In_NSDUs
Failure Name
ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_
NSDUs
Failure Cause
Failure Analysis
Handling Measure
On the MSC, trace the SCCP signaling of the user and check the specific
failure cause. The cause is usually an authentication failure, which is
resulted from illegal users.
1.134 ERR_SPS_RLSA_BSSAP_SccpDisconnect_End
_User_Failure
Failure Name
ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure
Failure Cause
SCCPDISConnect occurs, with the cause Disconnect_Normal_condition(13). The SCCPDISConnect is caused by a user.
Failure Analysis
During registration, the SCCP link is released by the MSC. This is usually
caused by a user that is not provisioned or by an illegal user.
Handling Measure
On the MSC, trace the SCCP signaling of the user to find the specific
failure cause.
1-81
SJ-20120828144226-019|2012-10-20 (R1.0)
1.135 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_
FCHAndDCCH_AbisdrConnectProccess_AbisdrCo
nnectMsgProccess
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_Abisdr
ConnectProccess_AbisdrConnectMsgProccess
Failure Cause
Failure Analysis
Handling Measure
If only a few such faults occur, this is normal, and no handling measure
needs to be taken.
1.136 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckI
fCellFitToSetup_HOReqCellIsExisted
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOR
eqCellIsExisted
Failure Cause
The cell requested by the target of the inter-BSC soft handoff already exists.
Failure Analysis
The release flow of the target is not completed owing to such cause as link
delay, while the source initiates the next handoff request.
Handling Measure
If only a few such faults occur, this is normal, and no handling measure
needs to be taken. If a large number of such faults occur, obtain the
abnormal probe and contact ZTE Corporation for analysis.
1.137 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqRe
leaseingCellIsNotExisted
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExi
sted
Failure Cause
The cell that the target wants to release in the inter-BSC soft handoff does
not exist.
1-82
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Owing to an internal cause of the target or a cause of the BTS, the cell has
already been released, but the source still requests to release the cell; or
the release message of the source carries an incorrect cell.
Handling Measure
If only a few such faults occur, this is normal, and no handling measure
needs to be taken. If a large number of such faults occur, obtain the
abnormal probe and contact ZTE Corporation for analysis.
1.138 ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNot
ify_UserInHigherPriorityService
Failure Name
ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPriority
Service
Failure Cause
A request of the PTT traditional group call is received, and the current call is
preempted.
Failure Analysis
Handling Measure
It is a normal case. On the PHR, you can set not allow voice to be
preempted.
1.139 ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPa
ge_UserInHigherPriority
Failure Name
ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriority
Failure Cause
A PTT call request is received, and the current call is preempted by the
PTT call.
Failure Analysis
Handling Measure
It is a normal case. On the PHR, you can set not allow voice to be
preempted.
1-83
SJ-20120828144226-019|2012-10-20 (R1.0)
1-84
SJ-20120828144226-019|2012-10-20 (R1.0)
Chapter 2
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState
Failure Cause
Failure Analysis
The possible failure cause is as follows: When the user originates a call and
the process does not release the message, the call fails.
Handling Measure
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState
2.2 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInSe
ssionState_Others
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others
2-1
SJ-20120828144226-019|2012-10-20 (R1.0)
2.3 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut
Failure Name
ERR_SPS_RLSA_BSSAP_HandShake_TimeOut
Failure Cause
Failure Analysis
After entering the session state, timer times out while waiting for DSPM
handshaking message.
Possible Solution
ERR_SPS_RLSA_BSSAP_HandShake_TimeOut
BSSAPDSPM
DSPM
1.
2.
BSCMP
3.
4.
DSPM
2.4 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegIn
AssignState_PowerOn
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn
2-2
SJ-20120828144226-019|2012-10-20 (R1.0)
2.5 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAs
signState_PowerDown
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD
own
Failure Cause
Failure Analysis
The user originates a Power OFF while the process does not release
and the call fails.
The user on a call presses the power off button and this is the user
personal action.
Handling Measure
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD
own
2.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistr
ation
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistration
Failure Cause
Failure Analysis
Handling Measure
2-3
SJ-20120828144226-019|2012-10-20 (R1.0)
2.7 ERR_SPS_RLSA_DSPM_HOH_OtherReason_Abisd
HandShakeFailure
Failure Name
ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure
Failure Cause
During a call, the handshake failure between DSPM and RCM originates
call release.
Failure Analysis
Possible Solution
The RCM and ABPM relevant to the BTS are operating improperly.
1. Verify that the setting for timer Tphysical on the DSMP board is correct
(default 2 minutes).
2. Verify that the RCM and ABPM relevant to the BTS are operating
normally and no abnormal reset or changeover occurs.
3. Verify that the versions of CCM and ABPM boards are correct and
operating properly.
ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure
DSPMRCM
BTSRCMABPM
DSMPTphysical
1. DSMPTphysical2
2.
BTSRCMABPM
3.
CCMABPM
2.8 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCF
EquipmentFailure
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure
Failure Cause
Failure Analysis
Possible Solution
2-4
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure
PCF
PCF
A10
1.
A9SetupA8IMSIHIDI
2.
A10
3.
PCF
2.9 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Than
dshakerecv
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv
Failure Cause
During a call, there is a handshake between the DSPM, SDU and BSSAP.
When there is no reply message, timer Trecv expires and the SPS releases
the call.
Failure Analysis
The DSPM does not receive a reply message from the SDM when it
sends two handshake messages to the SDM in 5 minutes.
The DSPM does not receive a reply message from the BSSAP when it
sends two handshake messages to the SDM in 5 minutes.
Possible Solution
1. Verify that the setting of the Trecv timer (default value is 5 minutes) on
the DSMP board is correct.
2. Check the corresponding CMP when the problem occurs. Verify that the
SDU operates properly and there is no abnormal reset or switchover.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv
DSPMSDUBSSAPTrecv
DSPM5SDM2SDM
DSPM5SDM2BSSAP
1. DSMPTrecv5
2.
CMPSDU
2-5
SJ-20120828144226-019|2012-10-20 (R1.0)
2.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHReleaseRSCHbyLegFail_ReleaseRschExistS
DMLegFailure
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLe
gFail_ReleaseRschExistSDMLegFailure
Failure Cause
The DSPM receives the LegLinkFailure report from SDM. If RSCH is not
partly soft handoff and the released cell, then the SDM notify different cells.
The failure is reported by DSPM.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLe
gFail_ReleaseRschExistSDMLegFailure
DSPMSDMLegLinkFailureRSCH
SDMDSPM
SDM
Abis
2.11 SDM_Link_Fail_RevNoFrm
Failure Name
SDM_Link_Fail_RevNoFrm
Failure Analysis
Link failure. The SDM cannot receive traffic frames sent from the BTS
during a period (default time is 18 s).
Reasons for this failure vary, for example, Abis link problem and CHM
dispatching problem, which are subject to different situations.
The call is released when the failure is reported.
Possible Solution
SDM_Link_Fail_RevNoFrm
SDM18 sBTS
AbistCHM
Abis
2-6
SJ-20120828144226-019|2012-10-20 (R1.0)
2.12 SDM_Link_Fail_RevTooManyBadFrm
Failure Name
SDM_Link_Fail_RevTooManyBadFrm
Failure Analysis
Link failure. The SDM receives almost all error frames from the BTS side
during receiving period (default time is 18 s).
The reasons for this failure may vary. The reason may be characterized as
normal or abnormal reasons depending upon the actual situation.
For example:
l
If the reverse radio link is very bad, the problem will be reported. This
is a normal release.
Possible Solution
SDM_Link_Fail_RevTooManyBadFrm
SDMBTS
18 s
BS
BSPN
1.
MSBSPN
2.
MS
2.13 SDM_Link_Fail_FwdA2pNoFrm
Failure Name
SDM_Link_Fail_FwdA2pNoFrm
Failure Cause
SDM cannot receive traffic frame sent from MGW during a period (default
time is 18 s).
2-7
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Reasons for this fault vary, for example, net cable on Ap port has a problem,
MGW process problem (not sending frame), which is subject to actual
situation. While submitting this fault, calling will be released.
Handling Measure
Check net cable on Ap port and check BSC side and MGW side
configuration (for example whether packet quantity is the same), if problem
is not found, then analyze MGW side.
SDM_Link_Fail_FwdA2pNoFrm
SDMMGW18 s
ApMGW
ApBSCMGW
MGW
2.14 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm
Failure Name
SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm
Failure Cause
Failure Analysis
1. Problem occur during MGW frame sending, i.e. not send frame to SDM.
2. Problem occurs in Ap port link during call; the possibility is relatively
small.
3. SDM process error.
Handling Measure
SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm
18 sSDMMGW
MGWSDM
Ap
SDM
1.
Ap
2.
2-8
SJ-20120828144226-019|2012-10-20 (R1.0)
2.15 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_Main
Entry_GetCallProc
Failure Name
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc
Failure Analysis
Handling Measure
If the a few such problems occur, ignore them. If a lot of such problems
occur, contact the local office of ZTE Corporation.
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc
BurstRequest
2.16 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnI
nHardHOAdd
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInHardHOAdd
During the hard handoff process, a call originating message is received
from the terminal.
Failure Analysis
Handling Measure
2.17 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPage
RspInHardHOAdd
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPageRspInHardHOAdd
Failure Cause
2-9
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
2-10
SJ-20120828144226-019|2012-10-20 (R1.0)
Chapter 3
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease
3.2 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSP
owerDown
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown
3-1
SJ-20120828144226-019|2012-10-20 (R1.0)
3.3 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnUmrSCHRequestMsg_ReleasebyMSDTXTime
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReq
uestMsg_ReleasebyMSDTXTime
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques
tMsg_ReleasebyMSDTXTime
RSCHDTXTime
3.4 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnAbarSCHRemoveIndication_RSCHReleaseby
SDMOtherReason
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason _SCHHOnAbarSCHRemo
veIndication_RSCHReleasebySDMDTXTime
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_RSCHReleasebySDMOtherReason
SDMRSCH
3-2
SJ-20120828144226-019|2012-10-20 (R1.0)
3.5 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HPNDropIndication_ReleasebyHOH
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_
ReleasebyHOH
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_
ReleasebyHOH
SCH
3.6 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SC
HHOnAbisdrBurstRelease_RSCHExistedCellRele
asebyRCM
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_RSCHExistedCellReleasebyRCM
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_RSCHExistedCellReleasebyRCM
BTSRSCH
3-3
SJ-20120828144226-019|2012-10-20 (R1.0)
3.7 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HRelease_ReleasebyCLH
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Release
byCLH
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Releaseb
yCLH
SCH
3.8 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnAbarSCHRemoveIndication_RSCHReleaseby
SDMOtherReason
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_ RSCHReleasebySDMOtherReason
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_ RSCHReleasebySDMOtherReason
SDMRSCH
3-4
SJ-20120828144226-019|2012-10-20 (R1.0)
3.9 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnAbarSCHRemoveIndication_FSCHReleaseby
SDMDuration
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_FSCHReleasebySDMDuration
Failure Cause
When the SCH dispatch timer is timeout, SDM initiates FSCH release.
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_FSCHReleasebySDMDuration
SCHSDMFSCH
3.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHFSCHHandoff_HardHandoff
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_H
ardHandoff
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_Har
dHandoff
SCHSCH
3-5
SJ-20120828144226-019|2012-10-20 (R1.0)
3.11 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tf
schdrop
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop
FSCH
3.12 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SC
HHOnTfschdroppending_ReleasebyTDropPending
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppendin
g_ReleasebyTDropPending
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppendin
g_ReleasebyTDropPending
FSCH
3-6
SJ-20120828144226-019|2012-10-20 (R1.0)
3.13 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnAbisdrBurstRelease_FSCHExistedCellRele
asebyRCM
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_FSCHExistedCellReleasebyRCM
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_FSCHExistedCellReleasebyRCM
BTSFSCH
3.14 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MS
GoingIntoDormant
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant
3.15 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCF
NormalRelease
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease
3-7
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Cause
Failure Analysis
Normal release.
Handling Measure
Normal release.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease
PCF
3.16 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDM
LinkFailure_toDormant
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant
Failure Cause
Data service air interface link fails. During a specific time, SDM receives
error frames or no frames from BTS (the default duration is 18 s) and
releases to the Dormant status.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant
SDMBTS
18 sDormant
3-8
SJ-20120828144226-019|2012-10-20 (R1.0)
BS
BSPN
1.
MSBSPN
2.
MS
3.
3.17 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHO
nA7rTarRemReq_CLHRlsInd
Failure Name
ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CL
HRlsInd
Failure Cause
During inter-BSC soft handoff, the target BSC detects fault, hence initiating
a soft handoff remove.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CL
HRlsInd
BSCBSC
l
A3
3-9
SJ-20120828144226-019|2012-10-20 (R1.0)
1.
2. IBBEIBBE
3. HGMHGME1
4.
3.18 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnA7rBurstRelease_FSCHExistedCellReleas
ebyRCM
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_FSCHExistedCellReleasebyRCM
Failure Cause
In the case of BSC interconnection, the target side initiates the release of
the forward supplementary channel.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_FSCHExistedCellReleasebyRCM
BSC
3.19 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnA7rBurstRelease_RSCHExistedCellReleas
ebyRCM
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_RSCHExistedCellReleasebyRCM
Failure Cause
In the case of BSC interconnection, the target side initiates the release of
the reverse supplementary channel.
Failure Analysis
Handling Measure
3-10
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_RSCHExistedCellReleasebyRCM
BSC
3.20 SDM_Find_Fail_NoFCHLeg
Failure Name
SDM_Find_Fail_NoFCHLeg
Failure Cause
Handling Measure
Check signaling to find out whether Layer 3 has noticed SDM to add this
leg; if it has, then the problem lies in SDM, if not then it lies in Layer 3.
Find the cause by signaling trace.
SDM_Find_Fail_NoFCHLeg
SDMAbafSDMDropLegSDM
SDM
SDMSDM
3.21 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Rele
ase_RSCH
Failure Name
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH
Failure Cause
Handling Measure
Normal status.
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH
3-11
SJ-20120828144226-019|2012-10-20 (R1.0)
3.22 ERR_SPS_RLSA_RCM_RSCH_OtherReason_R
elease_FSCH
Failure Name
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH
Failure Cause
Handling Measure
Normal status
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH
3.23 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpire
d_Tsch
Failure Name
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch
Failure Cause
Handling Measure
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch
3.24 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpir
ed_Tbstcomb
Failure Name
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb
Failure Cause
During data service, BTS side SCH channel resource allocation is finished,
waiting for BSC side confirm, BSC side confirm message timeout
Failure Analysis
After BTS side allocates SCH channel resource, the parameter in reply
message to BSC side is wrong.
3-12
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb
BTSBSC
BSC
BTSBSC
1.
Abis
2.
BTSBSCAbisdrBurstResponse
AbisdfBurstRequest
3.25 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Rev
SCHSetupFail
Failure Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail
Failure Cause
During data service, when an SCH channel is being set up, the database
resource is allocated, but the CHM board fails to be configured, and the
reverse SCH channel is released.
Failure Analysis
Handling Measure
3-13
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail
CHMSCHCE
CHMCE
1.
CHMCPU
2.
CHMCE
3.
CE
3.26 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_Fwd
SCHSetupFail
Failure Name
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail
CHMSCHCE
CHMCE
1.
CHMCPU
2.
CHMCE
3.
CE
3-14
SJ-20120828144226-019|2012-10-20 (R1.0)
3.27 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Burst
Commit_STATUS_RemovedSCH
Failure Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Re
movedSCH
Failure Analysis
Handling Measure
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Re
movedSCH
0STATUS_RemovedSCH
1.
CHMCPU
2.
CHMCE
3.
CE
3.28 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_Cel
lNotFoundInRevSCHResourceExtension
Failure Name
ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCH
ResourceExtension
Failure Cause
During data service, after SCH set up and when user transmits data
continuously, there is a newly added cell. This case is softer handoff add in
transmission. It is normal condition.
Handling Measure
Normal status.
ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCH
ResourceExtension
3-15
SJ-20120828144226-019|2012-10-20 (R1.0)
3.29 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tc
onfigtch
Failure Name
Failure Analysis
ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch
During data service, when an SCH channel is being set up and database
is in allocation, CHM board configuration fails and forward SCH channel is
released. The possible failure causes are as follows:
l
Possible Solution
ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch
CHMCE
CHMCE
1.
CHMCPU
2.
CHMCE
3.
OMCCE
3.30 ERR_SPS_RLSA_RCM_FSCH_OtherReason_End
OfDuration
Failure Name
ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration
Failure Analysis
Handling Measure
ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration
3-16
SJ-20120828144226-019|2012-10-20 (R1.0)
Chapter 4
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerEntry
__A7HOReqMsgProccessForHOWith1X
Failure Cause
The target BSC interconnects with the HIRS BSC. The handoff request
processing is abnormal.
Failure Analysis
The number of cells is greater than the maximum number of cells that
a call occupies.
l
Handling Measure
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_TargetBSCHandlerEntry_
A7HOReqMsgProccessForHOWith1X
BSCHirs BSC
1.
2.
PN
4.2 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetC
ircuit
Failure Name
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit
Failure Cause
4-1
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
The CIC state on the MSC side and that on the BSC side are different.
The CIC code on the MSC side and that on the BSC side are different.
1. Verify that the CIC state on the MSC side and that on the BSC side
are consistent.
2. Verify that the PCM codes on both the MSC and BSC sides are
consistent with the E1 cable.
Further
Troubleshooting
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit
MSC
MSCBSCCIC
MSCBSCCIC
1.
MSCBSCCIC
2.
MSCBSCPCME1
3.
MSC
4.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetB
SCHandler_A7fHandoffRequestProccess_Recieve
dA7HOReqWhenSemiHO
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoff
RequestProccess_RecievedA7HOReqWhenSemiHO
Failure Cause
Failure Analysis
Handling Measure
Source side initiates a new handoff before semi-soft handoff flow completes.
It is acceptable if the problem occurs occasionally, otherwise, check the
BSC at source side.
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoff
RequestProccess _RecievedA7HOReqWhenSemiHO
A7 Handoff Request
BSC
4-2
SJ-20120828144226-019|2012-10-20 (R1.0)
4.4 ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure
Failure Name
ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure
Failure Cause
A failure occurs during a transition, and the target side is expected to send a
transition failure message.
Failure Analysis
A failure occurs during a transition due to multiple reasons, and the target
side is expected to send a transition failure message.
Handling Measure
Some BTSs may report the failure cause. If the failure occurs frequently,
contact the local ZTE office.
4.5 ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscri
minator
Failure Name
ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscriminator
Failure Cause
The BSC fails to obtain the cell discrimination type of the peer BSC in a
non-network interconnection handoff from the database according to the
office No. of the interconnected BS.
Failure Analysis
The database is abnormal or the peer BSC does not support the
non-network interconnection.
Handling Measure
4.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssig
nmentMsgNotInValidState
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssignmentMsgNotInValidState
Failure Cause
Failure Analysis
Handling Measure
4-3
SJ-20120828144226-019|2012-10-20 (R1.0)
4.7 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAc
kNotInSetupState
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAckNotInSetupState
Failure Cause
Failure Analysis
The MS may go into another state due to a system allocation failure or other
reasons when receiving the SBSSAck message.
Handling Measure
4.8 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSA
ck_bTbssapRlcReqOut
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAck_bTbssapRlcReqOut
Failure Cause
Failure Analysis
The trg progress at the target side does not respond in time, or the link is
broken.
Handling Measure
4.9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHOR
equiredSBSSRInV5System
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHORequiredSBSSRInV5System
Failure Cause
Failure Analysis
Handling Measure
4-4
SJ-20120828144226-019|2012-10-20 (R1.0)
4.10 ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRem
ovalReqInSBSSRCallSetup
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSRCallSetup
Failure Cause
Failure Analysis
The state changes due to some reason, for example, a resource allocation
failure.
Handling Measure
4.11 ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlc
ReqNotInSetupState
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState
Failure Cause
Failure Analysis
Handling Measure
4.12 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque
stAck_atCellInfoIsInvalid
Failure Name
ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque stAck_atCellInfoIsInvalid
Failure Cause
Failure Analysis
Handling Measure
4-5
SJ-20120828144226-019|2012-10-20 (R1.0)
4.13 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque
stAck_ServiceTypeIsNotMatched
Failure Name
ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIsNotMatched
Failure Cause
Failure Analysis
Handling Measure
4.14 ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq
Failure Name
ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq
Failure Cause
Failure Analysis
Handling Measure
4.15 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A
7HandoffRequestReceived
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestReceived
Failure Cause
The target side receives a handoff request from the serving side when it
does not finish the current non-network interconnection handoff.
Failure Analysis
Handling Measure
4-6
SJ-20120828144226-019|2012-10-20 (R1.0)
4.16 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_
A7DropTargetReceived
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived
The target side receives a handoff drop request from the serving side when
it has not finished the current non-network interconnection handoff.
Failure Analysis
Handling Measure
4.17 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A
3DropReceived
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived
Failure Cause
The target side receives a leg elimination request from the serving side
when it has not finished the current non-network interconnection handoff.
Failure Analysis
Handling Measure
4.18 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_T
waitRlcExpired
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired
The soft handoff progress at the target side does not receive the
EV_S_SBSSRelocationComplete message in the timer duration after
sending an EV_S_SBSSRelocationRequestAck message to the hard
handoff progress during a non-network interconnection handoff.
Failure Analysis
Handling Measure
4-7
SJ-20120828144226-019|2012-10-20 (R1.0)
4.19 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_T
waitDrpTgtExpired
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired
The soft handoff progress at the target side does not receive the
A7DropTaregt message from the serving side in the timer duration after
receiving an EV_S_SBSSRelocationComplete message from the hard
handoff progress at the target side during a non-network interconnection
handoff.
Failure Analysis
Handling Measure
4.20 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_R
ecvRlcReqWhenSoftHOAdd
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHOAdd
Failure Cause
Failure Analysis
Handling Measure
4.21 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_Re
cvRlcReqWhenSoftHODrop
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHODrop
Failure Cause
Failure Analysis
4-8
SJ-20120828144226-019|2012-10-20 (R1.0)
Handling Measure
4.22 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_R
ecvRlcReqWhenSemiHOAdd
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemiHOAdd
Failure Cause
Failure Analysis
Handling Measure
4.23 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_R
ecvRlcReqWhenSCHExist
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSCHExist
Failure Cause
Failure Analysis
Handling Measure
4.24 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_
WrongChannelItemState
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState
Failure Cause
Failure Analysis
Handling Measure
It is unnecessary to handle.
4-9
SJ-20120828144226-019|2012-10-20 (R1.0)
4.25 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_U
nexpectedRlcState
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState
A message that is not expected to be received in the current state is
received during a non-network interconnection handoff.
Failure Analysis
Handling Measure
4.26 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredR
eject_OAMIntervention
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention
Failure Cause
Failure Analysis
Handling Measure
4.27 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredRe
ject_EquipmentFailure
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure
Failure Cause
Failure Analysis
Handling Measure
4-10
SJ-20120828144226-019|2012-10-20 (R1.0)
4.28 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredRe
ject_NoRadioResourceAvailable
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResource
Available
Failure Cause
Failure Analysis
Handling Measure
4.29 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_RTRUnavailable
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable
Failure Cause
During the outgoing hard handoff process, the required terrestrial circuit
resources are unavailable.
Failure Analysis
Handling Measure
4.30 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_BSNotEquipped
Failure Name
Failure Cause
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped
During the outgoing hard handoff process, there is a problem with the status
of the target BS.
Failure Analysis
Handling Measure
4.31 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_HandoffBlocked
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked
Failure Cause
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
4.32 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_RTAUnavailable
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable
Failure Cause
During the outgoing hard handoff process, the required coding/rate are
unavailable.
Failure Analysis
Handling Measure
4.33 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredRe
ject_TimeOut
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut
Failure Cause
During the outgoing hard handoff process, the handoff timer of the switch
times out.
Failure Analysis
Handling Measure
4.34 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredR
eject_Unspecified
Failure Name
ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified
Failure Cause
Failure Analysis
Handling Measure
4-12
SJ-20120828144226-019|2012-10-20 (R1.0)
4.35 SOFTADD_CELL_ERROR
Failure Name
SOFTADD_CELL_ERROR
Failure Cause
Failure Analysis
Lost of release message may cause this fault, but the possibility is
comparatively small.
Handling Measure
SOFTADD_CELL_ERROR
RCMDBS
BSC
BTSBTS
DSPMFCHSCH
4.36 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Soft
HOThocompletion
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion
Failure Cause
Failure Analysis
BTS clock is inconsistent with BSC clock when frame number checking
is enabled.
4-13
SJ-20120828144226-019|2012-10-20 (R1.0)
Possible Solution
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion
HDMThocompletion5 s
MSHCM
BTSBSC
1. DSMPThocompletion5 s
2.
3.
BTSBTS
4.
ABPMDTBDSM
4.37 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_T
horeq
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq
Failure Cause
Failure Analysis
Handling Measure
Further
Troubleshooting
4-14
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq
Abis/A3A7
BTS
BSCBSCA3A7HGM
1.
DSMPThoreq5 s
2.
Abis/A3A7
3. BTS
CE
4. BSCBSCA3A7HGM
5.
CCM
4.38 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_H
OHOnUmrCFSearchReport
Failure Name
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearc
hReport
Failure Cause
Failure Analysis
l
Further
Troubleshooting
Handling Measure
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchR
eport
1.
2. ABPMDTBDSM
4-15
SJ-20120828144226-019|2012-10-20 (R1.0)
4.39 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Sem
iSoftHOThocompletion
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion
Failure Cause
Failure Analysis
l
Handling Measure
1. Verify that the setting of the Thocompletion timer of the DSMP board is
correct (default value 5 s).
2. Check the handoff target cell transmission power.
3. Check the handoff target BTS board to see whether the call origination
under this BTS is normal or not.
Further
Troubleshooting
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion
HDMThocompletion5 s
MSHCM
BTSBSC
1. DSMPThocompletion5 s
2.
3.
BTSBTS
4. ABPMDTBDSM
4.40 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied
_HOHOnA7rHOReqAck
Failure Name
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck
Failure Cause
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
Further
Troubleshooting
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck
BTS/BSC
1.
Abis/A3A7
2. BTS
CE
3. BSCBSCA3A7HGM
4.
CCM
4.41 ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFai
l_GetHandoffProc
Failure Name
ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc
Failure Cause
Failure Analysis
The selected carrier frequency does not match FO, relevant macro
value: HO_STAT_CARRIER_FO_NOT_MATCH (0x00004A07).
4-17
SJ-20120828144226-019|2012-10-20 (R1.0)
The selected carrier frequency does not match the pilot, relevant macro
value: HO_STAT_PILOT_NO_SAME_FREQ (0x00004A08).
The pilot does not belong to this BSC, relevant macro value:
HO_STAT_PILOT_NOT_LOCALBSS (0x00004A0B).
HO_STAT_DESTBSC_NOT_SUPPORT_PTT (0x00004A0E).
macro value: HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
(0x00004A0F).
l
Possible Solution
ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc
HO_STAT_CARRIER_STATE_ERROR0x00004A03
HO_STAT_CARRIER_BEACON
0x00004A04
CEHO_STAT_CARRIER_NO_CE
0x00004A05
5KCEHO_STAT_CARRIER_NO_CE
0x00004A06
FOHO_STAT_CARRIER_FO_NOT_MATCH0x00004A07
HO_STAT_PILOT_NO_SAME_FREQ
0x00004A08
HO_STAT_PILOT_ALLCARRIER_NOT_AVAILABLE0x00004A09
4-18
SJ-20120828144226-019|2012-10-20 (R1.0)
FOHO_STAT_PILOT_ALLCARRIER_NO_FO0x00004A0A
BSCHO_STAT_PILOT_NOT_LOCALBSS
0x00004A0B
HO_STAT_PILOT_IS_NOT_NEIGHBOR0x00004A0C
BSCHO_STAT_PILOT_IS_OTHER_UNLNKBSS
0x00004A0D
BSCPTTHO_STAT_DESTBSC_NOT_SUPPORT_PTT0x00004A0E
IPHIRSBSC
HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO0x00004A0F
HO_STAT_DESTBSC_LINKSTATUS_ERROR0x00004A10
HO_STAT_PILOT_CELLMODE_DIFFERENT0x00004A11
1.
2.
3.
4.42 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDM
SetISLPFailure
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure
Failure Cause
Failure Analysis
When the conversation gets encrypted, SDM fails to inform VTC to enable
the ISLP protocol.
Handling Measure
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure
SDMISLP
SDMVTCISLP
VTC
4-19
SJ-20120828144226-019|2012-10-20 (R1.0)
4.43 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHO
nDBSHOProcACK_PNSConstructFrmDBS
Failure Name
ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PN
SConstructFrmDBS
Failure Cause
Failure Analysis
Handling Measure
1. Verify that the CCM, ABPM, HGM, and IBBE boards are normal.
2. Verify that the A7 link is normal.
3. Verify that the cell node configuration in OMC is correct.
ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PN
SConstructFrmDBS
CCMABPMHGM
IBBE
1.
CCMABPMHGMIBBE
2.
A7
3.
4.44 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_T
hocompletion
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion
Failure Cause
Failure Analysis
Handling Measure
Check the carrier signal strength. If the problem rarely occurs, it is normal.
4-20
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion
4.45 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
Failure Name
HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
Failure Cause
HGM does not support soft handoff within BSC with data service.
Failure Analysis
HGM does not support soft handoff within BSC with data service.
Handling Measure
Use an IBBE board so that IP BSC and HIRS BSC support soft handoff
within BSC with data service.
HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
HGMbsc
HGMbsc
4.46 HO_STAT_PILOT_NOT_LOCALBSS
Failure Name
HO_STAT_PILOT_NOT_LOCALBSS
Failure Cause
Failure Analysis
Remove the other BSC PN while performing the hard handoff on the BSC.
Possible Solution
Normal flow.
HO_STAT_PILOT_NOT_LOCALBSS
PNBSC
BSCBSC PN
4-21
SJ-20120828144226-019|2012-10-20 (R1.0)
4.47 HO_Func_GetTargetFromPreCell_ERR
Failure Name
HO_Func_GetTargetFromPreCell_ERR
Failure Cause
The candidate frequency in the active set and the preferred neighbor cell fail
to be obtained during a blind handoff.
Failure Analysis
The candidate frequency in the active set and the preferred neighbor cell fail
to be obtained during a blind handoff.
Handling Measure
4.48 SOME_CELL_FAIL
Failure Name
SOME_CELL_FAIL
Failure Cause
Failure Analysis
Handling Measure
Check the CE resource status on the BTS side and the carrier power
overload status.
SOME_CELL_FAIL
Ec/Io
BTSCE
4.49 CELL_IS_ERROR
Failure Name
CELL_IS_ERROR
Failure Cause
In the F-SCH soft handoff mode, the number of cells that re-transmit
application requests is smaller than the number of current cells.
Failure Analysis
In the F-SCH soft handoff mode, the number of cells that re-transmit
application requests is smaller than the number of current cells.
Handling Measure
Verify that the pilot strength of the user active set decreases sharply. If such
problems frequently occur, contact the local office of ZTE.
CELL_IS_ERROR
4-22
SJ-20120828144226-019|2012-10-20 (R1.0)
4.50 HO_STAT_PILOT_LIMITED
Failure Name
HO_STAT_PILOT_LIMITED
Failure Cause
During assignment to soft handoff mode, leg setup is forbidden in the cell
that has satisfying resources due to the limit of this mode.
Failure Analysis
The failure cause depends on the value of switch 96, as described in the
following:
l
When switch 96 is set to 0, all strong legs are set up and leg setup
is forbidden in the cell with weak signals although it has satisfying
resources.
When switch 96 is set to 2, strong legs with equivalent strength are set
up. In this mode, leg setup is forbidden in the cell with weak signals
although it has satisfying resources.
Handling Measure
4.51 ERR_SPS_RLSA_RCM_FCH_OtherReason_MReq
uestAbisConnect_SpecifiedCellIsReleasing
Failure Name
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Spec
ifiedCellIsReleasing
Failure Analysis
Possible Solution
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Spec
ifiedCellIsReleasing
1.
2.
4.52 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_
atTchStatusInSemiSoft_AbisdfBurstRequest
Failure Name
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstRequest
Failure Analysis
Possible Solution
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstRequest
SCH
4.53 HO_STAT_PILOT_IS_OTHER_UNLNKBSS
Failure Name
HO_STAT_PILOT_IS_OTHER_UNLNKBSS
Failure Cause
Failure Analysis
The MS is in the critical cell and reports that the pilot number is not under
this BSC and not interconnected.
Possible Solution
HO_STAT_PILOT_IS_OTHER_UNLNKBSS
4-24
SJ-20120828144226-019|2012-10-20 (R1.0)
BSCBSC
BSCBSC
4.54 HO_STAT_PILOT_NO_SAME_FREQ
Failure Name
HO_STAT_PILOT_NO_SAME_FREQ
Failure Cause
During handoff judge, as there is no suited frequency under the pilot, target
pilot aggregate cannot be added.
Failure Analysis
For semi-soft and hard handoff, the carrier with the smallest
transmission power in the first pilot is selected as the fundamental
carrier. Therefore for other pilots there is probably no such carrier, and
it is normal to submit the reason.
Possible Solution
For soft handoff, verify that the frequency for soft handoff is configured
under PN that is to be added.
HO_STAT_PILOT_NO_SAME_FREQ
PN
4.55 HO_STAT_CARRIER_PWR_OVERLOAD
Failure Name
HO_STAT_CARRIER_PWR_OVERLOAD
Failure Cause
Failure Analysis
During handoff judge, the power of the selected carrier is overloaded. The
reason for this failure is: The carrier has too many subscribers.
Possible Solution
4-25
SJ-20120828144226-019|2012-10-20 (R1.0)
HO_STAT_CARRIER_PWR_OVERLOAD
4.56 HO_STAT_CARRIER_STATE_MBLOCK
Failure Name
HO_STAT_CARRIER_STATE_MBLOCK
Failure Cause
Failure Analysis
Handling Measure
4.57 HO_STAT_CARRIER_STATE_RFE_BROKEN
Failure Name
HO_STAT_CARRIER_STATE_RFE_BROKEN
Failure Cause
Failure Analysis
The radio frequency of the carrier is faulty, so the carrier status is abnormal.
Possible Solution
HO_STAT_CARRIER_STATE_RFE_BROKEN
4.58 HO_STAT_CARRIER_STATE_RFE_LOWPOWER
Failure Name
HO_STAT_CARRIER_STATE_RFE_LOWPOWER
Failure Cause
Failure Analysis
Possible Solution
HO_STAT_CARRIER_STATE_RFE_LOWPOWER
4-26
SJ-20120828144226-019|2012-10-20 (R1.0)
4.59 HO_STAT_CARRIER_STATE_BDS_DISCONNECT
Failure Name
HO_STAT_CARRIER_STATE_BDS_DISCONNECT
Failure Cause
Failure Analysis
Possible Solution
HO_STAT_CARRIER_STATE_BDS_DISCONNECT
Abis
BSCBTS
Abis
4.60 HO_STAT_CARRIER_STATE_RFE_POWERDOWN
Failure Name
HO_STAT_CARRIER_STATE_RFE_POWERDOWN
Failure Cause
Failure Analysis
Possible Solution
HO_STAT_CARRIER_STATE_RFE_POWERDOWN
4.61 HO_STAT_CARRIER_RESOURCE_RESERVED
Failure Name
HO_STAT_CARRIER_RESOURCE_RESERVED
Failure Cause
4-27
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Possible Solution
HO_STAT_CARRIER_RESOURCE_RESERVED
Walshcode
4.62 HO_STAT_CARRIER_LIMITED
Failure Name
HO_STAT_CARRIER_LIMITED
Failure Cause
Failure Analysis
Possible Solution
HO_STAT_CARRIER_LIMITED
PTTPTT
4.63 HO_STAT_CARRIER_NO_CE
Failure Name
HO_STAT_CARRIER_NO_CE
Failure Cause
Failure Analysis
Possible Solution
4-28
SJ-20120828144226-019|2012-10-20 (R1.0)
HO_STAT_CARRIER_NO_CE
CE
CE
1.
CE
2.
4.64 HO_STAT_CARRIER_NO_5KCE
Failure Name
HO_STAT_CARRIER_NO_5KCE
Failure Cause
Failure Analysis
Possible Solution
HO_STAT_CARRIER_NO_5KCE
5KCE
5KCE15CE
1.
5K CE
2.
4.65 HO_STAT_PILOT_IS_NOT_NEIGHBOR
Failure Name
HO_STAT_PILOT_IS_NOT_NEIGHBOR
Failure Cause
Failure Analysis
Possible Solution
HO_STAT_PILOT_IS_NOT_NEIGHBOR
PN
PNlinkcell
PN
4-29
SJ-20120828144226-019|2012-10-20 (R1.0)
4.66 BSC_NO_SE
Failure Name
BSC_NO_SE
Failure Cause
Failure Analysis
Possible Solution
BSC_NO_SE
SE
SESDUSESE
1.
1XSDU
2.
SDU
3.
APRTPSDU
4.
SDUINDEX
5.
SE
4.67 BSC_NO_VE
Failure Name
BSC_NO_VE
Failure Cause
Failure Analysis
Possible Solution
1. Verify that the resource frame where the CIC is located is configured
correctly with corresponding quantity of VTC boards.
2. Verify that the VTC board operates properly and the CPU/DSP version
is correct.
3. Verify that the VTC board and INDEX status is normal in dynamic
management.
4. Verify that the VE resource quantity meets the requirements of traffic
capacity.
4-30
SJ-20120828144226-019|2012-10-20 (R1.0)
BSC_NO_VE
VE
VEVTCVEVE
1.
CICVTC
2.
VTCCPU/DSP
3.
VTCINDEX
4.
VE
4.68 BSC_NO_IWF
Failure Name
BSC_NO_IWF
Failure Cause
Failure Analysis
Handling Measure
BSC_NO_IWF
IWF
IWFIWFIWFIWF
1.
IWFBCIC
CICIWFB
2.
IWFBCPU/DSP
3.
IWFBINDEX
4.
IWF
4.69 BSC_DSPM_NO_INSTANCE
Failure Name
BSC_DSPM_NO_INSTANCE
Failure Cause
4-31
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Possible Solution
BSC_DSPM_NO_INSTANCE
DSPM
DSPMDSPMDSPMDSPM
1.
DSPMDSPM
2.
DSPMMP
3.
DSPM
4.
DSPM
4.70 BSC_NO_RTPPORT
Failure Name
BSC_NO_RTPPORT
Failure Cause
Failure Analysis
Handling Measure
1. In the case of external RTP, verify that the IPI board and RTP port are
correctly configured.
2. Verify that the IPI board where RTP port is located operates properly
and its version is correct.
3. Verify that the status of RTPPORT resource is normal during dynamic
management.
4. Verify that the RTPPORT resource quantity meets the requirements of
traffic capacity.
BSC_NO_RTPPORT
RTPPORTRTP
4-32
SJ-20120828144226-019|2012-10-20 (R1.0)
RTPPORTRTPRTPPORT
1. RTPIPIRTP
2.
RTPIPI
3.
RTPPORT
4.
RTPPORT
4.71 BSC_NO_VALID_RMP
Failure Name
BSC_NO_VALID_RMP
Failure Cause
Failure Analysis
Possible Solution
BSC_NO_VALID_RMP
RMP
RMPRMPRMP
1.
RMP
2.
RMPMP
3.
RMP
4.72 HO_STAT_CARRIER_NO_CE_LICENSE
Failure Name
HO_STAT_CARRIER_NO_CE_LICENSE
Failure Cause
Failure Analysis
Handling Measure
HO_STAT_CARRIER_NO_CE_LICENSE
4-33
SJ-20120828144226-019|2012-10-20 (R1.0)
1X CE
BTS1X CE
1.
CE_LICENSE
2.
BTS
4.73 HO_NoPilotAvailable_ERR
Failure Name
HO_NoPilotAvailable_ERR
Failure Cause
Failure Analysis
Handling Measure
HO_NoPilotAvailable_ERR
FailReason
4.74 ERR_SPS_RLSA_RCM_FCH_FunCallFail_Handler
AbisdfConnectAck_MCSHConstructAmdfFCHSet
up
Failure Name
ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup
Failure Analysis
Handling Measure
4-34
SJ-20120828144226-019|2012-10-20 (R1.0)
ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup
OMC
4.75 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHa
ndlerTCHfTSSetup_MHandlerAbisdfBTSSetup
Failure Name
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup
Failure Analysis
During call setup or handoff, an error occurs in handling the call setup or
handoff message .
Handling Measure
1. In the case that the BTS is in graceful degradation mode, when the BTS
receives the call setup or handoff message from the BSC, the BTS
reports the failure message. It is a normal case.
2. The RCM does not support concurrent setup flows. If the RCM receives
another call setup or handoff message during the leg setup process, the
RCM reports the failure message. If the problem occurs occasionally,
no troubleshooting is required.
3. If the BSSAP or DSPM handoff type is incorrect, the failure message is
also reported. If the problem occurs occasionally, no troubleshooting
is required.
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup
1.
BSC
2. RCM
3. BSSAPDSPM
4-35
SJ-20120828144226-019|2012-10-20 (R1.0)
4.76 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_H
andleAbisdfConnectAck_SoftHandoffLegNoInvalid
Failure Name
ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid
Failure Analysis
During call setup or handoff process, the leg number leg in the
AbisdfConnectAck message exceeds the maximum allowed value. A call
supports up to 12 legs. If the leg number exceeds 12, a call failure may
be caused.
Handling Measure
ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid
AbisdfConnectAck
1212
4.77 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHa
ndlerAbisdfBTSSetup_MCDHSaveToCommonData
Failure Name
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData
Failure Analysis
Handling Measure
If the a few such problems occur, ignore them. If a lot of such problems
occur, contact the local office of ZTE Corporation.
ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData
4-36
SJ-20120828144226-019|2012-10-20 (R1.0)
1.
2.
CICI
4.78 ERR_CES_RLSA_CEC_CALLHANDLER_V_Chan
nelType_Error
Failure Name
ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error
Failure Cause
In the case of soft handoff, during FCH setup, the incorrect channel type
causes the FCH setup failure.
Failure Analysis
Handling Measure
ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error
CHMCCM
CES
1.
2.
CHM
3.
CCM
4-37
SJ-20120828144226-019|2012-10-20 (R1.0)
4-38
SJ-20120828144226-019|2012-10-20 (R1.0)
Chapter 5
ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion
MSC
5.2 ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs
Failure Name
ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs
IMSI
IMSI
l
IMSI0
UIM
5-1
SJ-20120828144226-019|2012-10-20 (R1.0)
5.3 ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkF
ailure
Failure Name
ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure
Failure Cause
Failure Analysis
Handling Measure
It is a normal case. Trace it and find the IMSI information on the MSC side.
ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure
VLR/HLRIMSI
MSCIMSI
5.4 ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNo
tAllowed
Failure Name
ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed
Failure Cause
Failure Analysis
During registration, when the system wants to find the IMSI information in
VLR/HLR, it finds that the user is roaming in another place and the user has
no roaming rights. Hence, the registration fails.
Handling Measure
The user has no roaming rights; therefore, it is normal that the problem
is reported.
ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed
VLR/HLRIMSI
1.
2.
5-2
SJ-20120828144226-019|2012-10-20 (R1.0)
5.5 ERR_SPS_RLSA_BSSAP_Reg_Reject_Other
Failure Name
ERR_SPS_RLSA_BSSAP_Reg_Reject_Other
Failure Cause
Failure Analysis
The registration fails due to a cause other than network congestion, invalid
IMSI, network failure and no roaming rights.
Handling Measure
ERR_SPS_RLSA_BSSAP_Reg_Reject_Other
1.
2.
5.6 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Releas
e_In_Progress
Failure Name
ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress
Failure Cause
SCCP receives the repeated registration request from the same user,
causing the registration failure.
Failure Analysis
Handling Measure
ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress
SCCP
1.
2.
5-3
SJ-20120828144226-019|2012-10-20 (R1.0)
5.7 ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiU
nknown
Failure Name
ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiUnknown
Failure Cause
The MS whose number is not allocated on the HLR initiated a registration, and
the registration fails.
Failure Analysis
The number of the MS that initiates a registration is not allocated on the HLR.
Handling Measure
The problem rarely occurs. If this occurs, contact the ZTE local office or the
R&D personnel.
5-4
SJ-20120828144226-019|2012-10-20 (R1.0)
Chapter 6
ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNumOvld
Failure Cause
Failure Analysis
Handling Measure
Verify that the setting of the SMS overload threshold is reasonable and no
exception occurs during an SMS peak.
6.2 ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpda
te_SBSSRInvalidProcess
Failure Name
ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpdate_SBSSRInvalidProcess
Failure Cause
Failure Analysis
The PACA update fails when the MS transits to the target side completely.
Handling Measure
6.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7
BurstRequestReceived
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7BurstRequestReceived
Failure Cause
The target side receives a supplemental channel setup request from the
serving side when it does not finish the current non-network interconnection
handoff.
6-1
SJ-20120828144226-019|2012-10-20 (R1.0)
Failure Analysis
Handling Measure
6.4 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVE
RLOAD
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD
Failure Cause
Failure Analysis
Handling Measure
ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD
DSMPCPU
DSMPCPU
DSMP
6.5 INPUT_PARA_ERROR
Failure Name
INPUT_PARA_ERROR
Failure Cause
Failure Analysis
Possible Solution
Check the fault probe and take measures accordingly after identifying the
cause.
INPUT_PARA_ERROR
6-2
SJ-20120828144226-019|2012-10-20 (R1.0)
Walsh
6-3
SJ-20120828144226-019|2012-10-20 (R1.0)
6-4
SJ-20120828144226-019|2012-10-20 (R1.0)
Glossary
ABPM
- ABis Processing Module
- Abis
ACK
- ACKnowledgement
-
Abis
- Abis Interface between BSC and BTS
- BSCBTS
BDM
- Baseband Digital Module
BDM is a board in a micro-BTS, the functions of BDM are same as BDS in a
macro-BTS.
-
BS
- Base Station
-
BSC
- Base Station Controller
-
BSSAP
- Base Station System Application Part
-
BTS
- Base Transceiver Station
-
CCM
- Communication Control Module
-
CE
- Channel Element
-
CES
- Channel Element Subsystem
-
I
SJ-20120828144226-019|2012-10-20 (R1.0)
CHM
- Channel Processing Module
It completes forward modulation and reverse demodulation for baseband data of
the cdma2000-1X physical channel. As a concept corresponding to RF, baseband
refers to the signal before carrier modulation or after carrier demodulation.
-
CIC
- Circuit Identification Code
-
CMP
- Calling Main Processor
-
CPU
- Central Processing Unit
-
CSM
- Central Switching Module
-
DSM
- Data Service Module
Implements the Abis interface function between the IP BDS and the IP BSC, and
provides the conversion of IP packets into the E1/T1 signals that are suitable for
remote transmission before the signals are transmitted to the remote station.
-
DSMP
- Data Service Management Platform
-
DSP
- Digital Signal Processor
-
DTB
- Digital Trunk Board
-
ESN
- Electronic Serial Number
-
FO
- Frame Offset
-
II
SJ-20120828144226-019|2012-10-20 (R1.0)
Glossary
HGM
- HIRS GateWay Module
- HIRS
HIRS
- High-speed Interconnect Router Subsystem
-
HLR
- Home Location Register
-
IBBE
- Interface of BSC and BSC by Ethernet
- EthernetBSC
IMSI
- International Mobile Subscriber Identity
-
MGW
- Media Gateway
-
MS
- Mobile Station
-
MSC
- Mobile Switching Center
-
MSCe
- Mobile Switching Center emulator
-
OMC
- Operation & Maintenance Center
-
PCF
- Packet Control Function
PCF is a board which is responsible for the data selection between multiple
reverse traffic channels and data distribution from a forward traffic channel to
multiple cells/sectors during soft handoff.
-
PCM
- Pulse Code Modulation
-
III
SJ-20120828144226-019|2012-10-20 (R1.0)
PDSN
- Packet Data Service Node
-
R-SCH
- Reverse Supplemental Channel
-
RC
- Radio Configuration
-
RCM
- Radio Control Module
-
RMP
- Resource Main Processor
-
SCCP
- Signaling Connection Control Part
-
SCCP
- Signaling Connection Control Part
-
SCH
- Supplemental Channel
-
SDH
- Synchronous Digital Hierarchy
-
SDM
- Supervisory Division Multiplexing Board
-
SDU
- Selection and Distribution Unit
-
SDU
- Service Data Unit
-
SO
- Service Option
-
IV
SJ-20120828144226-019|2012-10-20 (R1.0)
Glossary
SSN
- Sub-System Number
-
UID
- User IDentifier
-
VLR
- Visitor Location Register
-
VTC
- Voice Transcoder Card
-
V
SJ-20120828144226-019|2012-10-20 (R1.0)