Call Related DX Causes in BSC.pdf

GSM/EDGE BSS, Rel. RG30(BSS), Operating Documentation, Issue 04

Reference

Call Related DX Causes in BSC

DN9814277

Issue 15-2Approval Date 2011-09-23

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN9814277


Id:0900d805808e4920Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2011. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN9814277 3



Table of contentsThis document has 107 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Overview of call related DX causes in BSC. . . . . . . . . . . . . . . . . . . . . . . 6

2 Functionality of call related DX causes in BSC . . . . . . . . . . . . . . . . . . . . 7

3 Call phases of call related DX causes in BSC . . . . . . . . . . . . . . . . . . . . . 93.1 Paging/initial MS on CCCH (phase 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.2 MM signalling (phase 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3 Basic assignment (phase 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.4 Release (phase 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.5 FACCH assignment (phase 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.6 SMS establishment on TCH (phase 6) . . . . . . . . . . . . . . . . . . . . . . . . . 143.7 SMS establishment on SDCCH (phase 7) . . . . . . . . . . . . . . . . . . . . . . . 143.8 Ciphering (phase 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.9 External handover for source side (phase 9) . . . . . . . . . . . . . . . . . . . . . 163.10 Internal handover intra for source side (phase 10) . . . . . . . . . . . . . . . . 173.11 Internal handover inter for source side (phase 11) . . . . . . . . . . . . . . . . 173.12 External handover for target side (phase 12). . . . . . . . . . . . . . . . . . . . . 183.13 Internal handover intra for target side (phase 13) . . . . . . . . . . . . . . . . . 193.14 Internal handover inter for target side (phase 14) . . . . . . . . . . . . . . . . . 203.15 Conversation (phase 15) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 List of call related DX causes in BSC . . . . . . . . . . . . . . . . . . . . . . . . . . 224.1 Success causes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.2 Failure causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5 DX and BSSMAP cause mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1 DX causes mapped to BSSMAP causes . . . . . . . . . . . . . . . . . . . . . . . . 475.2 BSSMAP causes mapped to DX causes . . . . . . . . . . . . . . . . . . . . . . . . 56

6 DX causes in BSC statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676.1 DX causes and BSC Level Clear Code Measurement . . . . . . . . . . . . . 676.2 DX causes and BSC Level Clear Code (PM) Measurement . . . . . . . . . 676.3 DX causes and BSC Level Clear Code (SERLEV) Measurement. . . . . 686.4 DX causes and observation report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686.5 DX causes and Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4 DN9814277



List of figuresFigure 1 Paging/initial MS on CCCH (phase 1). . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 2 MM signalling (phase 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 3 Basic assignment (phase 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 4 Release (phase 4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 5 FACCH assignment (phase 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 6 SMS establishment on TCH (phase 6) . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 7 SMS establishment on SDCCH (phase 7) . . . . . . . . . . . . . . . . . . . . . . . 15Figure 8 Ciphering (phase 8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 9 External handover for source side (phase 9) . . . . . . . . . . . . . . . . . . . . . 16Figure 10 Internal handover intra for source side (phase 10) . . . . . . . . . . . . . . . . . 17Figure 11 Internal handover inter for source side (phase 11) . . . . . . . . . . . . . . . . . 18Figure 12 External handover for target side (phase 12) . . . . . . . . . . . . . . . . . . . . . 19Figure 13 Internal handover intra for target side (phase 13) . . . . . . . . . . . . . . . . . . 20Figure 14 Internal handover inter for target side (phase 14) . . . . . . . . . . . . . . . . . . 21Figure 15 Conversation (phase 15). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

DN9814277 5

Call Related DX Causes in BSC Summary of changes


Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes made between issues 15-2 and 15-1Added cause codes related to the feature BSS21507: Flexible MCPA TX Power Pooling.

Added the following new success cause:

• intra_mcpa_pbho_tch_c (188)

Changes made between issues 15-1 and 15-0Added cause codes related to the feature BSS21534: OSC Full Rate with SAIC MS

Added the following new success causes:

• intra_ho_from_fr_to_dfr_c (184) • intra_dfr_rxqual_dmux_ho_c (185) • intra_dfr_rxl_df_dmux_ho_c (186) • intra_dfr_rxlev_dmux_ho_c (187)

Changes made between issues 15-0 and 14-1Added cause codes related to the features BSS21341: A over IP, Transcoder in BSS, BSS30380: A over IP, Transcoder in MGW and BSS21309: OSC Half Rate with SAIC and Packet Abis

Added the following new success causes:

• intra_ho_from_hr_to_dhr_c (179) • intra_ho_from_fr_to_dhr_c (180) • intra_dhr_rxqual_dmux_ho_c (181) • intra_rxlev_diff_dmux_ho_c (182) • intra_dhr_rxlev_dmux_ho_c (183) • inter_mss_trg_bss_int_ho_c (243)

Added the following new failure causes:

• etp_failure_c (377) • unavail_codec_type_conf_c (409) • no_support_a_if_type_c (630) • no_supp_redundancy_level_c (631) • no_supp_codec_type_conf_c (632) • unavail_a_if_type_c (633) • t25_timer_expiry_c (634) • call_id_alr_allocated_c (717) • unavail_terr_resource_c (718) • m_no_supp_codec_typ_conf_c (941) • m_no_support_a_if_type_c (942) • m_unavail_a_if_type_c (943) • m_unavail_codec_typ_conf_c (944) • m_no_supp_redundancy_lvl_c (945)

6 DN9814277


Id:0900d805805a24b5Confidential

Overview of call related DX causes in BSC

1 Overview of call related DX causes in BSCAll events that occur during a call have a cause. The causes can be coded in order to observe the transactions in the network, solve possible error situations and improve the quality of the network.

DX causes describe how the network transactions have succeeded: they provide infor-mation on the causes of events such as call establishment, handovers, internal faults, timer expiry cases, rejected messages sent to mobile stations and channel releases.

DX causes are conveyed within internal signalling messages and give more detailed information on the conditions inside the BSC than GSM-defined causes. DX causes also include GSM causes when a network element other than the BSC initiates the clearing of a transaction. Cases that are not observed in the MSC can also be examined through the use of DX causes in BSC.

The information conveyed by the DX causes can be examined through the use of BSC measurements and observations.

Related topics

• Functionality of call related DX causes in BSC • Call phases of call related DX causes in BSC • List of call related DX causes in BSC • DX and BSSMAP cause mapping • DX causes in BSC statistics

DN9814277 7

Call Related DX Causes in BSC Functionality of call related DX causes in BSC


2 Functionality of call related DX causes in BSCEach DX cause element consists of the following information:

• the cause code that describes the event (see List of call related DX causes in BSC) • a call phase that corresponds with a phase in the signalling scenario or procedure

and defines when the event has occurred (see Call phases of call related DX causes in BSC).

There are two types of DX causes: success causes and failure causes.

A success cause is set when the MS receives access to the network with a relevant establishment cause, or when a handover starts with a relevant handover setup cause.

Correspondingly, a failure cause is set when a failure occurs during a call or a handover. It indicates the error that caused the channel release. Some failures result in call clear-ing, while others, such as failures during a handover, do not.

Failure detectionThe handling of a DX cause is located on GSM layer 3 and failures can be detected in the A interface, Abis interface, and inside the BSC.

The BSC is responsible for the following functional parts on layer 3:

• base transceiver station management (BTSM) • radio resource management (RR) • base station system application part (BSSAP)BTSM and RR are parts of the Abis interface and BSSAP is a part of the A interface.

Since signalling on the mobility management (MM) layer is transparent to the BSC, it can detect only some of the failures on that layer. Such failures are, for example a timer expiry on the lower layer, corrupted messages and other protocol errors. The rest of the failures can be seen as the release of the MSC. The BSC cannot observe these failures if the phase is MM signalling (2) or conversation (15), because the BSC interprets this as a successful call. If the failure occurs on layer 1 or 2, the failure can be detected on layer 3 as a timer expiry or as different kinds of block causes.

For more information on BTSM, see 3GPP TS 48.058 Base Station Controller - Base Transceiver Station (BSC - BTS) Interface Layer 3 specification.

For more information on RR, see 3GPP TS 44.018 Mobile radio interface layer 3 spec-ification.

For more information on BSSAP, see 3GPP TS 48.008 Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification.

Handling of DX causesDX causes are handled as follows:

1. When the program block A detects a failure, it sets the cause and sends the appro-priate message, either directly or through another program block, to program block B that is responsible for the phase during which the error occurred. This internal message includes the DX cause element.The DX cause is set by the program block that initiates the channel release. When another network element sends a clearing to the BSC, it is transformed into a DX cause by the program block that receives the clearing indication.

8 DN9814277



Functionality of call related DX causes in BSC

2. When program block B receives the DX cause, it sets the phase value in the DX cause element.

3. When a program block responsible for updating the failure counter has performed the update, it also sets a flag in the DX cause element which indicates that the counter has already been updated. The counter is updated only once during call sig-nalling, such as a location update, an SMS or a call.

Prioritisation of conflicting failuresSince only one DX cause can be set for one transaction, only the first failure is generally set as the DX cause. In a conflict situation, the program block that has the highest priority defines the appropriate failure cause.

When two different failures are in conflict, the list of priorities is, as follows:

1. AIVPRB (because it also sets the cause of failure for the MSC)2. HASPRB3. other program blocks

The priority handling is implemented in the ABIPRB and the HASPRB. The A interface is only responsible for setting the appropriate cause values.

The following program blocks are involved in the handling of DX causes:

ABIPRB Abis Interface Program Block is responsible for the normal call phases including basic call, SMS, ciphering and FACCH call setup. It also updates the successful establishment counters and sets the causes mainly for Abis signalling failures.

AIVPRB A Interface Signalling Program Block in BSC sets the causes mainly for A interface signalling failures.

HASPRB Handover Attempt Supervisor Program Block is responsible for the handover phases including external, internal intra and internal inter handover signalling. It also updates the successful handover counters and sets the causes mainly for handover signalling failures.

RC0PRB The main purpose of the Resource Control Program Block in BSC is to implement the interface between the marker and the call control program blocks of the BSC. It sets the causes mainly for RC0PRB sig-nalling failures.

RCSPRB Radio Connection Supervision Program Block takes care of the prepro-cessing of the measurement samples, determines the RF output power of the MS and BTS, indicates whether a handover is required and performs supervision of the LAPD link by supervising the flow of mea-surement results coming from the BTS.

RRMPRB Radio Resource Management Program Block controls the use of the radio channels. The program block also sets the failures that have occurred in RRMPRB signalling.

SC7PRB Speech Circuit Control in GSM BSC A Interface takes care of the administration of the A interface speech circuits. It also sets the causes for SC7PRB signalling failures.

DN9814277 9

Call Related DX Causes in BSC Call phases of call related DX causes in BSC

Id:0900d805805a24bcConfidential

3 Call phases of call related DX causes in BSCThe call transactions are divided into 15 different phases, where the numbers from 1 to 15 represent the phase numbers in the observation report, for example.

1. Paging/initial MS on CCCH

2. MM signalling

3. Basic assignment

4. Release

5. FACCH assignment

6. SMS establishment on TCH

7. SMS establishment on SDCCH

8. Ciphering

9. External handover for source side

10. Internal handover intra for source side

11. Internal handover inter for source side

12. External handover for target side

13. Internal handover intra for target side

14. Internal handover inter for target side

15. Conversation

A phase is a stage of the GSM layer 3 call or handover signalling in the BSC. All the telecom signalling scenarios can be present as described in the list above and their purpose is to identify a failure when it occurs.

3.1 Paging/initial MS on CCCH (phase 1)This phase covers the starting signalling of the mobile originating and the mobile termi-nating call establishment. The dedicated channel can be a stand-alone dedicated control channel (SDCCH) or a traffic channel (TCH).

The ABIPRB is responsible for this phase. When the MS gains access to the network, the ABIPRB sets the establishment cause to the cause field of a DX cause element. The success cause is conveyed to the next phase if the signalling is finished successfully in this phase.

If a failure occurs, the success cause is overwritten with the failure cause and the sig-nalling continues as call clearing. The failure counter is updated by the RRMPRB (Radio Resource Management Program Block) or, in some cases, by the ABIPRB.

10 DN9814277



Call phases of call related DX causes in BSC

Figure 1 Paging/initial MS on CCCH (phase 1)

3.2 MM signalling (phase 2)This phase covers the MM signalling between the mobile subscriber and the MSC. The MM signalling occurring on an SDCCH or a TCH is transparent for the BSC.

The ABIPRB is responsible for this phase.

The successful cause is received from the previous phase and conveyed further to the following phase.

If a failure occurs, the successful cause is overwritten with the failure cause and the sig-nalling continues as call clearing. The RRMPRB updates the failure counter.

MS BTS BSC MSC

PAGING

PAGING_COMMAND

PAGING_REQUEST

CHANNEL_REQUEST

CHANNEL_REQUIRED

CHANNEL_ACTIVATION_ACKNOWLEDGE

IMMEDIATE_ASSIGNMENT_COMMAND

IMMEDIATE_ASSIGNMENT

SABM>

ESTABLISH_INDICATION

UA

PAGING_RESPONSE

AUTHENTICATION_REQUEST

CHANNEL_ACTIVATION

DN9814277 11



Figure 2 MM signalling (phase 2)

3.3 Basic assignment (phase 3)This phase covers the mobile subscriber assignment signalling from the SDCCH to the TCH by means of the Basic Call setup.




MS BTS BSC MSC


AUTHENTICATION_RESPONSE

AUTHENTICATION_RESPONSE

IDENTIFICATION_REQUEST

IDENTIFICATION_REQUEST

IDENTIFICATION_RESPONSE

IDENTIFICATION_RESPONSE

DATA_INDICATION

CALL_PROCEEDING CALL_PROCEEDING

ASSIGNMENT_REQUEST


DT1(set up)

MS BTS BSC MSC

ALERT ALERT

CONNECT CONNECT

CONNECT_ACK CONNECT_ACK

After Basic assignment phase

Before Basic assignment phase

12 DN9814277




Figure 3 Basic assignment (phase 3)

3.4 Release (phase 4)This phase covers the release on an SDCCH or a TCH.


When a CLEAR COMMAND is received from the MSC, the AIVPRB knows that the release is either normal or abnormal. The release is a normal one when the MSC releases the channel, for example, at the end of a location update or at the end of a call.

In a normal release, the AIVPRB sends information on a successful call release to the ABIPRB. When ABIPRB receives this information, it updates the successful call and establishment counters according to the success DX cause for establishment, which was received from the previous phase.

If a failure occurs during this phase, only one failure counter is updated. Counters that measure the BSC service level are not updated, because failures in this phase do not affect the service of the MS.

MS BTS BSC MSC

ASSIGNMENT_REQUEST

ASSIGNMENT_COMMAND

SABM ESTABLISH_INDICATION> >

UA

ASSIGNMENT_COMPLETE

ASSIGNMENT_COMPLETE

ALERT ALERT

PHYSICAL_CONTEXT_REQUEST

PHYSICAL_CONTEXT_CONFIRM

CHANNEL_ACTIVATION

CHANNEL_ACTIVATION_ACK

ASSIGNMENT_COMMAND

RF_CHANNEL_RELEASE

RF_CHANNEL_RELEASE_ACK

DN9814277 13



Figure 4 Release (phase 4)

3.5 FACCH assignment (phase 5)This phase covers the FACCH Call setup assignment signalling. The dedicated channel can only be a TCH.




Figure 5 FACCH assignment (phase 5)

MS BTS BSC MSC

CHANNEL_RELEASE CLEAR_COMMAND

CLEAR_COMPLETE

DISC

UA

RELEASE_INDICATION

RF_CHANNEL_REL_ACK

DEACTIVATE_SACCH

RF_CHANNEL_RELEASE

MS BTS BSC MSC

ASSIGNMENT_REQUEST

MODE_MODIFY_ACK

CH_MODE_MODIFICATION

CH_MODE_MODIFY_ACK

CH_MODE_MODIFY_ACK_S

ASSIGNMENT_COMPLETE

ALERT ALERT

MODE_MODIFY_REQ

CH_MODE_MODIFICATION

14 DN9814277




3.6 SMS establishment on TCH (phase 6)This phase covers the SMS establishment signalling on a TCH. The dedicated channel can only be a TCH.




Figure 6 SMS establishment on TCH (phase 6)

3.7 SMS establishment on SDCCH (phase 7)This phase covers SDCCH SMS establishment. The dedicated channel can only be an SDCCH.




MS BTS BSC MSC

UA(SAPI=3)

ESTABLISH_CONFIRM

DATA_REQUEST(CP_DATA)

DATA_INDICATION(CP_ACK)

DATA_INDICATION(CP_DATA)

DATA_REQUEST(CP_ACK)

DT1(CP_ACK)

DT1(CP_DATA)

DT1(CP_ACK)

SABM(SAPI=3)

DT1(CP_DATA)

ESTABLISH_REQUEST

DN9814277 15



Figure 7 SMS establishment on SDCCH (phase 7)

3.8 Ciphering (phase 8)This phase covers ciphering signalling. The dedicated channel can be an SDCCH or a TCH.




Figure 8 Ciphering (phase 8)

MS BTS BSC MSC

UA(SAPI=3)

ESTABLISH_CONFIRM

DATA_INDICATION(CP_ACK)

DT1(CP_DATA)

ESTABLISH_REQUEST

SABM(SAPI=3)

DATA_REQUEST(CP_DATA)

DT1(CP_ACK)

DATA_INDICATION(CP_DATA)

DT1(CP_DATA)

DT1(CP_ACK)

DATA_REQUEST(CP_ACK)

MS BTS BSC MSC

CIPHERING_MODE_COMMAND

CIPHERING_MODE_COMMAND

CIPHERING_MODE_COMPLETE

CIPHERING_MODE_COMPLETE

ENCRYPTION_COMMAND

16 DN9814277




3.9 External handover for source side (phase 9)This phase covers the external 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. The RCSPRB decides on the basis of the results whether the handover is performed. If the handover conditions are met, the RCSPRB sets the cause for the handover and sends the appropriate sig-nalling message forward, including the DX cause.

The HASPRB checks the cause of the handover and decides that an external handover is to be made. Next, the HASPRB converts the cause for the appropriate type of han-dover. The MSC indicates with a CLEAR COMMAND message that the signalling has finished successfully. When the BSC receives the CLEAR COMMAND, the AIVPRB knows if the clearing is normal and successful. It sends information on a successful call release forward. The HASPRB updates the successful handover counter and the ABIPRB updates the successful call and establishment counters with the success DX cause for establishment, which was received from the previous phase.

If a failure occurs before the CLEAR COMMAND is received from the MSC, the success cause is overwritten. The signalling continues as handover clearing and the failure counter is updated by the RRMPRB or, in some cases, the HASPRB.

If a failure occurs after the CLEAR COMMAND is received from the MSC, no failure counters are updated because the MS does not observe this 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.

Figure 9 External handover for source side (phase 9)

MS BTS BSC MSC

MEAS_REPORT MEAS_RESULT

HO_REQUIRED

HO_COMMAND

HO_CMD HANDOVER_COMMAND

CLEAR_COMMAND

CLEAR_COMPLETE

RF_CHANNEL_RELEASE


DN9814277 17



3.10 Internal handover intra for source side (phase 10)This phase 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. The RCSPRB decides on the basis of the results whether the handover is performed. When the handover con-ditions 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. Next, the HASPRB converts the DX cause for the appropriate han-dover.

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.

If a failure occurs on the source side before the assignment command is received, 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 10 Internal handover intra for source side (phase 10)

3.11 Internal handover inter for source side (phase 11)This phase covers the internal inter-cell handover signalling for the source side on an SDCCH or a TCH.

MS BTS BSC MSC


PHYSICAL_CONTEXT_REQUEST_S

PHYSICAL_CONTEXT_CONFIRM_S

ASSIGNMENT_COMMAND

ASSIGNMENT_COMMAND

RF_CHANNEL_RELEASE


18 DN9814277





The success and failure cases are handled as described in Internal handover intra for source side.

Figure 11 Internal handover inter for source side (phase 11)

3.12 External handover for target side (phase 12)This phase 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 han-dover. If the signalling finishes successfully, the HASPRB updates the handover success counter, and the DX cause is conveyed to the following phase.

If a failure occurs, 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, by the HASPRB.

MS BTS BSC MSC


HO_CMD HANDOVER_COMMAND

HO_PERFORMED

RF_CHANNEL_RELEASE


DN9814277 19



Figure 12 External handover for target side (phase 12)

3.13 Internal handover intra for target side (phase 13)This phase covers the internal intra-cell handover signalling for the target side on an SDCCH and a TCH.


See Internal handover intra for source side for a successful case.

If a failure occurs 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 the informative counters.

The HASPRB sets the flag restore_old as TRUE and includes it in the DX cause that is sent to the ABIPRB to indicate that the MS returns to the old channel. The source side

MS BTS BSC MSC

HO_REQUEST1

2

3

4

HANDOVER_ACCESS5 >

HO_DETECTION6

7

8

SABM ESTABLISH_INDICATION9 > 10

UA11

HANDOVER_COMPLETE12

RR13

HANDOVER_COMPLETE14

15

CHANNEL_ACTIVATION


HO_REQUEST_ACK

HO_DETECTION

PHYSICAL_INFO

HO_COMPLETED

20 DN9814277




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.

If the failure occurs after the assignment has been completed on the target side, the success cause is overwritten and the signalling continues as call clearing.

Figure 13 Internal handover intra for target side (phase 13)

3.14 Internal handover inter for target side (phase 14)This phase covers the internal inter-cell handover signalling for the target side on an SDCCH or a TCH.


The success and failure cases are handled as described in Internal handover intra for target side.

MS BTS BSC MSC

SABM ESTABLISH_INDICATION

UA

ASSIGNMENT_COMPLETE

RR

CHANNEL_ACTIVATION


HO_PERFORMED

DN9814277 21



Figure 14 Internal handover inter for target side (phase 14)

3.15 Conversation (phase 15)This phase covers MM signalling between the MS and the MSC during conversation on a TCH.


The phase starts when the BSC receives the CONNECT ACK message. The successful DX cause is received from the previous phase and conveyed further to the following phase.

If a failure occurs, the successful DX cause is overwritten with the failure cause and the signalling continues as call clearing. The RRMPRB updates the failure counter.

Figure 15 Conversation (phase 15)

MS BTS BSC MSC

HANDOVER_ACCESS

HO_DETECTION

SABM ESTABLISH_INDICATION

UA

PHYSICAL_INFO

HANDOVER_COMPLETE

RR

HANDOVER_COMPLETE

CHANNEL_ACTIVATION


HO_PERFORMED

MS BTS BSC MSC

CONNECT ACK CONNECT ACK

CHANNEL RELEASE CLEAR COMMAND

22 DN9814277


Id:0900d805808c0d49Confidential

List of call related DX causes in BSC

4 List of call related DX causes in BSCEach success and failure cause has its own number that is used to identify it. The cause numbers, codes and descriptions are listed in the following sections.

For more information on the relations of DX causes and BSSMAP causes, see DX and BSSMAP cause mapping.

4.1 Success causesThe success causes are described below:

Number Cause code and description

10 location_update_c

Location updates.

20 facch_emergency_call_c

FACCH call for which the establishment cause is emergency call.

21 facch_reestablishment_c

FACCH call for which the establishment cause is re-establishment.

22 facch_answer_to_pagin_c

FACCH call for which the establishment cause is answering to paging.

23 facch_mo_speech_call_c

FACCH call for which the establishment cause is mobile originating speech call.

24 facch_mo_data_call_c

FACCH call for which the establishment cause is mobile originating data call.

25 facch_other_procedure_c

FACCH call for which the establishment cause is other procedure.

26 facch_mt_data_call_c

FACCH call for which the establishment cause is mobile terminating data call.

27 facch_imsi_detach_c

IMSI detach on the TCH channel due to SDCCH congestion.

40 basic_emergency_call_c

Basic call for which the establishment cause is emergency call.

41 basic_reestablishment_c

Basic call for which the establishment cause is re-establishment.

42 basic_answer_to_pagin_c

Basic call for which the establishment cause is answering to paging.

43 basic_mo_speech_call_c

Basic call for which the establishment cause is mobile originating speech call.

DN9814277 23

Call Related DX Causes in BSC List of call related DX causes in BSC


44 basic_mo_data_call_c

Basic call for which the establishment cause is mobile originating data call.

45 basic_other_procedure_c

Basic call for which the establishment cause is other procedure.

46 basic_mt_data_call_c

Basic call for which the establishment cause is mobile terminating data call.

47 basic_imsi_detach_c

IMSI detach on the SDCCH channel.

80 ext_in_ul_quality_c

An incoming external handover. The handover setup cause is uplink quality.

81 ext_in_ul_strength_c

An incoming external handover. The handover setup cause is uplink strength.

82 ext_in_dl_quality_c

An incoming external handover. The handover setup cause is downlink quality.

83 ext_in_dl_strength_c

An incoming external handover. The handover setup cause is downlink strength.

84 ext_in_distance_c

An incoming external handover. The handover setup cause is dis-tance.

85 ext_in_o_and_m_inter_c

An incoming external handover. The handover setup cause is O and M intervention.

86 ext_in_resp_to_msc_invoc_c

An incoming external handover. The handover setup cause is resp_to_msc_invoc.

87 ext_in_better_cell_c

An incoming external handover. The handover setup cause is better cell.

88 ext_in_directed_retry_c

An incoming external handover. The handover setup cause is directed retry.

89 ext_in_unexpected_c

An incoming external handover. The handover setup cause is unex-pected.

90 ext_in_switch_crc_pool_c

An incoming external handover attempt for changing the A interface circuit pool.


24 DN9814277




91 ext_in_pre_empt_c

An incoming external handover. The handover setup cause is pre-emption.

92 ext_in_bsc_trho_c

An incoming external handover. The handover setup cause is BSC traffic reason handover.

93 ext_in_isho_c

An incoming external inter-system handover.

94 ext_in_int_ho_to_ext_c

An incoming MSC-controlled handover generated from an internal handover.

95 ext_in_dtm_no_res_avail_c

An incoming external handover due to no free PS resources for a DTM call in the source cell.

96 ext_in_dtm_traffic_c

An incoming external handover due to DTM disabled in the source cell and PCU quality control.

100 ext_out_dl_rxlev_c

An outgoing external handover. The handover setup cause is downlink rx level.

101 ext_out_ul_rxlev_c

An outgoing external handover. The handover setup cause is uplink rx level.

102 ext_out_dl_rxqual_c

An outgoing external handover. The handover setup cause is downlink rx quality.

103 ext_out_ul_rxqual_c

An outgoing external handover. The handover setup cause is uplink rx quality.

104 ext_out_dl_interf_c

An outgoing external handover. The handover setup cause is downlink interference.

105 ext_out_ul_interf_c

An outgoing external handover. The handover setup cause is uplink interference.

106 ext_out_distance_c

An outgoing external handover. The handover setup cause is dis-tance.

107 ext_out_pbgt_ho_c

An outgoing external handover. The handover setup cause is PBGT handover.

108 ext_out_umbrella_ho_c

An outgoing external handover. The handover setup cause is umbrella handover.


DN9814277 25



109 ext_out_forced_ho_c

An outgoing external handover. The handover setup cause is forced handover.

110 ext_out_dr_ho_c

An outgoing external handover. The handover setup cause is DR (directed retry) handover.

111 ext_out_tr_ho_c

An outgoing external handover. The handover setup cause is TR (traffic reason) handover.

112 ext_out_idr_ho_c

An outgoing external handover. The handover setup cause is IDR handover.

113 ext_out_pre_empt_ho_c

An outgoing external handover. The handover setup cause is pre-emption handover.

114 ext_out_rap_fld_drop_c

An outgoing external handover. The handover setup cause is rapid field drop.

115 ext_out_low_distance_c

An outgoing external handover. The handover setup cause is low distance (extended cell radius functionality).

116 ext_out_switch_crc_pool_c

An outgoing external handover attempt to change the A interface circuit pool.

117 ext_out_slow_moving_ms_c

An outgoing external handover. The handover setup cause is 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 criteria.

118 ext_out_det_slow_mov_ms_c

An outgoing external handover. The handover setup cause is low speed of MS. The slow moving detection is based on the MS speed indications sent by the BTS.

119 ext_out_det_fast_mov_ms_c

An outgoing external handover. The handover setup cause is high speed of MS. The fast moving detection is based on the MS speed indications sent by the BTS.

120 inter_dl_rxlev_c

An internal inter handover. The handover setup cause is downlink rx level.

121 inter_ul_rxlev_c

An internal inter handover. The handover setup cause is uplink rx level.

122 inter_dl_rxqual_c

An internal inter handover. The handover setup cause is downlink rx quality.


26 DN9814277




123 inter_ul_rxqual_c

An internal inter handover. The handover setup cause is uplink rx quality.

124 inter_dl_interf_c

An internal inter handover. The handover setup cause is downlink interference.

125 inter_ul_interf_c

An internal inter handover. The handover setup cause is uplink inter-ference.

126 inter_distance_c

An internal inter handover. The handover setup cause is distance.

127 inter_pbgt_ho_c

An internal inter handover. The handover setup cause is PBGT han-dover.

128 inter_umbrella_ho_c

An internal inter handover. The handover setup cause is umbrella handover.

129 inter_forced_ho_c

An internal inter handover. The handover setup cause is forced han-dover.

130 inter_dr_ho_c

An internal inter handover. The handover setup cause is DR han-dover.

131 inter_tr_ho_c

An internal inter handover. The handover setup cause is TR (traffic reason) handover.

132 inter_idr_ho_c

An internal inter handover. The handover setup cause is IDR han-dover.

133 inter_pre_empt_ho_c

An internal inter handover. The handover setup cause is pre-emption handover.

134 inter_rap_fld_drop_c

An internal inter handover. The handover setup cause is rapid field drop.

135 inter_low_distance_c

An internal inter handover. The handover setup cause is low distance (extended cell radius functionality).

136 inter_ok_ci_ratio_c

An internal inter handover. The handover setup cause is ok C/I ratio (Underlay-overlay handover).

137 inter_bad_ci_ratio_c

An internal inter handover. The handover setup cause is bad C/I ratio (Underlay-overlay handover).


DN9814277 27



138 inter_slow_moving_ms_c

An internal inter handover. The handover setup cause is 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 criteria.

139 inter_det_slow_mov_ms_c

An internal inter handover. The handover setup cause is low speed of the MS. The slow moving detection is based on the MS speed indica-tions sent by the BTS.

140 intra_dl_interf_c

An internal intra handover. The handover setup cause is downlink interference.

141 intra_ul_interf_c

An internal intra handover. The handover setup cause is uplink inter-ference.

142 intra_forced_ho_c

An internal intra handover. The handover setup cause is forced han-dover.

143 intra_dl_rxqual_c

An internal intra handover. The handover setup cause is downlink rx quality.

144 intra_ok_ci_ratio_c

An internal intra handover. The handover setup cause is ok C/I ratio (Underlay-overlay handover).

145 intra_bad_ci_ratio_c

An internal intra handover. The handover setup cause is bad C/I ratio (Underlay-overlay handover).

146 intra_pre_empt_ho_c

An internal intra handover. The handover setup cause is pre-emption handover.

147 intra_distance_c

An internal intra-cell handover from a normal area to an extended area is performed when the timing advance (TA) of the MS equals or is greater than that defined by the parameter maxMSDistanceHO-Threshold.

148 intra_low_distance_c

An internal intra-cell handover from an extended area to a normal area is performed when the timing advance (TA) of the MS equals or is greater than that defined by the parameter minMSDistanceHO-Threshold.

149 intra_dr_ho_c

Assignment attempt from an SDCCH to a super-reuse frequency.

150 intra_direct_access_c

A successful internal intra-cell handover from a dedicated control channel to a super-reuse TRX. Handover setup cause is direct access.


28 DN9814277




151 intra_gprs_ho_c

An internal intra handover. The handover is performed in order to get more resources for GPRS.

152 intra_ho_to_amr_hr_c

An internal intra-cell handover from AMR FR to AMR HR.

153 intra_ho_to_amr_fr_c

An internal intra-cell handover from AMR HR to AMR FR.

154 intra_inter_band_tch_c

A TCH-TCH handover that has been made due to load reasons between BTSs on different frequency bands of a segment.

155 intra_inter_band_sdc_c

An SDCCH-SDCCH handover, based on SDCCH reservation duration in a BTS on the BCCH frequency band, to a BTS on another frequency band.

156 inter_det_fast_mov_ms_c

An internal inter handover. The handover setup cause is high speed of the MS. The fast moving detection is based on the MS speed indi-cations sent by the BTS.

157 inter_erfd_ho_c

Handover cause Enhanced Field Drop handover.

158 inter_direct_access_c

A successful internal inter-cell handover from a dedicated control channel to a super-reuse TRX. Handover setup cause is direct access.

159 inter_bsc_trho_c

An internal inter handover whose setup cause is BSC traffic reason handover.

160 inter_dadlb_c

An internal inter handover whose setup cause is Direct Access to Desired Layer/Band.

162 inter_dtm_no_res_avail_c

An internal inter-cell handover due to no free PS resources for a DTM call in the source cell.

163 ext_out_erfd_ho_c

Handover cause Enhanced Rapid Field Drop handover.

164 ext_out_bsc_trho_c

An outgoing external handover whose setup cause is BSC traffic reason handover.

166 intra_inter_bts_type_tch_c

A TCH-TCH handover from one type of BTS to anothert type due to load reasons within a segment.

167 intra_inter_bts_type_sdc_c

An SDCCH-SDCCH handover, based on SDCCH reservation duration from one type of BTS to another type within a segment.


DN9814277 29



168 intra_ho_due_to_hscsd_c

An internal intra-cell handover made to enable an HSCSD upgrade.

169 intra_inter_band_due_lev_c

A TCH-TCH handover from a non-BCCH frequency layer between BTSs on different frequency bands of a segment, performed due to weak downlink signal level.

170 intra_dtm_mo_cs_to_ps_c

An internal intra-cell handover due to mobile-originated DTM call establishment.

171 intra_dtm_mt_cs_to_ps_c

An internal intra-cell handover due to mobile-terminated DTM call establishment.

172 intra_dtm_mt_ps_to_ps_c

An internal intra-cell handover due to PCU-initiated DTM call realloca-tion.

173 intra_dtm_ps_to_cs_c

An internal intra-cell handover due to DTM call release.

174 intra_lrtch_ho_to_norm_c

An internal intra-cell handover that is performed to move a call on a Long Reach TCH to a TCH in the normal area of the cell.

175 intra_lrtch_ho_to_ext_c

An internal intra-cell handover that is performed to move a call on a Long Reach TCH to a TCH in the extended area of the cell.

176 intra_lrtch_ho_to_super_c

An internal intra-cell handover that is performed to move a call on a Long Reach TCH to a TCH in the super extended area of the cell.

177 intra_ho_ext_to_super_c

An internal intra-cell handover that is performed to move a call on the extended area to the super extended area of the cell.

178 intra_ho_super_to_ext_c

An internal intra-cell handover that is performed to move a call on the super extended area to the extended area of the cell.

179 intra_ho_from_hr_to_dhr_c

An internal intra-cell handover that is performed in order to move call from AMR-HR to DHR.

180 intra_ho_from_fr_to_dhr_c

An internal intra-cell handover that is performed in order to move call from AMR-FR to DHR.

181 intra_dhr_rxqual_dmux_ho_c

An internal intra-cell handover starting from OSC DHR based on Rx quality

182 intra_rxlev_diff_dmux_ho_c

An internal intra-cell handover starting from OSC DHR based on UL Rx level difference between the multiplexed DHR TCHs


30 DN9814277




183 intra_dhr_rxlev_dmux_ho_c

An internal intra-cell handover starting from OSC DHR based on Rx level

184 intra_ho_from_fr_to_dfr_c

An internal intra-cell handover that is performed in order to move call from AMR-FR to DFR

185 intra_dfr_rxqual_dmux_ho_c

An internal intra-cell handover starting from OSC DFR based on Rx quality

186 intra_dfr_rxl_df_dmux_ho_c

An internal intra-cell handover starting from OSC DFR based on UL Rx level difference between the multiplexed DFR TCHs

187 intra_dfr_rxlev_dmux_ho_c

An internal intra-cell handover starting from OSC DFR based on Rx level

188 intra_mcpa_pbho_tch_c

An internal intra-cell power balancing handover to move calls from TSLs experiencing high power compression to better TSLs (within an MCPA enabled Segment).

190 ext_out_isho_c

An outgoing external inter-system handover. The handover setup cause is BSC traffic.

191 ext_out_inter_system_da_c

An outgoing external inter-system direct access handover. The handover setup cause is direct access handover.

192 ext_out_ibho_to_gsm_c

An outgoing external IMSI based handover from the source GSM network to the GSM authorised networks. The handover setup cause is BSC traffic load.

193 ext_out_ibho_to_utran_c

An outgoing external IMSI based handover from the source GSM network to the UTRAN authorised networks. The handover setup cause is BSC traffic.

194 ext_out_int_ho_to_ext_c

An outgoing MSC-controlled handover generated from an internal handover.

195 ext_out_dtm_no_res_avail_c

An outgoing external handover due to no free PS resources for a DTM call in the serving cell.

196 ext_out_dtm_disabled_c

An outgoing external handover due to DTM disabled in the serving cell.

197 ext_out_pcu_qual_cntrl_c

An outgoing external handover due to PCU quality control in the serving cell.


DN9814277 31



4.2 Failure causesThe failure causes are divided into the following groups according to the program block that sets the cause in question:

• causes set by the Abis Interface Program Block (ABIPRB) • causes set by the Radio Connection Supervision Program Block (RCSPRB) or

Radio Resource Management Program Block (RRMPRB) • causes set by the A interface Signalling Program Block in BSC (AIVPRB) • causes set by the Speech Circuit Control in GSM BSC A interface (SC7PRB) • causes set by the Resource Control Program Block in BSC (RC0PRB) • causes set by the Handover Attempt Supervisor Program Block (HASPRB) • causes set by the DX MSC (MSC).

Causes set by the Abis Interface Program Block (ABIPRB)

198 ext_out_dtm_ho_to_dtm_c

An outgoing external handover due to DTM not supported in the serving cell.

199 ext_out_dtm_ho_to_wcdma_c

An outgoing external handover for mobile stations that support WCDMA but not DTM.

240 inter_dtm_disabled_c

An internal inter-cell handover due to DTM disabled in the source cell.

241 inter_pcu_qual_cntrl_c

An internal inter-cell handover due to PCU quality control in the source cell.

242 inter_dtm_ho_to_dtm_c

An internal inter-cell handover due to DTM not supported in the source cell.

243 inter_mss_trg_bss_int_ho_c

An internal inter-cell handover due to Internal Handover requested by MSS



300 user_act_block_c

Channel blocking caused by the user.

301 netw_act_block_c

Channel blocking caused by the network.

302 bts_fail_block_c

Channel blocking caused by a BTS failure.

303 lapd_fail_block_c

Channel blocking caused by an LAPD failure.

32 DN9814277




304 abis_fail_block_c

Channel blocking caused by an Abis failure.

305 abis_msg_corrup_to_bts_c

The packing of the Abis interface message fails.

306 ass_fail_msg_c

The Abis interface receives an ASSIGNMENT FAILURE message from the MS during a Basic Call.

307 block_slave_c

Channel blocking caused by some other reason than the ones given above.

308 ch_act_nack_c

The Abis interface receives a CHANNEL ACTIVATION NACK message or its contents have been corrupted.

309 ch_act_nack_om_inter_c

The Abis interface receives a CHANNEL ACTIVATION NACK message, and the cause is O and M intervention.

310 ch_act_nack_equip_fail_c

The Abis interface receives a CHANNEL ACTIVATION NACK message, and the cause is equipment failure.

311 ch_act_nack_encryp_alg_c

The Abis interface receives a CHANNEL ACTIVATION NACK message and the cause is encryption algorithm not supported.

312 ch_act_nack_rad_ch_alr_a_c

The Abis interface receives a CHANNEL ACTIVATION NACK message and the cause is radio channel already allocated.

313 ch_act_nack_serv_not_ava_c

The Abis interface receives a CHANNEL ACTIVATION NACK message and the cause is service is not available.

314 ch_act_fail_c

The Abis interface receives a CHANNEL ACTIVATION ACK message and its contents have been corrupted or a timer expires while waiting for the message.

315 conn_fail_c

The Abis interface receives a CONNECTION FAILURE message.

316 conn_fail_rad_inf_fail_c

The Abis interface receives a CONNECTION FAILURE message and its cause is radio interface failure.

317 conn_fail_rad_link_fail_c

The Abis interface receives a CONNECTION FAILURE message and its cause is radio link failure.

318 conn_fail_rem_trans_fail_c

The Abis interface receives a CONNECTION FAILURE message and its cause is remote transcoder failure.


DN9814277 33



319 data_ind_corrup_c

The Abis interface receives a DATA INDICATION message whose contents have been corrupted.

320 err_ind_c

The Abis interface receives an ERROR INDICATION message.

321 estab_ind_fail_c

A timer expires while waiting for an ESTABLISH INDICATION message.

322 estab_conf_fail_c

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.

323 ho_fail_c

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.

324 ho_detect_fail_c

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.

325 mode_mod_nack_c

The Abis interface receives a MODE MODIFY NACK message.

326 mode_mod_ack_fail_c

The Abis interface receives a MODE MODIFY ACK message whose contents have been corrupted or a timer expires while waiting for the message.

327 no_meas_result_c

No measurement result messages from the BTS.

328 no_resp_from_copro_c

Timer expires because the co-process does not respond. A BSC-internal failure.

329 phy_cont_conf_fail_c

The Abis interface receives a PHYSICAL CONTEXT CONFIRM message. The contents have been corrupted or a timer expires while waiting for the message.

330 rcs_alg_start_ack_fail_c

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.

331 rcs_alg_cl_ack_fail_c

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.

332 rc0_disco_ind_c

The Abis interface receives an rco_disconnect_ind message from RC0.


34 DN9814277




333 rf_ch_rel_ack_fail_c

The Abis interface receives an RF CH REL ACK message whose contents have been corrupted or a timer expires while waiting for the message.

334 rel_ind_c

The Abis interface receives a RELEASE INDICATION message.

335 rel_ind_fail_c

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.

336 signalling_error_c

DTAP signalling fails.

337 state_conflict_c

An attempt to activate a blocked channel in the Abis interface.

338 type_conflict_c

An attempt to activate a channel with the wrong information in the Abis interface.

339 forced_rel_c

Forced TCH release.

340 rej_phantom_res_c

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.

341 overload_c

Overload message from the BTS.

342 abi_switchover_c

The BCSU switchover has been started.

343 sapi_3_fail_c

During SMS establishment, the Abis interface receives a RELEASE INDICATION message or the ESTABLISH_INDICATION message received has been corrupted.

344 paging_msg_fail_c

The Abis interface receives an MS PAGING message and the channel has been blocked.

345 ch_required_fail_c

The Abis interface receives a CHANNEL REQUIRED message whose contents have been corrupted.

346 mode_mod_nack_equip_fail_c

The Abis interface receives a MODE MODIFY NACK message with the cause equipment failure.

347 mode_mod_nack_trc_rat_un_c

The Abis interface receives a MODE MODIFY NACK message with the cause requested transcoding/rate adaption not available.


DN9814277 35



348 rrm_serv_req_nack_c

The Abis interface receives an RRM CH SER REQ NACK message.

349 ch_mode_mod_fail_c

The Abis interface receives a CH MODE MODIFY ACK message and the mode does not correspond to the requested mode.

350 ass_fail_c

Timer expires while waiting for the ASSIGNMENT COMPLETE message.

351 dr_fail_c

Directed retry procedure fails.

352 coprocess_fail_c

A failure has occurred in co-process.

353 err_rep_enc_alg_not_imp_c

An ERROR REPORT message is received from the BTS and the cause is encryption algorithm not implemented.

354 error_report_c

An ERROR REPORT message is received from the BTS.

355 ch_act_nack_ch_mode_err_c

The Abis interface receives a CHANNEL ACTIVATION NACK message and the failure cause is either not implemented unspecified or mandatory IE error.

356 ch_act_nack_gen_ie_err_c

The Abis interface receives a CHANNEL ACTIVATION NACK message and the failure cause is general IE error.

357 speech_version_unavail_c

The Abis interface receives an ASSIGNMENT FAILURE message or a HANDOVER FAILURE message from the MS during an assignment or a handover and the RR cause is channel mode unacceptable.

358 ignored_double_rand_acc_c

If two incoming random accesses have the same frame number, the latter one is ignored when random access buffering is used in an extended range cell.

359 rtsl_reconf_fail_c

Reconfiguration of a dynamic SDCCH resource has failed during immediate assignment. All SDCCH resources controlled by the BCSU are already in use.

360 ho_interrupted_c

If an assignment procedure is started before the MS is assigned to move to a new channel, the handover attempt is terminated with DX cause ho_interrupted_c.

361 downgrade_c

Channel release caused by a downgrade.

362 ho_not_started_c

Rejected handover start due to other ongoing procedures.


36 DN9814277




363 conf_change_not_allowed_c

Rejected upgrade, downgrade or ALA due to other ongoing proce-dures.

364 conf_change_bts_fail_c

Failed configuration change due to a MODE MODIFY NACK message or no answer from the BTS.

365 conf_change_ms_fail_c

Failed configuration change due to a configuration change reject or no answer from the MS.

366 hscsd_copro_fail_c

Channel release caused by a failure in another channel in the HSCSD configuration.

367 sub_timer_c

Timer expiry due to sub-channel not responding to the main channel in the HSCSD connection.

368 forced_ho_block_c

Forced handover due to channel or TRX block.

369 upgrade_fail_c

Upgrade procedure failure.

370 estab_ind_corrupted_c

An ESTABLISH INDICATION message which the Abis interface receives because of the corrupted contents of the message.

373 bsc_bsc_conflict_c

Unsuccessful channel setup when BSC-BSC conflict control is used.

374 cn_id_not_found_c

TCH or SDCCH channel release that occurs because a global CN ID that would match the mobile's IMSI is not found in the BSC for the CS PAGING RESPONSE message.

375 ciph_not_support_trx_c

Number of failed ciphering algorithm selections due to incompatible ciphering algorithm support

376 dfca_hop_prm_not_valid_c

Number of SDCCH channel releases caused by invalid DFCA hopping parameters

377 etp_failure_c

Number of TCH release due to ETPx resource reservation failure.


DN9814277 37



Causes set by the Radio Connection Supervision Program Block (RCSPRB) or Radio Resource Management Program Block (RRMPRB)

Causes set by the A interface Signalling Program Block in BSC (AIVPRB)


400 timing_advance_c

The call is released after the distance between the MS and the BTS has reached the maximum value allowed, that is, after the MS has exceeded the planned cell boundaries.

401 rrm_switch_crc_pool_c

The Radio Resource Management Program Block (RRMPRB) sets this cause in the TCH RESOURCE REQUEST NEGATIVE ACKNOWLEDGEMENT message in order to indicate the A interface circuit pool change request.

402 rrm_speech_ver_unavail_c

The requested speech version is not supported by the target BTS.

403 bts_not_supporting_c

A resource that is not supported by the BTS has been requested.

404 ms_not_supporting_c

A resource that is not supported by the MS has been requested.

405 rrm_invalid_cell_c

The traffic channel allocation in the external handover has failed. The HANDOVER REQUEST message received by the BSS indicates a target cell that is not controlled by the BSS.

409 unavail_codec_type_conf_c

Cause set when its unable to allocate the provided speech codecs in a segment during normal Assignment or External Handover. Assign-ment Failure or Handover Failure messages are sent to MSC which report that requested codec type or codec configuration is unavail-able.


600 aiv_hand_act_fail_c

Activation of a hand process fails in the AIVPRB master.

601 aiv_ssp_c

SCCP connection establishment is not possible because the subsys-tem is in the prohibited status. The situation is detected by the AIVPRB master.

602 sccp_conn_fail_c

SCCP connection establishment fails. A CREF message is received from the MSC.

603 sccp_conn_timeout_c

No response from the MSC to the SCCP connection establishment.

604 sccp_release_c

Abnormal release of the SCCP connection (RLSD received).

38 DN9814277




606 global_reset_c

State change of an SCCP subsystem or a RESET message from the MSC.

608 no_dtap_from_msc_c

No DTAP message from the MSC after a successful SCCP connec-tion establishment.

609 ho_denied_assign_c

Starting of the handover is not allowed because an assignment pro-cedure is in progress.

610 ho_denied_ciphering_c

Starting of the handover is not allowed because the ciphering proce-dure is in progress.

611 ho_denied_clear_c

Starting of the handover is not allowed because the call clearing pro-cedure is in progress.

612 ho_denied_no_sccp_conn_c

Starting of an external SDCCH handover is not allowed because the SCCP connection establishment is not complete.

613 T7_expiry_c

Expiry of GSM timer T7.

614 T10_expiry_c

Expiry of GSM timer T10.

615 aiv_crct_res_timeout_c

Timeout in the AIVPRB while allocating an A interface speech circuit.

616 aiv_crct_conn_timeout_c

Timeout in the AIVPRB while connecting an A interface speech circuit.

617 aiv_crct_disconn_timeout_c

Timeout in the AIVPRB while disconnecting an A interface speech circuit.

618 aiv_crct_rel_timeout_c

Timeout in the AIVPRB while releasing an A interface speech circuit.

619 aiv_timeout_c

Timeout in the AIVPRB in BSC internal communication.

620 act_ctrl_timeout_c

The BSC internal supervision timer, which supervises the communi-cation between the Abis and the A interface, has expired.

621 invalid_bssmap_msg_c

An erroneous message, which leads to the clearing of the call, is received from the MSC.

622 unknown_a_pcm_c

Message received concerning an unknown A interface circuit.


DN9814277 39



623 ho_denied_no_proper_crc_c

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.

624 ch_type_mismatch_c

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 con-tradictory with the type of TCH where the call is to be maintained.

625 aiv_transc_or_rate_unava_c

The TCH type requested by the MSC is not supported.

626 aiv_speech_version_unava_c

The speech coder version requested by the MSC is not supported.

627 aiv_pagin_refus_big_load_c

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.

628 aiv_conn_refresh_timeout_c

Timeout in the connection refreshing procedure.

629 aiv_conn_refresh_failed_c

The connection refreshing procedure has failed.

630 no_support_a_if_type_c

Cause is set when, Assignment Failure or Handover Failure messages are sent from BSC to MSC which report that requested A-interface type is not supported.

631 no_supp_redundancy_level_c

Cause set when MSC requested redundancy level for data calls is not supported by the BSC. Assignment Failure or Handover Failure messages are sent, which report that requested redundancy level is not supported.

632 no_supp_codec_type_conf_c

Cause set when none of the codecs provided by MSC in Assign-ment/Handover request are supported by the BSC. Assignment Failure or Handover Failure messages are sent, which report that requested codec type or codec configuration is not supported.

633 unavail_a_if_type_c

Cause set when Assignment Failure or Handover Failure messages are sent to MSC which report that requested A-interface type is unavailable.

634 t25_timer_expiry_c

Cause set when T25 timer expires waiting for Internal Handover Command from MSC.


40 DN9814277




Causes set by the Speech Circuit Control in GSM BSC A interface (SC7PRB)


800 a_tsl_user_mismatch_c

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.

801 sc7_crct_res_timeout_c

Timeout in the SC7PRB while allocating an A interface speech circuit.

802 sc7_crct_conn_timeout_c

Timeout in the SC7PRB while connecting an A interface speech circuit.

803 sc7_crct_disconn_timeout_c

Timeout in the SC7PRB while disconnecting an A interface speech circuit.

804 sc7_crct_rel_timeout_c

Timeout in the SC7PRB while releasing an A interface speech circuit.

805 a_tsl_blocked_c

Assignment of a circuit that is blocked.

806 a_tsl_status_unknown_c

Assignment of a circuit whose status is unknown.

807 lsi_access_fail_c

Access to the Line Signalling File (LSIGNL) failed.

808 scc_access_fail_c

Access to the System-controlled Circuit State File (SCCTST) failed.

809 undef_tsl_in_lsi_c

The circuit concerned is not defined in the LSIGNL file.

810 crct_equipment_fail_c

The SC7PRB has detected a situation which has been caused by hardware problems.

811 reset_crct_c

The RESET CIRCUIT message has been received from the MSC.

813 sc7_ssp_c

An error caused by the SCCP prohibited status. The situation has been detected by the SC7PRB.

815 a_pcm_fault_c

A fault has been detected in the 2-Mbit PCM connection.

817 a_crct_removed_c

A speech circuit has been removed from use.

819 a_et_state_change_c

State change of the ET has occurred.

DN9814277 41



Causes set by the Resource Control Program Block in BSC (RC0PRB)


700 rc0_hand_act_fail_c

The RC0PRB master fails to activate a hand process.

701 a_crct_alr_res_c

Assignment of a speech circuit which has already been allocated.

702 a_crct_conn_err_c

Connection error in marker while connecting an A interface speech circuit.

703 rc0_crct_conn_timeout_c

Timeout in the RC0PRB while connecting an A interface speech circuit.

704 access_out_of_crct_tbl_c

Requested speech circuit not found in the circuit control table.

705 a_crct_rel_err_c

Circuit release error in marker while releasing an A interface speech circuit.

706 rc0_transc_or_rate_unava_c

The requested channel rate corresponding to the A interface circuit pool has not been defined on the A interface.

707 rc0_cip_type_mismatch_c

The circuit type A is totally contradictory with the TCH channel rate requirement or the data rate requirement implies the circuit pool change.

708 rc0_inv_msg_contents_c

The radio interface data rate requirement is totally contradictory with the A interface pool configuration.

709 rc0_req_speech_ver_unava_c

BSC has received either an ASSIGNMENT REQUEST or a HANDOVER REQUEST message containing speech codec versions, none of which are supported by the BSC.

710 rc0_hunting_queue_full_c

The hunting queue is full.

711 rc0_a_crct_congestion_c

There is no free circuit for the call.

712 rc0_a_search_error_c

The content of the hunting request message is invalid.

713 rc0_crct_pool_mismatch_c

The hunted circuit is from the wrong circuit pool.

714 rc0_rej_due_eme_call_c

The hunting queue is full. An emergency call has taken priority over the ordinary call.

42 DN9814277




Causes set by the Handover Attempt Supervisor Program Block (HASPRB)

715 rc0_ilc_file_error_c

A interface circuit reservation fails because no pool is available on the hunting list.

716 a_crct_conn_err_consec_c

Consecutive connection errors are encountered on the same A-inter-face circuit.

717 call_id_alr_allocated_c

Cause set when it finds that the call_id provided by the MSC in Assignment Request/Internal Handover Command/Handover Request is already being used in the BSC. Assignment Failure or Handover Failure messages are sent to MSC which report that call identifier is already allocated.

718 unavail_terr_resource _c

Cause is set when it is unable to reserve PCM-TSL resources for an AoTDM call during Internal/External Handover. BSSAP Handover Failure messages are sent which report that requested terrestrial resource is unavailable.


500 ho_not_allowed_c

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.

501 no_radio_res_avail_c

No radio resources in the BTS for channel reservation during handover signalling.

503 no_resp_from_coprocess_c

Signalling with the internal processes has failed during handover sig-nalling.

504 no_resp_to_radio_res_req_c

Target channel reservation has failed during handover signalling. No answer to the radio resource request.

505 has_state_conflict_c

Target channel reservation has failed. CHANNEL ACTIVATION ACK message not been received and the timer for it has expired.

506 clear_cmd_not_received_c

No CLEAR COMMAND has been received from the A interface during external source handover signalling.

507 ms_is_lost_c

The timer T3107, T3103 or T9113 has expired. An ASSIGNMENT COMPLETE or HANDOVER COMPLETE message has not been received. The MS has not established a channel to the target side.


DN9814277 43



Causes set by the DX MSC (MSC)These causes are only possible during signalling. The BSC cannot observe these causes if the phase is MM signalling (2) or conversation (15).

508 no_resp_to_ho_cpl_msg_c

Problems in sending the HANDOVER PERFORMED message by the BSC.

509 has_switchover_c

Switchover has been started and the handover has failed.

510 target_fail_c

Failure in the target channel.

511 source_fail_c

Failure in the source channel.

512 has_call_control_c

The master has failed to create a hand.

513 adj_cell_id_err_c

The handover attempt was interrupted when the BSC noticed that the target cell information (BCCH frequency and/or BSIC) received from the MSC in the HANDOVER COMMAND message is incorrect. This counter indicates that information in the source BSS Radio Network Configuration Database concerning adjacent cells is incorrect.


900 m_radio_if_mess_fail_c

Cause value 0x00 radio interface message failure received from the MSC.

901 m_radio_if_fail_c

Cause value 0x01 radio interface failure received from the MSC.

902 m_uplink_quality_c

Cause value 0x02 uplink quality received from the MSC.

903 m_uplink_strength_c

Cause value 0x03 uplink strength received from the MSC.

904 m_downlink_quality_c

Cause value 0x04 downlink quality received from the MSC.

905 m_downlink_strength_c

Cause value 0x05 downlink strength received from the MSC.

906 m_distance

Cause value 0x06 distance received from the MSC.

907 m_o_and_m_inter_c

Cause value 0x07 O and M intervention received from the MSC.

908 m_resp_to_msc_invoc_c

Cause value 0x08 response to MSC invocation received from the MSC.


44 DN9814277




909 m_call_control_c

Cause value 0x09 call control received from the MSC.

910 m_r_if_f_rev_to_old_c

Cause value 0x0A radio interface failure, reversion to old channel received from the MSC.

911 m_handover_succ_c

Cause value 0x0B handover successful received from the MSC.

912 m_better_cell_c

Cause value 0x0C better cell received from the MSC.

913 m_directed_retry_c

Cause value 0x0D directed retry received from the MSC.

914 m_equipment_fail_c

Cause value 0x20 equipment failure received from the MSC.

915 m_no_radio_res_avail_c

Cause value 0x21 no radio resource available received from the MSC.

916 m_req_terr_res_unava_c

Cause value 0x22 requested terrestrial resource unavailable received from the MSC.

917 m_ccch_overload_c

Cause value 0x23 ccch overload received from the MSC.

918 m_processor_overload_c

Cause value 0x24 processor overload received from the MSC.

919 m_bss_not_equipped_c

Cause value 0x25 bss not equipped received from the MSC.

920 m_ms_not_equipped_c

Cause value 0x26 ms not equipped received from the MSC.

921 m_tr_cod_rat_ad_unav_c

Cause value 0x30 requested transcoding/rate adaption unavailable received from the MSC.

922 m_ciph_alg_not_supp_c

Cause value 0x40 ciphering algorithm not supported received from the MSC.

923 m_terr_chan_alr_allc_c

Cause value 0x50 terrestrial circuit already allocated received from the MSC.

924 m_prot_err_b_bsc_msc_c

Cause value 0x60 protocol error between BSC and MSC received from the MSC.

925 m_unexpected_c

Unexpected failure from the MSC.


DN9814277 45



926 m_invalid_cell_c

Cause value 0x27 invalid cell received from the MSC.

927 m_invalid_msg_cont_c

Cause value 0x51 invalid message contents received from the MSC.

928 m_ie_or_field_missing_c

Cause value 0x52 information element or field missing received from the MSC.

929 m_incorrect_value_c

Cause value 0x53 incorrect value received from the MSC.

930 m_unknown_msg_type_c

Cause value 0x54 unknown message type received from the MSC.

931 m_unknown_ie_c

Cause value 0x55 unknown information element received from the MSC.

932 m_transc_or_rate_unavail_c

Cause value 0x30 requested transcoding/rate adaption unavailable received from the MSC.

933 m_cip_type_mismatch_c

Cause value 0x31 circuit pool mismatch received from the MSC.

934 m_switch_crc_pool_c

Cause value 0x32 switch circuit pool received from the MSC.

935 m_speech_version_unavail_c

Cause value 0x31 requested speech version unavailable received from the MSC.

936 m_pre_empt_c

Cause value 0x29 preemption received from the MSC.

937 m_traffic_c

Cause value 0x0F traffic received from the MSC.

938 m_traffic_load_c

Cause value 0x28 traffic load received from the MSC.

941 m_no_supp_codec_typ_conf_c

Cause value 0x44 Requested Codec Type or Codec received from MSC.

942 m_no_support_a_if_type_c

Cause value 0x45 Requested A-Interface Type not supportedre-ceived from MSC.

943 m_unavail_a_if_type_c

Cause value 0x36 Requested A-Interface Type unavailable received from MSC.

944 m_unavail_codec_typ_conf_c

Cause value 0x35 Requested Codec Type or Codec Configuration unavailable received from MSC


46 DN9814277




945 m_no_supp_redundancy_lvl_c

Cause value 0x46 Requested Redundancy Level not supported received from MSC


DN9814277 47

Call Related DX Causes in BSC DX and BSSMAP cause mapping


5 DX and BSSMAP cause mappingThe purpose of the following tables is to help the user to determine the relations between DX causes and BSSMAP causes.

The first table maps DX causes to BSSMAP causes and the second BSSMAP causes to DX causes.

5.1 DX causes mapped to BSSMAP causesThe following table lists the BSC-internal DX causes and the corresponding BSSMAP causes that are used on the A interface.

HEX Dec DX cause BSSMAP cause HEX DEC

50 80 ext_in_ul_quality_c Uplink quality 2 2

51 81 ext_in_ul_strength_c Uplink strength 3 3

52 82 ext_in_dl_quality_c Downlink quality 4 4

53 83 ext_in_dl_strength_c Downlink strength 5 5

54 84 ext_in_distance_c Distance 6 6

55 85 ext_in_o_and_m_inter_c O and M intervention 7 7

56 86 ext_in_resp_to_msc_invoc_c Response to MSC invocation 8 8

57 87 ext_in_better_cell_c Better cell C 12

58 88 ext_in_directed_retry_c Directed retry D 13

59 89 ext_in_unexpected_c Used if the cause of incoming external handover is not recogn-ised or not mentioned at all

5A 90 ext_in_switch_crc_pool_c Switch circuit pool 32 50

5B 91 ext_in_pre_empt_c Preemption 29 41

5C 92 ext_in_bsc_trho_c Traffic F 15

5D 93 ext_in_isho_c Used if the incoming external handover is an inter–system handover

5E 94 ext_in_int_ho_to_ext_c Traffic F 15

5F 95 ext_in_dtm_no_res_avail_c Traffic load 28 40

60 96 ext_in_dtm_traffic_c Traffic F 15

64 100 ext_out_dl_rxlev_c Downlink strength 5 5

65 101 ext_out_ul_rxlev_c Uplink strength 3 3

66 102 ext_out_dl_rxqual_c Downlink quality 4 4

67 103 ext_out_ul_rxqual_c Uplink quality 2 2

68 104 ext_out_dl_interf_c Downlink quality 4 4

69 105 ext_out_ul_interf_c Uplink quality 2 2

64 106 ext_out_distance_c Distance 6 6

6B 107 ext_out_pbgt_ho_c Better cell C 12

6C 108 ext_out_umbrella_ho_c Better cell C 12

48 DN9814277



DX and BSSMAP cause mapping

6D 109 ext_out_forced_ho_c O and M intervention 7 7

6E 110 ext_out_dr_ho_c Directed retry D 13

6F 111 ext_out_tr_ho_c Response to MSC invocation 8 8

70 112 ext_out_idr_ho_c Directed retry D 13

71 113 ext_out_pre_empt_ho_c Response to MSC invocation 8 8

72 114 ext_out_rap_fld_drop_c Uplink strength 3 3

73 115 ext_out_low_distance_c Distance 6 6

74 116 ext_out_switch_crc_pool_c Switch circuit pool 32 50

75 117 ext_out_slow_moving_ms_c Better cell C 12

76 118 ext_out_det_slow_mov_ms_c Better cell C 12

77 119 ext_out_det_fast_mov_ms_c Better cell C 12

78 120 inter_dl_rxlev_c Downlink strength 5 5

79 121 inter_ul_rxlev_c Uplink strength 3 3

7A 122 inter_dl_rxqual_c Downlink quality 4 4

7B 123 inter_ul_rxqual_c Uplink quality 2 2

7C 124 inter_dl_interf_c Downlink quality 4 4

7D 125 inter_ul_interf_c Uplink quality 2 2

7E 126 inter_distance_c Distance 6 6

7F 127 inter_pbgt_ho_c Better cell C 12

80 128 inter_umbrella_ho_c Better cell C 12

81 129 inter_forced_ho_c O and M intervention 7 7

82 130 inter_dr_ho_c Directed retry D 13

83 131 inter_tr_ho_c Response to MSC invocation 8 8

84 132 inter_idr_ho_c Directed retry D 13

85 133 inter_pre_empt_ho_c Response to MSC invocation 8 8

86 134 inter_rap_fld_drop_c Uplink strength 3 3

87 135 inter_low_distance_c Distance 6 6

88 136 inter_ok_ci_ratio_c Downlink quality 4 4

89 137 inter_bad_ci_ratio_c Downlink quality 4 4

8A 138 inter_slow_moving_ms_c Better cell C 12

8B 139 inter_det_slow_mov_ms_c Better cell C 12

8C 140 intra_dl_interf_c Downlink quality 4 4

8D 141 intra_ul_interf_c Uplink quality 2 2

8E 142 intra_forced_ho_c O and M intervention 7 7

8F 143 intra_dl_rxqual_c Downlink quality 4 4

90 144 intra_ok_ci_ratio_c Downlink quality 4 4

91 145 intra_bad_ci_ratio_c Downlink quality 4 4

92 146 intra_pre_empt_ho_c Response to MSC invocation 8 8


DN9814277 49



93 147 intra_distance_c Distance 6 6

94 148 intra_low_distance_c Distance 6 6

95 149 intra_dr_ho_c Directed retry D 13

96 150 intra_direct_access Downlink strength 5 5

97 151 intra_gprs_ho_c Traffic F 15

98 152 intra_ho_to_amr_hr_c Better cell C 12

99 153 intra_ho_to_amr_fr_c Better cell C 12

9A 154 intra_inter_band_tch_c Traffic F 15

9B 155 intra_inter_band_sdc_c Traffic F 15

9C 156 inter_det_fast_mov_ms_c Better cell C 12

9D 157 inter_erfd_ho_c Better cell C 12

9E 158 inter_direct_access_c Downlink strength 5 5

9F 159 inter_bsc_trho_c Traffic F 15

A0 160 inter_dadlb_c Traffic F 15

A2 162 inter_dtm_no_res_avail_c Traffic load 28 40

A3 163 ext_out_erfd_ho_c Better cell C 12

A4 164 ext_out_bsc_trho_c Traffic F 15

A6 166 intra_inter_bts_type_tch_c Traffic F 15

A7 167 intra_inter_bts_type_sdc_c Traffic F 15

A8 168 intra_ho_due_to_hscsd_c Traffic F 15

A9 169 intra_inter_band_due_lev_c Downlink strength 5 5

AA 170 intra_dtm_mo_cs_to_ps_c Traffic F 15

AB 171 intra_dtm_mt_cs_to_ps_c Traffic F 15

AC 172 intra_dtm_mt_ps_to_ps_c Traffic F 15

AD 173 intra_dtm_ps_to_cs_c Traffic F 15

AE 174 intra_lrtch_ho_to_norm_c O and M intervention 7 7

AF 175 intra_lrtch_ho_to_ext_c O and M intervention 7 7

B3 179 intra_ho_from_hr_to_dhr_c Better cell C 12

B4 180 intra_ho_from_fr_to_dhr_c Better cell C 12

B5 181 intra_dhr_rxqual_dmux_ho_c Better cell C 12

B6 182 intra_rxlev_diff_dmux_ho_c Better cell C 12

B7 183 intra_dhr_rxlev_dmux_ho_c Better cell C 12

B8 184 intra_ho_from_fr_to_dfr_c Better cell C 12

B9 185 intra_dfr_rxqual_dmux_ho_c Better cell C 12

BA 186 intra_dfr_rxl_df_dmux_ho_c Better cell C 12

BB 187 intra_dfr_rxlev_dmux_ho_c Better cell C 12

BC 188 intra_mcpa_pbho_tch_c Better cell C 12

BE 190 ext_out_isho_c Traffic F 15


50 DN9814277




BF 191 ext_out_inter_system_da_c Directed retry D 13

C0 192 ext_out_ibho_to_gsm_c Traffic load 28 40

C1 193 ext_out_ibho_to_utran_c Traffic F 15

C2 194 ext_out_int_ho_to_ext_c Traffic F 15

C3 195 ext_out_dtm_no_res_avail_c Traffic load 28 40

C4 196 ext_out_dtm_disabled_c Traffic F 15

C5 197 ext_out_pcu_qual_cntrl_c Traffic F 15

C6 198 ext_out_dtm_ho_to_dtm_c Call control 9 9

C7 199 ext_out_dtm_ho_to_wcdma_c Traffic F 15

F0 240 inter_dtm_disabled_c Traffic F 15

F1 241 inter_pcu_qual_cntrl_c Traffic F 15

F2 242 inter_dtm_ho_to_dtm_c Call control 9 9

F3 243 inter_mss_trg_bss_int_ho_c Response to an Internal Handover Enquiry Message

16 10

12C 300 user_act_block_c O and M intervention 7 7

12D 301 netw_act_block_c O and M intervention 7 7

12E 302 bts_fail_block_c Equipment failure 20 32

12F 303 lapd_fail_block_c Equipment failure 20 32

130 304 abis_fail_block_c Equipment failure 20 32

131 305 abis_msg_corrup_to_bts_ c Equipment failure 20 32

132 306 ass_fail_msg_c Radio interface failure, reversion to old channel

A 10

133 307 block_slave_c Equipment failure 20 32

134 308 ch_act_nack_c Radio interface failure 1 1

135 309 ch_act_nack_om_inter_c O and M intervention 7 7

136 310 ch_act_nack_equip_fail_c Equipment failure 20 32

137 311 ch_act_nack_encryp_alg_c Ciphering algorithm not supported 40 64

138 312 ch_act_nack_rad_ch_alr_a_c No radio resource available 21 33

139 313 ch_act_nack_serv_not_ava_c Requested transcoding/rate adaption unavailable

30 48

13A 314 ch_act_fail_c Equipment failure 20 32

13B 315 conn_fail_c Radio interface failure 1 1

13C 316 conn_fail_rad_inf_fail_c Radio interface failure 1 1

13D 317 conn_fail_rad_link_fail_c Radio interface failure 1 1

13E 318 conn_fail_rem_trans_fail_c Equipment failure 20 32

13F 319 data_ind_corrup_c Radio interface message failure 0 0

140 320 err_ind_c Radio interface failure 1 1

141 321 estab_ind_fail_c Radio interface message failure 0 0

142 322 estab_conf_fail_c Radio interface message failure 0 0


DN9814277 51



143 323 ho_fail_c Radio interface failure, reversion to old channel

A 10

144 324 ho_detect_fail_c Radio interface message failure 0 0

145 325 mode_mod_nack_c BSS not equipped 25 37

146 326 mode_mod_ack_fail_c Radio interface message failure 0 0

147 327 no_meas_result_c Radio interface failure 1 1

148 328 no_resp_from_copro_c Equipment failure 20 32

149 329 phy_cont_conf_fail_c Radio interface message failure 0 0

14A 330 rcs_alg_start_ack_fail_c Equipment failure 20 32

14B 331 rcs_alg_cl_ack_fail_c Equipment failure 20 32

14C 332 rc0_disco_ind_c Equipment failure 20 32

14D 333 rf_ch_rel_ack_fail_c Radio interface failure 1 1

14E 334 rel_ind_c Radio interface failure 1 1

14F 335 rel_ind_fail_c Radio interface message failure 0 0

150 336 signalling_error_c Radio interface failure 1 1

151 337 state_confligt_c Equipment failure 20 32

152 338 type_confligt_c Equipment failure 20 32

153 339 forced_rel_c Preemption 29 41

154 340 rej_phantom_res_c Radio interface message failure 0 0

155 341 overload_c CCCH overload 23 35

156 342 abi_switchover_c O and M intervention 7 7

157 343 sapi_3_fail_c Radio interface failure 1 1

158 344 paging_msg_fail_c Radio interface message failure 0 0

159 345 ch_required_fail_c Radio interface message failure 0 0

15A 346 mode_mod_nack_equip_fail_c Equipment failure 20 32

15B 347 mode_mod_nack_trc_rat_un_c Requested transcoding/rate adaption unavailable

30 48

15C 348 rrm_serv_req_nack_c No radio resource available 21 33

15D 349 ch_mode_mod_fail_c Radio interface failure 1 1

15E 350 ass_fail_c Radio interface message failure 0 0

15F 351 dr_fail_c No radio resource available 21 33

160 352 coprocess_fail_c Radio interface failure 1 1

161 353 err_rep_enc_alg_not_imp_c Ciphering algorithm not supported 40 64

162 354 error_report_c Radio interface failure 1 1

163 355 ch_act_nack_ch_mode_err_c Requested transcoding/rate adaption unavailable

30 48

164 356 ch_act_nack_gen_ie_err_c Radio interface message failure 0 0

165 357 speech_version_unavail_c Radio interface failure, reversion to old channel

A 10


52 DN9814277




166 358 ignored_double_rand_acc_c Radio interface message failure 0 0

167 359 rtsl_reconf_fail_c No radio resource available 21 33

168 360 ho_interrupted_c Equipment failure 20 32

169 361 downgrade_c Equipment failure 20 32

16A 362 ho_not_started_c Equipment failure 20 32

16B 363 conf_change_not_allowed_c Equipment failure 20 32

16C 364 conf_change_bts_fail_c BSS not equipped 25 37

16D 365 conf_change_ms_fail_c Radio interface failure 1 1

16E 366 hscsd_copro_fail_c Equipment failure 20 32

16F 367 sub_timer_c Equipment failure 20 32

170 368 forced_ho_block_c O and M intervention 7 7

171 369 upgrade_fail_c Equipment failure 20 32

172 370 estab_ind_corrupted_c Radio interface message failure 0 0

175 373 bsc_bsc_conflict_c Call control 9 9

176 374 cn_id_not_found_c Equipment failure 20 32

177 375 ciph_not_support_trx_c Ciphering algorithm not supported 40 64

178 376 dfca_hop_prm_not_valid_c Equipment failure 20 32

179 377 etp_failure_c Equipment Failure 20 32

190 400 timing_advance_c Distance 6 6

191 401 rrm_switch_crc_pool_c Switch circuit pool 32 50

192 402 rrm_speech_ver_unavail_c Requested speech version unavailable

33 51

193 403 rrm_bts_not_supporting_c Requested transcoding/rate adaption unavailable

30 48

194 404 rrm_ms_not_supporting_c MS not equipped 26 38

195 405 rrm_invalid_cell_c Invalid cell 27 39

199 409 unavail_codec_type_conf_c Requested Codec Type or Codec Configuration unavailable

35 23

1F4 500 ho_not_allowed_c Call control 9 9

1F5 501 no_radio_res_avail_c No radio resource available 21 33

1F7 503 no_resp_from_coprocess_c Equipment failure 20 32

1F8 504 no_resp_to_radio_res_req_c Equipment failure 20 32

1F9 505 has_state_confligt_c Equipment failure 20 32

1FA 506 clear_cmd_not_received_c Radio interface message failure 0 0

1FB 507 ms_is_lost_c Radio interface message failure 0 0

1FC 508 no_resp_to_ho_cpl_msg_c Equipment failure 20 32

1FD 509 has_switchover_c O and M intervention 7 7

1FE 510 target_fail_c Call control 9 9

1FF 511 source_fail_c Call control 9 9


DN9814277 53



200 512 has_call_control_c Call control 9 9

201 513 adj_cell_id_err_c Invalid cell 27 39

258 600 aiv_hand_act_fail_c Equipment failure 20 32

259 601 aiv_ssp_c Call control 9 9

25A 602 sccp_conn_fail_c Call control 9 9

25B 603 sccp_conn_timeout_c Call control 9 9

25C 604 sccp_release_c Call control 9 9

25E 606 global_reset_c Call control 9 9

261 609 ho_denied_assign_c Call control 9 9

262 610 ho_denied_ciphering_c Call control 9 9

263 611 ho_denied_clear_c Call control 9 9

264 612 ho_denied_no_sccp_conn_c Call control 9 9

265 613 T7_expiry_c Call control 9 9

266 614 T10_expiry_c Equipment failure 20 32

267 615 aiv_crct_res_timeout_c Equipment failure 20 32

268 616 aiv_crct_conn_timeout_c Equipment failure 20 32

269 617 aiv_crct_disconn_timeout_c Equipment failure 20 32

26A 618 aiv_crct_rel_timeout_c Equipment failure 20 32

26B 619 aiv_timeout_c Equipment failure 20 32

26C 620 act_ctrl_timeout_c Equipment failure 20 32

26D 621 invalid_bssmap_msg_c Protocol error between BSS and MSC

60 96

26E 622 unknown_a_pcm_c Requested terrestrial resource unavailable

22 34

26F 623 ho_denied_no_proper_crc_c Call control 9 9

270 624 ch_type_mismatch_c Invalid message contents 51 81

271 625 aiv_transc_or_rate_unava_c Requested transcoding/rate adaption unavailable

30 48

272 626 aiv_speech_version_unava_c Invalid message contents 51 81

273 627 aiv_pagin_refus_big_load_c Call control 9 9

274 628 aiv_conn_refresh_timeout_c Equipment failure 20 32

275 629 aiv_conn_refresh_failed_c Equipment failure 20 32

276 630 no_support_a_if_type_c Requested A-Interface Type not supported

45 2D

277 631 no_supp_redundancy_level_c Requested Redundancy Level not supported

46 2E

278 632 no_supp_codec_type_conf_c Requested Codec Type or Codec Configuration not supported

44 2C

279 633 unavail_a_if_type_c Requested A-Interface Type unavailable

36 24


54 DN9814277




27A 634 t25_timer_expiry_c Call Control 9 9

2BC 700 rc0_hand_act_fail_c Equipment failure 20 32

2BD 701 a_crct_alr_res_c Terrestrial circuit already allocated 50 80

2BE 702 a_crct_conn_err_c Equipment failure 20 32

2BF 703 rc0_crct_conn_timeout_c Equipment failure 20 32

2C0 704 access_out_of_crct_tbl_c Equipment failure 20 32

2C1 705 a_crct_rel_err_c Equipment failure 20 32

2C2 706 rc0_transc_or_rate unava_c Requested transcoding/rate adaption unavailable

30 48

2C3 707 rc0_cip_type_mismatch_c Switch circuit pool 32 50

2C4 708 rc0_inv_msg_contents_c Invalid message contents 51 81

2C5 709 rc0_req_speech_ver_unava_c Requested speech version unavailable

33 51

2C6 710 rc0_hunting_queue_full_c Traffic load 28 40

2C7 711 rc0_a_crct_congestion_c Equipment failure 20 32

2C8 712 rc0_a_search_error_c Traffic load 28 40

2C9 713 rc0_crct_pool_mismatch_c Equipment failure 20 32

2CA 714 rc0_rej_due_eme_call_c Traffic load 28 40

2CB 715 rc0_ilc_file_error_c Equipment failure 20 32

2CC 716 a_crct_conn_err_consec_c Equipment failure 20 32

2CD 717 call_id_alr_allocated_c Call Identifier already allocated 57 39

2CE 718 unavail_terr_resource _c Requested terrestrial resource unavailable

22 16

320 800 a_tsl_user_mismatch_c Equipment failure 20 32

321 801 sc7_crct_res_timeout_c Equipment failure 20 32

322 802 sc7_crct_conn_timeout_c Equipment failure 20 32

323 803 sc7_crct_disconn_timeout_c Equipment failure 20 32

324 804 sc7_crct_rel_timeout_c Equipment failure 20 32

325 805 a_tsl_blocked_c Requested terrestrial resource unavailable

22 34

326 806 a_tsl_status_unknown_c Requested terrestrial resource unavailable

22 34

327 807 lsi_access_fail_c Equipment failure 20 32

328 808 scc_access_fail_c Equipment failure 20 32

329 809 undef_tsl_in_lsi_c Requested terrestrial resource unavailable

22 34

32A 810 crct_equipment_fail_c Equipment failure 20 32

32B 811 reset_crct_c Response to MSC invocation 8 8

32D 813 sc7_ssp_c Call control 9 9

32F 815 a_pcm_fault_c Equipment failure 20 32


DN9814277 55



331 817 a_crct_removed_c O and M intervention 7 7

333 819 a_et_state_change_c O and M intervention 7 7

384 900 m_radio_if_mess_fail_c Radio interface message failure 0 0

385 901 m_radio_if_fail_c Radio interface failure 1 1

386 902 m_uplink_quality_c Uplink quality 2 2

387 903 m_uplink_strength_c Uplink strength 3 3

388 904 m_downlink_quality_c Downlink quality 4 4

389 905 m_downlink_strength_c Downlink strength 5 5

38A 906 m_distance_c Distance 6 6

38B 907 m_o_and_m_inter_c O and M intervention 7 7

38C 908 m_resp_to_msc_invoc_c Response to MSC invocation 8 8

38D 909 m_call_control_c Call control 9 9

38E 910 m_r_if_f_rev_to_old_c Radio interface failure, reversion to old channel

A 10

38F 911 m_handover_succ_c Handover successful B 11

390 912 m_better_cell_c Better cell C 12

391 913 m_directed_retry_c Directed retry D 13

392 914 m_equipment_fail_c Equipment failure 20 32

393 915 m_no_radio_res_avail_c No radio resource available 21 33

394 916 m_req_terr_res_unava_c Requested terrestrial resource unavailable

22 34

395 917 m_cch_overload_c CCCH overload 23 35

396 918 m_processor_overload_c Processor overload 24 36

397 919 m_bss_not_equipped_c BSS not equipped 25 37

398 920 m_ms_not_eqipped_c MS not equipped 26 38

399 921 m_tr_cod_rat_ad_unav_c Requested transcoding/rate adaption unavailable

30 48

39A 922 m_ciph_alg_not_supp_c Ciphering algorithm not supported 40 64

39B 923 m_terr_chan_alr_allc_c Terrestrial circuit already allocated 50 80

39C 924 m_prot_err_b_bsc_msc_c Protocol error between BSS and MSC

60 96

39E 926 m_invalid_cell_c Invalid cell 27 39

39F 927 m_invalid_msg_cont_c Invalid message contents 51 81

3A0 928 m_ie_or_field_missing_c Information element or field missing

52 82

3A1 929 m_incorrect_value_c Incorrect value 53 83

3A2 930 m_unknown_msg_type_c Unknown message type 54 84

3A3 931 m_unknown_ie_c Unknown information element 55 85

3A5 933 m_cip_type_mismatch_c Circuit pool mismatch 31 49


56 DN9814277




5.2 BSSMAP causes mapped to DX causesThe following table shows which DX causes trigger a particular BSSMAP cause. The BSSMAP causes and their hexadecimal values are listed in the first two columns. The third column lists the cause fields of the DX causes which bring about a BSSMAP cause on the A interface.

3A6 934 m_switch_circuit_pool_c Switch circuit pool 32 50

3A7 935 m_speech_version_unavail_c Requested speech version unavailable

33 51

3A8 936 m_pre_empt_c Preemption 29 41

3A9 937 m_traffic_c Traffic F 15

3AA 938 m_traffic_load_c Traffic load 28 40

3AD 941 m_no_supp_codec_typ_conf_c Requested Codec Type or Codec Configuration not supported

44 2C

3AE 942 m_no_support_a_if_type_c Requested A-Interface Type not supported

45 2D

3AF 943 m_unavail_a_if_type_c Requested A-Interface Type unavailable

36 54

3B0 944 m_unavail_codec_typ_conf_c Requested Codec Type or Codec Configuration unavailable

35 23

3B1 945 m_no_supp_redundancy_lvl_c Requested Redundancy Level not supported

46 2E


BSSMAP cause HEX DX cause DEC

Radio interface message failure 0x00 data_ind_corrup_c 319

estab_ind_fail_c 321

estab_conf_fail_c 322

ho_detect_fail_c 324

mode_mod_ack_fail_c 326

phy_cont_conf_fail_c 329

rel_ind_fail_c 335

rej_phanton_res_c 340

paging_msg_fail_c 344

ch_required_fail_c 345

ass_fail_c 350

ch_act_nack_gen_err_c 356

ignored_double_rand_acc_c 358

estab_ind_corrupted_c 370

clear_cmd_not_received_c 506

ms_is_lost_c 507

m_radio_if_mess_fail_c 900

DN9814277 57



Radio interface failure 0x01 ch_act_nack_c 308

conn_fail_c 315

conn_fail_rad_inf_fail_c 316

conn_fail_rad_link_fail_c 317

err_ind_c 320

no_meas_result_c 327

rf_ch_rel_ack_fail_c 333

rel_ind_c 334

signalling_error_c 336

sapi_3_fail_c 343

ch_mode_mod_fail_c 349

coprocess_fail_c 352

error_report_c 354

conf_change_ms_fail_c 365

m_radio_if_fail_c 901

Uplink quality 0x02 ext_out_ul_quality_c 80

ext_out_ul_rxqual_c 103

ext_out_ul_interf_c 105

inter_ul_rxqual_c 123

inter_ul_interf_c 125

intra_ul_interf_c 141

m_uplink_quality_c 902

Uplink strength 0x03 ext_in_ul_strength_c 81

ext_out_ul_rxlev_c 101

ext_out_rap_fld_drop_c 114

inter_ul_rxlev_c 121

inter_rap_fld_drop_c 134

m_uplink_strength_c 903


58 DN9814277




Downlink quality 0x04 ext_in_dl_quality_c 82

ext_out_dl_rxqual_c 102

ext_out_dl_interf_c 104

inter_dl_rxqual_c 122

inter_dl_interf_c 124

inter_ok_ci_ratio_c 136

inter_bad_ci_ratio_c 137

intra_dl_interf_c 140

intra_dl_rxqual_c 143

intra_ok_ci_ratio_c 144

intra_bad_ci_ratio_c 145

m_downlink_quality_c 904

Downlink strength 0x05 ext_in_dl_strength_c 83

ext_out_dl_rxlev_c 100

inter_dl_rxlev_c 120

intra_direct_access_c 150

inter_direct_access_c 158

intra_inter_band_due_lev_c 169

m_downlink_strength_c 905

Distance 0x06 ext_in_distance_c 84

ext_out_distance_c 106

ext_out_low_distance_c 115

inter_distance_c 126

inter_low_distance_c 135

intra_distance_c 147

intra_low_distance_c 148

timing_advance_c 400

m_distance_c 906


DN9814277 59



O and M intervention 0x07 ext_in_o_and_m_inter_c 85

ext_out_forced_ho_c 109

inter_forced_ho_c 129

intra_forced_ho_c 142

intra_lrtch_ho_to_norm_c 174

intra_lrtch_ho_to_ext_c 175

user_act_block_c 300

netw_acct_block_c 301

ch_act_nack_om_inter_c 309

abi_switchover_c 342

forced_ho_block_c 368

has_switchover_c 509

a_crct_removed_c 817

a_et_state_change_c 819

m_o_and_m_inter_c 907

Response to MSC invocation 0x08 ext_in_resp_to_msc_invoc_c 86

ext_out_tr_ho_c 111

ext_out_pre_empt_ho_c 113

inter_tr_ho_c 131

inter_pre_empt_ho_c 133

intra_pre_empt_ho_c 146

reset_crct_c 811

m_resp_to_msc_invoc_c 908


60 DN9814277




Call control 0x09 ext_out_dtm_ho_to_dtm_c 198

inter_dtm_ho_to_dtm_c 242

bsc_bsc_conflict_c 373

ho_not_allowed_c 500

target_fail_c 510

source_fail_c 511

has_call_control_c 512

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

ho_denied_no_proper_crc_c 623

aiv_pagin_refus_big_load_c 627

t25_timer_expiry_c 634

sc7_ssp_c 813

m_call_control_c 909

Radio interface failure, reversion to old channel

0x0A ass_fail_msg_c 306

ho_fail_c 323

m_r_if_f_rev_to_old_c 910

Handover successful 0x0B m_handover_succ_c 911


DN9814277 61



Better cell 0x0C ext_in_better_cell_c 87

ext_out_pbgt_ho_c 107

ext_out_umbrella_ho_c 108

ext_out_slow_moving_ms_c 117

ext_out_det_slow_mov_ms_c 118

ext_out_det_fast_mov_ms_c 119

inter_pbgt_ho_c 127

inter_umbrella_ho_c 128

inter_slow_moving_ms_c 138

inter_det_slow_mov_ms_c 139

intra_ho_to_amr_hr_c 152

intra_ho_to_amr_fr_c 153

inter_erfd_ho_c 157

ext_out_erfd_ho_c 163

intra_ho_from_hr_to_dhr_c 179

intra_ho_from_fr_to_dhr_c 180

intra_dhr_rxqual_dmux_ho_c 181

intra_rxlev_diff_dmux_ho_c 182

intra_dhr_rxlev_dmux_ho_c 183

intra_ho_from_fr_to_dfr_c 184

intra_dfr_rxqual_dmux_ho_c 185

intra_dfr_rxl_df_dmux_ho_c 186

intra_dfr_rxlev_dmux_ho_c 187

intra_mcpa_pbho_tch_c 188

m_better_cell_c 912

Directed retry 0x0D ext_in_directed_retry_c 88

ext_out_dr_ho_c 110

ext_out_idr_ho_c 112

inter_dr_ho_c 130

inter_idr_ho_c 132

intra_dr_ho_c 149

ext_out_inter_system_da_c 191

m_directed_retry_c 913


62 DN9814277




Traffic 0x0F ext_in_bsc_trho_c 92

ext_in_int_ho_to_ext_c 94

ext_in_dtm_traffic_c 96

intra_gprs_ho_c 151

intra_inter_band_tch_c 154

intra_inter_band_sdc_c 155

inter_bsc_trho_c 159

inter_dadlb_c 160

ext_out_bsc_trho_c 164

intra_inter_bts_type_tch_c 166

intra_inter_bts_type_sdc_c 167

intra_ho_due_to_hscsd_c 168

intra_dtm_mo_cs_to_ps_c 170

intra_dtm_mt_cs_to_ps_c 171

intra_dtm_mt_ps_to_ps_c 172

intra_dtm_ps_to_cs_c 173

ext_out_isho_c 190

ext_out_ibho_to_utran_c 193

ext_out_int_ho_to_ext_c 194

ext_out_dtm_disabled_c 196

ext_out_pcu_qual_cntrl_c 197

ext_out_dtm_ho_to_wcdma_c 199

inter_dtm_disabled_c 240

inter_pcu_qual_cntrl_c 241

m_traffic_c 937


DN9814277 63



Equipment failure 0x20 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_nack_equip_fail_c 310

ch_act_fail_c 314

conn_fail_rem_trans_fail_c 318

no_resp_from_copro_c 328

rcs_alg_start_ack_fail_c 330

rcs_alg_cl_ack_fail_c 331

rc0_disco_ind_c 332

state_confligt_c 337

type_confligt_c 338

mode_mod_nack_equip_fail_c 346

ho_interrupted_c 360

downgrade_c 361

ho_no_started_c 362

conf_change_not_allowed_c 363

hscsd_copro_fail_c 366

sub_timer_c 367

upgrade_fail_c 369

cn_id_not_found_c 374

dfca_hop_prm_not_valid_c 376

etp_failure_c 377

no_resp_from_coprocess_c 503

no_resp_to_radio_res_req_c 504

has_state_confligt_c 505

no_resp_to_ho_cpl_msg_c 508

aiv_hand_act_fail_c 600

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

aiv_conn_refresh_timeout_c 628

aiv_conn_refresh_failed_c 629


64 DN9814277




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_a_crct_congestion_c 711

rc0_crct_pool_mismatch_c 713

rc0_ilc_file_error_c 715

a_crct_conn_err_consec_c 716

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

lsi_access_fail_c 807

scc_access_fail_c 808

crct_equipment_fail_c 810

a_pcm_fault_c 815

m_equipment_fail_c 914

No radio resource available 0x21 ch_act_nack_rad_ch_alr_a_c 312

rrm_serv_req_nack_c 348

dr_fail_c 351

rtsl_reconf_fail_c 359

no_radio_res_avail_c 501

m_no_radio_res_avail_c 915

Requested terrestrial resource unavailable 0x22 unknown_a_pcm_c 622

unavail_terr_resource _c 718

a_tsl_blocked_c 805

a_tsl_status_unknown_c 806

undef_tsl_in_lsi_c 809

m_req_terr_res_unava_c 916

CCCH overload 0x23 overload_c 341

m_cch_overload_c 917

Processor overload 0x24 m_processor_overload_c 918

BSS not equipped 0x25 mode_mod_nack_c 325

conf_change_bts_fail_c 364

m_bss_not_equipped_c 919

MS not equipped 0x26 rrm_ms_not_supporting_c 404

m_ms_not_equipped_c 920


DN9814277 65



Invalid cell 0x27 rrm_invalid_cell_c 405

m_invalid_cell_c 926

Traffic load 0x28 ext_in_dtm_no_res_avail_c 95

inter_dtm_no_res_avail_c 162

ext_out_ibho_to_gsm_c 192

ext_out_dtm_no_res_avail_c 195

rc0_hunting_queue_full_c 710

rc0_a_search_error_c 712

rc0_rej_due_eme_call_c 714

m_traffic_load_c 938

Preemption 0x29 ext_in_pre_empt_c 91

forced_rel_c 339

m_pre_empt_c 936

Requested transcoding/rate adaption unavailable

0x30 ch_act_nack_serv_not_ava_c 313

mode_mod_nack_trc_rat_un_c 347

ch_act_nack_ch_mode_err_c 355

rrm_bts_not_supporting_c 403

aiv_transc_or_rate_unava_c 625

rc0_transc_or_rate_unava_c 706

m_tr_cod_rat_ad_unav_c 921

Circuit pool mismatch 0x31 m_cip_type_mismatch_c 933

Switch circuit pool 0x32 ext_in_switch_crc_pool_c 90

ext_out_switch_crc_pool_c 116

rrm_switch_src_pool_c 401

rc0_cip_type_mismatch_c 707

m_switch_crc_pool_c 934

Requested speech version unavailable 0x33 rrm_speech_ver_unavail_c 402

rc0_req_speech_ver_unava_c 709

m_speech_version_unavail_c 935

Ciphering algorithm not supported 0x40 ch_act_nack_encryp_alg_c 311

err_rep_enc_alg_not_imp_c 353

ciph_not_support_trx_c 375

m_ciph_alg_not_supp_c 922

Terrestrial circuit already allocated 0x50 a_crct_alr_res_c 701

m_terr_chan_alr_allc_c 923


66 DN9814277




Invalid message contents 0x51 ch_type_mismatch_c 624

aiv_speech_version_unava_c 626

rc0_inv_msg_contents_c 708

m_invalid_msg_cont_c 927

Information element or field missing 0x52 m_ie_or_field_missing_c 928

Incorrect value 0x53 m_incorrect_value_c 929

Unknown message type 0x54 m_unkown_msg_type_c 930

Unknown information element 0x55 m_unknown_ie_c 931

Protocol error between BSS and MSC 0x60 invalid_bssmap_msg_c 621

m_prot_err_b_bsc_msc_c 924

Requested A-Interface Type unavailable 0x36 unavail_a_if_type_c 633

m_unavail_a_if_type_c 943

Requested A-Interface Type not supported 0x45 no_support_a_if_type_c 630

m_no_support_a_if_type_c 942

Requested Codec Type or Codec Configu-ration unavailable

0x35 unavail_codec_type_conf_c 409

m_unavail_codec_typ_conf_c 944

Requested Codec Type or Codec Configu-ration not supported

0x44 no_supp_codec_type_conf_c 632

m_no_supp_codec_typ_conf_c 941

Requested Redundancy Level not sup-ported

0x46 no_supp_redundancy_level_c 631

m_no_supp_redundancy_lvl_c 945

Response to an Internal Handover Enquiry Message

0x16 inter_mss_trg_bss_int_ho_c 243

Call Identifier already allocated 0x57 call_id_alr_allocated_c 717


DN9814277 67

Call Related DX Causes in BSC DX causes in BSC statistics

Id:0900d805807f93e0Confidential

6 DX causes in BSC statisticsThe information in DX causes can be examined using the measurements and observa-tions of BSC Statistics. The following methods can be used:

• using clear code counters on BSC basis, divided into different phases (50 BSC Level Clear Code Measurement)

• using BSC counters on BSC basis (51 BSC Level Clear Code (PM) Measurement) • using BSC counters on cell basis (57 BSC Level Clear Code (SERLEV) Measure-

ment) • using observations • using counters of Traffic Measurement (1 Traffic Measurement)

These measurements are described in the following sections. For more information on how to run measurements and observations, see BSC Statistics Administration.

6.1 DX causes and BSC Level Clear Code MeasurementThe counters of BSC Level Clear Code Measurement record failures that have occured during a call (signalling or conversation). The measurement collects the clear code counters for each of the 15 call phases (see Call phases of call related DX causes in BSC). The values of all counters are given on a BSC basis.

Each counter has a corresponding failure DX cause, whose cause number is the same as the last three digits of the counter number. For example, the clear code counter 500315 CONN FAIL corresponds to the failure DX cause conn_fail_c (315). DX causes are listed in List of call related DX causes in BSC.

Failure causes 902, 903, 904, 905, 906, 907, 908, 911, 912, 913, 934, 936, 937, and 938 do not update counters in BSC Level Clear Code Measurement.

For more information, see 50 BSC Level Clear Code Measurement under Refer-ence/Counters/performance indicators/Call control measurements (CS) in the PDF view.

6.2 DX causes and BSC Level Clear Code (PM) MeasurementThe counters of BSC Level Clear Code (PM) Measurement are divided into five different classes; there are failure counters, success counters, one BCSU counter, call attempt and call establishment cause counters, and handover counters. Counters are given on BSC basis.

Most of the counters have a one-to-one correspondence with a particular DX cause. These correspondences are indicated in the counter descriptions. However, some of the counters are primarily based on 3GPP-based BSSMAP causes or establishment causes.

For more information, see 51 BSC Level Clear Code (PM) Measurement under Refer-ence/Counters/performance indicators/Call control measurements (CS) in the PDF view.

68 DN9814277



DX causes in BSC statistics

6.3 DX causes and BSC Level Clear Code (SERLEV) Measure-mentBSC Level Clear Code (SERLEV) Measurement registers statistics about clear codes in a BSC during calls on cell basis.

Some of the counters correspond to several DX causes. These correspondences are not indicated in the counter descriptions, since no one-to-one correspondences exist.

For more information, see 57 BSC Level Clear Code (SERLEV) Measurement under Reference/Counters/performance indicators/Call control measurements (CS) in the PDF view.

6.4 DX causes and observation reportThe observation report includes counters for recording the starting and ending cause and phase. The observation counters are the following:

Phase in Contains the call phase for a channel seizure.

Cause in Contains the DX cause that indicates the reason for a channel seizure. This can only be a success cause.

Phase out Contains the call phase when a channel release is started.

Cause out Contains the DX cause that indicates the reason for a channel release. This can be a success or a failure cause.

The counters in different observations offer detailed information on call establishment and call clearing during handovers and basic calls:

• In 16 SDCCH Observation and 17 TCH Observation, the Phase in and the Cause in counters include the establishment cause. The Phase out and the Cause out counters are for the channel release cause.

• In 18 Handover Observation, the Phase in and the Cause in counters are for the handover starting cause. The Phase out and the Cause out counters are for the handover ending cause.

• In 22 Clear Code Observation, the DX cause structure includes the Phase out and the Cause out counters.

• In 23 Dropped Call Observation and 29 Drop Call Breakdown Observation, the Phase in and the Cause in counters include the establishment cause for the dropped call. The Phase out and the Cause out counters are for the channel release cause.

When the starting cause (Cause in) is the same as the ending cause (Cause out), the event has ended successfully. Similarly, when these two variables have different cause values, the signalling in question was not successful.

6.5 DX causes and Traffic MeasurementThe following table lists the counters of Traffic Measurement that are incremented due to DX causes. The first two columns list the counter name and number. The last two columns list the DX cause codes and their decimal numbers.

DN9814277 69



Counter name Counter number

DX cause DEC

TRANSACTIONS FAIL DUE TO BSS FAIL 001002 This is a sum of the counters 001033, 001034, 001035, 001036

TRANSACTIONS FAIL DUE TO RADIO FAIL

(incremented only in phases 1-8)

001003 ass_fail_msg_c 306

conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

target_fail_c 510

source_fail_c 511

TRANSACTIONS FAIL DUE RADIO ON SOURCE CHANNEL DURING HO

(incremented only in phases 9–11)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323


ass_fail_c 350

error_report_c 354



ms_is_lost_c 507

target_fail_c 510

70 DN9814277




TRANSACTIONS FAIL DUE RADIO ON TARGET CHANNEL DURING HO (incre-mented only in phases 12-14)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

source_fail_c 511

TRANSACTIONS ENDED DUE TO BSS PROBLEM

001012 This is a sum of the counters 001045, 001046, 001047, 001051

TRANSACTIONS ENDED DUE RADIO FAIL (incremented only in phases 1-8, 15)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

target_fail_c 510

source_fail_c 511


DX cause DEC

DN9814277 71



TRANSACTIONS ENDED DUE SOURCE CHANNEL FAIL DURING HO (incremented only in phases 9-11)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323


ass_fail_c 350

error_report_c 354



ms_is_lost_c 507

target_fail_c 510

TRANSACTIONS ENDED DUE TARGET CHANNEL FAIL DURING HO (incremented only in phases 12-14)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

source_fail_c 511

SDCCH ACT FAIL 001027 This is a sum of the counters 001072, 001074

TCH ACT FAIL 001028 This is a sum of the counters 001081, 001083

TCH TR FAIL (incremented only in phases 1-8, 15)

001029 conn_fail_rem_trans_fail_c 318

TCH TR FAIL SOURCE (incremented only in phases 9-11)


TCH TR FAIL TARGET (incremented only in phases 12-14)



DX cause DEC

72 DN9814277




SDCCH ABIS PROBL 001033 This is a sum of the counters 001075, 001076, 001077

SDCCH A IF PROBL 001034 This is a sum of the counters 001078, 001079, 001080

SDCCH LAPD FAIL 001035 lapd_fail_block_c 303

SDCCH BTS FAIL 001036 bts_fail_block_c 302

SDCCH USER ACT 001037 user_act_block_c 300

SDCCH NETW ACT 001039 netw_act_block_c 301

TCH ABIS PROBL 001045 This is a sum of the counters 001084, 001085, 001086

TCH LAPD FAIL 001046 lapd_fail_block_c 303

TCH BTS FAIL 001047 bts_fail_block_c 302

TCH USER ACT 001048 user_act_block_c 300

TCH NETW ACT 001050 netw_act_block_c 301

TCH A IF PROBL 001051 This is a sum of the counters 001087, 001088, 001089

SDCCH ACT FAIL CALL (incremented only in phases 1-8)

001072 ch_act_nack_c 308



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





ch_act_nack_gen_ie_err_c 356

speech_version_unavail_c 357




rrm_speech_ver_unavail_c 402


DX cause DEC

DN9814277 73



SDCCH ACT FAIL TARGET (incremented only in phases 12-14)







mode_mod_nack_c 325












DX cause DEC

74 DN9814277




SDCCH ABIS FAIL CALL (incremented only in phases 1-8)

001075 abis_fail_block_c 304


block_slave_c 307

ch_act_fail_c 314

data_ind_corrup_c 319










rel_ind_fail_c 335


sapi_3_fail_c 343

sub_timer_c 367



etp_failure_c 377

has_state_conflict_c 505


DX cause DEC

DN9814277 75



SDCCH ABIS FAIL SOURCE (incremented only in phases 9-11)



block_slave_c 307

ch_act_fail_c 314











rel_ind_fail_c 335


sapi_3_fail_c 343




DX cause DEC

76 DN9814277




SDCCH ABIS FAIL TARGET (incremented only in phases 12-14)



block_slave_c 307

ch_act_fail_c 314











rel_ind_fail_c 335


sapi_3_fail_c 343

sub_timer_c 367


etp_failure_c 377



DX cause DEC

DN9814277 77



SDCCH A IF FAIL CALL (incremented only in phases 1-8)

001078 rc0_disco_ind_c 332

rrm_switch_crc_pool_c 401

unavail_codec_type_conf_c 409




aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606






T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619


invalid_bssmap_msg_c 621

unknown_a_pcm_c 622


ch_type_mismatch_c 624





no_support_a_if_type_c 630

no_supp_redundancy_level_c 631

no_supp_codec_type_conf_c 632

unavail_a_if_type_c 633


rc0_hand_act_fail_c 700


DX cause DEC

78 DN9814277



















call_id_alr_allocated_c 717






a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815










DX cause DEC

DN9814277 79






m_unexpected_c 925



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



DX cause DEC

80 DN9814277




SDCCH A IF FAIL SOURCE (incremented only in phases 9-11)







aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606






T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622








a_crct_alr_res_c 701






DX cause DEC

DN9814277 81



















a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815











m_processor_overload_c 918




DX cause DEC

82 DN9814277








m_unexpected_c 925



m_ie_or_field_missing 928

m_incorrect_value 929

m_unknown_msg_type 930

m_unknown_ie 931





DX cause DEC

DN9814277 83



SDCCH A IF FAIL TARGET (incremented only in phases 12-14)






aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606






T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622















DX cause DEC

84 DN9814277
















unavail_terr_resource_c 718






a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815













DX cause DEC

DN9814277 85







m_unexpected_c 925






m_unknown_ie_c 931









TCH ACT FAIL CALL (incremented only in phases 1-8)







mode_mod_nack_c 325











DX cause DEC

86 DN9814277




TCH ACT FAIL TARGET (incremented only in phases 12-14)







mode_mod_nack_c 325











DX cause DEC

DN9814277 87



TCH ABIS FAIL CALL (incremented only in phases 1-8, 15)



block_slave_c 307

ch_act_fail_c 314











rel_ind_fail_c 335


sapi_3_fail_c 343

sub_timer_c 367



etp_failure_c 377



DX cause DEC

88 DN9814277




TCH ABIS FAIL SOURCE (incremented only in phases 9-11)



block_slave_c 307

ch_act_fail_c 314











rel_ind_fail_c 335


sapi_3_fail_c 343




DX cause DEC

DN9814277 89



TCH ABIS FAIL NEW (incremented only in phases 12-14)



block_slave_c 307

ch_act_fail_c 314











rel_ind_fail_c 335


sapi_3_fail_c 343

sub_timer_c 367


etp_failure_c 377



DX cause DEC

90 DN9814277




TCH A IF FAIL CALL (incremented only in phases 1-8, 15)







aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606






T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622














DX cause DEC

DN9814277 91






















a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815











DX cause DEC

92 DN9814277











m_unexpected_c 925






m_unknown_ie_c 931





DX cause DEC

DN9814277 93



TCH A IF FAIL SOURCE (incremented only in phases 9-11)







aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606






T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622












DX cause DEC

94 DN9814277






















a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815











DX cause DEC

DN9814277 95











m_unexpected_c 925






m_unknown_ie_c 931





DX cause DEC

96 DN9814277




TCH A IF FAIL NEW (incremented only in phases 12-14)






aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606






T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622















DX cause DEC

DN9814277 97



















unavail_terr_resource_c 718






a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815









DX cause DEC

98 DN9814277













m_unexpected_c 925






m_unknown_ie_c 931










DX cause DEC

DN9814277 99



TCH REL DUE TO RADIO FAIL (incre-mented only in phases 2, 3, 5, 8–14)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

target_fail_c 510

source_fail_c 511


DX cause DEC

100 DN9814277




TCH REL DUE TO BSS FAIL (incremented only in phases 2, 3, 5, 8–14)

001140 bts_fail_block_c 302




block_slave_c 307

ch_act_fail_c 314










rc0_disco_ind_c 332


rel_ind_fail_c 335


sapi_3_fail_c 343

sub_timer_c 367







aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606







DX cause DEC

DN9814277 101



T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622





























DX cause DEC

102 DN9814277





a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815












m_ms_not_eqipped_c 920





m_unexpected_c 925






m_unknown_ie_c 931





DX cause DEC

DN9814277 103



TCH REL DUE RAD FAIL PH 2-3 (incre-mented only in phases 2-3)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

target_fail_c 510

source_fail_c 511

TCH REL DUE RAD FAIL PH 12-14 (incre-mented only in phases 12-14)


conn_fail_c 315



err_ind_c 320

ho_fail_c 323



ass_fail_c 350

error_report_c 354




ms_is_lost_c 507

target_fail_c 510

source_fail_c 511


DX cause DEC

104 DN9814277




TCH REL DUE BSS FAIL PH 12-14 (incre-mented only in phases 12-14)

001207 bts_fail_block_c 302




block_slave_c 307

ch_act_fail_c 314










rc0_disco_ind_c 332


rel_ind_fail_c 335


sapi_3_fail_c 343

sub_timer_c 367







aiv_ssp_c 601



sccp_release_c 604

global_reset_c 606







DX cause DEC

DN9814277 105



T7_expiry_c 613

T10_expiry_c 614





aiv_timeout_c 619



unknown_a_pcm_c 622





























DX cause DEC

106 DN9814277





a_tsl_blocked_c 805






reset_crct_c 811

sc7_ssp_c 813

a_pcm_fault_c 815












m_ms_not_eqipped_c 920





m_unexpected_c 925






m_unknown_ie_c 931





DX cause DEC

DN9814277 107



TCH REL BSC BSC CONFLICT CALL (incremented only in phases 1-8 or 15)

001211 bsc_bsc_conflict_c 373

TCH REL BSC BSC CONFLICT TARG (incremented only in phases 12-14)

001212 bsc_bsc_conflict_c 373


DX cause DEC

Call Related DX Causes in BSC.pdf

Documents