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
The VTY prompt may contain regular expression metacharacters in it,
so the self.re_prompt will not match as expected. One example is
the modem app in osmocom-bb.git using promot 'OsmocomBB(modem)'.
Change-Id: Ibada798a214be97409b55556724f558b67da7365
Related: osmo-python-tests.git I47b1f1c1765acb1b935dcbcc54bbb5eb539db4f0
Related: OS#6001
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
This commit fixes 2 functions from util.py:
- setcap_netsys_admin: removed "self" from the arguments.
- create_netns: pass "run_dir" to Process and convert the arguments to
a list as the other methods in the file.
Change-Id: Ida4c6d6500be92b8d1f96e4e7a870e63bd329be9
Adds support to the malloc interceptor for the SRS eNodeB. This interceptor will generate a log file that lists the mallocs, reallocs and frees produced by the srsenb.
Change-Id: I0078020468f58bdd70b0b5de879eb58192f947a6
Sets the remote directory for fapi to the given in the variable 'remote_dir' in the reource schema.
Change-Id: I77a56835a4054b86d1d3f7da823a013b3370f767
Allows to run given scripts before and after the execution of the SRS
eNodeB. The scripts are retrieved as a list from the resource.conf file.
Change-Id: I5017caae933809b89b32ea132be8552d6554e20e
Added the feature to configure the packet length in udp iperf. Added a modifier to select the length value.
The default value is configured to 1460.
Change-Id: Ic886faa82b7cb25f2bce685eb80910623e4ff686
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
use RemoteProcessSafeExit() for launching all open5gs components
to make sure they are stopped at the end as well.
Change-Id: Ia1439577d60f9694da70c4e42c621100c8ef295e
there is no open5gs_enb so having the epc in the name is redundent, also
it safes typing and allows longer scenario configs without exceeding
filename limit.
Change-Id: Ib10bc6031ecc8de88a9c718b136d2641ce46e11d
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
this allows to use the lteue to generate DL traffic. the
server listens on the default spgw address.
Change-Id: Iad081e57e2fd9d3cbc3e59e4f729a4721ad778c9
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