ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

ZXC10 BSSB
CDMA Base Station System
Call Failure Reason and Call Drop

Explanation (EV-DO)
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: doc@zte.com.cn
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
6/11/2007
R1.0
sjzl20071308
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 (EV-DO)
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
Call Failure ....................................................................... 1
Chapter 2........................................................................ 27
Handoff Failure .............................................................. 27
Chapter 3........................................................................ 43
Reasons for Call Drop .................................................... 43
Chapter 4........................................................................ 81
Release Failure............................................................... 81
Tables ............................................................................. 85
About this Manual

Purpose
This manual describes reasons and explanations for call drop
and call failure for ZXC10 BSSB (EV-DO) product. This manual
also provides suitable solutions to solve these problems.
Intended Audience
This document is intended for engineers and technicians who
perform operation activities on ZXC10 BSSB (EV-DO) product.
Prerequisite Skill and Knowledge

To use this document effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
the ZXC10 BSSB system and its various components
local operating procedures
What is in This Manual

This Manual contains the following chapters:
TABLE 1 CHAPTER SUMM ARY
Chapter
Summary
Chapter 1
Describes causes and solutions for call

failure.
Call Failure
Chapter 2
Handoff Failure
Chapter 3
Describes reasons and settlement

measures for handoff failure.
Reasons for Call Drop
Explains the reasons and settlement

measures for call drop.
Chapter 4
Describes reasons and solutions for
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
Summary
Release Failure
release failure.
Related Documentation
The following documentation is related to this manual:
ZXC10 BSSB (V8.0.1.9) CDMA2000 Base Station System
General Description
Conventions
Typographical
Conventions
ZTE documents employ the following typographical conventions.

TABLE 2 TYPOGRAPHICAL CONVENTIONS
Typeface
Meaning
Italics
References to other Manuals and documents.
Quotes
Links on screens.
Bold
Menus, menu options, function names, input

fields, radio button names, check boxes, dropdown lists, dialog box names, window names.
CAPS
Keys on the keyboard and buttons on screens

and company name.
Constant width
Text that you type, program code, files and

directory names, and function names.
[]
Optional parameters.
{}
Mandatory parameters.
Select one of the parameters that are delimited

by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Mouse
Operation
Conventions
ii
TABLE 3 MOUSE OPERATION CONVENTIONS
Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually

the left mouse button) once.
Double-click
Refers to quickly clicking the primary mouse button
About this Manual
Typeface
Meaning
(usually the left mouse button) twice.
Right-click
Refers to clicking the secondary mouse button

(usually the right mouse button) once.
Drag
Refers to pressing and holding a mouse button and

moving the mouse.
How to Get in Touch

The following sections provide information on how to obtain
support for the documentation and the software.
Customer
Support
Documentation
Support
If you have problems, questions, comments, or suggestions

regarding
your
product,
contact
us
by
e-mail
at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
iii
iv
Chapter
Call Failure
This chapter describes failure cause values, causes and solutions
for call failure problems.
T A B L E 4 C O N N E C T I O N _ S E T U P _ AV B S C C H I T E M R E Q _ T I M E O U T
Failure
Cause
Value
142
After connection establishing and resource allocating, SP
sends an AvrBSCChItemRequired message to BSSAP to
request the information of adding channel table. If no
response, connection establishing fails.
Details
In the following cases, there may be a large volume of

such failures:
1. links between boards fail
2. version mismatch
3. Incorrect data configuration
If the links between boards fail, reset the suspected
board (DOCMP, DOSDU and UIM)
Solution
if there is a version mismatch, check the version

compatibility of DOCMP and DOSDU
If data configuration is incorrect, check the data
configuration and rollback.
TABLE 5 CONNECTION_SETUP_SETDRCLENTR ANS_FAILURE
Failure
Cause
Value
141
Details
After resource allocating and before sending TCA, an

AbiscfSetDRCAndAckInfo message and an
AbiscfSetDRCLengthTransition message is sent to all
channel boards for parameter settings. In the
received AbiscrSetDRCLengthTransitionAck message,
if the field Result0 (0 stands for success),
connection establishing fails.
Solution
Check the system parameters in NetNumenTM

M3(ZXC10 BSSB). If the DRCLength (in DRC
parameter table) that correspond to the different
numbers of leg are incorrect, the data configuration
may be faulty, consider rollback.
Chapter 1 Call Failure
TABLE 6 CONNECTION_SETUP_SETDRC AND ACKINFO_F AILURE
Failure
Cause
Value
140
Details
After resource allocating and before sending TCA, an

AbiscfSetDRCAndAckInfo message and an
AbiscfSetDRCLengthTransition message is sent to all
channel boards for parameter settings. In the
received AbiscrSetDRCAndAckInfoAck message, if the
field Result0 (0 stands for success), connection
establishing fails.
Solution
Check the system parameters in OMC. If the

DRCLength, DRCChannelGain, AckChanelGain, and
DSCChannelGain and DRCThreshold (in DRC
parameter table) that correspond to the different
numbers of leg are incorrect, the data configuration
may be faulty, consider rollback.
TABLE 7 CONNECTION_SETUP_AT ACQUIRED_TIMEOUT
Failure
Cause Value
Details
139
Upon receiving a reverse capture message, SP sends
an AbiscfATAcquired message to channel board to
request power control mode change and wait for the
response. If not all responses are collected before
timer expires, connection establishing fails.
In the following cases, there may be a large volume
of such failures:
1. links between boards fail
2. version mismatch
If the links between boards fail, reset the suspected
board (DOSDU, CHM and UIM)
Solution
If there is a version mismatch, check the version

compatibility of CHM and DOSDU
T A B L E 8 C O N N E C T I O N _ S E T U P _ AV F _ B S C C H I T E M R E Q A C K _
P AR A _ E R R O R
Failure
Cause Value
Details
138
Connection is established after the completion of
resource allocation. SP sends
AvrBSCChItemRequired message to BSSAP to
request access to channel adding list. If the quantity
of ucBSCIPNumber in the received
vfBSCChItemRequiredAck message is more than the
highest leg number (6), mistakes occurs while saving
BSCIP.
Upon completion of connection establishing and
resource allocating, SP sends an
AvrBSCChItemRequired message to BSSAP to
request a connection. This request fails.
Solution
Perhaps BSSAP fails to retrieve data from database.

The IP addresses are configured by the system
automatically. If there are a large volume of such
failures, reset DOCMP board and synchronize the
data.
TABLE 9 CONNECTION_SETUP_RCP_TIMEOUT
Failure
Cause
Value
137
Details
SP sends a resource allocating request to RCP without

receiving reply. The timer expires. The state of the
sector that waits for resource allocation will be marked
with this reason. If it is the 1st resource allocating
request, the connection establishing fails with the cause
CONNECTION_SETUP_CARRIER_ALLOCATE_TIMEOUT.
Otherwise, the connection establishing will not fail.
In the following cases, there may be a large volume of
such failures:
1. Some CEs are abnormal. Solution: check the probe in
OMC reset CHM;
Solution
2. Perhaps the problem of the links between boards

causes message loss. Solution: reset the suspected
boards(DOSDU, CCM, UIM and etc.);
3. Version mismatch. Solution: check version

compatibility of DOSDU, CCM and CHM
4. BSC and BTS have inconsistent data. Solution:
synchronize data towards OMP and CCM
5. Incorrect data configuration. Solution: Check data
T A B L E 1 0 C O N N E C T I O N _ S E T U P _ A B N O R M A L _ R E L E AS E
Failure
Cause Value
136
Details
While establishing a connection, if base station

initiates a release because of some reasons,
Reasons for release failure vary. Checking out
abnormality in some modules occurs and
abnormality probe are suggested.
Solution
There are a lot of release causes.
TABLE 11 CONNECTION_SETUP_TCC_TIMEOUT_W AITING_TCC_

COMING
Failure
Cause Value
135
Details
SP sent a TCA message to handset without receiving

the TCC message. TCC waiting timer expiration
causes connection establishment failure.
Confirm one of the following situations on MS side
log message when above problems occur.
1. Handset does not receive the RTCAck message.

If the parameters in the received TCA message
are correct, but the handset does not start
sending data at reverse direction, consider the
following possibilities:
(1)CHM does not capture the handset, or DOSDU is
not notified after capture. This problem may be
because of following:
CHM or links between boards fail,
Solution
Solution: check CHM or DOSDU according to running

information observation or abnormal probe to see if
they run normally. Consider resetting CHM and
DOSDU.
(2)Handset is captured by base station. But the
RTCAck message sent from DOSDU is not received
by the handset. Perhaps the forward media stream
has problem. Solution: Make sure CHM, DOSDU,
ABPM and DSM run normally and are in correct
versions. Consider resetting these boards.
2. Handset receives the RTCAck message and

sends out the TCC message, but base station
does not receive it. Perhaps the reverse media
stream has problem. Solution: Make sure CHM,
DOSDU, ABPM and DSM run normally and are in
correct versions. Consider resetting these
boards.
TABLE 12 CONNECTION_SETUP_AT_TERMINATED
Failure
Cause Value
134
Details
When establishing a connection, if a handset

initiates a call release because of some reasons,
Solution
Users mishandling. No special handling is needed.
TABLE 13 CONNECTION_SETUP_SDU_OVERLO AD
Failure
Cause Value
130
Details
A new call origination request is received, but SDU

is overloaded, connection establishing fails.
Solution
Overload control is necessary. No special handling is

needed.
TABLE 14 CONNECTION_SETUP_SEND_TC A_F AILURE
Failure
Cause Value
129
Details
When connection establishing resources allocating

completes, SP creates a TCA message and sends it
to handset via control channel, if fail to send it,
Solution
If there are a large volume of such failures. SP

module may be internally faulty. Reset DOSDU
board.
TABLE 15 CONNECTION_SETUP_EXCEED_ONE_PILOT_F AILURE
Failure
Cause Value
128
Details
When establishing a connection, if more than one

sector suffers from resource allocation failure, but
connection establishing does not fail, this reason will
be reported by the last service observation.
of such failures:
1. Some carrier/sectors are abnormal and cause
resource allocating failure. Solution: check CEs
state with probe. Consider resetting the CHM board.
2. Malfunctions of the links between boards cause
message loss. Solution: reset the suspected boards
(DOSDU, the CCM that the failed sector is in, UIM
and etc.);
Solution
3. Version mismatch. Solution: check the version

compatibility of DOSDU, the CCM and CHM that the
failed sector is in;
4. Incorrect data configuration. Solution:
synchronize data towards OMP and the CCM that the
failed sector is in, or check data configuration and
rollback.
TABLE 16 CONNECTION_SETUP_RCP_ ADD_CH ANNELITEM_FAILURE
Failure
Cause Value
126
Details
When SP requests resource allocation from RCP,

RCP has to add channel board information on DSM.
If this operation fails, RCP will initiate a release
against SP, connection establishing fails.
of such failures:
Solution

compatibility of CCM and DSM
2. Data is not synchronized or data is
configured
incorrectly.
Solution:
synchronize data towards OMP and CCM, or
check data configuration and rollback.
T A B L E 1 7 C O N N E C T I O N _ S E T U P _ AV F _ N E I G H B O R L I S T _ P A R A _ E R R O R
Failure
Cause Value
125
Details
SP requests neighbor cell information from BSSAP. In

the received AvfNeighborListUpdateMsg, if there is a
parameter error,(e.g. :ucNumPilots is greater than
the maximum number of pilot in active set, or
ucBTSNumber is greater than the maximum number
of neighbor cell, or the number of ChannelRecord is
greater than the maximum number of pilot after
saving the ChannelRecord contained in neighbor cell
pilot), connection establishing fails.
of such failures:
Solution

compatibility of DOCMP and DOSDU;
2. Incorrect data configuration. Solution: check OMC
neighbor cell configuration, synchronize data towards
OMP, or check data configuration and rollback.
TABLE 18 CONNECTION_SETUP_DRCAND ACKINFO_TIMEOUT
Failure
Cause
Value
124
Details
After resource allocating and before sending TCA, it

is needed to send AbiscfSetDRCAndAckInfo and
AbiscfSetDRCLengthTransition message to all channel
boards for parameter setting. If the timer expires
before all replies are collected, connection
establishing fails.
of such failures:
1. Links between boards are faulty. Solution: reset
the suspected boards(DOSDU, CHM and UIM);
Solution

compatibility of DOSDU, CHM and UIM;
3. Check system parameters in OMC to see if the
DRCLength, DRCChannelGain, AckChanelGain,
DSCChannelGain and DRCThreshold (in DRC
parameter table) that correspond to different
numbers of leg are correct. If not, the data
configuration may be incorrect. Consider rollback.
TABLE 19 CONNECTION_SETUP_CARRIER_ALLOCATE_TIMEOUT
Failure
Cause Value
123
Details
SP sends the 1st resource allocating request to RCP

without reply. Connection establishing fails.
of such failures:
the suspected boards (DOSDU, CCM, UIM and etc.);
Solution

compatibility of DOSDU, CCM and UIM;
3. Data is not synchronized or data is configured
incorrectly. Solution: Synchronize data towards OMP
and CCM, or check data configuration and rollback.
TABLE 20 CONNECTION_SETUP_CARRIER_ALLOCATE_P AR A_ ERROR
Failure
Cause Value
122
Details
SP sends the 1st resource allocating request to RCP,

if in the received reply the number of leg is not 1,or
the number of sector under the leg is not
1,connection establishing fails.
of such failures:
compatibility of DOSDU, CCM and UIM;
Solution
2. CCM not works normally, reset it;

incorrectly. Solution: synchronize data towards OMP
TABLE 21 CONNECTION_SETUP_ALLOC ATE_C AR RIER_ID_ERROR
Failure
Cause Value
121
Details

if the CarrierId in the received reply is not found in
the sector information saved in SP, the CarrierId is
believed incorrect. Connection establishing fails.
of such failures:
Solution

compatibility of DOSDU, CCM and UIM
TABLE 22 CONNECTION_SETUP_CARRIER_ALLOCATE_F AILURE
Failure
Cause Value
120
Details

If the resource allocating of the 1st sector under the
1st leg that carried in the in the received reply is not
0 (0 stands for success), connection establishing
fails.
of such failures:
Solution
1. Version mismatch. Solution:check version

TABLE 23 CONNECTION_SETUP_PILOTS_NUMBER_ERROR
Failure
Cause Value
119
Details
In the RU message sent over the access channel by

a handset, except the reference pilot, if the number
of other pilots is greater than the maximum number
of pilot (15), connection establishing fails.
Solution
Handset reports an error. No special handling is

needed.
TABLE 24 CONNECTION_SETUP_INVALID_PILOT_PN
Failure
Cause Value
118
Details
SP cannot find the sector (it is determined by BSSAP

parsing) that handsets report RU messages in the
sector information carried in Av interface message,
or cannot find the reference carrier parsed by
BSSAP in the sector information when it processes
Av interface connection establishing message,
of such failures:
Solution
1.There is data inconsistency between BSC and BTS.

It is suggested to synchronize data towards OMP
and CCM.
2. BSSAP module has internal malfunctions. It is
suggested to reset DOCMP board.
10
TABLE 25 CONNECTION_SETUP_CELL_NUMBER_ERROR
Failure
Cause Value
117
Details
SP detects that the number of carried sector is

greater than the maximum number of sector (16)
when it processes Av interface connection
establishing message, connection establishing fails.
Solution
If there is large volume of such failures, perhaps

BSSAP module has internal malfunction. It is
suggested to reset DOCMP board
TABLE 26 CONNECTION_SETUP_BTS_NUMBER_ERROR
Failure
Cause Value
116
Details
SP detects that the number of carried BTS information is

greater than the maximum number of sector (16) when it
processes Av interface connection establishing message,
Solution
If there is large volume of such failures, perhaps BSSAP

module has internal malfunction. It is suggested to reset
DOCMP board
TABLE 27 CONNECTION_SETUP_PILOT_INCREMENT_ERROR
Failure
Cause Value
115
Details
SP detects that PilotIncrementparameter in Session

information is 0 when it processes Av interface connection
establishing message, connection establishing fails.
Solution
If there is large volume of such failures, possibly BSSAP

module has internal malfunction. It is suggested to reset
DOCMP board
TABLE 28 CONNECTION_SETUP_M AX _SOFTH ANDOFF_NUM_ERROR
Failure
Cause
Value
114
Details
SP detects that MaxSoftHandoffNumparameter is less

than 3 or greater than 6 when it processes Av
interface connection establishing message,
If there is large volume of such failures, the possible
causes:
Solution
1. Data configuration is faulty. Solution:check data

configuration and rollback the data;
2. BSSAP module has internal malfunction, It is
suggested to reset DOCMP board and BSSAP module.
11
TABLE 29 CONNECTION_SETUP_MOBILE ACQUIRED_

FORW ARDDESIRED _TIMEOUT_FLOWCTRL_RECV
Failure
Cause
Value
112
Details
After SP sends the TCA message to handset, MobileAcquired

and ForwardDesired are not received after forward/reverse
capture timer expires. Connection establishing fails.
View the log information at handset side to check if TCA
message is received.
If it is not received, there may be packet sending problem on
forward control channel:timecard
1. Links between boards failed. Solution: reset the
suspected boards(DOSDU, CCM, UIM and etc.);
Solution

