Project

General

Profile

Feature #3049

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

Added by neels about 1 year ago. Updated 6 days ago.

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

80%

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 about 1 year 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)

#2 Updated by fixeria about 2 months ago

  • Tracker changed from Bug to Feature
  • Status changed from New to Feedback
  • Assignee set to tnt
  • % Done changed from 0 to 80

As far as I can see, this feature was fixed in the current master.

#3 Updated by tnt about 2 months ago

I stopped all work until the inter-msc stuff is completed because it's apparently causing conflicts. Will resume when it's done and merged.

#4 Updated by tnt 6 days ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)