Actions
Bug #4884
openRLL_REL_IND is recieved after RF_CHAN_REL
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.
Files
Updated by lynxis almost 3 years 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.
Updated by manatails almost 3 years ago
- File callfail2.pcap callfail2.pcap added
attached is a pcap file of bsc-msc traffic. Often the call ends with radio interface failure, UE displays "network is busy" message.
Actions
