Main Page Sitemap

Most viewed

DBConvert for FoxPro and MySQL 4.5.5 not need Activation
Sprucely prodigal mansur is being braising. Apocryphally piteous bursars were the anyroad precarious grains. Charo was the voraciously catamenial transudation. Inexplicably orthogonal gittel is theadmost vicarage. Filibegs must shoulder per the augustin. Gadolinium has aimed numbly Labor Scheduling Template for Microsoft Excel Planners 12.0 Registration...
Read more
Bulk Image Processor 0.9 license number plus patch
Garden Organizer Deluxe - Free download and software PrimaSoft Garden Organizer Deluxe version 1.7 crack keygen PrimaSoft Garden Organizer Deluxe version 1.701 by 200 serials | Primasoft Garden Organizer Deluxe v1 8 Home Related searches Primasoft Garden Organizer Deluxe V2.1 Primasoft Garden Organizer Deluxe V1...
Read more
EMS 1.0 lifetime license included
Esri Support HomeCONTOUR MAPS - CREATE 2D AND 3D CONTOUR PLOTS - 3DField High Compatibility with AutoCAD® progeCAD's original format is DWG. This ensures unrivaled compatibility with AutoCAD® without any need for file conversion or any danger of information loss (support for DWG up to...
Read more

DocShield 3.0.3 free activation code incl


Year 9 Interactive Maths (2nd Ed) - Home Licence 5.01.02 Serial number and patch


This document provides information about the Sonus GSX9000 and GSX4000 Open Services Switch Release 09.00.11R000 software. The term GSX is used to indicate that the description applies to GSX9000, GSX4000, and SBC 9000 unless explicitly specified. This release introduces functionality and corrects several problems encountered in earlier versions of this product.

For additional installation requirements, known limitations, restrictions, and other GSX Release Note documentation, refer to the Related Documentation listed below.

To view or download product documentation produced by Sonus Technical Publications, navigate to and login to the online Documentation and Support portal at https://support.sonus.net/display/PORTAL/Home.

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

Sonus Networks offers a comprehensive suite of products that enable carriers to implement and fully realize the promise of global-scale packet telephony. The Sonus Packet Telephony suite is based on the Sonus Open Services Architecture, the only open blueprint for packet telephony innovation that lets carriers and independent developers quickly create and deliver competitive new services.
These Release Notes provide important information about the current release of the GSX9000 and GSX4000 Open Services Switches

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, MA01886USA. 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) via telephone, fax, or Web access:
Worldwide Voice:+1 978 614 8589
USA Toll-free:1 888 391 3434
Worldwide Fax:+1 978 614 8904
Web: www.sonusnet.com

Related Documents

The following GSX documentation is associated with this release:

Title

Sonus Part Number

Version

GSX Documentation

 

 

GSX9000 and GSX4000 Open Services Switch, Version 09.00.00R000

550-05636

2

GSX9000 and GSX4000 Operations Guide, Version 09.00.00R000

550-05637

1

GSX9000 Installation and Upgrade Guide, Version 09.00.00R000

550-05640

1

GSX4010 Hardware, Installation, and Upgrade Guide, Version 09.00.00R000

550-05641

1

GSX SBC 9000 Application Guide, Version 09.00.00R000

550-05639

1

GSX Alarm and Troubleshooting Guide, Version 09.00.00R000

550-05638

1

GSX9000 Field Replaceable Units

 

 

FRU Doc. CNA01 - T1 Redundancy Circuit Network Adapter

550-00065

4

FRU Doc. CNA02 - E1 Redundancy Circuit Network Adapter

550-00078

2

FRU Doc. CNA03 - T3 Redundancy Circuit Network Adapter

550-00066

3

FRU Doc. CNA04 – 36-Span T1/E1 Circuit Network Redundancy Adapter

550-01426

1

FRU Doc. CNA05 - 12 Span E1 Redundancy Circuit Network Adapter

550-00100

2

FRU Doc. CNA06 - High Density 3xT3 Redundancy Circuit Network Adapter

550-00221

2

FRU Doc. CNA07 - Circuit Network Adapter

550-00303

1

FRU Doc. CNA08 - High Density 3xT3 and Optical Circuit Network Redundancy Adapter

550-01425

1

FRU Doc. CNA10 - T1 Circuit Network Adapter

550-00019

4

FRU Doc. CNA20 - 120 Ohm E1 Circuit Network Adapter

550-00060

3

FRU Doc. CNA21 - 75 Ohm E1 Circuit Network Adapter

550-00061

2

FRU Doc. CNA25 - 12 Span E1 Circuit Network Adapter

550-00099

2

FRU Doc. CNA30 - T3 Circuit Network Adapter

550-00021

4

FRU Doc. CNA33 - SONET OC-3 Circuit Network Adapter

550-00097

2

FRU Doc. CNA40 - 36 Span T1/E1 Circuit Network Adapter

550-01423

4

FRU Doc. CNA60 - High Density 3xT3 Circuit Network Adapter

550-00220

4

FRU Doc. CNA70 - Circuit Network Adapter

550-00302

1

FRU Doc. CNA80 - High Density 3xT3 Circuit Network Adapter

550-01424

1

FRU Doc. CNA81 - High Density Optical Circuit Network Adapter

550-01421

1

FRU Doc. CNS40 - 36 Span T1/E1 Circuit Network Server

550-01416

1

FRU Doc. CNS45 - 36 Span T1/E1 Circuit Network Server

550-01417

1

FRU Doc. CNS60 - High Density 3xT3 Circuit Network Server

550-00219

5

FRU Doc. CNS71 - Circuit Network Server

550-00299

3

FRU Doc. CNS80 - High Density 3xT3 Circuit Network Server

550-01419

1

FRU Doc. CNS81 - High Density Optical Circuit Network Adapter

550-01414

1

FRU Doc. CNS85 - High Density 3xT3 Circuit Network Server

550-01420

1

FRU Doc. CNS86 - High Density Optical Circuit Network Server

550-01415

1

FRU Doc. CPIM71 - Circuit Pluggable Interface Module

550-00301

2

FRU Doc. CPIM81 - Circuit Pluggable Interface Module for CNS86 and CNS81

550-01422

1

FRU Doc. Fan - Fan Tray

550-00014

5

FRU Doc. MNA10 - Management Network Adapter

550-00016

4

FRU Doc. MNA20 - Management Network Adapter

550-00634

2

FRU Doc. MNA21 - Management Network Adapter

550-00635

2

FRU Doc. MNA25 - Management Network Adapter

550-00831

2

FRU Doc. MNS20 - High Density Management Network Server

550-00633

6

FRU Doc. MNS21 - High Density Management Network Server

550-01814

4

FRU Doc. MNS26 –High Density Management Network Server

550-02871

1

FRU Doc. MTA10a - Management Timing Adapter

550-00093

3

FRU Doc. MTA20a - Management Timing Adapter

550-00094

3

FRU Doc. MTA21a - Management Timing Adapter

550-00087

4

FRU Doc. MTA30 - Management Timing Adapter

550-00304

2

FRU Doc. PNA10 - Ethernet Packet Network Adapter

550-00023

4

FRU Doc. PNA30 - Gigabit Ethernet Packet Network Adapter

550-00127

2

FRU Doc. PNA35 - Packet Network Adapter

550-00380

1

FRU Doc. PNS40 - Dual Gigabit Ethernet Packet Network Server

550-01119

4

FRU Doc. PNS41 - Dual Gigabit Ethernet Packet Network Server

550-01813

3

FRU Doc. PNA40 - Dual Gigabit Ethernet Packet Network Adapter

550-01120

4

FRU Doc. PNA45 - Dual Gigabit Ethernet Packet Network Adapter

550-01121

4

FRU Doc. SHF - 16-Slot GSX9000 Chassis

550-00013

8

FRU Doc. SPS70 - High Density Signal Processing Server

550-00297

4

FRU Doc. SPS80 - High Density Signal Processing Server

550-01418

2

FRU Doc. SHIELD – GSX9000 Protective Shield

550-01180

1

GSX4000 Field Replaceable Units

 

 

FRU Doc. GSX4010-CHAS_T1_E1_Chassis

550-00957

3

FRU Doc. GNS15_Gateway_Network_Server

550-00958

2

FRU Doc. GNA10_Gateway_Network_Adapter

550-00959

1

FRU Doc. GSX4000-FAN

550-00960

1

FRU Doc. GSX4000-FILTER

550-00961

1

FRU Doc. GSX4000-AC_DC_Power_Assembly

550-00962

2

Network File Server/DataStream Integrator Documentation

 

 

DSI Administration and Maintenance Guide, versionV09.00.00R000

550-05632

1

DSI Installation and Upgrade Guide (Solaris), version V09.00.00R000

550-05630

1

DSI Installation and Upgrade Guide (Linux), version V09.00.00R000

550-05631

1

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. For more information about these features, refer to the GSX9000 and GSX4000 Series Open Services Switch Operations Guide.
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 ManagerNational Communications SystemAttn: GETS Program Office701 South Courthouse Rd.Arlington, VA22204-2198Email:

Scripting Support - Optional Sonus SPE Software

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

Title

Sonus Part Number

SPE User Guide, Version V06.03.05

550-01243

SPE Version 06.03.05 Release Notes

550-02178

Unsupported GSX cards in Release V09.00.11R000

The following GSX cards are not supported in Release V09.00.11R000:

  • MNS11
  • PNS10
  • PNS20
  • PNS30
  • PNS30a
  • CNS20
  • CNS30
  • CNS30a

CNS10 and CNS25 Card Performance Advisory

The end of product life (EOPL) CNS10 and CNS25 cards (the "EOPL Cards") will execute R9 software subject to the following changes in performance characteristics and supportability:

  • Performance of R9-enabled EOPL Cards may be lower than the performance the customer observed with previous SW releases (for example R6, R7, etc.) on the EOPL cards
  • Performance of the cards may be lower than observed with other CNS cards (e.g. CNS40, CNS80, etc.) still in production.

Other software features newly introduced in R9 (that is not present in R7 or earlier releases) may not operate or operate correctly in an EOPL Card.

Sonus does not guarantee the availability or correct operation of these new features in an r9-enabled EOPL card, nor does Sonus assure repair of any such new features should the customer raise a trouble report.

Obtain the V09.00.11R000 software from Customer Software Bundle on the Sonus SalesForce Customer Portal under the WL 9.0 software bundle.

GSX Upgrade Paths

This section provides information on the supported and tested upgrade paths to the release version 09.00.11R000.

