osmo-ci utils
Previous script didn't clean workspace and git repositories were
allegedly not being updated, hiding build failures against newer deps.
Currently cellmgr-ng is not being maintained and fails to build against
recent libosmo-sccp. For that dep repo, tag "old_sua" is used since
after that tag, APIs changed considerably and it is known that
cellmgr-ng cannot build starting from there.
It's up to whoever wants to maintain it to make changes in cellmgr-ng to
support newer libosmo-sccp.
While building with new jenkins.sh script and "old_sua" tag, still there
are some build issues (mostly related to build system), like some
Makefile.am files missing some LDFLAGS. Some of them are fixed in
follow-up patches. Some other are left as an exercise for whover wants
to revive this repo.
Change-Id: Ic597664198547ec367d7926d4e401b9734c8cfa9
Currently the connect is blocking leading to one bad connection
(e.g. to a black hole) blocking all other connections leading to
bursty traffic.
Change-Id: Idfca8acbce09176055da3e577566386e07d7a348
There seems to be issues with the write handling of the osmo-stp
and so far we did not enable vty tests here. Make it possible to
enable the tests, fix the VTY strings, change string to OsmoSTP.
Change-Id: I547fd4840d86ce16e8589fb63802dd7099781194
Provide a modern systemd service file for the osmo-stp. The sysvinit
file is quite basic and doesn't signal syntax errors nicely. Let us
embrace the future.
Change-Id: Ic0cc0f17d442aa0ad38de9f0cf8aeb14121938de
mgcp/mgcp_protocol.c: In function ‘mgcp_handle_message’:
/home/ich/install/openbsc/include/osmocom/core/logging.h:59:4: warning: ‘save’ may be used uninitialized in this function [-Wmaybe-uninitialized]
logp2(ss, level, __BASE_FILE__, __LINE__, 0, fmt, ##args); \
^
mgcp/mgcp_protocol.c:368:15: note: ‘save’ was declared here
char *elem, *save;
Change-Id: I28152373b043c8a5b55a83ac09dd7bafce4d2d66
The return type changed from enum to int and it is time to catch
up with it.
vty_interface.c:108:2: warning: initialization from incompatible pointer type
.go_parent_cb = ss7_go_parent,
^
vty_interface.c:108:2: warning: (near initialization for ‘vty_info.go_parent_cb’)
mgcp_ss7_vty.c:36:2: warning: initialization from incompatible pointer type
.go_parent_cb = mgcp_go_parent,
^
mgcp_ss7_vty.c:36:2: warning: (near initialization for ‘vty_info.go_parent_cb’)
Change-Id: I8061df697daf79fa57b8313c15f6567ff152f4a5
For M3UA we already skip the link-test handling and there is no
point in waiting for management messages to collect routing info.
We already know where to send things. At first I tried to overload
the skip handling but it is better to just set the timer to 0 and
then move on.
For M3UA we should have one time-out for operation we want and
then re-transmit it. As this is too much work right now create
a single timer that waits that after a connect the ASPAC_ACK
state will be reached.
In case of back pressure we can not send messages quick enough
and will drop messages. Add a counter so we can count how often
this happened per link/linkset. The SCTP M2UA code is not changed
as we don't have a link in the hands and adding it is too risky
without tests (not all M2UA have a link index so some might not
have a link).
For the "bridging" to IPA mode we can force the SCTP/M3UA connection
down. This way the remote STP will do a proper link fail-over
procedure instead of the STP throwing data away.
This is not configurable yet.
Oliver Smith
Pau Espin
Neels Hofmeyr