If the TCA message received by handset passes the
verification, the reverse demodulation of CHM is likely
faulty. Make sure the chip setting parameters of CHM
and the data in the DRC parameter table of system
parameters are correct. Consider rollback.
TABLE 30 CONNECTION_SETUP_FORW ARDDESIRED_

TIMEOUT_FLOWCTRL_RECV
Failure
Cause Value
110
Details
Upon sending the TCA message to handset, SP receives a

MobileAcquired message. But ForwardDesired is not
received even after forward/reverse capture timer expires.
Connection establishing fails eventually.
Solution
CHM reverse demodulation has problem. The reverse

demodulation of CHM is likely to be faulty. Make sure the
chip setting parameters of CHM and the data in the DRC
parameter table of system parameters are correct. Consider
rollback.
TABLE 31 CONNECTION_SETUP_MOBILE ACQUIRED_TIMEOUT
12
Failure
Cause Value
109
Details
Upon sending the TCA message to handset, SP

receives a ForwardDesired message. But
MobileAcquired is not received even after
forward/reverse capture timer expires. Connection
establishing fails eventually.
Solution
The reverse demodulation of CHM is likely to be

faulty. Make sure the chip setting parameters of
CHM and the data in the DRC parameter table of
system parameters are correct. Consider rollback.
TABLE 32 CONNECTION_SETUP_NEIHBOURLIST_TIMEOUT
Failure
Cause Value
108
Details
SP requests neighbor cell information from BSSAP. If

AvfNeighborListUpdateMsg is not received,
of such failures:
the suspected boards(DOCMP, DOSDU, UIM and
etc.);
Solution

compatibility of DOCMP and DOSDU;
TABLE 33 CONNECTION_SETUP_NO_PILOT_IN_LAST_
ROUTERUPDATE
Failure
Cause Value
106
Details
After processing the Av interface connection

establishing message, SP needs to find a sector to
create the 1st AbiscfConnectionSetupMsg to send to
RCP for requesting carrier resource allocating. If the
message creation fails, connection establishing fails.
of such failures:
1. The RouteUpdate message reported by handset is
abnormal. Be confirmed according to the Log
information at handset side.
Solution
2. BSSAP module has internal malfunction, it is

suggested to reset DOCMP board.
TABLE 34 CONNECTION_SETUP_ADD_CH ANNELITEM_TIMEOUT
Failure
Cause Value
105
Details
After connection establishing and resource allocating,

SP needs to send an AcfBSCAddChannelItemMsg to
the IGWP module on ABPM to request a new channel
table. If no reply is received before the timer expires,
of such failures:
Solution

compatibility of DOSDU and ABPM;
13
TABLE 35 CONNECTION_SETUP_ADD_CH ANNELITEM_FAILURE
Failure
Cause Value
104
Details
After connection establishing and resource allocating,

SP needs to send an AcfBSCAddChannelItemMsg to
the IGWP module on ABPM to request a new channel
table. If the field dwCause in the received
AcrBSCAddChannelItemAck message is not 0 (0
stands for success), connection establishing fails.
of such failures:
Solution

compatibility of DOSDU and ABPM;
TABLE 36 CONNECTION_SETUP_ACTIV ATE_TP_F AILURE
Failure
Cause Value
103
Details
After connection establishing and resource

allocating, SP needs to activate TP module to
prepare for data sending. If it fails to invoke the
activation function of TP module, connection
establishing fails.
Solution
If there is large volume of such failures, likely cause

is TP module has internal malfunction. It is
suggested to reset DOSDU board
TABLE 37 CONNECTION_SETUP_TCA_ENCODE_FAILURE
Failure
Cause Value
102
Details
SP needs to code the TCA message before sending it

to handsets via air-interface. If it fails to invoke the
coding function, connection establishing fails.
Solution

is the internal malfunction SP module. It is
TABLE 38 CONNECTION_SETUP_CARRIER_ALLOCATE_ERROR
14
Failure
Cause Value
101
Details
SP detects that there is no pilot in active set when it

creates a TCA message, connection establishing
fails.
Solution

is SP module has internal malfunction It is
T A B L E 3 9 C O N N E C T I O N _ S E T U P _ I N V A L I D _ AB I S _
B ANDWIDTH_DISTRIBUTED
Failure
Cause Value
21
Details
Abis bandwidth allocating fails
Solution

is Abis link has no bandwidth. Solution: wait for
restore of Abis bandwidth
TABLE 40 CONNECTION_SETUP_SDU_OVERLO ADED
Failure
Cause Value
20
Details
SDU overloads
There are the following possibilities:
1. On this DOSDU, there are a lot of users in
forward data transmission. Solution: wait for the fall
of DOSDU CPU, or add DOSDU boards.
Solution
2. Overload algorithm on DOSDU has problem.

Solution: Collect information and contact local ZTE
office.
TABLE 41 CONNECTION_SETUP_CONNECTIONSETUP_TIMEOUT
Failure
Cause Value
19
Details
connection establishing expires
Solution
Perhaps DOSDU runs abnormally. Solution: Contact

local ZTE office and reset DOSDU.
TABLE 42 CONNECTION_SETUP_INVALID_RSP_PID
Failure
Cause Value
18
Details
Failed to create the PID of RSP process
Solution
Perhaps DOCMP runs abnormally. Solution:reset

DOCMP
TABLE 43 CONNECTION_SETUP_INVALID_PPPSESSION_PID
Failure
Cause Value
17
Details
the PID that creates PPPSession process fails
Solution

DOCMP
15
T A B L E 4 4 C O N N E C T I O N _ S E T U P _ I N V A L I D _ B S S AP _ P I D
Failure
Cause Value
16
Details
Failed to retrieve PID of BSSAP process
Solution

DOCMP
TABLE 45 CONNECTION_SETUP_INVALID_DBS_CONFIG
Failure
Cause Value
14
Details
Failed to retrieve negotiation parameters
Solution
OMC does not have parameter configuration, or the

configuration is incorrect. Solution: Configure
correctly and synchronize data.
TABLE 46 CONNECTION_SETUP_INV ALID_INFO_UPDATE_POLICY
Failure
Cause Value
13
Details
Fail to retrieve update strategy of connection

information
Solution
Perhaps OMC is not configured with parameters or

configuration is incorrect. Solution: Configure
TABLE 47 CONNECTION_SETUP_INV ALID_DRCACK_INFO
Failure
Cause Value
11
Details
fail to retrieve DRC and ACK channel parameters
Solution

is OMC is not configured with DRC parameter table.
Solution: Configure correctly and synchronize data.
TABLE 48 CONNECTION_SETUP_INV ALID_LOC ATION_P AR AME TER
16
Failure
Cause Value
10
Details
Fail to retrieve Location parameters
Solution

configuration is incorrect. Solution:Configure
TABLE 49 CONNECTION_SETUP_INV ALID_M AX_SOFTH ANDOFF_NUM
Failure
Cause Value
Details
Fail to retrieve MaxSoftHandoffparameter
Solution

configuration is incorrect. Solution:Configure
TABLE 50 CONNECTION_SETUP_INVALID_CELL_INFO
Failure
Cause Value
Details
Fail to retrieve cell parameters
Solution
Likely cause is parameters are not synchronized

after modification. Solution:synchronize the
parameters in OMC
TABLE 51 CONNECTION_SETUP_INVALID_RU
Failure
Cause Value
Details
fail to retrieve active pilots from RU
Solution
Likely cause is parameters are not synchronized

after modification. Solution:synchronize the
parameters in OMC
TABLE 52 CONNECTION_SETUP_INVALID_CELLID
Failure
Cause Value
Details
Fail to retrieve CellIdparameter
Solution
Likely cause is data is not synchronized after

parameter modification. Solution:synchronize the
OMC parameters
TABLE 53 CONNECTION_SETUP_INVALID_SESSION_INFO
Failure
Cause
Value
Details
Fail to retrieve SessionInformationparameter
Solution
Likely cause is DOCMP runs abnormally.

Solution:contact local ZTE office
17
TABLE 54 CONNECTION_SETUP_INVALID_SDU
Failure
Cause Value
Details
Fail to allocate SE resources, or fail to retrieve the

ModuleID that SE belongs to
likely causes:
Solution
1. SE is in wrong state. Solution:check parameters

in OMC;
2. System call upper limit is reached. Solution:add
DOSDU board.
TABLE 55 CONNECTION_SETUP_INV ALID_CALL_PAR AMETER
Failure
Cause Value
Details
Lack of ConnectionRequest message or RouteUpdate

message in connection establishment command
Solution

DOCMP board
TABLE 56 CONNECTION_SETUP_INV ALID_ AT
Failure
Cause Value
Details
Fail to retrieve AT object
Solution
Likely cause is DOCMP runs abnormally.

Solution:reset DOCMP board
TABLE 57 CONNECTION_SETUP_NETWORK_BUSY
Failure
Cause Value
Details
Fail to create CallHandler object

Likely causes:
Solution
1. Upper limit of system calls is reached.

Solution:add DOCMP board;
2. DOCMP runs abnormally. Solution:reset DOCMP
board.
18
T A B L E 5 8 C O N N E C T I O N _ S E T U P _ AM R _ P A R A _ E R R O R
Failure
Cause
Value
220
Details
When establishing a connection at BTS side, CES

returns parameter errors in connection result
Check the EV_S_AmrConnectSetupAck (or
EV_S_AmrSofterAddAck) in signaling tracking of
connection establishing and the parameter fields
ucCellNumber/aucCarrierCellId in
EV_S_AmfConnectionSetup (or EV_S_AmfSofterAdd)
to see if they are the same.
Solution
In the case they are not the same, check the

CarrierCellId to see if it is the same as the OMC
configuration. CES processing is not normal if they
are the same.
TABLE 59 CONNECTION_SETUP_CES_SOFTER_HANDOFF_
ADD_TIMEOUT
Failure
Cause Value
219
Details
If a handset requests new pilot handoff, SP will send

a message to RCP to request BTS resource
allocating. In softer handoff adding on BTS, softer
handoff adding of CES is timeout.
Check the signaling tracking when the connection is
established to see if there is
EV_S_AmrSofterAddAck.
Solution
If the problem occurs occasionally, perhaps the

communication between boards is faulty. Check the
CHM to see if it has alarms of links.
If the problem occurs frequently, check the CHM. If
it runs abnormally, It is suggested to reset CHM
TABLE 60 CONNECTION_SETUP_CES_CONNECTION_SETUP_TIMEOUT
Failure
Cause
Value
218
Details
Allocating resources for many pilots in connection

establishing or handset requests handoff to add new
pilots in handoffs. SP will send messages to RCP to
request BTS resource allocating. When establishing a
connection at BTS side, the soft handoff adding of
CES is timeout.
Check the signaling tracking when the connection is
established to see if there is
EV_S_AmrConnectSetupAck.
Solution
If the problem occurs occasionally, perhaps the

communication between boards is faulty. Check the
CHM to see if it has alarms of links.
If the problem occurs frequently, check the CHM. If it
runs abnormally, It is suggested to reset CHM
19
TABLE 61 CONNECTION_SETUP_SECTOR_USER_OVERLO AD
Failure
Cause Value
216
Details

request BTS resource allocating. In resource
allocating, user overload causes resource allocating
failure.
Solution
It is acceptable if the overload policy is reject new

connections. However, there must be a problem if
the policy is access the new connection and remove
the old connection.
TABLE 62
CONNECTION_SETUP_SECTOR_OVERLO AD_NOT_FIND_BUMP_USER
Failure
Cause Value
214
Details

request BTS resource allocating. User overloading is
detected in resource allocation, but the user to be
removed can not be found according to the removal
principle.
Solution
If appear at all times, check how many users are

under the carrier/sector. If the number nearly
reaches the threshold, and the user should be
removed can not be found out, it is believed that
the overload policy has problem.
TABLE 63 CONNECTION_SETUP_CCM_CPU_OVERLO AD
20
Failure
Cause Value
213
Details

request BTS resource allocating. CPU utilization of
CCM reaches the threshold will cause resource
allocating failure.
Solution
CPU optimization is needed if this circumstance

occurs frequently.
TABLE 64 CONNECTION_SETUP_CELLINP AR A_NOTEXIST
Failure
Cause
Value
212
Details

request BTS resource allocating. CCM detects that
the cell ID of new leg that carried in connection
request is invalid will cause handoff adding failure of
a leg.
Solution
Check signaling tracking to confirm if the aucCellId

value (the subscript of the array that corresponds to
the parameter atSetupLegInfo in the signaling
EV_S_AbiscfConnectionSetup) is a valid configured
cell ID
TABLE 65 CONNECTION_SETUP_MODIFYCARRIERUSER_FAIL
Failure
Cause Value
211
Details

establishing at BTS side, database fails to record
number of user will cause handoff adding failure of a
leg.
Solution
If it always appears, it is suggested to reset CCM

board
TABLE 66 CONNECTION_SETUP_GETDSMIP_FAIL
Failure
Cause Value
210
Details

establishing at BTS side, fail to retrieve DSM IP
address from database will cause handoff adding
failure of a leg.
Solution
If it appears at all times, make sure BSC and BTS

are synchronized. Check Abis link to see if it is
normal.
21
T A B L E 6 7 C O N N E C T I O N _ S E T U P _ G E T B S C I P _ F AI L
Failure
Cause Value
209
Details

establishing at BTS side fail to retrieve BSC IP
failure of a leg.
Solution
If appear at all times, make sure BSC and BTS are

synchronized. Check Abis link to see if it is normal.
TABLE 68 CONNECTION_SETUP_BTSIP ALLOC_F AI L
Failure
Cause Value
208
Details

establishing at BTS side, fail to retrieve BTS IP
failure of a leg.
Solution
If appear at all times, make sure BSC and BTS are

synchronized. Check Abis link to see if it is normal.
TABLE 69 CONNECTION_SETUP_CARRIERINP AR A_NOTEXIST
Failure
Cause
Value
207
Details

request BTS resource allocating. But the database at
BTS side returns carrier parameter errors.
Solution
Confirm whether BSC and BTS have both

synchronized data. If it occurs afterwards, firstly
check whether tCurrentChannel and
wChannelNumber in EV_S_AbiscfConnectionSetup
message is an efficient frequency in BSC wireless
configuration.
Make sure BSC and BTS have established data
synchronization.
22
TABLE 70 CONNECTION_SETUP_FOALLOC_F AIL
Failure
Cause Value
205
Details

request BTS resource allocating. In connection
establishing at BTS side, database fails to distribute
frame offsets.
Solution
Frame offset allocating failure is mainly caused by

channel board malfunction. If this failure occurs
frequently, reset the channel board.
TABLE 71 CONNECTION_SETUP_CHANNELINP ARA_NOTEXIST
Failure
Cause
Value
204
Details

establishing at BTS side, there is no specified channel
number in database records.
Solution
Check signal tracking. If the parameter

bChannelIncluded of the signaling
EV_S_AbiscfConnectionSetup is1, check the values of
the fields of ucSystemType,ucBandClass and
wChannelNumber (note: in current systems,
ucSystemType and ucBandClass are 0;
wChannelNumber stands for channel number)
TABLE 72 CONNECTION_SETUP_CARRIERALLOC_F AIL
Failure
Cause Value
203
Details

establishing at BTS side, database fails to allocate
carriers.
Solution
Check CHM and TRX to see if they run normally.

Check CE and carrier to see if they are blocked.
Check CEs to see if they are all busy.
Under the circumstance above, the board runs
abnormally. Otherwise, it is suggested to reset CCM
for further observation.
23
TABLE 73 CONNECTION_SETUP_LEGNUMBER_FROM_SP_ERROR
Failure
Cause
Value
202
Details

request BTS resource allocating. The parameter
ucLegNumber carried in connection request sent
from SP is invalid (greater than 6)
Solution
Check if the parameter ucLegNumber of

EV_S_AbiscfConnectionSetup in signaling tracking is
greater than 6.
TABLE 74 CONNECTION_SETUP_CELLNUMBER_FROM_SP_ERROR
Failure
Cause
Value
201
request BTS resource allocating:
1. The number of cell in new leg information that
carried in SPs connection request is invalid (0 or the
value greater than 3).
Details
2. Cell quantity in leg message of softer handoff add

contained in SP connection requirement message is
invalid (0 or a value greater than 3).
Check if the ucCellNumber in the parameter
atSetupLegInfo of EV_S_AbiscfConnectionSetup in
signaling tracking is 0 or greater than 6
Solution
TABLE 75
CONNECTION_SETUP_GIVENCARRIER_NOUS ABLECE
Failure
Cause Value
221
Details
no available CE resources
1. Make sure the channel board runs normally
Solution
2. Check if the current channel board reaches the

upper limit of users.
3. Confirm if the manual block is activated on the
channel board.
24
T AB L E 7 6 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ C R I N P AR AN O T E X I S T
Failure
Cause Value
222
Details
carrier does not exist
Solution
Check the carrier configuration in call origination cell

and make sure BSC side and BTS side are
synchronized.
T AB L E 7 7 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ C H M TY P E N O T M AT C H
Failure
Cause Value
223
Details
channel board type mismatch