Caution
Note the following before performing LSWU:
  • If Layer3 IP redundancy is configured using OSPF, then OSPF mode must be set to PASSIVE mode prior to performing the Live Software Upgrade.
    In case OSPFv2 is being used for Layer 3 redundancy, the commands for setting the mode to passive are as the following:

    In case OSPFv3 is being used for Layer 3 redundancy, the CLI commands for setting the mode to passive are the following:

  • If the setup has SPS70, perform the following steps before performing the LSWU:
    • LSWU should be done on low call volume on the SPS70 cards. Alternatively, the SPS card should be dried up before initiating LSWU.
    • Before upgrading SPS70 card through LSWU from the older releases (07.0x.0x), assign Overload Profile to the SPS70 active slot. This Overload Profile ensures that SPS70 does not run out of memory. To configure the Overload Profile to SPS70 card, execute the following commands:

      The slot number can be between 3 and 16.

  • Once GSX is upgraded successfully, revert previously configured Overload Profile for SPS70 card by using the following command:


    If nothing was configured explicitly, set it to defaultSps.

  • Before upgrading a GSX with V09.02.04R000 release, the user should ensure that the existing configuration contains every NIF/SIF in exactly one NIF GROUP in an earlier software release.

  • The AMR and EFR VAD in case of LSWU for the stable call have VAD OFF for the upgraded version. By default, VAD will be ON for the new call.

  • A new input prefix value for IPv6 (IP6ADDRESS) is added to the GSX CLI. Ensure that all the configuration TCL files using short form for IP Address (i.e. "ip") need to either change it to "ipaddress" - denoting IPv4 address or, "ipv6address" - denoting IPv6 address.

  • Prior to performing the software upgrade from GSX Release 07.03.xx to GSX Release V09.02.04R000, ensure that the light gray policer is disabled on all the NIFs. Light Gray policer information is configured at NIF level and can be retrieved using the following command:

    For all the NIFs that have light gray policer enabled, use the following command to disable it:

    After the software upgrade is done, enable the light gray policer on all the NIFs for which it was disabled during upgrade. This can be done by using the following command:

Refer to the latest maintenance Patch Release Notes for the latest patch release version updates.

 

Supported GSX Upgrade Paths

This section provides information on the supported and tested upgrade paths in GSX Release V09.00.11R000.

Table : Supported GSX Upgrade Paths

Release

Series

Version

V09.00

R

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

 

F

V09.00.00F001
V09.00.02F001
V09.00.03F001, V09.00.03F002
V09.00.04F001
V09.00.05F001, V09.00.05F002, V09.00.05F003
V09.00.06F001, V09.00.06F003
V09.00.07F001, V09.00.07F004
V09.00.08F001
V09.00.08F002
V09.00.10F001

 

S

V09.00.02S001, V09.00.02S002

V08.04

R

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

 

F

V08.04.01F001, V08.04.01F002, V08.04.01F003, V08.04.01F004, V08.04.01F005, V08.04.01F006
V08.04.02F002, V08.04.02F003, V08.04.02F004, V08.04.02F005, V08.04.02F006
V08.04.03F001, V08.04.03 F002, V08.04.03F003, V08.04.03 F004, V08.04.03F005
V08.04.05F001, V08.04.05F002, V08.04.05F003, V08.04.05F004, V08.04.05F005, V08.04.05F006, V08.04.05F007, V08.04.05F008
V08.04.06F001
V08.04.08F001, V08.04.08F002, V08.04.08F004, V08.04.08F005
V08.04.10F001
V08.04.14F002

 

S

V08.04.04 S001, V08.04.04 S002, V08.04.04 S003, V08.04.04 S004

V08.03

R

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

 

F

V08.03.00 F001, V08.03.00 F002
V08.03.01 F001, V08.03.01 F002, V08.03.01 F003, V08.03.01 F004
V08.03.04 F001, V08.03.04 F002, V08.03.04 F003, V08.03.04 F004, V08.03.04 F005

V08.02

R

V08.02.01 R000

V07.03

R

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

 

F

V07.03.01 F001, V07.03.01 F002, V07.03.01 F003, V07.03.01 F004, V07.03.01 F005, V07.03.01 F006, V07.03.01 F007, V07.03.01 F008, V07.03.01 F009
V07.03.02 F000, V07.03.02 F001, V07.03.02 F002, V07.03.02 F003, V07.03.02 F004, V07.03.02 F005, V07.03.02 F006, V07.03.02 F007, V07.03.02 F008, V07.03.02 F009, V07.03.02 F010, V07.03.02 F011, V07.03.02 F012, V07.03.02 F013, V07.03.02 F014, V07.03.02 F015, V07.03.02 F016, V07.03.02 F017, V07.03.02 F018, V07.03.02 F019, V07.03.02 F020, V07.03.02 F021, V07.03.02 F022, V07.03.02 F023, V07.03.02 F024, V07.03.02 F025, V07.03.02 F026, V07.03.02 F027, V07.03.02 F028, V07.03.02 F029, V07.03.02 F030
V07.03.03 F001, V07.03.03 F002,V07.03.03 F003, V07.03.03 F004, V07.03.03 F005, V07.03.03 F006, V07.03.03 F007, V07.03.03 F008, V07.03.03 F009, V07.03.03 F010,V07.03.03 F011, V07.03.03 F012, V07.03.03 F013
V07.03.04 F001, V07.03.04 F002, V07.03.04 F003, V07.03.04 F004, V07.03.04 F005, V07.03.04 F006, V07.03.04 F007, V07.03.04 F008, V07.03.04 F009, V07.03.04 F010, V07.03.04 F011, V07.03.04 F012
V07.03.05 F001, V07.03.05 F002, V07.03.05 F003, V07.03.05 F004, V07.03.05 F005, V07.03.05 F006, V07.03.05 F007, V07.03.05 F008, V07.03.05 F009, V07.03.05 F010, V07.03.05 F011, V07.03.05 F012, V07.03.05 F013, V07.03.05 F014
V07.03.06 F001, V07.03.06 F002, V07.03.06 F003, V07.03.06 F004, V07.03.06 F005, V07.03.06 F006, V07.03.06 F007, V07.03.06 F008, V07.03.06 F009, V07.03.06 F010, V07.03.06 F011, V07.03.06 F012
V07.03.06 F013, V07.03.06 F014, V07.03.06 F015, V07.03.06 F016, V07.03.06 F017, V07.03.06 F018, V07.03.06 F019, V07.03.06 F020, V07.03.06 F021, V07.03.06 F022, V07.03.06 F023, V07.03.06 F024, V07.03.06 F025, V07.03.06 F026, V07.03.06 F027, V07.03.06 F031
V07.03.07 F001, V07.03.07 F002, V07.03.07 F003, V07.03.07 F004, V07.03.07 F005, V07.03.07 F006, V07.03.07 F007, V07.03.07 F008, V07.03.07 F009, V07.03.07 F010, V07.03.07 F011, V07.03.07 F012, V07.03.07 F013, V07.03.07 F014, V07.03.07 F015, V07.03.07 F016, V07.03.07 F017, V07.03.07 F018, V07.03.07 F019, V07.03.07 F020, V07.03.07 F021, V07.03.07 F022, V07.03.07 F023

 

S

V07.03.02 S001
V07.03.04 S001, V07.03.04 S002,V07.03.04 S003, V07.03.04 S004, V07.03.04 S005
V07.03.04 S100, V07.03.04 S101, V07.03.04 S102, V07.03.04 S103, V07.03.04 S104, V07.03.04 S105, V07.03.04 S106, V07.03.04 S107, V07.03.04 S108, V07.03.04 S109, V07.03.04 S114
V07.03.04 S200
V07.03.05 S402
V07.03.07 S001, V07.03.07 S002, V07.03.07 S003, V07.03.07 S004, V07.03.07 S005, V07.03.07 S006, V07.03.07 S007, V07.03.07 S008, V07.03.07 S009, V07.03.07 S010, V07.03.07 S011, V07.03.07S012

V07.02

R

V07.02.00 R000, V07.02.00 R001
V07.02.01 R000
V07.02.02 R000, V07.02.02 R001, V07.02.02 R002, V07.02.02 R003, V07.02.02 R004, V07.02.02 R005, V07.02.02 R006, V07.02.02 R007 V07.02.02 R008, V07.02.02 R009, V07.02.02 R010
V07.02.03 R000, V07.02.03 R001
V07.02.04 R000, V07.02.04 R001, V07.02.04 R002, V07.02.04 R003
V07.02.05 R000, V07.02.05 R001, V07.02.05 R002
V07.02.06 R000
V07.02.07 R000, V07.02.07 R001, V07.02.07 R002
V07.02.08 R000
V07.02.09 R000
V07.02.10 R000, V07.02.10 R001
V07.02.11 R000

 

F

V07.02.02 F003
V07.02.02 F001, V07.02.02 F002, V07.02.02 F004, V07.02.02 F005, V07.02.02 F006, V07.02.02 F007, V07.02.02 F008, V07.02.02 F009, V07.02.02 F010, V07.02.02 F011, V07.02.02 F012
V07.02.05 F001, V07.02.05 F002, V07.02.05 F003
V07.02.06 F001, V07.02.06 F002, V07.02.06 F003
V07.02.07 F001, V07.02.07 F002, V07.02.07 F003, V07.02.07 F004
V07.02.10 F001

 

S

V07.02.01 S001, V07.02.01 S002, V07.02.01 S003
V07.02.02 S301, V07.02.02 S302, V07.02.02 S303, V07.02.02 S304
V07.02.06 S001

V07.01

R

V07.01.00 R000, V07.01.00 R001, V07.01.00 R002, V07.01.00 R003, V07.01.00 R004, V07.01.00 R005, V07.01.00 R006
V07.01.01 R000, V07.01.01 R001, V07.01.01 R002, V07.01.01 R003, V07.01.01 R004. V07.01.01 R005, V07.01.01 R006, V07.01.01 R007, V07.01.01 R008
V07.01.02 R000, V07.01.02 R001, V07.01.02 R002, V07.01.02 R003, V07.01.02 R004, V07.01.02 R005, V07.01.02 R006
V07.01.03 R000
V07.01.04 R000, V07.01.04 R001, V07.01.04 R002
V07.01.05 R000
V07.01.06 R000, V07.01.06 R001, V07.01.06 R002, V07.01.06 R003
V07.01.07 R000
V07.01.08 R000
V07.01.09 R000
V07.01.10 R000

 

F

V07.01.00 F001, V07.01.00 F002, V07.01.00 F003, V07.01.00 F004, V07.01.00 F005, V07.01.00 F006, V07.01.00 F007, V07.01.00 F008
V07.01.01 F001
V07.01.02 F001, V07.01.02 F002
V07.01.03 F001, V07.01.03 F002, V07.01.03 F003, V07.01.03 F004
V07.01.04 F001, V07.01.04 F002, V07.01.04 F003, V07.01.04 F004
V07.01.06 F001, V07.01.06 F002, V07.01.06 F003
V07.01.07 F001, V07.01.07 F002, V07.01.07 F003

 

S

V07.01.04 S001, V07.01.05 S001, V07.01.05 S002
V07.02.02 S301, V07.02.02 S302, V07.02.02 S303, V07.02.02 S304

The highlighted upgrade paths are explicitly tested by Sonus.

RTCP must be disabled before upgrading from GSX release V08.03.04R000 to V09.00.11R000.

 

GSX Upgrade Path Exceptions

This section lists the release versions that are not merged with the GSX 09.00.11R000 release. Refer to the latest maintenance Patch Release Notes for the latest patch release version updates.

Release

Series

Version

V08.04

F

V08.04.03 F003, V08.04.03 F004

GSX Interoperability Matrix

For information on the product interoperability with GSX Release V09.00.11R000, see "Sonus Product Compatibilities" at https://support.sonus.net/display/ALLDOC/Sonus+Product+Compatibilities.

Upgrade Notes

This section describes upgrade notes for this release.

Master Trunk Group Upgrade Procedures


Pre-requisites before upgrading

