Product Release Notes

These release notes are issued to inform the customer of any changes in the hardware and software implemented for the TransPath system, which may not be addressed in the published documentation.

1.2 Scope

This document covers any issues related to previous and current versions of the software and hardware.

1.3 Overview

This document consists of the following sections:

Section 1: "Introduction"

Section 2: "Critical Information - READ THIS FIRST" This section contains critical information to correct or supplement critical flaws or omissions in the documentation the failure to take note of which would cause critical damage or operational failure.

Section 3: "Functionality in the Documentation Not Implemented As Documented" This section addresses issues relating to discrepancies between the functionality of the delivered product and its description in the documentation.

Section 4: "Performance Anomalies" This section addresses performance issues that are not consistent with expected results.

Section 5: "Errata/Supplement to Published Documentation" This section documents errata in the Product Documentation, and may also contain substitution or supplemental pages.

2. Critical Information - READ THIS FIRST

2.1 All product CDs are Cataloged on Sun systems Running Solaris

Description: During the installation of transutil#1 subsequent transutil versions of a TransPath System product CD, on some Sun systems running the server version of the Solaris operating system, the operating system appears to be cataloging the CDs, by appending a number to the name of the CD.

Workaround: If this occurs on your system, for example if during the installation of theTransPath Utilities CD, instead of observing the transutil title, you may see transutil#1 instead. This is not a problem. Follow the installation instructions as usual, simply replacing the title name displayed.

2.2 Customer Responsibilities in Disk Space Management

Description: The TransPath system Installation Guide, as well as the Software Operations and Maintenance Guide provide guidelines for the minimum recommended disk space required for system operations. Should a customer elect to maintain more data on the system or perhaps change the log level, either of which will require additional disk space, the correct procedure is for the UNIX system administrator to use the Solaris disk management utilities to reconfigure the system to meet the expected disk usage requirements.

Workaround: Not Applicable.

2.3 Customer Responsibilities in Ensuring Validity and Accuracy

Description: The TransPath System is designed as a user configurable application with the greatest degree of flexibility. It is however, the customer's responsibility to ensure the validity and accuracy of configuration data in order that the TransPath System application will operate as desired. The system should be configured to meet specific customer configuration requirements in accordance with the guidelines specified in the Installation and Operations/Maintenance Guide(s), as appropriate. In particular, this applies to the circuits, timers, properties and other key elements being properly configured to meet the requirements of a given carrier's network.

Workaround: Not Applicable.

2.4 Use of DPNSS Test Frames and Channel Controller Log Level Changes

Description: The application currently provides support for DPNSS test frames being set to true or false, depending on whether the use of DPNSS test frames is required or not, as a parameter in the XECfgParm.dat configuration data file. In addition the I/O channel log utility allows the logging level to be modified on the channel controllers. Please refer to the Installation and Software Operations and Maintenance Guide(s) for a description of correct usage.

Workaround: Not Applicable.

2.5 TransPath Configuration Tool Usage in a Local Area Network (LAN)

Description: The TransPath Configuration Tool may be accessed either directly on the Windows NT platform or from another PC running Windows 95 located on the LAN. In order for access to be enabled from any device other than the Windows NT platform, the default.html file must be edited to include the fully qualified (for example, to include the domain) host name of the Windows NT platform.

Workaround: Not Applicable.

2.6 The Auxiliary Signaling Network (ASN)

Description: The establishment of the initial ASN communications link among TransPath system host computers may take up to 60 seconds per link (2 times the value discussed below) Feature Transparency calls attempted before links are established will not perform as expected. This timing is controlled by the Sun TCP bind parameter and is configurable. At this time it is not recommended to be set lower than 30000 (milliseconds or 30 seconds).

Workaround: Wait for the connection to be established on all links in a network, as verified through the opt/TransPath/var/log/Syslog.Platform, prior to making any feature transparency related calls.

2.7 The TransPath System provides no capability currently to add new services

Description: The TransPath System provides no capability currently to add new services (for example, additions to NES services .dat, new programs, additional MML sessions, and so on), should it be necessary while the application is running.

Workaround: None - The application must be shut down to add services, if needed. It is expected that this will occur during normal maintenance windows.

2.8 First Call may Abort after Idle Period (848).

Description: After a prolonged idle period, during which no calls are processed, the first call to arrive may be released (with a normal release cause identified).

Workaround: Contact the TAC if this is a problem for your network.