Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Labels:
-
Customer:Ooreedo Tunisia
Description
Dear @Khaled Khalil,
Could you please assign a NEP DEV resource to check and fix the following issue:
(I) XML File: 2025-09-17-11.04.12_Ooredoo
(II) Import Date: 17-09-2025
(III) Platform: .102
Issue Description:
Although channel bandwidths are available in the XML, an error still appears during import. All 4G cells are successfully imported in NEP, but the error persists. For reference, I am sharing an example below.
References Attached:
NEP Error Snippet:
Snippet of “enodebandwidths” from XML:
Snippet of “radiochannelbandwidths” xml:
XML-Radio channel frequency band snippet:
Thank you
Indrasan
Dear @Indrasan Yadav,
If we take this example:
The following band(s) 'TDD_42' should support at least one channel bandwidth for eNodeB (BARF026).
When we search for this eNodeB in the error report, we find the following message: "Wrong Channel Bandwidth format (42.0) for EnodeB BARF026"
The implemented logic uses a specific pattern to validate channel-bandwidth formats. This pattern was modified to accept the 42.0 channel bandwidth, patch is needed: 3.7.0.1352.
In addition, a script has already been applied to the schema to add the 42.0 channel bandwidth.
Please ensure the server is restarted after applying the patch.
Regards,
Mustapha