| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Be able to configure a list of destinations (duplicates allowed)
that will be tried in a round robin fashion. The change is in
the bsc_msc_connection to operate on a list. We achieve the
round robin nature with the same trick used in the paging code
to delete and append the current entry. The nat code was updated
to compile but one can only configure one destination.
|
|
Right now the code assumes that any request coming
from the NAT is a query and the code responds to with
a list of configured LACs.
|
|
|
|
For restarting the NAT we can now block it, it will not accept
new connections and for existing connections it will attempt
to drop them over time. A blocked NAT will end up with no BSC
connections left and then can be safely restarted.
|
|
We want to send MGCP through the Osmo Extension and also
want to send the list of local LACs to it.
|
|
|
|
Keep track of the used transaction identifier and always forward
messages to the USSD provider. E.g. this can be used to have a
dialogue going. Right now it is still possible that the MSC will
close down the connection.
|
|
|
|
Remove the usage of 0, 1, 2 and start using enum values. We can
still assume con_local is a number.
|
|
These are not needed any more. We used them for u_int
types but we now use uint which comes from stdint.h
|
|
This was done with sed on the files.
|
|
ipaccess_idtag_name() now takes a uint8_t as parameter which is the
length of the type tag.
This patch was suggested by Zecke.
|
|
We need to include this directly to help LCR in building.
|
|
* include/openbsc/ipaccess.h: Reserve a protocol number for control
commands
* input/ipaccess.c: New function ipaccess_prepend_header_ext prepends
the extension header
|
|
Now this is used by ipaccess-proxy, remove redundant implementation in it.
|
|
Now this is used by ipaccess-proxy, remove redundant implemention in it.
|
|
This patch finishes the new ipaccess_send_*() functions and use them
in the ipaccess-proxy code.
I have also cleanup the definition of the PONG, ID_ACK and ID_REQ
messages (including some minor documentation about them).
I had to rename ipaccess_recvmsg() in ipaccess-proxy to avoid clashing
with the one defined in libabis.
|
|
Make it possible to specify the rf-socket path via the
vty configuration as well. The command line setting will
override it though.
|
|
For the USSD module we only want to handle requests that are
legitimate. This is achieved by looking for the CM Service Accept
or the BSSAP CIPHER MODE COMMAND.
|
|
This patch extends the make_sock() prototype so you can fully set
the fields priv_nr and data of the bsc_fd structure.
This is the first step to get rid of the internal make_sock()
implementation that ipaccess-proxy uses.
This patch includes a minor cleanup to pass INADDR_ANY instead
of zero, if you do not want to bind the socket to one specific
address.
|
|
If the regexp fails to compile the internal dfa is NULL and a
regexec will crash nicely. Fail and free the string if the regexp
fails to compile.
|
|
This allows to match multiple numbers and multiple patterns
|
|
libosmogsm is a new library that is distributed in the libosmocore.
Now, openbsc depends on it. This patch gets openbsc with this
change.
This patch also rewrites all include path to the new
osmocom/[gsm|core]
Signed-off-by: Pablo Neira Ayuso <pablo@gnumonks.org>
|
|
This change is required to finish the integration of the VTY and
the per-application logging categories that provides:
"vty: integration with logging framework"
in libosmocore.
It has been tested with osmo-nitb. The other just compiled tested.
|
|
|
|
TS objects are not part yet
|
|
... this allows the BTS driver to decide if it should handle the event at all
|
|
|
|
|
|
|
|
They can be triggered from the VTY
|
|
The HSL Femtocell seems to be a poor man implementation of the
ip.access Abis/IP protocol, but cutting corners wherever possible.
We try to workaround those corners wherever possible...
|
|
|
|
|
|
|
|
A trunk will always have 32 endpoints to be used and we allow
a sparse allocation of endpoints.
|
|
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 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.
|
|
Delay executing RF commands up to a second. If many commands
arrive within a second then just execute the last command.
|
|
Verify that the BTS is following our orders, if we think there was
an error we will drop the OML connection.
|
|
|
|
|
|
This introducecs the new VTY command "neighbor-list mode manual-si5"
in combination with "si5 neighbor-list (add|del) arfcn <0-1024>",
which allows you to (optionally) have neighbor channel lists that
differ in SI5 and in SI2.
|
|
This uses the new bts_model->config_write_bts() callbacks
|
|
This way a BTS module can append config data to the TS, TRX and BTS
sections.
|
|
Depending on the MO we adress, select the proper OML link
|
