Skip to end of metadata
Go to start of metadata

Search the Release Notes:

On this page:

About SBC Release Notes

This page describes new features, new hardware and software requirements, and known limitations for the latest release of Sonus' Session Border Controller (SBC 5000 series).

Related Documentation

The SBC 5000 series 04.00.01R000 documentation is located at the following  Sonus Networks Wiki space: SBC 5000 Series Documentation.

Problems or Questions

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

Worldwide Voice: 1 (978) 614-8589

USA Toll-free: 1 (888) 391-3434

Worldwide Fax: 1 (978) 614-8609

Email: TechnicalPublications@sonusnet.com.

About SBC 5000 Series

The Sonus Session Border Controller platforms (SBC5100, 5110, 5200, 5210) provide enterprises and service providers with the features, performance, and reliability that they require. This versatile series of SBCs can be deployed as a Peering, Access, or enterprise SBC (e-SBC), and is tested for interoperability and performance against a variety of third party products and call flow configuration in the customer networks.

Interoperability

The SBC 5000 series software interoperates with the following:

  • SIP/H.323 compliant IADs and IP-PBXs
  • Sonus PSX Policy Server Softswitch via SIP redirects and/or Diameter+ protocol
  • Sonus SBC 9000 through SIP call signaling and Sonus Networks MCS protocol

Compatibility with Sonus Products

This 04.00.01R000 release is compatible with the following Sonus product releases versions:

The minimum compatible release versions are listed.

Supported Device Bundles

PSX

GSX

EMS

DSI

ePSX OVA
V09.01.00R000V09.00.03R000V09.01.00R000V09.00.00R000V09.01.00R001
 V09.00.02R000 V08.04.07R000 (Linux) 
 V08.04.08R000 V08.04.02R000 P4 (Solaris) 

For Replica ePSX Installation on SBC:

  • Install/Upgrade PSX Master with the correct version before you install replica ePSX on SBC.
  • Ensure that PSX Master is running V09.01.00R001 version.

ePSX (OVA)

FileUsage
ePSX-V09.01.00R001-51xx.ova

ePSX installation package on SBC 5110.

ePSX-V09.01.00R001-52xx.ovaePSX installation package on SBC 5200 and SBC 5210.

ePSX installation is not supported on SBC 5100.

The ePSX installation package is not available in the standard SBC package. It is provided separately.

Required Software and Firmware Versions

The following SBC 5000 series software and firmware versions are required for this release:

Components

Software/Firmware

Version

SBC 5000 Series Platform

  

BMC

V02.04.01-R0

BIOS

V02.02.00-R0
(Minimum required: V02.01.02-R0)

ConnexIP OS

V02.00.03-R000

SBC 5000 Series Application

 

 

SonusDB

V04.00.01-R000
(Minimum required: V01.02.00-R000)

SBC Application

sbc-V04.00.01-R000

Prior SBC 5000 Series Software/Firmware Versions

SBC Release

BMC*

BIOS*

ConnexIP OS

SonusDB*