The type of channel board that distributes carriers is
different from the type of the board in use.
Solution
Software has problem. Resolve the problem with

BSSAP/SP.
T AB L E 7 8 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ C R I S B E AC O N
Failure Cause
Value
224
Details
The carriers to be allocated are beacons

1. Normally, handsets originate calls in a critical
cell configured with beacons.
Solution
2. If no beacon is found in the current cell, check

the carrier configurations.
T AB L E 7 9 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ C R I S U N N O RM AL
Failure Cause
Value
225
Details
carrier is abnormal
1. Check TRX state;
Solution

carrier
T AB L E 8 0 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ N O U S AB L E C E
Failure Cause
Value
226
Details
No available CE resource
1. Make sure the channel board runs normally
Solution
2. Check if the current channel board reaches the

upper limit of users.
channel board.
25
T AB L E 8 1 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ C R I S OV E R L O AD
Failure
Cause Value
227
Details
carrier overloads
Solution
1. Check the number of users under the carrier and

the number of overloaded users in overload
parameter setting user-interface to see if the
number of users under the sector reaches the
overload threshold or not.
2. Adjust overload threshold according to network
planning.
T AB L E 8 2 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _ GE T C E L L AL L C R F AI L E D
Failure
Cause Value
228
Details
failure to retrieve the carrier configured under the

current cell
Solution
Check OMC configuration. Make sure carriers are

correctly configured under the cell, and BSC side is
synchronized with BTS side.
T AB L E 8 3 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _
GETCURCELLALLPREFFAILED
Failure
Cause Value
229
Details
specified carrier allocating failure
Solution
Software has problem. Resolve the problem with

SP.
T AB L E 8 4 C O N N E C T I O N _S E T U P _ CR AL L O C F AI L _
GETGIVENBANDCLASSCRFAILED
26
Failure
Cause Value
230
Details
Carrier allocating failure in specified frequency

bands
Solution
Handset and software have problems. Resolve the

problem with SP.
Chapter
Handoff Failure
This chapter describes failure reason values, reasons and
settlement measures for handoff failure problems.
27
T A B L E 8 5 C O N N E C T I O N _ S E T U P _ AM R _ P A R A _ E R R O R
Failure
Reason
Value
220
Reason
Description
Parameter mistake in CES return results during BTS

side connection setup
Settlement
Measures
Check if EV_S_AmrConnectSetupAck(or
EV_S_AmrSofterAddAck)in signaling tracing is
consistent with message parameter field
ucCellNumber and aucCarrierCellId in signaling
EV_S_AmfConnectionSetup(or
EV_S_AmfSofterAdd)during connection setup. If it
is not, check if CarrierCellId is consistent with the
configuration in OMC. If they are consistent, it
means abnormality occurred in CES processing.
TABLE 86
CONNECTION_SETUP_CES_SOFTER_H ANDOFF_ADD_TIMEOUT
Failure
Reason Value
Reason
Description
Settlement
Measures
28
219
While distributing resources for multiple pilots
during connection setup or when cell phone
requires handoff of newly-added pilot in handoff
process, SP sends messages to RCP to request BTS
resource distribution, and CES Softer handoff add
operation is timeout during Softer handoff add at
BTS side.
Check if EV_S_AmrSofterAddAck is in signaling
tracing during connection setup. If it is occasional,
it might be inter-board communication problem and
thus check whether there is history alarm of link
failure in CHM. If it is frequent, check whether CHM
operation is normal. If CES operation is abnormal,
resetting CHM is suggested.
Chapter 2 Handoff Failure
TABLE 87 CONNECTION_SETUP_CES_CONNECTION_SETUP_TIMEOUT
Failure
Reason Value
218
Reason
Description

resource distribution and CES soft handoff add
operation is timeout in connection setup on BTS
side.
Check if EV_S_AmrConnectSetupAck is in signaling
tracing during connection setup.
Settlement
Measures
If it is occasional, it might be inter-board

communication problem and thus check whether
there is history alarm of link failure in CHM. If it is
frequent, check whether CHM operation is normal.
If operation is abnormal, resetting CHM is
suggested.
TABLE 88 CONNECTION_SETUP_SECTOR_USER_OVERLO AD
Failure
Reason Value
216
Reason
Description

resource distribution; resource distribution failure
occurs because of subscriber overload during
resource distribution.
Settlement
Measures
This situation is normal when overload strategy is

refusing new connection and is abnormal when
overload strategy is accessing new connection and
kicking away old connection
TABLE 89 CONNECTION_SETUP_SECTOR_OVERLO AD_NOT_FIND_

BUMP_USER
Failure
Reason Value
214
Reason
Description

resource distribution; subscriber overload is found
during resource distribution, but the subscriber
being kicked away can not be found based on kickaway principle in overload situation.
Settlement
Measures
If this continues, check subscriber quantity under

the sector; if subscriber quantity approaches
threshold, and subscriber that can be kicked away
can not be found, the problem lies in overload
strategy.
29
TABLE 90 CONNECTION_SETUP_CCM_CPU_OVERLO AD
Failure
Reason Value
213
Reason
Description

resource distribution; but resource distribution fails
because of CCM overload because CPU utilization
ratio crosses threshold.
Settlement
Measures
If this happen frequently, optimization is needed to

reduce CPU utilization ration.
TABLE 91 CONNECTION_SETUP_CELLINP AR A_NOTEXIST
Failure
Reason
Value
212
Reason
Description

resource distribution; if CCM finds unlawful cell ID
contained in newly-built leg in connection
requirement message, handoff add of a certain cell
occurs.
Settlement
Measures
Check signaling tracing, if aucCellId value in lower

mark structure of the corresponding number group
of atSetupLegInfo parameter of signaling,
EV_S_AbiscfConnectionSetup is a valid cell ID
configured.
TABLE 92 CONNECTION_SETUP_MODIFYCARRIERUSER_FAIL
30
Failure
Reason Value
211
Reason
Description

resource distribution; when database has failure in
recording subscriber quantity during resource
setup on BTS side, handoff add of a certain leg will
occur.
Settlement
Measures
If this continues, resetting CCM board is

suggested.
TABLE 93 CONNECTION_SETUP_GETDSMIP_FAIL
Failure
Reason Value
210
Reason
Description

resource distribution; failure in accessing DSM IP
address from database during resource setup on
BTS side, handoff add of a certain leg will occur.
Settlement
Measures
If this continues, confirm whether there has been

synchronization of BSC and BTS, and check
whether Abis link is normal.
T A B L E 9 4 C O N N E C T I O N _ S E T U P _ G E T B S C I P _ F AI L
Failure
Reason
Value
CONNECTION_SETUP_GETBSCIP_FAIL
Reason
Description

during connection setup or when cell phone requires
handoff of newly-added pilot in handoff process, SP
sends messages to RCP to request BTS resource
distribution; failure in accessing BSC IP address
from database during resource setup on BTS side,
handoff add of a certain leg will occur.
Settlement
Measures

synchronization of BSC and BTS, and check whether
Abis link is normal.
TABLE 95 CONNECTION_SETUP_BTSIP ALLOC_F AI L
Failure
Reason Value
208
Reason
Description

resource distribution; failure in accessing BTS IP
address from database during resource setup on
BTS side, handoff add of a certain leg will be
resulted in.
Settlement
Measures

synchronization of BSC and BTS, and check
whether Abis link is normal.
31
TABLE 96 CONNECTION_SETUP_CARRIERINP AR A_NOTEXIST
Failure
Reason
Value
207
Reason
Description

resource distribution; database returns carrier
parameter error.
Settlement
Measures
Confirm whether there has been data

synchronization for BSC and BTS. If it occurs
afterwards, firstly check if wChannelNumber of
tCurrentChannel in EV_S_AbiscfConnectionSetup
message is effective frequency in BSC wireless
configuration.
TABLE 97 CONNECTION_SETUP_FOALLOC_F AIL
Failure
Reason Value
205
Reason
Description

process SP sends messages to RCP to request BTS
resource distribution; database distribution frame
offset distribution of data base fails during
connection setup on BTS side.
Settlement
Measures
Frame offset distribution failure is usually caused

by channel board failure. If this continues, please
reset channel board.
TABLE 98 CONNECTION_SETUP_CHANNELINP ARA_NOTEXIST
32
Failure
Reason
Value
204
Reason
Description
While distributing resources for multiple pilots during

connection setup or when cell phone requires handoff
of newly-added pilot in handoff process SP sends
messages to RCP to request BTS resource
distribution; there is no appointed frequency in
database records during connection setup on BTS
side.
Settlement
Measures
Check signaling tracing whether the parameter of

signaling EV_S_AbiscfConnectionSetup is 1; if it is,
then check if these fields the values in structure of
parameter tCurrentChannel
(ucSystemType,ucBandClass,wChannelNumber)are
correct.(note: in current system, ucSystemType and
ucBandClass are both 0, while wChannelNumber
refers to frequency)
TABLE 99 CONNECTION_SETUP_CARRIERALLOC_F AIL
Failure
Reason Value
203
Reason
Description

resource distribution; carrier distribution of
database fails during connection setup on BTS
side.
Settlement
Measures
Check if CHM and TRX operate normally; check if

CE and carrier are blocked; check if CE is
absolutely busy CE. If the former situation takes
place, it means board operation is abnormal. If the
former situation does not take place, continuous
observation after resetting CCM is suggested.
TABLE 100 CONNECTION_SETUP_LEGNUMBER_FROM_SP_ERROR
Failure
Reason
Value
202
Reason
Description

resource distribution; leg number contained in
connection requirement message sent by SP is
unlawful (bigger than 6)
Settlement
Measures
Check if ucLegNumber parameter of

EV_S_AbiscfConnectionSetup signaling during
signaling tracing is bigger than 6.
TABLE 101 CONNECTION_SETUP_CELLNUMBER_FROM_SP_ERROR
Failure
Reason
Value
201
Reason
Description

resource distribution:
1. Cell number in newly-built leg message
contained in connection requirement message sent
by SP is null (0 or a value bigger than 3)
2. Cell number in leg message of softer handoff
add in connection requirement message sent by SP
is null (0 or a value bigger than 3).
Settlement
Measures
Check if ucCellNumber value of number group

structure of parameter atSetupLegInfo of
EV_S_AbiscfConnectionSetup in signaling tracing is
0 or bigger than 3.
33
TABLE 102 CONNECTION_SETUP_GIVENCARRIER_NOUS ABLECE
Failure
Reason Value
221
Reason
Description
CE resource unavailable
1. Check channel board operation status to
confirm whether it operates normally;
Settlement
Measures
2. Check subscriber number under current channel

board to confirm whether it has reached maximum
subscriber quantity;
3. Confirm whether manual blocking is carried out
for the channel board.
TABLE 103 CONNECTION_SETUP_CRALLOCFAIL_CRINP AR ANOTEXIST
Failure
Reason Value
222
Reason
Description
carrier does not exist
Settlement
Measures
Check carrier configuration of calling cell, and

confirm synchronization on BSC and BTS side.
TABLE 104 CONNECTION_SETUP_CRALLOCFAIL_CHMTYPENOTM ATCH
Failure
Reason Value
223
Reason
Description
channel board types mismatch
Settlement
Measures
Channel board type of allocated distributed carrier

is not the same as channel board type in actual
configuration.
software problem that needs to be handled
through coordinating with BSSAP/SP.
TABLE 105 CONNECTION_SETUP_CRALLOCFAIL_CRISBEACON
Failure
Reason Value
224
Reason
Description
Carrier that is to be distributed is beacon pilot.
Settlement
Measures
34
1. In normal situation, mobile phone calls under

critical cell that has beacon pilot;
2. If there is no beacon pilot under current cell,
check carrier configuration to confirm whether it is
improperly configured.
TABLE 106 CONNECTION_SETUP_CRALLOCFAIL_CRISUNNORMAL
Failure
Reason Value
225
Reason
Description
carrier status is abnormal
Settlement
Measures
1. Check whether TRX operation status is normal;

2. Check whether manual blocking is carried out
on carrier.
TABLE 107 CONNECTION_SETUP_CRALLOCFAIL_NOUSABLECE
Failure
Reason Value
226
Reason
Description
CE resource unavailable
1. Check if channel board operation status is
normal;
Settlement
Measures
2. Check if the subscriber quantity under current

channel board has reached the maximum value.
3. Confirm whether manual blocking has been
carried out on the channel board.
TABLE 108 CONNECTION_SETUP_CRALLOCFAIL_CRISOVERLOAD
Failure
Reason Value
227
Reason
Description
Carrier is overloaded.
Settlement
Measures
1. Check subscriber quantity under carrier and

overloaded subscriber quantity in overload
parameter configuration interface to confirm
whether subscriber quantity under sector has
reached overload threshold;
2. Adjust overload threshold basing on actual
situation and network planning.
TABLE 109 CONNECTION_SETUP_CRALLOCFAIL_GETCELLALLCRFAILED
Failure
Reason Value
228
Reason
Description
Failure in accessing carrier configured in current

cell
Settlement
Measures
Check OMC configuration to confirm that carrier is

normally configured under cell and that
synchronization on BSC and BTS side has been
carried out.
35
TABLE 110
CONNECTION_SETUP_CR ALLOCFAIL_GETCURCELLALLPREFFAILED
Failure
Reason Value
229
Reason
Description
Failure in allocated carrier distribution
Settlement
Measures
Software problem that needs to be solved through

associating with SP.
TABLE 111
CONNECTION_SETUP_CR ALLOCFAIL_GETGIVENBANDCLASSCRFAILED
Failure
Reason Value
230
Reason
Description
failure in carrier distribution on allocated frequency

band
Settlement
Measures
Mobile phone and software problem that needs to

be solved through associating with SP.
T A B L E 1 1 2 H A N D O F F _ E X C E E D _ O N E _ P I L O T _ F AI L U R E
Failure
Reason Value
13
Reason
Description
While switching newly-added pilot, if resource

distribution failure occurs in more than one sector
and this switchover does not fail, final switchover
observation will submit the reason.
Possibilities for frequent failures are as follows:
1. Resource distribution failure resulted by
abnormal status of partial sectors. The method is
to check CE status using probe, and resetting
relevant CHM board can be considered;
Settlement
Measures
2. Partial messages lost because of inter-board

link problem. The solving measure is to reset
relevant boards (DOSDU, CCM and UIM where
failure sector is)
3. Inconsistent versions. The solving method is to
check whether the version of DOSDU, CCM and
CHM where failure sector are compatible;
4. Abnormal data configuration. The solving
method is to synchronize data on OMP and CCM
where failed sectors reside, or to check data
configuration and backtrack data.
36
T A B L E 1 1 3 H AN D O F F _ D R C _ S E T U P _ E R R O R
Failure
Reason
Value
12
Reason
Description
During handoff, if it is soft or half-soft handoff,

sending AbiscfSetDRCAndAckInfo and
AbiscfSetDRCLengthTransition message to channel
board to configure relevant parameters needs to be
done before sending TCA message or after
receiving TCC message and wait for response. If w
Result field in received Ack message is not 0 (0
means successful parameter configuration), handoff
failure of this reason will be resulted in.
1. Inconsistent versions. Solving method is to
check whether versions of DOSDU, CHM and UIM
are compatible.
Settlement
Measures
2. Check configured system parameters in OMC,

correctness of DRCLength value, DRCChannelGain
value, AckChanelGain value, DSCChannelGain value
and DRCThreshold value that correspond to
different leg number in DRC parameter list need to
be confirmed. If they are incorrect, data
configuration might be abnormal and backtracking
data should be considered.
T A B L E 1 1 4 H AN D O F F _ AD D L E G _ T I M E O U T
Failure
Reason Value
11
Reason
Description
During adding process of soft handoff or half-soft

handoff, newly-added legs information needs to be
announced to FSP; if FSP does not return
indication of successful leg adding, handoff failure
will occur.
Settlement
Measures
For frequent failures of this kind, internal

abnormality might occur in SP or TP module;
resetting DOSDU board is suggested.
T A B L E 1 1 5 H AN D O F F _ AT AC Q U I R E D _ T I M E O U T
Failure
Reason Value
10
Reason
Description
SP has sent TCA message to mobile phone and has

received MobileAcquired message, and ATAcquired
message needs to be sent to channel board to
change power control mode; if not all response
messages are collected when timer is timeout,
handoff failure of this reason occurs.
Settlement
Measures
Several possibilities for frequent failures are as

follows:
1. Inter-board link problem; the solving method is
to reset relevant boards(DOSDU, CHM, and UIM
37
Failure
Reason Value
10
etc);
2. Inconsistent versions; solving method is to
check versions of DOSDU, CHM, and UIM are
compatible.
T A B L E 1 1 6 H AN D O F F _ D R C _ S E T U P _ T I M E O U T
Failure
Reason
Value
Reason
Description
During handoff, if it is soft or half-soft handoff,

sending AbiscfSetDRCAndAck Info and
AbiscfSetDRCLengthTransition message to channel
board to configure relevant parameters needs to be
done before sending TCA message or after
receiving TCC message, and wait for response. If
not all Ack responses are collected before timer is
timeout, handoff failure of this reason occurs.
Possibilities for frequent failure are as follows:
1. Inter-board link problem; solving method is to
reset relevant boards (DOSDU, CHM, UIM etc);
Settlement
Measures

