Troubleshoot Call Failures in Huawei Mobile Networks

Security Level: Public
Call Failure Troubleshooting
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.
HUAWEI Confidential
Upon completion this course, you will be able to:

Deeply understand MOC, MTC call flow
Deeply understand Assignment
Deeply understand Paging
HUAWEI Confidential
Chapter 1 Assignment
Chapter 2 MOC Troubleshooting
Chapter 3 Paging
Chapter 4 MTC Troubleshooting
HUAWEI Confidential
MOC Call flow

BSC/RNC
MSC
CM Service Request
Authentication procedure
Intra MSC call

MS to MS:(SRI Procedure with HLR)
Cipher procedure
Inter MSC call

Setup
MS to MS: (SRI Procedure with HLR and

ISUP, BICC with other MSC)
MS to PSTN: (ISUP, BICC with PSTN)
Call proceeding
Assignment procedure
Alerting
Connect
HUAWEI Confidential
MOC Assignment failure

Symptom
After sending the Assignment Request message, the MSC receives the
Assignment Response message with the failure cause value.
Possible Causes
When this fault occurs, you need to start performance measurement and
interface message trace to analyze and locate the fault cause.
The cause of the fault may be one of the following:
Radio channel resources are insufficient on the BSC side.
The status of circuits on the BSC side is inconsistent with that on the
MSC side.
The A-interface circuits are insufficient.
The speech versions on the MSC side are inconsistent with those on
the BSC side.
HUAWEI Confidential
During early or late assignment, the local MSC receives an ASSIGNMENT

FAILURE message from the originating BSC/RNC
HUAWEI Confidential

The general troubleshooting procedure is as follows:
1.
Check Whether the Success Rate of Assignment Is Too Low
2. Check Whether Traffic Is Too Heavy

3. Check Whether the Number of Cause Values Is Too Large
4. Check Whether Radio Channels Are Insufficient
5. Check Whether the Status of Circuits on the RAN Side Is Inconsistent With
That on the MSC Side
6. Check Whether A/Iu-Interface Circuits Are Insufficient
7. Check Whether the Speech Versions on the MSC Side Are Inconsistent With
Those on the RAN Side
HUAWEI Confidential
MOC Assignment timeout

Symptom
After the MSC Server sends the Assignment Request message, the assignment duration
exceeds 30 seconds. Run LST TIMER to check whether Timer Name is
TN_RAB_WAIT_FOR_ASSIGNMENT_ACK.
Possible Causes
When this fault occurs, you need to enable performance measurement and message trace
to locate the fault cause. The fault is primarily caused by the A-interface link failure.
HUAWEI Confidential
MOC Assignment timeout

1. Check Whether the A-Interface Link Is Abnormal
2. Check Whether the Assignment Request Is Present
3. Check the Status of the SCCP DSP
4. Check the Status of the MTP/M3UA Route
5. Check the Status of the MTP/M3UA Link
6. Check the Status of the MGW
7. Check Whether the transmission Are Normal
HUAWEI Confidential
Early assignment On the caller side

During the call setup process, after sending to the caller a Call PROCEEDING, the
MSC assigns a traffic channel to the caller before the callee is alerted.
BSC-A
MSC
BSSAP-A
BSSAP-A
CM_SERVICE_REQ
MAP-B/C
VLR
BSC-B
HLR
MAP-B/D
BSSAP-A
MAP-C/D
Process Access
Request
Process Access
Request Ack
CM_SERVICE_ACC
SETUP
Send Info For
Outgoing Call (OCS)
Call Proceeding
Complete Call
Send Routing Information REQ
Provide Roaming Number REQ
Provide Roaming Number ACK
Send Routing Information ACK
Send Info For
Incoming Call (ICS)
Assignment REQ
Assignment COMP
HUAWEI Confidential
Early assignment On the callee side

The MSC assigns a traffic channel after receiving a CALL CONFIRMED from the
callee.
BSC-A
BSSAP-A
MSC
BSSAP-A
MAP-B/C
VLR
BSC-B
HLR
MAP-B/D
BSSAP-A
MAP-C/D
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Assignment REQ
Assignment COMP
HUAWEI Confidential
Late assignment On the caller side

