createOrderByValueRequest XML API Incorrectly Determines Telephone Number Type for a 'Pending Disconnect' Ported Out Telephone Number
Last updated on SEPTEMBER 26, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
***Checked for relevance on 26-Sep-2017***
While executing the createOrderByValueRequest XML API, when a 'Pending Disconnect' ported out telephone number (TN) is assigned to a Line, the type of the TN does not change to locally owned but instead remains as a ported out TN. The new suffix that is created should be a type of WTN.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms