Age | Commit message (Collapse) | Author | Files | Lines |
|
It's useful to know RTP statistics (number of packets lost, jitter, etc)
when looking at voice call quality issues. Right now this information is
not avialable anywhere and this looks like the best place to start.
|
|
This can be used to replicate a build issue more easily.
Build specific to the Octphy.
|
|
This can be used to replicate a build issue more easily.
|
|
|
|
This is only with osmo-bts-trx as others require headers that are
not packaged yet.
|
|
Fixes: OS#1665
|
|
|
|
|
|
Explicitly store and use "center" arfcn used by each dsp (1 dsp
corresponds to 1 phy link).
|
|
|
|
|
|
|
|
|
|
|
|
There are several types of System Information messages with tricky
scheduling rules described in 3GPP TS 05.02 § 6.3.1.3. This GNU Awk
script takes in .csv file with sequence of scheduled SI messages (for
example generated using tshark from GSMTAP capture - see usage note
inside the script) and check the scheduling rules compliance.
|
|
Add missing entries to .gitignore
|
|
Right now we do not support multiple SI2quater messages, so return error
if either index or count is non-zero.
|
|
According to 3GPP TS 05.02 § 6.3.1.3 SI2ter messages should be scheduled
in FN with TC=4 only if SI2bis messages are also available.
|
|
Upcoming releases will support TCH/H and we should start to test
the DSP->RTP code.
|
|
The file has been renamed, attempt to catch up
|
|
Add SysmoBTS-specific example.
Remove outdated generic example which is no longer working.
|
|
This issue prevented scheduling of SI 2quater messages.
|
|
Bad parameters are passed to the event structure and the default
initialization should happen.
|
|
I had accidently bumped the version as I thought that osmo_ph_pres_info_type
was part of the ABI. It is not an only internal to the BTS. Revert
this part of the change.
|
|
Previously osmo-bts-octphy have not provided in-band presence
information which cause off-by-one errors and misinterpretation of
ph_data_ind by PCU. This fixed now by adding support for explicitly
passing PH-DATA presence info. Corresponding check and in-band passing
of presence information are removed.
Note: this requires libosmocore version with osmo_ph_pres_info_type
support integrated.
[hfreyther/max: Remove + 1 from the decoded length]
|
|
We want the size of the array, not of the pointer to the array.
Found by coverity (CID 1351422).
|
|
This is not really an issue, but makes coverity happy (CID 1351422).
|
|
There was a copy+paste error, checking for plink but we should check for
pinst.
This was found by coverity (CID 1351424).
|
|
|
|
|
|
|
|
|
|
Let's use one systematic naming schemes for all BTS models.
osmobts-trx -> osmo-bts-trx
sysmobts -> osmo-bts-sysmo
lc15bts -> osmo-bts-lc15
|
|
In some cases we'd like to run multiple instances of osmo-bts on a
single machine. This is the case where we a multi-TRX PHY is to be used
for several BTSs, or in case osmo-bts-trx has multple SDRs attached.
This wa currently prevented by having a hard-coded PCU socket path
and telnet port, which are now configurable via VTY / config file
itself.
|
|
|
|
It remains up to the individual BTS hardware models to decide
whether or not to register those commands (depending on whether they
support the feature) via cfg_bts_auto_band_cmd / cfg_bts_no_auto_band_cmd
|
|
We want to start talking to the L1 from the point the PHY link has
been opened, and not only once an OML connection has been established.
|
|
|
|
At the time the phy link / phy instance level VTY configuration
commands are parsed, we did not yet call l1if_open() and thus
pinst->u.{lc15,sysmobts}.hdl == NULL.
PHY or PHY instance specific configuration must thus be stored inside
the phy_link or phy_instance itself, and not inside the (not yet
existing) handle.
We solve this by moving around some parameters:
* clk_use_eeprom/clk_cal/clk_src/calib_path get replicated in
phy_instance
* min_qual_{rach,norm} are moved into the generic part (which means
that osmo-bts-octphy and osmo-bts-trx should also implement them)
|
|
this is part of the copy+paste legacy from sysmobts and can be removed
as it is not used.
|
|
Due to the changes introduced by the phy_link API, it's not easy to set
the default DSP trace flags via a command line argument anymore. We now
rather introduce a persitent VTY configuration command, by which the
default DSP tracing configuration can be set (for each PHY).
The persistent trace flags are stored in the phy_instance, while the
current operational run-time flags are in fl1h->phy_instance.
|
|
this function is intended to be used by VTY commands that need to
resolve a given PHY interface.
|
|
|
|
|
|
|
|
|
|
This includes changes required for
* shared main() function accross all BTS models
* use of the new phy_link / phy_instance infrastructure as the basis
for true multi-TRX operation
|
|
The user can now use ./configure --with-litecell15=/my/local/path
|
|
|
|
by using a talloc pool, we avoid having to go back to the libc
malloc pool all the time. The msgb allocations and libortp allocations
happen quite frequently during processing and show up as one of the
high priority items in osmo-bts profiles on sysmoBTS with 14 concurrent
TCH/H calls (highest load scenario).
talloc still consumes significant CPU, this is mostly due to the
zero-initialization of all the associated buffers. Strictly speaking
we shouldn't need this, but any change there would require lots of
testing, as there might be hidden assumptions in the code?
In some percentage of cases, talloc still seems to fall back on malloc
for msgb allocations, which is currently a bit of a mystery. The pools
certainly are large enough, talloc_reprt() rarely reports more than a
few tens of kilobytes used by the msgb pool.
From 2ecbf871301cdc36c0212dd7526fc94ffa4597d1
|