Dialogic
®
DSI SS7G41 Signaling Server – SIU Mode Release Notes
Release 2.2.9
12
Release 2.2.9
1
Overview
This release is a significant feature release which provides as a Generally
Available Release all the enhancements from Release 2.2.3 and a number of
additional enhancements as described below.
It contains the ability to automatically restore the previous configuration files
when reverting to the previous software release and supports the ability to
rebalance Class 0 SCCP traffic to ensure even load distribution. It includes
new SCTP configuration options, a number of MAP extensions and
enhancements to Message Router Functionality.
This is the first Generally Available release since Release 1.3.9 and it is fully
backwards compatible with that release. Users should read carefully the
release notes for Release 2.2.3 and Release 2.2.9 prior to installing this
release.
1.1
Applicability
This release is applicable to all users.
This release should be used in conjunction with DSMI MIB package V4.01 (or
later). A new SNMP MIB (V4.03) is available which additionally includes
definitions for the new alarms supported in this release.
The following user documentation updates are available for use in conjunction
with this release:
Dialogic
®
DSI Signaling Servers – SS7G41 Operators Manual, Issue 11,
Dialogic
®
DSI Protocol Stacks – SCCP Programmer’s Manual, Issue 11,
Dialogic
®
DSI Protocol Stacks – MAP Programmer’s Manual, Issue 21.
1.2
Resolved Customer Issues
The following customer issues are resolved in this release: IPY00116444,
IPY00116450, IPY00116703 and IPY00116844.
2
New Functionality
2.1
Software roll-back restores previous configuration
If it is necessary during a software update cycle to revert to the previous
version of software then the MNRSI command should be used with
RESTART=PREVIOUS. This causes the previous release of software to be
automatically reinstalled. From this release it will also automatically restore
the previous configuration files (config.txt, config.CF3 & SWS.CF3) that were
saved internally at the time of the software upgrade (providing the operating
mode (SIU or SWS) is not changed during the roll back).
This feature simplifies the process of reverting to an earlier software release
where the configuration file formats were not completely compatible (such as
reverting to a pre Release 2.0.0 version). Users are still advised to make their
own configuration backup prior to performing a software upgrade but the new
feature makes it less likely that it will need to be used.