check if versions of DOSDU, CHM, and UIM are
compatible;
3. Check configured system parameters in OMC,
correctness of DRCLength value, DRCChannelGain
value, AckChanelGain value, DSCChannelGain value
and DRCThreshold value that correspond to
different leg number in DRC parameter list need to
be confirmed. If those are incorrect, data
configuration might be abnormal and backtracking
data should be considered.
T A B L E 1 1 7 H AN D O F F _ I N V AL I D _ P I L O T _ P N
Failure
Reason Value
Reason
Description
Receives RU message of mobile phone, but newlyadded pilot of certain request cannot be found in
neighboring message on base station side or
relevant message is incomplete. Then handoff
failure of this reason will be submitted to the pilot,
but handoff will unnecessarily fail.
1. No configuration on neighboring cell, the
solving method is to check configuration in OMC;
Settlement
Measures
2. Inconsistent BSC and BTS data, the solving

method is to synchronize data on OMP and CCM.
3. Abnormal data configuration, the solving
method is to check data configuration, synchronize
data or backtrack data.
38
T A B L E 1 1 8 H AN D O F F _ I N V AL I D _ R O U T E U P D AT E
Failure
Reason Value
Reason
Description
RU information of mobile phone has been received,

but abnormality occurs during processing, such as
sector quantity has passed the maximum carrier
quantity (8), or pilot quantity under certain carrier
passed the maximum pilot quantity (16), or
repeated pilot occurs under certain carrier etc;
these result in handoff failure of this reason.
Settlement
Measures
Possibly RU message submitted by mobile phone is

incorrect, which doesnt require handling.
T A B L E 1 1 9 H AN D O F F _ F O R W AR D D E S I R E D _ T I M E O U T
Failure
Reason Value
Reason
Description
During frequency-changing handoff, AN has sent

TCA message to mobile phone but without
receiving reverse capture message (MobileAcquired
message or TCC message) for all the time until
timer is timeout. This results in handoff failure.
Check log message on mobile phone side to
confirm whether mobile has received TCA message.
If it has not, problem might lay in transmission of
forward traffic channel packet. There are following
possibilities:
Settlement
Measures
1.
Inter-board link problem; the solving
method is to reset relevant boards (DOSDU, CHM
and UIMetc);
2.
Inconsistent versions. The solving method
is to check whether the version of DOSDU, CCM
and CHM are compatible.
If mobile phone has received TCA message and
confirmed its correctness, CHM reverse
demodulation might have problem; checking the
correctness of CHM chip configuration parameters
and data in DRC parameter list is suggested and
data backtracking should be considered.
39
TABLE 120 HANDOFF_ AD D_CH ANNELITEM_FAILURE
Failure
Reason Value
Reason
Description
During adding process of soft handoff or half-soft

handoff, adding channel table for new legs is
required; if Result field in response message
returned by ABPM is not 0 (0 means success),
handoff failure because of this reason might be
caused.
Settlement
Measures
1. Inconsistent versions; the solving method is to

check versions of DOSDU and ABPM are
compatible.
2. Abnormal data configuration; the solving
method is to check data configuration and
backtrack data.
TABLE 121 HANDOFF_RE SOURCE_ALLOC ATED_TIMEOUT
Failure
Reason Value
Reason
Description
When base station processes RU message,

resource distribution is needed for new-added
pilot, and sending resource distribution request to
RCP and awaiting response as well. If timer is
timeout without collecting all response messages,
the status of pilot under awaiting distribution
situation will be recorded as that macro.
There are several possibilities for frequent failures ,
such as :
reset relevant board (DOSDU, CCM and UIM etc);
Settlement
Measures

check whether the versions of DOSDU, CCM and
UIM are compatible;
3. Data is not synchronized or data configuration
is abnormal; solving method is to synchronize OMP
and CCM data, or check data configuration and
backtrack data.
40
TABLE 122 HANDOFF_RE SOURCE_ALLOC ATED_FAILURE
Failure
Reason Value
Reason
Description
Base station processes mobile phone RU message;

for half-soft handoff, if the first carrier distribution
fails, handoff failure of this reason will be
submitted. For non half-soft handoff and there is
new-added pilot, which needs resource
distribution, sending resource distribution request
and awaiting response, if return failure of response
message occurs, the status of corresponding pilot
will be recorded as that macro.
A few possibilities for frequent failure are as
follows:
Settlement
Measures

check if the versions of DOSDU, CCM and UIM are
compatible;
2. Data is not synchronized or data configuration is
abnormal; solving method is to synchronize OMP
and CCM data, or to check data configuration and
backtrack data.
T A B L E 1 2 3 H AN D O F F _ T C C _ T I M E O U T
Failure
Reason Value
Reason
Description
AN has sent TCA message to mobile phone, but

has not received TCC message, and timeout of TCC
waiting timer results in handoff failure.
Check log message on mobile phone side, confirm
whether mobile phone has received TCA message.
If not received, packet sending of forward traffic
channel might have problem. There are following
possibilities:
reset relevant board (DOSDU, CHM and UIM etc);
check if the versions of DOSDU, CHM and UIM are
compatible
Settlement
Measures
If mobile phone has received TCA message and has

checked correctness of message content, then:
1. For carrier-changing handoff, problem possibly
lies in CHM reverse demodulation; checking
correctness of CHM chip configuration parameters
and data in DRC parameter list of system
parameters and backtracking data is suggested;
2. For non carrier-changing handoff, problem
possibly lies in reverse media flow; the solving
method is to confirm whether CHM, DOSDU, ABPM
and DSM board operation is normal and their
versions are consistent; resetting these boards
may be considered.
41
42
Chapter
Reasons for Call Drop

The chapter explains the reasons and settlement measures for
call drop problems.
43
TABLE 124 CONNECTION_RELE ASE_SESSIONCONFIG_IDP_

CONFIG_F AIL
Failure
Reason Value
127
Description
If the negotiation for IDP protocol is failed, it will

cause connection release.
If the cause occurs in individual AT, it must be the
problem in AT processing.
Settlement
Measure
If the cause occurs in the large number of ATs, the

configuration data in OMC should be checked.
(check path: DO parameternon QoS parameter
radio protocol parameterIdle State Protocol
parameter)
TABLE 125
CONNECTION_RELE ASE_SESSIONCONFIG_FTCM AC_CONFIG_F AIL
Failure
Reason Value
126
Description
If the negotiation for FTCMAC protocol is failed, it

will cause connection release.
problem about AT processing.
Settlement
Measure

radio protocol parameterForward Traffic Channel
MAC Protocol parameter)
TABLE 126
CONNECTION_RELE ASE_SESSIONCONFIG_ AUTH_CONFIG_ F AIL
Failure
Reason Value
125
Description
If the negotiation for AUTH protocol is failed, it will

Settlement
Measure
44

radio protocol parameterAuthentication Protocol
parameter)
Chapter 3 Reasons for Call Drop
TABLE 127 CONNECTION_RELE ASE_SESSIONCONFIG_ ACM AC_

CONFIG_F AIL
Failure
Reason
Value
124
Explanation
If the negotiation for ACMAC protocol is failed, it will

configuration data in OMC should be checked. (check
path: DO parameternon QoS parameterradio
protocol parameterAccess Traffic Channel MAC
Protocol parameter)
Solution
TABLE 128 CONNECTION_RELE ASE_SESSIONCONFIG_TX_

CFGCOMPLETE_ TIMEOUT
Failure
Reason
Value
122
Explanation
The negotiation is failed because AN does not

transmit the UmfCfgComplete message at timer
timeout. This will cause connection release.
Generally, some protocols do not send out the
negotiation completion message. It is required to
analyze the detail reason according to the signaling
track or check DOSDU if abnormal probes are
reported.
Solution
TABLE 129 CONNECTION_RELE ASE_SESSIONCONFIG_SET_

CFGDONE_ FAILURE
Failure
Reason
Value
121
Explanation
Solution
After the negotiation for some protocol completed,

the negotiation completion message should be
transmitted. Negotiation is not accomplished until
SCM receives all indications. If the indication
transmission is failed, it will cause negotiation failure
and connection release.
Generally, some protocols do not send out the

indication of negotiation completion message. It is
required to analyze the detail reason according to
the signaling track or check DOSDU if abnormal
probes are reported.
45
TABLE 130 CONNECTION_RELE ASE_SESSIONCONFIG_ ATINITI ATED_

REQUEST_ CFG ATTR_TIMEOUT
Failure
Reason
Value
120
Explanati
on
When AT originates negotiation, if AT negotiation

request is still not received at the timeout of timer, it
Check log information in the mobile phone side and
make sure if it receives the information of
Configuration Start.
Solution
If not received, channel transmission for the forward

service will have errors possibly. Solution: check if
CHM, DOSDU, ABPM and DSM board run normally and
the versions are consistent. The boards can be reset.
If the mobile phone has received the message but does
not reply correctly, it can be considered to reset the
mobile phone.
TABLE 131 CONNECTION_RELE ASE_SESSIONCONFIG_RX_

CFGCOMPLETE_ TIMEOUT
46
Failure
Reason
Value
119
Explanation
In the process of negotiation, if AN is timeout waiting

for the message of UmrCfgComplete transmitted by
AT, it will cause connection release.
Solution
According to signaling track or log information, Check

if AT negotiation flow is correct. If error information
occurs, it can be considered to reset the mobile
phone.
TABLE 132 CONNECTION_RELE ASE_SESSIONCONFIG_RE ADY_

REQUEST_CFG ATTR_TIMEOUT
Failure
Reason
Value
118
Explanati
on
After connection setup, if the mobile phone or base

station does not need to negotiate, negotiation flow
will enter into the Ready state; At that time, if
negotiation request from the mobile phone is received,
SP will transmit the message of negotiation property
request for Av port and wait for the response; If the
response is timeout, it will cause connection release.
If the error occurs in a great deal, there may be the
following reasons:
1. The link problem from boards
Measures: reset the boards(DOCMPDOSDUUIM and
so on);
Solution
2. Versions difference
Measures: check if the versions of DOCMP and DOSDU
are compatible;
3. Data configuration abnormity
Measures: check data configuration and roll back data
TABLE 133 CONNECTION_RELE ASE_ATTRIBUTEOVERRIDE_TIMEOUT
Failure
Reason
Value
115
Explanation
After handoff, if RU negotiation parameter needs to

be updated according to the flow of
AttributeOverride, it should transmit request to the
mobile phone and wait for the response; if the
response is timeout, it will cause connection release.
Check if the Log information in the mobile phone side
receives the request of Override.
If the request is received but the content is wrong,
the reasons may be:
1. Data configuration abnormity
Solution
Measures: check data configuration and roll back

data.
2. SP module inside abnormity
Measures: suggest resetting DOSDU board. If the
mobile phone dose not receive Override request, it
will be doubted that the channel transmission for the
forward service has some error. Measure: check if
CHM, DOSDU, ABPM and DSM board run normally
and the versions are consistent. The boards can be
reset
47
TABLE 134 CONNECTION_RELE ASE_AT_INITI AL_SESSION_CLOSE
Failure
Reason Value
114
Explanation
When AN receives the SessionClose information

from the reverse servicechannel by mobile phone,
it will cause connection release.
Solution

problem about AT processing; If the cause occurs
in the large number of ATs, it is possible that the
base station transmits abnormal message and
contact with the ZTE local office to analyze further.
TABLE 135 CONNECTION_RELE ASE_TCC_TIMEOUT
Failure
Reason
Value
113
Explanation
TCC reception timeout in the process of handoff.

Handoff failure and the reason for connection release
will be reported.
Solution
Same as handoff failure for HANDOFF_TCC_TIMEOUT
TABLE 136 CONNECTION_RELE ASE_SP_ADD_CHANNELITEM_

F AILURE
Failure
Reason
Value
112
Explanation
In the process of handoff, if new legs need, it will be

necessary to increase channel table. If SP transmits
channel table unsuccessfully or waits for response
timeout for channel table increase, it will cause
handoff failure and connection release.
Solution
Same as handoff failure for

HANDOFF_ADD_CHANNELITEM_FAILURE
TABLE 137 CONNECTION_RELE ASE_AT_INITI ATE
48
Failure
Reason
Value
110
Explanation
connection release caused by AT
Solution
Normal
TABLE 138 CONNECTION_RELE ASE_SESSIONCONFIGUR ATION_

F AILURE
Failure
Reason
Value
109
Explanation
Session negotiation failure causes connection

release.
Solution

problem about AT processing; If the cause occurs in
the large number of ATs, the configuration data in
OMC should be checked. (check path: DO parameter
non QoS parameterradio protocol parameterAll
parameter)
TABLE 139 CONNECTION_RELE ASE_SESSIONCONFIGUR ATION_

SUCCESS
Failure
Reason
Value
108
Explanation
Session negotiation success and connection close
Solution
Normal
TABLE 140 CONNECTION_RELE ASE_H ANDOFF_FAILURE
Failure
Reason
Value
107
Explanation
Soft or softer handoff failure causes connection

release
Solution
Make single user signaling track to check the specific

failure reason for the Soft or softer handoff.
TABLE 141 CONNECTION_RELE ASE_AIR_LINK_LOST_TIMEOUT
Failure
Reason
Value
106
Explanation
After the link lost, the timer will wait for a period of
time. If the link does not recapture until timeout for
the timer, it will cause connection release.
Solution
Check if the air link is normal by the radio link state

information from the mobile phone side.
49
TABLE 142 CONNECTION_RELE ASE_RLP_RESET_ ACK_TIMEOUT
Failure
Reason
Value
105
Explanation
In the process of RLP reset, if AN is timeout waiting

for ResetAck/ResetComplete message from AT, AN
Take waiting for ResetAck as an example: check log
information in mobile phone and if mobile phone
receives Reset message from RLP.
Solution
If the message is not received, it indicates that the

forward media flow is abnormal. Measure: Check if
CHM, DOSDU, ABPM and DSM board run normally
and if their versions are identical. It is able to reset
the boards.
If mobile phones receive the ResetAck message but
not transmit it, it is necessary to check if the
message content is right.
If mobile phone has transmitted ResetAck message
but AN has not received, the reverse media flow may
have problem. Measures: Check if CHM, DOSDU,
ABPM and DSM board run normally and if their
versions are identical. It is able to reset the boards.
T A B L E 1 4 3 C O N N E C T I O N _ R E L E A S E _ S P _ S H AK E _ H A N D _ T I M E O U T
Failure
Reason
Value
104
Explanation
The timeout for SP handshake with BSSAP will cause

connection release.
If the error occurs in a great deal, the followings
may be the reasons:
1. The link problem from boards
Solution
Measures: reset the boards(DOCMPDOSDUUIM

and so o);
2. Versions difference
Measures: check if the versions of DOCMP and
DOSDU are compatible;
T A B L E 1 4 4 C O N N E C T I O N _ R E L E A S E _ S E M I H AN D O F F _ F A I L U R E
50
Failure
Reason
Value
103
Explanation
Semi-handoff failure causes connection release.
Solution
Make single user signaling track to check the specific

failure reason for the Soft or softer handoff.
TABLE 145 CONNECTION_RELE ASE_DORM ANCY_TIMEOUT
Failure
Reason
Value
102
Explanation
TP supplies a inactive timer to maintain each flow.

The inactive timer timeout causes connection
release.
Solution
Normal
TABLE 146 CONNECTION_RELE ASE_DRC_SETUP_F AILURE
Failure
Reason
Value
101
Explanation
In the process of handoff, before TCA message

transmission or after TCC message receipt, transmit
AbiscfSetDRCAndAckInfo and
AbiscfSetDRCLengthTransition to the channel board,
set up the relevant parameters and wait for
response. If it dose not receive all Ack responses
before timer timeout, or the field of wResult in the
Ack is not 0 (0 means parameter setup success), it
If the error occurs in a great deal, the followings
must be:
1.
The link problem from boards
Measure: reset the boards(DOCMPDOSDUUIM

and so on);
2.
Versions difference
Measure: check if the versions of DOCMP and

DOSDU are compatible;
Solution
3.
Check system parameters for OMC onfiguration.
Examine if the values of DRCLength,

DRCChannelGain, AckChanelGain, DSCChannelGain
and DRCThreshold are correct relevant to different
leg numbers; if not correct, data configuration may
be abnormal and reset data.
TABLE 147 CONNECTION_RELE ASE_GETP AR AFROM AUX_F AILURE
Failure
Reason
Value
505
Explanation
TP parameter capture failure from RSPAux module
Solution
Check if RSPAux process is normal; if this is multiflow application, examine if QoS parameter relevant
to it in OMC is right. For example, UserRank; each
Profile relevant to the rate, DelayBound and so on.
51
TABLE 148 CONNECTION_RELE ASE_CPUOVERLOADED
Failure
Reason Value
504
Explanation
TP default packet uses (SN) to set up the flow

adjuster; if this is failure, DOSDU will overload.
Solution
Examine the reason for CPU overload and inform

system maintenance persons to analyze. If users
are too many, increase resource boards for DOSDU
to share load.
TABLE 149 CONNECTION_RELE ASE_OPEN_DAT AFLOW_F AILURE
Failure
Reason Value
503
Explanation
TP default packet uses(SN or RN)to open Data Flow

