When introducing the rewriting for 6.3.0 we broke the 6.1.0 support.
Now the result should build on Debian with both 6.1.0 and 6.3.0
Change-Id: I263a6abd2d9eb15ce5778ef8dbfcdac2a228b77d
This will ensure that a 'make compile' on a freshly-cloned repo
will first clone all the deps to ensure a successful build
Change-Id: I6583a42758b5682b04d1e90585063904508aa3a9
It's unsure if the tests do anything useful. At least they build again
The fundamental problem is some clashes/overlap between our own
definitions for certain protocols and those that Ericsson released
later. Ideally we should use Ericsson whenever possible and resort on
our own ones only as a fall-back for those that don't exist, but
significant development has been done before Ericsson released their
codecs, so it's TBD for the future.
We used to rely on out-of-tree git clones to be prepared by the user.
This commit changes the system to make sure we clone all git repos
we depend upon into the 'deps' folder, and then setup the symlinks
to that folder. As a result, we should be able to support
self-contained builds using the makefiles in this repo.
So far, only the IPA client was instructing the IPL4asp to use
the message-desegmentation function. The server didn't use it, leading
to inconsistent behaviour.
We use the "oml-connection-status == degraded" to determine if
the OML connection has been brought up by the external helper.
However, this status is advertised from the moment the ID_ACK was
issued on the OML connection, and *not* only from the moment on
when we're expecting the RSL connection (after initializing all MO).
Let's introduce some delay to avoid running into a race condition here.
The proper solution is to implement OML inside the test suite, which
is too large of a task to be done right now, where the focus is on
RSL+BSSAP testing.
Rather than using the more complex RSL Emulation and BSSAP emulation
components, we attach to the RSL and BSSAP Codec Ports and send some
messages back and forth for low-level testing such as timeouts, response
to RACH requests, failure of MSC to react to CR requests, etc.