Age | Commit message (Collapse) | Author | Files | Lines |
|
This now enforces a unique structure: All of our main daemon
programs start with an "osmo-" prefix.
|
|
The new structure divides the code into a number of libraries
for the BSC core functionality, MSC core functionality, Abis transport,
TRAU and other bits.
This doesn't introduce any functional code change but simply moves
around files and alters Makefile.am accordingly.
Next step would be to disentangle a lot of the inter-library
dependencies and make the individual bits of code more independent.
|
|
We want to support real trunks in the MGCP code and we need to
have some better book keeping for those. Move the code around.
|
|
This will influence the allocator from where to search for the
next free endpoint. This can be used to force it to allocate a
specific endpoint next.
|
|
|
|
|
|
This code allocates endpoints from multiple multiplexes but
will always leave 0x0 and 0x1f unassigned in the multiplex.
|
|
Introduce a VTY setting that right now needs to be set to
one. To make updating this setting possible we will now store
the number of endpoints in the bsc connection as well.
|
|
Allocate the status for an endpoint dynamically. We will support
BSCs with different amount of multiplexes and need to have this
flexibility in the future. Add the proper null checks to the
current users of this code.
|
|
... as this is now used as SYSLOG ident
|
|
|
|
Switch the type to international and skip the '00' of the phone
number. This should fix some issues with gateway MSCs.
|
|
If the replaced number is too long for the phone number we will
have to stop processing here.
|
|
bsc_init.c was a big mess even only for two supported BTS models,
so before adding more BTS types, this needs a cleanup.
All the BTS specific code from bsc_init.c has now moved into
bts_{siemens_bs11,ipaccess_nanobts}.c
This has required that input_event() and nm_state_event() get both
converted to proper libosmocore signals instead of referencing external
symbols.
|
|
Instead of using more numbers from the proto range we will
use the 0xee and then have a mini header with our new proto
id in there. For a start rename the use types to _OLD.
|
|
The reason for this is quite simple: We want to make sure anyone
running a customized version of OpenBSC to operate a network will
have to release all custom modifiations to the source code.
|
|
This adds a test coverage build. One can use gcov and lcov on the
resulting data afterwards to see which code paths were executed and
which were not.
|
|
Make sure that the MSC endpoint exists on the NAT, otherwise
we end up trying to free this endpoint when the SCCP connection
is taken down and will corrupt our memory. This issue started
to pop up as we have reduced the number of endpoints to 60
to allow transcoding on them.
|
|
This should help the BS+ to release RF channels earlier.
|
|
We need to match everything BUT the wildcard and then
do the normal strcmp...
|
|
|
|
|
|
Send a RLSD down to the BSC in case the USSD Provider is gone. It
is not sending a Clear Command and ut depends if the BS+ will
like this kind of behavior. At least the data on the NAT will
be freed soon afterwards due the RLC message.
|
|
Add a _msc to the method as we will send a RLSD to the
MSC and will add a method to send it down to the BSC
as well.
|
|
|
|
|
|
In case any rule has a '*' we will always match this
rule.
|
|
|
|
Create a new function, hand the data to this function, take back
a possible modified msgb and invalidate parsed at this point.
|
|
Parse a msg file in case we do have a list.
|
|
|
|
Forward the SCCP state and the data to the USSD provider,
also mark the connection as local.
|
|
|
|
Remove a lot of code in favor of a new function that is freeing
the old string and copying the new one. I should have gotten the
context and the strings right.
|
|
We will have the USSD provider connecting to us and we
will use the IPA protocol, including the auth mechanism.
|
|
Have various checks, check if the IMSI should be handled,
if there is a USSD query set and then decode and compare
the value.
|
|
Allow the query string to be set. The ussd matching code
will check for this string and then forward it to the bypass.
|
|
We will use this method in the USSD module to check if the
IMSI should be handled for USSD queries.
|
|
|
|
|
|
If we have a CM Service Request we will look into the message
to see if it is a Supplementary Service Activation.
|
|
DTAP unpacking will be used by the USSD checking code
|
|
Extract the IMSI from the first message as well and safe it
in the connection structure. The problem is that we do not
have this structure at this point, so we will allocate the
imsi as child of the bsc_connection and then move/steal it.
|
|
Store the IMSI for the connections that we are tracking,
it will be freed when the normnal SCCP connection is freed.
|
|
Currently it is not is not easily possible to disable
everyone and then only allow certain SIMs. By changing
the order we can do:
access-list imsi-deny only-something ^[0-9]*$
access-list imsi-allow only-something ^123[0-9]*$
and still keep the usecase of only forbidding certain
SIMs on certain LACs. Adjust test case, test that the
other cases are still functional.
|
|
|
|
This will be used by the USSD module to forward the data
without creating another copy of the data.
|
|
|
|
|
|
|