[LS-783] Feasibility Check: Darwish Requirements for Cutover Process Modification Created: 14/Nov/25  Updated: 22/Dec/25  Due: 14/Nov/25

Status: Need More Info
Project: L3 Support
Component/s: FN
Affects Version/s: None
Fix Version/s: None

Type: CR Priority: Normal
Reporter: Shamim Ahmed Assignee: Ayed Bada
Resolution: Unresolved Votes: 0
Labels: MS_OT
Σ Remaining Estimate: 2 hours Remaining Estimate: 2 hours
Σ Time Spent: 5 hours Time Spent: 5 hours
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: File RE Feasibility Check Darwish Requirements for Cutover Process Modification.msg    
Sub-Tasks:
Key
Summary
Type
Status
Assignee
LS-784 Feasibility Check: Darwish Requiremen... Technical task Open Bug Khaled Khalil  
Customer:
OMAN-Tel
Planned Start:
Planned End:
Actual Start:
Date of Baselining:

 Description   

Dear @Abir Messaikeh

This memo outlines three key requirements from Darwish concerning the Cutover process. We require an assessment of their technical feasibility:

1. DP (Distribution Point) Selection Logic:
o Current State: During cutover, NEP determines the DP based on the existing (OLD) DP, using the provided OLD EXC, New EXC, OLD Cabinet, and New Cabinet inputs.
o Required Change: NEP must ignore the OLD DP. If the OLD DP is available within the New Exchange (New EXC), it should be used. If not, NEP must select any available DP from the New Exchange (New EXC).

2. Cutover History Management:
o Requirement: All existing data must be cleared from the Cutover History upon completion of the process.

3. Error Handling and Messaging:
o Current State: NEP currently displays a "Cutover successful" prompt simultaneously with a system error (as shown below/in the attachment).
o Required Change: When the cutover process is not fully/partially successful, NEP must correctly display a "Cutover failure" message instead of a success prompt.

Action Required: Please review these three points and advise on the feasibility required for implementation.



 Comments   
Comment by Abir Messaikeh [ 22/Dec/25 ]

pending customer to share GTM if required before going to next step

Generated at Fri Apr 17 08:27:57 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.