| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Additionally it wasn't possible to send concatenated sms from the vty.
To send multiple sms, it is necessary to use padding bits and add a user_data_header.
Therefore the gsm_7bit_encode function was splitted to gsm_7bit_encode and gsm_septets2octets.
gsm_septets2octets: this is the old gsm_7bit_encode function + additional padding parameter
Additionally the gsm_7bit_decode function was modified to take account for the user_data_header.
With the new gsm_get_octet_len function you can get the octet length for a given septet length.
I also added several sms tests.
|
|
|
|
|
|
|
|
| |
For some interactive commands (e.g. sending a SMS in OpenBSC) we
are using the "NAME." arg definition. For the usecase of sending SMS
it is not enough to only allow about 13 spaces. Increase the limit.
Original patch is coming from Dennis Wehrle.
|
|
|
|
| |
This had broken lcr compilation...
|
|
|
|
|
| |
This could be used to submit SMS to OpenBSC and to get informed
about new SMS coming from OpenBSC.
|
|
|
|
|
| |
They are not used anywhere in our libraries, so they should be defined
by the respective applications
|
|
|
|
|
|
|
|
| |
* All loging prefixes in libraries should be DL like DLINP
* All signals / subsystems should be called S_L_* SS_L_*
* All command nodes should be called L_*_NODE
This makes sure existinc code still compiles as expected
|
|
|
|
|
| |
this ensures struct msgb is the same size as before, which will ensure
binary compatibility
|
|
|
|
|
| |
This patch reserves E1INP_NODE and IPA_NODE for libosmo-abis
VTY interfaces.
|
|
|
|
|
|
|
|
|
|
| |
This patch adds a new attribute to msgb objects. This new
attribute will store a pointer to the routing information,
in the case of the A-bis link, this will be used to store
e1inp_sign_link instead of struct gsm_bts_trx.
This deprecates msg->trx, that can be removed once all
application are ported to use msg->dst.
|
|
|
|
|
|
| |
This adds the libosmo-abis logging subsystems to libosmocore,
it uses the new change that harald proposed based on negative
numbers for library logging subsystems.
|
|
|
|
|
|
|
|
|
| |
The first range (from 0 to INT_MAX/2) of signal subsystems can be
used by client applications while the second range (from INT_MAX)
is reserved for libraries.
This is useful to support signals defined in libraries that
may be used by different client applications.
|
|
|
|
|
|
|
| |
This was introduced by me in commit
79599ba0eb7a9aeaeb9dfbbf4881f0633724a471
Thanks to Alexander Huemer for detecting it
|
|
|
|
| |
Found by Smatch
|
| |
|
|
|
|
|
|
|
| |
If we encounter a tag with 0xFF, we overflow our existing tlv_parse
array definitions.
Warning: this breaks ABI
|
|
|
|
| |
Detected by Smatch
|
|
|
|
| |
detected by Smatch
|
|
|
|
| |
This has been detected by http://smatch.sourceforge.net/
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We do this by using a trick: library-internal log categories use
negative subsystem numbers, which are converted into positive
array indexes at the time of logging.
library-internal log categories need to be knwo at compile-time,
while application-specified categories now are of unlimited number,
as they are dynamically allocated.
|
| |
|
| |
|
|
|
|
| |
(from openbsc's rsl_number_of_paging_subchannels)
|
| |
|
| |
|
|
|
|
|
| |
Written-by: Andreas Eversberg <jolly@eversberg.eu>
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
|
|
|
|
|
| |
those two are used in the RSL SACCH FILLING messages and delivered
like SI5 / SI6.
|
| |
|
| |
|
|
|
|
|
| |
The idea here is to use the osmocom core primitive code ot abstract out
primitives for inter-layer comunication in GSM.
|
| |
|
|
|
|
|
|
|
|
| |
This extends the socket infrastructure in libosmocore to allow
to create non-blocking sockets.
Basically, it replaces the connect0_bind1 parameter by one
flags parameter.
|
|
|
|
| |
(otherwise 'struct value_string' would not be defined)
|
| |
|
|
|
|
|
| |
This file is using enums in that might or might not be
known to the compiler. Forward declare them.
|
| |
|
| |
|
| |
|
|
|
|
| |
warning: array ‘abis_nm_obj_class_names’ assumed to have one element
|
|
|
|
|
|
|
|
| |
and export the underlying raw value_string arrays instead:
abis_nm_obj_class_names / abis_nm_adm_state_names.
This permits the caller to use get_string_value() as well as
get_value_string().
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
osmo_sock_init_ofd() is a wrapper around osmo_sock_init() which will
take care of initializing and registering a 'struct osmo_fd' for the
newly-created socket.
|
| |
|
|
|
|
|
|
| |
* use write_queue where applicable
* provide functions that work on raw FD and those with osmo_fd
* add support for multiple gsmtap instances (no global variables)
|
|
|
|
|
|
|
|
|
| |
The plan is to collect structs and routines for application
setup and remove many copies of the boilerplate code we have
right now. This starts with routines to ignore certain signals
and the stderr init code.
Increment the age of the library because a new interface was added.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary of changes:
s/msg_entry/osmo_config_entry/g
s/msg_entries/osmo_config_list/g
s/msg_entry_parse/osmo_config_list_parse/g
minor glitch included in this patch while I was at it:
-#include "linuxlist.h"
+#include <osmocom/core/linuxlist.h>
|