Changes

asterisk: Enable capabilities required to set up ipsec

Change-Id: I2dc040cf87169c9a59dc7e9f1af0e1c17bde6683

ttcn3-asterisk: Enable debug in log file

Change-Id: Ifbc8208507ba47e9f6a1eaf5a43465d2a1af08c1

ttcn3-asterisk: Enable debug for pjproject

Change-Id: I7de6ac31f7a75411fb515501611187f97e829ab3

ttcn3-asterisk: Configure asterisk for initial SIP register on IMS side

This set of pjsip config requires work done by jolly in our fork of
asterisk adding IMS features.

Depends: osmo-ttcn3-hacks.git Change-Id Idb3b19ccd82cad25948106b2c72aa424d7f79cd8
Change-Id: I66d128192146ad600203ea2a41b8bf019311d603

ttcn3-docker-run.sh: Fix dumpcap failing to access /data inside docker

In docker, the /data dir is mapped to $VOL_BASE_DIR, which is created by
docker-playground.git jenkins-common.sh, hence as the user running
jenkins.sh in the host system.
As a result, when the dir is mapped to /data, inside the container it
will have the UID:GID of the outter user, not the one inside docker.

Before this patch, if a ttcn3 container was started in jenkins.sh with
--cap-add=NET_ADMIN, then osmo-ttcn3-hacks.git/ttcn3-tcpdump-start.sh
would select dumpcap instead of tcpdump, to attempt to record a pcap
file to /data/$testcase.pcap.
Due to some unknown way of dropping privileges done by dumpcap though,
it was unable to open the /data/$testcase.pcap due to /data being owned
to another user (tcpdump doesn't have this problem).

This patch fixes the above scenario by making sure /data is chowned to
the user running stuff inside docker. This is already kinda expected
since there's a fix_perms() script in jenkins-common.sh reverting files
created during the test so that they can be accessible by outter user
once everything is finished.

Change-Id: I1229a91cdbb1aa73fd94f1bf7e26f34086f06b25

ttcn3-ggsn-test-ogs: run smf in 4g only mode

Remove the SBI related configuration, so open5gs-smf does not attempt to
connect to the NRF every few seconds.

Fix for:
  [sbi] WARNING: [299d78ae-fae5-41ee-84a3-dbd9fa117ce7] Retry registration with NRF (../lib/sbi/nf-sm.c:182)
  [sbi] WARNING: [7] Failed to connect to 127.0.1.10 port 7777 after 200 ms: Couldn't connect to server (../lib/sbi/client.c:698)

Change-Id: I61d60e6e71b671c3deb20cc7ff8abb81ea4d5f03

Revert "ttcn3-docker-run.sh: Fix dumpcap failing to access /data inside docker"

This reverts commit 2b9c8e3db8cf77c5ce5c3f888365f983f3ee8d76, as it
causes a lot of testsuites to fail with e.g.

  + network_replace_subnet_in_configs
  + set +x
  Applying SUBNET=161 to: /home/osmocom-build/jenkins/workspace/ttcn3-ggsn-test/logs/ggsn-all/osmo-ggsn.cfg
  Applying SUBNET=161 to: /home/osmocom-build/jenkins/workspace/ttcn3-ggsn-test/logs/ggsn-tester-all/GGSN_Tests.cfg
  sed: couldn't open temporary file /home/osmocom-build/jenkins/workspace/ttcn3-ggsn-test/logs/ggsn-tester-all/sedsByWIc: Permission denied

Let's discuss how to fix the dumpcap problem instead in OS#6455.

Change-Id: Ic98e8206d8251060b777fc7d0b4497ba3e1caf7f

debian-*: install pylint from debian repos

Get pylint from the debian repositories to be on the same version until
we use the next debian version, instead of always installing the latest
pylint version from pip.

Change-Id: I721db1c18db43cc7a2d38177e9846c43dbdd0ae3

ttcn3-asterisk: Configure docker testsuite to be able to set up ipsec tunnels

Depends: osmo-ttcn3-hacks.git Change-Id Ic042422788ee406f5b71ca3878bc5617e5455579
Change-Id: I3379e4991a5c705b5b0a14e5fee2eb165cc8a1e3