unsuccessfully.
Solution
Examine RLP and demodulation parameters for AN.

If it is SN, examine parameter configuration for
UserRank; if it is RN, examine parameter
configuration for ZTEProfiled.
TABLE 150 CONNECTION_RELE ASE_CRE ATE_FS E_FAILURE
Failure
Reason
Value
502
Explanation
TP generates FSE unsuccessfully, which may be

caused by memory shortage or serious abnormity in
itself.
Solution
Rebuild to connect or reset DOSDU boards.
TABLE 151 CONNECTION_RELE ASE_NOT_ ALL_RESERV ATION_

OPENED
52
Failure
Reason
Value
501
Explanation
At the time of re-activation, part of or all Reservation

in Session, opens unsuccessfully.
Solution
Clean Session and rebuild it.
TABLE 152 CONNECTION_RELE ASE_FSP_SETARQMODE_F AILURE
Failure
Reason
Value
405
Explanation
FSP originates the flow for setup ARQ mode and

transmits the message to the target leg. But the
result for response is processing failure.
The main reason is possible that the status of
channel board driver is wrong.
Solution
Measures: Examine the channel board status. If a

large amount of release is caused by the reason,
reset the channel boards.
TABLE 153 CONNECTION_RELE ASE_FSP_SETARQMODE_TIMEOUT
Failure
Reason
Value
404
Explanation

transmits the message to the target leg. But in the
set time do not receive the leg response.
The reasons may be:
1. The message is delayed or lost by Abis link.
Measures: check Abis link and make sure it
unblocked.
2. CES discarded because of some reason does not
process.
Solution
Measures: Examine channel board status. If a

large amount of release is caused by the reason,
reset the channel boards.
TABLE 154 CONNECTION_RELE ASE_FSP_SETTRANSMISSIONMODE_

TIMEOUT
Failure
Reason
Value
403
Explanation

transmits the message to all legs in the activity set.
But do not receive the response for part of legs in
the set time.
The reasons may be:
Measure: check Abis link and make sure it
unblocked.
Solution

process.
Measure: examine channel board status. If a large
amount of release is caused by the reason, reset the
channel boards.
53
TABLE 155 CONNECTION_RELE ASE_FSP_SETTRANSMISSIONMODE_

F AILURE
Failure
Reason
Value
403
Explanation

transmits the message to all legs in the activity set.
But do not receive the response for part of legs in
the set time.
The reasons may be:
Measure: check Abis link and make sure it is
unblocked.
Solution
2. CES discarded because of some reason, and does

not process.
Measure: examine channel board status. If a
large amount of release is caused by the
reason, reset the channel boards.
TABLE 156 CONNECTION_RELE ASE_FSP_SHAKEH AND_TIMEOUT
Failure
Reason
Value
401
The reasons may be:
Measures: check Abis link and make sure it
unblocked
Solution

process.
Measures: examine channel board status. If a large
amount of release is caused by the reason, reset the
channel boards.
TABLE 157 CONNECTION_RELE ASE_A9PCFGOING_TO_DORMANT
54
Failure
Reason
Value
65
Explanation
PCF receives A9SetupA8 message and then sets up

A10 to enter into Dormant. After that, BSSAP will
receive the response for A9ReleaseA8Complete
message, including the reason value.
Solution
normal flow
TABLE 158
CONNECTION_RELE ASE_ A9_PDSNDENIED_UNKNOWN_PDSN_
ADDRESS
Failure
Reason
Value
63
Explanation
If the reason value for PDSN return is other PDSN

addresses recommended (namely the PDSN address
unknown), PCF will receive A9SetupA8 message and
then select PDSN to set up the request for A10. At
the time, if PSF adds the PDSN address
recommended unsuccessfully and has no other any
address, BSSAP will receive the response for
A9ReleaseA8Complete message, including the reason
value
In theory, it must meet the following conditions to
cause the reason value: the failure for PCF adding
PDSN address recommended and no other any PDSN
address available. So:
Solution
1. Check the configuration and number of PDSN.

2. Check if RP connection is available on PCF.
TABLE 159 CONNECTION_RELE ASE_A9_PDSNDENIED_

POORLYFORMED_ A11REQUEST
Failure
Reason
Value
62
Explanation
If the reason value for PDSN return is PDSN register

refuse-A11RegRequest code format error, PCF will
receive A9SetupA8 message and then select PDSN to
set up the request for A10. BSSAP will receive the
response for A9ReleaseA8Complete message,
including the reason value.
1. Check the IOS version for PDSN support actually.
Solution
2. Check the IOSMode field of PDSN configuration in

OMC and select the relevant version number for IOS.
TABLE 160 CONNECTION_RELE ASE_A9_PDSNDENIED_MOBILENODE_

F AILED_ AUTHENTICATION
Failure
Reason
Value
61
Explanati
on

refuse-PCF authentication failure, PCF will receive
A9SetupA8 message and then select PDSN to set up
the request for A10. BSSAP will receive the response
for A9ReleaseA8Complete message, including the
reason value.
Solution
Check if SPI confirmation and A10 address on SPCF are

the same with that on PDSN.
55
TABLE 161 CONNECTION_RELE ASE_A9_PDSNDENIED_

IDENTIFICATION_ MISM ATCH
Failure
Reason
Value
60
Explanation

refuse-timestamp unsuited, PCF will receive
reason value.
The reason: configuration timestamp check function
in the RP connection configuration and the difference
between PDSN response timestamp and PCF itself
timestamp is more than configuration threshold in
OMC. So,
Solution
1. If the difference between the two timestamps is

less than the maximal timestamp threshold for RP
connection configuration, configure a suitable time
stack threshold in RP connection configuration.
2. Or else, close timestamp check function in RP
connection configuration.
TABLE 162 CONNECTION_RELE ASE_A9_PDSNDENIED_RELE ASE_

INSUFFICIENT_RESOURCE
Failure
Reason
Value
59
Explanati
on

refuse-recourse shortage, PCF will receive A9SetupA8
message and then select PDSN to set up the request
for A10. BSSAP will receive the response for
value.
Solution
In the normal condition, PDSN side will restore

automatically for a period of time with the call traffic
drops.
T A B L E 1 6 3 C O N N E C T I O N _ R E L E A S E _ A 9 _ P D S N D E N I E D _ R E AS O N _
ADMINISTRATIVELY_PROHIBITED
56
Failure
Reason
Value
58
Explanati
on

refuse-management barring, PCF will receive
reason value.
Solution
Consult PDSN management persons and feedback log

message on PDSN.
UNSPECIFIED
Failure
Reason
Value
57
Explanation

refuse-the reason undetermined, PCF will receive
reason value.
Solution

message on PDSN.
VSE_ERROR
Failure
Reason
Value
56
Explanation

refuseno support for Vendor ID or CVSE data
unencoded, PCF will receive A9SetupA8 message and
then select PDSN to set up the request for A10.
BSSAP will receive the response for
value.
1. Check if IOS version for PDSN configuration in
OMC and actual IOS version supported by PDSN are
identical.
Solution
2. Consult PDSN management persons and feedback

log message on PDSN.
EVERSE_TUNNEL_UNAV AIL ABLE
Failure
Reason
Value
55
Explanati
on

refusereverse channel unavailable, PCF will receive
reason value.
Solution

message on PDSN.
57
TBIT_NOTSET
Failure
Reason
Value
54
Explanation

refusereverse channel controlled and no sign
location, PCF will receive A9SetupA8 message and
then select PDSN to set up the request for A10.
value.
Solution

message on PDSN.
TABLE 168 CONNECTION_RELE ASE_A9_PCFDENIED_EQUIPMENT_

F AILURE
Failure
Reason
Value
53
Explanation
Check IMSI and A9Indicators fields when PCF

receives A9SetupA8 message. If there is an error,
value
Solution
Check IMSI and A9Indicators fields from A9SetupA8

message.
TABLE 169 CONNECTION_RELE ASE_A9_PCFDENIED_PCF_

R E S O U R C E _ U N AV I A L A B L E
Failure
Reason
Value
Explanat
ion
Solution
58
52
If A9SetupA8 message for PCF receipt can not distribute

UPCF recourses, BSSAP will receive the response for
value for PCF refusePCF recourses unavailable.
1. Check if PCF configuration is abnormal.
2. Check if UPCF is normal or close.
TABLE 170 CONNECTION_RELE ASE_A9_PCFDENIED_PDSN_

R E S O U R C E _ U N AV A I L A B L E
Failure
Reason
Value
51
Explanat
ion
If PCF receives A9SetupA8, it will select a PDSN to

originate a request for A10 setup. If setup fails, BSSAP
will receive the response for A9ReleaseA8Complete
message, including the reason value for PCF refuse
PDSN resources unavailable. At the same time, PCF will
fill the release reason in PDSNCode field (in the case of
PDSNCode available)
In normal condition, if the RP link is unavailable, there
will be alarm on the SPCF board in order to check.
Solution
1. Check if the RP link is normal.

2. Check if PDSN run is normal.
TABLE 171 CONNECTION_RELE ASE_A9_PCFNORM AL_RELE ASE
Failure
Reason Value
50
Explanation
If PDSN causes release, PCF will transmit

A9DisconnectA8 to BSSAP, including the reason
value. At the same time, PCF will fill the release
reason for PDSN in PDSNCode field (in the case of
PDSNCode available)
Solution
normal flow
TABLE 172 CONNECTION_RELE ASE_SESSION_AN_CLOSED_ACCESS

_ AUTH_F AILURE
Failure
Reason Value
46
Explanation
Access authentication failure
Solution
Maybe AT has no number distribution.

Measures: assign number in the N AAA Server.
59
TABLE 173 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_

ACCESS_AUTH_TIMEOUT
Failure
Reason Value
45
Explanation
Access authentication timeout

It may be:
1. The link between OMC Server and AN-AAA
Server is blocked.
Measures: restore link.
Solution
2. Each server for AN-AAA Server does not start or

is abnormal.
Measures: reset servers.
3. A12 parameters have errors.
Measures: correct and synchronize

A 1 2 T R A N S M I T _ O T H E R _ R E AS O N
Failure
Reason
Value
44
Explana
tion
AAA authentication failure: A12 transmission ---- other

unknown reasons
Solutio
n
Combine abnormal probes with the access authentication

module to locate the problem.
TABLE 175 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_NO_

A12TR ANSMIT_ID
60
Failure
Reason Value
43
Explanation
AAA authentication failure: A12 transmission--UserID distribution failure
Solution
It is caused by A12Transmit module recourses

limited. Originate call again for a while.
TABLE 176
CONNECTION_RELE ASE_ ACCESS_AUTH_INV ALID_W AIT_SERVERRSP
_TIMEOUT
Failure
Reason
Value
42
Explanati
on
AAA authentication failure: AAA server response

timeout
Check configuration and connection for AAA server.
Check if AAA server and BSC are in the same physical
network. Make sure physical connection for IP network
port from AN_AAA ping IPCF to AN_AAA and IP
address from RPU protocol stack ping AN_AAA on the
AN side.
If IP of AN_AAA and IP of A12 port in IPCF are not the
same network section, configure the static router.
Solution
Check if AN_AAA binds authentication port 1812

correctly and safe association to A12 port is configured
on AN_AAA.
Check IPCF side configuration to make sure A12
function entry correct on the IPCF board.
If the above is no problem, reset IPCF board.

CLIENT_SHARESECRET_ERROR
Failure
Reason
Value
41
Explanati
on
AAA authentication failure: AAA authentication

password error
Solution
Check if the password shared for safe association on

AN_AAA is identical with that of A12 interface
parameter on OMC side. The share password in OMC
configuration should be ASCII format.

SUCCESS_BUT_MNID_INV ALID
Failure
Reason
Value
40
Explanati
on
AAA authentication failure: AAA server does not return

to the right MNID.
Solution
Make sure AT has distributed number in AAA server

and check if MNID in AAA server is correct.
61
TABLE 179 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_CLIENT

_OTHER_REASON
Failure
Reason
Value
39
Explanati
on
AAA authentication failure: other reasons
Solution
Combine abnormal probes with the access

authentication module to locate the problem.

CLIENT_ USERID_ERROR
Failure Reason
Value
38
Explanation
AAA authentication failure: user ID invalid
Solution
Code processing is abnormal. Originate call again

for a while or reset DOCMP.

AAACLIENT_ID
Failure
Reason Value
37
Explanation
AAA authentication failure: UserID unavailable
Solution
It is caused by AAAClient module resources limited.

Originate call again for a while.

CLIENT_DECODEPKT_FAIL
62
Failure
Reason
Value
36
Explanati
on
Decode failure for return information to AAA server
Solution
It is possible for profileID configuration property in

AN_AAA. Check if configuration property of AN_AAA is
right.

A12 ACCESSREQ_TIMEOUT
Failure
Reason
Value
33
Explanati
on

timeout
AN side.
Solution

on AN_AAA.
If the above is no problem, reset IPCF board.

CLIENT_ SOCKET_ERROR
Failure
Reason Value
32
Explanation
AAA authentication failure: AAA protocol stack

transmission failure
Solution
Check if IP address for A12 interface on IPCF of

OMC protocol stack is identical with A12 parameter
in the radio parameters.

ACCESS_AUTH_F AILURE
Failure
Reason Value
31
Explanation
AAA authentication failure: AAA refuse
Solution
Make sure AT has distributed number in AAA server

and check if user names and passwords in the AAA
server and AT are identical.
63
TABLE 186 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_LCP_

ESTABLISH_F AIL
Failure
Reason Value
30
Explanation
AAA authentication failure: LCP negotiation failure

between AN and AT.
Solution
Analyze track signaling and check the reason for

PPP negotiation failure.
T A B L E 1 8 7 C O N N E C T I O N _ R E L E A S E _ A C C E S S _ A U T H _ I N V A L I D _ C H AP _
CH ALLENGE _TIMEOUT
Failure
Reason
Value
29
Explanati
on
AAA authentication failure: CHAP authentication

timeout between AN and AT.
Solution
CHAP Protocol, Check if reverse link loss or other

situation to show no good radio environment occurs in
the current radio signal. Analyze track signaling and
check if mobile phone side responds to forward
negotiation message and mobile phone supports CHAP
protocol.
TABLE 188 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_W AIT_

CLIENTRSP_TIMEOUT
Failure
Reason
Value
27
Explanati
on

timeout
AN side.
Solution

on AN_AAA.
If the above is correct, reset IPCF board.
64

PPPSESSION_ID
Failure Reason
Value
26
Explanation
AAA authentication failure: instances unavailable to

negotiate PPP protocol with mobile phone in
PPPSection.
Solution
Originate call again for a while.
TABLE 190 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_PPP_

ESTABLISH_TIMEOUT
Failure
Reason
Value
25
Explanati
on
AAA authentication failure: PPP protocol timeout
Solution
Check if reverse link loss or other situation to show no

good radio environment occurs in the current radio
signal. Analyze track signaling and check PPP
negotiation property for mobile phone side and if
mobile phone responds to forward negotiation message

PPPSES_ WAIT_POWER_ON
Failure
Reason
Value
24
Explanati
on
AAA authentication failure: receive PPP setup

information on the stage of PPP start.
Wait for normal power-up for PPP session and call
again.
Solution
TABLE 192 CONNECTION_RELE ASE_ACCESS_AUTH_INV ALID_ AUTH_

ID_UNM ATCHED
Failure
Reason Value
23
Explanation
AAA authentication failure: Identification message

in the CHAP_Response which mobile phone
responds to is unmatched with CHAP_Challenge in
the base station.
Solution
Check if radio signal is normal and link transfer is

delayed too much.
65
TABLE 193 CONNECTION_RELE ASE_ACCESS_AUTH_SUCCESS_

AFTER_ SCP_OR_USERQOS_CH ANGE D
Failure
Reason
Value
22
Explanati
on
User grade changed or AAA authentication completed

actively after SCP completion cause connection release.
TABLE 194 CONNECTION_RELE ASE_A9_SH AKEHAND_TIMEOUT
Failure
Reason Value
21
Explanation
Handshake with PCF timeout release connection
Solution
The possible reason is that SPCF resets.
TABLE 195 CONNECTION_RELE ASE_RE_AUTH
Failure Reason
Value
20
Explanation
Connection release because AN side starts reauthentication.

The possible reason is OMC starts
Solution
re-authentication belongs to normal procedure,

solution: no solution.
TABLE 196 CONNECTION_RELE ASE_A9_ AUTH_FAILURE_OR_AT_

POWER_DOWN
Failure
Reason Value
19
Explanation
AT power-off releases connection
Solution
The possible reason is AT power off, belongs to

normal procedure.
TABLE 197 CONNECTION_RELE ASE_A9_UPD ATE _ A8_TIMER_EXPIRED
Failure
Reason Value
18
Explanation
SPCF replies with A9UPDATEA8 message timeout,

release connection.
1. IPCF and PDSN network connection problem,
solution: recover connection;
Solution
2. IPCF runs abnormally,

