http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-663 L3 Support <p>Dear @Khaled Khalil,</p> <p>Could you please assign a NEP DEV resource to check and fix the following issue:</p> <p>(I) XML File: 2025-09-17-11.04.12_Ooredoo<br/> (II) Import Date: 17-09-2025<br/> (III) Platform: .102</p> <p>Issue Description:</p> <p>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.</p> <p>References Attached:</p> <p>NEP Error Snippet:</p> <p>Snippet of “enodebandwidths” from XML: </p> <p>Snippet of “radiochannelbandwidths” xml:</p> <p>XML-Radio channel frequency band snippet:</p> <p>Thank you<br/> Indrasan</p> LS-663

Error Regarding Channel Bandwidths While 4G Cells Are Importing (Huawei)

Bug Normal Closed Fixed Indrasan Yadav Indrasan Yadav AI_All_incidents Huawei_RAN_OO Wed, 17 Sep 2025 15:12:50 +0300 Fri, 26 Sep 2025 15:35:06 +0300 Thu, 25 Sep 2025 04:34:47 +0300 NEP Tue, 30 Sep 2025 00:00:00 +0300 0 2 0 minutes 1 day, 3 hours, 30 minutes <p>Dear @Indrasan Yadav, </p> <p>If we take this example:</p> <p>The following band(s) 'TDD_42' should support at least one channel bandwidth for eNodeB (BARF026). </p> <p>When we search for this eNodeB in the error report, we find the following message: "Wrong Channel Bandwidth format (42.0) for EnodeB BARF026"</p> <p>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.</p> <p>In addition, a script has already been applied to the schema to add the 42.0 channel bandwidth.</p> <p>Please ensure the server is restarted after applying the patch.</p> <p>Regards, <br/> Mustapha</p> <p>Dear @Khaled Khalil,</p> <p>Kindly release the NEP patch version 3.7.0.1352, as the same issue has already been fixed by @Mustapha Al-Hage.</p> <p>Thank you<br/> Indrasan</p> <p>Dear @Basant Kumar,</p> <p>Kindly deploy the NEP patch on server .102. After the deployment, please ensure the server is restarted. Once the activity is completed, kindly provide an update.</p> <p>Build SUCCESS<br/> Project: NEP_OMANTEL<br/> Release Version: 3.7.0.1352 <br/> Build URL: <a href="http://ciserver.mobinets.local:8080/job/NEP_OMANTEL/1813/" class="external-link" rel="nofollow">http://ciserver.mobinets.local:8080/job/NEP_OMANTEL/1813/</a></p> <p>Date of build: Wed, 24 Sep 2025 08:18:00 +0300<br/> Build duration: 10 min</p> <p>Thank you,<br/> Indrasan</p> <p>Dear indrasan ,</p> <p>Latest NEP 3.7.0.1352 patch has been deployed on 102 . Kindly check and update </p> <p>Regards,<br/> Basant</p> <p>Dear @Mustapha Al-Hage,</p> <p>Thank you for your email.</p> <p>After applying the patch you shared, I imported the same XML, and I am pleased to inform you that the issue has now been resolved.</p> <p>Regards,<br/> Indrasan</p> Actual Start Thu, 18 Sep 2025 00:00:00 +0300 Baseline End Tue, 30 Sep 2025 00:00:00 +0300 Baseline Start Tue, 30 Sep 2025 00:00:00 +0300 Customer Date of Baselining Thu, 18 Sep 2025 08:20:43 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Tue, 30 Sep 2025 00:00:00 +0300 Planned Start Tue, 30 Sep 2025 00:00:00 +0300 Rank 0|xtiqjd: Rank (Obsolete) 9223372036854775807 VTDirections