Release Notes
Release 52.0
E69069-03
September 2016
This document describes the enhancements that are introduced and the Access Service Ordering Guidelines (ASOG) issues that have been implemented in Oracle Communications MetaSolv Solution Access Service Request (ASR) 52.
This document consists of the following sections:
See ASR Installation Guide for instructions about installing ASR 52.
The ASR52BD.sql file is included in this release. The installer provides all upgrades to MetaSolv Solution executable files and stored procedure files (Procs directory).
MetaSolv Solution 6.3.x supports ASR 52 on the following software versions:
Oracle Enterprise Linux Server 6.2 (or later) and 7 (or later)
Red Hat Enterprise Linux Server 6.2 (or later) and 7 (or later)
Oracle Solaris 10 1/13 and Solaris 11
Windows Server 2012 R2
Oracle WebLogic Server 12.1.3
Oracle Database 12c R1
JacORB 3.5
MetaSolv Solution 6.2.x supports ASR 52 on the following software versions:
Oracle Linux Server release 5.5 (Carthage)
Red Hat Enterprise Linux Server 5
Oracle Solaris 10 update 5/08 or higher (on a SPARC machine)
AIX 6.1 or higher (on a POWER6 machine)
HP-UX 11.23 or higher (on an Itanium machine. 32-bit and 64-bit JAVA supported)
Windows Server 2008 R2
Oracle WebLogic Server 10.3.1
Oracle Database 11g R2
JacORB 2.3.1
This section describes new enhancements in ASR 52.
ASR now supports updated operating systems and underlying software systems. See "Software Support" for more information.
Wireless Site Indicator (WSI-P) - PRILOC
Ethernet Virtual Connection (EVC) Form
Priority Bit Color Ingress (P-BITC-I)
Priority Bit Color Egress (P-BITC-E)
Multi-Chassis Link Aggregation Group ID (MCLAG-ID)
Switched Ethernet Services (SES) Form
Color Identifier (CI)
Multi-Chassis Link Aggregation Group (MCLAG)
Multi-Chassis Link Aggregation Group ID (MCLAG-ID)
Multi-Chassis Link Aggregation Group Protection (MCLAG-P)
The length of the Billing Account Number (BAN) field has been increased from 13 to 14.
The Wireless Site Indicator (WSI) field has been renamed to Wireless Site Indicator (WSI-S) - SECLOC and its existing definition has been modified.
The existing definition of the Early Date Acceptance (EDA) field has been modified.
The length of the Billing Account Number (BAN) field has been increased from 13 to 14.
Ethernet Virtual Connection (EVC) Form
The existing definition of the following fields has been modified:
Priority Bit (P-BIT)
Related UNI Identifier (RUID)
Multiple-Exchange Company (Multi-EC) Form
The length of the Billing Account Number (BAN) field has been increased from 13 to 14.
Service Address Location Information (SALI) Form
The length of the following fields has been increased from 15 to 18:
Access Telephone Number (ACTEL)
Alternate Access Telephone Number (AACTEL)
Alternate Local Contact Telephone Number (ALCON TEL)
Additional Alternate Local Contact Telephone Number (AALCON TEL)
Table 1 describes the Access Service Ordering Guidelines (ASOG) issues that have been implemented in this release.
| Issue Number | Description |
|---|---|
|
3519 |
The following changes have been made in the ADMIN form:
|
|
3529 |
The length of the Billing Account Number (BAN) field has been increased from 13 to 14 in the following forms:
|
|
3530 |
Implemented UI and API usage validation changes for the End User Indicator (EU) field in the ADMIN form. |
|
3531 |
The existing definition of the Early Date Acceptance (EDA) field has been modified in the ADMIN form. Added a new valid entry to the Response Type (RT) field in the CN form. Implemented UI and API usage validation changes for the Supplement Type (SUP) field in the ADMIN form. |
|
3532 |
Added a new valid entry to the General Exchange Tariff Options Code (GETO) field in the Transport form. |
|
3533 |
The length of the following fields has been increased from 15 to 18 in the SALI form:
|
|
3535 |
Added new Color Identifier (CI) field in the SES form. The following changes have been made in the EVC form:
|
|
3537 |
Implemented UI and API usage validation changes for the Service Virtual Local Area Network (S-VLAN) field in the EVC form. |
|
3539 |
Implemented UI and API usage validation changes for the New Construction (NCON) field in the SALI form. |
|
3540 |
Added the following new fields in the SES form:
Added new Multi-Chassis Link Aggregation Group ID (MCLAG-ID) field in the CN form. The existing definition of the Related UNI Identifier (RUID) field has been modified in the EVC form. Implemented UI and API usage validation changes for the Related UNI Identifier (RUID) field in the EVC form. |
Table 2 lists the customer-reported bugs that have been fixed in this release.
| BugDB Number | Description |
|---|---|
|
20854485 |
Issue When running the importEUSA ASR CORBA API, if the REFNUM field is not populated in the first SALI form, the API returns the following error: Field: [LMetaSolv.CORBA.WDI.WDIError; = Array (values following) [0] Field: code = 25151 [0] Field: reason = PON: XXX | FORM : SALI |:: REFNUM is required. [1] Field: code = 25164 [1] Field: reason = PON: XXX | FORM : 'ASR' |:: Please correct the above listed errors to initiate the OBF usage rules validation. Resolution Code has been corrected and now the importEUSA ASR CORBA API runs successfully by assigning the REFNUM value as 0001 when the REFNUM field is not populated in the first SALI form. |
|
17344449 |
Issue When opening the ACI circuit, the application intermittently returns the following error: An error has occurred in the script on this page. Line: 11 Char: 14 Error: 'document.all.buttonRepeat2' is null or not an object Resolution The code has been corrected and now the ACI form opens properly without any errors. |
|
17347555 |
Issue The end user location name is updated in the End User Location window when you modify the EUNAME field in the ASR SALI form despite the Update EUL name when the End User name is modified in the ASR SALI form preference being set to N. Resolution The code has been corrected and now the end user location name is not updated in the End User Location window when you modify the EUNAME field in the ASR SALI form with the Update EUL name when the End User name is modified in the ASR SALI form preference set to N. |
|
14490154 |
Issue When you enter a circuit ID (ECCKT) in the ECCKT field in the Admin form on an ASR Change/Disconnect order, the application allows you to enter canceled and disconnected circuits. This issue occurs in both GUI and API. Resolution The code has been corrected and now when you enter a circuit ID (ECCKT) in the ECCKT field in the Admin form on an ASR Change/Disconnect order, the application displays the following error message for canceled and disconnected circuits: Error: The circuit corresponding to the circuit ID provided in the ECCKT field should not be in a disconnected or canceled status. For API, the import of the ASR order fails and the application displays the same error message mentioned above for GUI. |
|
20548860 |
Issue When running the importCR ASR CORBA API, if the UREF and LREF fields are not populated and the REFNUM field is populated, the API returns the following error:
Field: [LMetaSolv.CORBA.WDI.WDIError; = Array (values following)
[0] Field: code = 25862
[0] Field: reason = PON: XXX | Form: UREF | VC Number: | Field: {3} | Value {4} |:: is invalid.
[1] Field: code = 25164
[1] Field: reason = PON: XXX | FORM : CR |:: The valid values are: 1-5 for LREF.
Resolution The code has been corrected and now the importCR ASR CORBA API runs successfully even when the UREF and LREF fields are not populated and the REFNUM field is populated. |
|
21316085 |
Issue The OBF validation rules are not triggered when the Routing Matrix field contains the following values in the ASR Translation Questionnaire (TQ) form: 1+5YY, 0+5YY, 0-L, 411, LPDA, and 0+L. Resolution The code has been corrected and now the OBF validation rules are triggered properly even if the Routing Matrix field contains the following values in the ASR TQ form: 1+5YY, 0+5YY, 0-L, 411, LPDA, and 0+L. |
This section describes the known problems in this release.
The Capture ASR Audit/Supplement History feature enables you to capture the audit and supplement history of ASR orders. Currently this feature does not support the capturing of audit history of certain data. Specifically, you cannot capture the audit history of the following:
Port Configuration form
Routing Matrix form
Routing Exception Matrix form
Translation Questionnaire Additional CIC information
Translation Questionnaire SAC NXX
Fields on the Circuit Identification window
User Data
Notes
Tasks
Links
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Communications MetaSolv Solution ASR Release Notes, Release 52.0
E69069-03
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.