Actions
Bug #2729
closedCTRL "msc_connection_status" reports "disconnected" even ater MSC is connected
Start date:
12/09/2017
Due date:
% Done:
0%
Spec Reference:
Description
A CTRL Get on msc_connection_status returns disconnected even after the MSC connection is up:
./osmo_ctrl.py -d 127.0.0.1 -p 4249 -g msc_connection_status Got message: GET_REPLY 8952135329486579618 msc_connection_status disconnected
Sidenote: As osmo-bsc supports multiple MSCs, it might make sense to introduce instance dispatching, similar like the bts.N.foobar variables.
Updated by dexter over 6 years ago
- Assignee changed from dexter to stsp
I heard this is now solved, if yes, just set the ticket to resolved.
Updated by stsp about 6 years ago
- Status changed from New to Resolved
Fixed with https://gerrit.osmocom.org/#/c/5627/
Actions
