Age | Commit message (Collapse) | Author | Files | Lines |
|
Lets openbsc accept and connect CSD calls with V.110 9.6kbit/s
transparent mode.
This affects only the call signalling. To get actual data transmitted
you also need the matching libosmo-abis.
|
|
|
|
This adds a CSD mode parameter to the functions modifying the channel
mode on the phone and on the BTS side. Parameter will be ignored if
channel mode is not data.
|
|
We now have a lchan->csd_mode member that determines if RSL should
activate the channel in CSD transparent services or not. The previous
code always assumed CSD is non-transparent.
(This requires libosmocore >= eed26116c96f03c6128fac3dead9054714af6cab)
|
|
|
|
A function called this way should return 1 if it is compatible, so
something like "if (!chan_compat_with_mode())" will check if it is not
compatible.
|
|
Some nodes below 'config' didn't have ournode_exit / ournode_end,
and thus were not able to properly perform this function. exit should
always only go back one level, while end drops us back to ENABLE_NODE.
The prompt now represents the nesting level, and there's one consistent
space after the final prompt character (typically #).
|
|
|
|
This effectively limits the number of BTSs to 256, but I think that's
acceptable for now. Unfortuantely there's no decent way to dynamically
update the valid number range depending on how many BTSs are actually
configured in the system :/
|
|
this uses vty_cmd_string_from_valstr() from _very_ recent libosmocore,
so you have to update the library, sorry.
|
|
|
|
|
|
|
|
|
|
Use the len of the end and not the filename.
|
|
The BTS has 10s to respond to a command but we do not run any
timer. So it is possible that the BTS gets stuck in the process
of the bring up.
|
|
Use the Smalltalk SIP implementation to create a call
and once the call has been established start the replay
using the commoncode. No patching of RTP occurs yet.
|
|
|
|
|
|
|
|
Require a 0.5.2+ libosmogb due the change of the suspend_ref type.
|
|
|
|
One command missed the NO_STR in the documentation, share the
main text across all commands.
|
|
Update/Move/Create example configuration files for NiTB, BSC,
MGCP, NAT and the GbProxy. Create a script that starts, generates
the vty reference and terminates the application.
|
|
|
|
Change "pending send" to "pending-send" as there is no other pending
command right now, add missing documentation for parameters.
|
|
|
|
While generally we should log troly unknown RR messages, we can simply
pass along RRLP messages (which aren't unknown!)
In real networks, the RRLP would probably not end up at the MSC, but
well, sometimes we don't care what real/classic networks do.
|
|
A crash was obsserved in cb_data_ind() when mm is dereferenced.
This patch adds some safeguards that try to prevent the library handle
back-pointer to the pdp_ctx to be NULL, and print a stack backtrace in
case we are free() ing the sgsn-side pdp_ctx while there's still a
library handle attached.
|
|
It might be that we're deleting structures instead of properly cleaning
up the attached libgtp handles...
|
|
Group all three structure members involved in bts-specific timezone
handling into a sub-structure.
|
|
... it might well a completely non-ho-related establishment
|
|
The Nokia E71 sends a "IMSI Detach" this msc code does not immediately
send the "RR Channel Release", the E71 is impatient and sends a DISC,
the "RELEASE INDICATION" is handled by starting the channel release
procedure. OpenBSC sends a "RR Channel Release" which will never be
answered, during the early release there is no timer and the lchan will
be in "RELEASE REQUESTED" forever.
This commit removes the anchor operation and checks if the channel can
be released immediately. Regarding the channel release handling there
is already a branch that needs to be tested.
|
|
|
|
We are currently not checking if the BTS actually suports that cipher,
and we particularly don't have any hack for ip.access which apparently
seems to re-use the RSL algorithm identifier for A5/2.
|
|
so far, osmo-bts/sysmobts used to be entered as "sysmobts" type in the
configuration file. However, there are some differences in the
protocol/behaviour and we should reflect that by a new BTS plugin (with
lots of code reuse from the nanobts driver).
|
|
... otherwise it's impossible to distinguish them from each other.
|
|
this is primarily needed on the BTS side, but we should also use it on
the BSC side and make the parameters VTY-configurable.
|
|
|
|
This removes the libgb (GPRS NS/BSSGP) code from the openbsc.git
repository and uses the new version from libosmocore.git instead.
|
|
implementation
|
|
like in libosmogsm, we separate between header files that are just
reflecting information in the respective specs, and header files that
related to our specific implementation.
|
|
We change the minority of functions employing the gprs_bssgp_ prefix to
match with the majority without gprs_ in front.
|
|
|
|
|
|
Instead of direct function calls to individual functions, we now
generate primitives (osmo_prim) and send them to one
application-provided function "bssgp_prim_cb()"
|
|
|
|
|
|
|
|
Rather than using openbsc internal data/functions, we now use only
internal and libosmocore-provided ones.
|