This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Dec DX cause
80 ext_in_ul_quality_c
81 ext_in_ul_strength_c
82 ext_in_dl_quality_c
83 ext_in_dl_strength_c
84 ext_in_distance_c
85 ext_in_o_and_m_inter_c
86 ext_in_resp_to_msc_invoc_c
87 ext_in_better_cell_c
88 ext_in_directed_retry_c
89 ext_in_unexpected_c
90 ext_in_switch_crc_pool_c
91 ext_in_pre_empt_c
92 ext_in_bsc_trho_c
93 ext_in_isho_c
100 ext_out_dl_rxlev_c
101 ext_out_ul_rxlev_c
102 ext_out_dl_rxqual_c
103 ext_out_ul_rxqual_c
104 ext_out_dl_interf_c
105 ext_out_ul_interf_c
106 ext_out_distance_c
107 ext_out_pbgt_ho_c
108 ext_out_umbrella_ho_c
109 ext_out_forced_ho_c
110 ext_out_dr_ho_c
111 ext_out_tr_ho_c
112 ext_out_idr_ho_c
113 ext_out_pre_empt_ho_c
114 ext_out_rap_fld_drop_c
115 ext_out_low_distance_c
116 ext_out_switch_crc_pool_c
117 ext_out_slow_moving_ms_c
118 ext_out_det_slow_mov_ms_c
119 ext_out_det_fast_mov_ms_c
120 inter_dl_rxlev_c
121 inter_ul_rxlev_c
122 inter_dl_rxqual_c
123 inter_ul_rxqual_c
124 inter_dl_interf_c
125 inter_ul_interf_c
126 inter_distance_c
127 inter_pbgt_ho_c
128 inter_umbrella_ho_c
129 inter_forced_ho_c
130 inter_dr_ho_c
131 inter_tr_ho_c
132 inter_idr_ho_c
133 inter_pre_empt_ho_c
134 inter_rap_fld_drop_c
135 inter_low_distance_c
136 inter_ok_ci_ratio_c
137 inter_bad_ci_ratio_c
138 inter_slow_moving_ms_c
139 inter_det_slow_mov_ms_c
140 intra_dl_interf_c
141 intra_ul_interf_c
142 intra_forced_ho_c
143 intra_dl_rxqual_c
144 intra_ok_ci_ratio_c
145 intra_bad_ci_ratio_c
146 intra_pre_empt_ho_c
147 intra_distance_c
148 intra_low_distance_c
149 intra_dr_ho_c
150 intra_direct_access
151 intra_gprs_ho_c
152 intra_ho_to_amr_hr_c
153 intra_ho_to_amr_fr_c
154 intra_inter_band_tch_c
155 intra_inter_band_sdc_c
156 inter_det_fast_mov_ms_c
157 inter_erfd_ho_c
158 inter_direct_access_c
159 inter_bsc_trho_c
160 inter_dadlb_c
163 ext_out_erfd_ho_c
164 ext_out_bsc_trho_c
166 intra_inter_bts_type_tch_c
167 intra_inter_bts_type_sdc_c
168 intra_ho_due_to_hscsd_c
169 intra_inter_band_due_lev_c
190 ext_out_isho_c
300 user_act_block_c
301 netw_act_block_c
302 bts_fail_block_c
303 lapd_fail_block_c
304 abis_fail_block_c
305 abis_msg_corrup_to_bts_ c
306 ass_fail_msg_c
307 block_slave_c
308 ch_act_nack_c
309 ch_act_nack_om_inter_c
310 ch_act_nack_equip_fail_c
311 ch_act_nack_encryp_alg_c
312 ch_act_nack_rad_ch_alr_a_c
313 ch_act_nack_serv_not_ava_c
314 ch_act_fail_c
315 conn_fail_c
316 conn_fail_rad_inf_fail_c
317 conn_fail_rad_link_fail_c
318 conn_fail_rem_trans_fail_c
319 data_ind_corrup_c
320 err_ind_c
321 estab_ind_fail_c
322 estab_conf_fail_c
323 ho_fail_c
324 ho_detect_fail_c
325 mode_mod_nack_c
326 mode_mod_ack_fail_c
327 no_meas_result_c
328 no_resp_from_copro_c
329 phy_cont_conf_fail_c
330 rcs_alg_start_ack_fail_c
331 rcs_alg_cl_ack_fail_c
332 rc0_disco_ind_c
333 rf_ch_rel_ack_fail_c
334 rel_ind_c
335 rel_ind_fail_c
336 signalling_error_c
337 state_confligt_c
338 type_confligt_c
339 forced_rel_c
340 rej_phantom_res_c
341 overload_c
342 abi_switchover_c
343 sapi_3_fail_c
344 paging_msg_fail_c
345 ch_required_fail_c
346 mode_mod_nack_equip_fail_c
347 mode_mod_nack_trc_rat_un_c
348 rrm_serv_req_nack_c
349 ch_mode_mod_fail_c
350 ass_fail_c
351 dr_fail_c
352 coprocess_fail_c
353 err_rep_enc_alg_not_imp_c
354 error_report_c
355 ch_act_nack_ch_mode_err_c
356 ch_act_nack_gen_ie_err_c
357 speech_version_unavail_c
358 ignored_double_rand_acc_c
359 rtsl_reconf_fail_c
360 ho_interrupted_c
361 downgrade_c
362 ho_not_started_c
363 conf_change_not_allowed_c
364 conf_change_bts_fail_c
365 conf_change_ms_fail_c
366 hscsd_copro_fail_c
367 sub_timer_c
368 forced_ho_block_c
369 upgrade_fail_c
370 estab_ind_corrupted_c
400 timing_advance_c
401 rrm_switch_crc_pool_c
402 rrm_speech_ver_unavail_c
403 rrm_bts_not_supporting_c
404 rrm_ms_not_supporting_c
405 rrm_invalid_cell_c
500 ho_not_allowed_c
501 no_radio_res_avail_c
502 restore_old_c
503 no_resp_from_coprocess_c
504 no_resp_to_radio_res_req_c
505 has_state_confligt_c
506 clear_cmd_not_received_c
507 ms_is_lost_c
508 no_resp_to_ho_cpl_msg_c
509 has_switchover_c
510 target_fail_c
511 source_fail_c
512 has_call_control_c
513 adj_cell_id_err_c
600 aiv_hand_act_fail_c
601 aiv_ssp_c
602 sccp_conn_fail_c
603 sccp_conn_timeout_c
604 sccp_release_c
606 global_reset_c
608 no_dtap_from_msc_c
609 ho_denied_assign_c
610 ho_denied_ciphering_c
611 ho_denied_clear_c
612 ho_denied_no_sccp_conn_c
613 T7_expiry_c
614 T10_expiry_c
615 aiv_crct_res_timeout_c
616 aiv_crct_conn_timeout_c
617 aiv_crct_disconn_timeout_c
618 aiv_crct_rel_timeout_c
619 aiv_timeout_c
620 act_ctrl_timeout_c
621 invalid_bssmap_msg_c
622 unknown_a_pcm_c
623 ho_denied_no_proper_crc_c
624 ch_type_mismatch
625 aiv_transc_or_rate_unava_c
626 aiv_speech_version_unava_c
627 aiv_pagin_refus_big_load_c
628 aiv_conn_refresh_timeout_c
629 aiv_conn_refresh_failed_c
700 rc0_hand_act_fail_c
701 a_crct_alr_res_c
702 a_crct_conn_err_c
703 rc0_crct_conn_timeout_c
704 access_out_of_crct_tbl_c
705 a_crct_rel_err_c
706 rc0_transc_or_rate unava_c
707 rc0_cip_type_mismatch_c
708 rc0_inv_msg_contents_c
709 rc0_req_speech_ver_unava_c
710 rc0_hunting_queue_full_c
711 rc0_a_crct_congestion_c
712 rc0_a_search_error_c
713 rc0_crct_pool_mismatch_c
714 rc0_rej_due_eme_call_c
715 rc0_ilc_file_error_c
800 a_tsl_user_mismatch_c
801 sc7_crct_res_timeout_c
802 sc7_crct_conn_timeout_c
803 sc7_crct_disconn_timeout_c
804 sc7_crct_rel_timeout_c
805 a_tsl_blocked_c
806 a_tsl_status_unknown_c
807 lsi_access_fail_c
808 scc_access_fail_c
809 undef_tsl_in_lsi_c
810 crct_equipment_fail_c
811 reset_crct_c
813 sc7_ssp_c
815 a_pcm_fault_c
817 a_crct_removed_c
819 a_et_state_change_c
900 m_radio_if_mess_fail_c
901 m_radio_if_fail_c
902 m_uplink_quality_c
903 m_uplink_strength_c
904 m_downlink_quality_c
905 m_downlink_strength_c
906 m_distance_c
907 m_o_and_m_inter_c
908 m_resp_to_msc_invoc_c
909 m_call_control_c
910 m_r_if_f_rev_to_old_c
911 m_handover_succ_c
912 m_better_cell_c
913 m_directed_retry_c
914 m_equipment_fail_c
915 m_no_radio_res_avail_c
916 m_req_terr_res_unava_c
917 m_cch_overload_c
918 m_processor_overload_c
919 m_bss_not_equipped_c
920 m_ms_not_eqipped_c
921 m_tr_cod_rat_ad_unav_c
922 m_ciph_alg_not_supp_c
923 m_terr_chan_alr_allc_c
924 m_prot_err_b_bsc_msc_c
926 m_invalid_cell_c
927 m_invalid_msg_cont_c
928 m_ie_or_field_missing_c
929 m_incorrect_value_c
930 m_unknown_msg_type_c
931 m_unknown_ie_c
933 m_cip_type_mismatch_c
934 m_switch_circuit_pool_c
935 m_speech_version_unavail_c
936 m_pre_empt_c
937 m_traffic_c
BSSMAP cause HEX DEC
Uplink quality 2 2
Uplink strength 3 3
Downlink quality 4 4
Downlink strength 5 5
Distance 6 6
O and M intervention 7 7
Response to MSC invocation 8 8
Better cell C 12
Directed retry D 13
Used if the cause of incoming external handover is not recognised or not mentioned at all
Switch circuit pool 32 50
Preemption 29 41
Traffic F 15
Used if the incoming external handover is an inter–system handover
Downlink strength 5 5
Uplink strength 3 3
Downlink quality 4 4
Uplink quality 2 2
Downlink quality 4 4
Uplink quality 2 2
Distance 6 6
Better cell C 12
Better cell C 12
O and M intervention 7 7
Directed retry D 13
Response to MSC invocation 8 8
Directed retry D 13
Response to MSC invocation 8 8
Uplink strength 3 3
Distance 6 6
Switch circuit pool 32 50
Better cell C 12
Better cell C 12
Better cell C 12
Downlink strength 5 5
Uplink strength 3 3
Downlink quality 4 4
Uplink quality 2 2
Downlink quality 4 4
Uplink quality 2 2
Distance 6 6
Better cell C 12
Better cell C 12
O and M intervention 7 7
Directed retry D 13
Response to MSC invocation 8 8
Directed retry D 13
Response to MSC invocation 8 8
Uplink strength 3 3
Distance 6 6
Downlink quality 4 4
Downlink quality 4 4
Better cell C 12
Better cell C 12
Downlink quality 4 4
Uplink quality 2 2
O and M intervention 7 7
Downlink quality 4 4
Downlink quality 4 4
Downlink quality 4 4
Response to MSC invocation 8 8
Distance 6 6
Distance 6 6
Directed retry D 13
Downlink strength 5 5
Traffic F 15
Better cell C 12
Better cell C 12
Traffic F 15
Traffic F 15
Better cell C 12
Better cell C 12
Downlink strength 5 5
Traffic F 15
Traffic F 15
Better cell C 12
Traffic F 15
Traffic F 15
Traffic F 15
Traffic F 15
Downlink strength 5 5
Traffic load 28 40
O and M intervention 7 7
O and M intervention 7 7
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Radio interface failure, rev to old ch A 10
Equipment failure 20 32
Radio interface failure 1 1
O and M intervention 7 7
Equipment failure 20 32
Ciphering algorithm not supported 40 64
No radio resource available 21 33
Req transc/rate adaption unavail 30 48
Equipment failure 20 32
Radio interface failure 1 1
Radio interface failure 1 1
Radio interface failure 1 1
Equipment failure 20 32
Radio interface message failure 0 0
Radio interface failure 1 1
Radio interface message failure 0 0
Radio interface message failure 0 0
Radio interface failure, rev to old ch A 10
Radio interface message failure 0 0
BSS not equipped 25 37
Radio interface message failure 0 0
Radio interface failure 1 1
Equipment failure 20 32
Radio interface message failure 0 0
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Radio interface failure 1 1
Radio interface failure 1 1
Radio interface message failure 0 0
Radio interface failure 1 1
Equipment failure 20 32
Equipment failure 20 32
Preemption 29 41
Radio interface message failure 0 0
CCCH overload 23 35
O and M intervention 7 7
Radio interface failure 1 1
Radio interface message failure 0 0
Radio interface message failure 0 0
Equipment failure 20 32
Req transc/rate adaption unavail 30 48
No radio resource available 21 33
Radio interface failure 1 1
Radio interface message failure 0 0
No radio resource available 21 33
Radio interface failure 1 1
Ciphering algorithm not supported 40 64
Radio interface failure 1 1
Req transc/rate adaption unavail 30 48
Radio interface message failure 0 0
Radio interface failure, rev to old ch A 10
Radio interface message failure 0 0
No radio resource available 21 33
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
BSS not equipped 25 37
Radio interface failure 1 1
Equipment failure 20 32
Equipment failure 20 32
O and M intervention 7 7
Equipment failure 20 32
Radio interface message failure 0 0
Distance 6 6
Switch circuit pool 32 50
Requested speech version unavailable 33 51
Req transc/rate adaption unavail 30 48
MS not equipped 26 38
Invalid cell 27 39
Call control 9 9
No radio resource available 21 33
Radio interface failure, rev to old ch A 10
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Radio interface message failure 0 0
Radio interface message failure 0 0
Equipment failure 20 32
O and M intervention 7 7
Call control 9 9
Call control 9 9
Call control 9 9
Invalid cell 27 39
Equipment failure 20 32
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Call control 9 9
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Protocol error betw BSC and MSC 60 96
Req terrestrial resource unavail 22 34
Call control 9 9
Invalid message contents 51 81
Req transc/rate adaption unavail 30 48
Invalid message contents 51 81
Call control 9 9
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Terr circuit already allocated 50 80
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Req transc/rate adaption unavail 30 48
Switch circuit pool 32 50
Invalid message contents 51 81
Requested speech version unavailable 33 51
Traffic load 28 40
Equipment failure 20 32
Traffic load 28 40
Equipment failure 20 32
Traffic load 28 40
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Equipment failure 20 32
Req terrestrial resource unavail 22 34
Req terrestrial resource unavail 22 34
Equipment failure 20 32
Equipment failure 20 32
Req terrestrial resource unavail 22 34
Equipment failure 20 32
Response to MSC invocation 8 8
Call control 9 9
Equipment failure 20 32
O and M intervention 7 7
O and M intervention 7 7
Radio interface message failure 0 0
Radio interface failure 1 1
Uplink quality 2 2
Uplink strength 3 3
Downlink quality 4 4
Downlink strength 5 5
Distance 6 6
O and M intervention 7 7
Response to MSC invocation 8 8
Call control 9 9
Radio interface failure, rev to old ch A 10
Handover successful B 11
Better cell C 12
Directed retry D 13
Equipment failure 20 32
No radio resource available 21 33
Req terrestrial resource unavail 22 34
CCCH overload 23 35
Processor overload 24 36
BSS not equipped 25 37
MS not equipped 26 38
Req transc/rate adaption unavail 30 48
Ciphering algorithm not supported 40 64
Terr circuit already allocated 50 80
Protocol error betw BSC and MSC 60 96
Invalid cell 27 39
Invalid message contents 51 81
Information elem or field missing 52 82
Incorrect value 53 83
Unknown message type 54 84
Unknown information element 55 85
Circuit pool mismatch 31 49
Switch circuit pool 32 50
Requested speech version unavail 33 51
Preemption 29 41
Traffic F 15
BSSMAP cause HEX DX cause
RADIO INTERFACE MESSAGE FAILURE 0x00 data_ind_corrup_c
estab_ind_fail_c
estab_conf_fail_c
ho_detect_fail_c
mode_mod_ack_fail_c
phy_cont_conf_fail_c
rel_ind_fail_c
rej_phanton_res_c
paging_msg_fail_c
ch_required_fail_c
ass_fail_c
ch_act_nack_gen_err_c
ignored_double_rand_acc_c
estab_ind_corrupted_c
clear_cmd_not_received_c
ms_is_lost_c
m_radio_if_mess_fail_c
RADIO INTERFACE FAILURE 0x01 ch_act_nack_c
conn_fail_c
conn_fail_rad_inf_fail_c
conn_fail_rad_link_fail_c
err_ind_c
no_meas_result_c
rf_ch_rel_ack_fail_c
rel_ind_c
signalling_error_c
sapi_3_fail_c
ch_mode_mod_fail_c
coprocess_fail_c
error_report_c
conf_change_ms_fail_c
m_radio_if_fail_c
UPLINK QUALITY 0x02 ext_out_ul_quality_c
ext_out_ul_rxqual_c
ext_out_ul_interf_c
inter_ul_rxqual_c
inter_ul_interf_c
intra_ul_interf_c
m_uplink_quality_c
UPLINK STRENGTH 0x03 ext_in_ul_strength_c
ext_out_ul_rxlev_c
ext_out_rap_fld_drop_c
inter_ul_rxlev_c
inter_rap_fld_drop_c
m_uplink_strength_c
DOWNLINK QUALITY 0x04 ext_in_dl_quality_c
ext_out_dl_rxqual_c
ext_out_dl_interf_c
inter_dl_rxqual_c
inter_dl_interf_c
inter_ok_ci_ratio_c
inter_bad_ci_ratio_c
intra_dl_interf_c
intra_dl_rxqual_c
intra_ok_ci_ratio_c
intra_bad_ci_ratio_c
m_downlink_quality_c
DOWNLINK STRENGTH 0x05 ext_in_dl_strength_c
ext_out_dl_rxlev_c
inter_dl_rxlev_c
intra_direct_access_c
inter_direct_access_c
intra_inter_band_due_lev_c
m_downlink_strength_c
DISTANCE 0x06 ext_in_distance_c
ext_out_distance_c
ext_out_low_distance_c
inter_distance_c
inter_low_distance_c
intra_distance_c
intra_low_distance_c
timing_advance_c
m_distance_c
O AND M INTERVENTION 0x07 ext_in_o_and_m_inter_c
ext_out_forced_ho_c
inter_forced_ho_c
intra_forced_ho_c
user_act_block_c
netw_acct_block_c
ch_act_nack_om_inter_c
abi_switchover_c
forced_ho_block_c
has_switchover_c
a_crct_removed_c
a_et_state_change_c
m_o_and_m_inter_c
RESPONSE TO MSC INVOCATION 0x08 ext_in_resp_to_msc_invoc_c
ext_out_tr_ho_c
ext_out_pre_empt_ho_c
inter_tr_ho_c
inter_pre_empt_ho_c
intra_pre_empt_ho_c
reset_crct_c
m_resp_to_msc_invoc_c
CALL CONTROL 0x09 ho_not_allowed_c
target_fail_c
source_fail_c
has_call_control_c
aiv_ssp_c
sccp_conn_fail_c
sccp_conn_timeout_c
sccp_release_c
global_reset_c
no_dtap_from_msc_c
ho_denied_assign_c
ho_denied_ciphering_c
ho_denied_clear_c
ho_denied_no_sccp_conn_c
T7_expiry_c
ho_denied_no_proper_crc_c
aiv_pagin_refus_big_load_c
sc7_ssp_c
m_call_control_c
RADIO INTERFACE FAILURE, REVERSION TO OLD CHANNEL 0x0A ass_fail_msg_c
ho_fail_c
restore_old_c
m_r_if_f_rev_to_old_c
HANDOVER SUCCESSFULL 0x0B m_handover_succ_c
BETTER CELL 0x0C ext_in_better_cell_c
ext_out_pbgt_ho_c
ext_out_umbrella_ho_c
ext_out_slow_moving_ms_c
ext_out_det_slow_mov_ms_c
ext_out_det_fast_mov_ms_c
inter_pbgt_ho_c
inter_umbrella_ho_c
inter_slow_moving_ms_c
inter_det_slow_mov_ms_c
intra_ho_to_amr_hr_c
intra_ho_to_amr_fr_c
inter_erfd_ho_c
ext_out_erfd_ho_c
m_better_cell_c
DIRECTED RETRY 0x0D ext_in_directed_retry_c
ext_out_dr_ho_c
ext_out_idr_ho_c
inter_dr_ho_c
inter_idr_ho_c
intra_dr_ho_c
m_directed_retry_c
TRAFFIC 0x0F ext_in_bsc_trho_c
intra_gprs_ho_c
intra_inter_band_tch_c
intra_inter_band_sdc_c
inter_bsc_trho_c
inter_dadlb_c
ext_out_bsc_trho_c
intra_inter_bts_type_tch_c
intra_inter_bts_type_sdc_c
intra_ho_due_to_hscsd_c
m_traffic_c
EQUIPMENT FAILURE 0x20 bts_fail_block_c
lapd_fail_block_c
abis_fail_block_c
abis_msg_corrup_to_bts_c
block_slave_c
ch_act_nack_equip_fail_c
ch_act_fail_c
conn_fail_rem_trans_fail_c
no_resp_from_copro_c
rcs_alg_start_ack_fail_c
rcs_alg_cl_ack_fail_c
rc0_disco_ind_c
state_confligt_c
type_confligt_c
mode_mod_nack_equip_fail_c
ho_interrupted_c
downgrade_c
ho_no_started_c
conf_change_not_allowed_c
hscsd_copro_fail_c
sub_timer_c
upgrade_fail_c
no_resp_from_coprocess_c
no_resp_to_radio_res_req_c
has_state_confligt_c
no_resp_to_ho_cpl_msg_c
aiv_hand_act_fail_c
T10_expiry_c
aiv_crct_res_timeout_c
aiv_crct_conn_timeout_c
aiv_crct_disconn_timeout_c
aiv_crct_rel_timeout_c
aiv_timeout_c
act_ctrl_timeout_c
aiv_conn_refresh_timeout_c
aiv_conn_refresh_failed_c
rc0_hand_act_fail_c
a_crct_conn_err_c
rc0_crct_conn_timeout_c
access_out_of_crct_tbl_c
a_crct_rel_err_c
rc0_a_crct_congestion_c
rc0_crct_pool_mismatch_c
rc0_ilc_file_error_c
a_tsl_user_mismatch_c
sc7_crct_res_timeout_c
sc7_crct_conn_timeout_c
sc7_crct_disconn_timeout_c
sc7_crct_rel_timeout_c
lsi_access_fail_c
scc_access_fail_c
crct_equipment_fail_c
a_pcm_fault_c
m_equipment_fail_c
NO RADIO RESOURCE AVAILABLE 0x21 ch_act_nack_rad_ch_alr_a_c
INFORMATION ELEMENT OF FIELD MISSING 0x52 m_ie_or_field_missing_c
INCORRECT VALUE 0x53 m_incorrect_value_c
UNKNOWN MESSAGE TYPE 0x54 m_unkown_msg_type_c
UNKNOWN INFORMATION ELEMENT 0x55 m_unknown_ie_c
PROTOCOL ERROR BETWEEN BSC AND MSC 0x60 invalid_bssmap_msg_c
m_prot_err_b_bsc_msc_c
319
321
322
324
326
329
335
340
344
345
350
356
358
370
506
507
900
308
315
316
317
320
327
333
334
336
343
349
352
354
365
901
80
103
105
123
125
141
902
81
101
114
121
134
903
82
102
104
DEC
122
124
136
137
140
143
144
145
904
83
100
120
150
158
169
905
84
106
115
126
135
147
148
400
906
85
109
129
142
300
301
309
342
368
509
817
819
907
86
111
113
131
133
146
811
908
500
510
511
512
601
602
603
604
606
608
609
610
611
612
613
623
627
813
909
306
323
502
910
911
87
107
108
117
118
119
127
128
138
139
152
153
157
163
912
88
110
112
130
132
149
913
92
151
154
155
159
160
164
166
167
168
937
302
303
304
305
307
310
314
318
328
330
331
332
337
338
346
360
361
362
363
366
367
369
503
504
505
508
600
614
615
616
617
618
619
620
628
629
700
702
703
704
705
711
713
715
800
801
802
803
804
807
808
810
815
914
312
348
351
359
501
915
622
805
806
809
916
341
917
918
325
364
919
404
920
405
926
190
710
712
714
91
339
936
313
347
355
403
625
706
921
933
90
116
401
707
934
402
709
935
311
353
922
701
923
624
626
708
927
928
929
930
931
621
924
Counter description Counter
Number of SDCCH transaction failures due to BSS failure 1002
Number of SDCCH transaction failures due to a radio failure (incremented only in phases 1-8) 1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1003
1004
1004
1004
1004
1004
1004
1004
1004
1004
1004
1004
1004
1004
1005
1005
1005
1005
1005
1005
1005
1005
1005
1005
1005
1005
Number of SDCCH transaction failures due to a radio failure of the old channel during and SDCCH-SDCCH or SDCCH-TCH handover (incremented only in phases 9–11)
Number of SDCCH transaction failures due to a radio failure of the new channel during a SDCCH handover (incremented only in phases 12-14)
1005
1005
1005
Number of radio TCH transactions ended due to BSS problems 1012
Number of radio TCH transactions ended due to a radio failure (incremented only in phases 1-8, 15) 1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1013
1014
1014
1014
1014
1014
1014
1014
1014
1014
1014
1014
1014
1014
1015
1015
1015
1015
1015
1015
1015
1015
1015
1015
Number of radio TCH ansactions ended due to a radio failure of the old channel during a HO on a TCH (incremented only in phases 9-11)
Number of radio TCH transactions ended due to a radio failure of the new channel during a HO on a TCH (incremented only in phases 12-14)
1015
1015
1015
1015
1015
Number of SDCCH transaction failures due to an activation failure 1027
Number of radio TCH transactions ended due to an activation failure 1028
1029
1030
1031
Number of SDCCH transaction failures due to Abis interface failure 1033
Number of SDCCH transaction failures due to A interface failure 1034
Number of SDCCH transaction failures due to a LAPD failure 1035
Number of SDCCH transaction failures due to a BTS failure 1036
Number of SDCCH transaction failures due to user actions 1037
Number of SDCCH transaction failures due to radio network reconfiguration actions 1039
Number of TCH transaction failures due to an Abis interface failure 1045
Number of TCH transaction failures due to a LAPD failure 1046
Number of TCH transaction failures due to a BTS failure 1047
Number of TCH transaction failures due to user actions 1048
Number of TCH transaction failures due to radio network reconfiguration actions 1050
Number of TCH transaction failures due to an A interface failure 1051
1072
1072
1072
1072
1072
1072
1072
1072
1072
1072
1072
1072
1072
1072
1072
1074
1074
1074
1074
1074
Number of radio TCH transactions ended due to a transcoder failure (incremented only in phases 1-8, 15)
Number of radio TCH transactions ended due to a transcoder failure of the old channel during a HO on a TCH (incremented only in phases 9-11)
Number of radio TCH transactions ended due to a transcoder failure of the new channel during a HO on a TCH (incremented only in phases 12-14)
Number of SDCCH transaction failures due to an activation failure during call (incremented only in phases 1-8)
Number of SDCCH transaction failures due to an activation failure of the new channel during an SDCCH handover (incremented only in phases 12-14)
1074
1074
1074
1074
1074
1074
1074
1074
1074
1074
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1075
1076
1076
1076
1076
1076
1076
1076
1076
1076
1076
1076
1076
1076
1076
Number of SDCCH transaction failures due to an Abis interface failure during call (incremented only in phases 1-8)
Number of SDCCH transaction failures due to an Abis interface failure on the old channel during SDCCH-SDCCH or SDCCH-TCH handover (incremented only in phases 9-11)
1076
1076
1076
1076
1076
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1077
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
Number of SDCCH transaction failures due to an Abis interface failure on the new channel during SDCCH-SDCCH or SDCCH-TCH handover (incremented only in phases 12-14)
Number of SDCCH transaction failures due to an A interface failure during call attempt (incremented only in phases 1-8)
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1078
1079
1079
1079
1079
1079
1079
1079
1079
Number of SDCCH transaction failures due to an A interface failure on the old channel during SDCCH-SDCCH or SDCCH-TCH handover (incremented only in phases 9-11)
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1079
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
Number of SDCCH transaction failures due to an A interface failure on the new channel during and SDCCH handover (incremented only in phases 12-14)
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1080
1081
1081
1081
1081
1081
1081
1081
1081
1081
1081
1081
1081
1081
1081
1081
1083
1083
1083
1083
1083
1083
1083
1083
1083
1083
1083
1083
1083
1083
1083
Number of radio TCH transactions ended due to an activation failure during call attempt (incremented only in phases 1-8)
Number of radio TCH transactions ended due to an activation failure on the new channel during an SDCCH-TCH or TCH-TCH handover (incremented only in phases 12-14)
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1084
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1085
1086
1086
1086
1086
Number of TCH transaction failures due to an Abis interface failure during call (incremented only in phases 1-8, 15)
Number of TCH transaction failures due to an Abis interface failure on the old channel during a TCH handover (incremented only in phases 9-11)
Number of TCH transaction failures due to an Abis interface failure on the new channel during a TCH handover (incremented only in phases 12-14)
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1086
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
Number of TCH transaction failures due to an A interface failure during call (incremented only in phases 1-8, 15)
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1087
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
Number of TCH transaction failures on the old channel due to an A interface failure during handover attempt (incremented only in phases 9-11)
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1088
1089
1089
1089
1089
1089
1089
Number of TCH transaction failures on the new channel due to an A interface failure during handover attempt (incremented only in phases 12-14)
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1089
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1139
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
Number of TCH releases due to radio failures in call set-up phase before connect acknowledgement (incremented only in phases 2, 3, 5, 8–14)
Number of the TCH releases due to BSS failures in call set-up phase before connect acknowledgement (incremented only in phases 2, 3, 5, 8–14)
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
1140
DX cause DEC
This is a sum of the counters 1033, 1034, 1035, 1036
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ho_detect_fail_c 324
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
conf_change_ms_fail_c 365
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
target_fail_c 510
source_fail_c 511
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
target_fail_c 510
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ho_detect_fail_c 324
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
conf_change_ms_fail_c 365
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
source_fail_c 511
This is a sum of the counters 1045, 1046, 1047, 1051
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ho_detect_fail_c 324
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
conf_change_ms_fail_c 365
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
target_fail_c 510
source_fail_c 511
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
target_fail_c 510
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ho_detect_fail_c 324
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
conf_change_ms_fail_c 365
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
source_fail_c 511
This is a sum of the counters 1072, 1074
This is a sum of the counters 1081, 1083
conn_fail_rem_trans_fail_c 318
conn_fail_rem_trans_fail_c 318
conn_fail_rem_trans_fail_c 318
This is a sum of the counters 1075, 1076, 1077
This is a sum of the counters 1078, 1079, 1080
lapd_fail_block_c 303
bts_fail_block_c 302
user_act_block_c 300
netw_act_block_c 301
This is a sum of the counters 1084, 1085, 1086
lapd_fail_block_c 303
bts_fail_block_c 302
user_act_block_c 300
netw_act_block_c 301
This is a sum of the counters 1087, 1088, 1089
ch_act_nack_c 308
ch_act_nack_om_inter_c 309
ch_act_nack_equip_fail_c 310
ch_act_nack_encryp_alg_c 311
ch_act_nack_rad_ch_alr_a_c 312
ch_act_nack_serv_not_ava_c 313
mode_mod_nack_c 325
mode_mod_nack_equip_fail_c 346
mode_mod_nack_trc_rat_un_c 347
err_rep_enc_alg_not_imp_c 353
ch_act_nack_ch_mode_err_c 355
ch_act_nack_gen_ie_err_c 356
speech_version_unavail_c 357
conf_change_bts_fail_c 364
rrm_speech_ver_unavail_c 402
ch_act_nack_c 308
ch_act_nack_om_inter_c 309
ch_act_nack_equip_fail_c 310
ch_act_nack_encryp_alg_c 311
ch_act_nack_rad_ch_alr_a_c 312
ch_act_nack_serv_not_ava_c 313
mode_mod_nack_c 325
mode_mod_nack_equip_fail_c 346
mode_mod_nack_trc_rat_un_c 347
err_rep_enc_alg_not_imp_c 353
ch_act_nack_ch_mode_err_c 355
ch_act_nack_gen_ie_err_c 356
speech_version_unavail_c 357
conf_change_bts_fail_c 364
rrm_speech_ver_unavail_c 402
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
sub_timer_c 367
estab_ind_corrupted_c 370
has_state_confligt_c 505
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
estab_ind_corrupted_c 370
has_state_confligt_c 505
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
sub_timer_c 367
estab_ind_corrupted_c 370
has_state_confligt_c 505
rc0_disco_ind_c 332
rrm_switch_crc_pool_c 401
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equpment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_equipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing_c 928
m_incorrect_value_c 929
m_unknown_msg_type_c 930
m_unknown_ie 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
rc0_disco_ind_c 332
rrm_switch_crc_pool_c 401
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equpment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_equipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing 928
m_incorrect_value 929
m_unknown_msg_type 930
m_unknown_ie 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
rc0_disco_ind_c 332
rrm_switch_crc_pool_c 401
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equpment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_equipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing_c 928
m_incorrect_value_c 929
m_unknown_msg_type_c 930
m_unknown_ie_c 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
ch_act_nack_c 308
ch_act_nack_om_inter_c 309
ch_act_nack_equip_fail_c 310
ch_act_nack_encryp_alg_c 311
ch_act_nack_rad_ch_alr_a_c 312
ch_act_nack_serv_not_ava_c 313
mode_mod_nack_c 325
mode_mod_nack_equip_fail_c 346
mode_mod_nack_trc_rat_un_c 347
err_rep_enc_alg_not_imp_c 353
ch_act_nack_ch_mode_err_c 355
ch_act_nack_gen_ie_err_c 356
speech_version_unavail_c 357
conf_change_bts_fail_c 364
rrm_speech_ver_unavail_c 402
ch_act_nack_c 308
ch_act_nack_om_inter_c 309
ch_act_nack_equip_fail_c 310
ch_act_nack_encryp_alg_c 311
ch_act_nack_rad_ch_alr_a_c 312
ch_act_nack_serv_not_ava_c 313
mode_mod_nack_c 325
mode_mod_nack_equip_fail_c 346
mode_mod_nack_trc_rat_un_c 347
err_rep_enc_alg_not_imp_c 353
ch_act_nack_ch_mode_err_c 355
ch_act_nack_gen_ie_err_c 356
speech_version_unavail_c 357
conf_change_bts_fail_c 364
rrm_speech_ver_unavail_c 402
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
sub_timer_c 367
estab_ind_corrupted_c 370
has_state_confligt_c 505
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
estab_ind_corrupted_c 370
has_state_confligt_c 505
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
sub_timer_c 367
estab_ind_corrupted_c 370
has_state_confligt_c 505
rc0_disco_ind_c 332
rrm_switch_crc_pool_c 401
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equpment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_equipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing_c 928
m_incorrect_value_c 929
m_unknown_msg_type_c 930
m_unknown_ie_c 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
rc0_disco_ind_c 332
rrm_switch_crc_pool_c 401
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equpment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_equipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing_c 928
m_incorrect_value_c 929
m_unknown_msg_type_c 930
m_unknown_ie_c 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
rc0_disco_ind_c 332
rrm_switch_crc_pool_c 401
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equpment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_equipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing_c 928
m_incorrect_value_c 929
m_unknown_msg_type_c 930
m_unknown_ie_c 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
ass_fail_msg_c 306
conn_fail_c 315
conn_fail_rad_inf_fail_c 316
conn_fail_rad_link_fail_c 317
err_ind_c 320
ho_fail_c 323
ho_detect_fail_c 324
ch_mode_mod_fail_c 349
ass_fail_c 350
error_report_c 354
conf_change_ms_fail_c 365
timing_advance_c 400
no_resp_from_coprocess_c 503
ms_is_lost_c 507
target_fail_c 510
source_fail_c 511
bts_fail_block_c 302
lapd_fail_block_c 303
abis_fail_block_c 304
abis_msg_corrup_to_bts_c 305
block_slave_c 307
ch_act_fail_c 314
data_ind_corrup_c 319
estab_ind_fail_c 321
estab_conf_fail_c 322
mode_mod_ack_fail_c 326
no_meas_result_c 327
no_resp_from_copro_c 328
phy_cont_conf_fail_c 329
rcs_alg_start_ack_fail_c 330
rcs_alg_cl_ack_fail_c 331
rc0_disco_ind_c 332
rf_ch_rel_ack_fail_c 333
rel_ind_fail_c 335
signalling_error_c 336
sapi_3_fail_c 343
sub_timer_c 367
estab_ind_corrupted_c 370
rrm_switch_crc_pool_c 401
has_state_confligt_c 505
clear_cmd_not_received_c 506
no_resp_to_ho_cpl_msg_c 508
aiv_hand_act_fail_c 600
aiv_ssp_c 601
sccp_conn_fail_c 602
sccp_conn_timeout_c 603
sccp_release_c 604
global_reset_c 606
no_dtap_from_msc_c 608
ho_denied_assign_c 609
ho_denied_ciphering_c 610
ho_denied_clear_c 611
ho_denied_no_sccp_conn_c 612
T7_expiry_c 613
T10_expiry_c 614
aiv_crct_res_timeout_c 615
aiv_crct_conn_timeout_c 616
aiv_crct_disconn_timeout_c 617
aiv_crct_rel_timeout_c 618
aiv_timeout_c 619
act_ctrl_timeout_c 620
invalid_bssmap_msg_c 621
unknown_a_pcm_c 622
ho_denied_no_proper_crc_c 623
ch_type_mismatch_c 624
aiv_transc_or_rate_unava_c 625
aiv_speech_version_unava_c 626
aiv_conn_refresh_timeout_c 628
aiv_conn_refresh_failed_c 629
rc0_hand_act_fail_c 700
a_crct_alr_res_c 701
a_crct_conn_err_c 702
rc0_crct_conn_timeout_c 703
access_out_of_crct_tbl_c 704
a_crct_rel_err_c 705
rc0_transc_or_rate_unava_c 706
rc0_cip_type_mismatch_c 707
rc0_inv_msg_contents_c 708
rc0_req_speech_ver_unava_c 709
rc0_hunting_queue_full_c 710
rc0_a_crct_congestion_c 711
rc0_a_search_error_c 712
rc0_crct_pool_mismatch_c 713
rc0_rej_due_eme_call_c 714
rc0_ilc_file_error_c 715
a_tsl_user_mismatch_c 800
sc7_crct_res_timeout_c 801
sc7_crct_conn_timeout_c 802
sc7_crct_disconn_timeout_c 803
sc7_crct_rel_timeout_c 804
a_tsl_blocked_c 805
a_tsl_status_unknown_c 806
lsi_access_fail_c 807
scc_access_fail_c 808
undef_tsl_in_lsi_c 809
crct_equipment_fail_c 810
reset_crct_c 811
sc7_ssp_c 813
a_pcm_fault_c 815
a_crct_removed_c 817
a_et_state_change_c 819
m_radio_if_mess_fail_c 900
m_radio_if_fail_c 901
m_uplink_quality_c 902
m_uplink_strength_c 903
m_downlink_quality_c 904
m_downlink_strength_c 905
m_distance_c 906
m_o_and_m_inter_c 907
m_resp_to_msc_invoc_c 908
m_r_if_f_rev_to_old_c 910
m_handover_succ_c 911
m_better_cell_c 912
m_directed_retry_c 913
m_equipment_fail_c 914
m_no_radio_res_avail_c 915
m_req_terr_res_unava_c 916
m_cch_overload_c 917
m_processor_overload_c 918
m_bss_not_equipped_c 919
m_ms_not_eqipped_c 920
m_tr_cod_rat_ad_unav_c 921
m_ciph_alg_not_supp_c 922
m_terr_chan_alr_allc_c 923
m_prot_err_b_bsc_msc_c 924
m_unexpected_c 925
m_invalid_cell_c 926
m_invalid_msg_cont_c 927
m_ie_or_field_missing_c 928
m_incorrect_value_c 929
m_unknown_msg_type_c 930
m_unknown_ie_c 931
m_transc_or_rate_unavail_c 932
m_cip_type_mismatch_c 933
m_switch_crc_pool_c 934
m_speech_version_unavail_c 935
m_pre_empt_c 936
m_traffic_c 937
DX causes of Call related DX causes in BSC
The DX cause contains a field for the phase and the cause. The cause element of the DX cause is set by the different program blocks which offer services for the call setup and handover features. The causes are set as follows:
1. The MS receives access to the network with the relevant establishment cause (success cause).
2. The handover starts with the relevant handover cause (success cause).
3. A failure has occurred during the call or handover (failure cause).
These cases are divided into two different cause classes which are called success and failure causes. The DX causes are conveyed within the internal signalling message.
Success causes
The meanings of the success causes are represented below:
1. location_update (10)
The location update.
2. facch_emergency_call (20)
The FACCH calls for which the establishment cause is an emergency call.
3. facch_reestablishment (21)
The FACCH calls for which the establishment cause is re-establishment.
4. facch_answer_to_pagin (22)
The FACCH calls for which the establishment cause is answering to paging.
5. facch_mo_speech_call (23)
The FACCH calls for which the establishment cause is a mobile originating speech call.
6. facch_mo_data_call (24)
The FACCH calls for which the establishment cause is a mobile originating data call.
7. facch_other_procedure (25)
The FACCH calls for which the establishment cause is another procedure.
8. facch_mt_data_call (26)
The FACCH calls for which the establishment cause is a mobile terminating data call.
9. facch_imsi_detach (27)
10. basic_emergency_call (40)
The basic calls for which the establishment cause is an emergency call.
11. basic_reestablishment (41)
The basic calls for which the establishment cause is re-establishment.
12. basic_answer_to_pagin (42)
The basic calls for which the establishment cause is answering to paging.
13. basic_mo_speech_call (43)
The basic calls for which the establishment cause is a mobile originating speech call.
14. basic_mo_data_call (44)
The basic calls for which the establishment cause is a mobile originating data call.
15. basic_other_procedure (45)
The basic calls for which the establishment cause is another procedure.
16. basic_mt_data_call (46)
The basic calls for which the establishment cause is a mobile terminating data call.
17. basic_imsi_detach (47)
Number of IMSI detaches on the SDCCH channel.
18. ext_in_ul_quality (80)
The incoming external handover. The handover setup cause is uplink quality.
19. ext_in_ul_strength (81)
An incoming external handover. The handover setup cause is uplink strength.
20. ext_in_dl_quality (82)
An incoming external handover. The handover setup cause is downlink quality.
21. ext_in_dl_strength (83)
An incoming external handover. The handover setup cause is downlink strength.
Number of IMSI detaches on the TCH channel due to SDCCH congestion.
An incoming external handover. The handover setup cause is distance.
23. ext_in_o_and_m_inter (85)
24. ext_in_resp_to_msc_invoc (86)
An incoming external handover. The handover setup cause is resp_to_msc_invoc.
25. ext_in_better_cell (87)
An incoming external handover. The handover setup cause is a better cell.
26. ext_in_directed_retry (88)
An incoming external handover. The handover setup cause is a directed retry.
27. ext_in_unexpected (89)
An incoming external handover. The handover setup cause is unexpected.
28. ext_in_switch_crc_pool (90)
An incoming external handover attempt for changing the A interface circuit pool.
29. ext_in_pre_empt_c (91)
An incoming external handover. The handover setup cause is preemption.
30. ext_in_bsc_trho_c (92)
An incoming external handover. The handover setup cause is a BSC traffic reason handover.
31. ext_in_isho_c (93)
An incoming external inter-system handover
32. ext_out_dl_rxlev (100)
An outgoing external handover. The handover setup cause is the downlink rx level.
33. ext_out_ul_rxlev (101)
An outgoing external handover. The handover setup cause is the uplink rx level.
An incoming external handover. The handover setup cause is O and M intervention.
34. ext_out_dl_rxqual (102)
An outgoing external handover. The handover setup cause is the downlink rx quality.
35. ext_out_ul_rxqual (103)
An outgoing external handover. The handover setup cause is the uplink rx quality.
36. ext_out_dl_interf (104)
An outgoing external handover. The handover setup cause is the downlink interference.
37. ext_out_ul_interf (105)
An outgoing external handover. The handover setup cause is the uplink interference.
38. ext_out_distance (106)
An outgoing external handover. The handover setup cause is distance.
39. ext_out_pbgt_ho (107)
An outgoing external handover. The handover setup cause is PBGT handover.
40. ext_out_umbrella_ho (108)
An outgoing external handover. The handover setup cause is an umbrella handover.
41. ext_out_forced_ho (109)
An outgoing external handover. The handover setup cause is a forced handover.
42. ext_out_dr_ho (110)
An outgoing external handover. The handover setup cause is DR (directed retry) handover.
43. ext_out_tr_ho (111)
An outgoing external handover. The handover setup cause is TR (traffic reason) handover.
44. ext_out_idr_ho (112)
An outgoing external handover. The handover setup cause is IDR handover.
45. ext_out_pre_empt_ho (113)
An outgoing external handover. The handover setup cause is pre-emption handover.
46. ext_out_rap_fld_drop (114)
An outgoing external handover. The handover setup cause is a rapid field drop.
47. ext_out_low_distance (115)
An outgoing external handover. The handover setup cause is a low distance (extended cell radius feature).
48. ext_out_switch_crc_pool (116)
An outgoing external handover attempt for changing the A interface circuit pool.
49. ext_out_slow_moving_ms (117)
An outgoing external handover. The handover setup cause is a Slow Moving MS in the Macro Cell. The slow moving detection is based on the received measurement of adjacent micro cells and on the umbrella like handover criterias.
50. ext_out_det_slow_mov_ms (118)
An outgoing external handover. The handover setup cause is the low speed of the MS. The slow moving detection is based on the MS speed indications sent by the BTS.
51. ext_out_det_fast_mov_ms (119)
An outgoing external handover. The handover setup cause is a high speed of MS. The fast moving detection is based on the MS speed indications sent by the BTS.
52. ext_out_erfd_ho (163)
Handover cause for Enhanced Field Drop handover.
53. ext_out_bsc_trho_c (164)
An outgoing external handover whose setup cause is a BSC traffic reason handover.
54. ext_out_isho_c (190)
An outgoing external inter-system handover. The handover setup cause is BSC traffic load.
55. inter_dl_rxlev (120)
An internal inter handover. The handover setup cause is the downlink rx level.
56. inter_ul_rxlev (121)
An internal inter handover. The handover setup cause is the uplink rx level.
57. inter_dl_rxqual (122)
An internal inter handover. The handover setup cause is the downlink rx quality.
58. inter_ul_rxqual (123)
An internal inter handover. The handover setup cause is the uplink rx quality.
59. inter_dl_interf (124)
An internal inter handover. The handover setup cause is the downlink interference.
60. inter_ul_interf (125)
An internal inter handover. The handover setup cause is the uplink interference.
61. inter_distance (126)
An internal inter handover. The handover setup cause is distance.
62. inter_pbgt_ho (127)
An internal inter handover. The handover setup cause is PBGT handover.
63. inter_umbrella_ho (128)
An internal inter handover. The handover setup cause is an umbrella handover.
64. inter_forced_ho (129)
An internal inter handover. The handover setup cause is a forced handover.
65. inter_dr_ho (130)
66. inter_tr_ho (131)
An internal inter handover. The handover setup cause is a TR (traffic reason) handover.
67. inter_idr_ho (132)
An internal inter handover. The handover setup cause is an IDR handover.
68. inter_pre_empt_ho (133)
An internal inter handover. The handover setup cause is a pre-emption handover.
69. inter_rap_fld_drop (134)
An internal inter handover. The handover setup cause is a rapid field drop.
70. inter_low_distance (135)
An internal inter handover. The handover setup cause is a low distance (extended cell radius feature).
An internal inter handover. The handover setup cause is a DR handover.
An internal inter handover. The handover setup cause is an ok C/I ratio (Underlay-overlay handover).
72. inter_bad_ci_ratio (137)
An internal inter handover. The handover setup cause is a bad C/I ratio (Underlay-overlay handover).
73. inter_slow_moving_ms (138)
An internal inter handover. The handover setup cause is a Slow Moving MS in the Macro Cell. The slow moving detection is based on the received measurement of adjacent micro cells and on the umbrella like handover criterias.
74. inter_det_slow_mov_ms (139)
An internal inter handover. The handover setup cause is the low speed of the MS. The slow moving detection is based on the MS speed indications sent by the BTS.
75. inter_det_fast_mov_ms (156)
An internal inter handover. The handover setup cause is the high speed of the MS. The fast moving detection is based on the MS speed indications sent by the BTS.
76. inter_erfd_ho (157)
Handover cause for Enhanced Field Drop handover.
77. Inter_direct_access (158)
The counter indicates the number of successful internal inter-cell handovers from a dedicated control channel to a super-reuse TRX. Handover setup cause is the direct access procedure.
78. inter_bsc_trho_c (159)
An internal inter handover whose setup cause is a BSC traffic reason handover.
79. inter_dadlb_c (160)
An internal inter handover whose setup cause is the Direct Access to Desired Layer/Band feature.
80. intra_dl_interf (140)
An internal intra handover. The handover setup cause is the downlink interference.
81. intra_ul_interf (141)
An internal intra handover. The handover setup cause is the uplink interference.
82. intra_forced_ho (142)
An internal intra handover. The handover setup cause is a forced handover.
83. intra_dl_rxqual (143)
An internal intra handover. The handover setup cause is the downlink rx quality.
84. intra_ok_ci_ratio (144)
An internal intra handover. The handover setup cause is an ok C/I ratio (Underlay-overlay handover).
85. intra_bad_ci_ratio (145)
An internal intra handover. The handover setup cause is a bad C/I ratio (Underlay-overlay handover).
86. intra_pre_empt_ho (146)
An internal intra handover. The handover setup cause is pre-emption handover.
87. intra_distance (147)
Intra cell handover from a normal area to an extended area. Intra cell handover from a normal area to an extended area is performed when the timing advance (TA) of the MS is equal or more than the parameter maxMSDistanceHOThreshold defines.
88. intra_low_distance (148)
Intra cell handover from an extended area to a normal area. Intra cell handover from an extended area to a normal area is performed when the timing advance (TA) of the MS is equal or less than the parameter minMSDistanceHOThreshold defines.
89. intra_dr_ho (149)
Assignment attempt from an SDCCH to a super-reuse frequency.
90. intra_direct_access (150)
91. intra_gprs_ho (151)
92. intra_ho_to_amr_hr (152)
An intra cell handover from AMR FR to AMR HR.
93. intra_ho_to_amr_fr (153)
An intra cell handover from AMR HR to AMR FR.
94. intra_inter_band_tch (154)
A TCH-TCH handover that has been made due to load reasons between BTSs on different frequency bands of a segment.
95. intra_inter_band_sdc (155)
The counter indicates the number of successful internal intra-cell handovers from a dedicated control channel to a super-reuse TRX . Handover setup cause is the direct access procedure.
An internal intra handover. The handover is done to get more resources for GPRS .
The Abis interface receives an assignment_failure message from the MS during a Basic Call.
8. block_slave (307)
Channel blocking caused by some other reason than the ones given above.
9. ch_act_nack (308)
The Abis interface receives a channel_activation_nack message or its contents have been corrupted.
10. ch_act_nack_om_inter (309)
11. ch_act_nack_equip_fail (310)
12. ch_act_nack_encryp_alg (311)
13. ch_act_nack_rad_ch_alr_a (312)
14. ch_act_nack_serv_not_ava (313)
15. ch_act_fail (314)
The Abis interface receives a channel_activation_ack message and its contents have been corrupted or a timer expires while waiting for the message.
16. conn_fail (315)
The Abis interface receives a connection_failure message.
17. conn_fail_rad_inf_fail (316)
18. conn_fail_rad_link_fail (317)
19. conn_fail_rem_trans_fail (318)
The Abis interface receives a channel_activation_nack message, and the cause is O and M intervention .
The Abis interface receives a channel_activation_nack message, and the cause is equipment failure .
The Abis interface receives a channel_activation_nack message and the cause is an encryption algorithm not supported .
The Abis interface receives a channel_activation_nack message and the cause is radio channel already allocated .
The Abis interface receives a channel_activation_nack message and the cause is that the service is not available .
The Abis interface receives a connection_failure message and its cause is radio interface failure .
The Abis interface receives a connection_failure message and its cause is radio link failure .
20. data_ind_corrup (319)
The Abis interface receives a data_indication message whose contents have been corrupted.
21. err_ind (320)
The Abis interface receives an error_indication message.
22. estab_ind_fail_c (321)
A timer expires while waiting for an establish_indication message.
23. estab_conf_fail (322)
The Abis interface receives an establish_confirm message. The contents of the message have been corrupted or a timer expires while waiting for the message.
24. ho_fail (323)
The handover has failed and the MS returns to the source channel. The MS has sent an assignment failure or a handover failure message to the network during the handover.
25. ho_detect_fail (324)
The Abis interface receives an ho_detect message. The contents of the message have been corrupted or a timer expires while waiting for the message.
26. mode_mod_nack (325)
The Abis interface receives a mode_modify_nack message.
27. mode_mod_ack_fail (326)
The Abis interface receives a mode_modify_ack message whose contents have been corrupted or a timer expires while waiting for the message.
28. no_meas_result (327)
No measurement result messages from the BTS.
29. no_resp_from_copro (328)
Timer expires because the co-process does not respond. A BSC internal failure.
30. phy_cont_conf_fail (329)
The Abis interface receives a physical_context_confirm message. The contents have been corrupted or a timer expires while waiting for the message.
31. rcs_alg_start_ack_fail (330)
The Abis interface receives a connection_failure message and its cause is remote transcoder failure .
The Abis interface receives an rcs_algorithm_start_ack message whose contents have been corrupted or a timer expires while waiting for the message. BSC internal signalling.
32. rcs_alg_cl_ack_fail (331)
The Abis interface receives an rcs_algorithm_clear_ack message whose contents have been corrupted or a timer expires while waiting for the message. BSC internal signalling.
33. rc0_disco_ind (332)
The Abis interface receives an rc0_disconnect_ind message from RC0.
34. rf_ch_rel_ack_fail (333)
The Abis interface receives an rf_ch_rel_ack message whose contents have been corrupted or a timer expires while waiting for the message.
35. rel_ind (334)
The Abis interface receives a release_indication message.
36. rel_ind_fail (335)
The Abis interface receives a release_indication message. The contents of the message have been corrupted or a timer expires while waiting for the message.
37. signalling_error (336)
DTAP signalling fails.
38. state_conflict (337)
An attempt to activate a blocked channel in the Abis interface.
39. type_conflict (338)
An attempt to activate a channel with the wrong information in the Abis interface.
40. forced_rel (339)
Forced TCH release.
41. rej_phantom_res (340)
Rejected phantom reservations caused by the wrong establishment cause in the channel required message from the MS or a too long distance between the MS and the BTS.
42. overload (341)
Overload message from the BTS.
43. abi_switchover (342)
The BCSU switchover has been started.
44. sapi_3_fail (343)
During the SMS establishment the Abis interface receives a release_indication message or the establish_indication message received has been corrupted.
45. paging_msg_fail (344)
The Abis interface receives an ms_paging message and the channel has been blocked.
46. ch_required_fail (345)
The Abis interface receives a channel_required message whose contents have been corrupted.
47. mode_mod_nack_equip_fail (346)
48. mode_mod_nack_trc_rat_un (347)
49. rrm_serv_req_nack (348)
The Abis interface receives an rrm_ch_serv_req_nack message.
50. ch_mode_mod_fail (349)
The Abis interface receives a ch_mode_modify_ack message and the mode has not been the same as the mode requested.
51. ass_fail (350)
Timer expires while waiting for the assignment_complete message.
52. dr_fail (351)
Directed retry procedure fails.
53. coprocess_fail (352)
A failure has occurred in co-process.
54. err_rep_enc_alg_not_imp (353)
55. error_report (354)
An error_report message received from the BTS.
The Abis interface receives a mode_modify_nack message with the cause equipment failure .
The Abis interface receives a mode_modify_nack message with the cause requested transcoding/rate adaption not available .
An error_report message is received from BTS and the cause is encryption algorithm not implemented .
56. ch_act_nack_ch_mode_err (355)
57. ch_act_nack_gen_ie_err (356)
58. speech_version_unavail (357)
59. ignored_double_rand_acc (358)
When random access buffering is used in an extended range cell, if two incoming random accesses have the same frame number, the latter one is ignored.
60. rtsl_reconf_fail (359)
Reconfiguration of a dynamic SDCCH resource has been failed at the time of the immediate assignment. All of the SDCCH resources under the control of the BCSU are already in use.
61. ho_interrupted (360)
If an assignment procedure is started before the MS is assigned to move to a new channel, handover attempt is terminated with DX cause ho_interrupted_c.
62. downgrade (361)
Number of channel releases caused by a downgrade.
63. ho_not_started (362)
Number of HO starts rejected due to other ongoing procedures.
64. conf_change_not_allowed (363)
Number of upgrades, downgrades and ALAs rejected due to other ongoing procedures.
65. conf_change_bts_fail (364)
Number of failed configuration changes due to mode modify nack or no answer from the BTS.
66. conf_change_ms_fail (365)
Number of failed configuration changes due to configuration change reject or no answer from the MS.
67. hscsd_copro_fail (366)
Number of channel releases caused by a failure in another channel in the HSCSD configuration.
68. sub_timer (367)
The Abis interface receives a channel_activation_nack message and the failure cause is either the not implemented unspecified or mandatory IE error .
The Abis interface receives a channel_activation_nack message and the failure cause is the general IE error .
The Abis interface receives an assignment_failure message or handover_failure message from the MS during an assignment or handover and the RR cause is channel mode unacceptable .
Number of timer expiries due to sub-channel not responding to the main channel in the HSCSD connection.
69. pre_emption (368)
Number of TCH pre-emption releases.
70. upgrade_fail (369)
Number of upgrade procedure failures.
71. estab_ind_corrupted_c (370)
Number of the ESTABLISH_INDICATION messages which the Abis interface receives because of the corrupted contents of the message.
Causes set by the Radio Connection Supervision Program Block (RCSPRB)
1. timing_advance (400)
The call is released after the distance between the MS and the BTS has reached the maximum value allowed, i.e. the MS has exceeded the planned cell boundaries.
2. rrm_switch_crc_pool (401)
The Radio Resource Management Program Block (RRMPRB) will set this cause in the TCH resource request negative acknowledgement message in order to indicate the A interface circuit pool change request.
3. rrm_speech_ver_unavail (402)
The requested speech version is not supported by the target BTS.
4. bts_not_supporting (403)
Resource that is not supported by BTS has been requested.
5. ms_not_supporting (404)
Resource that is not supported by MS has been requested.
6. rrm_invalid_cell_c (405)
The traffic channel allocation in the external handover has failed. The "Handover Request" message received by the BSS indicates a target cell which is not controlled by the BSS.
Causes set by the A interface Signalling Program Block in BSC (AIVPRB)
1. aiv_hand_act_fail (600)
Activation of a hand process fails in the AIVPRB master.
2. aiv_ssp (601)
SCCP connection establishment is not possible because the subsystem is in the prohibited status. The situation is detected by the AIVPRB master.
3. global_reset (606)
State change of an SCCP subsystem or a RESET message from the MSC.
4. sccp_conn_fail (602)
SCCP connection establishment fails. A CREF message is received from the MSC.
5. sccp_conn_timeout (603)
No response from the MSC to the SCCP connection establishment.
6. sccp_release (604)
Abnormal release of the SCCP connection (RLSD received).
7. no_dtap_from_msc (608)
No DTAP message from the MSC after a successful SCCP connection establishment.
8. ho_denied_assign (609)
Starting the handover is not allowed because an assignment procedure is in progress.
9. ho_denied_ciphering (610)
Starting the handover is not allowed because the ciphering procedure is in progress.
10. ho_denied_clear (611)
Starting the handover is not allowed because the call clearing procedure is in progress.
11. ho_denied_no_sccp_conn (612)
Starting the external SDCCH handover is not allowed because the SCCP connection establishment is not complete.
12. T7_expiry (613)
Expiry of the GSM timer T7.
13. T10_expiry (614)
Expiry of the GSM timer T10.
14. aiv_crct_res_timeout (615)
Timeout in the AIVPRB while allocating an A interface speech circuit.
15. aiv_crct_conn_timeout (616)
Timeout in the AIVPRB while connecting an A interface speech circuit.
16. aiv_crct_disconn_timeout (617)
Timeout in the AIVPRB while disconnecting an A interface speech circuit.
17. aiv_crct_rel_timeout (618)
Timeout in the AIVPRB while releasing an A interface speech circuit.
18. aiv_timeout (619)
Timeout in the AIVPRB in BSC internal communication.
19. act_ctrl_timeout (620)
The BSC internal supervision timer, which supervises the communication between the Abis and the A interface, has expired.
20. invalid_bssmap_msg (621)
An erroneous message, which leads to the clearing of the call, has been received from the MSC.
21. unknown_a_pcm (622)
Message received concerning an unknown A interface circuit.
22. ho_denied_no_proper_crc (623)
23. ch_type_mismatch (624)
The radio interface data rate requirement is totally contradictory with the TCH channel rate request of the channel type IE included in the normal Assignment Request or Handover Request. In the Assignment Request related to the In Call Modification or the FACCH call setup, the TCH channel rate request or the data rate request are totally contradictory with the type of TCH where the call is maintained.
24. aiv_transc_or_rate_unava (625)
The TCH type requested by the MSC is not supported.
25. aiv_speech_version_unava (626)
The speech coder version requested by the MSC is not supported.
26. aiv_pagin_refus_big_load (627)
A paging message is received from the MSC when the BCSU unit load is too high. The load is observed by the number of unhandled messages in the unit.
Handover is denied when the AIVPRB receives the handover inquiry message from the Handover Attempt Supervisor Program Block (HASPRB) with the cause switch circuit pool and there is no proper A interface circuit fitting in with the pool list of the inquiry message.
27. aiv_conn_refresh_timeout (628)
Timeout in the connection refreshing procedure.
28. aiv_conn_refresh_failed (629)
The connection refreshing procedure has failed.
Causes set by the Speech Circuit Control in GSM BSC A interface (SC7PRB)
1. a_tsl_user_mismatch (800)
A request to connect, disconnect or release a speech circuit is received from a process which is not recorded as a user of the circuit in the internal control tables of SC7PRB.
2. sc7_crct_res_timeout (801)
Timeout in the SC7PRB while allocating an A interface speech circuit.
3. sc7_crct_conn_timeout (802)
Timeout in the SC7PRB while connecting an A interface speech circuit.
4. sc7_crct_disconn_timeout (803)
Timeout in the SC7PRB while disconnecting an A interface speech circuit.
5. sc7_crct_rel_timeout (804)
Timeout in the SC7PRB while releasing an A interface speech circuit.
6. a_tsl_blocked (805)
Assignment of a circuit that is blocked.
7. a_tsl_status_unknown (806)
Assignment of a circuit whose status is unknown.
8. lsi_access_fail (807)
Access to the Line Signalling File (LSIGNL) failed.
9. scc_access_fail (808)
Access to the System-controlled Circuit State File (SCCTST) failed.
10. undef_tsl_in_lsi (809)
The circuit concerned is not defined in the LSIGNL file.
11. crct_equipment_fail (810)
The SC7PRB has detected a situation which has been caused by hardware problems.
12. reset_crct (811)
The RESET CIRCUIT message has been received from the MSC.
13. sc7_ssp (813)
14. a_pcm_fault (815)
A fault has been detected in the 2-Mbit PCM connection.
15. a_crct_removed (817)
A speech circuit has been removed from use.
16. a_et_state_change (819)
State change of the ET has occurred.
Causes set by the Resource Control Program Block in BSC (RC0PRB)
1. rc0_hand_act_fail (700)
The RC0PRB master fails to activate a hand process.
2. a_crct_alr_res (701)
Assignment of a speech circuit which has already been allocated.
3. a_crct_conn_err (702)
Connection error in marker while connecting an A interface speech circuit.
4. rc0_crct_conn_timeout (703)
Timeout in the RC0PRB while connecting an A interface speech circuit.
5. access_out_of_crct_tbl (704)
Requested speech circuit not found in the circuit control table.
6. a_crct_rel_err (705)
An error caused by the SCCP prohibited status. The situation has been detected by the SC7PRB.
Circuit release error in marker while releasing an A interface speech circuit.
7. rc0_transc_or_rate_unava (706)
The requested channel rate corresponding to the A interface circuit pool has not been defined on the A interface.
8. rc0_cip_type_mismatch (707)
The circuit type A is totally contradictory with the TCH channel rate requirement or the data rate requirement implies the circuit pool change.
9. rc0_inv_msg_contents (708)
The radio interface data rate requirement is totally contradictory with the A interface pool configuration.
10. rc0_req_speech_ver_unava (709)
BSC has received either an Assignment Request or a Handover Request message containing speech codec versions none of which are supported by the BSC.
11. rc0_hunting_queue_full (710)
There is no free place for the call in the hunting queue.
12. rc0_a_crct_congestion (711)
There is no free circuit for the call.
13. rc0_a_search_error (712)
The content of the hunting request message is invalid.
14. rc0_crct_pool_mismatch (713)
The hunted circuit is from the wrong circuit pool.
15. rc0_rej_due_eme_call (714)
The hunting queue is full. An emergency call has taken priority over the ordinary call.
16. rc0_ilc_file_error (715)
A interface circuit reservation fails because no pool is available on the hunting list.
Causes set by the Handover Attempt Supervisor Program Block (HASPRB)
1. ho_not_allowed (500)
External handover was not allowed during a FACCH call setup, external DR handover was disabled, or all candidate cells for an external handover were n-areas of the extended cells.
2. no_radio_res_avail (501)
No radio resources in the BTS for channel reservation during handover signalling.
3. no_resp_from_coprocess (503)
Signalling with the internal processes has failed during handover signalling.
4. no_resp_to_radio_res_req (504)
Target channel reservation has failed during handover signalling. No answer to the radio resource request.
5. has_state_conflict (505)
Target channel reservation has failed. Channel activation acknowledgement has not been received, a timer for that has expired.
6. clear_cmd_not_received (506)
No clear command has been received from the A interface during external source handover signalling.
7. ms_is_lost (507)
The timer t3107, t3103 or t9113 has expired. The assignment complete or handover complete message has not been received. The MS has not established a channel to the target side.
8. no_resp_to_ho_cpl_msg (508)
Problems in sending the handover performed message by the BSC.
9. has_switchover (509)
Switchover has been started and the handover has failed.
10. target_fail (510)
Failure in the target channel.
11. source_fail (511)
Failure in the source channel.
12. has_call_control (512)
The master has failed to create a hand.
13. adj_cell_id_err (513)
The handover attempt was interrupted when the BSC noticed that the target cell information (BCCH frequency and/or BSIC) received in the handover command message from the MSC is not correct. This counter indicates that information in the source BSS Radio Network Configuration Database concerning adjacent cells is wrong.
Causes set by the Mobile Services Switching Centre (MSC)
These causes are possible only during signalling. The BSC cannot observe these if the phase is MM signalling (2) or conversation (15).
1. m_radio_if_mess_fail (900)
2. m_radio_if_fail (901)
3. m_uplink_quality (902)
4. m_uplink_strength (903)
5. m_downlink_quality (904)
6. m_downlink_strength (905)
7. m_distance (906)
8. m_o_and_m_inter (907)
9. m_resp_to_msc_invoc (908)
10. m_call_control (909)
11. m_r_if_f_rev_to_old (910)
12. m_handover_succ (911)
Cause value 0x00 radio interface message failure received from the MSC.
Cause value 0x01 radio interface failure received from the MSC.
Cause value 0x02 uplink quality received from the MSC.
Cause value 0x03 uplink strength received from the MSC.
Cause value 0x04 downlink quality received from the MSC.
Cause value 0x05 downlink strength received from the MSC.
Cause value 0x06 distance received from the MSC.
Cause value 0x07 O and M intervention received from the MSC.
Cause value 0x08 response to MSC invocation received from the MSC.
Cause value 0x09 call control received from the MSC.
Cause value 0x0A radio interface failure, reversion to old channel received from the MSC.
Cause value 0x0B handover successful received from the MSC.
13. m_better_cell (912)
14. m_directed_retry (913)
15. m_equipment_fail (914)
16. m_no_radio_res_avail (915)
17. m_req_terr_res_unava (916)
18. m_ccch_overload (917)
19. m_processor_overload (918)
20. m_bss_not_equipped (919)
21. m_ms_not_equipped (920)
22. m_tr_cod_rat_ad_unav (921)
23. m_ciph_alg_not_supp (922)
24. m_terr_chan_alr_allc (923)
Cause value 0x0C better cell received from the MSC.
Cause value 0x0D directed retry received from the MSC.
Cause value 0x20 equipment failure received from the MSC.
Cause value 0x21 no radio resource available received from the MSC.
Cause value 0x22 requested terrestrial resource unavailable received from the MSC.
Cause value 0x23 ccch overload received from the MSC.
Cause value 0x24 processor overload received from the MSC.
Cause value 0x25 bss not equipped received from the MSC.
Cause value 0x26 ms not equipped received from the MSC.
Cause value 0x30 requested transcoding/rate adaption unavailable received from the MSC.
Cause value 0x40 ciphering algorithm not supported received from the MSC.
Cause value 0x50 terrestrial circuit already allocated received from the MSC.
25. m_prot_err_b_bsc_msc (924)
26. m_unexpected (925)
Unexpected failure from the MSC.
27. m_invalid_cell (926)
28. m_invalid_msg_cont (927)
29. m_ie_or_field_missing (928)
30. m_incorrect_value (929)
31. m_unknown_msg_type (930)
32. m_unknown_ie (931)
33. m_transc_or_rate_unavail (932)
34. m_cip_type_mismatch (933)
35. m_switch_crc_pool (934)
36. m_speech_version_unavail (935)
37. m_pre_empt_c (936)
Cause value 0x60 protocol error between BSC and MSC received from the MSC.
Cause value 0x27 invalid cell received from the MSC.
Cause value 0x51 invalid message contents received from the MSC.
Cause value 0x52 information element or field missing received from the MSC.
Cause value 0x53 incorrect value received from the MSC.
Cause value 0x54 unknown message type received from the MSC.
Cause value 0x55 unknown information element received from the MSC.
Cause value 0x30 requested transcoding/rate adaption unavailable received from the MSC.
Cause value 0x31 circuit pool mismatch received from the MSC.
Cause value 0x32 switch circuit pool received from the MSC.
Cause value 0x31 requested speech version unavailable received from the MSC.
38. m_traffic_c (937)
Cause value 0x29 preemption received from the MSC.
Cause value 0x0F traffic received from the MSC.
Internal Description of Call related DX causes in BSC
The radio interface data rate requirement is totally contradictory with the TCH channel rate request of the channel type IE included in the normal Assignment Request or Handover Request. In the Assignment Request related to the In Call Modification or the FACCH call setup, the TCH channel rate request or the data rate request are totally contradictory with the type of TCH where the call is maintained.
In this phase, the MS gains access to the network, and the ABIPRB sets the cause of establishment to the cause field of a DX cause. The success cause is conveyed to the next phase if the signalling is finished successfully in this phase.
When a failure has occurred, the success cause is overwritten with the failure cause and the signalling continues as call clearing. The failure counter is updated by the RRMPRB (Radio Resource Management Program Block) or, in some cases, also by the ABIPRB.
Figure: Phase 1 of DX causes
MM signalling
The DX cause phase 2 covers the MM signalling between the mobile subscriber and the MSC. The MM signalling is transparent for the BSC occurring on an SDCCH or TCH.
The ABIPRB is responsible for this phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
The DX cause phase 1 covers the starting signalling of the mobile originating and the mobile terminating call establishment. The dedicated channel can be an SDCCH (stand-alone dedicated control channel) or TCH .
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 2 of DX causes
Figure: Phase 2 of DX causes
Basic Assignment
The DX cause phase 3 covers the mobile subscriber assignment signalling from the SDCCH to the TCH by means of the Basic Call Setup.
The ABIPRB is responsible for this phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 3 of DX causes
Release
The DX cause phase 4 covers the release on an SDCCH or a TCH.
The ABIPRB is responsible for this phase.
When a failure has occurred during this phase, only one of the BSC clear code counters is updated. The service level counters are not updated, because failures in this phase do not affect the service of the MS.
Figure: Phase 4 of DX causes
FACCH assignment
The DX cause phase 5 covers the FACCH call setup assignment signalling. The dedicated channel can only be a TCH.
When a clear command is received from the MSC, the AIVPRB knows that the release is either normal or abnormal (normal means that the MSC has released the channel, for example, at the end of the location update or at the end of the call). In a normal release, the AIVPRB sets the cause to normal_rel_c and sends the appropriate message to the ABIPRB within the DX cause. The ABIPRB checks the DX cause of the message and decides whether to update the counter. Because of the normal_rel_c , the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The ABIPRB is responsible for this phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 5 of DX causes
SMS establishment on TCH
The DX cause phase 6 covers the SMS establishment signalling of a TCH. The dedicated channel can only be a TCH.
The ABIPRB is responsible for this phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 6 of DX causes
SMS establishment on SDCCH
The DX cause phase 7 covers SDCCH SMS establishment. The dedicated channel can only be an SDCCH.
The ABIPRB is responsible for this phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 7 of DX causes
Ciphering
The DX cause phase 8 covers ciphering signalling. The dedicated channel can be an SDCCH or a TCH.
The ABIPRB is responsible for this phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 8 of DX causes
External handover for source side
The DX cause phase 9 covers the external handover signalling of the source side on an SDCCH and a TCH.
The HASPRB is responsible for this phase.
When a failure has occurred before the clear command from the MSC, the success cause is overwritten. The signalling continues as handover clearing and the RRMPRB or, in some cases, also the HASPRB updates the failure counter.
When the failure has occurred after a clear command from the MSC, no failure counters are updated because the MS has not observed that kind of failure (the success DX cause counter has been updated because the MS has been released immediately after the clear command).
When the MSC sends a clear command with the relevant failure cause, the cause is converted into a DX cause and the RRMPRB updates the failure counter.
The MS and the BTS send the measurement results to the BSC. With these measurement results, the RCSPRB decides whether the handover is performed. When the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate signalling message forward, including the DX cause.
The HASPRB checks the cause of the handover and decides that an external handover is to be made. After this decision, the HASPRB converts the cause for the appropriate type of handover. The MSC indicates that the signalling has been successfully finished by means of a clear command message. The BSC receives the clear command. The AIVPRB knows when the clearing is normal and successful. The AIVPRB sets the cause to normal_rel_c and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The DX cause phase 10 covers the internal intra-cell handover signalling of the source side on an SDCCH and a TCH.
The HASPRB is responsible for this phase.
The MS and the BTS send the measurement results to the BSC. Based on these measurement results, the RCSPRB decides whether the handover is performed. When the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate signalling message forward, including the DX cause.
The HASPRB checks the cause for the handover and decides that an internal handover should be made. After this decision, the HASPRB converts the DX cause for the appropriate handover.
On the source side, the ABIPRB sends the original DX cause (success DX cause for establishment) via the HASPRB to the target ABIPRB. It is taken into use on the target side after the handover signalling has finished successfully.
The HASPRB updates the successful handover counter and the call continues as a normal call on the target side.
When a failure has occurred on the source side before the assignment command, the success cause is overwritten and the signalling continues as call clearing. The failure counter is updated by the RRMPRB.
On the target side, the HASPRB sets the cause to source_fail_c. No failure counters are updated because only one counter is updated for each failure. (The RRMPRB has updated the failure counter on the source side.)
Figure: Phase 10 of DX causes
Internal handover inter for source side
The DX cause phase 11 covers the internal inter-cell handover signalling for the source side on an SDCCH or a TCH.
The HASPRB is responsible for this phase.
Figure: Phase 11 of DX causes
External handover for target side
The DX cause phase 12 covers the external handover signalling for the target side on an SDCCH and a TCH.
The HASPRB is responsible for this phase.
The BSC receives the HO_REQUEST message with the relevant handover cause. The AIVPRB sends the appropriate signalling message to the HASPRB, including the DX cause. The HASPRB converts the cause into the relevant DX cause for the external handover. When the signalling is finished successfully, the HASPRB updates the handover success counter, and the DX cause is conveyed to the following phase.
When a failure has occurred, the successful DX cause is overwritten and the signalling continues as handover clearing. The failure counter is updated by the RRMPRB or, in some cases also by the HASPRB.
The success and failure cases happen as described in Internal handover intra for source side .
The DX cause phase 13 covers the internal intra-cell handover signalling for the target side on an SDCCH and a TCH.
The HASPRB is responsible for this phase.
A failure has occurred before the assignment has been completed on the target side. The appropriate failure counter is updated. The MS is able to return to the old channel. If it returns to the old channel, it sends an assignment failure. This kind of situation only affects informative counters.
When the failure has occurred after the assignment has been completed on the target side, the success cause is overwritten and the signalling continues as call clearing.
See Internal handover intra for source side for a successful case.
The HASPRB sets restore_old_c as the cause and sends it to the ABIPRB. The source side ABIPRB receives the DX cause and the original establishment cause is restored. The signalling continues on the old channel.
If the MS does not return to the old channel (the MS is lost), the HASPRB sets the source_fail_c as the cause and sends it to the target side ABIPRB. Call clearing is started with the real failure cause on the source side and the failure counter is updated by the RRMPRB.
The ABIPRB is responsible for this phase. This phase starts when the BSC receives the CONNECT_ACK message.
The successful DX cause is received from the previous phase and the same DX cause is conveyed to the following phase.
When a failure has occurred, the successful DX cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
Figure: Phase 15 of DX causes
In this phase, the MS gains access to the network, and the ABIPRB sets the cause of establishment to the cause field of a DX cause. The success cause is conveyed to the next phase if the signalling is finished successfully in this phase.
When a failure has occurred, the success cause is overwritten with the failure cause and the signalling continues as call clearing. The failure counter is updated by the RRMPRB (Radio Resource Management Program Block) or, in some cases, also by the ABIPRB.
The DX cause phase 2 covers the MM signalling between the mobile subscriber and the MSC. The MM signalling is transparent for the BSC occurring on an SDCCH or TCH.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
The DX cause phase 1 covers the starting signalling of the mobile originating and the mobile terminating call establishment. The dedicated channel can be an SDCCH (stand-alone dedicated control channel) or TCH .
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
The DX cause phase 3 covers the mobile subscriber assignment signalling from the SDCCH to the TCH by means of the Basic Call Setup.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
When a failure has occurred during this phase, only one of the BSC clear code counters is updated. The service level counters are not updated, because failures in this phase do not affect the service of the MS.
The DX cause phase 5 covers the FACCH call setup assignment signalling. The dedicated channel can only be a TCH.
When a clear command is received from the MSC, the AIVPRB knows that the release is either normal or abnormal (normal means that the MSC has released the channel, for example, at the end of the location update or at the end of the call). In a normal release, the AIVPRB sets the cause to normal_rel_c and sends the appropriate message to the ABIPRB within the DX cause. The ABIPRB checks the DX cause of the message and decides whether to update the counter. Because of the normal_rel_c , the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
The DX cause phase 6 covers the SMS establishment signalling of a TCH. The dedicated channel can only be a TCH.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
The successful cause is received from the previous phase and the same cause is conveyed to the following phase.
When a failure has occurred, the successful cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
When a failure has occurred before the clear command from the MSC, the success cause is overwritten. The signalling continues as handover clearing and the RRMPRB or, in some cases, also the HASPRB updates the failure counter.
When the failure has occurred after a clear command from the MSC, no failure counters are updated because the MS has not observed that kind of failure (the success DX cause counter has been updated because the MS has been released immediately after the clear command).
When the MSC sends a clear command with the relevant failure cause, the cause is converted into a DX cause and the RRMPRB updates the failure counter.
The MS and the BTS send the measurement results to the BSC. With these measurement results, the RCSPRB decides whether the handover is performed. When the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate signalling message forward, including the DX cause.
The HASPRB checks the cause of the handover and decides that an external handover is to be made. After this decision, the HASPRB converts the cause for the appropriate type of handover. The MSC indicates that the signalling has been successfully finished by means of a clear command message. The BSC receives the clear command. The AIVPRB knows when the clearing is normal and successful. The AIVPRB sets the cause to normal_rel_c and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The DX cause phase 10 covers the internal intra-cell handover signalling of the source side on an SDCCH and a TCH.
The MS and the BTS send the measurement results to the BSC. Based on these measurement results, the RCSPRB decides whether the handover is performed. When the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate signalling message forward, including the DX cause.
The HASPRB checks the cause for the handover and decides that an internal handover should be made. After this decision, the HASPRB converts the DX cause for the appropriate handover.
On the source side, the ABIPRB sends the original DX cause (success DX cause for establishment) via the HASPRB to the target ABIPRB. It is taken into use on the target side after the handover signalling has finished successfully.
The HASPRB updates the successful handover counter and the call continues as a normal call on the target side.
When a failure has occurred on the source side before the assignment command, the success cause is overwritten and the signalling continues as call clearing. The failure counter is updated by the RRMPRB.
On the target side, the HASPRB sets the cause to source_fail_c. No failure counters are updated because only one counter is updated for each failure. (The RRMPRB has updated the failure counter on the source side.)
The DX cause phase 11 covers the internal inter-cell handover signalling for the source side on an SDCCH or a TCH.
The DX cause phase 12 covers the external handover signalling for the target side on an SDCCH and a TCH.
The BSC receives the HO_REQUEST message with the relevant handover cause. The AIVPRB sends the appropriate signalling message to the HASPRB, including the DX cause. The HASPRB converts the cause into the relevant DX cause for the external handover. When the signalling is finished successfully, the HASPRB updates the handover success counter, and the DX cause is conveyed to the following phase.
When a failure has occurred, the successful DX cause is overwritten and the signalling continues as handover clearing. The failure counter is updated by the RRMPRB or, in some cases also by the HASPRB.
The DX cause phase 13 covers the internal intra-cell handover signalling for the target side on an SDCCH and a TCH.
A failure has occurred before the assignment has been completed on the target side. The appropriate failure counter is updated. The MS is able to return to the old channel. If it returns to the old channel, it sends an assignment failure. This kind of situation only affects informative counters.
When the failure has occurred after the assignment has been completed on the target side, the success cause is overwritten and the signalling continues as call clearing.
as the cause and sends it to the ABIPRB. The source side ABIPRB receives the DX cause and the original establishment cause is restored. The signalling continues on the old channel.
source_fail_c as the cause and sends it to the target side ABIPRB. Call clearing is started with the real failure cause on the source side and the failure counter is updated by the RRMPRB.
The DX cause phase 14 covers the internal inter-cell handover signalling for the target side on an SDCCH or a TCH.
The ABIPRB is responsible for this phase. This phase starts when the BSC receives the CONNECT_ACK message.
The successful DX cause is received from the previous phase and the same DX cause is conveyed to the following phase.
When a failure has occurred, the successful DX cause is overwritten with the failure cause and the signalling is continued as call clearing. The RRMPRB updates the failure counter.
In this phase, the MS gains access to the network, and the ABIPRB sets the cause of establishment to the cause field of a DX cause. The success cause is conveyed to the next phase if the signalling is finished successfully in this phase.
When a failure has occurred, the success cause is overwritten with the failure cause and the signalling continues as call clearing. The failure counter is updated by the RRMPRB (Radio Resource Management Program Block) or, in some cases, also by the ABIPRB.
When a clear command is received from the MSC, the AIVPRB knows that the release is either normal or abnormal (normal means that the MSC has released the channel, for example, at the end of the location update or at the end of the call). In a normal release, the AIVPRB sets the cause to normal_rel_c and sends the appropriate message to the ABIPRB within the DX cause. The ABIPRB checks the DX cause of the message and decides whether to update the counter. Because of the normal_rel_c , the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
When a failure has occurred before the clear command from the MSC, the success cause is overwritten. The signalling continues as handover clearing and the RRMPRB or, in some cases, also the HASPRB updates the failure counter.
When the failure has occurred after a clear command from the MSC, no failure counters are updated because the MS has not observed that kind of failure (the success DX cause counter has been updated because the MS has been released immediately after the clear command).
The MS and the BTS send the measurement results to the BSC. With these measurement results, the RCSPRB decides whether the handover is performed. When the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate signalling message forward, including the DX cause.
The HASPRB checks the cause of the handover and decides that an external handover is to be made. After this decision, the HASPRB converts the cause for the appropriate type of handover. The MSC indicates that the signalling has been successfully finished by means of a clear command message. The BSC receives the clear command. The AIVPRB knows when the clearing is normal and successful. The AIVPRB sets the cause to normal_rel_c and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The MS and the BTS send the measurement results to the BSC. Based on these measurement results, the RCSPRB decides whether the handover is performed. When the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate signalling message forward, including the DX cause.
On the source side, the ABIPRB sends the original DX cause (success DX cause for establishment) via the HASPRB to the target ABIPRB. It is taken into use on the target side after the handover signalling has finished successfully.
The BSC receives the HO_REQUEST message with the relevant handover cause. The AIVPRB sends the appropriate signalling message to the HASPRB, including the DX cause. The HASPRB converts the cause into the relevant DX cause for the external handover. When the signalling is finished successfully, the HASPRB updates the handover success counter, and the DX cause is conveyed to the following phase.
A failure has occurred before the assignment has been completed on the target side. The appropriate failure counter is updated. The MS is able to return to the old channel. If it returns to the old channel, it sends an assignment failure. This kind of situation only affects informative counters.
as the cause and sends it to the target side ABIPRB. Call clearing is started with the real failure cause on the source side and the failure counter is updated by the RRMPRB.
and sends the appropriate message to the ABIPRB within the DX cause. The ABIPRB checks the DX cause of the message and decides whether to update the counter. Because of the normal_rel_c , the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The HASPRB checks the cause of the handover and decides that an external handover is to be made. After this decision, the HASPRB converts the cause for the appropriate type of handover. The MSC indicates that the signalling has been successfully finished by means of a clear command message. The BSC receives the clear command. The AIVPRB knows when the clearing is normal and successful. The AIVPRB sets the cause to normal_rel_c and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The BSC receives the HO_REQUEST message with the relevant handover cause. The AIVPRB sends the appropriate signalling message to the HASPRB, including the DX cause. The HASPRB converts the cause into the relevant DX cause for the external handover. When the signalling is finished successfully, the HASPRB updates the handover success counter, and the DX cause is conveyed to the following phase.
and sends the appropriate message to the ABIPRB within the DX cause. The ABIPRB checks the DX cause of the message and decides whether to update the counter. Because of the normal_rel_c , the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
The HASPRB checks the cause of the handover and decides that an external handover is to be made. After this decision, the HASPRB converts the cause for the appropriate type of handover. The MSC indicates that the signalling has been successfully finished by means of a clear command message. The BSC receives the clear command. The AIVPRB knows when the clearing is normal and successful. The AIVPRB sets the cause to normal_rel_c and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
, the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
, the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.
and sends the appropriate signalling message forward. The HASPRB updates the successful handover counter and the ABIPRB updates the establishment counter and the success counter with the other DX cause (success DX cause for establishment), which has been received from the previous phase.