Telephone Numbers In Not Recycled Which Are Disconnected From JMS Request
(Doc ID 2414981.1)
Last updated on JUNE 27, 2018
Applies to:Oracle Communications Unified Inventory Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Issue with TN transition SOAP over JMS request.
There is a problem where if a Telephone Number assigned to the Service is disconnected using the SOAP over JMS Capture Interaction request coming from Oracle OSM server, the Telephone Number gets disconnected. However the MSISDN is not getting transitioned to the Unassigned even after serving the Disconnect and Transitional Quarantine period. Where as the Telephone Number which is disconnected using the SOAP over HTTP Capture Interaction request coming from SOAP UI, the Telephone Number is released from Quarantine state after serving the Disconnected and Transitional period, successfully.
The servers are physically located in different timezone.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document