SIP message 401 unauthorized, call drop event

Transport Networks
, ,
1

Hi Experts.
Please help analyse SIP message 401 unauthorized, call drop event occurred here.

image

2

Check what happened on RRC why you deregister.
401 Unauthorised is normal behavior after Register.

3

Before RRC reconfig no EPS bearer identity assign in ESM response.

image
image1017Ă—513 297 KB

4

You had RRCConnectionRelease message on top.
Check whay that happened before.
After that RRCConnectionReconfiguration message whith reconfigured DRBs came after your selected message.

5

There is not rrcconnectionRelease before ESM response.
Which message you refer to?

6

Second row.

7

Please check whether Dynamic QoS Modification (E//) or eRAB Modification (N//) is activated/not.

8

401 unauthorised is a normal msg during call flow for authorization…check 503 service seems ue is not able to perform requested service. Also ue was deregistered as mentioned by Spale.

9

I can’t see any other abnormal event but IMS voice server de registered abnormally. Also HHO intrafreq occur to a logical cell b4 rrc connection rel.

image
image1218Ă—537 281 KB

10

What is recommendation for Huawei?

Also: I have all drops on this one location with multiple attempt failures.

image

image

11

With RRcconnRelease (probably due to radio or problem with HO) all 3 bearers are released.
UE goes to idle and do again RRC establishment.
After that need RRCConnReconfiguration to do reactivation of all 3 bearers.
Check radio conditions before Rrc release message.
And maybe you will need to check S1AP interface from eNB side. Those consecutive drops looks suspicious.

12

Any inputs on

  1. Affected QCI
  2. KPI Counter which is affected
13

Interference?

14

Looks like call failed at 503 Unavailable.

15

SIP IMS Call flow:

image
image335Ă—537 65.9 KB

16

Seems SIP/IMS signalling is successful.
The issue is voice bearer couldn’t be allocated as RRC reconfiguration message is missing (to update default radio bearer to voice bearer) in L3 as per shared snap.
In general multiple reasons can be… unsupported encryption algorithm/voice codec causing de-registration, some underlying enb level parameter is missing if it’s not NW level issue, Bad Coverage (levels, quality), choked capacity, TNL failures, S1 Interface failure, etc.

1 Like
17

RF environment doesn’t look bad for consecutive drops.

image
image885Ă—496 218 KB

18

I didn’t get this message after 401 unauthorized.

19

RSRP is ok but check RSRQ.

20

Chek again your first photo.
After 401 you will see UL Register and 200 ok on DL → successfully registration.