[ACE-716]  Review SRD API checkCopperTrailFeasibility Created: 10/Mar/26  Updated: 02/Apr/26  Due: 10/Mar/26

Status: Ready for QA
Project: ACE
Component/s: SRD
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Mbaye Lo Assignee: Mbaye Lo
Resolution: Unresolved Votes: 0
Labels: Milestone2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Customer:
OMAN-Tel
Planned Start:
Planned End:

 Description   

Review SRD API checkCopperTrailFeasibility :

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.internal.api.srd.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:checkCopperTrailFeasibility>
<!-Optional:->
<requestId>12082024</requestId>
<!-Optional:->
<siteLat>23.55626893321905</siteLat>
<!-Optional:->
<siteLong>58.21754375406719</siteLong>
<!-Optional:->
<maxDpDistanceInMeters>1000</maxDpDistanceInMeters>
<!-Optional:->
<maxExchangeDistanceInMeters>1000</maxExchangeDistanceInMeters>
<!-Optional:->
<coordinateFormat>EAST_NORTH</coordinateFormat>
<!-Optional:->
<serviceTypeName>New</serviceTypeName>
<!-Optional:->
<dataProfilType>?</dataProfilType>
<!-Optional:->
<bandWith>100.0</bandWith>
<!-Optional:->
<nbLines>100.0</nbLines>
<!-Optional:->
<nbChannels>100.0</nbChannels>
</ser:checkCopperTrailFeasibility>
</soapenv:Body>
</soapenv:Envelope>

 Comments   
Comment by Ayed Bada [ 01/Apr/26 ]

I checked the logs and found that the API returns <responseMessage>No Trail found</responseMessage> because the NEP API returned null.
I retested the use case locally, and the NEP API returned correct data for ID 84. This suggests that the issue may occur when the NEP service is down, causing checkCopperTrailFeasibility to return an invalid response.
Currently, the VPN is down, so I cannot verify whether the API is returning valid data in that environment.
In another case, the API returns <responseMessage>SRD_DP_MVIEW</responseMessage>. This occurs because the SRD backend reads from a materialized view instead of the correct view.
Fixed the HttpClientErrorException issue.

This issue will be resolved in patch 4.0.0.5.

Generated at Wed Apr 15 13:45:53 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.