Page tree
Skip to end of metadata
Go to start of metadata

Click here to view a PDF version of this release notes document.
Table of Contents

About PSX Release Notes

This document provides information about PSX V09.01.09R000 Release.This release note describes new features, the latest hardware and software requirements, known limitations and other pertinent release information for the latest Insight PSX software release V09.01.09R000 on Solaris and Linux platform.

To view or download product documentation produced by Sonus Technical Publications, login to the online Documentation and Support portal.

First time visiting Documentation and Support portal, or forgot your password? Click here to activate your account or request a new password.

Release Notes Use and Distribution

These Release Notes are protected under the copyright laws of the United States of America. This work contains proprietary information of Sonus Networks, Inc., Westford, MA01886, USA. Use, disclosure, or reproduction in any form is strictly prohibited without prior authorization from Sonus Networks, Inc.

Problems or Questions

For problems or questions, contact the Sonus Technical Assistance Center (TAC) through telephone, fax, or e-mail:

Worldwide Voice: 1 (978) 614-8589
USA Toll-free: 1 (888) 391-3434
Worldwide Fax: 1 (978) 614-8609
Email: TechnicalPublications@sonusnet.com

 

Related Documentation

You can download the latest PDF version of PSX 9.1 documents from the content library of the Sonus Salesforce Customer Portal or Sonus Technical Publications Wiki at PSX Documentation.

The following PSX documentation is associated with this release.

Table : Related Documents

 PSX Related Document Title

Sonus Part Number

PSX 9.1 Tools Guide

550-05892

PSX 9.1 Alarm Troubleshooting Guide

550-05891

PSX 9.1 Policy Server Product Description

550-06161

PSX 9.1 Policy Server Provisioning Guide

550-06162

PSX 9.1 StandaloneMaster InstallationUpgradeGuide Solaris

550-05895

PSX 9.1 MasterwithSlaves InstallUpgradeGuide Solaris

550-05896

PSX 9.1 Slave Installation Upgrade Guide Solaris

550-05897

PSX 9.1 StandaloneMaster InstallationUpgradeGuide Linux

550-05898

PSX 9.1 MasterwithSlaves InstallUpgradeGuide Linux

550-05899

PSX 9.1 Slave Installation Upgrade Guide Linux

550-05900

PSX 9.1 Errata Document

550-05976

HP Quick Start Documentation

The HP ProLiant DL380p G8 Quick Start Guide provides details for purchasing, deploying, and installing the HP ProLiant DL380p G8. The HP ProLiant DL380p G8 Quick Start Guide also provides information on HP hardware procurement options, part-numbers, BIOS Settings, ILO Setup, NEBS conversion requirements, BIOS Settings, and HP firmware upgrade.
Ensure to refer the HP Quick Start Guide before purchasing HP G8 hardware.

About PSX

Sonus PSX provides centralized policy and call routing for both Sonus distributed Softswitch TDM - GSX and IP - SBC solution and third party products. When deployed in Service Provider network or Enterprises network, it interfaces with these call processing nodes while processing either TDM (SS7, PRA) or SIP calls. The centralized PSX is flexible enough to query various databases such as LDAP, ENUM, DNS, MSAD and so on, and also on-board database to provide the best routing based on the policies and configurations provided by network operators.

GETS Software

This release supports the High Probability of Completion (HPC) network capability intended to provide enhanced probability of call completion to authorized Government Emergency Telecommunication Service (GETS) and Wireless Priority Service (WPS) users during times of network stress and/or congestion. HPC features include GETS Call Routing, Office-Wide Call Queuing, and SIP Resource Priority Header.

The use of the GETS SOFTWARE is restricted in the U.S. and U.S. TERRITORIES to NS/EP users authorized by the Office of the Manager, National Communications System (OMNCS). Telecommunications deployment of GETS SOFTWARE must be coordinated with the OMNCS at the following address:
Office of the Manager
National Communications System
Attn: GETS Program Office
701 South Courthouse Rd.
Arlington, VA 22204-2198
Email: gets@ncs.gov

Hardware and Software Requirements

Scripting Support–Optional Sonus SPE Software

The Sonus Service Profile Editor (SPE) Version 06.03.05 Build 12 is an optional, additional software purchase that can be used to develop custom application scripts and customize copies of the seeded processing scripts for the PSX V09.01.09R000 Release. SPE documentation is available separately with the optional software; the following SPE documentation is associated with this release:

Table : Service Profile Editor

PSX Related SPE Document Title

Sonus Part Number

SPE 6.3.5 User Guide

550-01243

SPE 6.3.5 Release Notes

550-02178

Customer-Provided Equipment

The customer is required to provide appropriate networking equipment and infrastructure other than that purchased from Sonus.

PSX Installation and Upgrade Notes

This section provides additional upgrade notes required for upgrading to the latest 9.1.XX patch release. For detailed information on PSX installation and upgrade procedures, refer PSX 09.01.00R000 Installation and Upgrade Guides.

Upgrading from PSX 09.01.XX to Latest 09.01.XX Patch Release

This section provides additional information on upgrading from any PSX 09.01.XX releases to the latest 9.1.XX patch release.

  1. Download the following files from the Sonus Salesforce Customer Portal:
    • For Solaris
      PSX.V09.01.09R000.tar.z
      psxBootStrap-V09.01.09R000.tar

    • For Linux
      PSX.V09.01.09R000_RHEL.tgz
      psxBootStrap-V09.01.09R000_RHEL.tar

  2. Perform the upgrade procedures in the chapter on "Upgrading PSX using Salesforce Portal" in the PSX 09.01.00R000 Installation and Upgrade Guides.

The following procedures in the PSX 09.01.00R000 Installation and Upgrade Guides are not required if you are upgrading from PSX 09.01.XX to the latest 09.01.XX patch release:

  • Upgrading Platform or OS
  • Database Software Upgrade
  • Upgrading Firmware

Upgrading from Releases Prior to PSX 09.01.00R000

This section provides additional information on upgrading from any release prior to PSX 09.01.00R000 release to the latest 9.1.XX patch release.
Download the following files from the Sonus Salesforce Customer Portal:

  • For Solaris
    PSX.V09.01.09R000.tar.z
    psxBootStrap-V09.01.09R000.tar
    Solaris_Utilities_<current_release>.tar
    Sonus_OS_delta_9.1_Upgrade.tar.gz
    SONUS-DB11.2.0.3-SOLARIS-SW-R3.tar

  • For Linux
    PSX.V09.01.09R000_RHEL.tgz
    psxBootStrap-V09.01.09R000_RHEL.tar
    psx_patch-V09.00.00R001-RHEL_06.01.02.01R000.x86_64.rpm
    psx_patch-V09.01.00R001-RHEL_06.01.03.00R001.x86_64.rpm
    SONUS-DB11.2.0.3-LINUXSW-R3.zip
    PLTF-6.1.2.2-Firmware.tgz

Upgrade Recommendation

SIP Over SCTP Service is Enabled

PSX SIP over SCTP service is now enabled during upgrade migration.

Restoring DNS/ENUM Configuration after Upgrade