MTRM need not be turned off unconditionally. If you are using release V07.03.07R008 or later or V08.04.05R000 or later which contain the MTRM updates, you can upgrade to V09.00.10 without changing the MTRM configuration.

The following steps must be performed before upgrading to V09.00.11R000.

  1. Disable all MTRM functions (for example, remove MTRG from IPTG configuration) and readjust IPTG local resource pool, if necessary.
    1. Increase the CAC limit for IPTG (if required).
    2. Remove all IPTG associations by using the following command:

CONFIGURE TRUNK GROUP <IPTG Name> TRUNK GROUP NONE

  1. Delete Master Trunk Group configuration by using the following commands:

CONFIGURE MASTER TRUNK GROUP <Master Trunk Group Name> MODE OUTOFSERVICE
CONFIGURE MASTER TRUNK GROUP <Master Trunk Group Name>STATE DISABLED
DELETE MASTER TRUNK GROUP <Master Trunk Group Name>

  1. Delete Master Trunk Group connection port by using the following commands:

CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 MODE OUTOFSERVICE
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 STATE DISABLED
DELETE MASTER TRUNK GROUP CONNECTION PORT 1

  1. All IPTGs operate in their local capacity with no MTRM resource management.
  2. Upgrade each GSX9000/SBC 9000 using the normal procedure.
  3. No explicit LSWU support for ICM messages as all MTRM functions are shut down.

Post-upgrade Procedures
The following steps must be performed after upgrading to V09.00.11R000:

  1. Create and enable all connection ports using the following commands:

CREATE MASTER TRUNK GROUP CONNECTION PORT 1 ROLE SERVER
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 IPADDRESS <Connection Port IP> INTERFACE <Interface Name>
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 MODE INSERVICE
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 STATE ENABLED
CREATE MASTER TRUNK GROUP CONNECTION PORT 2 ROLE CLIENT
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 2 IPADDRESS <Connection Port IP> INTERFACE <Interface Name>
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 2 MODE INSERVICE
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 2 STATE ENABLED
CREATE MASTER TRUNK GROUP CONNECTION PORT 1 ROLE CLIENT
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 IPADDRESS <Connection Port IP> INTERFACE <Interface Name>
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 MODE INSERVICE
CONFIGURE MASTER TRUNK GROUP CONNECTION PORT 1 STATE ENABLED

  1. Create and enable all master trunk groups. Configure the role as client/server using the following commands:

CREATE MASTER TRUNK GROUP SERVER <Master Trunk Group Name>
CONFIGURE MASTER TRUNK GROUP SERVER <Master Trunk Group Name> CONNECTION PORT INDEX 1
CONFIGURE MASTER TRUNK GROUP SERVER <Master Trunk Group Name> mode in
CONFIGURE MASTER TRUNK GROUP SERVER <Master Trunk Group Name> STATE ENABLED
CREATE MASTER TRUNK GROUP CLIENT <Master Trunk Group Name>
CONFIGURE MASTER TRUNK GROUP CLIENT <Master Trunk Group Name> CONNECTION PORT INDEX 2
CONFIGURE MASTER TRUNK GROUP CLIENT <Master Trunk Group Name> MODE INSERVICE
CONFIGURE MASTER TRUNK GROUP CLIENT <Master Trunk Group Name> STATE ENABLE

  1. Configure all IPTG associations using the following command:

CONFIGURE TRUNK GROUP sipDefault MASTER TRUNK GROUP <Master Trunk Group Name>

  1. Create co-resident client connection ports, if necessary.
  2. Create co-resident client Master Trunk Groups, if necessary.

 

CAM/CDR Field Changes

No CAM/CDR field changes in this release.

NIF Group

In release V09.00.11R000, each NIF/SIF must be in one single NIF GROUP.
CAUTION: Before upgrading a GSX with V09.00.11R000 release, check if both NIF/SIF are in one single NIF GROUP (in previous releases).

Changes in Default Behavior

This section describes the changes made that affect the default behavior of the GSX.

  • Out of Dialog Refer will be routed by default if PSX has appropriate route. This behavior is not configurable and is available by default. In prior releases, we used to reject such a Refer.
  • Changes in Default DNS behavior:
    • DNS Servers will now be attached to a Zone. The default Zone of a newly created DNS Server is INTERNAL. Also, after an upgrade, existing DNS Servers will belong to INTERNAL Zone.
    • Configuration of more than 8 DNS Servers is supported in this release. However, maximum number of DNS Server supported per Zone is 8.
    • RFC5452 support:
      • Source Port of DNS queries will be randomized. The port rollover happens every 60 seconds.
      • Query ID of the DNS message will be randomized (all 16 bits).
      • DNS query responses will be subject to Query Matching Rules and will be dropped if the query matching fails. No update to local DNS Records cache will be made in this case.
  • It is no longer possible to configure one NIF/SIF in multiple NIF Groups.
  • In Local Policy mode, GSX will not relay in-dialog Refer and GSX would process and act on this Refer if Refer relay is not enabled.
  • PNS41 card supports a maximum of 20000 Relay Dialogs (REFER/SUBSCRIBE/OOD messages).
  • SBC will be compliant with RFC 3261 by mapping the 503 response code received on the egress call leg to 500 response code onto the ingress call leg for initial INVITE and REGISTER messages.

 

GSX CDR Streaming Configuration

When using the CDR streaming feature, one DSI can support live event/CDR data streaming from multiple GSXs. This means that during LSWU a DSI must be able to support multiple CAM versions, from multiple GSX devices running different CAM versions. Therefore, to ensure correct behavior during GSX upgrade, you must upgrade the active and standby DSI devices and load the correct streaming configuration files onto the DSIs before upgrading the GSX.
If the GSX is being upgraded as a part of a major planned release, then it is very likely that DSI too has been upgraded to the same release. When the DSI upgrade is complete, all the selectable CDR configuration files—both old and new—that are needed to support the GSX should be present on the DSI.
However, if the GSX is being upgraded in association with a specific GSX maintenance release, there may not be a planned DSI upgrade. It is especially important in this case to confirm dependencies of the new GSX maintenance release for possible new and required DSI selectable CDR configuration files to support the GSX maintenance release. Make sure that the selectable CDR streaming configuration files for the old and new CAM versions are present on the DSI before LSWU of GSX devices. If the specific required selectable CDR configuration file is not present on the DSI servers, then upgrade must be postponed until the necessary configuration files can be obtained and loaded on the DSI servers.
For V09.00.11R000, ensure this additional selectable CDR streaming configuration file is present on the DSI servers:
BCAMSelRecord.gsx.76.0.0.stream_config
This file may be found in the /export/home/dsi/files directory on the DSI server along with the similarly named file(s) for whichever version(s) of GSX CAM is/are presently being supported before upgrade of the GSX. If this file is not present, you should contact Sonus TAC to get the necessary configuration files to support your upgrade.

GSX Firmware Versions

The following GSX firmware versions are currently recommended for the following card types:

Card

Binary Name

Version

MNS20, MNS21, MNS26

mns20b.bin

V01.20.00R002

CNS8x, CNS4x, SPS80

cns80b.bin

V01.16.00R001

PNS40, PNS41

pns40b.bin

V01.18.00R006

GNS15

gns15b.bin

V01.14.00R007

All others (default)

N.A.

V01.12.00R003

Sonus recommends that you perform firmware upgrades during a low-volume maintenance window, and refrain from disturbing the system during the upgrade.

 

Firmware V01.20.00R002

Firmware (flash) version V01.20.00R002 is recommended for the MNS20, MNS21and MNS26.

Firmware V01.16.00R001

Firmware (flash) version V01.16.00R001 is recommended for the CNS86, CNS81, CNS85, CNS80, CNS40, CNS45, and SPS80. This version disables ECC HW circuitry, which has been found to cause erroneous software problems on rare occasions.

Firmware V01.18.00R006

Firmware (flash) version V01.18.00R006 is recommended for the PNS40, and PNS41. This version adds support for new server module types for the GSX and other Sonus products.

Firmware V01.14.00R007

Firmware (flash) version V01.14.00R007 is recommended for the GNS15. This version disables HW ECC circuitry, which has been found to cause erroneous software problems on rare occasions.

Firmware V01.12.00R003

Firmware (flash) version V01.12.00R003 is recommended for the all other GSX server module types.

Software Upgrade Considerations

Consider the following issues when upgrading to this release.

PSX Device Profile

The Device Profile object on the PSX Policy Server is not supported by the GSX in this release. Endpoint registration timeouts must now be specified on the GSX SIP Service object.
To specify the timeout for the default SIP registration keepalive mechanism, use the following command:
CONFIGURE SIP SERVICE <sipservice_name> REGISTRATION MAXEXPIRES
To enable the protocol-specific timeouts for registrations established over TCP or UDP connections respectively, use the following commands:
CONFIGURE SIP SERVICE <sipservice_name> REGISTRATION MAXEXPIRES NATOVERTCP
CONFIGURE SIP SERVICE<sipservice_name> REGISTRATION MAXEXPIRES NATOVERUDP
To enable non-nat timeouts, use the following command:
CONFIGURE SIP SERVICE <sipservice_name> REGISTRATION MAXEXPIRES NONNAT
For more information on this feature,refer to "SIP Service" section in GSX9000 and GSX4000 Open Services Switch Operations Guide (550-05375).

Overload Control Profile Settings

The following releases and later support the System-Level Adaptive Overload feature: V06.04.02R000, V06.05.00, V7.x (all), and V08.04.04R000.

The MC3 overload profile call rate default is now set = 0 for new installations (per SONUS00040601).Existing customers who upgrade to this release must manually set the call rate set/clear thresholds to 0 in the default MC3 overload profile.

For more information on the Overload Profiles, refer to the "Congestion Control" section in the GSX9000 and GSX4000 Open Services Switch Operations Guide (550-05375).

 

IP Filters

Link integrity checking requires that ICMP replies from the next hop peer be allowed into the GSX. You must verify that there are no IP filters that would discard such replies. Otherwise, the link will be declared as unavailable and, if so configured, the card will switch over. The IP filter configuration should be checked even if link integrity is currently working, since a bug that incorrectly permitted ICMP replies through (SONUS00059718) has since been corrected.

IP Path Routing

As of release 6.3, the GSX enforces the correct path routing for signaling. In most cases this is fully backward-compatible for existing deployments. However, in releases prior to 6.3, SIP or Gateway signaling port configurations were allowed to be inconsistent with the IP routing tables. If SIP or Gateway signaling ports are configured to use a PNS interface, IP route table entries must direct SIP or Gateway signaling packets to a PNS NIF. Check your routing configuration before you upgrade.

New Default Value for Bandwidth Request Variable

The default value of the MIB variable sonusTgMtrgBWPerReq (range 2480 to 248000 in units of 1K bits per second) and the Trunk Group parameter "mbwperreq" was changed to 12400 in GSX 6.1 and later. TRM requests more bandwidth when the available trunk group (IP type MTRG) bandwidth is <1x this value, and frees bandwidth when the available bandwidth is >2x this value.

Default Carrier Codes

The default carrier codes for trunk groups are configured on the PSX, and not on the GSX.

Logical Signaling Addresses and ARP Requests

The 'ARPable logical address' feature introduced in 6.x allows configuration of signaling addresses (SIP/GW/H323) in the same subnet as packet NIFs, and expect GSX to respond to ARP requests for those addresses with appropriate ARP replies. By default ARPable logical address feature is disabled. Therefore, if logical signaling addresses are already in the same subnet as packet NIFs (in prior releases), the GSX does not automatically respond to ARP requests when upgrading to this release.