solution: reset IPCF;
3. PDSN runs abnormally,
solution: reset PDSN.
66
T A B L E 1 9 8 C O N N E C T I O N _ R E L E A S E _ A 9 _ R E L E AS E _ A 8 _
TIMER_EXPIRED
Failure
Reason Value
17
Explanation
SPCF replies with A9RELEASEA8 message timeout,

release connection.
Solution

TABLE 199 CONNECTION_RELE ASE_A9_DISCONNECT_A8_REQ
Failure Reason
Value
16
Explanation
PDSN sends release.
Solution
It belongs to normal procedure, no solution.
TABLE 200 CONNECTION_RELE ASE_A9SETUP A8_TIMER_EXPIRED
Failure
Reason Value
15
Explanation
SPCF replies with A9SETUPA8 message timeout

and releases connection.
Solution

TABLE 201 CONNECTION_RELE ASE_DORM ANT_HANDOFF_

OR_PDSN_NO_RES
Failure
Reason Value
14
Explanation
DORMANT handoff happens or PDSN has no

response
Solution
1. Dormant handoff, belongs to normal procedure,

solution: no;
2. PDSN runs abnormally, solution: reset PDS
67
TABLE 202 CONNECTION_RELE ASE_A9SETUP_RES_UNV ALI ABLE
Failure Reason
Value
13
Explanation
SPCF replies with A9CONNECTA8 to express

equipment failure.
Solution
It is possible that PDSN runs abnormally,

T A B L E 2 0 3 C O N N E C T I O N _ R E L E A S E _ A 9 _ M A S T E R _ T O _ S L AV E _
CH ANGEOVER
Failure
Reason Value
11
Explanation
Master and slave changeover release connection
Solution
It is possible that DOCMP master and slave

changeover, belongs to normal procedure
TABLE 204 CONNECTION_RELE ASE_SERVICE_TERMINATE
Failure
Reason Value
Explanation
In the case of connection exiting, AT sends packet

in access channel, AN side starts release actively.
Solution
It is possible that AT sends packet in access

channel, it is AT action.
T A B L E 2 0 5 C O N N E C T I O N _ R E L E A S E _ M AS T E R _ T O _ S L A V E _
CH ANGEOVER
Failure
Reason Value
Explanation
Master and slave changeover release connection
Solution
It is possibly because of DOCMP master and slave

changeover, which belongs to normal procedure,
no solution.
T A B L E 2 0 6 C O N N E C T I O N _ R E L E A S E _ R E A L L O C _ S D U _ F AI L U R E
68
Failure
Reason Value
Explanation
SDU resource can not be allocated in master and

slave changeover
Solution
It is possible that SDU configuration changes.
TABLE 207 CONNECTION_RELE ASE_CONNECTION_INTERNAL_ERROR
Failure
Reason Value
Explanation
BSSAP internal pointer mistake.
Solution
It is possible that DOCMP runs abnormally,

suggest resetting DOCMP.
TABLE 208 CONNECTION_RELE ASE_BSS AP_SH AKE_HAND_TIMEOUT
Failure
Reason Value
Explanation
BSSAP release connection shake hands timeout
Solution
It is possible that DOSDU runs abnormally,

suggest resetting DOSDU.
TABLE 209 CONNECTION_RELE ASE_SESSION_AN_TERMINATED
Failure
Reason Value
Explanation
Connection release caused by AN active cleaning

SESSION.
Solution
The reason is possible that MNID of AT is same as

another; suggest assigning number to this AT.
TABLE 210 CONNECTION_RELE ASE_SESSION_AN_CLOSED
Failure
Reason Value
Explanation
Re-authentication release connection

1. Access authentication is failed, solution: check
if AT has been assigned with number, if AN and AN
AAA Server connection is normal; if AN AAA Server
service is started; if A12 parameter is correct;
Solution
2. OMC sends cleaning session, belongs to normal

procedure.
TABLE 211 CONNECTION_RELE ASE_SP_SEND_ADDCH ANNELMSG_

F AILURE
Failure
Reason Value
159
Explanation
During handoff procedure, if new leg needs to add,

it is necessary to add channel table, if SP is failed
in sending adding channel table message, handoff
failure will happen and connection release of this
reason will be sent.
Solution
It is possible that SP module internal part has

problem. It is suggested to reset DOSDU board.
69
T A B L E 2 1 2 C O N N E C T I O N _ R E L E A S E _ M U L T I C AS T T I M E O U T
Failure
Reason Value
158
Explanation
During virtual handoff procedure, multi-broadcast

time will be too long and connection release of this
Solution
Check air link status according to the radio link

information of MS side
T A B L E 2 1 3 C O N N E C T I O N _ R E L E A S E _ S E M I H AN D O F F _ F A I L U R E _
FORW ARDDESIREDTO
Failure
Reason
Value
157
Explanation
During change frequency handoff, reverse

acquisition timeout leads to handoff failure.
Connection release of this reason will be reported.
Solution
The same as
HANDOFF_FORWARDDESIRED_TIMEOUT
ACTIVESETEMPTY
Failure
Reason Value
156
Explanation
During handoff procedure, after resource

allocation, if the expected active set is empty, then
handoff and connection release is sent.
Solution

problem, suggest resetting DOSDU board.
RESOURCEALLOC
70
Failure
Reason
Value
155
Explanation
During change frequency handoff, if frequency

allocation is failed, handoff failure will happen and
connection release of this reason will be sent.
Solution
The same as
HANDOFF_RESOURCE_ALLOCATED_FAILURE
AT ACQUIRE DTO
Failure
Reason Value
154
Explanation
During change frequency handoff, BTS need to

reacquire MS, when SP receives reverse acquisition
message, it is necessary to send AbiscfATAcquired
message to CHM board to request change power
control mode and wait for reply, before timer
expires. If all reply still not be received, handoff
failure will happen and connection will be released.
If this problem happens frequently, there are
1. Boards link problem, reset the related boards
(DOSDU, CHM, UIM);
Solution
2. Version is not consistent, check DOSDUCHM

UIM version;
TABLE 217 CONNECTION_RELE ASE_AT ACQUIRE D ACK_TIMEOUT
Failure
Reason Value
153
Explanation
When ATAcquired timer expires and it is not in

change frequency handoff, connection release will
happen.
(DOSDU, CHM, UIM);
Solution
2. Version is not consistent, check DOSDUCHM

UIM version;
TABLE 218 CONNECTION_RELE ASE_ADDLEGFORHO_TIMEOUT
Failure
Reason Value
152
Explanation
In handoff, if new leg needs to add, SP sends add

leg message to FSP and waits for reply, if
successful add reply is always not received,
handoff will be failed and connection is released.
Solution

71
TABLE 219 CONNECTION_RELE ASE_NEEDTOUPDATE_TOKEN
Failure
Reason
Value
151
When the following condition is satisfied, it is
necessary to start connection release and new call,
and update the flow in control channel:
Explanation
1. During handoff new added PN has cell which is

configured in 5500 CHM board, suppose this PN is
PNx;
2. PILOTCOMPARE_FOR_PERSEAONALITY
CHANG..PNx compares with the strongest PN in
active set; its value is
PILOTCOMPARE_FOR_PERSEAONALITYCHANGE
lower than that.
Solution
Normal processing
TABLE 220 CONNECTION_RELE ASE_UPDATE_RE SERV ATION_

F AILURE
Failure Reason
Value
150
Explanation
AT requests reserved resource is failed.
Solution
AN resource is not enough and tries again later.
TABLE 221 CONNECTION_RELE ASE_ GETBSCCHITEM_TIMEOUT
Failure
Reason Value
149
Explanation
During handoff procedure, if one leg needs to be

added, SP needs to send AvrBSCChItemRequired
message to BSSAP and request to acquire the
information of adding channel table, if the reply is
not received, handoff failure will happen and
connection will be released.
Solution

(DOCMP, DOSDU, UIM);
2. Version is not consistent, check DOCMP, DOSDU
version;
3. Data configuration position is abnormal, check
data configuration and recover data.
72
TABLE 222
CONNECTION_RELE ASE_NEIGHBORLISTUPDATE _TIMEOUT
Failure
Reason Value
148
Explanation
After SP sends handoff completion message to

BSSAP, it is necessary to set timer to wait for
BSSAP to send neighbor list update message to
SP, if timer expires, this message still not be
received, handoff will be failed and connection is
released.
(DOCMP, DOSDU, UIM);
Solution
2. Version is not consistent, check DOCMP,

DOSDU version;
data configuration and recover data.
TABLE 223 CONNECTION_RELE ASE_FINDSERVINGLEG_F AILURE
Failure
Reason Value
147
Explanation
During virtual handoff, it is necessary to find

current service leg. If the searching is failed,
Solution

TABLE 224 CONNECTION_RELE ASE_SENDUMFTCA_ERROR
Failure
Reason Value
146
Explanation
During handoff, TCA message for MS is failed and

handoff will be failed, connection release of this
Solution

73
TABLE 225 CONNECTION_RELE ASE_BSCCHITEMREQ ACK_ERROR
Failure
Reason Value
145
Explanation
During handoff procedure, if it is necessary to add

leg, SP needs to send AvrBSCChItemRequired
message to BSSAP and request to acquire the
information of adding channel table, if the
parameter of the reply message is wrong, this will
lead to handoff failure and connection release of
this reason will be released.
1. Version is not consistent, check DOCMP, DOSDU
version;
Solution

data configuration and recover data;
3. BSSAP module internal part is abnormal, reset
DOCMP board.
TABLE 226 CONNECTION_RELE ASE_SESSIONCONFIG_KEP_

SKEYLEN_ CONFIG_F AIL
Failure
Reason Value
144
Explanation
During DH-Key negotiation, negotiation key length

is failed and negotiation is failed, connection
release of this reason will be sent.
Only some MS has this problem , it is possible that
MS has internal problem, suggest to reset MS;
If many MS has this problem:
1. It is necessary to check OMC configuration data.
( check route: DO parameter>Non-QoS
parameter>radio protocol parameter>DH-Key
Exchange Protocol parameter)
Solution
2. It is possible that SP module has internal

TABLE 227 CONNECTION_RELE ASE_SESSIONCONFIG_KEP_SEND_

ANKEYCOMPLETE_FAIL
74
Failure
Reason
Value
140
Explanati
on
During key exchange procedure, sending

UmfANKeyComplete message is failed and connection
Solution
It is possible that SP module has some internal

TABLE 228 CONNECTION_RELE ASE_SESSIONCONFIG_KEP_SEND_

KEYREQUEST_F AIL
Failure
Reason Value
139
Explanation
During key exchange procedure, sending

UmfKeyRequest message is failed and connection
Solution
It is possible that SP module internal mistake,

suggest resetting DOSDU board.
TABLE 229 CONNECTION_RELE ASE_SESSIONCONFIG_KEP_ST ART_

T ASK_F AIL
Failure
Reason Value
138
Explanation
During key exchange procedure, AN Session Key

calculation mission is failed and connection release
of this reason will be sent.
Solution
It is possible that SP module has some internal

problem. Suggest resetting DOSDU board.
TABLE 230 CONNECTION_RELE ASE_SESSIONCONFIG_KEP_REV_

KEYRESPONSE_DUR_COMPUTEKEY
Failure
Reason
Value
137
Explanati
on
During key calculation procedure of

AN, if AN received UmrKeyResponse message, it is
thought procedure mistake and connection release of
this reason will be sent.
Only some MS has this problem , it is possible that MS
has internal problem, suggest to reset MS;
Solution
If many MSs have this problem, it is possible that SP

module has internal problem, suggest resetting DOSDU
board.

ATKEYCOMPLETE_RES AULT_F AIL
Failure
Reason
Value
136
Explanati
on
During key exchange procedure, receive

ATKeyComplete message, but Result field is not 0 (0
means successful), key exchange is failed and
Solution
The possible reason is AT side and BTS side time is not

consistent and key value calculation is not consistent,
suggest to check BTS side time.
75

ATKEYCOMPLETE_TRANSID_NOM ATCH
Failure
Reason
Value
135
Explanati
on
During key exchange procedure, inside the received

message ATKeyComplete, TransactionID is different
from TransactionID of ANKeyComplete message, key
exchange is failed and connection release of this
Only some MS has this problem , it is possible that MS
has internal problem, suggest to reset MS;
Solution
If many MSs have this problem, it is possible that SP

module has internal problem. Suggest resetting
DOSDU board.
TABLE 233 CONNECTION_RELE ASE_SESSIONCONFIG_STR_

CONFIG_F AIL
Failure
Reason Value
133
Explanation
Flow wire relation negotiation is failed, it will lead

to connection release of this reason
Solution
Related parameter is not configured in OMC, it is

necessary to start single user signal tracing.
TABLE 234 CONNECTION_RELE ASE_SESSIONCONFIG_SMP_

CONFIG_F AIL
Failure
Reason Value
132
Explanation
SMP protocol negotiation is failed, it will lead to

connection release of this reason
Some AT has this problem, maybe it is AT
processing problem;
Solution
76
Many ATs have this problem, it is necessary to

check OMC configuration data. ( check route: DO
parameter>Non-QoS parameter>radio protocol
parameter>Session Management Protocol
parameter)
TABLE 235 CONNECTION_RELE ASE_SESSIONCONFIG_SCP_

CONFIG_F AIL
Failure
Reason Value
131
Explanation
SCP protocol negotiation is failed, it will lead to

connection release of this reason
processing problem;
Many AT have this problem, it is necessary to
parameter>Session Configuration Protocol
parameter)
Solution
TABLE 236 CONNECTION_RELE ASE_SESSIONCONFIG_RTCMAC_

CONFIG_F AIL
Failure
Reason Value
130
Explanation
RTCMAC protocol negotiation is failed; it will lead

to connection release of this reason.
processing problem;
Many AT have this problem, it is necessary to
check OMC configuration data. (Check route: DO
parameter>Default Reverse Traffic Channel MAC
Protocol parameter and Subtype 3 RTCMAC QoS
Independent Parameters parameter).
Solution
T A B L E 2 3 7 C O N N E C T I O N _ R E L E A S E _ S E S S I O N C O N F I G _ P AP _
CONFIG_F AIL
Failure
Reason Value
129
Explanation
PAP negotiation failure can lead to connection

release of this reason.
If AT meets this problem, maybe it is AT
processing problem
Solution
If many ATs meet this problem, check OMC

configuration data. (check route: DO
parameter>Default Packet Application Protocol
parameter)
77
TABLE 238 CONNECTION_RELE ASE_SESSIONCONFIG_RUP_

CONFIG_F AIL
Failure
Reason Value
128
Explanation
RUP negotiation failure can lead to connection

release of this reason.
If AT meets this problem, maybe it is AT
processing problem.
Solution
If many ATs meet this problem, check OMC

configuration data. (check OMC cell handoff
configuration data)

SIGCOMP_ KEYCOMP_TIMEOUT
Failure
Reason
Value
141
Explanation
During key exchange procedure of negotiation, if AN

does not send ANKeyComplete message before
timer TKEPKeyCompAT expires, it is thought that
key exchange procedure is failed and negotiation is
failed, the connection release will be sent.
Solution
It is possible that AN internal key exchange

parameter calculation time is too long, consider
optimization.

KEYRESPONSE_TIMEOUT
78
Failure
Reason Value
142
Explanation
During key exchange procedure of negotiation,

after AN send KeyReRequest message to AT,
before timer TKEPANResponse timeout, if AN still
not receive KeyResponse message from AT, it is
thought that key exchange procedure is failed and
negotiation is failed, the connection release is sent.
Solution
It is possible that AT has problem, suggest

resetting AT.
TABLE 241 CONNECTION_RELE ASE_SESSIONCONFIG_KEP_SESSION_

KEYLEN_ERROR
Failure
Reason Value
143
Explanation
During negotiation, before starting key exchange

procedure, if Keylength of the negotiation result
does not equal to 768 or 1024 defined by protocol,
key exchange procedure can not be started and
negation will be failed. The connection release of
this reason will be sent.
If this error happens frequently, the following
reasons are possible:
1. Negotiation configuration parameter is wrong,
parameter>Non-Qos parameter>radio protocol
parameter>Key Exchange Protocol parameter);
Solution
2. SP module internal problem, change DOSDU

board.
TABLE 242 CONNECTION_RELE ASE_UPDATERESERV ATION_TIMEOUT
Failure
Reason Value
145
Explanation
While establishing and updating multiple flows, it is

necessary to send AbiscfUpdateReservation
message to RCP to update Abis port bandwidth and
set timer to wait for reply, if timer expires and all
reply is still not received, connection release of this
If this error happens frequently, the following
reasons are possible:
1. Board link problem, reset DOSDU, CCM boards;
Solution
2. Version is not consistent, check DOSDU, CCM

board version;
3. BTS resource is not enough, try again later.
TABLE 243 CONNECTION_RELE ASE_RCP_BSCIP_ASSIGNMENT_

F AILURE
Failure
Reason Value
205
Explanation
After RCP reply with new leg successful

establishment to SP, it will wait for
EV_S_AbiscfBSCIPAssignment message of SP and
adds DSM channel table. If this message of SP is
not received or adding channel table is failed, this
service observation failure reason will be reported.
Solution
If this phenomenon happens frequently, check

DSM board alarm, according to alarm information
decide whether to reset.
79
TABLE 244 CONNECTION_RELE ASE_RCP_ADD_CH ANNELITEM_

