Project

General

Profile

Bug #3049

fix & revisit silent call feature after the split from osmo-nitb

Added by neels 7 months ago. Updated 7 months ago.

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

0%

Estimated time:
Resolution:

Description

Using osmo-msc's VTY commands 'subscriber [...] silent-call start [...]' I can initiate a paging and activation of an SDCCH, but 'silent-call stop' seems to have no effect. Fix that.
Also look at the channel type selection from the VTY command, which is no longer possible with a separate osmo-bsc; resolve that by limiting the VTY command (or enabling the feature otherwise?).
Furthermore, look at two '#if BEFORE_MSCSPLIT' in silent_call.c, whether these can be re-enabled using the A-interface information, or #2391.

History

#1 Updated by neels 7 months ago

silent call release doesn't work because the ref counting of the conn is not balanced.
See attached pcap of REF logging from the MSC, where the fsm refcount is never removed.
(The silent call is stopped at packet 16)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)