New Features and Modifications

New Features and Modifications in V09.00.06R000

The following new feature is included in this release:

  • IPV6 Link Local Nexthop Support

IPV6 Link Local Nexthop Support

With the current implementation, GSX was unable to use Link-Local Nexthop for IPv6. Support has been added to configure IPv6 Link Local address as Nexthop in static routes configured on MGMT NIF/NIF/SIF.

New Features and Modifications in V09.00.05R000

The following features are included in V09.00.05R000 release:

  • End to End ACK
  • Need alarm off Dynamic Blacklist Entry

End to End ACK

As per the current behavior of GSX, receiving a "200 OK" from a SIP side is responded with ACK almost instantaneously. This can cause inconsistencies in billing of the call if the ACK from other side has not been received yet.
As part of this feature, the behavior of sending an ACK to be End to End is implemented, i.e.; if configured, receiving a "200 OK" from Egress side will not be responded with ACK until an ACK is received from Ingress side.
This configuration is a flag in PSX: 'End to End Ack' in Egress IPSP of Ingress Trunk Group.

  • If the flag is enabled, the behavior will be End to End.
  • If the flag is disabled, the current behavior prevails, i.e.Instantaneous ACK will be sent on receiving "200 OK". This is also the default value.

    This behavior/feature is valid only for initial INVITE of the call.

Need alarm off Dynamic Blacklist Entry

Currently, there is no way to easily get the status of a dynamic blacklisted entity since there is no alarm generated and no log entry unless on INFO level logging.
This feature introduces a new SNMP trap, which is generated when DBL watch or blacklist threshold for an endpoint is reached. This trap will get generated every time a new EP is identified for Dynamic Blacklisting and will be delivered in best effort basis. The trap will also get logged in SYS logs at MAJOR level.
Following are the trap parameters:

  • Endpoint IP
  • Slot
  • Port
  • LIF Index
  • SIP service group name
  • DBL profile name
  • DBL threshold
  • Blacklist/watch duration
  • Reason (invite malformed or register authentication failure)

New Features and Modifications in V09.00.04R000

The following features are included in V09.00.04R000 release:

  • Porting GSX Tools to Lintel platform
  • Lawful Intercept, RADIUS message buffering limitation removed
  • AIS TIMER Call Drop
  • GSX discards SID or CN Packets with Payload Size Greater than 10 Bytes
  • RFC 5806 not followed for a Single Diversion Header
  • Call Flow Transcoding fails between Inband and 2833

This feature enhances the support of PIF tool and verifyAnnFile for DSI box (Linux).

  • PIF Tool: This tool (compiled and linked with snPifLib.a) allows a user to perform a variety of operations on a PIF file. Syntax: piftool <mode> <param file> [ <text file> ] [ <options> ]

    Mode

    Description

    read

    Read a PIF file and dump all objects as parsable records.

    browse

    Dump contents of parameter file in a form suitable for browsing.

    summary

    Dump summary of data from Sonus header and PIF header and trailers.

    checksum

    Reads parameter file to determine if file-wide checksum is valid.

    version

    Print Sonus software version that generated schema.

    genkey

    Produce MD5 key that uniquely identifies a schema.

    schema

    Schema Details.

    Option

    Description

    -flat

    When used in conjunction with "read" mode, it produces flat (non-hierarchical) output.

    -onlyobj

    Confine read/browse to loading specified obj-id or name.

    -fieldcopy

    When reading from file, copy "object" fields using PIF COPY API. This copies the field data into the space specified, otherwise, the PIF GET API is used which allocates memory and returns the value.

    -enumerations

    Translate numeric enumeration values into their textual form.

    -fieldasnnames

    Translate numeric field IDs into their associated MIB object names.

    -objnames

    Print textual name of object type.

  • verifyAnnFile: This tool allows a user to verify user created announcement files.

Syntax: verifyAnnFile <wave file> [<-v>]

Lawful Intercept, RADIUS message buffering limitation removed


GSX uses packet cable PKT-SP-EM-I07-030815 specification to send LI message to the mediation device. This specification uses RADIUS Accounting protocol. RADIUS Accounting protocol is based on client/server model with the client sending a request and server sending a response to it. The GSX has a frame work, where it sends a LI message as a request and waits for a response before it sends the next message (request). The framework allows only one outstanding message at a time. If there are multiple messages to be sent, then the message are buffered and sent one by one.
The GSX was buffering a maximum of 256 messages when there is a burst of LI RADIUS messages that need to be sent. With this feature, this limit is removed and the GSX will buffer as many messages (more than 256) that need to be sent to the LI server.

Currently, in the event of a fiber cut, the GSX declares AIS alarm on the E1s that are multiplexed within the fiber before the Automatic Protection Switching completed, thereby failing all the calls carried by the affected E1s.  GSX has an AIS timer hardcoded at 100 ms as verses 2.5 s, resulting in bringing down the E1 port in 100 msec. The AIS timer expires in 100 msec and the ports (E1 ports) are brought down.  The stable calls are cleared.
PCR 8172 addresses the configuration requirements for AIS timer providing flexibility for the customer to be able to configure AIS timer through CLI commands without bringing down the E1 ports.
As part of this PCR a new configurable control under E1 is introduced, which provides choice to the customer to choose between timer option values 100ms and 2500ms.
The CLI command is as follows:
CONFIGURE E1 <e1> AISTIMER
<millisec100> <millisec2500> 
The default value for AIS Timer is <millisec100> value.
A new configurable control under E1 is introduced, which provides choice to customer to choose between timer option values 450ms and 2500ms.
The CLI command is as follows:
CONFIGURE E1 <e1> RAITIMER
<millisec450> <millisec2500> 
The default value for RAI Timer is set as <millisec 450> value.

In order for GSX to declare AIS alarm on the E1s in 2.5 seconds, both AIS and RAI timers must be configured to value of millisec 2500.

 

GSX discards SID or CN Packets with Payload Size Greater than 10 Bytes  

Currently, GSX had a restricted SID payload size of a maximum of 10 bytes (1 byte of noise level and 9 bytes of reflection co-efficient). Any SID payload whose size is greater than 10 bytes gets dropped and DSP does not generate corresponding comfort noise.
This feature addresses the issue by increasing the maximum SID payload size supported to 36 bytes. This fix is applicable on VPAD resources on CNS cards.

 

Sonus proprietary SID is no more supported.

 

Currently, on receiving a SIP INVITE with a single diversion header for a SIP to ISUP/ISDN/SIP-I call, the Diversion header was mapped to both the Redirecting Number and Original Called Number on the egress leg. This conflicts with RFC 5806, which describes the interworking between SIP-ISUP.
As part of this feature, a new flag is introduced in the SIP Service to control the new behavior:

  • CONFIGURE SIP SERVICE <ingress-sip-service> POPULATE ONLY_RN FOR SINGLE DIVERSION HEADER ENABLED
  • CONFIGURE SIP SERVICE <ingress-sip-service> POPULATE ONLY_RN FOR SINGLE DIVERSION HEADER DISABLED

The flag status can be checked using: SHOW SIP SERVICE <text> ADMIN
By default, this flag will be disabled and the behavior will be the same as prior to this feature.
Whereas, on enabling this flag, if a single Diversion header is received in the SIP INVITE, this will be matched only to the Redirecting Number and not to the Original Called Number.

Call Flow Transcoding fails between Inband and 2833 

While bridging two legs for Two B-channel Transfer (TBCT) (ISUP-A ---->GW1<>GW2 --ISDN-> ISDN-B-->SIP-C), if original call legs do not have DRES (XPAD/PXPAD), GSX will now bring in new DSP resource for the bridged call legs. It will perform transcoding between In-band DTMF and 2833 DTMF based on the options selected in GW PSP.

Support for MAJOR logs to Notify Media Failure due to unreachability of Nexthop


This feature addresses the need to change the log level of two of the existing logs from MINOR to MAJOR.

New Features and Modifications in V09.00.03R000

The following features are included in V09.00.03

  • PCR 8380- CRG Message Propagation
  • LCQ 8397- Called Number incorrect SIP Redirect is followed by ISUP Redirect
  • PCR 8260-GSX CANCEL behavior for SIP-T
  • LCQ 8450- Need alarm off Dynamic Blacklist Entry
  • PCR 8817-GSX, SBC Gateway - Gateway Support for the PCRs 7643 and 6896
  • PCR 8095&8096: ISDN Progress Indicator parameter and STATUS message issue
  • PCR 8559- Enhancements to GSX-DSI fail-over mechanism in degraded IP NW conditions

PCR 8380 – CRG Message Propagation

Currently, the Charge Message Propagation flag in the Signaling Profile screen on the PSX is not used if there is no Charge Band Entry configured.
This PCR allows for the charge message propagation control to be passed back in the policy response even when the charge band information is not provisioned/present. This allows the operator to specify that the CRG message in India can be propagated even though the charge band is not provisioned.

LCQ 8397 -Called Number incorrect SIP Redirect is followed by ISUP Redirect

Currently, in a call scenario where a SIP redirection is followed by ISUP redirection, the Called Directory Number sent in the final IAM contained the original called number from the first IAM instead of the called number from the Intermediate (second) IAM. LCQ 8397 addresses this problem by setting the Called Directory Number to the Called Number from the Intermediate (second) IAM.

PCR 8260 - GSX CANCEL behavior for SIP-T

Currently GSX can generate CANCEL method for INVITE before receiving 100 Trying for SIP-T. This is not compliant with the SIP standard RFC3261, but it is intended for SIP-T/ISUP.
The requirement is to provide a flag to disable the current behavior (generate CANCEL immediately) and wait for 100 Trying back from the peer before issuing a CANCEL.
A Flag called "Enable 3261 Cancel Handling" is added in "IP Signaling Profile" under "Egress IP Attributes" -> Flags.

  • When this flag is enabled, it indicates to the gateway initiating an INVITE that it can only send a SIP CANCEL after receiving a SIP provisional response i.e. SIP CANCEL must conform to RFC3261.
  • When this flag is disabled, this constraint does not apply and the CANCEL can be sent anytime. This is the default behavior.

LCQ 8450 - Need alarm off Dynamic Blacklist Entry

Currently, there is no way to easily get the status of a dynamic blacklisted entity since there is no alarm generated and no log entry unless on INFO level logging.
LCQ 8450 introduces a new SNMP trap, which is generated when DBL watch or blacklist threshold for an endpoint is reached. This trap will get generated every time a new EP is identified for Dynamic Blacklisting and will be delivered in best effort basis. The trap will also get logged in SYS logs at MAJOR level.
Following are the trap parameters:

  • Endpoint IP
  • Slot
  • Port
  • LIF Index
  • SIP service group name
  • DBL profile name
  • DBL threshold
  • Blacklist/watch duration
  • Reason (invite malformed or register authentication failure)

 

PCR 8817-GSX, SBC Gateway - Gateway Support for the PCRs 7643 and 6896