In the call setup process, after sending to the caller a Call PROCEEDING, the MSC
assigns a traffic channel to the caller after the callee is alerted.
BSC-A
MSC
BSSAP-A
BSSAP-A
MAP-B/C
VLR
BSC-B
HLR
MAP-B/D
BSSAP-A
MAP-C/D
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Alerting
Alerting
Assignment REQ
Assignment COMP
HUAWEI Confidential
Late assignment On the callee side

The MSC informs the callee of late assignment through the SETUP message. The
callee responds with an ALERTING immediately after the CALL CONFIRMED. The
MSC assigns a traffic channel for the callee. Late assignment usually occurs after the
MSC receives the CONNECT message from the callee.
BSC-A
BSSAP-A
MSC
BSSAP-A
MAP-B/C
VLR
BSC-B
HLR
MAP-B/D
BSSAP-A
MAP-C/D
Page MS
Page Response
Process Access
Request
Process Access
Request Ack
SETUP
Call Confirm
Alerting
Alerting
Connect
Assignment REQ
Assignment COMP
HUAWEI Confidential
Disconnection suspending before assignment
BSC
MSC
CM Service Request
Change bit 4 of P173 to 0:
Setup
The MSC server sends a DISCONNECT

message instructing a mobile terminal to
disconnect a call only after the MSC server
receives an assignment response from the
access network.
Assignment Request
Disconnect
Assignment Response
Release
Optimization for 2G assignment

succ rate
HUAWEI Confidential
Disconnection suspending before assignment
RNC
MSC
CM Service Request
Setup
Assignment Request
Disconnect
Release
Optimization for 3G assignment

succ rate
No assignment response, it means one
time with assignment failure.
Note:
Bit 11 of P1006 and bit 8 of P1005
determines whether to enable the
suspension of call disconnection after
sending the assignment request and
before receiving the assignment response.
Change Bit 11 of P1006 =0 and bit 8 of
P1005 =0
HUAWEI Confidential
3G Assignment Succ Rate in VMS1- RSRHMI1
RNC-Date
RSRHMI1-06/05
RSRHMI1-07/05
RSRHMI1-08/05
RSRHMI1-09/05
RSRHMI1-10/05
RSRHMI1-11/05
RSRHMI1-12/05
RSRHMI1-13/05
RSRHMI1-14/05
RSRHMI1-15/05
RSRHMI1-16/05
RSRHMI1-17/05
RSRHMI1-18/05
Assignmen
Assignmen
t Failure
Assignmen t Failure
Assignmen due to
Traffic
t Failure
due to
t Failure
Release of NonSuccessful Channel
due to
Maximum due to
MSC/RNC specified Traffic
Assignmen
Invalid
Bit Rate
Other
During
Failure
Channel
t
RABID(tim Unavailabili Reasons(ti Assignmen Cause(time Assignmen Requests(ti Assignmen
es)
ty(times) mes)
t(times)
s)
ts(times) mes)
t Succ rate
0
0
22
2445
601
350784
353831 99.13885
2
0
26
2552
577
365506
368638 99.15039
1
0
22
2472
526
354136
357137 99.15971
1
0
27
2568
621
352511
355701 99.10318
1
0
19
2295
396
332604
335296 99.19713
1
0
32
1835
252
278992
281082 99.25644
1
0
23
1540
139
217617
219297 99.23392
2
0
29
2328
365
352255
354951 99.24046
1
0
18
2493
320
351783
354599 99.20586
0
0
23
2553
468
359365
362388 99.16581
0
0
28
2434
518
352497
355448 99.16978
0
0
27
2529
613
356714
359858 99.12632
0
2
24
1991
272
280739
283005 99.19931
HUAWEI Confidential
Chapter 3 Paging
HUAWEI Confidential
MOC Failed to obtain Routing Information
Symptom
Obtaining routing information from the HLR fails.
Possible Causes
When this fault occurs, you need to start user message trace. The cause of the
fault may be one of the following:
1.The calling office does not send the Send Routing Information message to the
HLR.
2.The called office does not send the Providing Roaming Number message to the
HLR.
3.Other device is faulty (take the case that the MSC and the HLR are connected
by the STP as an example).
HUAWEI Confidential
HUAWEI Confidential

