This commit fixes the following deprecation warnings:
range must end at an odd port number, autocorrecting port (16000) to: 16001
% Deprecated 'sdp audio-payload number <0-255>' config no longer has any effect
% Deprecated 'sdp audio-payload name NAME' config no longer has any effect
Change-Id: I98549abf8dd726fcc67a1de6a5f8bee64558883d
This commit fixes the following deprecation warnings:
% MGCP commands outside of 'mgw' nodes are deprecated.
You should consider reading the User Manual and migrating to 'mgw' node.
Change-Id: Ic2b3c8a6775b6a34bfc03e0643a34772ae789139
This patch eliminates the following deprecation warnings:
% deprecated: 'ip.access rtp-base' has no effect, RTP is handled by the MGW
Please do not use legacy config 'mgw endpoint-range' (the range can no longer be defined by the MGCP client)
Change-Id: I64f6a26a3ae347083968c12855357de10baabc59
In change [1] I attempted to fix osmo-gsm-tester_virtual, but I did
not notice that the same problem also was in osmo-bsc.cfg.tmpl.
Also add the missing params to osmo-sgsn.cfg.tmpl.
Change-Id: I7b3adfa131a9dbb867b9ae68615da27191b021e5
Related: [1] Ie29589b46c65707089ff2b22c3b139b7b435cc95
This commit fixes osmo-gsm-tester_virtual, which currently fails
because osmo-msc is unable to start:
DLSCCP NOTICE sccp_user.c:656 OsmoMSC-A-Iu: Requesting an SCCP
simple client on ASP asp-clnt-OsmoMSC-A configured
with 'sctp-role server'
DLSCCP ERROR sccp_user.c:661 OsmoMSC-A-Iu: Requesting an SCCP
simple client on ASP asp-clnt-OsmoMSC-A configured
with 'sctp-role server' but no matching xUA server
was configured!
Change-Id: Ie29589b46c65707089ff2b22c3b139b7b435cc95
Configure the mgw in the mgw node, and drop the obsolete commands
endpoint-range and bts-base.
Fix for:
| Error occurred during reading the below line:
| mgw bts-base 8000
|
| % MGCP commands outside of 'mgw' nodes are deprecated. You should consider reading User Manual and migrating to 'mgw' node.
Change-Id: I077c4cd4c593da776a306117ad2a898a82d91064
open5gs requires the tun device to be pre-created and pre-configured
before using it. A ticket was opened in order to allow upfd itself
configuring it in [1]
[1] https://github.com/open5gs/open5gs/issues/899
Change-Id: I3b1857f09017cacee1c86f41dae1463c11b50490
this patch adds the ability to configure NR cells with
Amarisoft eNB. It adds the new DRB-NR template and updates
the normal enb.cfg template to allow using it as LTE only
or with NR cells (5G NSA).
Change-Id: Ia27bbc6db5920ce14bacabe8043601aa2adaa5fe
this also removes the entire help text around arguments (that
were very outdated already) and only leaves the actual values with changes.
Change-Id: Icb9e8e7b1c68cf024db3a7273af791f017c32003
due to internal PDU buffering between PDCP/RLC the poll frequency
needs to be increase to get quicker feedback.
Change-Id: I4114fb36e675b3f91c471558f716276ab24f1db5
this patch adds generic support for custom frequency bands to the ms class.
it then extends the config template for AmariUE to use them.
we set the default values for EARFCNs for DL/UL to the old values.
Change-Id: I7b2250e13fc1161be1a1d73a4348f07b31c0f724
this config option overwrites the EARFCN config that is typically
used to tell the UE the bands to scan for cells. When custom
frequencies are used, this option allows to set them explicitly.
Change-Id: Ice070ea6755e273d916db2dc941068d33bbe206a
the UEs count param, if specified, is mapped into the config
values of the EPC so it can be used for template rendering.
Since we only have one count parameter, its added to the first
subscriber. 1 is the default value and its used when no count
param is specified.
this allows to run the Amarisoft UE simulator with the Amarisoft EPC
without having to create subscriber entries for each simulated UE.
Change-Id: I29885791f716c204d0b6f18ba134885bae853b6f
Despite open5gs allowing to change the GTP ports in the config file, in
reality changing those values to something else than the standard prot
will fail. Hence, we must use the standard port. As a result, we must
use different IP addresses in each process to avoid ip+port collisions.
Let's use some loopback addresses which shouldn't require extra
configuration on the host, and still only requiring 1 run_node as per
existing EPCs, with the limitation that only 1 open5gs EPC instance can
be run at one in a given run_node.
Related: https://github.com/open5gs/open5gs/issues/897
Change-Id: Id3062c6ad9d6de4c6066547e1e46edad5da285c1
when they are greater than 0 they are written as config paramter.
if they are -1 they are disbaled and automatic gain calibration is
used.
Change-Id: I473ff3ae679784178574d2f76b612dbf77180490
we've provided only all_log_level so far but sometimes it's needed
to select the level per layer. This patch adds the ability
to do so for the NAS layer in the UE.
Change-Id: Iab2bce65e8af81f6d344849c97952e6441cb2846
srsENB now supports PDCP discard so we set it to a sane value.
Also enable status reporting for UL.
Change-Id: Ib6ad0ff57b95a1f220f87c1ede0f6eacc5fb21ff
we've detected a possible race condition during the Msg3
transmission that caused the thread that sets the Msg3 grant
to be delayed. The PHY worker that executed TTI+2 finished
by that time already and didn't even see the pending UL grant.
This is issue is more likely to happen on loaded system,
for example when running parallel ZMQ jobs. We therefore decided
to reduce the number of parallel PHY workers to 2 so the issue
is circumvented.
Change-Id: Ibdb42a1705d87b6d343201458c8fe397398802bc
we've already incrased the t3413 value in 9c7fd618d2
but realized it may still be too low in some cases.
we set it to 12s now.
Change-Id: I9c3c59c0ff8f539a44b420f8ba31eea016c211ce
This patch enables setting cipher and integrity algorithms
in Amarisoft eNB and srsENB via scenario files. If no
settings are defined following defaults are applied:
- Cipher algorithm: EEA0, EEA2, EEA1
- Integrity algorithm: EIA2, EIA1, EIA0
Example of setting cipher algorithms:
- 4g:srsue-rftype@uhd+srsenb-rftype@uhd+mod-enb-cipher@eea1+mod-enb-cipher@eea0+mod-enb-nprb@6
Change-Id: I595206b7d49016fb6d0aec175c828d9537c53886
this executed the PRACH search in the main thread so
PHY workers and PRACH processing don't diverge in loaded
scenarios
Change-Id: I97eddb5f9ca682251ded1f73093c2d0a49462bd6
we've seen that the default value of 2s might be a bit tight.
the value is network dependent so no real default value exists.
however, 6s seems to be a good compromise.
Change-Id: Icc75ee048c2cc605ab26c4c87a039519998f7e57
since ZMQ runs are not using wall clock anyway, measuring
TTI execution isn't useful, disable it therefore to avoid
misleading warnings.
Change-Id: I5c2cb0abcfce0ee67806f6611356f4d5d180541d
the order of checks needs to go from high to low, i.e. the higher
release feature (e.g. qam256) needs to be checked and set first.
in theory it should also be possible to have a CA-capable UE
that does not support QAM256, but for srsUE we announce both anyway.
Change-Id: I2fa49f0cb5d80db412a811ceeb380359c8ad67a7
this patch fixes some regressions in the Amarisoft UE class,
the config template, etc. that have been undetected bc we never
executed tests with it.
Change-Id: I397e675a4018acf3372a3b7e29fd864703b2b919
* add new UE feature
* enable in srsue.conf.templ
* add new table for maximum rates
* add config scenario to enable SIB option for QAM64
Change-Id: I6ac2c9989a761e91b93d76c2507f55f0140b202d
Vadim Yanitskiy
Pau Espin
Oliver Smith
Andre Puschmann