During a PSX upgrade, the lwresd.conf file (containing the customer's current LWRESD configuration) is automatically backed up to /export/home/ssuser/OLD_SS_CONF_FILES.
Once these values are preserved, the PSX upgrade process replaces the lwresd.conf file with a template lwresd.conf file containing default configuration parameters. Following the upgrade, edit this template file and change the default configuration settings to the LWRESD configuration settings from the backed up file.
If the backed up file has the fields "retransmit-timer" and "max-retransmit-timer", then they should be removed before starting the softswitch. These two fields "retransmit-timer" and "max-retransmit-timer" were introduced as part of SONUS00127087 and LCQ 6801 to enable user to configure minimum and maximum time LWRESD process waits for DNS-ENUM responses. They are available only in PSX 7.3.6 and PSX 7.3.7 and are not ported to PSX 08.04.01R000. PCRs 4112 and 4115 which provide significant enhancements to DNS-ENUM functionality are available in PSX 8.4.1 and customer should use these new PCRs instead.

Enabling Link Trap Generation

The Solaris 10 SNMP MIB II agent does not support link up/ link down notifications. To enable your system to send these notifications, run the LinkTrapGen.sh script to enable and configure mibiisa to work with your system. Download the script from WL9.0 Software Bundle available in the Sonus SalesForce Customer Portal.

  1. Log in as Root and execute the script as follows:

    sh LinkTrapGen.sh

    The script creates a backup copy of the /etc/snmp/conf/snmpdx.acl file that it modifies. It also restarts the Solaris SMA SNMP master agent.

PSX Upgrade Paths

LDM upgrade from any PSX F-version to PSX 09.01.09R000 is not supported unless explicitly mentioned in the document.

Upgrade Path for PSX on Solaris

This section provides information on the supported upgrade paths to PSX 09.01.09R000 on Solaris:

The highlighted upgrade paths are explicitly tested by Sonus.

Table : Upgrade Path on Solaris

 Release

Series

Upgrade Paths

V09.01

R

V09.01.00R000, V09.01.01R000, V09.01.02R000, V09.01.03R000, V09.01.04R000, V09.01.05R001, V09.01.06R000, V09.01.07R000, 09.01.08R000

V09.00

R

V09.00.00R000, V09.00.01R000, V09.00.02R000, V09.00.02R003, V09.00.03R000, V09.00.04R000, V09.00.06R000, V09.00.07R000, V09.00.08R000, V09.00.09R000, V09.00.10R000

V08.04

R

V08.04.00R000, V08.04.01R000, V08.04.02R000, V08.04.03R000, V08.04.04R000, V08.04.07R000, V08.04.07R001, V08.04.08R000, V08.04.09R000, V08.04.10R000, V08.04.11R000, V08.04.12R000, V08.04.13R001, V08.04.14R000

V08.03

R

V08.03.00R000, V08.03.01R000, V08.03.02R000, V08.03.03R000

V07.03

R

V07.03.00R000
V07.03.01R000, V07.03.01R001, V07.03.01R002, V07.03.01R003, V07.03.01R004, V07.03.01R005, V07.03.01R006, V07.03.01R007, V07.03.01R008
V07.03.02R000, V07.03.02R001, V07.03.02R002, V07.03.02R003, V07.03.02R004, V07.03.02R005, V07.03.02R006, V07.03.02R007
V07.03.03R000, V07.03.03R001, V07.03.03R002, V07.03.03R003, V07.03.03R004, V07.03.03R005
V07.03.04R000, V07.03.04R001, V07.03.04R002, V07.03.04R003, V07.03.04R004, V07.03.04R005, V07.03.01R006, V07.03.01R007, V07.03.01R008, V07.03.01R009, V07.03.01R010
V07.03.05R000, V07.03.05R001, V07.03.05R002, V07.03.05R003, V07.03.05R004, V07.03.05R005
V07.03.06R000, V07.03.06R001, V07.03.06R002, V07.03.06R003, V07.03.06R004, V07.03.06R005
V07.03.07R000, V07.03.07R001, V07.03.07R002, V07.03.07R003, V07.03.07R004, V07.03.07R005, V07.03.07R006, V07.03.07R007, V07.03.07R008, V07.03.07R009

V07.02

R

V07.02.00R001
V07.02.01R001
V07.02.02R000, V07.02.02R001, V07.02.02R002
V07.02.03R000, V07.02.03R001
V07.02.04R000, V07.02.04R001, V07.02.04R002, V07.02.04R003, V07.02.04R004
V07.02.05R000
V07.02.06R000
V07.02.07R000
V07.02.08R000
V07.02.09R000

V07.01

R

V07.01.00R001, V07.01.01R000
V07.01.02R000, V07.01.02R001
V07.01.03R000
V07.01.04R000
V07.01.05R000, V07.01.05R001
V07.01.06R000
V07.01.07R000
V07.01.08R000

Upgrade Path for PSX on Linux

This section provides information on the supported upgrade paths to PSX 09.01.09R000 on Linux:

The highlighted upgrade paths are explicitly tested by Sonus.

Table : Upgrade Path on Linux


 Release

Series

Upgrade Paths

V09.01

R

V09.01.00R000, V09.01.01R000, V09.01.02R000, V09.01.03R000, V09.01.04R000, V09.01.05R001, V09.01.06R000, V09.01.07R000, 09.01.08R000

V09.00

R

V09.00.00R000, V09.00.01R000, V09.00.02R000, V09.00.02R003, V09.00.03R000, V09.00.04R000, V09.00.06R000, V09.00.07R000, V09.00.08R000, V09.00.09R000, V09.00.10R000

V08.04

R

V08.04.07R000, V08.04.07R001, V08.04.08R000, V08.04.09R000, V08.04.10R000, V08.04.11R000, V08.04.12R000, V08.04.13R001, V08.04.14R000

Migrating PSX Database from Solaris to Linux

All upgrade paths listed in the section Upgrade Path for PSX on Solaris are supported for Migrating from PSX Solaris to PSX Linux.
For information on procedure to migrate PSX Solaris to PSX Linux, refer the following documents:

  • 550-05898_PSX_9.1_StandaloneMaster_InstallUpgradeGuide_Linux_1
  • 550-05899_PSX_9.1_MasterwithSlaves_InstallUpgradeGuide_Linux_1
  • 550-05900_PSX_9.1_Slave_Installation_Upgrade_Guide_Linux_1


PSX Interoperability Matrix

To view the minimum compatible release versions of each Sonus device that can interoperate with PSX, see PSX Interoperability Matrix.

For complete interoperability details between the various Sonus products, including backwards compatibility, see Ribbon Product Compatibilities.

ePSX Interoperability with SBC

Table : ePSX Interoperability with SBC

 File Name

SBC version

ePSX-V09.01.08R000.ova

SBC 5000 series (except 5100) and SBC 7000 series

  • ePSX installation is not supported on SBC 5100 and SBC SWe.
  • The ePSX installation package is available in the standard SBC software bundle posted on Salesforce.

 

New Features and Modifications

This section provides an overview of new features and enhancements included in PSX 09.01.xx releases.

New Features in PSX V09.01.09R000

PSX-18584: Equal Access Call Routing

The Call Parameter Filter Profile screen has been enhanced to route the call to the equal access carrier when a number defined in Destination with Called Forced Routing is enabled and the route label is defined. This enhancement enables the Destination screen to give routes to some access carriers.

"Carrier Type" is added to Call Parameter Filter Data - Type dropdown.

Figure : Equal Access Call Routing

PSX-19916 PSX Enhancement of ssreqCLI Tool

PSX is enhanced to send policy request to SSReq using CLI. The ssreqCLI is the command line version of the SSREQ GUI tool. The ssreqCLI command sends a policy request to SSREQ server and receive call trace data. Also, ssreqCLI tool allows you to save the Policy Request, Policy Response and Call trace in an output file.

ssreqCLI includes the following arguments:

  • G = Gateway
  • O = Output file name
  • N = Called Number
  • T = Trunkgroup
  • I = PSX IP                 
  • M = Calling Number
  • F = Input configuration file
  • C = ConfigFileName for running in batch mode

Gateway, TrunkGroup and Called Number are the mandatory arguments.

The ssreq tool must be run from the following path:

/export/home/ssuser/SOFTSWITCH/BIN

The syntax for the input passed in command line:

ssreqCLI -G <GatewayName> -O <outputFileName>> -N <CalledNumber> -I <PSX IP> -M <CallingNumber>

Example:

ssreqCLI -G SBTM_JTI_IN_GW1 -O 456.xml -N 9783301234 -TSBTM_JTI_IN_1 -I 10.54.2.198 -M 7411036676

 

Instead of output file name, if output is required at "stdout" then pass the argument as following example:

ssreqCLI -G SBTM_JTI_IN_GW1 -O /dev/stdout -N 9783301234 -T SBTM_JTI_IN_1 -I 10.54.2.198 -M 7411036676

 

To use an input xml file instead of command line arguments as input, use the following syntax:

ssreqCLI -F <InputFileName>

Example:

ssreqCLI -F default.xml

By default the traces are displayed on the screen. To save the traces to a file, use the following syntax:

ssreqCLI -F <InputFileName> -O <outputFileName>

PSX-19995 Blocking Profile Not Working When Calling Party is Treated as Username

PSX is enhanced to execute the blocking profile logic successfully when the calling number is a SIP URI with username. To accomplish this, PSX uses the ingress Trunk Group Country Code as the Calling Party country code.

Prior to this enhancement, the username of the SIP URI was not determining the calling party’s country code. Consequently, the blocking profile configured for a called party number failed to work as intended and the calls were allowed to pass through.

A new flag Use Trunk Group Country For Blocking Profile is added in the Feature Control Profile to support this enhancement.

If the calling party number is a SIP URI with username, and if this flag is selected, the Calling party’s country code is populated with the ingress Trunk Group country code. PSX uses the determined country code to execute the blocking profile logic. Once PSX executes the blocking profile logic, the Calling Party Country code is reset, and rest of the PSX processing is performed without the Calling Party.

Figure : Feature Control Profile

New Features in PSX V09.01.08R000

PSX-19310: Configurable LCR Disconnect Treatment

PSX is enhanced to configure the release cause code returned when Least Cost Routing (LCR) fails to find routes that meet the specified criteria. To see a release cause code other than the default NO_ROUTES_FOUND script, you can create a new Service Profile Editor (SPE) script with the required cause code and link it to the corresponding entity.
Currently, when the LCR does not return any routes, by default the NO_ROUTES_FOUND script is returned.
A new Call Processing Element Type "LCR Customer" is added in Element Script screen. You can choose this CPE type to configure a script name specific to an LCR Customer entity. When this CPE type is selected LCR Customer dropdown appears which lists all available LCR customer entities. This enables you to choose a customer profile to which this script needs to be linked.

Figure : Configurable LCR Disconnect Treatment

PSX-19694: Generic Digits Interworking for DMS Switch

This enhancement allows Parameter Manipulation of DM/PM Rule Entity to support "Spare 09" digit type and Binary Short (DMS) encoding type.
The enhanced DM/PM rule enables PSX to copy the contractor number to generic digits in DMS format which is further sent back to GSX.
The following enhancements have been made in DM/PM Rule screen:

  • New parameter "Spare 09" included in Type dropdown available under Generic Digits.
  • New parameter "Binary Short (DMS)" included in Encoding dropdown available under Generic Digits.

Figure : Configurable LCR Disconnect Treatment

New Features in PSX V09.01.07R000

PSX-18716 - JIP Parameter use for IN 800 Queries

Currently customers that are carrying 8xx traffic are not doing the SMS dip using the JIP information and are therefore routing mobile originated calls to the LATA of their ANI and not to the LATA of the JIP field, which tells the network what switch is currently originating the mobile call.
This enhancement provides the ability to dip the 800 SMS database correctly and respond with the jurisdictionally correct CIC and LATA of origin. This would also allow the ingress trunk group DM rules to replace the Charge number with the JIP number which gets the correct IN response from the SMS 800 database and route the calls correctly.
This enhancement also enables the use of JIP parameter value as digit source in DM/PM rule so that the JIP digits can replace any digit fields such as calling, or charge, or billing TN.

New Features in PSX V09.01.06R000

SBX-2283 EVRC and EVRCB Transcoding

MaxInterleaveDepth parameter support is introduced to all EVRC and EVRCB codec entry calls. This parameter holds the range values between 0-7.
This parameter will be visible only for the EVRC and EVRCB codec entries with packet size of 40 or 60. By default, this parameter holds the value 0.
For more information on EVRC and EVRCB Transcoding, refer New Features section in SBC 04.01.04R000 Release Notes.

Figure : EVRC and EVRCB Transcoding

New Features in PSX V09.01.05R001

PSX-17268 - Support of IBM V3700 RAID

The IBM Storwize V3700 RAID support is introduced in this PSX release. IBM 3700 can be configured using CLI.
IBM V3700 is designed with two controllers with two ports each. Both the controllers have a dedicated service IP on the first port and are connected to two switches. These switches connect with the active and standby PSX through eth7 interface.
The following table shows the hardware and software specifications of the IBM Storwize V3700 RAID:

Component

Specification (Standard Sonus Configuration)

Host Interface

Two U modular disk system.
6 Gbps SAS and 1 Gbps iSCSI host interface with optional 8 Gbps Fibre Channel.
10 Gbps iSCSI/Fibre Channel over Ethernet host ports or additional 6 Gbps SAS.
1 Gbps iSCSI host ports.

Disk Drives

Five 300GB 15K 2.5-inch HDD

Slots

Installed in slots 1-5

RAID Level

RAID-10

Power Supply

Two hot-swap DC/AC power supplies

Controllers

Dual hot-swap controllers, and 2GB battery protected cache per controller


For more information on firmware upgrade, refer IBM Storwize V3700 Firmware Upgrade Quick Start.
For more information on configuring PSX with IBM Storwize V3700 RAID, refer PSX Support for IBM Storwize V3700 RAID-Method Of Procedure (550-06315).

New Features in PSX V09.01.05R000

This version is not used.

New Features in PSX V09.01.04R000

There were no new features added in this release.

New Features in PSX V09.01.03R000

PSX-2583 Onboard LNP (Hosted LNP) Database Design inconsistency

Onboard LNP solution is deployed at a couple of customers' networks. The primary keys that the PSX is using for the HOSTED_LNP table are not in sync with Neustar's primary keys. Neustar expects vendors to use "Region ID" and "TN" as the keys. Update transactions are failing for them because of this issue. The PSX database is losing sync with the Neustar database and calls are routed to incorrect LRNs.
As part of this feature PSX will use National ID, Country ID, Region ID, and LNP Data Type as primary key to HOSTED_LNP table. A new column named TRANSACTION_ID is added for debugging purpose. The Transaction ID can go up to 38 digits long, so it will be defined as a character string.
GUI Changes:

  • The National and Country are part of the primary key.
  • A new text box named Transaction ID is added. It displays information in the TRANSACTION_ID column.

For more information, see 550-06161_PSX_9 1 3_Provisioning_Guide_1.
Note: If customer is using Hosted LNP feature and upgrading from releases prior to 9.0.6R000 or prior to 9.1.3R000 to PSX 9.1.3R000 or higher 9.1.x release, then only Standard Upgrade is supported. LDM upgrade is not supported.
Additionally, the primary key for the Hosted LNP table has changed. Hence, the customer needs to stop provisioning BDD until Master and Slave are upgraded and then reload BDD. If customer has already downloaded a new BDD as part of upgrade to PSX 9.0.6R000 or higher 9.0.x or 9.1.3R000 or higher 9.1.x release then a new BDD is not needed on this 9.1.x release.

SBX-1908 Support for a new version of T.38 Protocol

PSX is enhanced to support a new version of T.38 protocol to configure and treat fax calls. T.38 protocol Version 3 has support for V.34 fax relay.
To support this functionality, a flag T.38FaxProtocolVersion is introduced in the Packet Service Profile Screen.
For more information, see 550-06161_PSX_9 1 3_Provisioning_Guide_1.

SBX-280 Support for OPUS Codec 

PSX is enhanced to support an open standard audio codec, Opus. Opus is an HD codec that is designed for a wide range of applications for speech and music, in mono or stereo mode. This codec operates at a sampling rate ranging from 8-48 kHz and generates a bit stream from 6-510 kilobits/s.
For more information, see 550-06161_PSX_9 1 3_Provisioning_Guide_1.

SBX-24340 SIP Connect certification Gaps

PSX is enhanced to support a new configuration flag under IPSP, which confirms whether the PSX route must be used for routing the INVITE message or not. It must be possible to configure a flag at IPSP to control the anonymisation of FROM header when Calling Line Identification Restriction is enabled. When this flag is enabled, FROM header must be sent without anonymisation.
For more information, see 550-06161_PSX_9 1 3_Provisioning_Guide_1.

SBX-3081 Min-SE header added depending on the previous offer/answer

PSX is enhanced to support a new configuration flag in IP Signaling Profile.
SBC5xxx adds Min-SE header to every re-INVITE/UPDATE SIP message. A new flag Suppress Min-SE if not received is introduced under Common IP Attributes flags that allows SBC to optionally suppress adding Min-SE header in re-INVITEs/UPDATEs whenever Min-SE header does not exist in the previous offer/answer.
When this flag is enabled, Min-SE is added to the RE-INVITE/UPDATE only if exists in the previous Offer/answer.
For more information, see 550-06161_PSX_9 1 3_Provisioning_Guide_1.

SBX-2996 RFC 6337 Support

PSX is enhanced to support a new configuration flag in IP Signaling Profile.
When acts as an UAC, SBX5k fails to ignore SDP on 200 OK (INVITE) if the original offer had already been answered by an earlier 1xx-rel with SDP. To address this behavior, a flag Ignore SDP After Offer Answer Completed in 100Rel with SDP is introduced under IPSP Egress Attributes.
When this flag is enabled, SBC ignores the new SDP at egress leg in subsequent 1xx-rel or final 200 OK after Offer Answer for the initial Invite dialog have been completed and would not trigger a new offer or answer.
For more information, see 550-06161_PSX_9 1 3_Provisioning_Guide_1.

PSX-2856 Allow installing ePSX Slave when PSX Master is on a Lower Version

This enhancement allows the ePSX slave running higher PSX version to replicate with the PSX Master running a lower PSX version.
To accomplish this, before installing the ePSX slave, download the new psxBootStrap-<version>.tar file from Salesforce, untar the file and copy the files to PSX master. Then run the ldmMasterInit.pl script.
For more information on the procedure, you can refer to the following link in SBC documentation.
https://support.sonus.net/display/SBXDOC41/Allowing+a+Replica+ePSX+Installed+with+a+Higher+Version+than+the+Master+PSX

New Features in PSX V09.01.02R000

The following new features are added in PSX V09.01.02R000 release:

PSX to Transparently Pass ISUP Parameters

PSX has extended the support to transparently pass OLI and JIP parameters in the SIP Invite messages received over the D+ interface and send to external SIP SCP. This enhancement in the SIP-SCP communication process enables the capabilities of Pulse LCR routing server.
The call processing logic is enhanced to process the JIP parameter received in the D+ message from GSX. The JIP Parameters in an outgoing SIP Invite message in PAI/From header using RN parameter is sent to an external SIP SCP. This normalizes JIP in PAI header by default and always sends the SIP-SCP out to external SIP SCP. This functionality is activated by enabling the flag Send JIP To SIP SCP under SIP SCP Device screen.
Additionally, OLI parameter is passed in the From header of the SIP Invite and JIP in PAI header using the RN parameter. This functionality is activated by enabling the flag Send JIP In From Header To SIP SCP and OLIP To SIP SCP under SIP SCP Device screen.
Following new fields are added in SIP SCP Device screen to support this feature:

  • Send JIP To SIP SCP--When this check-box is selected, PSX determines if JIP is sent to LCR. By default, the flag is disabled.
  • Send Globalized JIP TO SIP SCP--When this check-box is selected, PSX sends the JIP in globalized format. . By default, the flag is disabled.
  • Send JIP In From Header To IP SCP--When this check-box is selected, PSX determines if JIP is sent in From Header. If this check-box is not selected, JIP is sent in PAI Header. By default, the flag is disabled.
  • Send OLIP To SIP SCP--When this check-box is selected, PSX determines if OLIP is sent to LCR. By default, the flag is disabled.


Following image highlights the new option added to SIP SCP Device Screen:

Figure : New Option in SIP SCP Device Screen

Configure DNS Query retry timer

PSX DNS query functionality has been enhanced as a part of this PCR. DNS query retry timer which was previously hard coded to 4 seconds has been made configurable.
Following new field has been added to DNS Zone Screen to support this feature:

  • Query Retry Timer (ms)--Specifies the Query Retry Timer for DNS Zone in milliseconds. This is the duration for which SLWRESD process in PSX waits for the response from DNS server before retrying the same query to a next server configured in forwarders list. If this timer is not configured or is not set to 0, SLWRESD assumes a default value of 4 seconds to maintain backward compatibility.

This timer is applicable for all types of queries (ENUM NAPTR, DNS NAPTR, SRV, A/AAAA) from PSX towards a DNS server.
Following image highlights the new option added to DNS Zone Screen:

Figure : Configure DNS Query Retry Timer


DNS-ENUM Request Timeout (ms) is an existing timer configuration in DNS-ENUM Service Definition. PES starts this timer when a DNS or an ENUM translation service is triggered. SLWRESD is a process that reaches out to external DNS servers and responds back to PES.
If this timer expires before receiving any response from SLWRESD, then the call is treated as timed out and default treatment procedures are applied.
While configuring Query Retry Timer and DNS-ENUM Request Timeout, always consider that 90% of DNS-ENUM Request Timeout time is available for trying the DNS servers and remaining 10% of that for overhead for some internal processing(in DNS-ENUM service definition). The examples below explain this.
Following are the examples on how to configure Query Retry Timer(ms) and DNS-ENUM Request Timeout (ms):
Example 1
This example illustrates a scenario, when there are four DNS servers configured for a zone and all are not reachable (worst scenario). If PSX is configured to perform an ENUM AoR query and the DNS-ENUM Request Timeout is configured as 2500 milliseconds, then the Query Retry Timer can be configured as 560 milliseconds approximately ( 90% of 2500 = 2250/4 = 562 ~= 560).
In this case, 250 milliseconds (2500-2250) is the extra time for overhead in internal processing.
Example 2
If an ENUM AoR query is performed and the maximum time to wait for each DNS server is known to be 800 milliseconds and if there are two such servers, then query must be successful within 1600 milliseconds.
Therefore, Query Retry Timer can be configured as 800 milliseconds and the DNS-ENUM Request Timeout (timer on PES timer) can be configured as 1800 milliseconds approximately (1600+10% = 1760).
When DNS NAPTR service is performed from PES, it usually requires further SRV and A/AAAA lookups towards the DNS servers. Therefore, the configured timeout in DNS-ENUM service definition must accommodate all three types of queries (NAPTR, SRV followed by A/AAAA).
Example 3
When there are two DNS servers and only the second server is functional, say each server usually takes 500 milliseconds. If DNS NAPTR service is performed, then query retry timer can be configured as 500 milliseconds and DNS-ENUM service timeout can be configured as 3300 milliseconds approximately (2*500 *3 = 3000 +10%).

New Features in PSX V09.01.01R000

The following modifications are done in PSX V09.01.01R000 release

Support for 16 Kbps packet coding rate as an option for g7221 and g7221s codec

PSX Codec Entry entity is enhanced to configure 16 kbps as coding rate for the following audio encoding codec: g7221s and g7221

LWRESD Support Additional ENUM Formats

PSX LWRESD is enhanced to support additional ENUM NAPTR response formats along with E2U+sip (per RFC) and E2U+SIP.

  1. sip+E2U
  2. SIP+E2U

Disabling Call Tracing during High Load

PSX is enhanced to dynamically disable call tracing under high load. During high call load, if a large percentage of calls landing on PSX have call trace enabled, it triggers a situation where Call Processing is impaired. CPU and memory resources on the PSX do not have any impact on call processing. Call processing is affected due to excessive call tracing that occurs due to abnormal thread usage and resource contention. To address this behavior, PSX disables call tracing dynamically in the described situation. PSX also generates a trap to indicate that call tracing has been disabled.
Call tracing can be restored or reset back by using the following options provided in ssmgmt tool

  1. Run ssmgmt tool
  2. Choose Option 14 (Logging Management Menu)
  3. Choose option 8 (Set Call Trace Mode Normal)

Following alarm is added as a part of this feature:

  • sonusSoftSwitchPesCallTracingDisabledNotification

The table below describes the alarm:

Table : Alarm Description


 Type

Informational

Definition

Call tracing is disabled. This trap is generated when large percentage of calls landing on PSX during high call load have call trace enabled leading to situation where Call Processing is impaired.                             

Impact

Call tracing is disabled.

Action

None

Clearing

Manual

Repetition

None

Instance Fields

None

Event Codes

None

Flag to INCLUDE or EXCLUDE Country for ENUM Dips

PSX is made flexible to format the ENUM query string as either 11 digits (E.164 format currently supported by PSX) or 10 digits number.
Currently, PSX formats the ENUM query string as E.164 number (country code + number) before sending out the ENUM query. A flag Do Not Use Country Code is added in DNS ENUM Service Definition screen. When this flag is enabled, Enum query is sent only with national number excluding the country code.

BRX License successfully applies on PSX

BRX license can now be successfully applied on PSX. Previously, BRX license failed to apply on PSX due to failure in feature configuration.

Unified ISO Image for ePSX

Previously, two OVA packages were released since the virtual disk images for 5110 and 52XX have different size requirements of 40GB and 60GB. Therefore, each disk image was packaged in a different OVA package. The enhancement is made to release a single OVA package with the single disk image. Using certain scripts, you can determine the platform on which package has to be installed and then you can run the commands to extend the disk partitions to the necessary size. Disk size for 5110, 52XX, and Bluefin are 40GB, 60GB and 100GB respectively.

Multiple SIP Trunk Groups in DefaultSigZone

PSX supports SIP signaling for inter-SBC5x00 communication to co-exist with Sonus GW-GW signaling. Currently, to use SIP in Sonus core, Use SIP In core flag can be enabled in the following IP Signaling Profiles:

  • Ingress IPSP of the Ingress Peer/IPTG
  • Egress IPSP of the Egress Peer/IPTG

In defaultSigZone, an INVITE can either come from a SIP Server or a Gateway. Therefore to differentiate these requests, the following condition is added to determine if SIP is to be used in Sonus core:

  • Enable Use SIP In Core flag in the IP Signaling Profile that are associated with Inter/intra Signaling Gateway Group.

New Features in PSX V09.01.00R000

For information on the new features in PSX V09.01.00R000 release, refer 550-05894_PSX_9.1_Release_Notes_Linux_1 and 550-05893_PSX_9.1_Release_Notes_Solaris_1 respectively.

End of Life Features

There are no features deprecated in PSX V09.01.09R000 release.
The following features have been deprecated and are not supported from V08.00.01R000 onwards:

  • PSX Support for Third-Party Application Servers via XML over TCP (SPAS Protocol)
  • PSX support for H.323 CDRs

The following hardware is not supported from V09.01.07R000:

  • Support of Sun Netra 240 and 440

Release 09.01.00R000 is the last release to support Light Weight Resolver Daemon (LWRESD), from the next release PSX supports only SLWRESD (Sonus LWRESD).

 

Resolved Issues

Resolved Issues in PSX V09.01.09R000

This section lists resolved issues in PSX release V09.01.09R000.

Table : Resolved Issues

Issue IDSeverityPlatform (Solaris/Platform)CategoryProblem DescriptionResolution
PSX-204541BothSIPESIPE Proxy coredumps on receiving an INVITE 94 or more headers due to memory corruption.The initial memory size and dynamic memory allocation routine has been modified to handle messages with large number of headers.
Additionally if an INVITE is received with more than the maximum number of headers supported, then SIPE proxy returns a 400 Bad Request.
Note:The maximum number of headers supported for Solaris is 96 and Linux is 62.
PSX-184772LinuxCall ProcessingTime Range Profile matching does not work on Lintel platform for timezones other than GMT or PSX Local.On linux platform when timezone was set to other than GMT or PSX Local, PES was not matching time range profile.
The local timezone was not getting set correctly in the environment variables before PES gets local time.
The fix calls the right utility to set timezone in environment variable before calling the function for getting local time.
PSX-192842BothDatabaseData not replicating on new master and slave setup, when using DB backup that has some unassigned SQL ID.Populate sql_ids is not indeed performed right after RMAN restore and recover of the database. Fix ensures that RMANRestore waits for some time before populating SQL IDs.
PSX-193082BothDatabaseRAID is not umount properly during HA Master failover.
This was due to RAID being unmounted from /export/raid directory or some process accessing the RAID mount while unmounting.
This fix checks if RAID is being unmounted from /export/raid directory or some process is accessing /export/raid while unmounting and returns an error message. The unmount will proceed only if /export/raid is not being accessed.
PSX-194932BothProvisioningIn PSX pipe command -a option is missing.
In pipe startup command, if “-a” is the first or last of all options, the pipe process coredumps continuously.
The code has been modified to address this issue.
PSX-196832BothProvisioningA Number Translation entry gets created even if an invalid Country name is passed in Number Translation table.Fix ensures that before creating Number_Translation entry with a country_id, a constraint is added to check if the Country Id is valid or not.
PSX-198982BothDatabaseWhen the hostname on master PSX is changed and
UpdateDb is run, the UpdateDB listener status still shows
the old hostname.
The issue is fixed by setting the db_domain parameter correctly.
PSX-199122BothCall ProcessingPES core during security scan.An uninitialized ENUME structure causes PES core when running a security scan that sent random requests to port 4100 (port on which PES listens for ENUME requests).
Fix ensures that the structure is initialized before use.
PSX-199242BothProvisioningHaving 2000 Routing Label routes per Routing Label was causing pipe to core dump in Lintel platform.The pipe internal data structures can hold only a maximum of 200 Routing Label Routes per Routing Label. Beyond this memory was being corrupted causing core dump.

A check is added in the pipe code to prevent users from creating more than 200 Routing Label Routes per Routing Label.
PSX-199342BothReplicationdbrepd process leaking memory.
While testing with a port scan software, it sent a very large message to dbrepd port. The large message resulted in memory leak.
Added a size limit of 10MB to the request message. All messages bigger than 10MB is rejected.
PSX-199732BothCall Processing INAPSCPA INAP has a Tssf Short Timer of 10 sec to wait for IDP response. When response is delayed for about 10 seconds there is a chance that the timeout handler thread and response processing thread trigger at same time. If this happens SCPA may go into a deadlock.
Response thread is holding on to a stack lock on the dialog and waiting on the application lock on the dialog. Timer thread is holding on to the application dialog lock (which it acquires to send notification to PES) and waiting on stack lock. The threads are never able to come out of this
situation due to locking order.
This fix ensures that the locking order is fixed in such way that the threads do not get into a deadlock.
PSX-199962BothCall ProcessingThe flags "Force Local Ring Back Tone" in Tone and Announcement profile of ingress Trunkgroup and "Enforce Max Digits for Valid Phone Number" (in Prefix profile screen when "Overlap Dialing" is enabled) are incorrectly written to the 7th octet in the DIAMETER response in the Ingress Parameter Flags section. The GSX also read the 2 flags from the same location.
This causes an issue when both features are being used.
The fix ensures that the 2 flags are written to their respective octets - "Force Local Ring Back Tone" (octet 6 of Ingress Parameter Flags) and "Enforce Max Digits for Valid Phone
Number" (octet 7 of Ingress Parameter Flags) so that both features work correctly.
PSX-200302BothCall ProcessingBlocking label profile failed to block when ALL is selected for all national destinations.
Both Blocking Label Profile and Hi-Fraud Country Blocking profile are populated in same DB table, BLOCKING_LABEL_PROFILE. When user creates Blocking Label Profile entry for National_Id=Sonus_NULL and a Hi-Fraud Blocking Profile entry both with the same profile Id name they both get written to the DB. Since there were two rows in DB with same Profile ID, PES
was not doing a correct search.
The fix ensures that PES searches with the right criteria to find the correct entry to block call.
PSX-200572BothPSX ManagerGuiClient.pkg is too big and results in no space on EMS when installed.SSGUI package is including jar files of several old versions that are not supported in 9.2 version. Removed the unsupported versions from PsxVersion.txt file so that SSGUI does not include these unsupported jar files.
PSX-203462BothCall ProcessingChanges made in database are not reaching the cache on PSX.
Changes made on the master PSX and verified to have replicated to the
PSX database are not reaching the cache, due to which it is not being
picked up by PES while routing a call.
ZoneID has been added into FQDN IP Peer cache table, so that the change in GUI in a FQDN IP Peer entity would be reflected in the PES cache table, therefore, routing calls correctly, even though the 2 entries contains the same FQDN:port but different Zone IDs.
PSX-203602BothProvisioningNumber Translation service area: All table entries with same serviceAreaId are deleted even though the serviceAreaCode is specified.The code has been modified to fix this issue.
PSX-204182BothPSX ManagerBlocking label profile not displaying toll indication in PSX manager GUI.
Blocking Label Profile screen does not display Toll Indication "Private" as an option. If private is selected either using CLI or API then the GUI display does not show selected toll indication as highlighted.
This fix ensures that toll indication "Private" is displayed on screen and all the selected toll indication values are displayed correctly.
PSX-204392SolarisProvisioningWhen you provision an entry for the LWRESD profile, the value of V4 Start Port Range and V4 End port Range fields is saved as 0 in database. This issue is observed only on Solaris platform.

The code has been modified to save the ports correctly into database. Following changes are made as part of this fix:

  1. GUI: default values are now displayed in the ports when creating new item.
  2. GUI: the input ports are now saved to DB correctly.
  3. If a port is out of the range of 49152-65535 in old version, the upgrade procedure sets it to default.
  4. The default value of start ports is set as 49152 and end ports as 65535.
PSX-204522BothSIPESIPE cored with PSX SMM applied.There was a check missing for null pointer which resulted in core dump.
The fix ensures that a null pointer is handled correctly.
PSX-205012BothDatabaseRequest to add -k as an additonal argument in PSX/EPX pipe serverThe '-k' option is added as default to pipe processes in all the seeded process manager entries. Migration code is also in place to ensure that seeded entries are migrated and have '-k' after migration.
PSX-206622BothCall ProcessingStatic cache resizing causes PES to become unresponsive for 10 seconds.
Few tables in PSX are defined as static cache. These tables can save up to 5000 entries. If you try to save more than 5000 entries, the additional entries are cached but the cache gets locked. As a result, calls that require this cache are waiting on lock causing latencies and failures in processing calls.
The fix ensures that the static cache for above 3 tables is sized at 50,000 entries at startup. The cache does not resize until you have 50,000 entries in this table.
PSX-207212BothPSX ManagerRouting Criteria Profile can be deleted even if it is being used in the TG screen.While deleting a Routing Criteria entity from PSX GUI, a warning message is displayed asking the user to verify that Routing Criteria is not used by any Trunk Group before deleting.
Before deleting a Routing Criteria, the user must ensure that the Routing Criteria is not being used by any Trunk Group.
PSX-207332BothDatabaseVBR routing returns NO_ROUTES_FOUND after DST change.To fix this issue, the data type of systimestamp is updated to "timestamp" (without time zone) instead of "timestamp with time  one”.
PSX-208472BothSCPA Call ProcessingLog profiles fail to work in SCPA for SIP SCP calls.Fix ensures that log profile is successfully associated with SCPA SIP SCP.
PSX-208962BothSIPuser=phone parameter is not always being sent in RURI and To Header in egress, when it is supposed to be transparency.The problem is fixed so that the “user=phone” will be included in egress RURI or To Header when transparency requires.
PSX-173643BothDatabaseWhen multiple IP PEERS are added with the same FQDN and different Zone Index Profile, EPSX results in error.
PSX does not allow user to create two IP Peers with same FQDN and unique Zone Index Profile ids. When user provisions IP PEER with IP instead of FQDN, it allows two IP Peers with same IP but different zone index.
Fix ensures that user can provision more than one IP PEER with same FQDN but unique Zone Index Profile id.
PSX-188293LinuxSIPE

Threads locked in SIPE process stops PSX from processing Invites and option ping.

A deadlock was observed in SIPE between SIPE TimerTask thread during Garbage Collect functionality and SIPE-PES

Interface task thread. This deadlock manifests only Lintel platform and is observed when there is a burst or load of

SUBSCRIBE messages that all result in 404 NOT FOUND.

The ACE recursive mutex implementation has a bug on the Lintel platform. The order in which the Timer thread and the PES Interface thread acquire the mutex causes both threads to be waiting on each other resulting in deadlock due to this bug. This issue can manifest in a REGISTER 404 NOT FOUND call flow in addition to SUBSCRIBE 404 NOT FOUND call flow.

This fix corrects the implementation of ACE recursive mutex for Lintel platform to prevent deadlock.

PSX-189363BothPSX ManagerCan not creante or update Call Parameter Filter via PSX Manager.
PSX Manager GUI was sending down actual string configured for “Value2” field down to database. Database was expecting numeric equivalent of these strings and hence was failing to update or add the database entry.
The fix ensures that the GUI passes down the correct values to pipe server to be written to database.
PSX-193793BothProvisioningTrunk Group Number on PSX vs Incoming Route Identification number on the GSX CDRs.The code has been modified such that in Billing Info Profile the Ingress Trunk Group Number tag (tag 4) can have a maximum length of 8.
PSX-200933BothSIPEPSX SIPE proxy adds quotes in "q" parameter of Accept-Language header even though the parameter was not enclosed in double quotes in the ingress INVITE.Fix ensures that q-parameter value is passed as it came in the ingress INVITE.
PSX-204133BothDatabaseNpaNxxInc.ksh for LERG loading fails when scrip calles "regionAsLata" argument.
The REGION table had alphanumeric region ids but the
NpaNxxInc.sql script checks only for numeric value. Hence
there was a failure.
The fix ensures that the script will check for alphanumeric values.
PSX-206243BothSIP Call ProcessingProxy PSX removes reason field from Diversion header in egress proxy INVITE when the reason field value is quoted.The fix ensures that all non-standard reason values that are received within double quotes will be transparently passed in the egress INVITE with double quotes. The 11 standard reason field values, will be passed in the egress INVITE without any double quotes.
PSX-206633BothPSX ManagerPSX Manager - Error <62> when launching Cache Management Screen.
The pesAddress is not initialized correctly. Therefore, the Cache management screen in the PSX Manager fails to open.
The fix ensures that the Cache management screen opens correctly.
PSX-207373BothProvisioningPIPE causing ORA-01008: not all variables bound from trunk group.
When Numbering Plan on trunkgroup is changed, PSX manager fails to save a new entry with the updated numbering plan and throws an error.
To fix this issue, pipe Trunkgroup APIs are modified to use a local db Connection handle instead of a cached handle.
PSX-207763BothPSX ManagerIn DM/PM Rule screen, the following three fields remain editable even though those 3 fields are invisible in Carrier Code type PM Rule screen.
Include In Egress Flag
Circuit Code
Presubscription Indicator
To fix this issue, the following changes are made in Carrier Code parameter type of DM/PM rule screen:
The field Include In Egress Flag is made visible and enabled. The radio button Presubscription Indicator is made visible and enabled.
Circuit Code is still invisible, but always set to Unspecified.
 

Resolved Issues in PSX V09.01.08R000

This section lists resolved issues in PSX release V09.01.08R000.

Table : Resolved Issues

  Issue IDSeverityPlatform (Solaris/Platform)CategoryProblem DescriptionResolution
PSX-18488

2

Both 

Database

VBR feature is not working because PSX does not convert Gateway Name sent from Netscore to upper case.

The code has been modified to convert Gateway Name sent from Netscore to uppercase before comparison and also added a new row "SONUS_MOU" in table VBR_QOS_TYPES.

PSX-18613

2

 Both

Call Processing

Communication between BRX and SLWRESD is down and BRX stuck in that state.When PSX communicates with multiple DNS servers, in event of a network failure when the DNS servers start going down PSX marks each server as Blacklisted as it becomes unavailable. When all but one server is blacklisted and PSX queries this server and times-out it goes ahead and marks the last server also as Blacklisted. However in this case there is no clean-up logic to clean-up the fetch context. The fetch context is hung and all requests coming to SLWRESD that need the same fetch context just get hung on it. SLWRESD very soon runs out of clients to service incoming requests.

Fix ensures that when all servers are down the cleanup happens correctly.

PSX-18691

2

 Both

Database

When ePSX is installed on standalone SBC, ePSX performs database back up in /export/home/oracle/product/11.2.0/db_1/dbs/ and does not use any retention policy to remove the old backups.

The code has been modified to avoid backup of archivelog when ePSX is installed on standalone nodes.

PSX-19175

2

 Both

Database

NpaNxxInc.ksh script does not have an option to give LOOKUP_TYPE.

The script has been modified to receive input for LOOKUP_TYPE. The default value for LOOKUP_TYPE is 2.

PSX-19224

2

 Both

PSX Manager

"Data Response Error" on PSX GUI when using subscriber link from standard route screen when the Country value is different from what displayed in the Subscriber entity. The same works when the Country in Subscriber entity is set to the same country that belongs to the subscriber and is used in the standard route.

The code has been modified to send the country code to subscriber entity when the subscriber link in standard route entity is clicked.

PSX-19310

2

Both

PES

PSX enhancement: Configurable VBR Disconnect Treatment.

PSX is enhanced to configure the release cause code returned when Value Based Routing (VBR) fails to find routes that meet the specified criteria.
See PSX-19310: Configurable VBR Disconnect Treatment in New Features and Modifications section.

PSX-19636

2

 Both

Call Processing

SLWRESD process core dumps when the query string is unusually long.On getting a response for this query with a long name if the statistics flag is enabled SLWRESD tries to increment counters. During this process it core dumps due to memory corruption. If slwresd times out waiting for response and ARS functionality is enabled it tries to determine the server status for Blacklisting. It may core dump at this step too due to memory corruption.The internal buffer defined to hold the query name string during Statistics increment or for ARS function were too small. Hence when the string was copied to this buffer, it was overflowing and corrupting the data that was present after the buffer resulting in core dumps.

The internal buffers are increased to a maximum size of 1024 to hold sufficiently long strings. This is the maximum length that can be defined. If the string were to exceed 1024 this scenario will be gracefully handled by SLWRESD and not core dump.

PSX-19656

2

 Both

Provisioning

Not able to delete "Number Translation Service Area" through EMS GUI. There is no error when deleting the entry but if you do a search after deleting, the entry still shows as being there.Checked database and entry was not deleted

To address this issue, removed the loop to get ServiceAreaCode which is not needed for deleting "Number Translation Service Area".

PSX-19707

2

 Both

Call Processing

In a complete routing design by customer VBR Routing was returning route labels which are marked for Route Hop. When these RHOP labels are evaluated the resulting routes are not inserted in the correct order in the final route list returned by PSX. However when VBR returns simple nested RLs then the route list order is perfectly fine.

When RHOP is involved after VBR the index to insert the routes from RHOP was not computed correctly and this resulted in routes not being returned in correct order. The fix ensures that the index is computed correctly.

PSX-18028

3

 Linux

SNMP Agent

DeviceInventory fails to gather data from Linux based PSX Nodes. When DeviceInventory runs on EMS, traps indicating "Authentication Errors" are displayed.

The code has been modified such that the rocommunity setting is not commented and thus PSX processes DeviceInventory as expected.

PSX-18229

3

Both

Traps

PSX alarm sonusExtendedSoftSwitchDbrepLagThresholdExceededNotification summary should not include a non-display character.The traps are not displayed properly because of the extra carriage return. The ASCII code is displayed instead of characters.

All occurrences of extra carriage return (\n) in the traps of Dbrep has been removed.

PSX-19122

3

 Both

Database

Application views (VBR based views) are missing after migrating to 9.1.6.

The fix modifies a cursor query to ensure that application views are displayed in query.

PSX-19484

3

 Both

Database

SC-VBR routing fails every 15 minutes - 'vbr_reset_ratesheet_status'

This issue is addressed by not setting the status to disable all vendors and offers for a brief time.

PSX-19488

3

Both

PSX Manager

Disconnect between PSX Manager/API and the database for Margin Percent acceptable values.

The percentage range is now defined as 0-99.

PSX-19694

3

Both

PES

PSX enhancement: Generic digits interworking for DMS switch.

This enhancement allows Parameter Manipulation of DM/PM Rule Entity to support "Spare 09" digit type and Binary Short (DMS) encoding type.
See PSX-19694: Generic Digits Interworking for DMS Switch in New Features and Modifications section.

PSX-19929

3

Both

PSX Manager

"Diversion with Transparency" and "Include History-Info" logic mixed up in PSX Manager

Removed the exclusive restriction between the following 2 flags in PSX Manager, "IP Signaling Profile > Egress IP Attributes>SIP Headers And Parameters->Call Forwarding->Redirection Information->Diversion With Transparency" and "IP Signaling Profile > Egress IP Attributes>SIP Headers And Parameters->Call Forwarding->History Information->Include History-Info".

PSX-19993

3

 Both

Traps

sonusSoftSwitchPipeTMControlRemovedNotification trap consists of non-printable character '0A' that causes display problem in EMS

"\n" is removed from the description field of the trap, so that the trap description field can be displayed correctly.

Resolved Issues in PSX V09.01.07R000

This section lists resolved issues in PSX release V09.01.07R000.

Table : Resolved Issues

Issue IDSeverityPlatform (Solaris/Platform)CategoryProblem DescriptionResolution
PSX-18716

1

Both

PES

Customer requires the ability to dip the 800 SMS database correctly and respond with the jurisdictionally correct CIC and LATA of origin.

See PSX-18716 - JIP Parameter use for IN 800 Queries in New Features and Modifications section.

PSX-15477

2

Both

BRX Application / SIP

BRX adds whitespaces to the Privacy Header. In RFC3323, privacy header definition uses ";" instead of "SEMI" that violates the rules of parsing the priv-values and results in spaces between the elements of privacy header definition, which is invalid.Due to this issue, the Privacy is not honored when the call is connected.

Extra space that was added between parameters of Privacy Header has been removed.

PSX-15565

2

Both

Provisioning

Cannot add entries into Trunkgroup Group entity.While adding a new Gateway/Trunk Group combination in Trunkgroup Group entity screen, the Gateway list displays message "too many entries to cache, please enter a value". If a Gateway is added, there is no option to add a Trunk Group. This issue is caused due condition failure for search of Gateway.

The code has been modified to fix this issue.

PSX-15677

2

Both

Database

Several Softswitch processes on PSX get <defunct> status and try to restart. When Softswitch is started with a PROCESS_MANAGER_ID that has 19 or more processes configured many processes do not startup correctly. The internal arrays to maintain list of all processes is not defined correctly resulting in this issue.

Fix ensures that internal structures can hold information about all processes configured correctly and hence the processes startup successfully.

PSX-15759

2

Both

Database

Generic Digit Type field values in the Signaling Profile entity is not taken care by the DB migration. After upgrade customer sees incorrect values.

Added the migration code for standard and LDM upgrade to migrate this field correctly.

PSX-17463

2

Both

VBR

Call processing latency is observed during VBR provisioning. In VO, call drops and high I/O are observed on slaves while VBR changes are being replicated.

Introduced rate sheet chunking from replication perspective.
Instead of pulling and committing the entire rate sheet, the rate sheet is broken into smaller chunks when provisioning, so that small batches are committed instead of the entire rate sheet which prevents high I/O and call drops.
The default chunksize is 250000. The size can be changed for example to 100000 by using an integer value as: vbrrsldr –l ratesheetfile.csv 100000

PSX-17516

2

Both

Call Processing - SIPE

SIPE process core dumps or thread locks.
There is an issue related to race condition between multiple threads processing the same options ping messages (same call id, branch, tag) due to retransmissions. While one thread is still processing the OPTIONS message another thread may delete the call control block created for the OPTIONS. This results in a heap corruption if the first thread tries to use the call control block after it is deleted. This results in a SIPE core at a later point. Sometimes this manifests as a PSX thread lock.

The fix eliminates this race condition and prevents coredump/threadlock.

PSX-17669

2

Both

Call Processing

Request for scpa core analysis. PSX memory usage is going high. PSX SCPA memory leak is significant when SIP SCP external server returns 5xx or 4xx.

To address this issue, the heap allocated for processing 5xx and 4xx query is deleted at the end.

PSX-18174

2

Both

HA

Connectivity of bond0 is lost when eth0 (reachability) is lost. This is because bond0 interface (well-known IP) was resolving to the wrong MAC address i.e. eth0's MAC address.

Resolved the issue by mapping the correct MAC address for bond0. It ensures that connectivity of bond0 or well-known IP is not lost even though eth0 (reachability) connection is lost.

PSX-18428

2

Both

Call Processing

PES process cored. The core happens when there are call flows that egress trunk group has IPSP assigned. When this IPSP is modified via provisioning, pes cache/memory is to be refreshed during which PSX routing access that part of the memory causing core dump.

The code has been modified to lock the memory so that provisioning will not cause pes core dump.

PSX-18697

2

Both

Database

When using the PSX "Trunk Group Renaming" function on the PSX Manager which has a trunk group of SIP, it renames ALL SIP Severs DEFAULT_TRUNKGROUP_ID to the new trunk group value.
The trunk group id for all gateways would be changed mistakenly to the new trunkgroup id, if the same trunk group id is being used by more than one gateways. This will lead to call processing failure.

The code has been modified to fix this issue.

PSX-18729

2

Both

Replication

Bulk replication keeps failing and displays message "Job does not exist". The Provisioned data is not replicating to slave, due to which slave encounter replication failure is happening.
This issue was caused due to the DB running out of a memory pool called shared pool, due to which the connection to dbrepd is lost.
Due to this issue calls from SIP proxy fails.

The code has been modified to fix this issue.

PSX-18744

2

Both

Call Processing

Call recording backward compatibility does not work after upgrading to 9.2.0R000. It shows MCT recording even when no recording criteria was matching.

The code has been modified to fix this issue.

PSX-18779

2

Both

PSX Manager

When adding a Routing Label Route in the GUI, selecting the GSX displays Trunk Groups that are available in the whole switch instead of only the ones that are available to the selected GSX. If the TG selected is not available in GSX this causes error while saving the RL Route.

The code has been modified to fix this issue.

PSX-18922

2

Both

VBR

VBR excluded route can no longer be selected again by PSX routing. When a route is excluded by VBR routing due to any KPI value out of range, Netscore stops sending KPI parameters for the excluded trunkgroup. PSX VBR Trunkgroup QOS table receives no update for the corresponding trunkgroup due to which that trunkgroup cannot be selected again by PSX VBR routing function.

The kpi loader is modified, so that whenever a file is loaded from Netscore into PSX, the utility vbrkpildr first cleans up the TG QOS entries which are present since 30 minutes (default value) or older.

PSX-18229

3

Both

Traps

PSX alarm sonusExtendedSoftSwitchDbrepLagThresholdExceededNotification summary should not include a non-display character.
The traps are not displayed properly because of the extra carriage return. The ASCII code is displayed instead of characters.

All occurrences of extra carriage return (\n) in the traps of Dbrep has been removed.

PSX-18621

3

Both

Provisioning

API Error Code should be ERR_INVALID_VAL not ERR_DB_OPR_FAIL.

The code has been modified to display the correct error message.

PSX-18789

3

Both

PSX Manager

Issue with PSX Manager displaying Standard Route entity when CPE Type is set to "Origination Region".Due to this the Standard Route entity display issues when Call Processing Element type is selected as Origination Region.

The code has been modified to fix this issue.

PSX-18907

3

Both

PSX Manager

PSX Policy Server Versions fails to list all the installed versions.EMS General > PSX Policy Server > PSX Policy Server Versions does not list all the installed versions.

The code has been modified to display all supported versions of PSX.

PSX-19015

3

Both

PSX Manager

DM/PM Apply later flag issue. Apply Later flag on Routing Label Route screen does not work.

The code has been modified to ensure that "Apply Later" flag works properly.

Resolved Issues in PSX V09.01.06R000

This section lists resolved issues in PSX release V09.01.06R000.

Table : Resolved Issues


 Category

Platform (Solaris/Linux)

Resolved Problems in V09.01.06R000

Effect if Not Fixed

Call Processing

Both

PSX-18620: Called Number getting globalized twice after upgrade to 9.1.

The code has been modified to ensure that Called Number is not incorrectly globalized. The code was incorrectly globalizing the Called number field when the Globalize flag for dialed number was enabled.

Severity 3: Call gets dropped because of an additional +1 being added to the called party, the App Server is rejecting the INVITE with 403 Unauthorized.

Database

Both

PSX-18571: Radius authenticated users on EMS might not be able to provision on Master PSX via PSX manager.

To address this issue, the buffer size is increased to 50 to ensure EMS username can be up to 50 characters.
The buffer to store the ems username was too small and hence radius authorization with long username was failing.

Severity 3: EMS users with username longer than 32 characters (mostly Radius authenticated) cannot provision Master PSX.

Provisioning

Both

PSX-18033: (ERR_DB_OPR_FAIL) Changes to entity not allowed. Feature license '(BRX-NU MBER-TRANSLATION-100CPS) BRX Local Number Translation' inactive. (rc=31)

To address this issue, the error message displayed (when licenses are not reassigned after upgrading from PSX7.x to PSX9.1.x) has been modified to reflect the problem more accurately.

Severity 2: The error message misleads the customer about which license is missing.

Install/Upgrade

Both

PSX-17951: When the "postinstall reconfig" script is executed errors are displayed.

The code has been modified to fix this issue.

Severity 3: postinstall script displays errors.

Provisioning

Both

PSX-16800: Entries in Blocking Profile are not being displayed in alphabetical order.

The code has been modified such that the entities are displayed in an alphabetic order.

Severity 3: Entries in "Blocking" Profile might not be displayed in alphabetical order.

PSX Manager

Both

PSX-18404: EMS General > PSX Policy Server > PSX Policy Server Versions does not list all the installed versions.

The code has been modified to display all supported versions of PSX.

Severity 3: PSX Policy Server Versions page displays incomplete information.

Database

Both

PSX-18384: VO - PSX severe call processing degradation during 9.1.5R1 LDM mode.

The code has been modified to fix this issue.

Severity 2: PSX consumes high CPU. Calls are failing due to the 100% CPU.

Call Processing

Linux

PSX-18619: PES cored on a 4270 Linux PSX when call load over license limit.

The code has been modified to fix this issue.

Severity 2: PES core dumps when running PSX with a BURST license installed.

Database

Both

PSX-18070: CrMasterSlaveCompatibilityCheckPkg.sql causing issues when rebuilding slaves while master version is same as slave version OR after LDM deletion, slaves are not in sync with master / dbrepd failing on same.

The Code has been modified to fix this issue.

Severity 2: Causes issues when rebuilding slaves.

Call Processing

Both

SBX-2283: EVRC and EVRCB Transcoding.

The code has been modified to fix this issue. For more information on EVRC and EVRCB Transcoding, refer New Features in PSX V09.01.06R000.

Severity 2: Not applicable

Resolved Issues in PSX V09.01.05R001

This section lists resolved issues in PSX release V09.01.05R001.

Table : Resolved Issues


 Category

Platform (Solaris/Linux)

Resolved Problems in V09.01.05R001

Effect if Not Fixed

Provisioning

Both

PSX-18179: Malformed query to Number Translation Criteria entity in pipe process results in NO response data.
The query to the Number Translation Criteria entity was malformed by Pipe server. This results in no rows and returns "Data Response Error" to PSX Manager client.
The rows are available in the database table, since the query is incorrect it fetches no rows.

The fix ensures that the query is correctly formed by pipe server and returns expected rows.

Severity 2: Number Translation Criteria entity search in PSX Manager results in 'Data Response Error'.

Call Processing - SIPE

Both

PSX-18037: SIPE process cored and did not restart and the PSX stops responding to messages.
SIPE was dumping core when trying to copy "Include Accept RPH in 417 Responses" flag to V6task in memory. Code was not checking for the task to be present before setting the flag.

The fix ensures that the PSX checks if the task is created before setting any flags.

Severity 2: SIPE may core dump when trying to update "Include Accept RPH in 417 Responses" flag in Softswitch entity.

Sonus Agent

Both

PSX-17994: SSA waits for the response for the processes, such as PES, SIPE, and SCPA, which are not running. SSA times out after 60 seconds. But the wait builds the message queue. PSX agent hangs up due to out of memory.

Do not send message to the processes that have not been active, i.e., have timed out in the previous try in the same session.

Severity 2: SSA takes more time than the idle time to consume one batch of stats requests (messages). Due to this, the socket buffer and the message queue on common agent gets filled up and the common agent runs out of memory.

Call Processing

Both

PSX-17506: When PES gets more_routes request under load, there are instances when the pol_rsp has already been flushed from cache and PES has to return an error status in pol_rsp. In such cases, sometimes PES steps beyond allocated memory and populates invalid data in pol_rsp. This leads to memory corruption and hence PES core.
Pol_Rsp structure was not initialized prior to being populated. Hence, it contained invalid data. Fix ensures that PES initializes pol_Rsp sturcture and populates only the required data for an error response.

Severity 2: PES process may core dump under load when processing MORE_ROUTES request from GSX.

SSREQ GUI

Both

PSX-17302: Users were unable to perform Advanced SSREQ with a Timestamp beyond the year 2010.
SSREQ GUI does not allow users to set Timestamp to current date or any date beyond the year 2010. The code has been modified to ensure that the users can set the current date.

Severity 3: Users cannot set Timestamp to current date or any date beyond the year 2010.

Signaling

Solaris

PSX-18119:
SCPA connection issue to Standby CE SGX - FD issue.
PSX ANSI TCAP client failed to make connection with SecondaryCE of SGX-2k. This behavior is observed only with T5220 server Solaris patch level for 9.x releases. The OS is creating file descriptors that are greater than 64, however the SGX2k client code only allows a maximum fd value of 64.
On some systems, the fd value for the backup CE connection from SGX has a value greater than 64. This is observed to be 256 on some systems.

The fix is to allow the maximum fd value to 1024.

Severity 2: SCPA process may have connection issue to Standby CE for SGX2K on a T5220 platform.

Replication

Both

PSX-18059: DBREP_PKG.REP_APPLY fails for 9.1.4 LDM upgrade (from 9.0.9).
Replication of VBR_VENDOR_RATE_SHEET table on LDM setup fails with error - Oracle Error: -927, ORA-00927: missing equal sign#012ORA-06512: at "LIVEDATAMIG.DBREP_PKG", line 687#012ORA-06512: at line 1#012
Data type "timestamp" is new data type for SSDB dbreplication that is first started to be used in VBR tables.
This data type is handled by regular replication dbrep triggers, but not by LDM dbrep triggers

The fix for this CQ includes the changes to handle data type timestamp by LDM dbrep triggers.

Severity 2: Replication for VBR related tables may fail during LDM upgrade.

Resolved Issues in PSX V09.01.05R000

Note: This version is not used.

Resolved Issues in PSX V09.01.04R000

This section lists resolved issues in PSX release V09.01.04R000.

Table : Resolved Issues

 Category

Platform (Solaris/Linux)

Resolved Problems in V09.01.04R000

Effect if Not Fixed

PSX Manager

Both

PSX-15583: In VBR Report
Metadata, "View Report" was not showing the entire file. "View More" button was grayed out.

The fix is to ensure that the "View More" button of Report Metadata screen is enabled always.

Severity 2: "View More" button can be grayed out.

Provisioning

Both

PSX-17012: PSX allowed Number Translation Service Area in use to be deleted.

The expected behavior is to display an error while attempting to delete the record in use, stating the record is currently in use. The record must not be removed from the GUI screen.
A check is added to the reference
from Number Translation

Severity 2: PSX allows Number Translation Service
Area in use to be deleted.

SIP

Both

PSX-16869: When 100 trying is received from SIP SCP, SCPA issues a critical log for every call. This happens due to the race condition that occurs between 100 trying response and 300 multiple choices, since the response parameter in the call leg is set to NULL.
To avoid the logs, ensure that the response parameter must not be set to NULL.

Severity 2: SCPA issues critical log for every call.

Call Processing

Both

PSX-17394: PSX Pes Process stops processing and cores.

PSX Pes fails to determine country code, since the digit type of called number was set to "User name" in prefix profile.
This causes Pes to core dump while fetching prefixes from country table. The core is reproducible at customer's site.
Code has been modified to fix the issue.

Severity 3: PSX Pes Process stops processing.

Database

Both

PSX-16940: PSX consumed high CPU, causing latencies.

The Stored procedure to query the VBR tables and fetch the vendors to PES process after all exceptions are processed was causing Oracle CPU to spike. The exceptions table is dipped in a nested loop which is not optimized.

The stored procedure is modified to optimize the query to VBR tables, resulting in much less CPU utilization.

Severity 1: High CPU utilization.

Call Processing

Both

PSX-17173: Endianess issue on
Disconnect Treatment information being passed to GSX. Disconnect Treatment Profile passed to GSX from PSX in TLV structure did not conform to Endianess for Lintel Platform. This resulted in GSX not being able to read the TLV and apply the treatment.
Fix ensures that PSX conforms to Endianess when populating DT in TLV.

Severity 2: GSX may not be able to read and
apply Disconnect Treatment sent by Linux PSX due to Endianess issue

Call Processing

Both

PSX-17200:
H323 bug on Linux PSX – little Endian vs. big Endian.

H323 gatekeeper confirmation has never been sent to the right IP and port in Linux, therefore it failed. "Pgkmgmt" was also not working, the IP address was Ipv6.

The fix ensures that the little Endian and big Endian format of the IP address and port are correctly converted to allow the RAS messages being sent to right places. The pgkmgmt problem is also fixed.H323 bug on Linux PSX.

Severity 1: A few types of RAS messages will fail on responses and pgkmgmt will also not be usable.

PSX Manager

Both

PSX-17186: In Routing Label Route Screen, Skip Local Recursion flag fails to store the correct value in DB. This causes routing issues in PSX.
GUI code has been fixed.

Severity 3: PSX fails to pick correct route if Skip Local Recursion flag is not set correctly.

Install/Upgrade

Both

PSX-15767: PSX Upgrade Script has reference check to an incorrect version of oracle, which results in an Upgrade error.
To fix the issue, the unnecessary check has been removed.

Severity 2: Upgrade fails with an error.

Database

Both

PSX-17364: When multiple IP PEERS are added with the same FQDN and different Zone Index Profile, EPSX results in error.

PSX does not allow user to create two IP Peers with same FQDN and unique Zone Index Profile ids. When user provisions IP PEER with IP instead of FQDN, it allows two IP Peers with same IP but different zone index.

Fix ensures that user can provision more than one IP PEER with same FQDN but unique Zone Index Profile id.

Severity 3: User cannot create multiple IP Peers with same FQDN but different Zone Index Profile IDs.

Resolved Issues in PSX V09.01.03R000

This section lists resolved issues in PSX release V09.01.03R000.

Table : Resolved Issues

Category

Platform (Solaris/Linux)

Resolved Problems in V09.01.03R000

Effect if Not Fixed

Install/Upgrade

Both

PSX-16722:
After successfully
loading a BDD from Neustar,
customer started incremental feed for On-Board Hosted LNP.
Customer was observing "Update"
operations failing with
ERR_REC_NOT_FOUND around midnight every night. However, when the database was checked, the record indeed was present.

When PSX database cron jobs like
DbDiag are running, database
records are locked and update operations are not successful. When
EMS re-tried the "Update"
operation, "Provisioning" function
was incorrectly reporting previous
update failure as
ERR_REC_NOT_FOUND even though the database record was present.

Fix ensures that once the database
row is unlocked, the "Update" operation is successful.

Severity 2: During cron jobs like DbDiag,
"Update" operations may fail due to ERR_REC_NOT_FOUND error message.

HA configuration

Both

PSX-15749: Network prefix has been hard coded to be 24 in Linux platform.

Script has been modified to use the same network prefix of eth0 if NetMask is absent from  /var/opt/sonus/haConfiguration

Severity 3:None

Call Processing

Both

PSX-16772: When calls are forwarded to VM from an UNREGISTERED VOLTE phone with an ANI of 000-000-0000, SIPE process restarts.
Under certain conditions, (a non-globalized number combined with FQDN SIP server configuration and populating a PAI header and some amount of load) SIPE reads beyond the end of a memory array and then, depending on the contents of the memory that is incorrectly read, will sometime core.
The fix ensures that SIPE reads only within the bounds of the memory allocated for the array thus preventing the core dump.

Severity 2:SIPE process may core dump under load for a non-globalized ANI with FQDN SIP Server configuration when populating PAI Header.

Call Processing - SIPE

Both

PSX-15258/SONUS00154911: PSX sent "500" response to INVITE: Transaction CreateLockedTCB collided with existing entry. Timer functionality in SIPE is misbehaving due to a race condition among SIPS Timer Task threads under load. As a result of this race condition, SIPE does not detect some timeouts and these timer IDs are still in use in the SIP stack Transaction Control blocks. Hence, SIP stack never deletes these transaction control blocks. When a subsequent call tries to allocate transaction with same handle as one being held due to timer issue, it results in a collision message in sipe.log and PSX sends a "500" to the client since it could not create the transaction. The Race condition in SIPS Timer threads shall be solved by maintaining appropriate states in SIPE. Once SIPE detects a timeout, it will move its state to TIMEOUT_IN_QUEUE state and wait for the worker thread to serve it. Any other thread that tries to cancel the timer, will not cancel it if it finds the timer entry in TIMEOUT_IN_QUEUE stack. This will ensure that all timeouts are detected and the transaction will be cleaned up.

Severity 3: Timer functionality could misbehave on SIPE under load when there are many timeouts and delays responses.

Install/Upgrade

Both

PSX-16707:Upgrade procedure fails with an error.
To fix the issue, #

!/bin/sh has been modified to #!

/bin/bash in haResources.template.

Severity 1:HA functionalities such as switchover and failover fail to work as desired.

Database

Both

PSX-15510: The required seed data is missing in table VBR_REPORT_TYPES.

A new report fails to be created based on VBR report metadata entity with a DB integrity check error.

Seed data was only present for new installs and not for upgrades Migration. Code has been added to resolve this issue.

Severity 2:A new report cannot be created based on VBR report metadata entity.

Call Processing

Both

PSX-16486:When CNAM enabled cache on Process Config, PES process started to core.

When a CNAM call load is run and 2 threads are handling different SCP responses and trying to cache the responses at the same time PES core dumps.

Code has been modified to fix the issue.

Severity 2:There was an extraneous delete of a pointer which was causing PES to core.

Database

Both

PSX-16792:ePSX replica is not in sync with master.
ePSX as replica installation is successful but the replication status on master is not in sync and throws a sql error message.
Replication setup script has been modified to set the correct replication resumption point if new slave already exists on master.

Severity 1:Master / Slave replication fails to resume due to replication error.

PSX Manager

Both

PSX-15700:Prefix Profile page hangs up.
When an attempt is made to query a Prefix Profile which has 70000 prefix digits, then PSX Manager GUI hangs up and needs to be killed and restarted.

To fix this issue, longer timeout value is set.

Severity 2:PSX Manager can hang up while querying a Prefix Profile with huge amount of prefix digits.

Database

Both

PSX-15426:UpdateDb fails with an error.
When trying to restore master from a slave, the slave uses the same name as the original master, then there is a link that has the same name as the global_name to be set.

Upgrade script is changed to remove any existing database object that refers to original master database.

Severity 3:UpdateDb fails when master database is restored from its own slave.

PSX Manager

Both

PSX-15713(SONUS00163019): Generic Digit Type dropdown issue in Signaling Profile. On opening up the Signaling profile screen, when the Generic Digit Type drop down value is changed, the GUI is not able to detect the change and it shows that nothing has changed. So when users save it, the Generic Digit type value is back to "unknown."
Note: This problem only shows in PSX systems which have upgraded from pre-V07.03.04R009, pre-V07.03.06R003, or pre-V08.04.01R000 to these versions or later versions.
The GUI problem has been fixed.

Severity 3: Generic Digit Type dropdown issue in Signaling Profile.

Call processing

ePSX only

SBX-23521:There is no mechanism to associate a global license to the ePSX. Therefore, if the call rate is greater than the configured cps rate then the calls that exceed the configured cps fail.

The change done in this request is to allow the calls to go through even though they exceed the licensing limit.

Note that if there are no licenses associated at all then calls will fail.

Severity 3:Calls above the configured limit fail to complete.

Call Processing

Both

PSX-16805:SCPA process core dumps when processing a call that had long called number string and SCPA was looking for special characters to remove them.

The temporary array used to hold the called number was defined as only 19 characters long whereas called number was longer than that. Hence SCPA core dumped.
Fix ensures that SCPA defines array with right size so that there is enough space to copy the called number.

Severity 2:SCPA process may core dump when processing a request with a called number greater than 19 digits.

Database

Both

PSX-16633:A temporary tablespace (BUILD_INDEX_TEMP) was created in /tmp tablespace for migrations performed during UpdateDb. 
Since the hosted_lnp table was huge, it caused the tablespace to require space more than the allocated space for /tmp. This resulted in failures at the customer site.The code has been modified to create the tablespace (datafiles) in the same place as other index files to avoid filling up /tmp tablespace.

Severity 3:UpdateDb may fail due to space issues on /tmp.

Resolved Issues in PSX V09.01.02R000

This section lists resolved issues in PSX release V09.01.02R000.

Table : Resolved Issues


 Category

Platform (Solaris/Linux)

Resolved Problems in V09.01.02R000

Effect if Not Fixed

Signaling

Both

PSX-15488:PSX failed to send queries through backup SGX2000. PSX used incorrect local PC/SSN when it failed over to the backup SGX.

The code has been modified to store the backup SGX data from the database. Also, the code has been updated with new routines to return the "current" SGX local address data.

Severity 2: PSX can use incorrect local PC/SSN when it fails over to backup SGX.

Call Processing

Both

PSX-15545:Overlapping Charge band entries cause no band to be returned. Charge Band Determination fails if Overlapped entries do not have either Calling or Called prefixes of same length.

  • Current design does not handle fetching correct Charge Band Profile entry from the database if the Called and Calling Prefixes are of mixed lengths.
  • Additionally, if user provisions CBP using CLI and enters ALL for Called or Calling National ID, the entry is saved with "ALL" in database instead of "Sonus_NULL".


    The fix addresses both issues. Fix ensures that when mixed length called and calling entries are present, the correct entry is fetched by PES process. CLI provisioning with Called or Calling national ID set to "ALL" will be correctly saved as "Sonus_NULL" in the database.

Severity 2:PSX might not match a valid Charge Band entry.

Call Processing

Both

PSX-15669:PSX failed to execute LNP DIP properly when using "Escaped Number". When an entry is provisioned in the Escaped Number table and the PSX is set to launch the LNP query, LNP query should not be launched. It escapes with the following message: "Digit Attribute NPA not present, LNP is escaped). However after deleting the entry from Escaped Number, PSX was still not able to launch the LNP query.

The fix is to ensure that once the escaped number is deleted, LNP must be launched when needed.

Severity 3: PSX cannot execute LNP DIP even the number is deleted from "Escaped Number".

Call Processing

Both

PSX-15503:In SIP Proxy call flow, call distribution is not equal across SIP servers configured for the routing label with CPS greater than 100.
Round Robin logic has been modified to return routes in correct order during load scenario.

Severity 2: Calls fail to equally distribute across SIP servers.

HA configuration

Both

PSX-15749: Network prefix has been hard coded to be 24 in Linux platform.

Script has been modified to use the same network prefix of eth0 if NetMask is absent from  /var/opt/sonus/haConfiguration

Severity 3:None

MIB/SNMP

Both

INS-18568:Port 161 is reserved for common agent. If common agent fails to get port 161, it leads to EMS reachability test and authentication trap problem.

Port has been changed to 1610 to fix the issue

Severity 3: PSXs fail to response to keep alive message from the EMS.

Call Processing

Both

PSX-15762:After receiving response to ENUM dip, PES fails to populate the domain name in Routing Criteria if the domain name is in IP address format. It populates only if it was in domain name format.

Fix ensures that PES populates the domain name correctly in Routing Criteria irrespective of its format.

Severity 2: Routing fails because PES fails to populate the domain name in routing criteria

Call Processing

Both

PSX-15730:External Dip Caching was supported only for LNP and CNAM dips not for Tollfree dips. Fix ensures that even when TTL value for Tollfree service is enabled on the Service Definition screen, PES continues to send dip to SCP for Tollfree service.

Severity 2:If TTLTimerForExtServLookupCache on a Tollfree Service Definition is set to a non-zero value, PES process fails to send the tollfree dip which results in a failure.

Call Processing

Both

PSX- 15758:While performing source GW routing, PES process uses the FROM header IP and Port values to determine the ingress GW and TG. If FROM header contains only IP address and no port value, PES process looks for a GW with matching IP value and port value set to 0. This lookup fails as the default port value is 5060.

In order to resolve this problem, SIPE sets the port value as 5060 if no port value is present the FROM header and sends this value to PES. PES use the IP value present in FROM header with port value of 5060 to performs ingress GW and TG lookup.

Severity 3: While performing source GW routing, PES process fails to determine the ingress TG and GW if the FROM header of incoming SIP message has no port value present in the host part of the URI.

Call Processing

Linux

SBX-22315:Policy response fails to return correct IPv6 address of IP Peer.
IPv6 address encoding in POL_RSP fails for IP peers on PSX/ePSX versions running on Linux OS. The issue is due to an incorrect IP address family value used in IP address conversion.

Code has been changed to fix the issue

Severity 2:Impacts external PSX running on Linux OS and ePSX (all versions). IP peers with IPv6 addresses cannot be used in routing.

Known Issues

This section lists known issues in PSX release V09.01.09R000.

Table : Known Issues

 Issue ID

Severity

Category

Problem Description

Workaround

PSX-19177

3

Call Processing

For a SIP ingress call, if the calling number is empty or anonymous then origination LATA is not determined in PSX though billing number is used as calling number as per the FCP flag "Always use Billing Number For Calling Party Number".

Create an "In DM/PM" rule on ingress trunk group with a DM/PM criteria to check if the calling number is empty and then copy a dummy number (say 12345) to calling number.

SONUS00132477

2

MIB/SNMP

During 8.x installation or upgrade SUN platform (Netra, 5220) traps do not work as expected.

/var/adm/messages provides information on the hardware events.

SONUS00137235

3

11GR2MAIN script

11GR2MAIN fails to validate version before proceeding and therefore resulting in 11g software being overwritten and loss of existing initSSDB.ora

Verify if the path /export/home/oracle/product/11.2.0/db_1 is available before installing the 11g Oracle software. If the path is not present, Oracle 11g is not installed. Proceed with 11gr2main to install the oracle 11g software.

SONUS00159298

3

GUI

PSX Manager hangs when the user tries to delete the created VBR customer entity by right-clicking the entity and choosing delete option from the displayed menu.

This operation is currently not supported on the right-click menu.

In case the PSX Manager hangs, the user must re-login to the PSX Manager.

Known Limitations

This section describes known limitations of  PSX in this release.

T5220 Server Support

The network management port of T5220 server supports only IPv4 addressing mode. This interface for out-of-band device management does not support IPv6 addressing mode.
To install the OS or jump start a server with software images of the following Sonus products, use only IPv4 address for management ports on T5220 server:

  • ASX
  • ADS
  • DSI
  • EMS
  • PSX

Adaptive Congestion Control

If larger Overload Control Interval is chosen, the CPU utilization may vary by 8%, in both directions, from the configured Target CPU Utilization. Also modifying the parameter values in the profile without proper analysis can cause unexpected behavior. Sonus recommends that you consult the Sonus Network Design and Analysis Group (NDAG) to simulate and analyze the load and determine recommended values for parameters.

Memory Usage

The following memory usage issues exist for PSX Manager, SSREQ, Shadow Database GUI, and HSX Manager applications.

Java Applet Memory Space

For JRE Plug-in versions earlier than JRE 1.7.0, the following situations can cause an "Out Of Memory" error to return, indicating that the virtual machine has run out of heap space:

  • When a PSX Manager or SSREQ applet is reloaded over and over with another Internet Explorer window open
  • When a PSX Manager launches the HSX Manager or a second PSX Manager for browsing the Shadow Database in another Internet Explorer window

If this issue occurs, add the arguments -Xmx256m -Xms128m to the Java parameters in the Control Panel to increase the maximum heap space (default = 96M) to 256M and the minimum heap space to 128MB.
Note: It is possible that a setting of 256MB may be too large for a particular system. If the applet fails to start and you see the following error message,
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
then reduce the maximum heap space from 256MB to 192MB (-xmx192m). If the same error occurs, reduce the heap space again to 128MB (-xmx128m). If the applet still does not load properly, you may have to either increase the memory in the system, or unload unneeded dll files using memory.

PSX Manager Repaint Issue

The following memory usage issues exist for PSX Manager.
If multiple versions of the Java Runtime Environment (JRE) are installed, you might experience repaint problems with the PSX Manager. If so, and there are multiple versions of the JRE installed under the "Add Or Remove Programs" Control Panel, uninstall all versions and reinstall the JRE plug-in 1.7.0.

Provisioning

Business Group Identifiers

The Business Group Identifier (bg_id in the CLI; Business Group field on the PSX Manager Business Group screen) must be a number in the range 0-2147483647. Do not use leading zeroes (for example, 02).

DM/PM Rules

If the calling number is not in the IAM, it has to be first created in the ingress DM rule. After then it can be modified at any place.

Appendix A

PSX Manager Signing Certificate

The following prompts will pop-up while launching PSX Manager GUI version PSX 9.0.3R0. PSX Manager has both signed and unsigned components - GuiClient.jar is signed where as other third-party jars are not signed. And as per recommendations it may not be legal to sign the third-party jars. Hence users may continue to see the following prompts while launching PSX Manager. See sections A.1 and A.2 for screenshots of these pop-ups.
User can navigate to a screen from the pop-up that displays that sonus has upgraded the signing certificate for sonus-specific jars. See section A.3 for screen that shows that certificate is signed and current.

A.1 JGuiClient pop-up

Java 7 Update 21 introduced changes to the Java browser plug-in behavior that enable you to make more informed decisions before running the Java applet in the browser. A security prompt asks for confirmation before allowing Java content to run in the browser. For more information, please check the below link http://www.java.com/en/download/help/appsecuritydialogs.xml#background

Figure : Java Prompt

A.2 Security Warning

Below security warning is displayed due to http://www.java.com/en/download/help/signedjar_dialog.xml

Figure : Security Warning


When signed applets that contain signed and unsigned components could potentially be unsafe unless the mixed code was intended by the application vendor. As of the Java SE 6 Update 19 release, when a program contains both signed and unsigned components, a warning dialog is raised. For more information, visit http://java.com/en/download/help/error_mixedcode.xml

Figure : Security Warning

A.3 View Certificate Details

Figure : Certificate Details