Bug #3616
closed
default (dynamic) ss7 config gets written to config file on write
Added by roh over 5 years ago.
Updated over 5 years ago.
Description
i verified this bug on osmo-msc nightly build today
to reproduce:
remove all occurences of cs7 from the config file.
restart osmo-msc
connect to vty
type 'write'
check config file.
it will contain at least this snippet in addition now:
cs7 instance 0
point-code 0.23.1
asp asp-clnt-OsmoMSC-A-Iu 2905 0 m3ua
remote-ip 127.0.0.1
as as-clnt-OsmoMSC-A-Iu m3ua
asp asp-clnt-OsmoMSC-A-Iu
routing-key 3 0.23.1
msc
cs7-instance-a 0
cs7-instance-iu 0
- Project changed from OsmoMSC to libosmo-sccp + libosmo-sigtran
- Assignee set to stsp
this is most likely a libosmo-sigtran bug. The configuration should only write those parts which are explicitly configured, and not routes as/asp's which are dynamically created as automatism of the "simple client".
Note that osmo-msc has to pass a default point code to the ss7 API (this is enforced by the API).
I suppose this means that this part will always have to be written out:
cs7 instance 0
point-code 0.23.1
and thus also the following lines, because they reference this cs7 instance:
msc
cs7-instance-a 0
cs7-instance-iu 0
- Status changed from New to In Progress
For consistency, I have checked the simple-server implementation for this problem as well.
It looks like dynamic AS/ASP created in server mode are already omitted from the configuration file when the config is written out.
Does anyone see anything else that needs to be done for this issue?
- Status changed from In Progress to Resolved
crickets
Sounds like nothing else seems to be needed. Closing this issue.
Also available in: Atom
PDF
