Details
-
Type:
Bug
-
Status:
Rejected
(View Workflow)
-
Priority:
Normal
-
Resolution: Cancelled
-
Affects Version/s: UA 4.0.0.10
-
Fix Version/s: UA 4.0.0.10
-
Component/s: FN
-
Labels:
-
Customer:OMAN-Tel
Description
Error while creating OBC order V+D New Activation. Order is not created.
Error returned : 73 = failed to get serial number from arbor, error code : 0752
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.api.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:arborWOOBC_fCNAOBC>
<fAppType>I</fAppType>
<fOLT>AZA1</fOLT>
<fFDHMDU>OOOO</fFDHMDU>
<fOBCTag>40QFM1448709571//OTXX837401</fOBCTag>
<fSubno>44444069</fSubno>
<fWOID>4444400169</fWOID>
<fUsage_Type>BG</fUsage_Type>
<fOrder_Type>INST</fOrder_Type>
<fNoOfSTBs>0</fNoOfSTBs>
<fUserID></fUserID>
<arborOrderId>444440069</arborOrderId>
</ser:arborWOOBC_fCNAOBC>
</soapenv:Body>
</soapenv:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-40d2a842-0d43-40bb-9029-dd93ef032e04">
<wsse:Username>nep-api-key</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">mobinets@2017</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<soap:Body>
<ns2:arborWOOBC_fCNAOBCResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>73</return>
</ns2:arborWOOBC_fCNAOBCResponse>
</soap:Body>
</soap:Envelope>
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Hello,
This issue is related to a data problem.
The error “73” is linked to the subscriberNumber. When we call the OMAPIServicesService API to retrieve the serialNumber associated with this subscriber, the request is rejected by their system.
The API response indicates that the fixed number provided is not valid (“Enter a valid fixed number”). As a result, the serial number cannot be retrieved, and the process fails at this step.
From our side, the call is correctly formed, but the data returned/validated by OMAPIServicesService is invalid.
Request payload :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:GetFixedInternetDetailsRequest xmlns:ns3="http://omantel.om/ordermanagementservice">
<OT_EAI_HEADER>
<RequestorId>NEP</RequestorId>
</OT_EAI_HEADER>
<Request>
<ReferenceNo>NEP_2004032427177980</ReferenceNo>
<externalId>44444048</externalId>
</Request>
</ns3:GetFixedInternetDetailsRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>"
Response Payload : INFO c.m.n.c.workflow.soap.SoapDelegate - JSON response >>> {
{ "RequestorId": "NEP" }"Body": {
"GetFixedInternetDetailsResponse": {
"OT_EAI_HEADER":
,
{ "ReferenceNo": "NEP_2004032427177980", "ReturnCode": "0752", "ReturnMessage": "Enter a valid fixed number" }"Response":
}
}
}