PCR 8817 addresses the following two issues with GW-GW call using GSX 9.0.x release and SBC 4.0 release.
In SIP to SIP call, when GSX receives JIP (Jurisdiction parameter) in INVITE, GSX drops JIP field's country code and global number flag, so SBC does not send these fields in the JIP parameter of egress INVITE.
In SIPI to SIP call, when GSX receives INVITE with SGD in IAM MIME and PSX flag "Map SGD digits to P-SIG-INFO header" is enabled, GSX fails to send the PSX indication "Map SGD digits to P-SIG-INFO" to SBC via GW-GW. SBC does not send P-SIG-INFO header with SGD in egress INVITE.
The mentioned issues are due to the down conversion routines of GSX. These conversion routines are updated to make the above scenarios work in GSX, SBC GW-GW calls.

PCR 8095&8096 - ISDN Progress Indicator parameter and STATUS message issue

As part of PCR 8095 & PCR 8096 the following issues have been addressed.

  • GSX currently does not add progress indicator=#8 to ALERT message receipt upon ACM/CPG in some cases. Some PBX cannot open its voice path without receiving progress indicator #8 in ALERT message. In that case, caller (ISDN user) will be connected to callee without hearing the ring back tone.
  • When GSX sends SETUP message with Cause of no ID parameter for TTC-ISUP, some PBX send back STATUS message as correct response since they do not support to receive the Cause of no ID parameter. GSX should not echo back STATUS message when it get STATUS message. This results in tearing down the call by some PBX.

The following fix has been provided and the behavior after the PCR changes is as follows.

  • Upon receiving the ACM/CPG for the JAPAN PRI to TTC ISUP, these scenarios are reported as an issue. GSX shall support sending out progress Indicator set to PI=#8 in ALERT message on the ISDN PRI.
  • For this TTC-ISUP to Japan PRI call scenarios reported, when GSX receives the STATUS message back from PBX, GSX shall consume the STATUS message received and shall not echo back STATUS message to PBX.
CLI Configuration

A new configurable control under ISDN SERVICE will be introduced which will take care of whether the requirements will be enabled and will ensure backward compatibility. A new CLI configuration will be introduced under ISDN SERVICE to enable the requirements for restricting echoing of the status message .This will ensure backward compatibility for the status echoing behavior.

Default configuration and command


CONFIGURE ISDN SERVICE isdn_se SEND PROGRESS INDICATOR INBAND IN ALERT
<supported> <unsupported> 
CONFIGURE ISDN SERVICE isdn_se RESTRICT ECHOING STATUS MESSAGE
<supported> <unsupported> 
Default shall be  set as "unsupported".

PCR 8559: Enhancement to GSX-DSI fail-over mechanism in degraded IP NW conditions

This PCR describes the implementation of the functionality of GSX NFS related software. Currently, in case of degraded IP NW scenarios, GSX receives TIMEDOUT errors and the write operation to active NFS fails. When this network impairment persists, CDR records are dropped as GSX fails to notice anything wrong with the network and continues to send data to active NFS.
In order to enhance the response of the external N/W. GSX NFS module functionality is enhanced to keep track of the number of non-fatal NFS. NFS Switchover is performed when the following conditions are met.

  1. When the number of non-fatal write-timeouts reach "x" within "y" seconds threshold.
  2. Secondary NFS is tested to be ready. Secondary NFS is tested periodically at the interval of 15 seconds.

If secondary NFS is also bad at this time, the switchover is avoided and the current NFS is used. An NFS switchover failure trap is generated for this condition.EMS support for the traps will be provided in future.

When the secondary link shows the same degraded N/W behavior then a problem is reported.

Additional implementation of a new feedback mechanism for the dropped packets to the NFS FSM is currently not considered as part of this document.

Newly added CLIs:

configure nfs  shelf  1  timeout period   <in secs>                
configure nfs  shelf  1  timeout threshold <>
configure nfs  shelf  1  timeout state enabled
Show nfs shelf 1 timeout admin
Show nfs she 1 timeout stats

Newly added trap:

NFS_SWITCHOVER_FAILURE( ULONG prevActiveServer, ULONG newActiveServer,
SOCKADDR serverIp, STRING serverMount, ULONG reason)

Enhanced existing trap:

NFS_SWITCHOVER( ULONG prevActiveServer, ULONG newActiveServer,
SOCKADDR serverIp, STRING serverMount, ULONG reason)
New value for reason: sonusNfsReason_serverLinkNotStable

New Features and Modifications in V09.00.02R000

The following features have been added in GSX V09.00.02

  • PCR 7117 –BTIUP to mime Interworking
  • LCQ 8667- SIP ONHOLD/OFFHOLD Race Condition Issues

PCR 7117- BTIUP to UKISUP mime Interworking.

This PCR addresses the need to enhance the GSX9000 to interwork between BT IUP to SIP-I(UK-ISUP) using GW-GW SBC5200 on the other side.
ISUPSG module has been updated for BT IUP changes on GSX. SS7LIB modules have been updated for the SIPI (UK ISUP) interworking on SBC.
ISUPSG parses the BT IUP messages and BT IUP parameters get mapped to internal CPC parameters. The whole IUP payload is tunneled to the egress SG and far side/egress ISUP SG maps BT-IUP payload to an ISUP payload.
In order to make this work over SIP-I, IUP payload has to be mapped to CPC parameters along with the bit bag and transported over Gateway.
For interworking between SIP-I (UKISUP) terminated on SBC5200 and IUP on the GSX using GW-GW, SBC5200 shall support encapsulating the whole UK-ISUP mime payload.
SBC5200 will also support new interworking functions to use the BT ISUP raw payload received from the other side to create the ISUP MIME in the SIP SG context instead of directly calling the existing generic library processing functions.

LCQ 8667 - SIP ONHOLD/OFFHOLD Race Condition Issues

With the current implementation, call on-hold/off-hold may teardown due to internal SDP offer/answer race conditions. Sometimes additional on-hold is generated while the call is already on-hold. LCQ 8667 addresses this issue such that additional on-hold is not generated while the call is already on-hold to prevent race conditions.

New Features and Modifications in V09.00.01R000

The intent of 9.0.1 release is to qualify GSX4010 platform on V09.00.0R000 software code.

 

For a summary of features in the base release V09.00.00R000, refer to the GSX V09.00.00R000 release notes, Sonus part number 550-05636.

 

In this release the following GSX4000 features and functionalities are not supported:

  • ACLs, IP input filters
  • NICE recording
  • IPv6
  • IPSec
  • Wildcard Policers
  • Local disk support for GNS
  • PK headers
  • Registration admission control
  • Call Park/pickup changes (P2P)
  • SIP over SCTP and SCTP
  • Conformance to SIP Connect, Comedia
  • REFER in P2P scenarios
  • SIP Registration Fraud
  • SIP-I to SIP-I flows
  • SIP over TLS
  • SIP Transparency
  • H323 to SIP/SIP-H323 interworking
  • SUBSCRIPTION Relay
  • Direct Media (in P2P flows involving both SIP and H323)
  • RCS
  • DOS protection
  • Any ASX to Any SBC (Any to Any)
  • NAT/NAPT
  • Endpoint CAC
  • Policers TG based, per VLAN
  • SIP Registration
  • SIP-SIP
  • ISUP – SIP-I
  • PER 4062 - Minimize Media Changes Flag changes
  • PCR 2366 - Trigger conditional transcoding when payload types are different
  • PCR 3289 Existing DOS protection testing
  • PCR 4042 - Maintain From tag for register after 401
  • PCR 4044 - ITX / TXA Spirou message support and logged in CDRs
  • PCR 5139 Add NAPT handling cases for which NAT usage cannot be determined

 

Problems Resolved

GSX 09.00.11R000 Problems Resolved

The following are the issues fixed in GSX V09.00.11R000. The implications of not upgrading to include a particular fix have been provided where appropriate:

Issue ID

Severity

Category

Problems Description

Resolution

GSX-39984

3

SIP

CDR Ingress IP Circuit End Point 0.0.0.0 for Full Late Media Call 100rel.

TO fix this issue a new function has been introduced in SIPSG which sends the Ingress IP to CC for late media calls.

GSX-43366

2

Statistics

Statistics 'Max & Total Packet Outage' are reporting abnormal value.

The debug logs have been modified to fix the issue.

GSX-51066

2

Platform

After upgrading, unable to add nif subinterface in NIFGROUP.

The code has been modified to properly sync up the nifgroup count after the GSX is restarted or upgraded.

GSX-51067

3

GSX9K

Doc change request - Request for removing some obsolete traps for ARS.

Few obsolete traps of ARS were deprecated.

GSX-51941

2

GSX9K

NRMA is unable to handle some specific call flow and NrmaDetermineModifyServiceCmdOfferActions() returns NRMA_ALLOC_REJECTED.

The code has been modified to handle egress reverse offer case of H323.

GSX-51963

2

SIP

SBC9000: CIT param is not exist on ACM MIME of 180.

The code has been modified to fix this issue, ported the Fix from SBX-10607 (SONUS00128838).

GSX-52001

3

CLI, Documentation

The CONFIGURE SIP SIGNALING REGISTRATION REGISTRAR command is deprecated and is no longer in use. But CLI still shows REGISTRAR configuration and deletion options.

The registrar related code has been removed.

GSX-52110

3

Coredump

GSX coredumps when extended ASCII characters are encountered in SIP signaling.

The code has been modified to fix this issue.

GSX-52395

3

GSX9K

CDR packets lost and packet outage sometimescontain random values.

The packet outage computation for single packet received cases has been modified to address this issue and also made some enhancements to media metrics monitoring code.

GSX-52423

2

GSX9K

Local egress Signaling IP has unspecIP instead of valid IP address in CDR

The code has been modified to convert unspecIP & nullIP to empty.

GSX-52434

2

SIP

ISUP to SIP Interworking for one diversion sets the wrong redirection reason. In an ISUP-> SIP interworking situation where the ISUP IAM contains the Redirecting Number, Original Called Number, Redirecting Reason and Original Redirecting reason for a case where one a single diversion has taken place, the Original Called Number and Original Redirecting Reason are used to map into the SIP diversion header.

The code has been modified such that when there is one diversion then the reason for diversion will be taken from redirection information.

GSX-52540

2

GSX9K

Enabling the fourth NIF interface leads to GSX rebooting and coring both MNS slots. In case of duplicate routes on different interfaces, only route with lowest preference is added to radix tree (which also adds radix mask to the mask tree) and remaining routes are maintained in the list. Masks for these routes in the list is not stored in radix node. So when the head route is deleted from radix tree and the next route is added in the list to the radix tree, the mask value or mask of zero is not being used to insert this. Hence these routes were not getting deleted.

The code has been modified and optimized to use the mask of head route when it is being deleted from radix tree while inserting the next route in this list, so that mask is preserved for all routes.

GSX-52624

2

Coredump

CNS60 Core dumps with error code 0x00000070.

The structure variable is made NULL after free, since it results in dangling pointer when it is used in respected functions.

GSX-52625

2

SIP-I

SBC9000 does not send 18x (ACM) until receiving 200 OK (ANM) from the succeeding office if INVITE (IAM) from the proceeding office is 64K unrestricted or SIP-Payload is clearmode.

Introduced a new flag for data calls. This flag is set for data calls when 18x is received.

GSX-52824

2

Coredump

Due to a memory leak observed in CPC and SIPSG modules, multiple PNS cards were coring at multiple sites.

The code has been modified to free an unfreed pointer to fix the memory leak.

GSX-52889

2

Platform

