testenv: remove dead code for [testsuite] prepare= (details)
testenv: add proper [testsuite] prepare= support (details)
hnbgw: Split ConnHdlr component code to its own file (details)
RAN_Emulation: Introduce field ranap_connect_ind_auto_res (details)
hnbgw: Allow modifying RanOps during test startup (details)
Convert RAN_Conn_Prim from enum to union (details)
RAN_Emulation: Allow setting reason in primitive MSC_CONN_PRIM_DISC_REQ (details)
Commit
c009d49e97b9302ccb411567fb23a9f3e760e40c
by Oliver Smith
testenv: remove dead code for [testsuite] prepare=
Remove some WIP code that I intended to use for enabling the mongodb repository before installing binary packages, to be able to dynamically install mongodb from there. I solved it differently by just always having mongodb in the podman image.
This was a dead code path because configs with prepare= in [testsuite] are currently not valid, and therefore testenv refuses to use these configs (see keys_valid_testsuite in testenv_cfg.py's verify()).
I have a different use case for running prepare= before running the testsuite, to replace a module parameter in the testsuite's config. This will be done in the next patch.
Move the execution time of prepare and clean scripts in testdir.prepare() after the testsuite config has been copied to the testdir, so it can be modified by the prepare script.
Commit
6ac0838dd48308f165343f32f3e9ae47848d121e
by Pau Espin Pedrol
RAN_Emulation: Introduce field ranap_connect_ind_auto_res
This field allows skipping automatic response of the connect_ind, hence allowing ConnHdlr to totally skip it, delay it, or generate a CREF by means of sending RAN_Conn_Prim:MSC_CONN_PRIM_DISC_REQ to RAN_Emulation, as per ITU Q.711 Figure 8.
Commit
b9ded6e8ac7bbd34128e68c457cb986d8cc2d853
by Pau Espin Pedrol
RAN_Emulation: Allow setting reason in primitive MSC_CONN_PRIM_DISC_REQ
This allows setting a specific reason in the CREF transmitted on the wire, other than "End user originted (0)". A follow-up commit will add a test in HNBGW_Tests where an emulated MSC answers with CREF reason "End user failure (0x02)".