Project

General

Profile

Bug #4884

RLL_REL_IND is recieved after RF_CHAN_REL

Added by manatails about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/02/2020
Due date:
% Done:

0%

Spec Reference:

Description

For some reason current version of osmo-bsc keeps getting RLL_REL_IND message after rf channel release when servicing nanoBTS, causing calls to fail a few seconds after connection.

callfail-osmo-bsc.txt callfail-osmo-bsc.txt 23.9 KB manatails, 12/02/2020 01:54 AM
callfail_.pcap callfail_.pcap 130 KB manatails, 12/02/2020 01:54 AM
callfail2.pcap callfail2.pcap 38.7 KB manatails, 12/02/2020 11:49 AM

History

#1 Updated by lynxis about 2 months ago

I'ven't looked into the problem if the REL IND is wrong at this time.

But the call release looks good. First the Call is terminated by a CC (Call Control) and afterwards the RR Channel is released.
The call seems to get through (Call Connect) and is terminated by the BSC (frame 1272) (Call Disconnect). Maybe the MSC hang up? The pcap doesn't contain the BSC<>MSC traffic.

#2 Updated by manatails about 2 months ago

attached is a pcap file of bsc-msc traffic. Often the call ends with radio interface failure, UE displays "network is busy" message.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)