WARNING: QA Issue: ortp rdepends on libcrypto, but it isn't a build dependency? [build-deps]
WARNING: QA Issue: ortp rdepends on libssl, but it isn't a build dependency? [build-deps]
We used asterisk to be able to speak SIP with the outside. LCR
has gained this capability in the past and we haven't used asterisk
in more than two years.
Asterisk doesn't seem to compile with master/dizzy and there is
little point in figuring out why.
The line doesn't have the signalling type set yet. It will be set
_after_ the rsl connection is considered up. This is addressing
RSL Connection failures like:
<0001> oml.c:1026 Rx IPA RSL CONNECT IP=1.2.3.4 PORT=3003 STREAM=0x00
<000f> input/ipaccess.c:921 cannot create RSL BTS link: trx_nr (0) does not refer to a signalling link
<0001> oml.c:1030 Error in abis_open(RSL): -22
<0001> oml.c:341 Sending FOM NACK with cause Message cannot be performed.
Fix the build by using a newer version and change the PR to be
a proper version number. I havent' checked if upgrading is possible
but is not a big concern right now.
The control interface has been moved to libosmocore and a new
library has been created for it. The ipaccess code has moved
from libosmo-abis to libosmocore and new defines for the VTY
and CTRL ports are now available inside libosmocore
osmo-sgsn was installing a sysvinit script but it wasn't inside
the INITSCRIPT_PACKAGES so it would not be started by default.
Use the already existing INITSCRIPT_PARAMS/INITSCRIPT_NAME variables
for the osmo-sgsn.
Fixes: SYS#366
Update to current master of lcr, which includes support for AMR
and RTP-bridge. Master openbsc doesn't support RTP-bridge yet,
but it will work with a transcoding LCR getting all TCH frames
in all codecs (HR/FR/EFR/AMR) via MNCC.
Currently OpenBSC and LCR are not compatible with each other.
So far we have only included patches that add new defines and
do not change the wire format of messages. Just revert it so
we can have LCR talk to OpenBSC
While working on the OpenBSC/NITB schema migration I experienced
crashes and traced it down to libdbi-drivers. It was possible that
a special string quote each character and then adding '"\0' would
result in out of bounds write.
This might require to rebuild the freshly built openggsn to
fix the libgtp0 depedency. I had this issue on Dora without
a PRServer. I am not sure it applies to edison or other configs.
Bump the PR of OpenBSC to force a rebuild of the SGSN.
Fixes: SYS#176
libosmo-sccp does not install any dynamically shared libraries
so let us install/depend on the staticdev package installing the
.a files and the -dev package.