Server module software failure in shelf 1 slot 15 CNS 86 with error code 0x00000021.

The code has been modified to fix this issue.

GSX-52896

2

SIP

GSX-38486 breaks all VSC calls.The SIP trunk has "allow VSC enabled", but when an invite is received with in the request, GSX sends back 400 (Bad request).

The code has been modified to fix this issue and removed changes done as part of GSX-38486.

GSX-52898

2

DSP

For IP to PSTN call, if a modem tone is detected during Inband DTMF generation it results in corrupted DTMF digits.

The code has been modified to fix this issue.

GSX-52918

3

DSP

Check-sum enhancement on VPAD.

The code has been modified to enhance the checksum repair functionality.

GSX-52924

2

CLI

Logical mgmt IP not working for SNMP requests.

The code has been modified to fix this issue.

GSX-52947

2

Coredump

CNS71 cored in ISDNSG.

GSX cored when it accessed an unexpected NULL pointer while printing a log message.
Code has been modified to fix this issue.

GSX-53052

3

ISUP

Invalid Location Number NPI prints wrong UPV log.

Checked the Numbering Plan Field and ensured that the selected Numbering Plan is Not "1" and also performed variant specific checks to fix this issue.

GSX-53117

2

SIP

GSX does not ACK an OK to a media lockdown re-invite when it has sendonly.

This issue is due to GSX holding the ACK for re-Invite if any media port change is encountered in the respective 200 OK. This should happen only when both the legs are SIP and should not happen when one of the leg is PSTN.Added a condition to hold the ACK only in SIP-SIP cases.

GSX-53153

2

Platform

asgUtils - Error 0x240f / asgMsgProc - Error 0x241d

Provided code changes for defensive fix to free ASG Blocks.

GSX-53154

1

Performance

BRM errors post LSWU cause GSX to slowdown and stop processing of new calls requests when NICE call recording is ON.

Fixed the problem in NP, the changes are tested with splitter enabled trans-coded active call load switch-overs.

 

GSX 09.00.10R001 Problems Resolved

The following are the issues fixed in GSX V09.00.10R001. The implications of not upgrading to include a particular fix have been provided where appropriate:

Issue ID

Severity

Category

Problems Description

Resolution

GSX-52896

2

SIP

GSX-38486 breaks all VSC calls.
In GSX-38486, the issue was GSX removes the in the end of the INVITE request number and sends this invalid number to PSX. To resolve this issue, the code was modified such that if '' is found in the number, call will be dropped with 400 BAD request.

Deleted the changes made based on GSX-38486.

GSX-52898

2

DSP

For IP to PSTN call, if a modem tone is detected during Inband DTMF generation it results in corrupted DTMF digits.

The code has been modified to fix this issue.

GSX-52918

3

DSP

Checksum Enhancement on VPAD.

The code has been modified to enhance the checksum repair functionality.

GSX-52924

2

CLI

Logical mgmt IP not working for SNMP requests.

The code has been modified to fix this issue.

 

GSX 09.00.10R000 Problems Resolved

The following are the issues fixed in GSX V09.00.10R000. The implications of not upgrading to include a particular fix have been provided where appropriate:

Issue ID

Severity

Category

Problems Description

Resolution

GSX-30 / GSX-52842 / GSX-52843 / GSX-52847 / GSX-52849

2

NBS9K

DSP crashes while handling G.729 media. The third party G.729 library was found to access an invalid memory region as a result of which BUSERR kicked in eventually leading to a DSP core-dump.

(BUSERR, a hardening feature available on DSP, detects any invalid memory access and freezes the corresponding DSP.)

Affected Cards : CNS-40/45/85/86, SPS80

This has been fixed by the third party vendor. And BUSERR has been re-enabled.

GSX-38486

2

GSX9K

When GSX receives INVITE request with in the end of the number, it removes the from the number and sends this invalid number to PSX.

The code has been modified such that if '' is found in the number, call will be dropped with 400 BAD request.

GSX-45376

3

GSX9K

ISUP circuits can be created even if the service name is not correct.
Due to this issue, some PSTN trunk groups are missing in "PSTN TrunkGroup/ Report Used Ports" on EMS.

The code has been modified to choose the exact match of ISUP service name while configuring ISUP service and while creating ISUP circuits.

GSX-50778

2

GSX9K

In H.323 to SIP call, the DTMF interworking is failing on egress SIP side as GSX is sending DTMF either as SIP INFO or inband whereas the expected is RFC2833.
The DTMF type capability exchange happens in TCS-TCS ACK message exchange when the offer-answer is complete. So SIP will not be advertising the DTMF capability in the offer-answer which happened. When the minimize media relay changes flag is set, the re-INVITE for DTMF type will not be advertised and the call fails. The same thing happens when the DTMF type selected is either 2833 or OOB or both.

To address this issue, SgOaMinimizeMediaChanges has been modified to include the DTMF types - 2833 or OOB or both.

GSX-51076

2

GSX9K

GNS switchover causes refclk binding status go to INVALID, only delete/regrow or node boot can restore them.

The code has been modified to fix this issue.

GSX-51089

2

Coredump

FKHgsx01 CNS86 slot11 switchover with error code 0x112d.
The issue was with the FSM manager where the FSM instance table had a valid address but with NULL contents in it.

The code has been modified to check for the availability of data inside FSM instance table.

GSX-51821

2

GSX9K

RTCP NAPT learning not enabled. GSX is responding to RTCP but not to the NATTed Port thus customer's device is not able to receive RTCP response.  NAPT media and RTCP is enabled on the ingress call leg. But GSX uses remote RTP port + 1 as the remote RTCP port instead of learning the remote RTCP port from received RTCP packets.

The code has been modified so that RTCP packet will be trapped and RTCP port will be learnt.

GSX-51844

2

SIP

When making SIP calls over TLS w/ SRTP, the FAX tone switch to FAX (NRMA/SgFSM) is OK, however SIPSG sends INVALID SDP data that leads to call failure on peer receiving T.38 re-Invite. While populating the cryptos, GSX fills cryptos on the basis of configuration shared from PSX.

The code has been modified to check for FAX such that it does not fill cryptos to SDP received and proceed accordingly.

GSX-51950

2

SIP

Sonus's T.38 implementation is not converting received T30_IND messages into a 2100 Hz (CED) tone on the PCM side. Due to this issue it is not able to receive fax from many different locations.

The code has been modified to fix this issue.

GSX-51983

2

GSX9K

Random calls fail with "DRE Activation / DeActivation".
This is a race condition that is impacting calls.
When re-invite comes before the tone, resources are released, NRMA tries to apply modify offer on tone resources that are being released which leads to call failure.

The code has been modified in common SG to queue answer message towards ingress peer if tone or announcement resources are not released by NRMA. The answer message will be sent towards ingress peer after tone resources are released. As re-invite arrives after tone resources are released, modify offer gets processed successfully

GSX-52079

2

DSP

The GSX does not count RFC2833 (DTMF) packets in the received packet and received byte statistics.

The code has been modified to count the DTMF packets and bytes.

GSX-52085

2

DSP

For a scenario with dial tone present in the packet to circuit direction, and DTMF digits being sent in the circuit to packet direction, the NLP's non-linear processor is squelching (removing) some of the DTMF digits. Due to this issue the call set up will fail because not all DTMF digits will be relayed.

The echo canceller NLP was adjusted to allow digits to pass in this scenario.

GSX-52143

2

GSX9K

Marlin errors is triggering inbound call failures which is fixed by Coredump.

The code has been modified to capture more information for this issue so that It will give more inputs in fixing if it reoccurs.

GSX-52210

2

SIP

PNS CPU load increases over time and halves after coredump for the same call load. As CPU load goes higher than 85%, call setup is impacted.
SIP MM rules and IP route messages were causing memory fragmentation and effecting overall performance of the PNS when allocating and freeing memory.

The code has been modified for memory allocation of these messages to retrieve memory from existing allocated bin to avoid fragmentation.

GSX-52263

2

GSX9K

Routing using FQDN as SIP server does not work on GSX. When routing to a SIP server (NOT using iptg) on a GSX, if the SIP server has FQDN information, the GSX fails to find an egress TG.

The code has been modified to fix this issue.

GSX-52359

2

SIP

CANCEL Request should match the INVITE transaction it is trying to cancel. When a call is canceled prior to answer, but after an 18x is received, the CANCEL that is sent out by the SBC contains Route-headers.
Due to this issue, it is not possible to onboard customers on to the SBC platform.

The SIP stack is modified to store the INVITE routeset in the call cb and will be retrieved while sending CANCEL and ACK to a negative response.

GSX-52444

2

Media(Fax)

Memory fragmentation still persists after GSX-52210.
Cached Route, Cached ARP and Packet Service Profile entries were causing memory fragmentation and effecting overall performance of the PNS when allocating and freeing memory.

The code has been modified for memory allocation of these messages to retrieve memory from existing allocated bin to avoid fragmentation.

GSX-52462

2

Platform

SBC9K does not globalize the Request-URI in egress SIP-I

When UNDO LNP flag was set in PSX, globalization was not happening. The code has been modified to fix this issue.

GSX-52513

2

SIP

SIPSG is getting terminated by FM due to 99% load in CPU.

The dequeuing logic in SIPSG has been modified to avoid queueing and dequeuing the same message repeatedly thereby resolving the repeated queueing of SG_EV_CC_EST_RSP.

GSX-52562

2

Platform

SUBSCRIBE KPML message gets truncated if transport is TCP. KPML does not work when the "Event" header is placed before the "Content-Length".

The code has been modified to fix this issue.

GSX-52623

2

Media(Fax)

Parse error, if Warning Header with host port is received.

The code has been modified to fix this issue.

GSX-52793

2

GSX9K

PortFix GSX-40 : Logical Mgmt IP for SNMP Response

The code has been modified to fix this issue.

GSX-52422

3

GSX9K

DNS responses from DNS servers are intermittently discarded by the media policer.
The response from the DNS server is not handled by GSX leading to call failure.

The code has been modified to fix this issue.

GSX-52428

3

GSX9K

GSX is creating invalid CDRs due to which Netscore fails to load CDRs into the database.

The code has been modified to fix this issue.

 

Known Problems

The following problems are known to exist in GSX V09.00.11R000:

Issue ID

Severity

Category

Problem Description

Workaround

SONUS00164394

3

Coredump

RTCP may fail when xNS cards reach their defined socket limit. SYS ERR in log will occur.

None

SONUS00153503

2

Configuration

Invalid prefix length configuration for IPv6 on MGMT NIFs results in a crash.

None

Known Limitations

The section describes limitations that are known to exist for the GSX4000 and GSX9000 in GSX V09.00.11R000 release.

Limitations for GSX9000 and GSX4000

The section describes platform, signaling, and call processing limitations for both the GSX9000 and the GSX4000.

Platform Limitations

The section describes the platform limitations for the GSX9000 and the GSX4000.

MNS and Management

Due to security changes to protect the GSX, the GSX will no longer respond when attempting a traceroute to the GSX.
Management NIFs no longer have 'active/standby' mode. Both MGMT NIFs are 'active' from operational point of view. Until release 6.0, route tables are modified such a way that, routes configured on "active" MGMT NIF have higher precedence over the standby MGMT NIF. Starting with release 6.0, both MGMT NIF ports on a given slot have equal preference, and routes are added to the routing table in the order they are configured/loaded. It is likely that an equivalent route on second management port might end up on top of the routing table because of the order in which ports are brought up.
The twenty-four hour cumulative (total) T1, T3, and E1 statistics cannot be reset.