F AILURE
Failure
Reason Value
203
If MS requests to remove one active PN in handoff,
SP will send message to RCP and request to release
BTS resource:
Explanation
1. DSM returns failure when BTS side add channel

table;
2. DSM returns timeout when BTS side add
channel table;
Solution
Check if DSM board is normal, if this phenomenon

happens frequently, suggest resetting DSM board
and observe.
TABLE 245 CONNECTION_RELE ASE_RCP_OVERLO ADCONTROL
Failure
Reason
Value
202
Explanation
During this user connection, RCP finds user overload

while processing new connection, and then release
this user according to user overload re-movement
principle.
Solution
Confirm if it is overloaded currently and overload

switch has been started, overload principle is
configured as inactive high byte
(INACTIVITY_HIGHBYTE_OVERLOAD_CONTROL_MET
HOD), this phenomenon is normal.
TABLE 246 CONNECTION_RELE ASE_RCP_SHAKE_H AND_TIMEOUT
80
Failure
Reason
Value
201
Explanation
During connection procedure, RCP and SP shake

hands timer expires. RCP starts connection release
request.
Solution
Check if there is EV_S_AbiscfShakehand signal

inside 46 seconds before sending release request
signal EV_S_AbiscrConnectionReleaseRequest in
signal tracing, if there is, and the parameter
wCallRefId in these two signals are same, and then
if Abis link is normal. Another possibility is SP has
released call, but does not release RCP, it is
necessary for SP and RCP to analyze together.
Chapter
Release Failure
This chapter explains release failure error messages and
provides solutions to solve the problem.
81
TABLE 247 RELE ASE_F AILURE_EXCEED_ONE_PILOT_F AILURE
Failure
Reason Value
Explanation
During handoff drop after receiving release order,

SP sends AbiscConnectionRelease to RCP and
request to release leg information, in some replay
messages, release result is non-0 value
(0:successful)
There are two possibilities, If this failure happens
frequently:
Solution
1. Version is not consistent, check DOSDU, CCM

version;
2. SP sends wrong release message, reset DOSDU
board.
TABLE 248 RELE ASE_F AILURE_RCP_TIMEOUT
Failure
Reason Value
Explanation
During handoff drop or after receive release order,

SP sends AbiscConnectionRelease to RCP and
request to release leg resource. If no reply, the leg
which will be released inside this message will be
set to this macro, this timeout will not affect
release procedure.
The possible reasons:
Solution
1. Link problem between boards leads to

information loss, solution: rest boards: DOSDU
CCMUIM;
2. Version is not consistent, solution: check
DOSDU, CCM version;
3. SP sends wrong release message, solution:
reset DOSDU board.
TABLE 249 RELE ASE_F AILURE_AT_RESPONSE_CONNECTIONCLOSE_

TIMEOUT
82
Failure
Reason Value
Explanation
After send release order for some BTS side

reasons, AN will send closed air link message to
MS and wait for reply, if MS does not reply until
timeout, this phenomenon will be recorded as
release failure. This timeout will not affect release
procedure.
Solution
The possible reason is that MS released in

advance, no need for processing.
Chapter 4 Release Failure
TABLE 250 RELE ASE_F AILURE_CELLNUMBER_FROM_SP_ERROR
Failure
Reason Value
101
If MS requests to remove one active PN, SP will
send message to RCP and request to release BTS
resource:
Explanation
1. The leg inside the release leg information

carried by connection release message sent by SP
does not exist;
2. The cell inside the release leg information
carried by connection release message sent by SP
does not exist;
Check if the ucLegNo, ucCellNumber, aucCellId
value of parameter atReleaseLegInfo inside signal
EV_S_AbiscfConnectionRelease is correct.
Solution
TABLE 251 RELE ASE_F AILURE_LEGNUMBER_FROM_SP_ERROR
Failure
Reason Value
102
Explanation

resource, inside request connection release
message, the number of released leg is illegal.
Solution
Check if the parameter ucLegNumber of

EV_S_AbiscfConnectionRelease is more than 6.
More than 6 means it is one illegal value.
TABLE 252 RELE ASE_F AILURE_RELFWDCE_FAIL
Failure
Reason Value
103
Explanation

resource. During resource release, database is
failed in deleting CE.
Solution
If it happens frequently, suggest resetting CCM and

observe.
TABLE 253 RELE ASE_F AILURE_FWDCE_ISNOTEXIST
Failure
Reason Value
104
Explanation

resource, during resource release, database can not
find assigned CE.
Solution
If it happens frequently, suggest reset CCM and

observe.
83
TABLE 254 RELE ASE_F AILURE_RELBTSIP_FAIL
Failure
Reason Value
107
Explanation

resource, during resource release, database is
failed in release DSM channel table.
Solution
Check if Abis link is normal, if this phenomenon

always happens, suggest resetting DSM board.
TABLE 255 RELE ASE_F AILURE_MODIFYC ARRIERUSER_FAIL
Failure
Reason Value
108
Explanation

resource, during resource release, database is
failed in deleting user.
Solution
Check if Abis link is normal
TABLE 256 RELE ASE_F AILURE_CES_CONNECTION_

RELE ASE_TIMEOUT
Failure
Reason Value
109
Explanation
If MS requests to remove one active PN in handoff,

SP will send message to RCP and request to release
BTS resource, during BTS side connection and
release, CES connection and timeout.
Solution
Check if there is EV_S_AmrConnectionReleaseAck

(or EV_S_AmrSofterAddAck) in signal tracing of
connection establishment, if no, that means CES
did not respond. This leads to release timeout.
TABLE 257 RELE ASE_F AILURE_CES_SOFTER_HANDOFF_

DROP_TIMEOUT
84
Failure
Reason
Value
110
Explanation
If MS requests to handoff drop one active PN, SP

will send message to RCP to request for softer
handoff drop and release BTS resource, during BTS
softer handoff drop, CES softer handoff drop timer
expires.
Solution
Check if there is EV_C_S_AmrSofterDropAck

corresponding to call release, if no, that means CES
does not reply timeout, if it always can be seen,
suggest resetting CHM and observe.
Tables
Table 1 Chapter Summary ...................................................i
Table 2 Typographical Conventions ...................................... ii
Table 3 Mouse Operation Conventions .................................. ii
Table 4 CONNECTION_SETUP_AVBSCCHITEMREQ_TIMEOUT....2
Table 5 CONNECTION_SETUP_SETDRCLENTRANS_FAILURE.....2
Table 6 CONNECTION_SETUP_SETDRCANDACKINFO_FAILURE .3
Table 7 CONNECTION_SETUP_ATACQUIRED_TIMEOUT ...........3
Table 8 CONNECTION_SETUP_AVF_BSCCHITEMREQACK_
PARA_ERROR.....................................................................4
Table 9 CONNECTION_SETUP_RCP_TIMEOUT ........................4
Table 10 CONNECTION_SETUP_ABNORMAL_RELEASE.............5
Table 11 CONNECTION_SETUP_TCC_TIMEOUT_WAITING_TCC_
COMING............................................................................5
Table 12 CONNECTION_SETUP_AT_TERMINATED ...................6
Table 13 CONNECTION_SETUP_SDU_OVERLOAD ...................6
Table 14 CONNECTION_SETUP_SEND_TCA_FAILURE ..............6
Table 15 CONNECTION_SETUP_EXCEED_ONE_PILOT_FAILURE 7
Table 16
CONNECTION_SETUP_RCP_ADD_CHANNELITEM_FAILURE........7
Table 17
CONNECTION_SETUP_AVF_NEIGHBORLIST_PARA_ERROR .......8
Table 18 CONNECTION_SETUP_DRCANDACKINFO_TIMEOUT ...8
Table 19 CONNECTION_SETUP_CARRIER_ALLOCATE_TIMEOUT 9
Table 20 CONNECTION_SETUP_CARRIER_ALLOCATE_PARA_
ERROR..............................................................................9
Table 21 CONNECTION_SETUP_ALLOCATE_CARRIER_ID_ERROR
.......................................................................................9
Table 22 CONNECTION_SETUP_CARRIER_ALLOCATE_FAILURE
..................................................................................... 10
Table 23 CONNECTION_SETUP_PILOTS_NUMBER_ERROR ..... 10
Table 24 CONNECTION_SETUP_INVALID_PILOT_PN ............. 10
Table 25 CONNECTION_SETUP_CELL_NUMBER_ERROR......... 11
85
Table 26 CONNECTION_SETUP_BTS_NUMBER_ERROR .......... 11

Table 27 CONNECTION_SETUP_PILOT_INCREMENT_ERROR... 11
Table 28
CONNECTION_SETUP_MAX_SOFTHANDOFF_NUM_ERROR ...... 11
Table 29 CONNECTION_SETUP_MOBILEACQUIRED_
FORWARDDESIRED _TIMEOUT_FLOWCTRL_RECV ................. 12
Table 30 CONNECTION_SETUP_FORWARDDESIRED_
TIMEOUT_FLOWCTRL_RECV............................................... 12
Table 31 CONNECTION_SETUP_MOBILEACQUIRED_TIMEOUT 12
Table 32 CONNECTION_SETUP_NEIHBOURLIST_TIMEOUT..... 13
Table 33 CONNECTION_SETUP_NO_PILOT_IN_LAST_
ROUTERUPDATE ............................................................... 13
Table 34 CONNECTION_SETUP_ADD_CHANNELITEM_TIMEOUT
..................................................................................... 13
Table 35 CONNECTION_SETUP_ADD_CHANNELITEM_FAILURE14
Table 36 CONNECTION_SETUP_ACTIVATE_TP_FAILURE ........ 14
Table 37 CONNECTION_SETUP_TCA_ENCODE_FAILURE ........ 14
Table 38 CONNECTION_SETUP_CARRIER_ALLOCATE_ERROR. 14
Table 39 CONNECTION_SETUP_INVALID_ABIS_
BANDWIDTH_DISTRIBUTED............................................... 15
Table 40 CONNECTION_SETUP_SDU_OVERLOADED ............. 15
Table 41 CONNECTION_SETUP_CONNECTIONSETUP_TIMEOUT
..................................................................................... 15
Table 42 CONNECTION_SETUP_INVALID_RSP_PID............... 15
Table 43 CONNECTION_SETUP_INVALID_PPPSESSION_PID... 15
Table 44 CONNECTION_SETUP_INVALID_BSSAP_PID ........... 16
Table 45 CONNECTION_SETUP_INVALID_DBS_CONFIG ........ 16
Table 46 CONNECTION_SETUP_INVALID_INFO_UPDATE_POLICY
..................................................................................... 16
Table 47 CONNECTION_SETUP_INVALID_DRCACK_INFO....... 16
Table 48
CONNECTION_SETUP_INVALID_LOCATION_PARAMETER........ 16
Table 49
CONNECTION_SETUP_INVALID_MAX_SOFTHANDOFF_NUM .... 17
Table 50 CONNECTION_SETUP_INVALID_CELL_INFO............ 17
Table 51 CONNECTION_SETUP_INVALID_RU ....................... 17
Table 52 CONNECTION_SETUP_INVALID_CELLID ................. 17
Table 53 CONNECTION_SETUP_INVALID_SESSION_INFO...... 17
Table 54 CONNECTION_SETUP_INVALID_SDU ..................... 18
Table 55 CONNECTION_SETUP_INVALID_CALL_PARAMETER.. 18
86
Tables
Table 56 CONNECTION_SETUP_INVALID_AT ....................... 18

Table 57 CONNECTION_SETUP_NETWORK_BUSY ................. 18
Table 58 CONNECTION_SETUP_AMR_PARA_ERROR .............. 19
Table 59 CONNECTION_SETUP_CES_SOFTER_HANDOFF_
ADD_TIMEOUT ................................................................. 19
Table 60
CONNECTION_SETUP_CES_CONNECTION_SETUP_TIMEOUT ... 19
Table 61 CONNECTION_SETUP_SECTOR_USER_OVERLOAD ... 20
Table 62
CONNECTION_SETUP_SECTOR_OVERLOAD_NOT_FIND_BUMP_U
SER ................................................................................ 20
Table 63 CONNECTION_SETUP_CCM_CPU_OVERLOAD .......... 20
Table 64 CONNECTION_SETUP_CELLINPARA_NOTEXIST ....... 21
Table 65 CONNECTION_SETUP_MODIFYCARRIERUSER_FAIL.. 21
Table 66 CONNECTION_SETUP_GETDSMIP_FAIL .................. 21
Table 67 CONNECTION_SETUP_GETBSCIP_FAIL................... 22
Table 68 CONNECTION_SETUP_BTSIPALLOC_FAIL ............... 22
Table 69 CONNECTION_SETUP_CARRIERINPARA_NOTEXIST.. 22
Table 70 CONNECTION_SETUP_FOALLOC_FAIL .................... 23
Table 71 CONNECTION_SETUP_CHANNELINPARA_NOTEXIST . 23
Table 72 CONNECTION_SETUP_CARRIERALLOC_FAIL ........... 23
Table 73 CONNECTION_SETUP_LEGNUMBER_FROM_SP_ERROR
..................................................................................... 24
Table 74 CONNECTION_SETUP_CELLNUMBER_FROM_SP_ERROR
..................................................................................... 24
Table 75 CONNECTION_SETUP_GIVENCARRIER_NOUSABLECE
..................................................................................... 24
Table 76 CONNECTION_SETUP_CrAllocFail_CrInParaNotExist . 25
Table 77 CONNECTION_SETUP_CrAllocFail_CHMTypeNotMatch
..................................................................................... 25
Table 78 CONNECTION_SETUP_CrAllocFail_CrIsBeacon ......... 25
Table 79 CONNECTION_SETUP_CrAllocFail_CrIsUnNormal ..... 25
Table 80 CONNECTION_SETUP_CrAllocFail_NoUsableCE ........ 25
Table 81 CONNECTION_SETUP_CrAllocFail_CrIsOverload ...... 26
Table 82 CONNECTION_SETUP_CrAllocFail_GetCellAllCrFailed 26
Table 83 CONNECTION_SETUP_CrAllocFail_
GetCurCellAllPrefFailed ...................................................... 26
Table 84 CONNECTION_SETUP_CrAllocFail_
GetGivenBandClassCRFailed............................................... 26
Table 85 CONNECTION_SETUP_AMR_PARA_ERROR .............. 28
87
Table 86
CONNECTION_SETUP_CES_SOFTER_HANDOFF_ADD_TIMEOUT
..................................................................................... 28
Table 87
CONNECTION_SETUP_CES_CONNECTION_SETUP_TIMEOUT ... 29
Table 88 CONNECTION_SETUP_SECTOR_USER_OVERLOAD ... 29
Table 89
CONNECTION_SETUP_SECTOR_OVERLOAD_NOT_FIND_
BUMP_USER .................................................................... 29
Table 90 CONNECTION_SETUP_CCM_CPU_OVERLOAD .......... 30
Table 91 CONNECTION_SETUP_CELLINPARA_NOTEXIST ....... 30
Table 92 CONNECTION_SETUP_MODIFYCARRIERUSER_FAIL.. 30
Table 93 CONNECTION_SETUP_GETDSMIP_FAIL .................. 31
Table 94 CONNECTION_SETUP_GETBSCIP_FAIL .................. 31
Table 95 CONNECTION_SETUP_BTSIPALLOC_FAIL ............... 31
Table 96 CONNECTION_SETUP_CARRIERINPARA_NOTEXIST.. 32
Table 97 CONNECTION_SETUP_FOALLOC_FAIL.................... 32
Table 98 CONNECTION_SETUP_CHANNELINPARA_NOTEXIST. 32
Table 99 CONNECTION_SETUP_CARRIERALLOC_FAIL ........... 33
Table 100
CONNECTION_SETUP_LEGNUMBER_FROM_SP_ERROR........... 33
Table 101
CONNECTION_SETUP_CELLNUMBER_FROM_SP_ERROR ......... 33
Table 102 CONNECTION_SETUP_GIVENCARRIER_NOUSABLECE
..................................................................................... 34
Table 103 CONNECTION_SETUP_CrAllocFail_CrInParaNotExist34
Table 104 CONNECTION_SETUP_CrAllocFail_CHMTypeNotMatch
..................................................................................... 34
Table 105 CONNECTION_SETUP_CrAllocFail_CrIsBeacon ....... 34
Table 106 CONNECTION_SETUP_CrAllocFail_CrIsUnNormal ... 35
Table 107 CONNECTION_SETUP_CrAllocFail_NoUsableCE ...... 35
Table 108 CONNECTION_SETUP_CrAllocFail_CrIsOverload..... 35
Table 109 CONNECTION_SETUP_CrAllocFail_GetCellAllCrFailed
..................................................................................... 35
Table 110
CONNECTION_SETUP_CrAllocFail_GetCurCellAllPrefFailed....... 36
Table 111
CONNECTION_SETUP_CrAllocFail_GetGivenBandClassCRFailed 36
Table 112 HANDOFF_EXCEED_ONE_PILOT_FAILURE............. 36
Table 113 HANDOFF_DRC_SETUP_ERROR........................... 37
88
Tables
Table 114 HANDOFF_ADDLEG_TIMEOUT ............................. 37