1. View the Trace Output to Check Whether the
MAP_SEND_ROUTING_INFORMATION_REQ Message Is Present
2. Check SCCPGT Configuration
3. Check the GT of the Called MSISDN
4. Check Whether the DSPs of the HLR to Which the Callee Belongs Are
Accessible
5. Check Whether the SCCP Subsystem of the HLR to Which the Callee
Belongs Runs Normally
6. Check Whether the Called Office Sends the PROVIDE_ROAMING_NUMBER
Message to the HLR
HUAWEI Confidential
MOC Call failure at the caller side

1. View the Trace Output to Check Whether the
MAP_SEND_ROUTING_INFORMATION_REQ Message Is Present
2. Check SCCPGT Configuration
3. Check the GT of the Called MSISDN
4. Check Whether the DSPs of the HLR to Which the Callee Belongs Are
Accessible
5. Check Whether the SCCP Subsystem of the HLR to Which the Callee
Belongs Runs Normally
6. Check Whether the Called Office Sends the PROVIDE_ROAMING_NUMBER
Message to the HLR
HUAWEI Confidential
Symptom
The subscriber fails to originate a call.
Possible Causes
The call connection procedure fails.
Supplementary services are not subscribed.
Bearer capabilities are not supported.
The number analysis procedure fails.
The outgoing routing procedure fails.
HUAWEI Confidential

1. Check whether the MSC receives the CM Service Request message, Setup.
2. Check whether the Bearer Service Not Implemented cause value is carried in
the Release Complete message.
3. Check the Setup message to see if information transfer capability of the
GSM Bearer Capability information element is 6 (Line2).
4. Check whether the requested facility not subscribed cause value is carried
in the Disconnect message. (CLIR Invocation information element is carried in
the Setup message)
5. Check Whether the Number Analysis Procedure Fails
6. Check ROUTING_INFORMATION procedure
7. Check Authentication procedure
8. Check Assignment procedure
9. Check Outgoing Call Failure
HUAWEI Confidential

Case 1: CLIR service
The calling SETUP message carries the clir invocation IE, Huawei MSC queries the
VLR for whether the subscriber has subscribed to the CLIR service. If the
subscriber does not subscribe to the CLIR service, the system forbids the call
connection through a software parameter. Therefore, the subscriber cannot serve
as a caller.
Bit 3 of P51 determines whether to release a call when a subscriber who does not
subscribe to the CLIR service requires the CLIR service.
[Values and Descriptions]:
= 1: to release a call
= 0: not to release a call
The default value is 1.
Register the CLIR service on the HLR for the subscriber.
HUAWEI Confidential
Case 2: Call from line 2 fail

Bit 11 of P172 determines whether the MSC supports Line 2.
= 0: not to support Line 2. If a user calls through Line 2, the MSC receives the call
through Line 1.
= 1: to support Line 2. If a user calls through Line 2, the MSC receives the call through
Line 2 as long as the user signs with Line 2. Otherwise, the MSC will terminate Line
2.
HUAWEI Confidential
MOC - Outgoing call failure

Symptom
Inter-MSC calls fail.
Possible Causes
1.The calling-partys-category information element carried in the IAM message
does not comply with the requirements.
2.The peer office does not support the continuity check.
3.The attribute or format of called-party-number or calling-party-number
information element carried in the IAM message does not comply with the
requirements.
4.The user-service-information information element carried in the IAM message
does not comply with the requirements.
5.A parameter incompatibility problem exists in the IAM message.
HUAWEI Confidential

1. Analyze Cause Values in the REL Message
2. Check Whether the IAM Message Is Normal
Check whether the value of calling-partys-category complies with the
carrier's requirements.
Check whether continuity-check-indicator is continuity-check-required
(1) in the IAM message.
Check whether nature-of-address-indicator of the called-party-number or
calling-party-number information element in the IAM message complies with
the carrier's requirements.
Check whether the format of address-signal of the called-party-number or
calling-party-number information element in the IAM message complies with
the carrier's requirements
Check whether the user-service-information information element carried in
the IAM message complies with the carrier's requirements
Check whether the location-number information element is carried in the IAM
message.
HUAWEI Confidential