V02.00.06-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-R000
V02.00.06-R001V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-R001
V02.00.06-R002V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-R002
V02.00.06-F001V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F001
V02.00.06-F002V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F002
V02.00.06-F003V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F003
V02.00.06-F004V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F004
V02.00.06-F005V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F005
V02.00.06-F006V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F006
V02.00.06-F007V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.06-F007
V02.00.07-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.07-R000
V02.00.07-F001V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.07-F001
V02.00.07-F002V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.07-F002
V02.00.07-F003V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.07-F003
V02.00.08-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.08-R000
V02.00.08-F001V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.08-F001
V02.00.08-F002V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.08-F002
V02.00.09-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.09-R000
V02.00.09-F001V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.09-F001
V02.00.10-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.10-R000
V02.00.10-R001V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.10-R001
V02.00.11-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.11-R000
V02.00.12-R000V01.14.00-R000V01.06.03-R000V01.07.05-R000V02.00.12-R000
V03.00.00-R000V02.01.07-R000V02.00.00-R000V01.08.00-R000V03.00.00-R000
V03.00.01-R000V02.01.07-R000V02.00.00-R000V01.08.01-R000V03.00.01-R000
V03.00.01-R001V02.01.07-R000V02.00.00-R000V01.08.01-R000V01.02.00-R000
V03.00.01-F001V02.01.07-R000V02.00.00-R000V01.08.01-R000V01.02.00-R000
V03.00.02-R000V02.01.07-R000V02.00.00-R000V01.08.02-R000V01.02.00-R000
V03.00.02-R001V02.01.07-R000V02.00.00-R000V01.08.02-R000V01.02.00-R000
V03.00.02-F001V02.01.07-R000V02.00.00-R000V01.08.02-R000V01.02.00-R000
V03.00.02-F002V02.01.07-R000V02.00.00-R000V01.08.02-R000V01.02.00-R000
V03.00.02-F003V02.01.07-R000V02.00.00-R000V01.08.02-R000V01.02.00-R000
V03.00.02-F004V02.01.07-R000V02.00.00-R000V01.08.02-R000V01.02.00-R000
V03.00.03-R000V02.01.07-R000V02.00.00-R000V01.08.03-R000V01.02.00-R000
V03.00.03-R001V02.01.07-R000V02.00.00-R000V01.08.03-R000V01.02.00-R000
V03.00.03-R002V02.01.07-R000V02.00.00-R000V01.08.04-R000V01.02.00-R000
V03.00.04-R000V02.01.07-R000V02.00.00-R000V01.08.04-R000V01.02.00-R000
V03.00.04-F001V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.04-F002V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.04-F003V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.04-F004V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.04-F005V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.04-F006V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.04-F007V02.01.07-R000V02.00.00-R000V01.08.05-R000V01.02.00-R000
V03.00.05-R000V02.01.07-R000V02.00.00-R000V01.08.06-R000V01.02.00-R000
V03.00.05-F001V02.01.07-R000V02.00.00-R000V01.08.06-R000V01.02.00-R000
V03.00.06-R000V02.01.07-R000V02.00.00-R000V01.08.07-R000V01.02.00-R000
V03.00.06-F001V02.01.07-R000V02.00.00-R000V01.08.07-R000V01.02.00-R000
V03.00.07-R000V02.01.07-R000V02.00.00-R000V01.08.07-R000V01.02.00-R000
V03.01.00-R000V02.01.07-R000V02.00.00-R000V02.00.00-R007V01.02.00-R000
V03.01.00-R001V02.04.01-R000V02.01.01-R000V02.00.00-R007V01.02.00-R000
V03.01.00-F001V02.04.01-R000V02.01.01-R000V02.00.00-R007V01.02.00-R000
V03.01.01-R000V02.04.01-R000V02.01.02-R000V02.00.00-R007V01.02.00-R000
V03.01.01-R001V02.04.01-R000V02.01.02-R000V02.00.01-R007V01.02.00-R000
V03.01.01-F001V02.04.01-R000V02.01.02-R000V02.00.01-R008V01.02.00-R000
V03.01.01-F002V02.04.01-R000V02.01.02-R000V02.00.01-R008V01.02.00-R000
V03.01.02-R000V02.04.01-R000V02.01.02-R000V02.00.01-R010V01.02.00-R000
V03.01.02-R001V02.04.01-R000V02.01.02-R000V02.00.01-R010V01.02.00-R000
V03.01.02-R002V02.04.01-R000V02.01.02-R000V02.00.01-R011V03.01.02-R002
V03.01.03-R000V02.04.01-R000V02.02.00-R000V02.00.01-R012V03.01.03-R000
V03.01.03-R001V02.04.01-R000V02.02.00-R000V02.00.01-R012V03.01.03-R001
V03.01.04-R000V02.04.01-R000V02.02.00-R000V02.00.01-R013V03.01.04-R000
V04.00.00-R000V02.04.01-R000V02.02.00-R000V02.00.02-R000V04.00.00-R000

* Minimum required version for this release.

How to Verify Currently Installed Software/Firmware Versions

Use Platform Manager to verify the currently installed software and firmware versions.

Figure : Platform Manager - Software Versions

During an SBC upgrade process, the SonusDB version may not get upgraded and this will not have any functional impact.

During an SBC upgrade, the Platform Manager user can be forcibly logged out. If the SBC fails the upgrade due to insufficient disk space, the Platform Manager user cannot log back in to determine the state of the upgrade. Please verify all pre-installation checks, such as current disk space availability, before starting an upgrade.

