Attention is currently required from: laforge.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-msc/+/28133
to look at the new patch set (#2).
Change subject: sms: Give smsc its own VTY
......................................................................
sms: Give smsc its own VTY
The pre-historic sms_queue code used to have very strange aspects,
such as having some parameters (max-failure, max-pending) which could
only be sent from the 'enable' node, but not from a config file.
Before adding more configuration parameters, let's clean this up by
introducing a proper VTY config node for the 'smsc'; move the existing
config commands there and add new ones for max-failure and max-pending.
As the sms_queue data structure is only allocated after the config file
parsing happens, we are introducing a new 'sms_queue_config' data
structure. This encapsulates the public readable/writable config
parameters.
Change-Id: Ie8e0ab1a9f979337ff06544b9ab3820954d9804a
---
M include/osmocom/msc/sms_queue.h
M include/osmocom/msc/vty.h
M src/libmsc/Makefile.am
M src/libmsc/msc_vty.c
M src/libmsc/sms_queue.c
A src/libmsc/smsc_vty.c
M src/osmo-msc/msc_main.c
M tests/test_nodes.vty
8 files changed, 178 insertions(+), 73 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-msc refs/changes/33/28133/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28133
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: Ie8e0ab1a9f979337ff06544b9ab3820954d9804a
Gerrit-Change-Number: 28133
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <lafo...@osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: laforge <lafo...@osmocom.org>
Gerrit-MessageType: newpatchset