Table 115 HANDOFF_ATACQUIRED_TIMEOUT ...................... 37
Table 116 HANDOFF_DRC_SETUP_TIMEOUT........................ 38
Table 117 HANDOFF_INVALID_PILOT_PN............................ 38
Table 118 HANDOFF_INVALID_ROUTEUPDATE ..................... 39
Table 119 HANDOFF_FORWARDDESIRED_TIMEOUT.............. 39
Table 120 HANDOFF_ADD_CHANNELITEM_FAILURE ............. 40
Table 121 HANDOFF_RESOURCE_ALLOCATED_TIMEOUT ....... 40
Table 122 HANDOFF_RESOURCE_ALLOCATED_FAILURE ........ 41
Table 123 HANDOFF_TCC_TIMEOUT ................................... 41
Table 124 CONNECTION_RELEASE_SESSIONCONFIG_IDP_
CONFIG_FAIL................................................................... 44
Table 125
CONNECTION_RELEASE_SESSIONCONFIG_FTCMAC_CONFIG_FA
IL................................................................................... 44
Table 126
CONNECTION_RELEASE_SESSIONCONFIG_AUTH_CONFIG_ FAIL
..................................................................................... 44
Table 127 CONNECTION_RELEASE_SESSIONCONFIG_ACMAC_
CONFIG_FAIL................................................................... 45
Table 128 CONNECTION_RELEASE_SESSIONCONFIG_TX_
CFGCOMPLETE_ TIMEOUT.................................................. 45
Table 129 CONNECTION_RELEASE_SESSIONCONFIG_SET_
CFGDONE_ FAILURE ......................................................... 45
Table 130
CONNECTION_RELEASE_SESSIONCONFIG_ATINITIATED_
REQUEST_ CFGATTR_TIMEOUT .......................................... 46
Table 131 CONNECTION_RELEASE_SESSIONCONFIG_RX_
CFGCOMPLETE_ TIMEOUT.................................................. 46
Table 132 CONNECTION_RELEASE_SESSIONCONFIG_READY_
REQUEST_CFGATTR_TIMEOUT ........................................... 47
Table 133
CONNECTION_RELEASE_ATTRIBUTEOVERRIDE_TIMEOUT ...... 47
Table 134
CONNECTION_RELEASE_AT_INITIAL_SESSION_CLOSE.......... 48
Table 135 CONNECTION_RELEASE_TCC_TIMEOUT ............... 48
Table 136 CONNECTION_RELEASE_SP_ADD_CHANNELITEM_
FAILURE.......................................................................... 48
Table 137 CONNECTION_RELEASE_AT_INITIATE ................. 48
Table 138 CONNECTION_RELEASE_SESSIONCONFIGURATION_
FAILURE.......................................................................... 49
89
Table 139 CONNECTION_RELEASE_SESSIONCONFIGURATION_

SUCCESS ........................................................................ 49
Table 140 CONNECTION_RELEASE_HANDOFF_FAILURE ........ 49
Table 141 CONNECTION_RELEASE_AIR_LINK_LOST_TIMEOUT
..................................................................................... 49
Table 142 CONNECTION_RELEASE_RLP_RESET_ACK_TIMEOUT
..................................................................................... 50
Table 143 CONNECTION_RELEASE_SP_SHAKE_HAND_TIMEOUT
..................................................................................... 50
Table 144 CONNECTION_RELEASE_SEMIHANDOFF_FAILURE . 50
Table 145 CONNECTION_RELEASE_DORMANCY_TIMEOUT..... 51
Table 146 CONNECTION_RELEASE_DRC_SETUP_FAILURE ..... 51
Table 147
CONNECTION_RELEASE_GETPARAFROMAUX_FAILURE........... 51
Table 148 CONNECTION_RELEASE_CPUOVERLOADED .......... 52
Table 149 CONNECTION_RELEASE_OPEN_DATAFLOW_FAILURE
..................................................................................... 52
Table 150 CONNECTION_RELEASE_CREATE_FSE_FAILURE .... 52
Table 151 CONNECTION_RELEASE_NOT_ALL_RESERVATION_
OPENED .......................................................................... 52
Table 152 CONNECTION_RELEASE_FSP_SETARQMODE_FAILURE
..................................................................................... 53
Table 153
CONNECTION_RELEASE_FSP_SETARQMODE_TIMEOUT .......... 53
Table 154
CONNECTION_RELEASE_FSP_SETTRANSMISSIONMODE_
TIMEOUT......................................................................... 53
Table 155
CONNECTION_RELEASE_FSP_SETTRANSMISSIONMODE_
FAILURE.......................................................................... 54
Table 156 CONNECTION_RELEASE_FSP_SHAKEHAND_TIMEOUT
..................................................................................... 54
Table 157 CONNECTION_RELEASE_A9PCFGOING_TO_DORMANT
..................................................................................... 54
Table 158
CONNECTION_RELEASE_A9_PDSNDENIED_UNKNOWN_PDSN_
ADDRESS ........................................................................ 55
Table 159 CONNECTION_RELEASE_A9_PDSNDENIED_
POORLYFORMED_ A11REQUEST ......................................... 55
Table 160
CONNECTION_RELEASE_A9_PDSNDENIED_MOBILENODE_
FAILED_AUTHENTICATION................................................. 55
90
Tables
Table 161 CONNECTION_RELEASE_A9_PDSNDENIED_

IDENTIFICATION_ MISMATCH ............................................ 56
Table 162 CONNECTION_RELEASE_A9_PDSNDENIED_RELEASE_
INSUFFICIENT_RESOURCE................................................. 56
Table 163 CONNECTION_RELEASE_A9_PDSNDENIED_REASON_
ADMINISTRATIVELY_PROHIBITED....................................... 56
UNSPECIFIED .................................................................. 57
VSE_ERROR..................................................................... 57
EVERSE_TUNNEL_UNAVAILABLE......................................... 57
TBIT_NOTSET .................................................................. 58
Table 168
CONNECTION_RELEASE_A9_PCFDENIED_EQUIPMENT_ FAILURE
..................................................................................... 58
Table 169 CONNECTION_RELEASE_A9_PCFDENIED_PCF_
RESOURCE_ UNAVIALABLE ................................................ 58
Table 170 CONNECTION_RELEASE_A9_PCFDENIED_PDSN_
RESOURCE_UNAVAILABLE ................................................. 59
Table 171 CONNECTION_RELEASE_A9_PCFNORMAL_RELEASE
..................................................................................... 59
Table 172
CONNECTION_RELEASE_SESSION_AN_CLOSED_ACCESS
_AUTH_FAILURE............................................................... 59
Table 173 CONNECTION_RELEASE_ACCESS_AUTH_INVALID_
ACCESS_AUTH_TIMEOUT .................................................. 60
A12TRANSMIT_OTHER_REASON ......................................... 60
Table 175
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_NO_
A12TRANSMIT_ID ............................................................ 60
Table 176
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_WAIT_SERVE
RRSP_TIMEOUT................................................................ 61
CLIENT_SHARESECRET_ERROR .......................................... 61
SUCCESS_BUT_MNID_INVALID .......................................... 61
Table 179
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_CLIENT
_OTHER_REASON............................................................. 62
CLIENT_ USERID_ERROR................................................... 62
91
Table 181
AAACLIENT_ID................................................................. 62
CLIENT_DECODEPKT_FAIL................................................. 62
A12ACCESSREQ_TIMEOUT................................................. 63
CLIENT_ SOCKET_ERROR .................................................. 63
ACCESS_AUTH_FAILURE ................................................... 63
Table 186
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_LCP_
ESTABLISH_FAIL .............................................................. 64
Table 187
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_CHAP_
CHALLENGE_TIMEOUT ...................................................... 64
Table 188
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_WAIT_
CLIENTRSP_TIMEOUT ....................................................... 64
Table 189
PPPSESSION_ID............................................................... 65
Table 190
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_PPP_
ESTABLISH_TIMEOUT ....................................................... 65
PPPSES_ WAIT_POWER_ON ............................................... 65
Table 192
CONNECTION_RELEASE_ACCESS_AUTH_INVALID_AUTH_
ID_UNMATCHED............................................................... 65
Table 193 CONNECTION_RELEASE_ACCESS_AUTH_SUCCESS_
AFTER_ SCP_OR_USERQOS_CHANGED................................ 66
Table 194 CONNECTION_RELEASE_A9_SHAKEHAND_TIMEOUT
..................................................................................... 66
Table 195 CONNECTION_RELEASE_RE_AUTH ...................... 66
Table 196 CONNECTION_RELEASE_A9_AUTH_FAILURE_OR_AT_
POWER_DOWN ................................................................ 66
Table 197
CONNECTION_RELEASE_A9_UPDATE_A8_TIMER_EXPIRED..... 66
Table 198 CONNECTION_RELEASE_ A9_RELEASE_A8_
TIMER_EXPIRED............................................................... 67
Table 199 CONNECTION_RELEASE_A9_DISCONNECT_A8_REQ
..................................................................................... 67
92
Tables
Table 200
CONNECTION_RELEASE_A9SETUPA8_TIMER_EXPIRED .......... 67
Table 201 CONNECTION_RELEASE_DORMANT_HANDOFF_
OR_PDSN_NO_RES........................................................... 67
Table 202 CONNECTION_RELEASE_A9SETUP_RES_UNVALIABLE
..................................................................................... 68
Table 203 CONNECTION_RELEASE_A9_MASTER_TO_SLAVE_
CHANGEOVER .................................................................. 68
Table 204 CONNECTION_RELEASE_SERVICE_TERMINATE ..... 68
Table 205 CONNECTION_RELEASE_MASTER_TO_SLAVE_
CHANGEOVER .................................................................. 68
Table 206 CONNECTION_RELEASE_REALLOC_SDU_FAILURE . 68
Table 207
CONNECTION_RELEASE_CONNECTION_INTERNAL_ERROR ..... 69
Table 208
CONNECTION_RELEASE_BSSAP_SHAKE_HAND_TIMEOUT ...... 69
Table 209 CONNECTION_RELEASE_SESSION_AN_TERMINATED
..................................................................................... 69
Table 210 CONNECTION_RELEASE_SESSION_AN_CLOSED .... 69
Table 211
CONNECTION_RELEASE_SP_SEND_ADDCHANNELMSG_ FAILURE
..................................................................................... 69
Table 212 CONNECTION_RELEASE_MULTICASTTIMEOUT....... 70
Table 213 CONNECTION_RELEASE_SEMIHANDOFF_FAILURE_
FORWARDDESIREDTO....................................................... 70
ACTIVESETEMPTY ............................................................. 70
RESOURCEALLOC ............................................................. 70
ATACQUIREDTO ............................................................... 71
Table 217 CONNECTION_RELEASE_ATACQUIREDACK_TIMEOUT
..................................................................................... 71
Table 218 CONNECTION_RELEASE_ADDLEGFORHO_TIMEOUT 71
Table 219 CONNECTION_RELEASE_NEEDTOUPDATE_TOKEN.. 72
Table 220 CONNECTION_RELEASE_UPDATE_RESERVATION_
FAILURE.......................................................................... 72
Table 221 CONNECTION_RELEASE_ GETBSCCHITEM_TIMEOUT
..................................................................................... 72
Table 222
CONNECTION_RELEASE_NEIGHBORLISTUPDATE_TIMEOUT .... 73
Table 223 CONNECTION_RELEASE_FINDSERVINGLEG_FAILURE
..................................................................................... 73
93
Table 224 CONNECTION_RELEASE_SENDUMFTCA_ERROR..... 73

Table 225 CONNECTION_RELEASE_BSCCHITEMREQACK_ERROR
..................................................................................... 74
Table 226 CONNECTION_RELEASE_SESSIONCONFIG_KEP_
SKEYLEN_ CONFIG_FAIL ................................................... 74
Table 227
CONNECTION_RELEASE_SESSIONCONFIG_KEP_SEND_
ANKEYCOMPLETE_FAIL...................................................... 74
Table 228
CONNECTION_RELEASE_SESSIONCONFIG_KEP_SEND_
KEYREQUEST_FAIL ........................................................... 75
Table 229
CONNECTION_RELEASE_SESSIONCONFIG_KEP_START_
TASK_FAIL ...................................................................... 75
Table 230 CONNECTION_RELEASE_SESSIONCONFIG_KEP_REV_
KEYRESPONSE_DUR_COMPUTEKEY ..................................... 75
ATKEYCOMPLETE_RESAULT_FAIL........................................ 75
ATKEYCOMPLETE_TRANSID_NOMATCH................................ 76
Table 233 CONNECTION_RELEASE_SESSIONCONFIG_STR_
CONFIG_FAIL .................................................................. 76
Table 234 CONNECTION_RELEASE_SESSIONCONFIG_SMP_
CONFIG_FAIL .................................................................. 76
Table 235 CONNECTION_RELEASE_SESSIONCONFIG_SCP_
CONFIG_FAIL .................................................................. 77
Table 236 CONNECTION_RELEASE_SESSIONCONFIG_RTCMAC_
CONFIG_FAIL .................................................................. 77
Table 237 CONNECTION_RELEASE_SESSIONCONFIG_PAP_
CONFIG_FAIL .................................................................. 77
Table 238 CONNECTION_RELEASE_SESSIONCONFIG_RUP_
CONFIG_FAIL .................................................................. 78
SIGCOMP_ KEYCOMP_TIMEOUT.......................................... 78
KEYRESPONSE_TIMEOUT................................................... 78
Table 241
CONNECTION_RELEASE_SESSIONCONFIG_KEP_SESSION_
KEYLEN_ERROR ............................................................... 79
Table 242
CONNECTION_RELEASE_UPDATERESERVATION_TIMEOUT ..... 79
Table 243 CONNECTION_RELEASE_RCP_BSCIP_ASSIGNMENT_
FAILURE.......................................................................... 79
94
Tables
Table 244 CONNECTION_RELEASE_RCP_ADD_CHANNELITEM_

FAILURE.......................................................................... 80
Table 245 CONNECTION_RELEASE_RCP_OVERLOADCONTROL 80
Table 246
CONNECTION_RELEASE_RCP_SHAKE_HAND_TIMEOUT .......... 80
Table 247 RELEASE_FAILURE_EXCEED_ONE_PILOT_FAILURE 82
Table 248 RELEASE_FAILURE_RCP_TIMEOUT ...................... 82
Table 249
RELEASE_FAILURE_AT_RESPONSE_CONNECTIONCLOSE_
TIMEOUT......................................................................... 82
Table 250 RELEASE_FAILURE_CELLNUMBER_FROM_SP_ERROR
..................................................................................... 83
Table 251 RELEASE_FAILURE_LEGNUMBER_FROM_SP_ERROR
..................................................................................... 83
Table 252 RELEASE_FAILURE_RELFWDCE_FAIL ................... 83
Table 253 RELEASE_FAILURE_FWDCE_ISNOTEXIST ............. 83
Table 254 RELEASE_FAILURE_RELBTSIP_FAIL ..................... 84
Table 255 RELEASE_FAILURE_MODIFYCARRIERUSER_FAIL.... 84
Table 256 RELEASE_FAILURE_CES_CONNECTION_
RELEASE_TIMEOUT........................................................... 84
Table 257 RELEASE_FAILURE_CES_SOFTER_HANDOFF_
DROP_TIMEOUT ............................................................... 84
95

ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (EV-DO)

Caricato da

Copyright:

Formati disponibili

ZXC10 BSSB

CDMA Base Station System

Call Failure Reason and Call Drop

Reason for Revision

Equipment Installation Date

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

This page is intentionally blank.

This page is intentionally blank.

About this Manual

Prerequisite Skill and Knowledge

the ZXC10 BSSB system and its various components

local operating procedures

What is in This Manual

Describes causes and solutions for call

Describes reasons and settlement

Reasons for Call Drop

Explains the reasons and settlement

Describes reasons and solutions for

Confidential and Proprietary Information of ZTE CORPORATION

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function names, input

Keys on the keyboard and buttons on screens

Text that you type, program code, files and

Select one of the parameters that are delimited

TABLE 3 MOUSE OPERATION CONVENTIONS

Refers to clicking the primary mouse button (usually

Refers to quickly clicking the primary mouse button

Confidential and Proprietary Information of ZTE CORPORATION

About this Manual

Refers to clicking the secondary mouse button

Refers to pressing and holding a mouse button and

How to Get in Touch

If you have problems, questions, comments, or suggestions

Confidential and Proprietary Information of ZTE CORPORATION

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION

In the following cases, there may be a large volume of

if there is a version mismatch, check the version

TABLE 5 CONNECTION_SETUP_SETDRCLENTR ANS_FAILURE

After resource allocating and before sending TCA, an

Check the system parameters in NetNumenTM

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Call Failure

TABLE 6 CONNECTION_SETUP_SETDRC AND ACKINFO_F AILURE

After resource allocating and before sending TCA, an

Check the system parameters in OMC. If the

TABLE 7 CONNECTION_SETUP_AT ACQUIRED_TIMEOUT

If there is a version mismatch, check the version

Confidential and Proprietary Information of ZTE CORPORATION

Perhaps BSSAP fails to retrieve data from database.

SP sends a resource allocating request to RCP without