SGX SS7 Gateway

Zero calls and loss of Primary OMNI CE may take 20 seconds to connect CE2.

Trunk Group Configuration Considerations

IP Trunk Groups – H.323 and SIP calls using G.711 with silence suppression and RTCP should disable the SID heartbeat to avoid premature Packet Outage Detection (POD) detection and the associated RTCP events. POD is an IP Trunk Groups feature that identifies significant network outages and can be used to reduce the capacity of an IP Trunk Group automatically. Silence Suppression has a silence insertion descriptor (SID) component and a silence insertion descriptor heartbeat; it is the latter that can trigger the false packet outage state. RTCP provisioning allows the GSX to detect when silence occurs and possibly disconnect a call, generate an SNMP trap and report statistics. If the SID heartbeat is not disabled in this scenario the RTCP-generated events will not be accurate. GW-GW calls are not affected by this limitation (SONUS00041846.)
Trunk Groups and Performance Statistics – Performance statistics are saved in a number of "intervals" (default = 4, maximum = 12) and performance statistics are run per trunk group per interval. Increasing the number of trunk groups, and to a greater extent increasing the number of intervals, increases the memory requirements for the interval table. So changing the number of intervals can have a dramatic effect on how much memory is used. Therefore we recommend that customers do not increase the number of intervals when using a large number of trunk groups.
Older CPL Scripts May Cause System Errors – Older CPL scripts that were created to work with a different GSX script architecture may not work properly and can even cause system errors if used with newer GSX versions (SONUS00047034.)
Service Profile Editor loop coding – Although SPE 6.x (e.g., SPE 06.03.05 used for GSX 7.2.3) does not allow any pointers to point back to the Begin SIBB, ensure that the script being built with the Sonus SPE tool does not have an infinite loop. An unintended consequence of using a loop-programming construct could be a forever loop, and such a script when executing on the GSX card could cause high CPU utilization.
Disabling Default IP Trunk Groups – You cannot directly disable the defaultIPTG or its service groups; trying to do so through the CLI will generate errors such as "The defaultiptg cannot be set out of service" or "Default IP service groups can never be modified or deleted" (SONUS00053613). However, you can configure the defaultIPTG trunk to not accept calls by setting the defaultIPTG call limit and bandwidth limit = 0 through the CLI or EMS. Via the CLI, use:
CONFIGURE TRUNK GROUP defaultiptg IP CALL LIMIT 0
CONFIGURE TRUNK GROUP defaultiptg IP BANDWIDTH LIMIT 0
On the EMS IP Trunk and defaultIPTG Trunk screens, use CONFIGURE SELECTED IP TRUNK GROUP - NO DISRUPTION to change the IP call and bandwidth limit without taking the trunk out of service.

Signaling and Call Processing Limitations

Different DTMF relay with conditional transcoding

Different DTMF Relay works best if PSPs and endpoints are partitioned. For example, Ingress is all 2833 (only) and Egress is all OOB (only). PSPs should be set in the same way and endpoints should be enabled in the same manner.

G729r8 Support in H.323 Signaling

The GSX can now process an incoming H.323 call request with G.729 payload in the offer (PCR1528, SONUS00074701). On the egress side, when configured appropriately with G.729A in the PSP-Ri and PSP-Re, the GSX sends both G.729 and G.729A in the offer to the peer. Upon receiving the answer from the terminating endpoint, the GSX sends G.729/G.729A in the answer to the originating side depending on what it received from the egress endpoint.
Previously the H.323 GW supported only G.729A, not G.729. Although G.729 was supported on the DSP it was not supported in the H.323 implementation, so no common codec could be negotiated for an incoming offer with G.729 payload and as a result calls.

Lawful Intercept Solution

Lawful Intercept (LI) functionality has the following current limitations for the LI solution:

  • Billing Number intercept criterion is not supported.
  • SIP URI intercept criterion is not supported.
  • VPN intercept criterion is not supported.
  • IP Loopback only works on GSX PNS40 cards (GSX 9000 only).
  • Inband DTMF digits are reported by Sonus Equipment to the LI Server.  However, final reporting to the Law Enforcement Agency (LEA) will depend on the LI Server vendor.

Contact Sonus regarding implementation of Lawful Intercept, including details of interfacing with an Intercept Server and any current functional limitations.

 

SIP

If the Mandatory Header fields have an illegal value and cannot be parsed, the GSX will not respond but rather will ignore the SIP packet (SONUS00031454).
For SIP calls, the GSX rejects a modified SDP offer in a PRACK.
RURI transparency is not consistent for relayed SUBSCRIBE/NOTIFY messages.

SIP Replaces

SIP Replaces is supported as an independent feature, it is not supported in conjunction with SIP REFER on the same call (i.e. you cannot perform a SIP Replaces operation on a call which has already performed SIP REFER, and vice versa).
Multiple SIP Replaces operations on the same call are not supported; you can only perform one SIP Replaces operation on any given call.
SIP Replaces is only supported in scenarios where the new Replaces call results in a pass-through call. This type of call is supported: A call from A  B is passed-through or transcoded and the SIP Replaces call from A  C is passed-through. This type of call is not supported: A call from A  B is passed-through or transcoded and the SIP Replaces call from A  C is transcoded.

Interoperability Constraints with the SIP Application Server

When using packet cards other than PNS40s, SIP-based applications that instruct the GSX to bridge the media streams of two independent calls may result in the following types of issues:

  • One way media flow
  • No media flow
  • Call failures

Call flow validation is required when the GSX is interworking with SIP Application Servers that provide call transfer scenarios (including those with SIP Refer), prepaid calling card applications, call forwarding applications, click-to-dial applications, Class 5 applications, or any application involving the bridging of two or more calls through the GSX.
These types of applications are typically implemented by an application server swapping the SDP of two independent calls. This action, by the application, results in the GSX sending media from one call back to itself for the other call. When the calls land on the same NIF, the GSX must recognize this situation and internally bridge the media between the two calls. This is referred to as an IP-loopback call. When the calls land on different NIFs, the media flows out of the GSX on one NIF through the IP network to the other NIF and back into the GSX; this scenario does not utilize internal bridging.
Why Bridge? Media streams for IP loopback calls must be bridged internally by the GSX and not send packets on to the IP network; packets of looped streams if sent out on the IP network are dropped by the routers/switches due to the fact that they have the same source and destination addresses.
IP loopback is not restricted to the scenarios where the two calls are PSTN to IP calls; loopback can also occur when A and B are IP endpoints or a mix of PSTN and IP endpoints.

ISDN to BT IUP Interworking

The table below indicates the interworking functionality that is provided between these protocols.

BT IUP

ISDN

Interworking Status

CLIP/CLIR

CLIP/CLIR

Full Interworking1

Overlap

Overlap

Full Interworking

Fallback

Fallback

Partial interworking2 3

NAE

SUB(Called)

Full Interworking

DDI

DDI

Full Interworking (PSX Functionality)

CCBS

CCBS

Cannot be mapped across the IWF

CUG

CUG

Cannot be mapped across the IWF 4

Call Diversion

Call Diversion

Cannot be mapped across the IWF4

Suspend/Resume

Suspend/Resume

Cannot be mapped across the IWF4

RBWF

n/a

Cannot be mapped across the IWF4

SWAP

n/a

Cannot be mapped across the IWF3

ACI

n/a

Cannot be mapped across the IWF

SIC

LLC

Partial Interworking

n/a

HLC

Cannot be mapped across the IWF

n/a

HOLD

Cannot be mapped across the IWF

n/a

CW

Cannot be mapped across the IWF

n/a

3PTY

Cannot be mapped across the IWF

n/a

CONF

Cannot be mapped across the IWF

n/a

ECT

Cannot be mapped across the IWF

n/a

COLP/COLR

Cannot be mapped across the IWF

n/a

UUS

Cannot be mapped across the IWF

1: The GSX ISDN implementation only Supports Single Number Delivery, interworking Calling and Presentation Number to ISDN as PNO 8, Issue 3.1, Table 8.3.
2: BT IUP only supports fallback from 3.1 kHz to Speech.
3: No messages requesting a Bearer Change can be interworked to BT IUP.
4: The GSX Euro-ISDN implementation does not support this functionality.

G.711

Starting with GSX 6.0, silence suppression descriptor (SID) packets are compliant with G711 Annex II. However, its use is not generally available with all signaling protocols and is only supported between GSXs with GW-GW signaling. G711 Annex II silence suppression with comfort noise generation (CNG) is not supported to SIP or H.323 endpoints.

Limitations for GSX9000 Only

The section describes platform, signaling, and call processing limitations for the GSX9000 only.

Platform Limitations

This section describes the platform limitations for the GSX9000.

PNS and Packet Transport

This release only supports a 3:1 PNS40 redundancy configuration.

PNS card switchover during high call load in GSX

In a configuration where all the PNS cards in GSX chassis are fully loaded with calls and incoming call load is significant, a PNS card switchover can create call distribution imbalance in the system. This call distribution imbalance can cause other PNS cards to go into cycles of congestion. This condition will abate once the call load in the system decreases. The problem was detected in a 3+1 PNS card configuration but is not specific to that configuration. It is possible in 1+1 PNS card configuration at sufficiently high call load during switchover.

MNS and Management

A maximum of four simultaneous telnet and/or SSH sessions is supported.
An NTP server is required in both Sonus SoftSwitch and third party softswitch models.

CNS and TDM Transport

Certain combinations of circuit redundancy groups must not be configured in a GSX. The restrictions in the table below are enforced. The CNS servers are divided into classes for the purpose of defining the restrictions within a class as well as between classes of servers. The table below shows the restrictions and the valid combinations:

Redundancy Group Class

CNS60

CNS71

CNS40 /45

CNS80/ 85

CNS86/ 81

CNS60

Multiple

Yes

Multiple

Multiple

Yes

CNS71

Yes

Multiple

Yes

Yes

Multiple

CNS40/45

Multiple

Yes

Multiple

Multiple

Yes

CNS80/85

Multiple

Yes

Multiple

Multiple

Yes

CNS86/81

Yes

Multiple

Yes

Yes

Multiple

Where:

  • One: A single redundancy group composed of one of these server types is permitted.
  • No: Redundancy groups composed of servers from each of these classes are not permitted.
  • Yes: Redundancy groups composed of servers from each class are permitted.
  • Multiple: Multiple redundancy groups composed of servers from this class are permitted.

All other redundant CNS modules must be installed in slots 14, 15, or 16. Only one T3 redundancy group is allowed to switchover at one time because it is dependent on the same hardware resources as the other T3 redundancy group.

CNS Card Announcement Memory

If a CNS card's announcement memory is full and all the announcements are currently in use (none have been unused long enough to be eligible for overwriting), an attempt to download another announcement will generate a Major error "...Segment Memory is Full..." The announcement will successfully load once an existing announcement is no longer in use.

Trunk Group Configuration Considerations

