Release Notes

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) 61.

This document consists of the following sections:

See ASR Installation Guide for instructions about installing ASR 61.

Data Conversions

The ASR61BD.sql file is included in this release. The installer provides all upgrades to MetaSolv Solution executable files and stored procedure files (Procs directory).

Software Support

MetaSolv Solution 6.3.1 supports ASR 61 on the following software versions:

  • Oracle Enterprise Linux Server 6.6 (or later) and 7.1 (or later)

  • Red Hat Enterprise Linux Server 6.6 (or later) and 7.1 (or later)

  • Oracle Solaris 11.2 or later

  • IBM AIX 7.1 Update 1

  • HP-UX Itanium 11.31 Update 7

  • Windows Server 2012 R2 or Windows Server 2016

  • Oracle WebLogic Server 12c (12.2.1.3 and 12.2.1.4)

  • Oracle Database 12cR2 (12.2.0.1), 18c (18.3.0.0.0), and 19c (19.3.0.0.0)

Product Enhancements

ASR CORBA APIs Desupported

CORBA APIs are no longer supported from ASR 60. Oracle recommends that you use ASR Web Services to integrate ASR with other Oracle products or with external applications. See ASR Web Services Developer's Guide for more information about the ASR Web Services.

ASOG Issues Implemented

The following table describes the Access Service Ordering Guidelines (ASOG) issues that have been implemented in this release.

Issue Number Description

3639

Modify ASR (001) practice to revise RORD field based on changes made in ASOG 60 with Issue 3635.

3642

Update the UREF field (EVC-016) Usage Note2 to clarify Issue 3633 from ASOG 60.

Fixes in This Release

The following table lists the customer-reported bugs that have been fixed in this release.

Bug Number Description

30060858

Issue

When validating Access Service Request - Confirmation Notice (CN) window for an ASR order with request type ‘P’, validation messages are incorrectly displayed for REFNUM 0002 when the order contains only one virtual circuit. On clicking the validation message on REFNUM0002 gives internal server error.

Resolution

Code has been modified and now when validating a Confirmation Notice (CN) page for an ASR order with request type ‘P’, proper valid validation messages will be displayed for appropriate REFNUM values and clicking on it will take the control to the appropriate field.

31053438

Issue

On clicking validate in Access Service Request, found some validations listed in the order are not aligned with ASOG for below fields.
  • ADMIN: AFO, FDT, LANM, PSL, PSLI, RPON, WST
  • BILLING: FUSF
  • CONTACT: IMPCON
  • EVC: RL
  • PIP: ES, GCON, NC
  • TRANSPORT: BSC, CFAU, DIR, ETET, EXEMPT REASON, LMP, N/U, NVC, PSPEED, SDIR
  • SALI: JK CODE, OFC, SANO, SPOT

Resolution

Code has been modified and now proper ASOG validations will be listed on validating ASR order.

31450866

Issue

On clicking validate in Access Service Request, we get Internal Error: Unknown Rule Id for below fields:
  • Clarification Request: INIT.1, TEL_NO.1, SUPR.1, CRDD.1, RDET.1, RDET.2, RDET.3, ERROR_TAG.1, ERROR_MESSAGE.1
  • Translation Questionnaire: NPA_TECH_CON.1, NPA_TECH_CON.2, NPA_TECH_CON.3, NPA_TEL_NO.1
  • Virtual Connection: EP.1, REP.1

Resolution

Code has been modified and now proper validation message of corresponding fields will be displayed.

30792371

Issue

When starting the MSS Server, server displays in the log stating "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder", KM Article 2604685.1 helped to resolve the issue after which "Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1" warning is displayed.

Resolution

Code has been modified to set UTF-8 file encoding by default and no warning messages will be displayed on the log.

Note: Perform a new installation to resolve the reported issue.

31169206

Issue

In an Access Service Request order, when an existing EUL with multiple addresses is updated in the SALI form, the application does not update the address.

Resolution

Code has been modified and now when users try to update an EUL with multiple addresses in the SALI form, the application will successfully update the address.

Documentation Accessibility

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.

Access to Oracle Support

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.