ZXC10 BSSBCDMA Base Station System Call Failure Reason and Call Drop Explanation (1X) Version 8.0.1.9 ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail:
[email protected] LEGAL INFORMATION Copyright © 2006 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. Additionally, the contents of this document are protected by contractual confidentiality obligations. All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION or of their respective owners. This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein. The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support or training are subject to change without notice. Revision History Date Revision No. Serial No. Reason for Revision 06/14/2007 R1.0 sjzl20071307 First edition ZTE CORPORATION Values Your Comments & Suggestions! Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers. Please fax to: (86) 755-26772236; or mail to Documentation R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057. Thank you for your cooperation! Document Name ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x) Product Version V8.0.1.9 Document Revision Number R1.0 Equipment Installation Date Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)
Good Your evaluation of this documentation
Fair
Average
Poor
Bad
N/A Accessibility: (Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
Bad
N/A Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A Please check the suggestions which you feel can improve this documentation: Your suggestions for improvement of this documentation
Improve the overview/introduction
Make it more concise/brief
Improve the Contents
Add more step-by-step procedures/tutorials
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Add more examples
Add more/better quick reference aids
Add more detail
Improve the index
Other suggestions __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ # Please feel free to write any comments on an attached sheet. If you wish to be contacted regarding your comments, please complete the following: Name Company Postcode Address Telephone E-mail This page is intentionally blank. Contents About this Manual ............................................................. i Purpose ................................................................................ i Intended Audience ................................................................. i Prerequisite Skill and Knowledge .............................................. i What is in This Manual ............................................................ i Related Documentation.......................................................... ii Conventions ......................................................................... ii How to Get in Touch............................................................. iii Chapter 1.......................................................................... 1 BSSAP Related Failures ................................................... 1 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified ... 1 ERR_SPS_RLSA_BSSAP_TE_T3230 .......................................... 2 ERR_SPS_RLSA_BSSAP_TE_Tassignment ................................. 2 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect ............... 3 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder .............. 4 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup ..................................... 4 ERR_SPS_RLSA_BSSAP_TE_T303............................................ 5 ERR_SPS_RLSA_BSSAP_TE_Txxp ............................................ 5 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr .......................................................................................... 6 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy...... 6 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing .......................................................................................... 7 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed....................... 7 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail ............................ 8 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer ..... 9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState....... 9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others ........................................................................................ 10 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut......................... 10 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerO n ...................................................................................... 11 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD own................................................................................... 11 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerE ntry__A7HOReqMsgProccessForHOWith1X .............................. 12 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit.................. 12 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBts Fail ................................................................................... 13 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSucces sful ................................................................................... 14 ERR_SPS_RLSA_BSSAP_TgtBSC_Other__TargetBSCHandler_A7fHa ndoffRequestProccess__RecievedA7HOReqWhenSemiHO........... 14 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurren tService ............................................................................. 15 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOptio n ...................................................................................... 15 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef ...... 16 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail................ 16 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailu re ..................................................................................... 17 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Authentication Failure ............................................................................... 17 Chapter 2........................................................................19 DSPM Related Failures...................................................19 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease .... 19 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder ............. 20 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure................ 21 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown ........ 21 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3 ............... 22 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequ estMsg_ReleasebyMSDTXTime .............................................. 23 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRem oveIndication_RSCHReleasebySDMDTXTime............................ 23 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndicatio n_ReleasebyHOH................................................................. 24 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstR elease_RSCHExistedCellReleasebyRCM ................................... 24 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Releas ebyCLH.............................................................................. 25 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRem oveIndication_RSCHReleasebySDMOtherReason ...................... 25 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRem oveIndication_FSCHReleasebySDMDuration............................. 26 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_H ardHandoff ......................................................................... 26 ...................................... 34 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup....................... 28 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure 28 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant ...................................................................................................................... 31 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearc hReport ........... 38 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Reso urce_Unavailable ...................... 38 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHby LegFail_ReleaseRschExistSDMLegFailure................................................................................... 42 SDM_Find_Fail_WaitConfigVTCTimeout ......................................................................................................................... 36 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAc k .............. 45 SDM_Find_Fail_WaitConfigRLPTimeout ................................................................................................. 39 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequ estMsg_FCHNotExisted ............................................................................................................. 39 Chapter 3.......... 29 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease....................................... 43 SDM_Link_Fail_RevNoFrm ......................... 44 SDM_Link_Fail_FwdA2pNoFrm ............................... 32 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq................................ 41 SDM Related Failures......................................ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop .............. 30 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq ....... 34 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD ............................................. 44 SDM_Link_Fail_RevTooManyBadFrm ................................ 27 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstR elease_FSCHExistedCellReleasebyRCM ...... 45 .................................................................... 41 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm ............. 27 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppen ding_ReleasebyTDropPending .......................................................... 33 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_U nspecified ........... 29 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion ............................. 41 SDM_Activate_Fail_AcquirePreambleFail_Normal ........................................................................................ 37 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_A dministratively_Pohibited ..... 35 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Tshakehandrecv .... 35 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocomple tion..................................................................................................... 32 ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailur e ........................ ....... 61 HO_STAT_PILOT_IS_NOT_NEIGHBOR ....................... 60 HO_STAT_CARRIER_NO_5KCE ...... 51 DBS_STASTIC_NO_RESOURCE_LACK ............................................................................ 49 DBS_STASTIC_FWDFCHCE_LACK .......................................................................................... 62 HO_STAT_PILOT_NOT_LOCALBSS .......................................49 DBS Related Failures. 56 BEFORE_CPS .................................... 50 DBS_STASTIC_UID_LACK................................................................... 47 SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut ................. 59 HO_STAT_CARRIER_PWR_OVERLOAD ........................................ 55 FO_NOT_ENOUGH ..... 58 HO_STAT_PILOT_NO_SAME_FREQ.............................. 47 SDM_Find_Fail_NoFCHLeg ..................................................................................................... 53 POWER_NOT_ENOUGH.............. 50 DBS_STASTIC_WALSHCODE_LACK ..................... 52 ARRIVE_TIME_ERROR ....................................................... 63 BSC_NO_SE ............................................................... 56 WALSHCODE_NOT_ENOUGH .......................... 54 NO_AVAILABLE_REV_CE .................................................................. 52 NO_SYSTEM_TIME..... 53 INPUT_PARA_ERROR ..................................................................................... 48 SDM_Activate_Fail_MsgParaFail....................................................................................................................................................... 57 RS_NOT_EXIST................. 58 ALLOCATE_UID_ERROR.................49 DBS_STASTIC_FWDFCHCE_REVCE_LACK............................................................ 51 FCH_NUMBER_TWO ................... 60 HO_STAT_CARRIER_NO_CE........................................................................ 54 SOFTADD_CELL_ERROR ........ 63 BSC_NO_CIC ....................................................................................... 64 ................................... 48 Chapter 4......... 59 HO_STAT_CARRIER_STATE_ERROR .................................................................. 46 SDM_Activate_Fail_InitVocoderFail ......................................... 55 CE_NOT_ENOUGH ..........................................SDM_Link_Fail_RSCHLegLinkFail ................................................................... 61 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO ................................................................................................................................................................................................................... 57 UIDWIDTH_NOT_ENOUGH ........................... 46 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm .................. 62 HO_STAT_PILOT_IS_OTHER_UNLNKBSS .................................... ................. 79 CES Related Failures ................. 80 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CEMCTRL_NULL ............... 79 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT .................... 76 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_S ameTimeCellInSameGroupInDiffSetupFlow ................................................ 75 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch.................................................................... 80 .... 72 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail ...................................................... 72 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_R emovedSCH .................... 65 BSC_DSPM_NO_INSTANCE............................. 74 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_S pecifiedCellIsReleasing................................ 66 BSC_NO_VALID_RMP .................................. 64 BSC_NO_IWF ............... 70 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch ........................................................... 77 Chapter 6.............. 66 Chapter 5............... 71 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail .................... 73 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSC HResourceExtension ........ 67 RCM Related Failures ..................... 75 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemi Soft_AbisdfBurstRequest.................................................................................................................................................................................. 68 ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired ..................................................BSC_NO_VE ..................... 77 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgDi spatch ...................................... 76 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_ConnInSet up ................................................................................... 67 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ ........... 74 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired .... 69 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH ...... 67 ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate............................................................................................................................................. 70 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail ......... 65 BSC_NO_RTPPORT ...... 73 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration ............................ 69 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH ... 71 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb ............................................................................................................ 79 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED ..... .......................................................................................ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS .........................83 ......................................... 81 Tables ............. Intended Audience This document is intended for engineers and technicians who perform operation activities on the ZXC10 BSSB (V8.About this Manual Purpose This Manual provides information about the ZXC10 BSSB (V8.9) (1x) Base Station System local operating procedures What is in This Manual This Manual contains the following chapters: TABLE 1 CHAPTER SUMM ARY Chapter Summary Chapter 1 BSSAP related Failures Describes the Failure analysis and troubleshooting for failures related to BSSAP Chapter 2 DSPM related Failures Describes the Failure analysis and troubleshooting for failures related to DSPM Chapter 3 SDM related Failures Describes the Failure analysis and troubleshooting for failures related to SDM Confidential and Proprietary Information of ZTE CORPORATION i .1.0.0.1.0.1.9) Call Failure and Call Drop for the (1x) system.9) (1x) Base Station System. Familiarity with the following is helpful: ZXC10 BSSB (V8. users should have a general understanding of wireless telecommunications technology. Prerequisite Skill and Knowledge To use this document effectively. 1. Bold Menus.0. and function names.1.1. | Select one of the parameters that are delimited by it.0. ZXC10 BSSB (V8. program code. menu options.9) Call Failure Reason and Call Drop Explanation (1x) Chapter Summary Chapter 4 DBS related Failures Describes the Failure analysis and troubleshooting for failures related to DBS Chapter 5 RCM related Failures Describes the Failure analysis and troubleshooting for failures related to RCM Chapter 6 CES related Failures Describes the Failure analysis and troubleshooting for failures related to CES Related Documentation The following documentation is related to this manual: ZXC10 BSSB (V8. Constant width Text that you type.9) CDMA2000 Base Station System General Description. window names. Note: Provides additional information about a certain topic. CAPS Keys on the keyboard and buttons on screens and company name. radio button names.ZXC10 BSSB (V8. input fields. {} Mandatory parameters. [] Optional parameters. ii Confidential and Proprietary Information of ZTE CORPORATION . TABLE 2 TYPOGRAPHICAL CONVENTIONS Typeface Meaning Italics References to other Manuals and documents. check boxes. Tip: Indicates a suggestion or hint to make things easier or more productive for the reader. “Quotes” Links on screens.0. dialog box names.9) CDMA2000 Base Station System Common Operation Manual Conventions Typographical Conventions ZTE documents employ the following typographical conventions. files and directory names. function names. dropdown lists. Checkpoint: Indicates that a particular step needs to be checked before proceeding further. You can also call our customer support center at (86) 755 26771900 and (86) 800-9830-9830. Double-click Refers to quickly clicking the primary mouse button (usually the left mouse button) twice.com. or you can fax your comments and suggestions to (86) 755 26772236. How to Get in Touch The following sections provide information on how to obtain support for the documentation and the software. which contains various interesting subjects like documentation. Customer Support Documentation Support If you have problems. or suggestions regarding your product. comments. ZTE welcomes your comments and suggestions on the quality and usefulness of this document.com. forum and service request.cn. For further questions. contact us by e-mail at support@zte. Drag Refers to pressing and holding a mouse button and moving the mouse.com.About this Manual Mouse Operation Conventions TABLE 3 MOUSE OPERATION CONVENTIONS Typeface Meaning Click Refers to clicking the primary mouse button (usually the left mouse button) once. questions. Right-click Refers to clicking the secondary mouse button (usually the right mouse button) once. You can also browse our website at http://support. comments.cn. Confidential and Proprietary Information of ZTE CORPORATION iii .cn.zte. you can contact us by e-mail at doc@zte. or suggestions on the documentation. knowledge base. 0.9) Call Failure Reason and Call Drop Explanation (1x) This page is intentionally blank.1. iv Confidential and Proprietary Information of ZTE CORPORATION .ZXC10 BSSB (V8. Such as timer expiration and access failure. analysis and the possible solutions are described in tables against each error as shown below. The cause is unknown Failure analysis 1.Chapter 1 BSSAP Related Failures This chapter introduces and describes call failures related to BSSAP and also discusses about possible troubleshooting methods. The failure cause. ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_Unspecified TABLE 4 ERR_SPS_RLS A_BSS AP_FCHSETUP_CLEARCOMMAND_ UNSPECIFIED Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand _Unspecified Failure Cause When a call is being setup. in this case. The cause carried in ClearCommand is Cause_A_CallProcessing.MSC sends a ClearCommand message to release the call. otherwise. cooperate with MSC side to find out the cause Confidential and Proprietary Information of ZTE CORPORATION 1 . change it to the BSC internal cause value (ERR_SPS_RLSA_BSSAP_FchSetup_ClearComman d_Unspecified). The cause value carried in Layer3 is 0x1f. Possible Solution It is acceptable if the problem occurs occasionally. this cause value is filled in. It is used a lot at switch side. non-standard cause value in A-interface protocol are carried in the Cause of ClearCommand； 2. 2 Confidential and Proprietary Information of ZTE CORPORATION . Check No. add more modules for DSMP 4. DSMP CPU utilization is too high 4. If SDM activation expires. Check the setting of the timer Tassignment on CMP.if the SccpConnect message is not received from the opposite side. SDM activation expires 1.1.ZXC10 BSSB (V8.0. T3230 expires Possible solution 1.BSSAP sends an EV_S_AvfServiceAssignment message to DSMP.perhaps the link is unstable 2.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_TE_T323 0 TABLE 5 ERR_SPS_RLS A_BSS AP_TE_T3230 Failure Name ERR_SPS_RLSA_BSSAP_TE_T3230 Failure Cause When a call is being setup. Check the fiber connections at media plate and the SDU subcards. Check if there are too many DSMP instances in the correlation of RMP and DSMP (different DSMP version supports different number of instance). DSMP is configured with too many instances (more than the number of DSMP instance that are supported).if the EV_S_AvrAssignmentComplete message or EV_S_AvrAssignmentFailure message is not received from DSMP.7 signaling link. 3. Failure Cause Most likely causes: 1. 3. More signaling links are needed.timer Tassignment expires too soon 2. If DSMP CPU utilization is too high. ERR_SPS_RLSA_BSSAP_TE_Tass ignment TABLE 6 ERR_SPS_RLS A_BSS AP_TE_TASSIGNMENT Failure Name ERR_SPS_RLSA_BSSAP_TE_Tassignment When a handset originates a call or be called. after BSSAP sending the CMServiceRequest or PagingResponse message to MSC.the default value is 6000 (6 seconds). Possible Solution 2.the media stream between SDU and CHM may be different.the timer Tassignment expires. or the clock between BSC and BTS is different. Traffic is too heavy at present. 254) of the local end and the opposite end 3. 3. handset does not assign numbers correctly at MSC side 4.SccpDisconnectmessage is received.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_FchSetu p_RcvSccpDisconnect TABLE 7 ERR_SPS_RLS A_BSS AP_FCHSETUP_RCVSCCPDISCONNECT Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect When a handset originates a call or be called. No. cell CI is different from the CI at MSC side 1. 1. Confidential and Proprietary Information of ZTE CORPORATION 3 . after sending a CMServiceRequest or PagingResponse message to MSC. Make sure the cell CI in the call origination message CMServiceRequest is configured correctly at MSC side. Make sure if the IMSI and ESN of the handset distributes numbers correctly at MSC side 4. 2.SCCP connection establishing fails or be removed accidentally.7 signaling link unstable or link is in wrong state. Failure Cause Most likely causes: 1. SSN is in wrong state. Check the BSC and MSC side to see if they are configured with SSN (0. Check the state of the signaling point on CMP with database probe to see if it is 0 Possible Solution 2. Check if there are enough CE and FO resource on BTS. Check the lifecycle of the predefined timer Tfchsetup. default value should be 5000 (5 seconds). or decrease antenna transmission power to reduce users. adjust CCM CPU overload threshold. Most likely causes: 1. Possible Solution 4 2. if it expires too soon.0. Confidential and Proprietary Information of ZTE CORPORATION . Timer Tfchsetup expires too soon. BSC sends an AbisdfBTSSetupmessage to BTS to request the fundamental channel establishment. change the default value to 5000. 3.ZXC10 BSSB (V8. 2. fail to establish fundamental channel on BTS 3. but the AbisdrBTSSetupAck message that indicates fundamental channel establishing is successful or unsuccessful is not received from BTS.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_FchSetu p_RcvMSReleaseOrder TABLE 8 ERR_SPS_RLS A_BSS AP_FCHSETUP_RCVMSRELEASEORDER Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder Failure Cause When a call is setup. If CCM CPU utilization is too high. the timer Tfchsetup on CMP expires. handset initiates the release on control channel Possible Solution No troubleshooting is needed ERR_SPS_RLSA_BSSAP_TE_Tfch setup TABLE 9 ERR_SPS_RLS A_BSS AP_TE_TFCHSETUP Failure Name ERR_SPS_RLSA_BSSAP_TE_Tfchsetup Failure Cause Timer Tfchsetup expires Failure Analysis When a call is setup. CCM CPU utilization is too high 1.1. Check the timer T303 on CMP. CallHandler process sends an A1rAssignmentCompletmessage to MSCe. MSC side has problem on call processing Possible Solution 1. 3. Txxp timer expires too soon. MSCe side has problem on call processing Possible Solution 1. Txxp expiration indicates MSCe side has problem to process the call. Find MSC call failure causes at MSC side. default value is (6 seconds ) 2.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_TE_T303 T A B L E 1 0 E R R _ S P S _ R L S A _ B S S AP _ T E _ T 3 0 3 Failure Name ERR_SPS_RLSA_BSSAP_TE_T303 Failure Cause timer T303 expires Failure Analysis When a handset originates a call or be called. Upon receiving the assignment complete message. set the timer Txxp to wait for the A1pfBearerUpdateRequestmessage from MSCe. T303 indicates MSC side has problem to process this call. If the A1pfBearerUpdateRequestmessage from MSCe is not received before Txxp expires. the T303 timer on CMP will expire. If Ap interface is supported. 2. Confidential and Proprietary Information of ZTE CORPORATION 5 . Check the setting of timer Txxp on CMP. ERR_SPS_RLSA_BSSAP_TE_Txxp T A B L E 1 1 E R R _ S P S _ R L S A _ B S S AP _ T E _ T X X P Failure Name ERR_SPS_RLSA_BSSAP_TE_Txxp Failure Cause Timer Txxp expires Failure Analysis 1. Use MSC tools to find out the problem cause.after sending a CMServiceRequest or PagingResponse message to MSC.if AssignmentRequestmessage is not received. Find the call failure causes at MSCe side. MSCe is needed to find out the problem cause. The default value is 6 seconds 2. T303 timer expires too soon 2. Most likely causes: 1. 0.1. the failure cause will be reported. If it fails to invoke. the cause value in the field CauseLayer3 carried by this message is 0x11. ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_UserBusy T A B L E 1 3 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ USERBUSY 6 Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBu sy Failure Cause When a call is setup.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_DB_Get BoardOrIndexNetAddrByLogicAddr T A B L E 1 2 E R R _ S P S _ R L S A _ B S S AP _ D B _ G E T B O A R D O R I N D E X N E T A D D R BYLOGICADDR Failure Name ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrBy LogicAddr Failure Cause Fail to retrieve board network address according to board logical address Failure Analysis When BSC sends messages to BTS. it invokes the database interface to retrieve BTS address. This is a normal release.ZXC10 BSSB (V8. Possible Solution Check the Abis interface to see if it unstable. Failure Analysis Likely cause: Possible Solution No troubleshooting is needed Called users are busy Confidential and Proprietary Information of ZTE CORPORATION .BSC receives the ClearCommand message sent from MSC. Transmission must be checked. which indicates the called user is busy. the cause value in the field CauseLayer3 carried by this message is 0x10. BSC receives the ClearCommand message sent from MSC. which indicates it is a normal release. Failure Analysis Likely cause: Possible Solution No troubleshooting is needed release initiated at MSC side ERR_SPS_RLSA_BSSAP_ByteInde x_IndexInUsed T A B L E 1 5 E R R _ S P S _ R L S A _ B S S AP _ B Y T E I N D E X _ I N D E X I N U S E D Failure Name Failure Cause ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed When a call is setup.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_NormalClearing T A B L E 1 4 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ NORM ALCLEARING Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Normal Clearing Failure Cause When a call is setup. BSSAP module detects that the instance number is in use in instance number distribution. Failure Analysis Likely cause: Possible Solution Check abnormal probe BSSAP module records a wrong instance number Confidential and Proprietary Information of ZTE CORPORATION 7 . check the group number of CE on CHM Further Trouble shootin g 8 Make sure the software versions run on BSC and BTS are the same. Most likely cause: 1.ZXC10 BSSB (V8.CE resource shortage.0. CE resource is in wrong state Failure Analysis 2. Check the UID state or media plate link with database probe 5. But all the cells in the AbisdrBTSSetupAck returned by BTS fail to establish. check the state of carrier (normal or blocked) 4. the exact failure causes can be found from the failure cause in AbisdrBTSSetupAckmessage: 0x5101 indicates forward fundamental channel CE shortage 0x5102 indicates fundamental channel reverse CE shortage Possible Solution 0x5103 indicates fundamental channel forward shortage and reverse CE shortage 0x5105 indicates WalshCode shortage 0x5106 indicates UID is incorrect 2. Confidential and Proprietary Information of ZTE CORPORATION . check the state of CE (normal or blocked) 3.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_FchSetu p_AllLegFail T A B L E 1 6 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ A L L L E G F A I L Failure Name Failure Cause ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail When a call is setup.WASH code shortage 3.UID is in wrong state or media plate link is incorrect 5.Carrier is in wrong state 1. FO shortage 4.1. BSC sends an AbisdfBTSSetupmessage to BTS to request BTS to establish the fundamental channel. which indicates it rings without answer. otherwise. further analysis is needed. Confidential and Proprietary Information of ZTE CORPORATION 9 . the call establishment message is received. the cause value in the field CauseLayer3 carried by this message is 0x13. Failure Analysis Likely cause: Possible Solution This is normal Nobody answers the release initiated by MSC ERR_SPS_RLSA_BSSAP_UnexptM sg_RcvOrgnInSessionState T A B L E 1 8 E R R _ S P S _ R L S A _ B S S AP _ U N E X P T M S G _ R C V O R G N I N SESSIONSTATE Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionSt ate Failure Cause During call status. This is normal. Failure Analysis Possible Solution Likely cause: When users originate call.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_NoAnswer T A B L E 1 7 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ NO ANSWER Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAn swer Failure Cause When a call is setup. and the process does not release the message. the call fails. BSC receives the ClearCommand message sent from MSC. It is acceptable if the problem occurs occasionally. the timer that waits for the DSPM handshake message expires Possible Solution Further Trouble shootin g 10 1. This register message may be of the other type like the timing register. otherwise. check timer setting Check the running of DSPM module Confidential and Proprietary Information of ZTE CORPORATION . Possible Solution It is acceptable if the problem occurs occasionally. further analysis is needed. Failure Analysis During a call. Check the foreground mp board of BSC 3.ZXC10 BSSB (V8. the register message is received other then the Power ON and Power OFF. Check handset state 2. ERR_SPS_RLSA_BSSAP_HandSh ake_TimeOut T A B L E 2 0 E R R _ S P S _ R L S A _ B S S AP _ H A N D S H A K E _ T I M E O U T Failure Name ERR_SPS_RLSA_BSSAP_ShakeHand_TimeOut Failure Cause Bssap Dspmhandshake expires Failure Analysis When a call is established.0. a register message is received.1.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_UnexptM sg_RcvRegInAssignState_Others T A B L E 1 9 E R R _ S P S _ R L S A _ B S S AP _ U N E X P T M S G _ RCVREGINASSIGNSTATE_OTHERS Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_O thers Failure Cause During call status. The user in a call presses power off button. It is acceptable if the problem occurs occasionally. The user originates a Power OFF due to which the process does not release and the call fails. further analysis is needed. 2. power on and register before the process release. Or battery runs out during a call. otherwise. depending on the terminal processing flow Confidential and Proprietary Information of ZTE CORPORATION 11 . power on and registers before the process release.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_UnexptM sg_RcvRegInAssignState_PowerOn T A B L E 2 1 E R R _ S P S _ R L S A _ B S S AP _ U N E X P T M S G _ RCVREGINASSIGNSTATE_POWERON Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignStat e_PowerOn Failure Cause power on registration message is received during a call Failure Analysis Possible Solution Take off the battery during a call. This is because of handset. ERR_SPS_RLSA_BSSAP_UnexptM sg_RcvRegInAssignState_PowerDo wn T A B L E 2 2 E R R _ S P S _ R L S A _ B S S AP _ U N E X P T M S G _ RCVREGINASSIGNSTATE_POWERDOWN Failure Name ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignStat e_PowerDown Failure Cause power off registration message is received during a call Failure Analysis Possible Solution 1. the circuit reset message sent from MSC is received.0. If the PN configuration of neighbor cell is reasonable or not ERR_SPS_RLSA_BSSAP_Other_R eceiveResetCircuit T A B L E 2 4 E R R _ S P S _ R L S A _ B S S AP _ O T H E R _ R E C E I V E R E S E T C I R C U I T Failure Name Failure Cause Failure Analysis Possible Solution Further Trouble shootin g 12 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit When a call or a hard handoff adding is being established.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_TgtBSC_ FunCallFail__TargetBSCHandlerEntr y__A7HOReqMsgProccessForHOWi th1X T A B L E 2 3 E R R _ S P S _ R L S A _ B S S AP _ T G T B S C _ F U N C A L L F A I L _ _ T A R G E T B S C H A N D L E R E N T R Y _ _ A7 H O R E Q M S G P R O C C E S S F O R H O W I T H 1 X Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSC HandlerEntry__A7HOReqMsgProccessForHOWith1X Failure Cause The target BSC interconnects with the Hirs BSC.The number of cell is greater than the maximum number of cell that a call occupies 2. The handoff request processing is abnormal. Neighbor cell is not configured. Failure Analysis Possible Solution 1.1. 1. CIC coding at MSC side and BSC side is different 1. Check CIC state at MSC side and BSC side 2. CIC state at MSC side and BSC side is different 2.ZXC10 BSSB (V8. Check interconnection configurations 2. Check the PCM number at both sides of MSC and BSC to see if it is the same as the real E1 wiring Cooperate with MSC side to find out the cause Confidential and Proprietary Information of ZTE CORPORATION . 1. fail to retrieve power parameters from database Failure Analysis 3. fail to send the Extended Channel Assignment Message to all BTS 1. Check more detailed information by checking abnormal probe 2. Fail to retrieve system ID/subsystem ID according to PN when sending the ECAMmessage 4. In ECAM/CAMmessage creation. Check version compatibility Confidential and Proprietary Information of ZTE CORPORATION 13 . no established cell is found 2.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_FchSetu p_SendChannelAssignment_AllBtsF ail T A B L E 2 5 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ S E N D C H A N N E L ASSIGNMENT_ALLBTSFAIL Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignm ent_AllBtsFail Failure Cause When a call is setup. fail to retrieve interface board （abpm/hgm and etc） address from database when sending the ECAMmessage 6. In ECAM/CAMmessage creation. If there are inter BSC assignments. there are coding errors when sending the ECAMmessage 5. perhaps fail to retrieve BSC interconnection interface board address Possible Solution 1. Failure Analysis Source side initiates a new handoff before semi-soft handoff flow completes. ERR_SPS_RLSA_BSSAP_TgtBSC_ Other__TargetBSCHandler_A7fHan doffRequestProccess__RecievedA7 HOReqWhenSemiHO T A B L E 2 7 E R R _ S P S _ R L S A _ B S S AP _ T G T B S C _ O T H E R _ _ TARGETBSCHANDLER_ A7FHANDOFFREQUESTPROCCESS__RECIEVED A7HOR EQWHENSEMIHO 14 Failure Name ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandl er_A7fHandoffRequestProccess_RecievedA7HOReqWhen SemiHO Failure Cause In semi-soft handoff.ZXC10 BSSB (V8. A7 Handoff Requestmessage will be discarded if it is received.1. cooperate with MSC side for troubleshooting. Possible Solution It is acceptable if the problem occurs occasionally. This failure should not occur when a call is being setup If the failure occurs when a call is being setup. otherwise. 2. If the hard handoff flow is successful. check the BSC at source side. Confidential and Proprietary Information of ZTE CORPORATION . Clear Command message will be received from MSC. the cause value carried in ClearCommand is ”hard handoff is successful” Failure Analysis Possible Solution 1.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_HandoffSuccessf ul T A B L E 2 6 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ HANDOFFSUCCESSFUL Failure Name RR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Hando ffSuccessful Failure Cause When a call is being setup or during a call.0. if the ClearCommand message sent from MSC is received. cooperate with MSC side to handle the problem.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_SemiConcurrent Service T A B L E 2 8 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ SEMICONCURRENTSERVICE Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Semi ConcurrentService Failure Cause When a call is setup. the cause value carried in ClearCommand is “pseudo concurrent service” Failure Analysis When the data service is started. The SO carried in call origination message is invalid (not the SO defined in the protocol) Possible Solution Determine what the SO is in call origination message and if the terminal is old or faulty. there is a new voice incoming call. ERR_SPS_RLSA_BSSAP_MsgPara _Origination_InvalidServiceOption T A B L E 2 9 E R R _ S P S _ R L S A _ B S S AP _ M S G P A R A _ O R I G I N A T I O N _ INVALIDSERVICEOPTION Failure Name ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidSer viceOption Failure Cause The SO carried in call origination message is invalid Failure Analysis Terminal cause.in the forward fundamental channel establishemnt. MSC sends out a ClearCommand to request MS to enter Dormant state Possible Solution This failure is acceptable. Confidential and Proprietary Information of ZTE CORPORATION 15 . If there are a lot of such failures. the ClearCommand message sent from MSC is received. Failure Analysis Hash deadlock may occur Possible Solution Save the abnormal probe information and contact ZTE office.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_BSSAP_HashOpr _AddItem_SccpId2CallRef T A B L E 3 0 E R R _ S P S _ R L S A _ B S S AP _ H A S H O P R _ A D D I T E M _ SCCPID2CALLREF Failure Name ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2Call Ref Failure Cause When adding the SCCP connection number into the HASH entry of call reference number.1.ZXC10 BSSB (V8. Failure Analysis the interface between modules are faulty Possible Solution Save the abnormal probe information and contact ZTE office.0. Confidential and Proprietary Information of ZTE CORPORATION . Hash operation fails. ERR_SPS_RLSA_BSSAP_Other_G et97DMTMsParaFail T A B L E 3 1 E R R _ S P S _ R L S A _ B S S AP _ O T H E R _ G E T 9 7 D M T M S P A R A F A I L 16 Failure Name ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail Failure Cause The 97D parameters fail during call. MSC sends out a ClearCommand message to release the call because of authentication failure Failure Analysis Perhaps terminal is invalid Possible Solution Co-operate with MSC side to find out the cause Confidential and Proprietary Information of ZTE CORPORATION 17 . Failure Analysis cooperate with MSC side to find out the cause Possible Solution It is acceptable if the problem occurs occasionally.Chapter 1 BSSAP Related Failures ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_EquipmentFailur e T A B L E 3 2 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ EQUIPMENTFAILURE Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Equip mentFailure Failure Cause When a call is setup.the failure cause is device malfunction. otherwise.MSC sends out a ClearCommand message to release the call. cooperate with MSC side to find out the cause ERR_SPS_RLSA_BSSAP_FchSetu p_ClearCommand_AuthenticationFai lure T A B L E 3 3 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _ AUTHENTICATIONFAILURE Failure Name ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Auth enticationFailure Failure Cause When a call is setup. 0. 18 Confidential and Proprietary Information of ZTE CORPORATION .1.9) Call Failure Reason and Call Drop Explanation (1x) This page is intentionally blank.ZXC10 BSSB (V8. Chapter 2 DSPM Related Failures This chapter introduces and describes failures related to DSMP and also discusses about possible troubleshooting methods. ERR_SPS_RLSA_DSPM_CLH_Oth erReason_MSNormalRelease TABLE 34 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_ MSNORM ALRELEASE Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRel ease Failure Cause Normal call release autonomously initiated by handset Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION 19 . analysis and the possible solutions are described in tables against each error as shown below. The failure cause. clock and the GCM board at BTS side and BSC side Check the versions and running of ABPM. BTS and BSC have different clock 3. Poor radio condition results in air-interface handshake message missing. It is acceptable if this failure occurs occasionally. Check transmission power of the cell 2. Once the effect scope is determined. DTB and DSM Confidential and Proprietary Information of ZTE CORPORATION . all base stations (under an ABPM) or BSC 4. 1. If frame number checking is enabled.1.after successfully entering traffic channel and capturing the prefix.0. Check the version compatibility and running of CHM and SDU board Possible Solution Further Trouble shootin g 20 3. If there are a lot of such failures. Other causes: Bit error and etc. Most likely causes: Failure Analysis 1. disable the frame number checking on the faulty BTS. If the situation becomes better.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_CLH_Tim erExpired_Twaitorder TABLE 35 ERR_SPS_RLSA_DSPM_CLH_TIMEREXPIRED_TWAITORDER Failure Name Failure Cause ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder When MS originates a call or be called. determine the problem effect scope firstly: single base station. it is believed that problem occurs because the BTS clock and BSC clock are different. airinterface traffic channel signaling handshake expires. 2.ZXC10 BSSB (V8. Check the GPS. If the handsets in a certain model always suffer from negotiation failure. the service negotiation between base station and MS fails Most likely cause: Failure Analysis 1. It is acceptable if this failure occurs occasionally. check the VTC working mode setting in BSS (default setting is 8K+EVRC) 3.Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_CLH_Oth erReason_SNFailure TABLE 36 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_SNFAILURE Failure Name Failure Cause ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure When MS originates a call or be called. 2. Poor radio condition causes air-interface negotiation message missing. Replace several combinations for testing. Further Trouble shootin g If the problem remains. capture the call failure signaling and contact the ZTE office ERR_SPS_RLSA_DSPM_CLH_Oth erReason_MSPowerDown TABLE 37 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_MSPOWERDOWN Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDow n Failure Cause Call release initiated by handset power off Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION 21 . Check the forward power of the cell Possible Solution 2. VTC working mode setting in BSS has a problem 1. after entering traffic channel. 1. after A8 link establishing. Tpcfinfol3timer setting has a problem 2.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_CLH_Tim erExpired_Tpcfinfol3 TABLE 38 ERR_SPS_RLSA_DSPM_CLH_TIMEREXPIRED_TPCFINFOL3 Failure Name Failure Cause Failure Analysis ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3 In data service call establishing stage. corresponding SDU runs abnormally 1.timer Tpcfinfol3 expires Most likely cause: 1. Check the version and running status of SDU Confidential and Proprietary Information of ZTE CORPORATION . If the setting of Tpcfinfol3timer on DSMP board is correct (default value is 3s） Possible Solution Further Trouble shootin g 22 2.0. Check the corresponding SDU when the problem occurs.ZXC10 BSSB (V8. Make sure if there is abnormal reset or switchover. DSPM sends an Abaf_PCFInfoL3message to SDM. no message is received in Tpcfinfol3（3s）. Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnUmrSCHRequ estMsg_ReleasebyMSDTXTime TABLE 39 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHONUMRSCHREQUESTMSG_RELEASEBYMSDTXTIME Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUm rSCHRequestMsg_ReleasebyMSDTXTime Failure Cause RSCH DTXTime release initiated by handset Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnAbarSCHRem oveIndication_RSCHReleasebySDM DTXTime TABLE 40 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHON ABARSCHREMOVEINDICATION_RSCHRELEASEBYSDMDTXTIME Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason _SCHHOnAbarSCHRemoveIndication_RSCHReleasebySD MDTXTime Failure Cause RSCH DTXTime release initiated by SDM Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION 23 . ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHPNDropIndication _ReleasebyHOH TABLE 41 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHPNDROPINDICATION_RELEASEBYHOH Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDro pIndication_ReleasebyHOH Failure Cause SCH release triggered by soft Hand Off remove on fundamental channel Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnAbisdrBurstRel ease_RSCHExistedCellReleasebyR CM TABLE 42 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHON ABISDRBURSTRELEASE_RSCHEXISTEDCELLRELEASEBYRCM 24 Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbi sdrBurstRelease_RSCHExistedCellReleasebyRCM Failure Cause RSCH release initiated at BTS side Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION . Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHRelease_Release byCLH TABLE 43 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHRELEASE_RELEASEBYCLH Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleas e_ReleasebyCLH Failure Cause SCH release triggered by call release Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnAbarSCHRem oveIndication_RSCHReleasebySDM OtherReason TABLE 44 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHON ABARSCHREMOVEINDICATION_RSCHRELEASEBYSDMOTHERREASO N Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAba rSCHRemoveIndication_ RSCHReleasebySDMOtherReason Failure Cause SDM initiate RSCHOther causes release Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION 25 . ZXC10 BSSB (V8.1. SDM initiates FSCH release Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHFSCHHandoff_Ha rdHandoff TABLE 46 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHFSCHHANDOFF_HARDHANDOFF Failure Name Failure Cause 26 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCH Handoff_HardHandoff SCH forward judges that a hard HO is to be done. hence there is a SCH release Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION .0.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnAbarSCHRem oveIndication_FSCHReleasebySDM Duration TABLE 45 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHON ABARSCHREMOVEINDICATION_FSCHRELEASEBYSDMDURATION Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAba rSCHRemoveIndication_FSCHReleasebySDMDuration Failure Cause When the SCH dispatch timer is timeout. Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_SCHH_Ti merExpired_Tfschdrop TABLE 47 ERR_SPS_RLSA_DSPM_SCHH_TIMEREXPIRED_TFSCHDROP Failure Name ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop Failure Cause release caused by FSCH due to timeout Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnTfschdroppend ing_ReleasebyTDropPending TABLE 48 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHONTFSCHDROPPENDING_RELEASEBYTDROPPENDING Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfs chdroppending_ReleasebyTDropPending Failure Cause release caused by FSCH due to timeout Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION 27 . When checking the handoff.A10 link establishing fails Check the version and running of PCF board Confidential and Proprietary Information of ZTE CORPORATION . Check the IMSI. A10 link establishing fails 1.1. corresponding PCFruns abnormally 2.0.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnAbisdrBurstRel ease_FSCHExistedCellReleasebyR CM TABLE 49 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHON ABISDRBURSTRELEASE_FSCHEXISTEDCELLRELEASEBYRCM Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbi sdrBurstRelease_FSCHExistedCellReleasebyRCM Failure Cause FSCH release initiated at BTS side Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_CLH_Oth erReason_PCFEquipmentFailure TABLE 50 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_ PCFEQUIPMENTFAILURE Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmen tFailure Failure Cause abnormal call release initiated by PCF Failure Analysis Possible Solution Further Trouble shootin g 28 Most likely cause: 1. HI and DI carried by A9SetupA8message 2.ZXC10 BSSB (V8. the normal call release initiated by PCF Failure Analysis Normal release Possible Solution Normal release Confidential and Proprietary Information of ZTE CORPORATION 29 .Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_CLH_Oth erReason_MSGoingIntoDormant TABLE 51 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_ MSGOINGINTODORM ANT Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingInto Dormant Failure Cause In data service. the call release autonomously initiated by handset Failure Analysis Normal release Possible Solution Normal release ERR_SPS_RLSA_DSPM_CLH_Oth erReason_PCFNormalRelease TABLE 52 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_ PCFNORM ALRELEASE Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRel ease Failure Cause In data service. g.0.1. Poor radio condition causes the air-interface handshake message missing. DTB and DSM Confidential and Proprietary Information of ZTE CORPORATION . base station sends out a handoff indication (HDM).9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_HOH_Tim erExpired_SoftHOThocompletion TABLE 53 ERR_SPS_RLSA_DSPM_HOH_TIMEREXPIRED_ SOFTHOTHOCOMPLETION Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThoco mpletion Failure Cause In soft handoffs. transmission bit error Possible Solution Further Trouble shootin g 30 1. 2. It is acceptable if this failure occurs occasionally. Check handoff target BTS board and calls under this BTS Check the versions and running of ABPM. Check the transmission power of handoff target cell 3.ZXC10 BSSB (V8. The setting of Thocompletion timer on DSMP board is correctly or not（default value is 5s） 2. Handoff completes message (HCM) is not received from MS after Thocompletion（default value is 5s） expires Most likely cause: Failure Analysis 1.Other causes:e.If frame number checking is enabled. BTS clock and BSC clock are different 3. carrier is faulty 4. Abis\A3A7 interface link is faulty Failure Analysis 2. Check the setting of Thoreqtimer on DSMP board （default value is 5s） Possible Solution 2.Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_HOH_Tim erExpired_Thoreq TABLE 54 ERR_SPS_RLSA_DSPM_HOH_TIMEREXPIRED_THOREQ Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq Failure Cause handoff request response expires Most likely cause: 1. Check the handoff target BTS board. Inter BSC handoff: Check the A3A7 interface boards (HGM) of the two BSC and physical links. and if CE is blocked) 4. Check Abis\A3A7 interface link 3. Channel board is faulty 5. Further Trouble shootin g Check the version and running of CCM board Confidential and Proprietary Information of ZTE CORPORATION 31 . Handoff target BTS board runs abnormally 3. the A3A7 interface boards (HGM) of the two BSC run abnormally 1. carrier state and channel board (if chip is normal. Inter BSC handoff. ABPM correspond to BTS run abnormally 2. the setting of Tphysicaltimer on DSMP board has a problem 1.The RCM. Confidential and Proprietary Information of ZTE CORPORATION . Make sure if there is abnormal reset or switchover.1. target carrier signal is too weak Possible Solution Check target carrier signal strength Further Trouble shootin g Check the versions and running of ABPM. It is acceptable if this failure occurs occasionally. DTB and DSM ERR_SPS_RLSA_DSPM_HOH_Oth erReason_AbisdHandShakeFailure TABLE 56 ERR_SPS_RLSA_DSPM_HOH_OTHERREASON_ ABISDHANDS HAKEF AILURE Failure Name ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandSh akeFailure Failure Cause During a call.0.radio condition is poor. A call release is initiated Most likely cause: Failure Analysis Possible Solution 32 1. Check the RCM of the corresponding BTS when the problem occurs. Poor radio condition causes air-interface message missing.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_HOH_Res NotSatisfied_HOHOnUmrCFSearch Report TABLE 55 ERR_SPS_RLSA_DSPM_HOH_RESNOTSATISFIED_ HOHONUMRCFSEARCHREPORT Failure Name ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUm rCFSearchReport Failure Cause In semi-soft handoffs. 2. the handoff at target side fails. The setting of Tphysicaltimer on DSMP board is correct or not（default value is 2 minutes） 2.ZXC10 BSSB (V8. Most likely cause: Failure Analysis 1. If ABPM runs normally or not. handshake between DSPM and RCM fails. Tfschbstreqtimer expires and the BurstResponsemessage from BTS is not received. after BSC sending the BurstRequestmessage. It is acceptable if this problem occurs occasionally. ABPM.Chapter 2 DSPM Related Failures Further Trouble shootin g Check the versions and running status of CCM and ABPM ERR_SPS_RLSA_DSPM_SCHH_Ti merExpired_Tfschbstreq TABLE 57 ERR_SPS_RLSA_DSPM_SCHH_TIMEREXPIRED_TFSCHBSTREQ Failure Name Failure Cause Failure Analysis Possible Solution Further Trouble shootin g ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq In FSCH establishment. Most likely cause: Message is missing at Abis interface. DTB and DSM Confidential and Proprietary Information of ZTE CORPORATION 33 . Check Tfschbstreqtimer setting（500ms） 2. 1. Make sure if the message is missing or not Check the versions and running status of CCM. A8 link establishing fails. when the cause value PDSN brings to DSPM is 0x80. Most likely cause: Failure Analysis Possible Solution 1.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_CLH_Oth erReason_PDSNDenied_Reason_U nspecified TABLE 58 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_PDSNDENIED_ REASON_UNSPECIFIED Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_ Reason_Unspecified Failure Cause In data service call establishing stage.0. A10link establishing fails 2. the failure cause reported by DSPM.ZXC10 BSSB (V8. unplug the standby board Further Trouble shootin g Add DSMP board Confidential and Proprietary Information of ZTE CORPORATION . Check the corresponding PCF when the problem occurs.1. check A10link to see if it is successfully established ERR_SPS_RLSA_DSPM_CLH_Oth erReason_OVERLOAD TABLE 59 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_OVERLO AD 34 Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD Failure Cause DSMP board CPU overloads Failure Analysis DSMP board CPU overloads Possible Solution If the problem is serious. Make sure if there is abnormal reset or switchover. Check the corresponding PCF when the problem occurs. If SDU runs normally or not.Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_CLH_Oth erReason_Ta8setup TABLE 60 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_TA8SETUP Failure Name Failure Cause ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup In data service call establishing stage.If the setting of Ta8setup timer （default value is 3s） on DSMP board is correct or not Possible Solution 2.In OMC. there is a handshake between DSPM. SDU and BSSAP. DSPM does not receive the reply message from SDM when it sends two handshake messages to SDM in 5 minutes. If the setting of Trecv timer (default value is 5 minutes) on DSMP board is correct or not 2. Make sure if there is abnormal reset or switchover.A8 link establishing expires: DSPM sends the A9SetupA8message to PCF. DSPM does not receive the reply message from BSSAP when it sends two handshake messages to SDM in 5 minutes. Most likely cause: Failure Analysis Possible Solution 1. Confidential and Proprietary Information of ZTE CORPORATION 35 . When there is no reply message. Check the corresponding CMP when the problem occurs. the Trecv is timeout due to which the SPS releases the call. 1. no reply message is received in Ta8setup（3s） Most likely cause: Failure Analysis 1.Physical link breaks 3. Make sure if there is abnormal reset or switchover.PCF IP address configuration has problem 2.corresponding PCF is faulty 1. Check the PCF IP address configuration in OMC and the physical link 3. ERR_SPS_RLSA_DSPM_CLH_Oth erReason_Tshakehandrecv TABLE 61 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_ TSHAKEHANDRECV Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_Tshakehandre cv Failure Cause During a call. 2. 1.g.0. base station sends out the handoff indication (HDM). If frame number checking is enabled. Other causes: e.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_HOH_Tim erExpired_SemiSoftHOThocompletio n TABLE 62 ERR_SPS_RLSA_DSPM_HOH_TIMEREXPIRED_ SEMISOFTHOTHOCOMPLETION Failure Name ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOT hocompletion Failure Cause In semi-handoffs. the handoff will expire. 2. if the MS handoff completes message (HCM) is not received when Thocompletion（default value is 5s） expires.Check the handoff target cell transmission power 3. bit error Possible Solution Further Trouble shootin g 36 1. BTS and BSC have different clocks 3. It is acceptable if this failure occurs occasionally. Check the versions and running of ABPM. Poor radio condition causes air-interface handshake message missing.ZXC10 BSSB (V8. Most likely cause: Failure Analysis 1.If the setting of Thocompletion timer ob DSMP board is correct or not（default value 5s） 2. Check the handoff target BTS board to see if the call originations under this BTS are normal or not. DTB and DSM Confidential and Proprietary Information of ZTE CORPORATION . resource at target BTS\BSC side has problem 2. 3.Check Abis\A3A7 interface link Possible Solution Further Trouble shootin g 2.Inter BSC handoff:Check the A3A7 interface board (HGM) of the two BSC and the physical link Check the version and running of CCM board Confidential and Proprietary Information of ZTE CORPORATION 37 .Flow has problem 1.Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_HOH_Res NotSatisfied_HOHOnA7rHOReqAck TABLE 63 ERR_SPS_RLSA_DSPM_HOH_RESNOTSATISFIED_ HOHON A7RHOREQ ACK Failure Name ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7r HOReqAck Failure Cause Handoff request is rejected by target side Failure Analysis Most likely cause: 1. carrier state and channel board (if the chip is normal and if CE is blocked). Check the handoff target BTS board. A8 link establishing fails. check A10 link to see if it is successfully established ERR_SPS_RLSA_DSPM_CLH_Oth erReason_PCFDenied_PDSN_Reso urce_Unavailable TABLE 65 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_PCFDENIED_ PDSN_RESOURCE_UNAV AILABLE Failure Name ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_P DSN_Resource_Unavailable Failure Cause In data service call establishing stage. A8 link establishing fails. Confidential and Proprietary Information of ZTE CORPORATION . the failure cause reported by DSPM.ZXC10 BSSB (V8.PDSN is faulty 1. Check A10 link to see if is successful established Possible Solution 38 2. Make sure if there is abnormal reset or switchover. Most likely cause: Failure Analysis Possible Solution 1. Check the corresponding PCF when the problem occurs. The cause value PCF brings for DSPM.0. A10 link establishing fails 2. Failure Analysis Most likely cause: 1. PDSN resource is unavailable. when the cause value PDSN brings to DSPM is 0x81.A10 link establishing fails 2.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_DSPM_CLH_Oth erReason_PDSNDenied_Reason_A dministratively_Pohibited TABLE 64 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_PDSNDENIED_ REASON_ ADMINISTRATIVELY_POHIBITED Failure Name Failure Cause ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_Administratively_Pohibited In data service call establishing stage. Make sure if there is abnormal reset or switchover. Check the corresponding PDSN when the problem occurs.1. Chapter 2 DSPM Related Failures ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHReleaseRSCHbyL egFail_ReleaseRschExistSDMLegFa ilure TABLE 66 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHRELEASERSCHBYLEGFAIL_RELEASERSCHEXISTSDMLEGFAILURE Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleas eRSCHbyLegFail_ReleaseRschExistSDMLegFailure Failure Cause When DSPM receives the LegLinkFailure reported by SDM. the failure is reported by DSPM. Failure Analysis Most likely cause: Possible Solution Check Abis interface SDM has no reverse frames ERR_SPS_RLSA_DSPM_SCHH_Ot herReason_SCHHOnUmrSCHRequ estMsg_FCHNotExisted TABLE 67 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_ SCHHONUMRSCHREQUESTMSG_FCHNOTEXISTED Failure Name ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUm rSCHRequestMsg_FCHNotExisted Failure Cause Data service fundamental channel receives a message from SCH for setup. Failure Analysis Most likely cause: Possible Solution This failure is acceptable call origination flow does not complete Confidential and Proprietary Information of ZTE CORPORATION 39 . if RSCH is not partly soft handoff and the released cell and SDM notify different cells. 9) Call Failure Reason and Call Drop Explanation (1x) This page is intentionally blank. 40 Confidential and Proprietary Information of ZTE CORPORATION .0.ZXC10 BSSB (V8.1. 1.Chapter 3 SDM Related Failures This chapter introduces and describes call failures related to SDM and also discusses about possible troubleshooting methods. BSC has not received Preamble sent by the mobile before timeout. Check if channel board has blocked CE. wrong CHM version. For example. Every problem in the system may cause failure in mobile capturing. Failure Cause There are many reasons for this abnormality. inconsistent RC and PN offset error etc. parameters for the mobile are inconsistent with that of base station side. long code error. but Idle frame can be received. The failure cause. Check CHM version Possible Solution 2. SDM_Activate_Fail_AcquirePreambl eFail_Normal TABLE 68 SDM_ACTIV ATE_FAIL_ ACQUIREPREAMBLEFAIL_NORM AL Failure Name SDM_Activate_Fail_AcquirePreambleFail_Normal Mobile establishing fails. Check failure reason submitted to abnormality probe 3. Confidential and Proprietary Information of ZTE CORPORATION 41 . analysis and the possible solutions are described in tables against each error as shown below. Check CE if there is residual forward CE in RB_FWDCE list 4. Channel list is wrongly added on either BTS or BSC side.Link block for Abis media flow 2. Possible Solution 2. BSC has not received reverse traffic frame sent by BTS before timer is timeout.0. Those with high probability are: 1.9) Call Failure Reason and Call Drop Explanation (1x) SDM_Activate_Fail_AcquirePreambl eFail_NoRevFrm TABLE 69 SDM_ACTIV ATE_FAIL_ ACQUIREPREAMBLEFAIL_NOREVFRM Failure Name SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm Mobile connection establishment fails. Failure Cause There are many reasons for BSC’s not receiving traffic frame from BTS.1. Check if Abis link is disconnected.Check if adding channel list (BSC and BTS side) in signaling tracing is successful 3. 1. Check if there are CE suspended in CHM 42 Confidential and Proprietary Information of ZTE CORPORATION . etc.ZXC10 BSSB (V8. the mobile does not receive confirmation message on BS side. Abnormal Level Three process. check if there is EV_S_AbafStartVocoderCoding message in signaling. the reason might be inconsistent parameters on MS and BS side. if there is no. so that it does not return confirmation message to BS. The abnormality may also be caused by inconsistent parameters between the mobile and BS side (e. 1. Check the versions of MS and BS side. If handshake is normal. Detailed reasons vary: for example. If none of these messages exists. DSPM has not sent message. SDM has not received EV_S_AbafStartVocoderCoding message sent by DSPM before timer is timeout. which can be judged from signaling tracing.g. it has not sent EV_S_AbafStartVocoderCoding message to SDM. The two possible reasons for this abnormality are: Failure Cause 1. but due to some reason it does not return confirmation to BS. RC inconsistent) causing the mobile not to detect confirmation message on base station side. 3. 2.Check if there are handshake messages EV_S_UmfBSOrder and EV_S_UmrMSOrder of traffic channel Possible Solution 2. Confidential and Proprietary Information of ZTE CORPORATION 43 . Or the mobile has received confirmation message on BS side.Chapter 3 SDM Related Failures SDM_Find_Fail_WaitConfigVTCTim eout TABLE 70 SDM_FIND_FAIL_W AITCONFIGVTCTIMEOUT Failure Name SDM_Find_Fail_WaitConfigVTCTimeout After SDM activation. Service negotiation fails between Level Three and mobile and Level Three does not receive confirmation message of the e mobile. After successful negotiation with the mobile. SDM_Link_Fail_RevTooManyBadFr m TABLE 72 SDM_LINK_FAIL_REVTOOM ANYBADFRM Failure Name SDM_Link_Fail_RevTooManyBadFrm Link failure.0. 1. Possible Solution Check if Abis link is disconnected. Thus it needs to be checked why the mobile releases itself spontaneously. due to certain reason the mobile releases itself spontaneously while BS does not receive release message of the mobile. Failure Cause Reasons for this abnormality vary. version) 2. While submitting the abnormality. this is failure within normal range. the abnormality will be submitted. Failure Cause Possible Solution 44 Reasons vary. while the reverse radio link is very bad.g. However. For example. it might be normal abnormal reasons. SDM can not receive traffic frame sent from BTS during a period (default time is 18s). This is normal release. If parameters are consistent. so that after a period abnormality will be submitted. which is subjected to actual situation. e.9) Call Failure Reason and Call Drop Explanation (1x) SDM_Link_Fail_RevNoFrm TABLE 71 SDM_LINK_FAIL_REVNOFRM Failure Name SDM_Link_Fail_RevNoFrm Link failure. Check MS and BS side parameters (PN offset.1. in calling process. for example. it is not necessarily normal. Confidential and Proprietary Information of ZTE CORPORATION . then MS releases itself spontaneously. Abis link problem and CHM dispatching problem. there probably are many underlying system problems.ZXC10 BSSB (V8. Besides. which is subject to different situation. inconsistent parameters between the mobile and BS side and PN offset error probably cause the failure. calling will be released. SDM receives from BTS side almost all error frame during a period (default time is 18s). Possible Solution This abnormality is usually caused by handshaking timeout between Level Three and mobile. 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. While submitting this abnormality. timer is timeout and the message is not received. then analyze MGW side. net cable on Ap port has problem.Chapter 3 SDM Related Failures SDM_Link_Fail_FwdA2pNoFrm TABLE 73 SDM_LINK_FAIL_FWD A2PNOFRM Failure Name SDM_Link_Fail_FwdA2pNoFrm SDM can not receive traffic frame sent from MGW during a period (default time is 18s) Failure Cause Possible Solution Reasons for this abnormality vary. SDM_Find_Fail_WaitConfigRLPTim eout TABLE 74 SDM_FIND_FAIL_W AITCONFIGRLPTIMEOUT Failure Name SDM_Find_Fail_WaitConfigRLPTimeout Failure Cause While waiting for EV_S_AbafPCFInfoL3 message sent by Level Three after successful digital service SDM activation. calling will be released. which is subject to actual situation. Confidential and Proprietary Information of ZTE CORPORATION 45 . MGW process problem (not sending frame). for example. ZXC10 BSSB (V8. i. Problem occur during MGW frame sending. the possibility is relatively small.9) Call Failure Reason and Call Drop Explanation (1x) SDM_Link_Fail_RSCHLegLinkFail TABLE 75 SDM_LINK_FAIL_RSCHLEGLINKFAIL Failure Name SDM_Link_Fail_RSCHLegLinkFail Failure Cause Reverse supplementary channel leg does not receive frame from reverse channel board.0. Possible Solution 1. Possible reasons are: Failure Cause 1. Check if Ap port link is normal 2. please contact engineers at the office. it is normal situation.e. 2 Problem occurs in A p port link during call. 3. SDM process error Possible Solution 46 1. 2. Confidential and Proprietary Information of ZTE CORPORATION . not send frame to SDM. Check signaling and find out if CHM has released the leg. 3.1. Check if reverse link has problem. Check CHM statistics for frame receiving and sending SDM_Link_Fail_FwdA2pTooManyEr rEncodeFrm TABLE 76 SDM_LINK_FAIL_FWD A2PTOOM ANYERRENCODEFRM Failure Name SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm Inadequate good frame is received from MGW within 18s. If it is not disconnected link. 2. please contact engineers at the office. adding board is needed. or problem occurs in the bottom level. the possible reasons are: the utilization of CPU of SDU board is too high so that message cannot be sent out. possible reason is that message lost occurs among boards. SDM_OprVocoder_Fail_WaitStartVo coderCodingAckTimeOut TABLE 78 SDM_OPRVOCODER_FAIL_W AITSTARTVOCODERCODINGACK TIMEOUT Failure Name SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTime Out Failure Cause SDM cannot receive ACK message of VTC after sending startVocoderCoding message to VTC. Check SDU board utilization ratio. If SDU board is normal but the failure remains. either startVocoderCoding message or ACK message is lost.Chapter 3 SDM Related Failures SDM_Activate_Fail_InitVocoderFail TABLE 77 SDM_ACTIV ATE_FAIL_INITVOCODERFAIL Failure Name Failure Cause Possible Solution SDM_Activate_Fail_InitVocoderFail Failure in sending initialized vocoder message. 1. If it is too high. Confidential and Proprietary Information of ZTE CORPORATION 47 . Possible Solution Please contact engineers at the office. no leg is found for SDM to remove. if not then it lies in Level Three. Confidential and Proprietary Information of ZTE CORPORATION . then the problem lies in SDM. but the parameter inside is incorrect.ZXC10 BSSB (V8.0. Possible reason is message maintained by SDM is different from that of Level Three. Possible Solution Check signaling to find out whether Level Three has noticed SDM to add this leg. Possible Solution Check SDM abnormality probe message to find which parameter is wrong.1. SDM_Activate_Fail_MsgParaFail TABLE 80 SDM_ACTIV ATE_FAIL_MSGP ARAF AIL 48 Failure Name SDM_Activate_Fail_MsgParaFail Failure Cause SDM receives message sent by Level THREE.9) Call Failure Reason and Call Drop Explanation (1x) SDM_Find_Fail_NoFCHLeg TABLE 79 SDM_FIND_FAIL_NOFCHLEG Failure Name SDM_Find_Fail_NoFCHLeg Failure Cause When SDM receives AbafSDMDropLeg message sent by Level Three. if it has. In signaling tracing check AbafActivateSDM message to find out where the fault is so as to confirm whether Level Three is wrongly written or it is the SDM process problem. i. the CE with status position as 0 (INDEX is 64-95) and check if channel board has blocked CE. Failure Analysis The reason for the failure is inadequate forward and reverse CE resource. Confidential and Proprietary Information of ZTE CORPORATION 49 . analysis and the possible solutions are described in tables against each error as shown below.Chapter 4 DBS Related Failures This chapter introduces and describes call failures related to DBS and also discusses about possible troubleshooting methods. check if there is residual reverse CE in RB_REVCE list. the CE with status position as 0 (INDEX is 0-31). Possible Solution Check if there is residual forward CE in RB_FWDCE list. Check failure reason submitted in abnormality probe.e. The failure cause. DBS_STASTIC_FWDFCHCE_REVC E_LACK TABLE 81 DBS_STASTIC_FWDFCHCE_REVCE_LACK Failure Name DBS_STASTIC_FWDFCHCE_REVCE_LACK Failure Cause Failure due to inadequate forward or reverse CE while basic channel is being set up during MS calling or MS’s being called.e. i. 3. DBS_STASTIC_WALSHCODE_LAC K TABLE 83 DBS_STASTIC_W ALSHCODE_LACK Failure Name Failure Cause Resource distribution failure due to WALSHCODE distribution failure while basic channel is being set up during MS calling or MS’s being called. Check if there is free resource in WALSHCODE using probe. Check failure reasons submitted in abnormality probe. Check if there is residual forward CE in RB_FWDCE list. Check if channel board has blocked CE. 2. Possible Solution 1.ZXC10 BSSB (V8.1. Failure Analysis The reason for this failure is there is no WALSHCODE available under the carrier.0. Check out failure reasons submitted in abnormality probe. Confidential and Proprietary Information of ZTE CORPORATION . Possible Solution 50 DBS_STASTIC_WALSHCODE_LACK 1. 2. Failure Analysis The reason for this failure is inadequate forward CE resource.9) Call Failure Reason and Call Drop Explanation (1x) DBS_STASTIC_FWDFCHCE_LACK TABLE 82 DBS_STASTIC_FWDFCHCE_L ACK Failure Name DBS_STASTIC_FWDFCHCE_LACK Failure Cause Failure due to inadequate reverse CE on 5K channel board while basic channel is being set up during MS calling or MSs being called. Possible Solution 1. 2. DBS_STASTIC_NO_RESOURCE_L ACK TABLE 85 DBS_STASTIC_NO_RESOURCE_LACK Failure Name DBS_STASTIC_NO_RESOURCE_LACK Failure Cause Reason for the failure that is not because of inadequate resource Failure Analysis This error reason code is default error code distributed by database resource. Check failure reasons submitted in abnormality probe.Chapter 4 DBS Related Failures DBS_STASTIC_UID_LACK TABLE 84 DBS_STASTIC_UID_LACK Failure Name DBS_STASTIC_UID_LACK Failure Cause Resource distribution failure due to UID distribution failure while basic channel is being set up by IP platform during MS calling or MS’s is being called. Failure Analysis There is no available broadband under the sector or failure occurs in bandwidth distribution. usually data error or parameter error occurs in some list inside. Once this code exists. Confidential and Proprietary Information of ZTE CORPORATION 51 . Possible Solution Check failure reasons submitted in abnormality probe. Check whether LeftBandWidth field in R_UID list is bigger than 9 using probe. BTS resource distribution return error will not be influenced. 2.9) Call Failure Reason and Call Drop Explanation (1x) FCH_NUMBER_TWO TABLE 86 FCH_NUMBER_TWO Failure Name FCH_NUMBER_TWO Failure Cause While supplementary channel is being set up. ARRIVE_TIME_ERROR T A B L E 8 7 AR R I V E _ T I M E _ E R R O R Failure Name Failure Cause Failure Analysis 52 ARRIVE_TIME_ERROR Channel board is too late to be configured in the period before supplementary channel starts during supplementary channel confirmation. Further Trouble shootin g Optimize link delay on Abis port Confidential and Proprietary Information of ZTE CORPORATION . The main reasons for this failure are: 1. Link delay on Abis port is too long. Clocks of BTS and BSC are different.1.ZXC10 BSSB (V8.0. Possible Solution Solve clock problem of BTS and BSC. Failure Analysis Main reason for this failure is: Possible Solution Further Trouble shootin g subscriber is under semi soft handoff status As it is stipulated. Ask DSPM and RCM to solve the problem of originating supplementary channel setup in semi soft handoff status. subscriber has two basic data channels. setting up supplementary channel is not permitted when subscriber is under semi soft handoff status. Possible Solution It usually appears during system reset. IP platform SCS does not send system time to DBS. Possible Solution It usually appears during system reset.Chapter 4 DBS Related Failures NO_SYSTEM_TIME TABLE 88 NO_SYSTEM_TIME Failure Name NO_SYSTEM_TIME Failure Cause CCM DBS has no system time during reserving supplementary channel resource. INPUT_PARA_ERROR TABLE 89 INPUT_P AR A_ ERROR Failure Name INPUT_PARA_ERROR Failure Cause Input parameter error The main reasons for this failure are: Failure Analysis HIRS platform probably does not send system time to CCM because of instantaneous CHM failure. Confidential and Proprietary Information of ZTE CORPORATION 53 . IP platform SCS does not send system time to DBS. The main reasons for this failure are: Failure Analysis HIRS platform probably does not send system time to CCM because of instantaneous CHM failure. Changing flow is suggested. which is caused by flow. cell of DBS given by RCM has error. Lost of release message may cause this abnormality. the required power surpasses the maximum transmission power of supplementary channel set by OMC. Confidential and Proprietary Information of ZTE CORPORATION . 2. Subscriber radio condition is relatively poor. Possible Solution Increase capacity SOFTADD_CELL_ERROR TABLE 91 SOFT ADD_CELL_ERROR Failure Name Failure Cause SOFTADD_CELL_ERROR Continuous transmission or softer add for reverse supplementary channel.1. The main reasons for this failure are: Failure Analysis Possible Solution 54 1.9) Call Failure Reason and Call Drop Explanation (1x) POWER_NOT_ENOUGH TABLE 90 POWER_NOT_ENOUGH Failure Name POWER_NOT_ENOUGH Failure Cause Inadequate power The main reasons for this failure are: Carrier power surpasses threshold for supplementary channel setup. Failure Analysis Residual power is not able to set up a forward supplementary channel with a rate of over 2X. setup application for supplementary channel reaches BTS before BTS basic channel handoff completes.ZXC10 BSSB (V8. but the possibility is comparatively small. the possibility is comparatively large. as BSC handoff is completed early. When basic channel undergoes handoff.0. Supplementary channel module of DSPM makes SCH setup application after FCH module handoff is finished. maybe FCH has comparatively more data on the same frame offset. The main reasons for this failure are: Failure Analysis Possible Solution Inadequate frame offset. and reverse supplementary channels have been set up. Failure Analysis The main reason for this failure is inadequate CE Possible Solution Increase capacity FO_NOT_ENOUGH TABLE 93 FO_NOT_ENOUGH Failure Name FO_NOT_ENOUGH Failure Cause No available frame offset when setting up reverse complementary channel. because frame offset of reverse supplementary channel is the same with FCH.Chapter 4 DBS Related Failures NO_AVAILABLE_REV_CE T A B L E 9 2 N O _ AV A I L A B L E _ R E V _ C E Failure Name NO_AVAILABLE_REV_CE Failure Cause No available reverse CE when setting up reverse supplementary channel. Increase capacity Confidential and Proprietary Information of ZTE CORPORATION 55 . Failure Analysis Possible Solution 56 The main reasons for this failure are: Too many forward supplementary channels are set up so that Walsh code is insufficient Increase capacity Confidential and Proprietary Information of ZTE CORPORATION .1.9) Call Failure Reason and Call Drop Explanation (1x) CE_NOT_ENOUGH TABLE 94 CE_NOT_ENOUGH Failure Name CE_NOT_ENOUGH Failure Cause No forward supplementary channel CE available when forward supplementary channel is being set up. Increase capacity WALSHCODE_NOT_ENOUGH TABLE 95 WALSHCODE_NOT_ENOUGH Failure Name WALSHCODE_NOT_ENOUGH Failure Cause No Walsh code available when forward supplementary channel is being set up. Failure Analysis Possible Solution The main reasons for this failure are: Too many forward supplementary channels are set up so that forward supplementary channels CE are insufficient.0.ZXC10 BSSB (V8. UIDWIDTH_NOT_ENOUGH TABLE 97 UIDWIDTH_NOT_ENOUGH Failure Name UIDWIDTH_NOT_ENOUGH Failure Cause UID bandwidth is insufficient during resource distribution of supplementary channel Failure Analysis The main reason for this failure is: Possible Solution Increase capacity Insufficient Abis bandwidth Confidential and Proprietary Information of ZTE CORPORATION 57 .Chapter 4 DBS Related Failures BEFORE_CPS TABLE 96 BEFORE_CPS Failure Name Failure Cause BEFORE_CPS Application is done too early during process of dispatch continuous transmission of forward supplementary channel Failure Analysis The main reasons for this failure are: Possible Solution Check GCM board to confirm there is no alarm Different system clocks of BTS and BSC. ALLOCATE_UID_ERROR TABLE 99 ALLOC ATE_UID_ERROR 58 Failure Name ALLOCATE_UID_ERROR Failure Cause UID distribution fails during resource distribution of supplementary channel. there is no corresponding record in RS list. This is normal situation that does not need settlement.ZXC10 BSSB (V8. subscriber A of supplementary channel needs to reserve another subscriber B of supplementary channel because of scheduling. however. Failure Analysis The main reason for this failure is : Possible Solution Stabilize UID status Instantaneous UID failure Confidential and Proprietary Information of ZTE CORPORATION . afterwards subscriber A data FCH is released and actually FCH no longer exists when supplementary channel is set up.9) Call Failure Reason and Call Drop Explanation (1x) RS_NOT_EXIST TABLE 98 RS_NOT_EXIST Failure Name RS_NOT_EXIST Failure Cause Records to which RS list corresponds is unavailable during resource distribution of supplementary channel Failure Analysis The main reason for this failure is scheduling algorithm of supplementary channel. Therefore.0. Possible Solution Supplementary channel that is reserved at present cannot be set up because data is released by subscriber.1. Level Three should not submit it. if this do occurs. Lower the subscriber quantity of every carrier. check if frequency for soft handoff is configured under PN that is to be added. For soft handoff. The reason for this failure is: The carrier has too many subscribers. because if there is no suitable carrier. therefore for other pilots there probably is no such carrier. Failure Analysis Possible Solution 1. For soft handoff. the power of the selected carrier is overloaded. this reason value means there is no suitable frequency under the pilot. For semi-soft and hard handoff. 2. target pilot aggregate can not be added. HO_STAT_CARRIER_PWR_OVER LOAD TABLE 101 HO_ST AT_C ARRIER_PWR_OVERLO AD Failure Name HO_STAT_CARRIER_PWR_OVERLOAD Failure Cause Power of the selected carrier is overloaded Failure Analysis Possible Solution During handoff judge. as there is no suited frequency under the pilot. the carrier with the smallest transmission power in the first pilot is selected as the fundamental carrier. this ought not to occur. Confidential and Proprietary Information of ZTE CORPORATION 59 . and it is normal to submit the reason.Chapter 4 DBS Related Failures HO_STAT_PILOT_NO_SAME_FRE Q TABLE 100 HO_ST AT_PILOT_NO_S AM E_FREQ Failure Name HO_STAT_PILOT_NO_SAME_FREQ Failure Cause During handoff judge. then it is failure. Confidential and Proprietary Information of ZTE CORPORATION . Possible Solution Identify any probable broken links between two Handle differently according to detail situation of “status”. Decrease subscriber quantity for every carrier. HO_STAT_CARRIER_NO_CE TABLE 103 HO_ST AT_C ARRIER_NO_CE 60 Failure Name HO_STAT_CARRIER_NO_CE Failure Cause There is no CE in the selected carrier. Status field is “status” in rbcarrier list on dsmp/cmp. 2. meaning of which is: Failure Analysis Bit1=0/1 Manual unblocking/ manual blocking Bit2=0/1 Failure unblocking/ failure blocking Bit3=0/1 RFE_DUP low power alarm unblocking carrier/ RFE_DUP low power alarm blocking carrier Bit4=0/1 two BDSs are normal BDSs. Failure Analysis CE resource to which the carrier corresponds has been used up or blocked Possible Solution 1.1.9) Call Failure Reason and Call Drop Explanation (1x) HO_STAT_CARRIER_STATE_ERR OR TABLE 102 HO_ST AT_C ARRIER_STATE_ERROR Failure Name HO_STAT_CARRIER_STATE_ERROR Failure Cause Abnormal status of selected carrier During handoff judge.0. Check if there is CE blocked. power status of the selected carrier is abnormal.ZXC10 BSSB (V8. Confidential and Proprietary Information of ZTE CORPORATION 61 . Failure Analysis PN is not configured as neighboring cell with active set. HO_STAT_PILOT_IS_NOT_NEIGH BOR TABLE 105 HO_ST AT_PILOT_IS_NOT_NEIGHBOR Failure Name HO_STAT_PILOT_IS_NOT_NEIGHBOR Failure Cause PN is not configured as neighboring cell.Chapter 4 DBS Related Failures HO_STAT_CARRIER_NO_5KCE TABLE 104 HO_ST AT_C ARRIER_NO_5KCE Failure Name HO_STAT_CARRIER_NO_5KCE Failure Cause No 5k channel board CE for selected carrier. Decrease subscriber quantity for every carrier. 2. Failure Analysis Possible Solution 5k channel board CE resource to which the carrier corresponds has been used up or blocked. Check if there is 5k CE blocked. but there is 15 channel board CE. with no record in link cell. 1. Possible Solution Check if PN has been configured in neighboring cell of the cell. Failure Analysis HGM does not support soft handoff within BSC with data service.ZXC10 BSSB (V8.1.0. IP BSC and HIRS BSC support soft handoff within BSC with data service only when IBBE board is used.9) Call Failure Reason and Call Drop Explanation (1x) HO_STAT_DESTBSC_IS_HIRS_DA TASOFTHO TABLE 106 HO_ST AT_DESTBSC_IS_HIRS_DAT AS OFTHO Failure Name HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO Failure Cause HGM does not support soft handoff within BSC with data service. Failure Analysis Remove the other BSC PN while constructing hard handoff inside BSC Possible Solution Normal flow Confidential and Proprietary Information of ZTE CORPORATION . HO_STAT_PILOT_NOT_LOCALBS S TABLE 107 HO_ST AT_PILOT_NOT_LOC ALBSS 62 Failure Name HO_STAT_PILOT_NOT_LOCALBSS Failure Cause PN is not of the BSC. Possible Solution IP BSC and HIRS BSC don’t support soft handoff within BSC with data service. Configuration on MSS side. Check the correctness of ground circuit (CIC) configuration of port A. 5. Check whether CIC resource quantity meets needs for traffic capacity. Check whether CIC resource is manually blocked in dynamic management. 3. Check whether DT board to which CIC corresponds operates normally and whether it is of correct version. 2. Possible Solution c) Check whether the DT board to which CIC corresponds is correctly attributed to RMP module. CIC resource status is abnormal or insufficient CIC resource 1. 4. Check whether E1 physical connection to which CIC corresponds is correct. Failure Analysis No CIC resource available: CIC resource configuration error. a) Check the correctness of PCM configuration at port A. b) Check whether trunk configuration is correct and notice it should be the same as that of time slot on MSS side. and notice it should be the same as PCM NO.Chapter 4 DBS Related Failures HO_STAT_PILOT_IS_OTHER_UNL NKBSS TABLE 108 HO_ST AT_PILOT_IS_OTHER_UNLNKBSS Failure Name HO_STAT_PILOT_IS_OTHER_UNLNKBSS Failure Cause HO_STAT_PILOT_IS_OTHER_UNLNKBSS Failure Analysis If pilot is neither in the BSC or in the other interconnected BSC Possible Solution Check neighboring configuration of the cell. BSC_NO_CIC TABLE 109 BSC_NO_CIC Failure Name BSC_NO_CIC Failure Cause System has no CIC (ground circuit) resource available. Confidential and Proprietary Information of ZTE CORPORATION 63 . Failure Analysis No VE resource available: VTC configuration error.ZXC10 BSSB (V8. Possible Solution 3. Check whether VTC board operates normally and whether CPU/DSP version is correct. Check if 1XSDU board is correctly configured. 1. 3. Check if the status of daughter card of SDU board and of INDEX is normal in dynamic management. Check whether VE resource quantity meets the needs of traffic capacity.1. 2. abnormal VE resource status or insufficient VE resource. Check if VTC board and INDEX status is normal in dynamic management. 5. SE resource status is abnormal or SE resource is insufficient. 4. 64 Confidential and Proprietary Information of ZTE CORPORATION . Failure Analysis No SE resource available: SDU configuration error. Check if SE resource quantity meets the needs of traffic capacity. 4. For the situation that AP interface is embedded in RTP. Check whether SDU board operates normally and whether its version is correct. 1. Possible Solution 2. checks if SDU virtual address configuration is correct.9) Call Failure Reason and Call Drop Explanation (1x) BSC_NO_SE TABLE 110 BSC_NO_SE Failure Name BSC_NO_SE Failure Cause The system does not have available SE resource. Check if the resource frame where CIC is configured correctly with corresponding quantity of VTC boards. BSC_NO_VE TABLE 111 BSC_NO_VE Failure Name BSC_NO_VE Failure Cause The system has no available VE resource.0. Check module list in probe view. Check if MP daughter card where DSPM module is operates normally and whether its version is correct. Failure Analysis IWF resource unavailable: IWF configuration error. Check whether IWFB board operates normally and whether CPU/DSP version is correct. Check if the quantity of DSPM examples meets the needs of traffic capacity. BSC_DSPM_NO_INSTANCE T A B L E 1 1 3 B S C _ D S P M _ N O _ I N S T AN C E Failure Name BSC_DSPM_NO_INSTANCE Failure Cause The system has unavailable DSPM examples Failure Analysis DSPM examples unavailable: DSPM configuration error. 4. Possible Solution 2. especially in the situation of not selecting CIC. abnormal IWF resource status or insufficient IWF resource 1. Check whether IWFB board is correctly configured. DSPM status abnormal or insufficient DSPM examples 1. and whether corresponding quantity of DSPM examples are configured. Check whether the status of IWFB board and INDEX is normal in dynamic management. 4. Check whether IWF resource quantity meets the needs of traffic capacity.Chapter 4 DBS Related Failures BSC_NO_IWF TABLE 112 BSC_NO_IWF Failure Name BSC_NO_IWF Failure Cause The system has unavailable IWF resource. Confidential and Proprietary Information of ZTE CORPORATION 65 . 3. Possible Solution 2. check if IWFB boards are configured in resource frame where CIC is. 3. and check if DSPM is in normal status. Check if DSPM module is correctly configured. Possible Solution 2. 4. abnormal status of RTP port or insufficient RTPPORT resource.1. For external RTP situation. Check whether MP daughter card where RMP module is operates normally and whether its version is correct. check if IPI board and RTP port are correctly configured. Check whether RMP module is correctly configured in the system. 1.ZXC10 BSSB (V8. Check if the status of RTPPORT resource is normal during dynamic management. Check module list in probe view. 1.9) Call Failure Reason and Call Drop Explanation (1x) BSC_NO_RTPPORT TABLE 114 BSC_NO_RTPPORT Failure Name BSC_NO_RTPPORT Failure Cause The system has unavailable RTPPORT resource（This failure reason is submitted only in the situation of external RTP. 66 Confidential and Proprietary Information of ZTE CORPORATION .） Failure Analysis Unavailable RTPPORT resource: configuration error. BSC_NO_VALID_RMP TABLE 115 BSC_NO_V ALID_RMP Failure Name BSC_NO_VALID_RMP Failure Cause The system has unavailable RMP module. Check whether IPI board where RTP port is operates normally and whether its version is correct. 3. Check if RTPPORT resource quantity meets the needs of traffic capacity. Failure Analysis Unavailable RMP module: RMP module configuration error or abnormal RMP status. Possible Solution 2. 3.0. and to check if RMP module status is normal. Confidential and Proprietary Information of ZTE CORPORATION 67 . If CHM and CCM are normal.Chapter 5 RCM Related Failures This chapter introduces and describes call failures related to RCM and also discusses about possible troubleshooting methods. The possible reasons are: 1. big problem. After confirming failure reason. it is possible that resource hung up. analysis and the possible solutions are described in tables against each error as shown below. Walsh is not enough 4. Input parameter mistake of using database Failure Analysis 2. it fails to apply for data base interface allocation resource. ERR_SPS_RLSA_RCM_DBAccFail_ FCHResourceAllocate T A B L E 1 1 6 E R R _ S P S _ R L S A_ R C M _ D B A C C F A I L _ F C H R E S O U R C E A L L O C A T E Failure Name ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate Failure Cause When MS is called or calling. during FCH setting up. Check failure reason in EV_S_AbisdrBTSSeupAck message reported in signal tracing 0x5064: forward channel CE is not enough 0x5065: Reverse CE is not enough Possible Solution 0x5066: forward channel and reverse CE are all not enough 2. check if CHM board is abnormal ( chipset and CE are normal or not) 3. The failure cause. FO is not enough 5. UID is not enough 1. CE resource is not enough or abnormal. 3. ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_RCM_PCALL_Ot herReason_CEC_REMOVEREQ T A B L E 1 1 7 E R R _ S P S _ R L S A_ R C M _ P C A L L _ O T H E R R E A S O N _ C E C _ REMOVEREQ Failure Name ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOV EREQ The failure reason is: during call procedure, CHM board requests to release current call after detecting no frame in forward channel (The default time is 6s). That is CHM does not receive SDU forward frame, then it will release procedure. The possible reasons : Failure Cause 1.IP or MAC value is invalid 2.Key invalid value leads to searching table address mistake 3.Channel table invalid position 4.SDM does not set up leg 5.The related DSP problem in VTC board 1.Check if there is SDM leg set up information in signal Possible Solution 68 2.Check IP and MAC value 3. If this problem occurs frequently, maybe DSP problem. Confidential and Proprietary Information of ZTE CORPORATION Chapter 5 RCM Related Failures ERR_SPS_RLSA_RCM_FCH_Timer Expired_TconnExpired T A B L E 1 1 8 E R R _ S P S _ R L S A_ R C M _ F C H _ T I M E R E X P I R E D _ T C O N N E X P I R E D Failure Name Failure Cause ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired During call setup, when resource is set up, Abis interface timer expires and leads to call release procedure, and call failure happens. This timer is 4S. The radio resource and service address in BTS side will tell BSC side to trigger, if BSC Ack message is not received before timeout, then BTS side will start release procedure. The reason for BTS side not to receive Ack message also maybe due to content mistake in BTS side message, except for link and message block. 1.Check if Abis link is normal Possible Solution 2. Check parameter in AbisdrConnect message carried by BTS side to BSC (mainly compared with AbisdfBTSSetup), mainly important parameter are: cell information in tAbisConnectInfo. ERR_SPS_RLSA_RCM_RSCH_Oth erReason_Release_RSCH T A B L E 1 1 9 E R R _ S P S _ R L S A_ R C M _ R S C H _ O T H E R R E A S O N _ R E L E A S E _ RSCH Failure Name ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSC H Failure Cause Release reverse SCH channel: Reverse SCH channel release notified by database message. Possible Solution Normal condition, no need for solution Confidential and Proprietary Information of ZTE CORPORATION 69 ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_RCM_RSCH_Oth erReason_Release_FSCH T A B L E 1 2 0 E R R _ S P S _ R L S A_ R C M _ R S C H _ O T H E R R E A S O N _ R E L E A S E _ FSCH Failure Name ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSC H Failure Cause Release forward SCH channel: forward SCH channel release notified by database message. Possible Solution Normal condition, no need for solution ERR_SPS_RLSA_RCM_FSCH_Fun CallFail_AddChannelFail T A B L E 1 2 1 E R R _ S P S _ R L S A_ R C M _ F S C H _ F U N C A L L F A I L _ ADDCHANNELFAIL Failure Name Failure Cause ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail During call setup, this failure occurs when IP platform BTS adds channel table. The possible reason is that too many channel tables are added at one time. Usually it happens during data SCH channel setup. If it happens in ordinary voice, the reason maybe channel table hung up. Possible Solution 70 If it happens during data service procedure, it is normal condition. If one call does not add channel table at one time (ordinary voice), that is resource hung up, please contact ZTE local agent. Confidential and Proprietary Information of ZTE CORPORATION the important parameter is the cell information. waiting for BSC side confirm.Confirm message lost 2. waiting for the acknowledgement. After BTS side allocates SCH channel resource. after SCH resource setup. Check if the parameter of AbisdrBurstResponse message carried by BTS side to BSC side is corrected (mainly compared with AbisdfBurstRequest). Confidential and Proprietary Information of ZTE CORPORATION 71 . BSC side confirm message timeout.Check if Abis link is normal Possible Solution 2. BTS side SCH channel resource allocation is finished. 1.Chapter 5 RCM Related Failures ERR_SPS_RLSA_RCM_SCHCOM M_TimerExpired_Tsch T A B L E 1 2 2 E R R _ S P S _ R L S A_ R C M _ S C H C O M M _ T I M E R E X P I R E D _ T S C H Failure Name Failure Cause Possible Solution ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch During data service procedure. following are the possible reasons: 1. Check if voice traffic is too heavy ERR_SPS_RLSA_RCM_SCHCOM M_TimerExpired_Tbstcomb T A B L E 1 2 3 E R R _ S P S _ R L S A_ R C M _ S C H C O M M _ T I M E R E X P I R E D _ T B S T C O M B Failure Name Failure Cause ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcom b During data service. mainly. database configuration timer expires. the parameter in reply message to BSC side is wrong. The reasons are the following. confirm if there is mistake in CE idle queue of database maintenance Confidential and Proprietary Information of ZTE CORPORATION .CE of SCH in CHM is hung up 3.Check OMC database probe. 1.0.Check if CHM has CE hung up 3.Check if the CPU of CHM is in overload status Possible Solution 2. 1.Check if the CPU of CHM is in overload status Possible Solution 72 2.CHM board configuration message lost 2. CHM board configuration fails and forward SCH channel is released. The reasons are the following. when SCH channel is setup and database is in allocation. it is possible that database has mistake in idle CE queue maintenance 1.1.Check OMC database probe.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_RCM_RSCH_Fun CallFail_RevSCHSetupFail T A B L E 1 2 4 E R R _ S P S _ R L S A_ R C M _ R S C H _ F U N C A L L F A I L _ REVSCHSETUPFAIL Failure Name Failure Cause ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupF ail During data service. If there is no resource hung up in CHM.Check if CHM has CE hung up 3. CHM board configuration fails and reverse SCH channel is released.ZXC10 BSSB (V8. when SCH channel is setup and database is in allocation. confirm if there is mistake in CE idle queue of database maintenance ERR_SPS_RLSA_RCM_FSCH_Fun CallFail_FwdSCHSetupFail T A B L E 1 2 5 E R R _ S P S _ R L S A_ R C M _ F S C H _ F U N C A L L F A I L _ FWDSCHSETUPFAIL Failure Name Failure Cause ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupF ail During data service. If there is no resource hung up in CHM.CE of SCH in CHM is hung up 3.CHM board configuration message lost 2. it is possible that database has mistake in idle CE queue maintenance 1. Check OMC database probe. This case is softer handoff add in transmission. It is normal condition. confirm if there is mistake in CE idle queue of database maintenance ERR_SPS_RLSA_RCM_RSCH_Stat eIncorrect_CellNotFoundInRevSCH ResourceExtension T A B L E 1 2 7 E R R _ S P S _ R L S A_ R C M _ R S C H _ S T A T E I N C O R R E C T _ CELLNOTFOUNDINREVSCHRESOURCEEXTENSION Failure Name ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoun dInRevSCHResourceExtension Failure Cause During data service.Check if CHM has CE hung up 3. there is new added cell. no need for solution Confidential and Proprietary Information of ZTE CORPORATION 73 .Check if the CPU of CHM is in overload status Possible Solution 2. after SCH set up and when user transmits data continuously. or connection status is STATUS_RemovedSCH 1.Chapter 5 RCM Related Failures ERR_SPS_RLSA_RCM_RSCH_Fun CallFail_BurstCommit_STATUS_Re movedSCH T A B L E 1 2 6 E R R _ S P S _ R L S A_ R C M _ R S C H _ F U N C A L L F A I L _ B U R S T C O M M I T _ ST ATUS_REMOVEDSCH Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_S TATUS_RemovedSCH Failure Cause The cell number is 0. Possible Solution Normal condition. 0.1. Confidential and Proprietary Information of ZTE CORPORATION . no need for solution ERR_SPS_RLSA_RCM_FCH_Other Reason_MRequestAbisConnect_Sp ecifiedCellIsReleasing T A B L E 1 2 9 E R R _ S P S _ R L S A_ R C M _ F C H _ O T H E R R E A S O N _ MREQUESTABISCONNECT_SPECIFIEDCELLISRELEASING 74 Failure Name ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisC onnect_SpecifiedCellIsReleasing Failure Cause During soft or softer handoff. the handoff fails as the process does not support both release and set up leg at the same time. it is possible to meet this case. Contact the ZTE local agent. Possible Solution If handoff happens frequently. the database initiates reverse SCH channel release.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_RCM_FSCH_Oth erReason_EndOfDuration T A B L E 1 2 8 E R R _ S P S _ R L S A_ R C M _ F S C H _ O T H E R R E A S O N _ ENDOFDURATION Failure Name ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuratio n Failure Cause During data service and continuous transmission. Possible Solution Normal condition.ZXC10 BSSB (V8. it is possible that the internal processing is stopped. if there is no handoff and an ordinary call meets this kind of failure. It is normal condition. handoff has been started when the release has not been finished. when the cell which has set up leg is released and at the same time one leg is going to be added. when there is a timeout waiting for database resource reserved report message. Confidential and Proprietary Information of ZTE CORPORATION 75 . Possible Solution During softer handoff procedure. ERR_SPS_RLSA_RCM_PCALL_Re cvUnexptMsg_atTchStatusInSemiSo ft_AbisdfBurstRequest T A B L E 1 3 1 E R R _ S P S _ R L S A_ R C M _ P C A L L _ R E C V U N E X P T M S G _ ATTCHSTATUSINSEMISOFT_ABISDFBURSTREQUEST Failure Name ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStat usInSemiSoft_AbisdfBurstRequest Failure Cause During data service and softer handoff procedure. Possible Solution Check if voice traffic is too heavy. SCH channel setup message is rejected. please contact ZTE local agent. when the SCH channel setup message is received.Chapter 5 RCM Related Failures ERR_SPS_RLSA_RCM_FSCH_Tim erExpired_TfschNotifyExpired T A B L E 1 3 0 E R R _ S P S _ R L S A_ R C M _ F S C H _ T I M E R E X P I R E D _ TFSCHNOTIFYEXPIRED Failure Name ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyEx pired Failure Cause During data service. This is a normal failure. If this case occurs frequently. to avoid parallel request for many times.1. SCH channel is requested to setup several times Possible Solution It belongs to abnormal probe report.Check OMC database probe. it is possible that database has mistake in idle CE queue maintenance 1.ZXC10 BSSB (V8. confirm if there is mistake in CE idle queue of database maintenance ERR_SPS_RLSA_RCM_RSCH_Fun CallFail_BurstRequest_ConnInSetup T A B L E 1 3 3 E R R _ S P S _ R L S A_ R C M _ R S C H _ F U N C A L L F A I L _ BURSTREQUEST_CONNINSETUP 76 Failure Name ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_C onnInSetup Failure Cause During data service.CHM board configuration message lost 2. the following are the reasons: 1.Check if the CPU of CHM is in overload status Possible Solution 2.Check if CHM has CE hung up 3. CHM board configuration fails and SCH channel is released. Confidential and Proprietary Information of ZTE CORPORATION . when SCH channel is setup and database is in allocation.0.CE of SCH in CHM is hung up 3.9) Call Failure Reason and Call Drop Explanation (1x) ERR_SPS_RLSA_RCM_PCALL_Ti merExpired_Tconfigtch T A B L E 1 3 2 E R R _ S P S _ R L S A_ R C M _ P C A L L _ T I M E R E X P I R E D _ T C O N F I G T C H Failure Name Failure Cause ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch During data service. If there is no resource hung up in CHM. then it is normal condition ( limitation: Hirs CCM 300. Possible Solution When this failure happens.IP CCM 600). RCM has no idle Handler processing. This leads to resource setup failure according to the principle. it is possible that OSS has changed the processing limitation value. The reason is all subprocessing are in busy status.Chapter 5 RCM Related Failures ERR_SPS_RLSA_RCM_FCH_Other Reason_MRequestAbisConnect_Sa meTimeCellInSameGroupInDiffSetu pFlow T A B L E 1 3 4 E R R _ S P S _ R L S A_ R C M _ F C H _ O T H E R R E A S O N _ MREQUESTABISCONNECT_SAMETIMECELLINS AMEGROUPINDIFFSETUPFLOW Failure Name ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisC onnect_SameTimeCellInSameGroupInDiffSetupFlow Failure Cause During the call. Belongs to code limitation ERR_SPS_RLSA_RCM_PMAIN_Fu nCallFail_MainEntry_MAbisdMsgDis patch T A B L E 1 3 5 E R R _ S P S _ R L S A_ R C M _ P M A I N _ F U N C A L L F A I L _ M A I N E N T R Y _ M ABISDMSGDISPATCH Failure Name ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MA bisdMsgDispatch Failure Cause During call setup. Confidential and Proprietary Information of ZTE CORPORATION 77 . several cells which can not support the same leg want to set up FCH. Possible Solution Normal condition.BDM 75. please contact with ZTE local agent. RCM main processing fails to send message to Handler processing. If a few of calls also meet this failure. if the call number is more than processing limitation. 1. 78 Confidential and Proprietary Information of ZTE CORPORATION .ZXC10 BSSB (V8.9) Call Failure Reason and Call Drop Explanation (1x) This page is intentionally blank.0. the resource is not released 6.Allocate some control channels to other board 4. ( at present ALL IP supports 6.CES code is abnormal. HIRS supports 4 chipsets) 5.BTS SDH transmission is not stable 4.If the problem is still not solved. there is CE hung up and this leads to FCH channel establishment failure Following are the reasons. 1. reset CHM Confidential and Proprietary Information of ZTE CORPORATION 79 .Too many sub-cards in CHM board. ERR_CES_RLSA_CEC_CALLHNDL _FCH_SETUP_CE_IN_USED T A B L E 1 3 6 E R R _ C E S _ R L S A_ C E C _ C A L L H N D L _ F C H _ S E T U P _ C E _ IN_USED Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_US ED Failure Cause When FCH channel is in established. block some sub-cards Possible Solution 2.Check SDH 3.If CPU usage ratio is too high.The upper level is abnormal and the release is not started 1.Chapter 6 CES Related Failures This chapter introduces and describes call failures related to CES and also discusses about possible troubleshooting methods. The failure cause.CHM board CPU usage ratio is too high 2. analysis and the possible solutions are described in tables against each error as shown below.UB alarm in CHM board Failure Analysis 3. The objective probe of one chipset CEMCTRL which is acquired by control management is empty 2.Check if there is UB alarm Possible Solution 2.Check board version 5.Mission initialization failure 1.CE type is not compatible 3.ZXC10 BSSB (V8.Block problem chipset Confidential and Proprietary Information of ZTE CORPORATION . the objective probe is empty Following are the reasons: Failure Analysis 1.Check CES with probe 4.9) Call Failure Reason and Call Drop Explanation (1x) ERR_CES_RLSA_CEC_CALLHNDL _FCH_SETUP_RCV_CEM_REJECT T A B L E 1 3 7 E R R _ C E S _ R L S A_ C E C _ C A L L H N D L _ F C H _ S E T U P _ R C V _ CEM_REJECT Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM _REJECT Failure Cause When FCH channel is in establishment.Block the problem chipset ERR_CES_RLSA_CEC_CALLHNDL _FCH_SETUP_CEMCTRL_NULL T A B L E 1 3 8 E R R _ C E S _ R L S A_ C E C _ C A L L H N D L _ F C H _ S E T U P _ CEMCTRL_NULL Failure Name ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CEMCTRL _NULL Failure Cause When FCH channel is in establishment.1.0. CEC receives CEM rejection message and this leads to FCH channel establishment failure Following are the reasons Failure Analysis 1.Check if chipset configuration accord with the reality 2.Check CHM board CPU 3.Chipset serial number is not correct Possible Solution 80 1.Internal transmission message failure 2. Solve the lower level problem 2.Chapter 6 CES Related Failures ERR_CES_RLSA_CEC_CALLMAIN _FCH_SETUP_CREATE_PROCES S T A B L E 1 3 9 E R R _ C E S _ R L S A_ C E C _ C A L L M A I N _ F C H _ S E T U P _ CRE ATE_PROCESS Failure Name ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_P ROCESS Failure Cause When FCH channel is in setup. process establishment fails.Dispatch V_Create function mistake 2. Failure Analysis Possible Solution Following are the reasons: 1.Check board version 1.Block the problem CHM board Confidential and Proprietary Information of ZTE CORPORATION 81 . 0.1.ZXC10 BSSB (V8.9) Call Failure Reason and Call Drop Explanation (1x) This page is intentionally blank. 82 Confidential and Proprietary Information of ZTE CORPORATION . ............................................................2 Table 6 ERR_SPS_RLSA_BSSAP_TE_Tassignment................................................................................................... 10 Table 20 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut ........................................9 Table 19 ERR_SPS_RLSA_BSSAP_UnexptMsg_ RcvRegInAssignState_Others ..........................................5 Table 12 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddr ByLogicAddr ................................7 Table 16 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail .2 Table 7 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect 3 Table 8 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder4 Table 9 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup..................5 Table 11 ERR_SPS_RLSA_BSSAP_TE_Txxp...............................6 Table 13 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ UserBusy ....................................Tables Table 1 Chapter Summary ......................7 Table 15 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed ...............................6 Table 14 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ NormalClearing .................................... 12 Confidential and Proprietary Information of ZTE CORPORATION 83 ....................... ii Table 3 Mouse Operation Conventions ............9 Table 18 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnIn SessionState.1 Table 5 ERR_SPS_RLSA_BSSAP_TE_T3230 ..i Table 2 Typographical Conventions ...................................... iii Table 4 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ Unspecified.................................................................................. 11 Table 22 ERR_SPS_RLSA_BSSAP_UnexptMsg_ RcvRegInAssignState_PowerDown .................... 10 Table 21 ERR_SPS_RLSA_BSSAP_UnexptMsg_ RcvRegInAssignState_PowerOn .... 11 Table 23 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__ TargetBSCHandlerEntry__A7HOReqMsgProccessForHOWith1X.4 Table 10 ERR_SPS_RLSA_BSSAP_TE_T303 ........................................................................................................................................8 Table 17 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ NoAnswer.......................................................... .......................................................... 15 Table 30 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_ SccpId2CallRef................. 14 Table 27 ERR_SPS_RLSA_BSSAP_TgtBSC_Other__ TargetBSCHandler_A7fHandoffRequestProccess__RecievedA7HO ReqWhenSemiHO ....................................... 20 Table 36 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure ...................................................... 17 Table 34 ERR_SPS_RLSA_DSPM_CLH_OtherReason_ MSNormalRelease................................................ 17 Table 33 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ AuthenticationFailure ...................................................... 14 Table 28 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ SemiConcurrentService ................................ 15 Table 29 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_ InvalidServiceOption ................. 25 84 Confidential and Proprietary Information of ZTE CORPORATION .......................................................................................................... 24 Table 42 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM.........................................................ZXC10 BSSB (V8.................................................................................... 23 Table 40 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMDTXTim e......................................................... 13 Table 26 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ HandoffSuccessful ..9) Call Failure Reason and Call Drop Explanation (1x) Table 24 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit ................. 21 Table 38 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3 .............. 19 Table 35 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder ............. 23 Table 41 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHPNDropIndication_ReleasebyHOH.................................................... 16 Table 31 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail16 Table 32 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_ EquipmentFailure ....................................1..0........................................................ 22 Table 39 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime ......................................................................................................... 24 Table 43 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHRelease_ReleasebyCLH................................................ 21 Table 37 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown ....................... 25 Table 44 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherRe ason ...... 12 Table 25 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannel Assignment_AllBtsFail ...................................................... .............. 37 Table 64 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_ Reason_Administratively_Pohibited ............................................ 33 Table 58 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_ Reason_Unspecified ................................................................. 34 Table 60 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup 35 Table 61 ERR_SPS_RLSA_DSPM_CLH_OtherReason_ Tshakehandrecv .......... 29 Table 53 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_ SoftHOThocompletion ................................................................ 38 Confidential and Proprietary Information of ZTE CORPORATION 85 .... 27 Table 48 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnTfschdroppending_ReleasebyTDropPending .................................... 31 Table 55 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_ HOHOnUmrCFSearchReport .............................. 36 Table 63 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_ HOHOnA7rHOReqAck ............................................ 26 Table 46 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHFSCHHandoff_HardHandoff ...... 32 Table 57 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq ............................................... 29 Table 52 ERR_SPS_RLSA_DSPM_CLH_OtherReason_ PCFNormalRelease......................................................................... 35 Table 62 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_ SemiSoftHOThocompletion................................................................................................................... 28 Table 50 ERR_SPS_RLSA_DSPM_CLH_OtherReason_ PCFEquipmentFailure .................................. 26 Table 47 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop ........................................................................................ 30 Table 54 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq ........................................... 27 Table 49 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM .................................................................. 28 Table 51 ERR_SPS_RLSA_DSPM_CLH_OtherReason_ MSGoingIntoDormant............................Tables Table 45 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration .... 32 Table 56 ERR_SPS_RLSA_DSPM_HOH_OtherReason_ AbisdHandShakeFailure ............... 38 Table 65 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_ PDSN_Resource_Unavailable ..................................................................... 34 Table 59 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD .......................................................... ........ 50 Table 83 DBS_STASTIC_WALSHCODE_LACK ..... 44 Table 73 SDM_Link_Fail_FwdA2pNoFrm................................................................. 58 Table 99 ALLOCATE_UID_ERROR .......................... 52 Table 87 ARRIVE_TIME_ERROR .................................................................................0... 46 Table 76 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm .................................................... 46 Table 77 SDM_Activate_Fail_InitVocoderFail..................ZXC10 BSSB (V8................. 55 Table 93 FO_NOT_ENOUGH .... 44 Table 72 SDM_Link_Fail_RevTooManyBadFrm....... 54 Table 91 SOFTADD_CELL_ERROR ............................. 57 Table 97 UIDWIDTH_NOT_ENOUGH ............ 51 Table 86 FCH_NUMBER_TWO ....................... 55 Table 94 CE_NOT_ENOUGH ............ 57 Table 98 RS_NOT_EXIST ............................ 48 Table 81 DBS_STASTIC_FWDFCHCE_REVCE_LACK ..................................................................................................... 43 Table 71 SDM_Link_Fail_RevNoFrm .................. 45 Table 75 SDM_Link_Fail_RSCHLegLinkFail ......................................................................................... 48 Table 80 SDM_Activate_Fail_MsgParaFail .............. 39 Table 68 SDM_Activate_Fail_AcquirePreambleFail_Normal ..... 56 Table 95 WALSHCODE_NOT_ENOUGH .................................................................................................................. 45 Table 74 SDM_Find_Fail_WaitConfigRLPTimeout .............................................................. 49 Table 82 DBS_STASTIC_FWDFCHCE_LACK............. 47 Table 78 SDM_OprVocoder_Fail_WaitStartVocoderCodingAck TimeOut.......... 53 Table 89 INPUT_PARA_ERROR............. 56 Table 96 BEFORE_CPS ......... 52 Table 88 NO_SYSTEM_TIME ............................... 54 Table 92 NO_AVAILABLE_REV_CE... 58 86 Confidential and Proprietary Information of ZTE CORPORATION . 50 Table 84 DBS_STASTIC_UID_LACK .......................................... 51 Table 85 DBS_STASTIC_NO_RESOURCE_LACK .............1............ 41 Table 69 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm 42 Table 70 SDM_Find_Fail_WaitConfigVTCTimeout . 47 Table 79 SDM_Find_Fail_NoFCHLeg ......................................................... 53 Table 90 POWER_NOT_ENOUGH ....................................9) Call Failure Reason and Call Drop Explanation (1x) Table 66 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure 39 Table 67 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_ SCHHOnUmrSCHRequestMsg_FCHNotExisted ........................... ................................ 71 Table 123 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb..... 62 Table 107 HO_STAT_PILOT_NOT_LOCALBSS .................. 73 Table 127 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_ CellNotFoundInRevSCHResourceExtension ............................................................................. 59 Table 101 HO_STAT_CARRIER_PWR_OVERLOAD........................................................................... 64 Table 111 BSC_NO_VE .............. 65 Table 113 BSC_DSPM_NO_INSTANCE.............................................. 63 Table 110 BSC_NO_SE ........................ 60 Table 103 HO_STAT_CARRIER_NO_CE .... 59 Table 102 HO_STAT_CARRIER_STATE_ERROR ................................................................................................................................... 65 Table 114 BSC_NO_RTPPORT .............. 71 Table 124 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_ RevSCHSetupFail... 63 Table 109 BSC_NO_CIC............................................................................................................................... 60 Table 104 HO_STAT_CARRIER_NO_5KCE.......... 68 Table 118 ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired.............. 66 Table 115 BSC_NO_VALID_RMP .................................. 62 Table 108 HO_STAT_PILOT_IS_OTHER_UNLNKBSS ................................. 70 Table 121 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_ AddChannelFail .......................................................................................................................................... 66 Table 116 ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate ....................................... 72 Table 126 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_ STATUS_RemovedSCH ................................ 64 Table 112 BSC_NO_IWF ......... 69 Table 120 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_ FSCH ............................................................... 73 Confidential and Proprietary Information of ZTE CORPORATION 87 .......................... 70 Table 122 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch ................ 72 Table 125 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_ FwdSCHSetupFail ...................................................................... 67 Table 117 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_ REMOVEREQ .. 61 Table 106 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO ............... 61 Table 105 HO_STAT_PILOT_IS_NOT_NEIGHBOR ........................Tables Table 100 HO_STAT_PILOT_NO_SAME_FREQ ......... 69 Table 119 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_ RSCH....... ......... 80 Table 138 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_ CEMCTRL_NULL .......................................9) Call Failure Reason and Call Drop Explanation (1x) Table 128 ERR_SPS_RLSA_RCM_FSCH_OtherReason_ EndOfDuration ................................................ 79 Table 137 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_ CEM_REJECT ..................................................... 75 Table 131 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_ atTchStatusInSemiSoft_AbisdfBurstRequest ................................................................................... 75 Table 132 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch ..................................................................... 77 Table 135 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_ MAbisdMsgDispatch ....... 74 Table 129 ERR_SPS_RLSA_RCM_FCH_OtherReason_ MRequestAbisConnect_SpecifiedCellIsReleasing ................................................................ 80 Table 139 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_ CREATE_PROCESS..........................................1...........ZXC10 BSSB (V8....... 81 88 Confidential and Proprietary Information of ZTE CORPORATION .........0.............................. 74 Table 130 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_ TfschNotifyExpired.............................. 77 Table 136 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_ IN_USED............ 76 Table 134 ERR_SPS_RLSA_RCM_FCH_OtherReason_ MRequestAbisConnect_SameTimeCellInSameGroupInDiffSetupFl ow ....................................... 76 Table 133 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_ BurstRequest_ConnInSetup .................................................................................