1. Reverts GTPU_need_ITTI back to develop
2. Removed gdb helper and co files
3. Reverts changes to logging mechanism
4. Reverts changes to assert that were unnecessary
5. Reverts changes to VNF that occured from a bad merge
6. Removes unnecessary else() in gNB softmodem
This change allows multiple UEs to have a tunnel interface
brought up when connecting to the 5GCN
Also, adding two new config files for mutltiple UEs
to connect to the 5GCN
When we check if the pointer is NULL before CALLOCing,
then the gNB will crash. It seems that we are mostlikely
leaking memeory since the gNB only crashes with the old
change. By reverting these changes, the gNB does not crash.
We are seeing UE-to-UE IP traffic on this commit when
the tunnel interfaces are established (~50% of the time).
MR !1317 : Change variable types in statistics
When running gNB for a long time and transferring high amount of data, statistics become negative (and later in an arithmetic overflow) because they are too short for such amount of bytes. Example: UE 0: ulsch_total_bytes_scheduled -1804219593, ulsch_total_bytes_received -1804223769
MR !1315 : Using rnti to assign different pucch resource to different UE
This MR is to assign different pucch resource to different UE using rnti
MR !1305 : Fix various issues on ULSCH processing on UE
-add mutex to protect ul_config_pdu against race condition with multiple threads. Otherwise UE will crash as parameter of subsequent thread will be overwritten: Assertion (Nl>0) failed!In nr_get_E() openairinterface5g/openair1/PHY/NR_TRANSPORT/nr_tbs_tools.c:47
-Fix a logical error that sends obsolete buffer erroneously on UL and causes crash in gNB. In nr_process_mac_pdu: residual UL MAC PDU in 736.19 with length < 0!, pdu_len -69
-Fix a logical error that if FAPI_NR_UL_CONFIG_TYPE_PUSCH pdu is not of index 0 in ul_config->ul_config_list, the packet is not sent out.
MR !1321 : CI automatic un-deployment of RAN containers + fixes
-in main container pipeline, the post section in the docker-hub-push stage was incorrectly placed
-when building images on develop pushes, the ran-build image was not built
-iptables check is correct now (could not detect if in not ACCEPT
-something is wrong, automatic un-deployment of RAN containers
-added a "dummy" undeploy scenario just to be sure.
-4g/5g RF simulation tests may fail due to lost socket on ue container. Repeat in case of failure
ci_bring_test_results_to_dashboard:
-RAN Status and Tests dashboards
cherry pick : nsa conf files, ulsch_max_frame_inactivity = 1;
-to reduce ping time
francescomani