ISUP Standard Failure Cause Code(Incoming)
BICC Standard Failure Cause Code (Incoming)
SIP Standard Failure Cause Code (Incoming)
SIP_I or Reason (Incoming)
Failure Cause Code Value
NA
NA
NA
NA
CV0
NA
NA
NA
NA
CV1
NA
NA
NA
NA
CV2
NA
NA
NA
NA
CV3
NA
NA
NA
NA
CV4
NA
NA
NA
NA
CV5
NA
NA
NA
NA
CV6
NA
NA
NA
NA
CV7
NA
NA
NA
NA
CV8
NA
NA
NA
NA
CV9
NA
NA
NA
NA
CV10
NA
NA
NA
NA
CV15
NA NA NA NA 0 0
NA NA NA NA 0 0
NA NA NA NA NA NA
NA NA NA NA NA NA
CV17 CV18 CV19 CV20 CV24 CV25
NA
NA
NA
NA
CV28
NA
NA
NA
NA
CV29
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
NA NA NA NA NA NA NA NA
CV33 CV34 CV36 CV39 CV40 CV41 CV43 CV44
NA
NA
NA
NA
CV46
NA
NA
NA
NA
CV47
NA
NA
NA
NA
CV48
NA
NA
NA
NA
CV49
NA
NA
NA
NA
CV50
NA
NA
NA
NA
CV51
NA NA NA
NA NA NA
NA NA NA
NA NA NA
CV53 CV56 CV59
NA
NA
NA
NA
CV63
NA
NA
NA
NA
CV64
NA
NA
NA
NA
CV65
NA NA NA NA NA NA
NA NA NA NA NA NA
NA NA NA NA NA NA
NA NA NA NA NA NA
CV69 CV71 CV72 CV73 CV74 CV75
NA
NA
NA
NA
CV76
NA
NA
NA
NA
CV77
NA
NA
NA
NA
CV78
NA
NA
NA
NA
CV79
NA
NA
NA
NA
CV92
NA
NA
NA
NA
CV93
NA
NA
NA
NA
CV94
NA
NA
NA
NA
CV95
NA
NA
NA
NA
CV96
NA
NA
NA
NA
CV97
NA
NA
NA
NA
CV98
NA
NA
NA
NA
CV99
NA
NA
NA
NA
CV101
NA
NA
NA
NA
CV103
NA
NA
NA
NA
CV104
NA
NA
NA
NA
CV106
NA
NA
NA
NA
CV108
NA
NA
NA
NA
CV109
NA
NA
NA
NA
CV111
NA
NA
NA
NA
CV112
NA
NA
NA
NA
CV115
NA
NA
NA
NA
CV124
NA NA 0 6
NA NA 0 6
NA NA NA NA
NA NA 0 6
CV126 CV127 CV128 CV134
7
7
NA
7
CV135
NA
NA
NA
NA
CV136
16
16
NA
16
CV144
18
18
NA
18
CV146
19
19
NA
19
CV147
20
20
480
20
CV148
21 26
21 26
603 NA
21 26
CV149 CV154
30
30
NA
30
CV158
31 92 93 NA 116 117 118 126/127
31 92 93 102 116 117 118 126/127
NA NA NA NA NA NA NA 300
31 92 93 NA 116 117 118 126/127
CV159 CV220 CV221 CV230 CV244 CV245 CV246 CV254
Failure Cause Code Description Supplementary service activation conflicted Supplementary service activation succeeded Supplementary service activation failed Supplementary service cancellation succeeded Supplementary service cancellation cancellation failed Supplementary service checking succeeded Supplementary service checking failed Supplementary service usage succeeded Supplementary service usage failed Malicious call tracing succeeded Malicious call tracing failed
ISUP Standard ISUP Standard Failure Cause Failure Cause Description (Outgoing) Code (Outgoing) 31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
No reply for long time
19
No answer from user (user alerted)
Self test succeeded No information for long No ring for long time No release for long time Release before ring Release before answer Operator interruption succeeded Operator forced r eleasing failed Number portability Restart CT0 Card number in arrears Cause 39 Lost TCSI data Lost OCSI data Call failure Dual seizure Remote password update failed
31 18 18 18 16 16
Normal, unspecified No user responding No user responding No user responding Normal call clearing Normal call clearing
31
Normal, unspecified
31
Normal, unspecified
31 31 31 31 21 21 31 31
Normal, unspecified Normal, unspecified Normal, unspecified Normal, unspecified Call rejected Call rejected Normal, unspecified Normal, unspecified
31
Normal, unspecified
Remote password update succeeded Activate remote remote call forwarding successfully Activate remote remote call forwarding unsuccessfully unsuccessfully Cancel remote call forwarding successfully Cancel remote call forwarding unsuccessfully Password error NM restricted Queue timeout Call forwarding from trunk barring Number length increased from 7 digits to 8 digits Dialed number is reserved number Abandon during the dialing dialing Cause 71 Cause 72 Cause 73 Cause 74 Signaling error Money of the card is not enough Black and white list restriction
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
31 41 17
Normal, unspecified Temporary failure User busy
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
16 31 31 31 31 31
Normal call clearing clearing Normal, unspecified Normal, unspecified Normal, unspecified Normal, unspecified Normal, unspecified
31
Normal, unspecified
21
Call rejected
Calling number discrimination restriction Port is not activated
21
Call rejected
31
Normal, unspecified
Forwarding indicator
31
Normal, unspecified
Call release
31
Normal, unspecified
Internal switching succeeded
31
Normal, unspecified
Internal switching failed
31
Normal, unspecified
Call forwarding from toll to toll
31
Normal, unspecified
Call barring timeout Terminal resource application failed Cause 99 No reply from mobile subscriber Mobile caller outgoing call barring
31
Normal, unspecified
31
Normal, unspecified
31
Normal, unspecified
19
No answer from user (user alerted)
31
Normal, unspecified
Mobile callee unreachable
18
No user responding
Call hold
31
Normal, unspecified
Mobile callee power off
20
Subscriber absent
Service unavailable
21
Call rejected
Emergency call
31
Normal, unspecified
Forwarding violation
21
Call rejected
MAP routing information error
31
Normal, unspecified
Subscriber out of service area
20
Subscriber absent
No enough balance Cause 127 Unknown error Route unacceptable Submit the call sent in the established path
31 31 0/16 6 7
Normal, unspecified Normal, unspecified #N/A Channel unacceptable Call awarded and being delivered in established channel
Operator determined barring
31
Normal, unspecified
Normal call clearing
16
Normal call clearing
No response from subscriber
18
No user responding
No answer from subscriber
19
No answer from user (user alerted)
Absent service
20
Subscriber absent
Call rejected Non-selected user clearing
21 26
Call rejected Non-selected user clearing
Response to status inquiry
30
Response to STATUS ENQUIRY
Normal IST command IST alert Recovery on timer expiry Release call from O-BCSM Release call from T-BCSM Subscriber request failed Interworking
31 31 31 102 31 31 31 127
Normal, unspecified Normal, unspecified Normal, unspecified Recovery on timer expiry Normal, unspecified Normal, unspecified Normal, unspecified Interworking, unspecified
BICC Standard Failure Cause Code(Outgoing)
SIP Standard Failure Cause ToneID Code(Outgoing)
Tone Type
31
480
TID127
Invalid tone
31
480
TID29
Music
31
480
TID127
Invalid tone
31
480
TID29
Music
31
480
TID127
Invalid tone
31
480
TID29
Music
31
480
TID127
Invalid tone
31
480
TID29
Music
31
480
TID127
Invalid tone
31
480
TID28
31
480
TID127
19
480
TID61
31 18 18 18 16 16
480 480 480 480 480 480
TID127 TID127 TID127 TID127 TID127 TID127
Malicious call tracing success tone Invalid tone Mobile callee not answer tone Invalid tone Invalid tone Invalid tone Invalid tone Invalid tone Invalid tone
31
480
TID29
Music
31
480
TID127
Invalid tone
31 31 31 31 21 21 31 31
480 480 480 480 480 480 480 480
TID127 TID127 TID127 TID127 TID115 TID115 TID127 TID127
Invalid tone Invalid tone Invalid tone Invalid tone IN protect tone IN protect tone Invalid tone Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31 41 17
480 480 480
TID127 TID127 TID127
Invalid tone Invalid tone Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
16 31 31 31 31 31
480 480 480 480 480 480
TID127 TID127 TID127 TID127 TID127 TID127
Invalid tone Invalid tone Invalid tone Invalid tone Invalid tone Invalid tone
31
480
TID127
Invalid tone
21
480
TID27
Call restriction tone
21
480
TID27
Call restriction tone
31
480
TID127
92
480
TID104
31
480
TID127
Invalid tone Forwarding notification tone Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
Invalid tone
31
480
TID127
19
480
TID61
Invalid tone Mobile callee not answer tone
31
480
TID27
Call restriction tone
Mobile callee not reachable tone Music Mobile callee power off tone Mobile service not availabe tone Emergency call tone Call forwarding restriction tone
18
480
TID32
31
480
TID29
20
480
TID58
21
480
TID59
31
480
TID101
21
480
TID44
38
480
TID127
20
480
TID32
31 31 0/16 6
480 480 480 480
TID127 TID127 TID127 TID127
Mobile callee not reachable tone Invalid tone Invalid tone Invalid tone Invalid tone
7
480
TID127
Invalid tone
31
480
TID56
16
480
TID127
Mobile call-out restriction tone Invalid tone
18
480
TID127
Invalid tone
19
480
TID61
20
480
TID58
21 26
480 480
TID27 TID127
Mobile callee not answer tone Mobile callee power off tone Call restriction tone Invalid tone
30
480
TID127
Invalid tone
31 31 31 102 31 31 31 127
480 480 480 480 480 480 480 480
TID127 TID114 TID114 TID127 TID127 TID127 TID127 TID127
Invalid tone IST notify tone IST notify tone Invalid tone Invalid tone Invalid tone Invalid tone Invalid tone
Invalid tone
Failure Cause Code Value CV0 CV1 CV2 CV3 CV4 CV5 CV6 CV7 CV8 CV9 CV10 CV11 CV12
CV_NS_SET_CONFLICT CV_NS_SET_OK CV_NS_SET_FAIL CV_NS_CANCEL_OK CV_NS_CANCEL_FAIL CV_NS_VERIFY_OK CV_NS_VERIFY_FAIL CV_NS_USE_OK CV_NS_USE_FAIL CV_NS_MCT_USE_OK CV_NS_MCT_USE_FAIL CV_NS_ABSENT_USER CV_NS_NO_DISTURB
CV13
CV_SWITCHING_EQUIPMENT_CONGESTION
CV14
CV_LONG_TIME_NO_DIALING
CV15
CV_LONG_TIME_NO_ANSWER
CV16
CV_TEMPORARY_FAILURE
CV17
CV_REMOTE_TEST_OK
CV18
CV_LONG_TIME_NO_INFORMATION
Failure Cause Code
CV19
CV_LONG_TIME_NO_ALERTING
CV20
CV_LONG_TIME_NO_RELEASE
CV21
CV_IN_BAND_SIGNAL
CV22
CV_COCK_FAILURE
CV23
CV_EXCEED_MAX_REATTEMPT_TIME
CV24
CV_RELEASE_BEFORE_RING
CV25
CV_RELEASE_BEFORE_ANSWER
CV26
CV_CALL_BARRING
CV27
CV_SWITCHING_EQUIPMENT_FAULT
CV28 CV29
CV_OPR_DISCONNECT_FORCELY_OK CV_OPR_DISCONNECT_FORCELY_FAILURE
CV30
CV_ST_BUSY
CV31 CV32 CV33 CV34 CV35 CV36
CV_SL_BUSY CV_OWNED CV_NUMBER_PORT CV_RESTART_CT0 CV_NS_RECORD_USE_OK CV_CREDIT_ARREARAGE
CV37
CV_CALLIN_BARRING
CV38
CV_EXCHANGE_ROUTE_ERROR
CV39
-
CV40
CV_HAVE_NOT_KD
CV41
CV_HAVE_NOT_KB
CV42
CV_REMOTE_EQUIPMENT_CONGESTION
CV43
CV_CALL_FAIL
CV44
CV_DUAL_SEIZE
CV45
CV_INVALID_CODE_FORM
CV46 CV47 CV48 CV49 CV50 CV51 CV52 CV53 CV54
CV_REMOTE_PASS_UPDATE_FAIL CV_REMOTE_PASS_UPDATE_SUC CV_REMOTE_LOGIN_CF_SUC CV_REMOTE_LOGIN_CF_FAIL CV_REMOTE_CANCEL_CF_SUC CV_REMOTE_CANCEL_CF_FAIL CV_CALLED_OWNED CV_PASSWORD_WRONG CV_REDIRECT_RESTRICTION
CV55
CV_MODULE_NOT_ARRIVED
CV56
CV_NET_MANAGE_BARRING
CV57 CV58 CV59 CV60
CV_USER_QUEUE_FAIL CV_GROUP_QUEUE_FAIL CV_TIMEOUT_IN_QUEUE CV_CPU_OVERLAP
CV61
CV_NO_CR
CV62
CV_NO_CCB
CV63 CV64
CV_REDIRECT_FROM_TRUNK_RESTRICTION CV_NUMRISE_FROM7TO8
CV65
CV_DIAL_NO_RESERED
CV66
CV_NO_CONFO
CV67
CV_NO_DIALING_ABANDON
CV68
CV_NO_DIALING_TIMEOUT
CV69
CV_PARTIAL_DIAL_ABANDON
CV70
CV_PARTIAL_DIAL_TIMEOUT
CV71 CV72 CV73
-
CV74
CV_MT_ASSIGN_FAIL
CV75 CV76
CV_SIGNALING_ERROR CV_MONEY_NOT_ENOUGH
CV77
CV_BW_LIST_BARRING
CV78
CV_CLI_JUDGE_RESTRICTION
CV79 CV80 CV81
CV_PORT_NOT_ACTIVE CV_HW_TS_UNAVAILABE CV_IWF_UNAVAILABLE
CV82
CV_NO_REQUEST_BEARER_ACIRCUIT
CV83 CV84
CV_NO_ACIRCUIT CV_USER_BUSY
CV85
CV_CUG_SERVICE_IMCOMPATIBLE
CV86
CV_UNKNOWN_CUG
CV87
CV_NO_CUG_SELECTED
CV88
CV_CUG_OUTGOING_CALL_BARRED
CV89
CV_CUG_WITHOUT_INCOMGING_ACCESS
CV90
CV_CUG_SS_INTERACTION_VIOLATION
CV91
CV_CUG_INCOMPATIBLE_DESTINATION
CV92 CV93 CV94
CV_FORWARD_IND CV_CALL_RELEASE CV_HO_COMPLETE
CV95
CV_HO_FAILURE
CV96
CV_TOLL_CT_TO_TOLL
CV97
CV_LIMIT_TIME_OUT
CV98 CV99
CV_TERMINATION_APPLY_FAIL -
CV100
CV_GSM_CLD_DN_NO_EXIST
CV101
CV_GSM_CLD_USER_NO_ACKNOWLEGE
CV102
CV_GSM_CLD_USER_BAIC
CV103
CV_GSM_CLI_USER_BAOC
CV104
CV_GSM_CLD_USER_NOT_REACHABLE
CV106
CV_GSM_LOCAL_CALL_NO_NATIONAL_AREA_CO DE CV_GSM_CALL_HOLD
CV107
CV_GSM_CLD_USER_BUSY
CV108
CV_GSM_CLD_USER_NOT_ACTIVE
CV109
CV_GSM_SERVICE_NOT_AVAILABLE CV_GSM_NO_DIAL_0_CALLING_OTHER_AREA_M OBILE_SUBSCIBER
CV105
CV110 CV111
CV_GSM_EMERGENCY
CV112
CV_FORWARDING_VIOLATION
CV113 CV114
CV_VM_DN_LONG CV_MSISDN_DN_LONG
CV115
CV_MAP_ROUTE_INFORMATION_ERROR
CV116
CV_GSM_ODB_BAOC
CV117
CV_GSM_ODB_BOIC
CV118
CV_GSM_BOIC
CV119
CV_GSM_BOIC_EXHC
CV120
CV_GSM_ODB_BOIC_EXHC
CV121
CV_GSM_ODB_BAIC
CV122
CV_GSM_ODB_ENTERTAINMENT
CV123
CV_GSM_ODB_MESSAGE
CV124
CV_GSM_OUT_OF_PLMN
CV125
CV_GSM_ODB_TOLL
CV126
CV_LOOPBACK_NO_BLNC
CV127
CV_SOSM_PROHIBIT_CALL
CV128
CV_UNKNOWN
CV129
CV_UNALOC_CODE
CV130
CV_NO_ROUTE_TO_SPECIFIED_INTERNETWORK
CV131
CV_NO_ROUTE_TO_TERMINAL
CV132
CV_SEND_PRIVATE_TONE
CV133
CV_ERROR_INCLUDE_LONG_DISTANCE
CV134
CV_ROUTE_UNACCEPTABLE
CV135
CV_CALL_HAS_ESTABLISHED_AND_DELIVERED_ ON_ROUTE_ESTABLISHED
CV136
CV_OPERATOR_DETERMINED_BARRING
CV137
CV_RESERVED_FOR_REUSE
CV138
CV_SSP_SCP_INTERACTIVE_FAIL
CV139 CV140 CV141
-
CV142
CV_PORTED_SUBSCRIBER
CV143
-
CV144
CV_NORMAL_CALL_CLEAR
CV145
CV_BUSY
CV146
CV_NO_RESPOND
CV147
CV_NO_ACKNOWLEGE
CV148
CV_ABSENT_SUBSCRIBER
CV149
CV_CALL_REJECTED
CV150
CV_NUMBER_CHANGED
CV151
CV_NO_FREE_CIRCUIT
CV152
CV_ANONYMOUS_CALL_REJECTED
CV153 CV154
CV_RAB_PRE_EMPTED CV_CLEAR_UNSELECTED_USER
CV155
CV_TERMINAL_ERROR
CV156
CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOU GH
CV157
CV_FACILITY_REJECTED
CV158
CV_RESPOND_TO_STATUS_ENQUIRY
CV159
CV_NORMAL
CV160 CV161
-
CV162
CV_NO_ROUTE_AVAILABLE
CV163
CV_TMSC_CIRCUIT_BUSY
CV164
CV_TMSC_NO_AVAIL_MGW
CV165
-
CV166
CV_NETWORK_ERROR
CV167 CV168
-
CV169
CV_ERROR_FOR_THE_TIME_BEING
CV170
CV_EXCHANGE_FACILITY_SURGE
CV171
CV_ACCESS_INFO_LOST
CV172
CV_NO_ROUTE_OR_CIRCUIT_APPLIED_AVAILABL E
CV173 CV174
CV_PRECEDENCE_CALL_BLOCKED
CV175
CV_NO_RESOURCE_AVAILABLE
CV176 CV177
CV_NO_SUITABLE_SERVICE_QUALITY
CV178
CV_FACILITY_APPLIED_NOT_PRESERVED
CV179 CV180 CV181 CV182
CV_CUG_OUTGO_CALL_BARRED -
CV183
CV_CUG_INCOMING_CALL_UNALLOW
CV184
-
CV185
CV_BEARER_CAPABILITY_NOT_PERMIT
CV186
CV_NO_BEARER_CAPABLILITY_AVAILABLE_THIS_ TIME
CV187
CV_IP_UNAVAILABLE_RESOURCE
CV188 CV189 CV190
CV_NO_SUITABLE_SERVICE_OR_OPTIONAL_PRO JECT -
CV191 CV192
_
_
_
_
_
CV194
CV_ROUTE_TYPE_NOT_LAY_OUT
CV195
CV_AOC_SERVICE_REQ_IS_FAIL
CV196
CV_ACM_EQUAL_TO_OR_GREATER_THAN_ACM MAX
CV197
CV_FACILITY_APPLIED_NOT_LAY_OUT
CV198 CV199 CV200 CV201 CV202 CV203 CV204 CV205 CV206
CV_ONLY_LIMITED_DIGITAL_INFO_BEARER_CAP ABILITY CV_IWF_RESOURCE_UNAVAILABE CV_NO_ECP -
CV207
CV_SERVICE_OR_OPTIONAL_PROJECT_NOT_LA Y_OUT
CV208
-
CV209
CV_INVALID_CALL_REFERENCE
CV210
CV_REOUTE_IDENTEFIED_NOT_EXIST
CV211
CV_SUSPENDED_CALL_EXIST_BUT_NO_CALL_ID ENTIFIER
CV212
CV_CALL_IDENTIFIER_IS_USING
CV213
CV_NO_SUSPENDED_CALL
CV214
CV_CALL_HAS_THE_CALL_IDENTIFIER_APPLIED_ CLEARED
CV215
CV_CALLED_IS_NOT_CUG
CV216
CV_TERMINAL_UNCOMPATABLE
CV217 CV218
CV_NON_EXIST_CUG
CV219
CV_INVALID_TRANSMIT_NETWORK_SELECTION
CV220
CV_CALL_ISTCOMMAND
CV221
CV_CALL_ISTALERT
CV222
-
CV223
CV_INVALID_MESSAGE
CV224
CV_NECESSARY_IE_LOST
CV225
CV_MESSAGE_TYPE_NOT_EXIST_OR_NOT_LAY_ OUT
CV226
CV_MESSAGE_STATE_ERROR_OR_MESSAGE_ER ROR
CV227
CV_IE_NOT_EXIST_OR_NOT_LAY_OUT
CV228
CV_INVALID_IE_CONTENT
CV229
CV_MESSAGE_UNFIT_FOR_CALL_STATE
CV230
CV_RECOVERY_OF_TIME_OUT
CV231
CV_PARA_NOT_EXIST
CV232 CV233
CV_ORDINARY_CONGESTION CV_TARIFF_CHANGED
CV234
CV_TBS_CHANGED
CV235 CV236 CV237 CV238
CV_HANDOVER_SUCCESS CV_HANDOVER_FAILURE CV_MESSAGE_WITH_UNRECOGNIZE_PARA
CV239
CV_PROTOCOL_ERROR
CV240 CV241 CV242
CV_EXCEPTION_OF_SCP CV_ERROR_FROM_SCP CV_REPORT_DP_ERROR
CV243
CV_LONG_TIME_NO_CCF_ACK
CV244 CV245 CV246 CV247
CV_RELEASECALL_FROM_O_BCSM CV_RELEASECALL_FROM_T_BCSM CV_SUBSCRIBER_REQ_FAIL CV_CLI_NOT_MATCH
CV248
CV_AIS_DROP_ACTIVE_CALL_PLAY_TONE
CV249
CV_CHECK_IMEI_BARRING
CV250
CV_BEARER_ERROR
CV251
CV_RELEASE_CCF_NORMAL
CV252
CV_FACILITY_APPLIED_NOT_PRESERVED_FOR_ CLIR_NOT_SUBSCRIBED
CV253
CV_CREATE_INTERMINAL_BILL
CV254
CV_INTERWORK
Description Supplementary service activation conflicted Supplementary service activation succeeded Supplementary service activation failed Supplementary service cancellation succeeded Supplementary service cancellation failed Supplementary service checking succeeded Supplementary service checking failed Supplementary service usage succeeded Supplementary service usage failed Malicious call tracing succeeded Malicious call tracing failed Absent service set on peer office Do-not-disturb service set on peer office
Switching device congestion
No dialing for long time
No reply for long time
Temporary failure
Self test succeeded
No information for long
No ring for long time
No release for long time
In-band signal
Continuity check failed
Exceed maximum retrying times
Release before ring
Release before answer
Call barring
Switching device fault
Operator interruption succeeded Operator interruption failed Called toll busy Called local busy Caller owing charge Number portability Restart CT0 Record service usage succeeded Card number in arrears Incoming call barring
Exchange route error
Cause 39
Have No TCSI Data
Have No OCSI Data
Remote equipment congestion
Call failure Dual seizure
Invalid number format
Remote password update failed Remote password update succeeded Activate remote call forwarding successfully Activate remote call forwarding unsuccessfully Cancel remote call forwarding successfully Cancel remote call forwarding unsuccessfully Owing charge callee Password error Forwarding restricted Module not arrived
NM restricted Call queuing failed Failure to queue on the group Queue timeout CPU congestion and overload No CR
No CCB Call forwarding from trunk barring Number length increased from 7 digits to 8 digits Dialed number is reserved number No conference telephone resources Abandon when there is no dialing
Time out when there is no dialing
Abandon during the dialing
Dial interval timeout Cause 71 Cause 72 Cause 73 Assignment Failure Signaling error Money of the card is not enough
Black and white list restriction
Calling number discrimination restriction
Port is not activated Network board timeslot unavailable IWF resource unavailable No A interface circuit requested by bearer service No A interface circuit Subscriber busy CUG service incompatible
Unknown CUG
No CUG selected
Outgoing calls barred within CUG
Incoming calls barred within CUG
CUG supplementary service failed
CUG destination incompatible Forwarding indicator Call release Internal switching succeeded Internal switching failed Call forwarding from toll to toll Call barring timeout Terminal resource application failed Cause 99
Mobile number nonexistent
No reply from mobile subscriber
Mobile callee incoming call barring
Mobile caller outgoing call barring
Mobile callee unreachable
No area code before a local fixed-line number Call hold Mobile callee busy
Mobile callee power off Service unavailable No zero before remote mobile number Emergency call
Forwarding violation Roaming number length rise MSISDN number length rise MAP routing information error
Operator determined barring of all outgoing calls
Operator determined barring of all outgoing international calls
Barring of all outgoing international calls
Barring of outgoing international calls except those directed to the home country
Operator determined barring of outgoing international calls except those directed to the home country
Operator determined barring of all incoming calls
Operator determined barring of entertainment stations
Operator determined barring of information stations
Subscriber out of service area
Operator determined barring of national toll
Insufficient balance Cause 127 Unknown error
Unallocated number
No route to specified network
No route to terminal
Send private signal tone Misdial toll prefix Route unacceptable
Submit the call sent in the established path
Operator determined barring Reserved for reuse Interaction between SSP and SCP failed Cause 139 Cause 140 Cause 141 Ported subscriber Cause 143 Normal call clearing Subscriber busy
No response from subscriber
No answer from subscriber
Absent service
Call rejected
Number changed
No free circuit
Anonymous Call Rejected
RAB preempted Non-selected user clearing Terminal fault
Invalid number format or incomplete address
Facility rejected Response to status inquiry Normal Cause 160 Cause 161 No route available
T office circuit busy
No T office media gateway available Cause 165
Network fault
Cause 167 Cause 168 Temporary fault
Switching device congestion
Access information discarded
No route or circuit available Cause 173 Priority call blocked No resource available Cause 176 Quality of service not available
Requested facility not subscribed
Cause 179 Cause 180 CUG outgoing call barred Cause 18
CUG incoming call unallowed
Cause 184
Bearer capability unallowed
No bearer capability available now
IP Congestion Cause 188 Cause 189 Cause 190 No service or optional item available Cause 192
Route type not implemented AOC service request failed ACM equal to or greater than ACM maximum
Requested service not supported
Only restricted digital information bearer capability Cause 199 Cause 200 IWF resource unavailable No ECP Cause 203 Cause 204 Cause 205 Cause 206 Service or optional item not implemented Cause 208 Invalid call reference value
Route identifier does not exist Suspended call exists, but no call identifier Call identifier in use
No suspended call
Call with the request ID has been cleared
Callee not member of CUG
Terminal incompatible Cause 217 Nonexistent CUG Invalid transit network selection ISTCOMMAND service is activated
ISTALERT service is activated Cause 222
Invalid message
Mandatory information element is missing
Message type nonexistent or not implemented Message not compatible with call status or message type nonexistent Information element nonexistent or not implemented
Invalid information element contents
Message not compatible with call status
Recovery on timer expiry
Parameter nonexistent or not implemented Ordinary congestion Tariff changed
TBS changed Ticket handover succeeded Ticket handover failed Cause 237 Unidentified parameter contained in message Protocol error SCP exception SCP return error Report DP error CCF no answer for long time Release call from O-BCSM Release call from T-BCSM Subscriber request failed Caller number not matched Play announcement upon call drop
Check IMEI barring
Bearer Error
Release CCF normally Device unreserved for calling line identification restriction is not subscribed
Create terminal ticket
Interworking
Cause It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. The congestion results from insufficient resources in the MSC. This cause code may be generated in the following scenarios: The MSC lacks internal resources. Certain timers in the MSC expire. They cannot be used for timing. Some users register AOCC or AOCI service but there is no corresponding data configured in the MSC. During a test call made on a designated trunk circuit, the designated trunk circuit is used for synchronization or hosted by a faulty module. Trunk data configured on the MSC is incomplete. The timer in the MSC expires before the called number is received completely. The timer in the MSC expires before the callee answers the call. This cause code may be generated in the following scenarios: The called user does not answer the call for a long time. When interception is activated, the system sends IAM to the LIC and starts the T2 timer. The T2 timer expires before the LIC returns an ANM. The system releases the call. Some unspecific and temporary errors may occur in the system. This cause code may be generated in the following scenarios: Some timers in the MSC expire. They cannot be used for timing. Even though the times for call forwarding exceed the maximum forwarding times permitted, CFB or CFNRY is still activated. The MSC sends a STATUS to the MS. But the MS does not reply. After the timer expires, the MSC re-sends a STATUS but the MS still does not reply. It is not used currently. The callee does not return a Call connected message in a normal period of time. This cause code may be generated in the following scenarios: The timer in the originating MSC expires when the MSC waits for the RCH response. The timer in the originating MSC expires when the MSC obtains the TLDN from the VLR. The timer in the originating MSC expires when the MSC waits for a paging response. The timer in the originating MSC expires when the MSC waits for a Bearer setup message from the calling side. The timer in the originating MSC expires when the MSC waits for a Bearer setup message from the handoff side. During a test call made on a designated trunk circuit, a board requests another board to provide information about the circuit with a specific CIC, but the queried board does not return a response within the predefined time.
The MSC attempts to query the Called Number Barring Group table, but it does not receive a response within the predefined time. The VMSC does not receive an RCH response within the predefined time. In the CAMEL4 NP procedure, the wait for caller's subscription data times out. The callee does not return an Alerting response in a certain period of time. This cause code may be generated in the following scenario: The timer in the originating MSC expires when the MSC waits for an Alerting response from other NEs. The MSC does not receive a Call release message in a certain period of time. This cause code may be generated in the following scenarios: In caller release mode, after the callee sends a Release request, the originating MSC triggers the internal timer and sends an Alerting message to the callee. If the timer expires before the callee answers the call, the call is released. In callee release mode, after the caller sends a Release request, the terminating MSC triggers the internal timer and sends an Alerting message to the caller. If the timer expires before the caller answers the call, the call is released. After playing the failure tone that is configured in the local office, the system implements the call release flow mapped by the f ailure cause code. This cause code m ay be generated in the following scenario: After playing the failure tone (special information tone) configured in the local office, the system releases the call. The cause code CV22 indicates that the continuity check f ails. The following are exam ple scenarios of generating the cause code CV22: When the outgoing path fails the continuity check, the MSC repeats the call attempt with the cause code CV22 if the call is an ordinary call or releases t he call with the cause code CV22 if the call is handed over to another MSC. When the incoming path fails the continuity check, the MSC releases the call with the cause code CV22. For an outgoing call, the system selects routes for too many times and the times exceed the default upper threshold. This cause code may be generated in the following scenario: For an outgoing call, if the selected route is occupied by an incoming call, the system must select another route. However, if this route is still occupied by another call, the system must re-select a route for the third time. The system repeats selection until an available route is selected and the call is connected. If the number of repeat times exceeds the maximum reattempt times, the system releases the call. Before the callee is alerted, the caller hooks on the MS. This cause code may be generated in the following scenario: The caller hooks on the MS when the system waits for an Alerting response. Before the callee answers the call, the caller hooks on the MS. This cause code may be generated in the following scenario: The system sends an Alerting message but the callee does not answer the call. The caller hooks on the MS before the callee answers the call. The system restricts calls for users with certain attribute. This cause code may be generated in the following scenarios: If the PSTN does not support dialing test on trunks, calls for dialing test on specified trunks in the PSTN are restricted. For incoming trunks, tones are played by the LAI. During dialing test on specified trunk s, calls originated by users whose subscriber type is set to tester are restricted. If the software parameter prevents international roaming PPS subscribers from originating calls, calls originated by these subscribers are r estricted.
In a CCBS call procedure, if the destination numbers of the first call leg (an ordinary mobile-originated call) and the second call leg (a CCBS call) are changed to different numbers, the MSC generates CV26. The MSC generates the cause code CV26 when the query of the Tone Test Data table fails because the table is not configured. The MSC may become faulty. This cause code may be generated in the following scenarios: After the MSC sends an SRI to the HLR, the HLR does not reply in time due to link failure or HLR fault. The MSC sends INFORMATION to the callee for many times. Other MSC internal resources are not enough to support temporary traffic peak. The count of the times that the system reanalyzes the number is bigger than the maximum count set by the system (5 times). No IN subscriber number segment is configured for PPS users. The MSRN contained in an incoming call is not allocated by the VLR. After the MSCs switch over, the link for calls f ails. When the number re-analysis times exceeds the maximum allowable limit, the MSC generates CV27. The MSC generates CV27 when the query of t he Charging Control table fails during implementation of the AoC charging service, pulse-based charging service, and India charging service. It is not used currently. It is not used currently. The callee of an outgoing call is busy. This cause code may be generated in the f ollowing scenario: The callee served by another MSC is busy (for example, an inter-office STB message received by the TUP indicates that the callee is busy in a toll call). When Subscriber A calls Subscriber B, Subscriber B is engaged in a local call. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. In some special cases, the system restricts incoming calls. This cause code may be generated in the following scenario: The gateway office enables the call barring f unction. The cause code CV38 indicates that the hop count value obtained by the MSC is 0. The following is an example scenario of generating CV38: When a call is routed across more hops than allowed, the MSC generates CV38. The cause code CV39 indicates that the sequential ringing t imer expires. The following is an example scenario of generating CV39: The MSC generates CV39 when the timer of the internal call processing module expires during implementation of the sequential ringing service, a type of the One MSISDN Multiple SIMs service. The callee does not have TCSI data. This cause may be generated in the f ollowing case: The callee does not register the TCSI IN service. The Service attributein the User Service Attribute table or the IMSI Bit Analysis table, however, is set toTCSI protect. The caller does not have OCSI data. This cause may be generated in the following case: The caller does not register the OCSI-DP2 IN service. The Service attributein the User Service Attribute table or the IMSI Bit Analysis table or the Subscriber Integrated Service table, however, is set toOCSI protect.
The congested remote MSC sends a CGC message to the localMSOFTX3000. This cause code may be generated in the following scenario: TheMSOFTX3000receives a CGC message from another MSC. This cause code may be generated in the f ollowing scenario: An incorrect message is received over the incoming trunk before digits collection is completed. If an incoming call and an outgoing call select the same circuit, the route fails. If the number is not allocated, the system regards it as an invalid number. This cause code may be generated in the following scenarios: As the system fails to normalize the called number, the called number is regarded as an invalid number. When the system converts the called number, too many digits are inserted into the number. The length of the called number exceeds the maximum number length for analysis. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. It is not used currently. Certain modules in the MSC are unreachable. This cause code may be generated in the following scenario: Certain modules (for example, call control module) in the MSC are faulty. The call is released due to HTR calls. The device mapped by the DSP contained in the message that is sent from the MSC restricts calls. It is not used currently. It is not used currently. It is not used currently. It is not used currently. No CR resource is available. This cause code may be generated in the following case: CR resource allocation fails during an outgoing call. The CCB resources are insufficient in the MSC. This cause code may be generated in the following scenario: The CCB resources are used up. It is not used currently. It is not used currently. The cause code CV65 indicates that the outgoing PRA call fails. The following is an example scenario of generating CV65: During an outgoing PRA call, the query of the callee's subscription information indicates that the dialed number is not registered. It is not used currently. A call is abandoned before dialing. This cause code may be generated in the following scenario: The call is released by the caller. The cause code CV68 indicates that no dialing takes place within the predefined time. T he following is an example scenario of generating CV68: During a PRA call, the timer of the local or peer MSC expires before a digit is dialed.
A call is abandoned during dialing. This cause code may be generated in the following scenario: A call release message is received during digits collection for an incoming call. The inter-digits timer expires. This cause code may be generated in the following scenario: The next digit is not received within the required time over the incoming trunk. It is not defined curr ently. It is not defined curr ently. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: The allocation of radio resources is unsuccessful. It is not used currently. It is not used currently. In the feature of Black and white list restriction, the call right of the subscriber in the black list is limited. This cause code may be generated in the f ollowing scenario: In the gateway office, when a subscriber in the black list calls a subscriber who is not in the white list, the call is barred. The operation related to calling line identification (CLI) service fails. This cause code may be generated in the following scenarios: If a subscriber registering "reject incoming call" in the Caller Number Discrimination table originates a call, the system r eleases the call. If the length of the calling number does not meet the discrimination condition, the system releases the call. It is not used currently. It is not used currently. It is not used currently. The MSC fails to allocate an A-interface circuit for certain specific bearer service. This cause code may be generated in the following scenario: The circuit does not have a certain bearer capability, so the routing of the system fails. The MSC fails to allocate an A-interface circuit for a call. After the callee is alerted, the callee hooks on the MS. The closed user group (CUG) user does not register the CLI Restriction (CLIR) service. This cause code may be generated in the f ollowing scenario: As the CUG user does not register the CLIR service, the system cannot obtain the CLIR.CUG information. The attribute of CUG user is not saved in the HLR. This cause code may be generated in the following scenario: After the MSC sends an SRI message containing the caller CUG interlock index, the HLR returns an Unknown CUG index message. This cause code may be generated in the f ollowing scenarios: A call is rejected because the CUG subscription data of a subscriber does not contain the preferential CUG or the Outgoing Access (OA) and the caller side does not send the CUG information. A call is rejected because the CUG subscription data of a subscriber contains the OA but does not contain the preferential CUG, the caller side does not send the CUG information, but the data is configured to suppress the OA. A call is rejected because the CUG subscription data of a subscriber does not contain the preferential CUG or the OA, the caller side sends the CUG preference indication other than the CUG formation. Outgoing calls are barred within the CUG. This cause code may be generated in the following scenario: After the MSC sends an SRI message to the HLR, the HLR returns a CUG outgoing call barred message.
Incoming calls to the CUG are barred. This cause code may be generated in the following scenario: When handling a call from a subscriber outside a CUG group to a member of the group, the MSC receives from the HLR an SRI_ACK message that carries the cause value "USER ERROR" with the subvalue 5. CUG calls are rejected. This cause code may be generated in the following scenario: During a CUG call, the HLR responds to the MSC with an SRI_ACK message carrying a cause value "USER ERROR" with subvalue 7. The MAP m odule sends a release message with CC_CUG_SS_INTERACTION_VIOLATION to the CC module. A CUG call is barred and thus cannot be forwarded to another directory number. In this case, the MAP module sends a release message carrying a cause value "CC_CUG_SS_INTERACTION_VIOLATION" to the CC module. The CUG destination is incompatible or unreachable. This cause code m ay be generated in the following scenario: After the MSC sends an SRI message to the HLR, the HLR returns a CUG destination incompatible message. It is not used currently. It is not used currently. It is not used currently. This cause code may be generated in the f ollowing scenario: The Alerting message generated during the switching does not contain the internal switching information. It is not used currently. This cause code may be generated in the f ollowing scenario: The call duration time exceeds the upper threshold set by the system. It is not used currently. It is not defined curr ently. The system fails to process the number due to the format error of the number. This cause code may be generated in the following scenario: After the MSC sends an SRI message to the HLR, the HLR returns the SRI ACK message that carries "unidentifiedSubscriber", "unknownSubscriber" or "unallocatedNumber", indicating that the called number cannot be identified. The service attribute of the call isVoice recording by DTMF, and the system fails to query corresponding records when analyzing the called number. The callee does not answer the call after the MS is alerted, which results in the release of the call. This cause code m ay be generated in the following scenario: The mobile subscriber does not answer the call for a long time after the MS is alerted. The timer expires when the MSC waits for the CONNECT message from the callee. It means that the mobile subscriber registers the supplement service of barring all incoming calls (BAIC), which prohibits all incoming calls. This cause code may be generated in the following scenario: If the mobile subscriber registers the supplement service of barring all incoming calls, when this subscriber is called, the MSC releases the call directly. It means that the mobile subscriber registers the supplement service of barring all outgoing calls (BAOC), which prohibits all outgoing calls. This cause code may be generated in the following scenario: If the mobile subscriber registers the supplement service of barring all outgoing calls, when this subscriber originates a call, t he MSC releases the call directly. It means that when the callee fails to respond the paging, the system prompts that the callee is unreachable. This cause code may be generated in the following scenario:
The callee fails to respond when the MSC pages the callee. It is not used currently. It is not used currently. The system prompts that the callee is busy when the callee is in a conversation. This cause code may be generated in the following scenario: When the MSC pages the callee, the callee is busy. When the MSC pages the callee, the callee does not respond. The system prompts that the MS of callee is powered off when the MS of callee is powered off. This cause code may be generated in the following scenario: When the mobile subscriber is powered off. When the mobile subscriber is out of service area. It is not used currently. It is not used currently. This cause code may be generated in the f ollowing scenario: When the mobile subscriber originates an emergency call, the MSC releases the call after playing the announcement. This cause code may be generated in the f ollowing scenario: When the times of call forwarding exceed the permitted maximum value, the MSC releases the call. It is not used currently. It is not used currently. An error occurs when the system obtains the routing information about the called number during a call. This cause code m ay be generated in the following scenario: When the MSC sends an SRI message to the HLR, the HLR returns an SRI ACK message that carries the system failure information. It means that the operator determines the function of BAOC. This cause code may be generated in the following scenario: When the subscriber has no right to call, if this subscriber originates a call, the MSC releases the call directly. It means that the operator determines the function of barring all outgoing international calls (BOIC). This cause code may be generated in the following scenario: When the subscriber has no right to originate an international call, if this subscriber originates an international call, the MSC releases t he call directly. This cause code may be generated in the f ollowing scenario: When the subscriber registers and activates the supplement service function of BOIC, if the subscriber has no right t o originate an international call but this subscr iber originates an international call, the MSC releases the call directly. This cause code may be generated in the f ollowing scenario: When the subscriber registers and activates the supplement service of barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC for short), if this subscriber roams to another country and originates an international call (except the call to his home country), the MSC releases the call directly. This cause code may be generated in the f ollowing scenario: When the operator determines the supplement service of BOIC-exHC for the subscriber, if this subscriber roams t o another country and originates an international call (except t he call to his home country), the MSC releases the call directly. This cause code may be generated in the f ollowing scenario: When the operator determines the function of BAIC for the subscriber, if this subscriber is called, the MSC releases the call directly. This cause code may be generated in the f ollowing scenario:
When the operator determines the function of barring all calls to the entertainment station for the subscriber, if this subscriber originates a call to the entertainment station, the MSC releases the call directly. This cause code may be generated in the f ollowing scenario: When the operator determines the function of barring all calls to the information station for the subscriber, if this subscriber originates a call to the information station, the MSC releases the call directly. This cause code may be generated in the f ollowing scenario: When the callee does not respond or the system cannot forward the call to a specified subscriber, the system considers that the subscriber is out of service area by default. This cause code may be generated in the f ollowing scenario: When the operator determines the function of barring all outgoing national toll calls for the subscriber, if this subscriber originates a national toll call, the MSC releases the call directly. This cause code may be generated in the f ollowing scenario: When the account balance of any subscriber in conversation is not enough, the MSC plays announcement of last minute and releases the call directly. It is not used currently. This cause code may be generated in the f ollowing scenario: The MSC releases the call directly if some unknown errors occur during a call. It means the number that is not allocated in the HLR. This cause code may be generated in the following scenario: The MSC sends an SRI message to the HLR, and the HLR returns the SRI ACK message that carries "unidentifiedSubscriber", "unknownSubscriber" or "unallocatedNumber". During the automatic dialing test of trunk, the system selects one outgoing circuit and no calling side exists. In this case, the route selection code and route selection source code are null due to some causes, so the system releases the dialing test. After obtaining the data of the caller or the subscriber, when recording data, the system finds IMSI numbers which are not standard and then releases the call. It means that the system fails to obtain the route to the specified network during a call. This cause code may be generated in the following scenario: For the cell in which the caller or the callee is located, the system fails to query the cell information configured inADD BSC,ADD RNC,ADD LAIGCI, andADD LAISAI. The BSC sends the release message to the MSC after the MSC receives the paging response message. There is no route to a specified transit network. It means that the system fails to obtain the route to the specified network during a call. This cause code may be generated in the following scenario: This cause code may be generated in the f ollowing scenario: There is no route to specified terminal network. This cause code may be generated in the f ollowing scenario: System internal source assignment fails when the MF IN flow is triggered. Private signal tone is required in specific occasions. It is not used currently. The specified channel is unacceptable during a call. This cause code may be generated in the following scenario: During the dialing test on a circuit at the A interface, the system attempts to activate the early assignment process but fails. It is not used currently.
The operator determines the call barring for the subscriber. This cause code may be generated in the following scenario: The MSC releases certain calls according to the operator's decision. It is not used currently. This cause code may be generated in the f ollowing scenario: The interaction between the SSP and SCP fails during an IN call, which causes the processing mode of DCH as call releasing. It is not defined curr ently. It is not defined curr ently. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: In the MNP Service Prefix table,MNP processing typeis set toReleaseandFailure cause codeto142. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: The system clears the call normally. This cause code may be generated in the f ollowing scenario: The callee hooks on the phone after the MS is alerted. In this case, the MSC releases the call. It means that the callee does not answer the call after the MS is alerted, which results in the release of the call. This cause code may be generated in the following scenario: The timer expires when the MSC waits for the Call Confirmed message from the callee. The timer expires when the MSC waits for the Alerting message from the callee. It means that the callee does not answer the call after the MS is alerted, which results in the release of the call. This cause code may be generated in the following scenario: The timer expires when the MSC waits for the Connect message from the callee. It means that the called number does not exist. This cause code may be generated in the following scenario: The callee is powered off or the record of the callee in the HLR is cleared, which causes the failure to connect the call. This cause code may be generated in the f ollowing scenario: In processing normal call, ODB_BAIC and BAIC are provided for the callee. In processing international call, BOIC and BOIC_exHC are provided for the caller. In processing redirect call, redirect service is not provided for the callee. In processing forwarding call, forwarding times are more than the maximum. The callee is in black list. In processing rerouting, the module number is set incorrectly. If call forwarding is triggered when PFPH is active, the MSC releases the call with CV149. When call forwarding is implemented on CAMEL4 UCB call leg A, the MSC releases the call with CV149. When the received SRI_ACK message does not contain TCSI information of the PFPH callee, the MSC releases the call with CV149. Assume that the simultaneous ringing service, sequential ringing service, or CAMEL4 IN service is already active for a subscriber. If the simultaneous ringing service or sequential ringing service subscriber forwards an incoming call to another sequential ringing subscriber, the MSC releases the call with CV149. When a subscriber provisioned with the cell-based service restriction service makes or receives calls in an unauthorized cell, the MSC rej ects the calls with CV149. The local MSC receives a 410 response. T his cause code may be generated in the following scenario: :
The dialed number becomes permanently invalid. The system prompts that no SOSM circuit is available. This cause code may be generated in the following scenario: In triggering the monitor call, the system prompts that no SOSM circuit is available. This cause code may be generated in the f ollowing scenario: The software parameter is set to enable the anonymous call rejection (ACR) service. The caller has subscribed to the Calling Line Identification Restriction service; while the callee has subscribed to the ACR service but not to the Calling Line Identification Restriction Override service. It is not used currently. It is not used currently. The terminal error defined by the system results in the call failure. This cause code may be generated in the following scenario: In the VLR, the user information is deleted or logged out. The number is incomplete or of invalid format. This cause code may be generated in the following scenario: In processing the number analysis, an incomplete number is provided for the callee. In dialing the toll area code by the caller, the call is released. The service attribute of the call is configured as an illegal number, and then the system fails in analyzing the called number. This cause code may be generated in the f ollowing scenario: The call requires CLIR_CUG information, but the CLIR_CUG information is not provided for the subscriber. It is not used currently. A normal or unspecified situation. This cause code may be generated in the following scenario: The call is cleared by the system norm ally. It is not defined curr ently. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: The MSC has no free circuit. The allocation of circuits fails. This cause code may be generated in the f ollowing scenario: When the reroute times are less than the maximum, the system receives the message indicating that the peer office is unavailable. This cause code may be generated in the f ollowing scenario: When the reroute times are less than the maximum, the system receives the message indicating that no media gateway is available. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: The MSC sends the SRI information to the HLR, but the HLR does not reply in time. In this case, the link is faulty or the HLR is faulty. The load processed by the bill pool reaches the call barring threshold. When the system deals with the DN set and plays tones, the system fails to query the LAI table for a certain reason, for example, the LAI table is not configured with the tone playing index. The insufficient MSC internal resources cause the call failure. The system fails to obtain the VTCSI data from the VDB due to VDB failures. It is not defined curr ently. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: Certain internal timer expires. This cause code may be generated in the f ollowing scenario:
The switching devices corresponding to the CV13, CV27, CV42 and CV44 are congested. Errors occur on the switching devices. The remote failures are congested. The trunks are in contention. The cause code CV171 indicates that access infor mation is unavailable. The following is an example scenario of generating CV171: During UUS signaling exchange, the user-to-user information element sent by the peer device is invalid. This cause code may be generated in the f ollowing scenario: There is no free MSC circuit available. Allocating circuits fails. It is not defined curr ently. It is not used currently. This cause code may be generated in the f ollowing scenario: Certain internal resources such as t he call control table are f aulty. It is not defined curr ently. It is not used currently. This cause code may be generated in the f ollowing scenario: The subscriber simultaneously subscribes the AOCI and AOCC supplementary service. The subscriber set the CLIR service on his mobile phone, but he does not register the CLIR service in the HLR. If the subscriber originates a call, the MSC releases the call. It is not defined curr ently. It is not defined curr ently. It is not used currently. It is not defined curr ently. Incoming calls to a CUG are restricted. This cause code may be generated in the following scenario: During a CUG call, the HLR responds to the MSC with an SRI_ACK message that carry a cause value "USER ERROR" with subvalue 15 but does not carry the CUG reject cause. The MAP module then sends a release message with CC_CUG_INCOMING_CALL_BARRED to the CC module. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: The subscriber has not subscribed the bearer service, but originates a BS call. The tandem call barring function of BICC incoming and BICC outgoing is enabled. In this case, the call barring causes the release of the call. When make test calls through the A interface, the system checks that the calling side is not the BSC and then releases the call. This cause code may be generated in the f ollowing scenario: The transfer from the GSM bearer control to the ISDN bearer control fails, which results in the call failure. The MSC does not have certain special resource, for example the IWF. When the subscriber uses this resource, the MSC releases the call. IP Congestion and Office Param "Peer Office Support IP Congestion Rerouter" is chosen. It is not defined curr ently. It is not defined curr ently. It is not defined curr ently. It is not used currently. It is not defined curr ently. This cause code may be generated in the f ollowing scenario:
The MSC does not support som e services required by the subscriber. It is not used currently. This cause code may be generated in the f ollowing scenario: In the AOC service, the MSC sends the AOCI message to the subscriber. But the MS does not send reply to the MSC and the MSC releases the call. It is not used currently. This cause code may be generated in the f ollowing scenario: Allocating common call fails. The re-establishing for the CM service fails. The modifying for the Termination attribute fails. It is not used currently. It is not defined curr ently. It is not defined curr ently. It is not used currently. It is not used currently. It is not defined curr ently. It is not defined curr ently. It is not defined curr ently. It is not defined curr ently. This cause code may be generated in the f ollowing scenarios: A call is released because of the use of both dual BC and the Als line2 service. The retrieve operation is unsuccessful. It is not defined curr ently. This cause code may be generated in the f ollowing scenario: The local MSC receives a message that carries an invalid call reference through the trunk. This cause code may be generated in the f ollowing scenario: The local MSC receives a PRA RESTART message that indicates a blocked or suspended circuit. It is not used currently. This cause code may be generated in the f ollowing scenarios: The local MSC receives a PRA SUSPEND REQUEST message that carries a call identifier different from the recorded one. The following is an example scenarios of this cause code: The local MSC receives a PRA RECOVER message, but the call is not suspended. This cause code may be generated in the f ollowing scenario: The local MSC receives a PRA RECOVER message, but the call has been released. This cause code may be generated in the f ollowing scenario: A call from a non-CUG subscriber to a CUG subscriber is released becauseCUG special service number typeof the called number is set to Not special service number. This cause code may be generated in the f ollowing scenario: The subscriber originates the BS service, but the terminal does not support the BS service. It is not defined curr ently. It is not used currently. It is not used currently. All calls are smoothly released because of the activation of the ISTCOMMAND service. This cause code may be generated in the f ollowing scenario:
The local MSC receives an MP_CC_ISTCOMMAND message. All calls are smoothly released because of the activation of the ISTALERT service. This cause code may be generated in the following scenario: The local MSC receives an MP_CC_ISTALERT_RSP message. It is not defined curr ently. This cause code may be generated in the f ollowing scenarios: The local MSC receives an invalid facility message or fails to respond to the message. A CRG message carries incorrect charging-related inform ation elements. Segment-based charging fails because the incorrect segment number in a CRG message causes the failure of querying the Charging Segment Information table. Comprehensive charging fails because the incorrect charging information in a CRG message causes the failure of calculating the charging rate of the current segment or the failure of recording the detailed charging information about the next segment. A CRG message does not carry the segment number or detailed charging information. This cause code may be generated in the f ollowing scenario: The MSC receives message and checks some common information elements (IEs), but a mandatory IE is lost or its content is incorrect. This cause code may be generated in the f ollowing scenario: The MSC receives a message with a non-existent message type and the MSC releases the call. This cause code may be generated in the f ollowing scenario: The roaming information obtained by the system is not consistent with the actual roaming status. This cause code may be generated in the f ollowing scenario: The local MSC has received an ISUP message or a PRA message that carries unidentifiable or incorrect information elements. This cause code may be generated in the f ollowing scenario: The MSC receives message and checks some common IEs, but a mandatory IE is lost or its content is incorrect. This cause code may be generated in the f ollowing scenarios: The HOLD/RETRIVE message received by the local MSC is not compatible with the call status. The message the local MSC received from another MSC is not compatible with the call status. When the timer expires, it recovers to the initial status. This cause code may be generated in the following scenario: The following timers auto recover to the initial status after expiry. Call received Call present Disconnect Indication Release request Incoming call proceeding Connect Indication Modify request CC Connec. Pending CC-Est. Present CC-Est. Confirmed This cause code may be generated in the f ollowing scenario: The dialing test performed by the specified A interface fails because the parameter setting is wrong. It is not used currently. It is not used currently.
This cause code may be generated in the f ollowing scenario: In the telecom service TS and bearer service BS, when the switch creates the trunk bill of bearer transform, theCause for termination information changes. It is not used currently. It is not used currently. It is not defined curr ently. It is not used currently. This cause code may be generated in the f ollowing scenario: The protocol is wrong. It is not used currently. It is not used currently. It is not used currently. This cause code may be generated in the f ollowing scenario: When the DP is intra-reported, the CCF does not respond. In this case, the internal timer expires. It is not used currently. It is not used currently. It is not used currently. It is not used currently. This cause code may be generated in the f ollowing scenario: When in conversation, the caller or the callee is moved out of service and the MSC releases the call. This cause code may be generated in the f ollowing scenario: When the MSC needs to check the subscriber IMEI, but the IMEI is invalid and the MSC releases the call. This cause code may be generated in the f ollowing scenarios: The local MSC receives an ISUP message that carries a cause value "BCLIB_ABNORMAL_MIDDLE_BEARER_RELEASE_IND" or "BCLIB_LOGIC_TERM_ABORD" to indicate a bearer operation failure. This cause code is applicable to the scenario where a bearer error occurs. The reason might be that the resource request fails. It is not used currently. This cause code may be generated in the f ollowing scenario: The subscriber sets the CLIR service on his mobile phone, but he does not subscribe the CLIR service in the HLR. When the subscriber originates the call, the MSC releases this call. This cause code may be generated in the f ollowing scenario: When creating the first IN bill and the intermediate bill, the Cause for terminationinformation changes. Network interworking is unsuccessful. This cause code may be generated in the following scenarios: A request is not acknowledged within the required time. A response is incorrect because of network faults. The IWF cannot be activated. TheSpecial function listin the Service Check table is set toDisconnect when no charge, and the local MSC receives a response where the backward call indication is set to no charge.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
Unallocated (unassigned) number No route to specific transit network No route to destination Send special info tone Misdialed trunk prefix Channel unacceptable Call awarded and being delivered in established channel Preemption Preemption - circuit reserved for reuse 10 11 12 13 14 15 Normal call clearing User busy No user responding No answer from user (user alerted) Subscriber absent Call rejected Number changed 23 24 Exchange routing error Non-selected user clearing Destination out of order Invalid number format Facility rejected Response to STATUS ENQUIRY Normal, unspecified 32 33 No circuit/channel available 35 36 37 Network out of order Permanent frame mode connection out of service Permanent frame mode connection operational Temporary failure Switching equipment congestion Access information discarded Requested channel/circuit not available 45 Precedence call blocked Resources unavailable, unspecified
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94
48 Quality of service unavailable Requested facility not subscribed 51 52 Outgoing calls barred within CUG 54 Incoming calls barred within CUG 56 Bearer capability not authorized Bearer capability not presently available 59 60 61 Inconsistency in designed outg. access inf. and subscr. class Service or option not available, unspecified 64 Bearer capability not implemented Channel type not implemented 67 68 Requested facility not implemented Only restricted digital bearer cap. is available 71 72 73 74 75 76 77 78 Service or option not implemented, unspecified 80 Invalid call reference value Identified channel does not exist A suspended call exists, but this call identity does not Call identity in use No call suspended Call having the requested call identity has been cleared User not member of CUG Incompatible destination 89 Non-existing CUG Invalid transit network selection 92 93 94
