Details
-
Type:
Bug
-
Status:
To Be Released
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: SRD
-
Labels:None Labels
-
Customer:OMAN-Tel
-
Complexity:Medium
-
Product:NEP
Description
For SRD OBB Scenario, we are not reaching the OBC Activation task - Verify if SRD is sending to the right destination.jpg
The SSE team completes the OBB_CONFIRMATION task, after which SRD sends the OBB order to OBC with all required parameters.
The Request Status updates to PENDING_OBB, and an automated task named OBC Activation is triggered—unassigned and not manually executable.
When the OBC Activation task is active, it confirms that the order has been successfully sent to OBC. The process now awaits updates from OBC, which will be logged in the OBB milestone grid.
Attachments
Issue Links
- clones
-
ACE-858
updateSrdServiceStatus
-
Activity
| Description |
Input:
<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:updateSrdServiceStatus> <!--Optional:--> <requestId>05</requestId> <!--Optional:--> <serviceName>FBB</serviceName> <!--Optional:--> <serviceStatus>Upgrade</serviceStatus> </ser:updateSrdServiceStatus> </soapenv:Body> </soapenv:Envelope> Output: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:updateSrdServiceStatusResponse xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/"/> </soap:Body> </soap:Envelope> Same for both 179 and new local |
For SRD / OBB Scenarion :
The SSE team completes the OBB_CONFIRMATION task, after which SRD sends the OBB order to OBC with all required parameters. The Request Status updates to PENDING_OBB, and an automated task named OBC Activation is triggered—unassigned and not manually executable. When the OBC Activation task is active, it confirms that the order has been successfully sent to OBC. The process now awaits updates from OBC, which will be logged in the OBB milestone grid. |
| Summary | CLONE - updateSrdServiceStatus | For SRD OBB Scenario, we we are not reaching the OBC Activation task - Verify if SRD is sending to the right destination (OBC Team) |
| Description |
For SRD / OBB Scenarion :
The SSE team completes the OBB_CONFIRMATION task, after which SRD sends the OBB order to OBC with all required parameters. The Request Status updates to PENDING_OBB, and an automated task named OBC Activation is triggered—unassigned and not manually executable. When the OBC Activation task is active, it confirms that the order has been successfully sent to OBC. The process now awaits updates from OBC, which will be logged in the OBB milestone grid. |
For SRD OBB Scenario, we are not reaching the OBC Activation task - Verify if SRD is sending to the right destination.jpg
The SSE team completes the OBB_CONFIRMATION task, after which SRD sends the OBB order to OBC with all required parameters. The Request Status updates to PENDING_OBB, and an automated task named OBC Activation is triggered—unassigned and not manually executable. When the OBC Activation task is active, it confirms that the order has been successfully sent to OBC. The process now awaits updates from OBC, which will be logged in the OBB milestone grid. |
| Summary | For SRD OBB Scenario, we we are not reaching the OBC Activation task - Verify if SRD is sending to the right destination (OBC Team) | For SRD OBB Scenario, we are not reaching the OBC Activation task - Verify if SRD is sending to the right destination (OBC Team) |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
| Attachment | Screenshot 2026-06-15 141104.png [ 136924 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
3d 5h 19m | 1 | Zein Trabelsi | Today 1:48 PM | |||||
|
7s | 1 | Zein Trabelsi | Today 1:49 PM | |||||
|
11s | 1 | Zein Trabelsi | Today 1:49 PM |
|
Links Hierarchy |
 Documentation
|
its OBC integration issue, not SRD issue. SRD is correctly configured to http://10.64.163.150:7955/obcservice?wsdl (reachable). But the WSDL OBC returns references its OpenShift route https://obc-route-cp4i-stg.apps.ocptest.otg.om:443/obcservice. That host is unreachable from the SRD environment verified from machine 10.164.144.85 (see attached ss) + SRD server log shows java.net.UnknownHostException, and a browser on a client server on the same network returns ERR_CONNECTION_TIMED_OUT.
Action (OBC/infra): either republish the OBC WSDL so its xsd:include and soap:address use the reachable host 10.64.163.150:7955, or make obc-route-cp4i-stg.apps.ocptest.otg.om:443 reachable from the SRD network. Then we restart SRD and re-test.