Changes

hnbgw: with-pfcp: Support running ConnHdlr concurrently

Use Mutex to serialize PFCP session establishment to workaround the
"Req with SEID=0" dispatching problem.
This same system is used in S1GW_Tests.

Change-Id: Ie19ee0bd1b811e9381e3c245a4b1208de8afcbce

RAN_Emulation: Increase ExpecTable size to 16

Use same size as other tables.
This allow running HNBGW_Tests with 16 ConnHdlrs instead of 8.

Change-Id: I0748da523d886a8097b9f35991b9044e6ca33f95

hnbgw: Add test TC_ps_rab_assignment_concurrent

Related: SYS#6602
Change-Id: I053950373cec93ed8dbdfd6b8a71ffe31de3806f

hnbgw: Parametrize MgcpParameters MGCP endpoint

This will be needed if we want to run several CS RAB ConnHdlrs in
parallel.

Change-Id: I4bb28dea22a6ea5b415d6ca16bde61b835d435bc

hnbgw: mgcp: Support running CS RAB ConnHdlr concurrently

Use Mutex to serialize CRCX wildcard endpoint, in order to be able
to properly steer the message to the good ConnHdlr.

Change-Id: Ibd97a37d98abfa746b58db0ea8bb591e7c8dc638

hnbgw: Introduce test TC_rab_assignment_concurrent

Related: SYS#6602
Change-Id: I1f717edbe4a758288d017861c4b77836c5811040

RUA_Emulation: Add missing msg component destination

Seen while running lots of components concurrently:
"RUA_Emulation.ttcn:315 Dynamic test case error: Port CLIENT has more
than one active connections. Message can be sent on it only with
explicit addressing."

Change-Id: Ief257969a451f2d11ad7619fb97af16d7dd7e199

hnbgw: Small fixes in f_tc_rab_assignment()

Change-Id: I2f21d3ed59f6b8d26cfee3bd8e75c63cc9d710a3

deps: Update titan.ProtocolEmulations.SCCP to upstream master

Until now we were using our own fork with an extra patch with a fix for
SCCP conn id 0.
This patch, together with other patches was merged upstream today.
Hence, update our dependency to point to current upstream master.

Related: OS#6185
Change-Id: I8ba6cec24205337f19bac951d9a8d4f5d4d476ad

osmo-*.cfg: enable gsmtap log

Now that jenkins uses the osmo-*.cfg files from osmo-ttcn3-hacks for the
testsuites that were ported to testenv, make sure that these configs
enable logging to gsmtap log as it was the case in docker-playground.
This gives useful additional context in the pcap files.

Change-Id: I8a1c734c0d34b81e70707b0ac6732a366b867bbe

library/gsup: improve GSUP_IE templates

* Turn template params into templates
* Use proper template restrictions
* Remove unnecessary valueof()s
* Improve formatting

Change-Id: I67cc555a54113dccb11d0cc05cee66f5c2d795fe

library/gsup: rework f_gen_{tr,ts}_ss_ies() and SS templates

* Add missing param restrictions to SS related templates.
* f_gen_{tr,ts}_ss_ies(): proper template param restrictions.
* f_gen_ts_ss_ies(): return a template, not a value.
* f_gen_ts_ss_ies(): append IEs using list index.
* f_gen_ts_ss_ies(): isvalue() -> istemplatekind()
                     to allow passing template lists.
* f_gen_tr_ss_ies(): istemplatekind() -> ispresent()
                     to allow passing template lists.
* f_gen_tr_ss_ies(): 'omit' -> '*' for optional params.

Change-Id: Ia611ffa3845d48c5553c70f10981aa029d00d873

library/gsup: add src/dst name IEs to all SS templates

This enables us to send/match OSMO_GSUP_{SOURCE,DESTINATION}_NAME
IEs (if needed) and brings consistency to all SS related templates.

This patch makes the following testcases pass [again]:

* TC_mt_ussd_for_unknown_subscr,
* TC_proc_ss_for_unknown_session.

At some point osmo-msc started including the Source Name IE in
OSMO_GSUP_MSGT_PROC_SS_ERROR messages, which we didn't expect.

Change-Id: I8d947313a99491d2e4790bc06db863fe09d8b5cf