Software Bundles

Download the required software bundles from the Customer Portal to your PC:

Verify all the downloaded .rom files with the respective Sonus supplied .md5 files to make sure that the .rom files are not corrupted.

Firmware

  • firmware-bmc5X00_v2.4.1-R0-bios5X00_v2.2.0-R0.tar.gz
  • firmware-bmc5X00_v2.4.1-R0-bios5X00_v2.2.0-R0.tar.gz.md5

Operating System

  • connexip-os-V02.00.03R000.tar.gz
  • connexip-os-V02.00.03R000.tar.gz.md5

Application

  • sbc-V04.00.01-R000.x86_64.tar.gz
  • sbc-V04.00.01-R000.x86_64.md5
  • sbc-V04.00.01-R000.x86_64.signature

For detailed information on installation and upgrade procedures, refer to Installing and Commissioning SBC 5000 Series.

Supported SBC 5000 Series Upgrade Paths

From release version...To release version...
V02.00.06R000V04.00.01R000
V02.00.06R001V04.00.01R000
V02.00.06R002V04.00.01R000
V02.00.06F001V04.00.01R000
V02.00.06F002V04.00.01R000
V02.00.06F003V04.00.01R000
V02.00.06F004V04.00.01R000
V02.00.06F005V04.00.01R000
V02.00.06F006V04.00.01R000
V02.00.06F007V04.00.01R000
V02.00.07R000V04.00.01R000
V02.00.07F001V04.00.01R000
V02.00.07F002V04.00.01R000
V02.00.07F003V04.00.01R000
V02.00.08R000V04.00.01R000
V02.00.08F001V04.00.01R000
V02.00.08F002V04.00.01R000
V02.00.09R000V04.00.01R000
V02.00.09F001V04.00.01R000
V02.00.10R000V04.00.01R000
V02.00.10R001V04.00.01R000
V02.00.11R000V04.00.01R000
V02.00.12R000V04.00.01R000
V03.00.00R000V04.00.01R000
V03.00.01R000V04.00.01R000
V03.00.01R001V04.00.01R000
V03.00.01F001V04.00.01R000
V03.00.02R000V04.00.01R000
V03.00.02R001V04.00.01R000
V03.00.02F001V04.00.01R000
V03.00.02F002V04.00.01R000
V03.00.02F003V04.00.01R000
V03.00.02F004V04.00.01R000
V03.00.03R000V04.00.01R000
V03.00.03R001V04.00.01R000
V03.00.03R002V04.00.01R000
V03.00.04R000V04.00.01R000
V03.00.04F001V04.00.01R000
V03.00.04F002V04.00.01R000
V03.00.04F003V04.00.01R000
V03.00.04F004V04.00.01R000
V03.00.04F005V04.00.01R000
V03.00.04F006V04.00.01R000
V03.00.04F007V04.00.01R000
V03.00.05R000V04.00.01R000
V03.00.05F001V04.00.01R000
V03.00.06R000V04.00.01R000
V03.00.06F001V04.00.01R000
V03.00.07R000V04.00.01R000
V03.01.00R000V04.00.01R000
V03.01.00R001V04.00.01R000
V03.01.00F001V04.00.01R000
V03.01.01R000V04.00.01R000
V03.01.01R001V04.00.01R000
V03.01.01F001V04.00.01R000
V03.01.01F002V04.00.01R000
V03.01.02R000V04.00.01R000
V03.01.02R001V04.00.01R000
V03.01.02R002V04.00.01R000
V03.01.03R000V04.00.01R000
V03.01.03R001V04.00.01R000
V03.01.04R000V04.00.01R000
V04.00.00R000V04.00.01R000

Customers upgrading from SBC version V04.00.00R000 and ePSX OVA version V09.01.00R000, only need to upgrade the SBC application to V04.00.01R000. The ePSX OVA package may remain at V09.01.00R000. For all other upgrade paths, upgrade the SBC application to V04.00.01R000 and perform a fresh installation of the ePSX OVA V09.01.00R001 version.

SBC versions V02.00.06R000 and above can directly LSWU to V04.00.01R000.

New Features

The following new features/enhancements are included in this release:

SBX 2329 - SNMP Traps for Dynamic Blacklist

