Feature #3049
closedfix & revisit silent call feature after the split from osmo-nitb
80%
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.
Files
Updated by neels about 6 years 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)
Updated by fixeria about 5 years 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.
Updated by tnt about 5 years 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.