Check whether continuity-check-indicator is continuity-check-required (1) in the
IAM message.
Check whether the peer office supports the continuity check because the continuity
check is initiated for this call.
Run MOD N7TG to modify the value of Continuity Check to No for the peer office.
MOD N7TG: CC = YES;
Make a test call again, and then check whether the fault is rectified.
HUAWEI Confidential

Check whether the format of address-signal of the called-party-number or callingparty-number information element in the IAM message complies with the carrier's
requirements.
Change suffixed by "F" at the calling number or called number according to a carrier's
requirement.
Run MOD OFC to modify the suffix rule for the corresponding office direction
according to the carrier's requirements
HUAWEI Confidential
Chapter 3 Paging
HUAWEI Confidential
MTC Call flow

BSC/RNC
MSC
Paging procedure
Authen&Cipher procedure
Setup
Call confirmed
Assignment procedure
Alerting
Connect
HUAWEI Confidential
MTC Paging Failure

Symptom
The MSOFTX3000 fails to page subscribers.
Possible Causes
1.The communication between the MSC and the BSC is abnormal.
2.The BSC is abnormally stopped or does not respond.
3.The MSC is configured wrongly.
4.The MSC cannot obtain the cell data of the subscriber from the VLR.
5.The location area/cell (service area) configuration on the core network side is
different from that on the access network side.
HUAWEI Confidential
MTC Paging Failure

1. Trace User Interface Messages, check the trace output to see if the Paging
message is present.
2. Check Whether the Location Area Data of the Subscriber Is Present in the VLR
3. Check Whether the Location Area/Cell Data on the MSC Side Is Consistent With
That on the BSC Side
4. Check the Message Dispatch Capabilities of the Modules on the MSOFTX3000
(LST SPA, Service Dispatch Ability is BSSAP or RANNAP)
5. Check Whether the BSC Sends the Disconnect or Release Message
6. Check Whether the MSC Sends the Disconnect or Release Message Before
Receiving the Page Response Message
7. Check the Status of signaling Connected to the BSC/RNC
8. Query the paging duration LST PGCTRL
9. Check the duration of implicit IMSI detach LST VLRCFG
HUAWEI Confidential
MTC Paging Failure
IMSI implicit detach timer in VLR

After the implicit IMSI detach timer times out, the VLR automatically sets the
subscriber to the detached state
The MSC will not paging the UE implicit detached by MSC, it will reduce the no
response times. But the problem is at the same time to improve the paging success
rate, the UE state The user is switch off will be increase.
So suggest set the MSC implicit detach timer 1.1 times to 1.2 times as BSC T3212. If
the BSC T3212 is less than 30 min, so the MSC implicit detach timer set 2 times and
5 min; if the BSC T3212 is more than 30 min, we set MSC implicit detach timer 1
times and 5-10 min as BSC T3212.
Explicit IMSI detach: An MS initiates the IMSI detach flow when the subscriber powers
off the MS, and the VLR sets the subscriber to the detached state.
HUAWEI Confidential
MTC Paging Failure

Call is released before ringing
P166 BIT15 controls whether to measure the PAGING RESP message when a call is
released before ringing. If open, the MSC will measure the PAGING RESP when the
call is released before ringing, include the MTC PAGING RESP, PAGING RESP
during Location update, first paging RESP as first paging resp.
HUAWEI Confidential
MTC Paging Failure

Impact with location update
P1100BIT1 Controls whether to make the location area update and paging at the
same time, for improving the paging success rate. If the location update fail or during
the location update process the UE send a follow on message, paging fail. Set
P1100BIT1 as 0, the MSC server will send the paging message after the UE finish
the location update
HUAWEI Confidential
Chapter 3 Paging
HUAWEI Confidential
MTC Call Failure at the called side