Dynamic Blacklist (DBL) functionality is enhanced to log events & traps when end points are added or removed from blacklist:

  • When an end point is added to Dynamic Blacklist (DBL) for the first time, a MINOR level event is logged in SYS log indicating that there are one or more DBL entries in the system and a MAJOR Level SNMP trap is generated in EMS informing the operator that there are DBL entries in the system. SBC also logs a MINOR level event in the SEC log providing details about the end point including Address Context name, Remote IP address, DBL event (badSipMessage, sipEpCacAggrRej or sipRegistrationFailure), DBL profile name, DBL action (blacklist or watch), Duration of sanction. At the same time a MAJOR Level SNMP trap is generated to inform EMS that there are DBL entries in the system.
  • Subsequently, whenever a new end point is added to DBL, SBC logs MINOR level event in the SEC log with all details. Similarly, when an entry is removed from DBL either manually or as part of timer expiry, MINOR level event is logged in SECURITY log providing details about the end point.
  • SBC polls system every 60 minutes to check if there are any DBL entries present in the system. If found, SBC logs a MINOR level event in SYS log and generate the corresponding trap in EMS mentioning there are DBL entries in the system. This should overwrite any existing trap in EMS with new one and with new time stamp.
  • When the last DBL entry in the system gets removed manually/expired, a MINOR level event is logged in SYS log to indicate that there are no more DBL entries in the system and a clearing trap is generated for the EMS.
  • When a standalone CE restarts or switchover happens for a HA system, DBL entries are cleared from memory. In these scenarios, clearing events are not generated and manual clearance is needed in EMS as well.

For more information, refer to sonusSbxDBLActionMajorNotification and sonusSbxDBLClearActionMajorNotification.

SBX 2330 - Pilot Number Registration for SBC

Two new additional parameters are added to Require Registration flag of Sip Trunk Group object:

  • required-group: If this option is selected for an ingress IP trunk group in relation to a received call (e.g. call from IP-PBX towards AS) so that if the source IP address and port of the INVITE/OOD request do not match the source IP address and port of an existing registration in the zone, they are rejected. However, if the AOR does not match, but if the source IP Address and the port match to the existing registration in the zone, messages are accepted. If this option is selected for an egress IP trunk group in relation to a received call (e.g. call from AS towards IP-PBX), the user part check between registered AoR and Request-URI of the INVITE does not occur, and the call is accepted.
  • required-group-nonpriority: Use this option to prevent unregistered IADs from making or receiving non-priority calls. All emergency calls are allowed even if the source IP/port fails to fetch RCB.

For more information, refer to SIP Trunk Group, Signaling - Registration, and sipTrunkGroup signaling (CLI).

SBX 2694 - Use Default Zone for routing calls to ASX or SIP Servers

SBC has been enhanced to route calls to ASX or SIP Servers (no zone or Zone Index 0 configured on PSX) using defaultSigZone, a named IPTG and a sipSigPort in the defaultSigZone.

When SBC queries the PSX for routing a call to ASX / SIP Server (no zone or Zone Index 0 configured on PSX), the ASX/ SIP Server IP address, virtual TG and no zone is returned in the response. SBC will use defaultSigZone, customer provisioned named sipTrunkGroup (the ingress IP Prefix of which matches the ASX/ SIP Server IP address) and customer provisioned sipSigPort in the defaultSigZone for routing the call, previously the call would have failed.

For more information, refer to Routing Mechanisms.

SBX 3129 - BIOS update in OS package for SBC

The required BIOS version is now available in the OS package. The OS installation (ISO) or OS upgrade automatically upgrades BIOS to the required version and no additional steps are required to upgrade or downgrade. On completion of BIOS and OS upgrade, server reboots. On reboot, server will go back to ‘ISO install screen’ (this is seen in JViewer remote console). Unmount the ISO and reboot the server to boot from the disk. This issue occurs if the OS upgrade is performed from the shell. However, if the OS is upgraded from the Platform Manager this issue does not occur.

Issues Resolved

Please Log in to view Issues Resolved for Release 04.00.01R000 page.

Known Issues

Please Log in to view Known Issues for Release 04.00.01R000 page.

Known Limitations

Please Log in to view Known Limitations for Release 04.00.01R000 page.