Release GSX 6.3 and later allow you to configure a maximum of 2048 trunk groups on MNS20 card. The maximum number of service groups allowed is 2047. However, in general, the more trunk groups and service groups that you configure, the more likely that call rate performance will be reduced, as follows:

  • Configuring large numbers of trunk groups with similar names can cause a severe degradation of calls per second performance. Trunk group names received from the PSX are located using a named lookup. This search is most efficient when the trunk groups have dissimilar names and least efficient when they take similar names such as TrunkGroup01, TrunkGroup02, etc.
  • Configuring larger performance statistics interval sizes and saving fewer intervals can reduce the load on the management port. Sonus Insight communicates with SNMP over the management port to maintain trunk group performance statistics. Other management port functions, such as policy requests and responses, could be delayed or lost by these performance statistics causing calls to fail.
  • A larger number of trunk groups and service groups will require more MNS module processing resources to complete periodic saves of the parameter files. This could result in fewer cycles to process calls when parameters are saved due to configuration changes.
  • The time that is taken to successfully perform a CNS or MNS switchover will be lengthened as the number of trunk groups increases.
  • PSX processing is also subjected to increased load when large numbers of trunk groups are configured. When large numbers of trunk groups are configured on a single routing label, the route label should not have the "All" flag enabled.
  • Any trap that is generated per trunk group or per service group can potentially cause a "trap storm" if there is an event that causes a trap to be generated for a large number trunk groups or service groups. This may occur during a CNS or MNS switchover, when communication with the SGX is lost, or when a high capacity port (e.g. OC-3) goes down. Trap storms can bog down the management port on the GSX and EMS, and the GSX may drop some traps when its queues get full.
EMS Support for Expanded Numbers of Trunk Groups

Due to EMS processing limitations, it is recommended that the number of provisioned trunk groups on the GSX not exceed several hundred trunk groups. Any number beyond that may detrimentally affect the EMS's ability to collect trunk group data and to manage the GSX via the GSX Navigator.
It is also recommended that as the number of trunk groups provisioned on the GSX is increased that the performance data collection frequency be decreased.
Finally it is recommended that the number of intervals configured on the GSX for the trunk group interval table be reduced as the number of provisioned trunk groups increases.

T.38 Fax Transmission

When the T.38 fax transmission ceases, the audio session should be terminated. GSX does not allow the audio session to be re-established after the successful fax call ends.

Packet-to-Packet Call Services

In Packet-to-Packet call services, the GSX sends zero duration for RTP Event packet.

Direct Media

It is a Direct Media call, but the Ingress Codec Info and Egress Codec Info of the CDR fields has Codec type negotiated in the signaling.

Redundancy for PNS40/41 Cards

Because of the increased memory footprint of the software, Release V09.00.02R000 supports 3:1 redundancy instead of 4:1 redundancy for PNS 40/41 cards.

If CICs are added on the GSX when all the M3UA links between GSX and SGX are down, then the registration information could go out of sync between GSX and SGX when the links come back up.
This can be rectified by making the SGP links to the standby MNS card outOfService and back inService at the SGX.

Performance Limitations

This section describes the performance limitations for the GSX9000.

Standby PNS41 crash

Standby PNS41 crashes with an out of memory condition in a 4+1 redundancy configuration in an Access SBC role. PNS41 crashes with 240,000 subscribers spread across 4 active cards backed up by 1 standby card.
Under load at 160 cps, PNS41 crashes for SIP-SIP call, where signaling and media is on IPv6 for both legs.
The PNS41 cards must be reconfigured into a 2+1 redundancy configuration.

AMR Limitations

The GSX9000 does not support interleaving, CRC, and robust sorting in transcoded call. But these are supported for pass through calls. Supported interleaving is 4-19 frame-blocks.
Sonus AMR, WB AMR, and EFR implementation has VAD turned ON and there is no configurable option currently to disable the VAD.
Currently, silence suppression check box in PSX will be used to configure VAD for the three codecs. When silence suppression box is checked, it implies that the VAD is ON. 
AMR-NB supports VAD1 and VAD2, the VAD type should be made configurable. For Backward compatibility default VAD2 must be configured.
However, AME-WB codec AMR-WB and EFR have only one VAD type.

INVITE with Replaces

When GSX receives an INVITE with Replaces from an End Point which has received a REFER, 
GSX does not relay the INVITE to the intended Party and there is no Replaces header in the message.

Traps

The following SNMP Traps are not supported by the GSX9000:

MIB

SNMP Trap Not Supported by GSX9000

rfc1573.mib

linkDown

rfc1573.mib

linkUp

rfc1907.mib

coldStart

rfc1907.mib

warmStart

rfc1907.mib

authenticationFailure

rfc2320.mib

ipoaMtuExceeded

rfc2320.mib

ipoaDuplicateIpAddress

rfc2320.mib

ipoaLisCreate

rfc2320.mib

ipoaLisDelete

rfc2495.mib

dsx1LineStatusChange

rfc2496.mib

dsx3LineStatusChange

rfc3498.smib

apsEventSwitchover

rfc3498.smib

apsEventModeMismatch

rfc3498.smib

apsEventChannelMismatch

rfc3498.smib

apsEventPSBF

rfc3498.smib

apsEventFEPLF

sonusAps.mib

sonusApsTrapProtectionSwitchingByteFailure

sonusAps.mib

sonusApsTrapChannelMismatch

sonusAps.mib

sonusApsTrapModeMismatch

sonusAps.mib

sonusApsTrapFarEndProtectionLineFailure

sonusAps.mib

sonusApsTrapSwitchover

sonusIpdc.mib

sonusIpdcSessionConnectNotification

sonusIpdc.mib

sonusIpdcSessionDisconnectNotification

sonusIpdc.mib

sonusIpdcSessionChangeNotification

sonusIpdc.mib

sonusIpdcSessionEndNotification

Limitations for GSX4000 Only

The section describes platform, signaling, and call processing limitations for the GSX4000 only.

Platform Limitations

This section describes platform limitations for the GSX4000.

Management

In a scenario where there was one MTRM server/client on one GSX4000, one MTRM client on another GSX4000 (with GW calls on an IP selected trunk group between them), prior to taking MTRM server outofservice, the calls allocated were balanced at 500 and 500 for each GSX4000 client. (The MTRM Server bandwidth limit was UNLIM while the global call limit was 1000.) Upon taking it outofservice and once again inservice, calls allocated did not achieve this balanced state again; thus, resources were not symmetrically allocated.
In order to work around this issue, use a more granular number for the following configuration:
CONFIGURE TRUNK GROUP <trunk group name> CALLS PER REQUEST <number>
There is a performance tradeoff with this workaround. If you set this number too low with respect to the overall expected rate of arrival of calls, then there will be an increased number of messages. If too high, then there is a possibility of the anomaly reported here. A good number would be MIN{20, peak rate/3}.

DSP Re-Loading

The GSX4000 does not support re-loading of DSPs. This is due to the existence of three distinct DSP XPAD images (UXPAD, GSXPAD, and EXPAD). There are two workarounds to this limitation:

  • Configure the DS1 type (CONFIGURE DS1 ALL TYPE circuittype) after you configure the MEDIA PROFILE.
  • Dynamically change the MEDIA PROFILE while the system is up and running, turn on parameter loading, and re-boot the GSX4000.
Local Disk and Event Logs

This platform does not support event logging to the local disk.

Packet Transport

Support for signaling and media flows between communicating packet peers is supported with restrictions. Any combination of SIP, SIP-T, and Gateway may be used on both ingress and egress call legs. Media negotiation occurs between the peers on a call-by-call basis, resulting either in the mapping (transcoding) or in the pass through (RTP relay) of media. Negotiations may occur during the call, as well as at call setup.
RTCP is not supported for packet-to-packet calls that are setup with RTP relay. For these calls, RTP flows through the GSX without DSP processing.

Traps

The following SNMP Traps are not supported by the GSX4000:

MIB

SNMP Trap Not Supported by GSX

rfc1573.mib

linkDown

rfc1573.mib

linkup

rfc1907.mib

coldStart

rfc1907.mib

warmStart

rfc1907.mib

authenticationFailure

rfc2495.mib

dsx1LineStatusChange

Emergency Link activation is possible without the CIC configured (SONUS00046398.) In the current design, SS7 Links stay in OUTOFSERVICE state as long as ISUP CICs are not configured, and are brought into INSERVICE state when the CICs are configured. But whenever the CLI command to perform emergency Activation of a linkset is used, the MTP2 Links go into INSERVICE state. Therefore, availability of MTP2 Links after using above CLI command doesn't indicate that the ISUP CICs are configured on the chassis. You can bring the link into service with the CLI command even though CICs are not configured. When bringing up MTP2 links, you must also configure the CICs.
MTP3 can report MTP2 Link status as L2OOS, when the actual status is INSERVICE (SONUS00052079.) Whenever an MTP3 link is deactivated and mode Blocked, followed by re-activation by 'EMERGENCY or NORMAL' option, the MTP3 link status indicate the MTP2 link state as UNAVL|LBLK|L2OOS instead of only UNAVL|LBLK. This indicates that MTP2 link is OUTOFSERVICE, instead of INSERVICE. Later, when the MTP3 Link is mode unblocked, the MTP3 link state changes to AVAILABLE as expected.

 

During CNS switchover, MTP2 may glitch the line. However, calls are not impacted.

 

Signaling and Call Processing Limitations

This section describes the signaling and call processing limitations for the GSX4000.

SS7

The GSX4000 can only support one SS7 MTP3 MGMT node.

GSX Behavior Change

The GSX CLI may occasionally appear to halt when a large number of commands are executed via the CLI. This behavior is not indicative of a problem with the system.

 

Labels
  • None

On this page:

  • About this Document
    • Introduction
    • Release Notes Use and Distribution
    • Problems or Questions
    • Related Documents
    • GETS Software
    • Scripting Support - Optional Sonus SPE Software
  • Unsupported GSX cards in Release V09.00.11R000
  • CNS10 and CNS25 Card Performance Advisory
  • Information about Software Download
  • GSX Upgrade Paths
    • Supported GSX Upgrade Paths
    • GSX Upgrade Path Exceptions
  • GSX Interoperability Matrix
  • Upgrade Notes
    • Master Trunk Group Upgrade Procedures
    • CAM/CDR Field Changes
    • NIF Group
    • Changes in Default Behavior
    • GSX Firmware Versions
    • Software Upgrade Considerations
  • New Features and Modifications
    • New Features and Modifications in V09.00.06R000
    • New Features and Modifications in V09.00.05R000
    • New Features and Modifications in V09.00.04R000
    • New Features and Modifications in V09.00.03R000
    • New Features and Modifications in V09.00.02R000
    • New Features and Modifications in V09.00.01R000
    • GSX4000 Unsupported Features and Functionalities
  • Problems Resolved
    • GSX 09.00.11R000 Problems Resolved
    • GSX 09.00.10R001 Problems Resolved
    • GSX 09.00.10R000 Problems Resolved
  • Known Problems
  • Known Limitations
    • Limitations for GSX9000 and GSX4000
    • Signaling and Call Processing Limitations
    • Limitations for GSX9000 Only
    • Performance Limitations
    • AMR Limitations
    • INVITE with Replaces
    • Traps
    • Limitations for GSX4000 Only
    • Signaling and Call Processing Limitations
    • GSX Behavior Change

GSX R000 Release Notes - Sonus Networks Product Full text of Thinkdigit Magazine 2008-05 - Internet Archive


54
Sitemap