Symptom
A call connection or processing failure occurs at the callee side.
Possible Causes
1.A paging fails.
2.The Setup message contains information elements not supported by the MS.
3.An assignment fails.
4.The bearer capability is insufficient.
HUAWEI Confidential

1.Check whether the paging procedure is successful.
2.Check whether the MS sends the Call Confirmed message.
3.Check whether the assignment procedure is successful on the callee side.
4.Check whether the callee is alerted.
5.Check whether the callee answers the call.
HUAWEI Confidential

Check whether the MS sends the Call Confirmed message.
Check whether the HLC information element is carried in the Setup message,
Set bit 7 of P168 to 0.
Bit 7 determines whether to include the High Layer Compatibility (HLC) cell in
the SETUP message when the HLC cell exists.
= 0: not to include the High Layer Compatibility (HLC) cell in the SETUP
message
= 1: to include the High Layer Compatibility (HLC) cell in the SETUP message
HUAWEI Confidential

The MSC sends the Disconnect message after the MS sends
the Call Confirmed message
Check whether the Disconnect message contains any of the following cause
values:
no bearer capability available this time (58):
bearer capability not permit (57): In normal cases, the bearer service is not
provided during call waiting. The handling procedure is complete.
HUAWEI Confidential
Thank You
www.huawei.com

Troubleshoot Call Failures in Huawei Mobile Networks

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Troubleshoot Call Failures in Huawei Mobile Networks

Enviado por

Direitos autorais:

Formatos disponíveis

Security Level: Public

Call Failure Troubleshooting

HUAWEI TECHNOLOGIES CO., LTD.

Upon completion this course, you will be able to:

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

MOC Call flow

Intra MSC call

Inter MSC call

MS to MS: (SRI Procedure with HLR and

HUAWEI TECHNOLOGIES CO., LTD.

MOC Assignment failure

HUAWEI TECHNOLOGIES CO., LTD.

MOC Assignment failure

During early or late assignment, the local MSC receives an ASSIGNMENT

HUAWEI TECHNOLOGIES CO., LTD.

MOC Assignment failure

Check Whether the Success Rate of Assignment Is Too Low

2. Check Whether Traffic Is Too Heavy

HUAWEI TECHNOLOGIES CO., LTD.

MOC Assignment timeout

HUAWEI TECHNOLOGIES CO., LTD.

MOC Assignment timeout

HUAWEI TECHNOLOGIES CO., LTD.

Early assignment On the caller side

HUAWEI TECHNOLOGIES CO., LTD.

Early assignment On the callee side

HUAWEI TECHNOLOGIES CO., LTD.

Late assignment On the caller side

HUAWEI TECHNOLOGIES CO., LTD.

Late assignment On the callee side

HUAWEI TECHNOLOGIES CO., LTD.

Disconnection suspending before assignment

Change bit 4 of P173 to 0:

The MSC server sends a DISCONNECT

HUAWEI TECHNOLOGIES CO., LTD.

Optimization for 2G assignment

Disconnection suspending before assignment

HUAWEI TECHNOLOGIES CO., LTD.

Optimization for 3G assignment

3G Assignment Succ Rate in VMS1- RSRHMI1

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

MOC Failed to obtain Routing Information

HUAWEI TECHNOLOGIES CO., LTD.

MOC Failed to obtain Routing Information

HUAWEI TECHNOLOGIES CO., LTD.

MOC Failed to obtain Routing Information

HUAWEI TECHNOLOGIES CO., LTD.

MOC Call failure at the caller side

HUAWEI TECHNOLOGIES CO., LTD.

MOC Call failure at the caller side

HUAWEI TECHNOLOGIES CO., LTD.

MOC Call failure at the caller side

HUAWEI TECHNOLOGIES CO., LTD.

MOC Call failure at the caller side

HUAWEI TECHNOLOGIES CO., LTD.

MOC Call failure at the caller side

Case 2: Call from line 2 fail

HUAWEI TECHNOLOGIES CO., LTD.

MOC - Outgoing call failure

HUAWEI TECHNOLOGIES CO., LTD.

MOC - Outgoing call failure