From d4715fdecabbaf01c84031e66119c0bfaaa6156e Mon Sep 17 00:00:00 2001 From: Robert Schmidt Date: Thu, 23 Nov 2023 13:45:03 +0100 Subject: [PATCH] Add PNF to VNF's list of PNFs when IP available The same function is called in nr_start_resp_cb(), why there and not here? At reception of nr_param_response, we receive the remote PNF information on PNF/VNF. We have to store it. In nr_start_response, it might not be correct and/or can be taken out. The next commit will remove it. --- nfapi/oai_integration/nfapi_vnf.c | 1 + 1 file changed, 1 insertion(+) diff --git a/nfapi/oai_integration/nfapi_vnf.c b/nfapi/oai_integration/nfapi_vnf.c index 9bc3c37452..1da5f66a52 100644 --- a/nfapi/oai_integration/nfapi_vnf.c +++ b/nfapi/oai_integration/nfapi_vnf.c @@ -1551,6 +1551,7 @@ int nr_param_resp_cb(nfapi_vnf_config_t *config, int p5_idx, nfapi_nr_param_resp // for now just 1 NFAPI_TRACE(NFAPI_TRACE_INFO, "[VNF] %d.%d pnf p7 %s:%d timing %u %u %u %u\n", p5_idx, phy->id, phy->remote_addr, phy->remote_port, p7_vnf->timing_window, p7_vnf->periodic_timing_period, p7_vnf->aperiodic_timing_enabled, p7_vnf->periodic_timing_period); + nfapi_vnf_p7_add_pnf((p7_vnf->config), phy->remote_addr, phy->remote_port, phy->id); req->header.message_id = NFAPI_NR_PHY_MSG_TYPE_CONFIG_REQUEST; req->header.phy_id = phy->id; NFAPI_TRACE(NFAPI_TRACE_INFO, "[VNF] Send NFAPI_CONFIG_REQUEST\n");