Actions
Bug #5993
closedError in mgw pool config leads to loading defaults, instead of exit
Start date:
04/04/2023
Due date:
% Done:
100%
Spec Reference:
Description
If OsmoMSC (or OsmoBSC) has a MGW pool config that is invalid (e.g. because it contains an invalid listen IP), I would expect it to exit.
Instead it uses the old-style MGW configuration in the VTY node 'msc' (even if nothing is configured there, using the defaults).
Only if the MGW configuration in the VTY node 'msc' is also invalid, it exits.
This should be easy to fix, preparing patches.
Updated by osmith about 1 year ago
- Status changed from New to In Progress
- % Done changed from 0 to 90
Updated by osmith about 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Actions
