Project

General

Profile

Bug #2730

BSC doesn't release RF conenction or SCCP connection after main signalling link is closed

Added by laforge about 1 month ago. Updated 14 days ago.

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

0%

Spec Reference:

Description

If a MS sends us an "RLL RELEASE IND" on SAPI0/DCCH, it closes the main signaling link.

I'm developing TC_chan_rel_rll_rel_ind in the ttcn-3 BSC_Tests.ttcn to produce this scenario.

OsmoBSC currently seems to ignore this, meaning that neither do we
  • attempt to re-establish it
  • properly close the Radio channel (RF CHAN REL, ...)
  • close the SCCP/A connection

I'm not entirely sure what's the specified action at that point. The best is probably to drop the RF channel and A connection in such situations, rather than trying to recover from something that clearly looks like an implementation bug of a phone.

History

#1 Updated by laforge about 1 month ago

T3111 could play into this, e.g. if the main signalling connection is closed, T3111 should be started until the RF CHAN REL is performed. At the same time, we should probably stop the SACCH when starting T3111.

See Timers

#2 Updated by laforge 14 days ago

  • Assignee set to dexter

Also available in: Atom PDF