Dialogic
®
DSI SS7G41 Signaling Server – SIU Mode Release Notes
Release 2.2.3
19
Users should familiarize themselves with the full content of these release
notes prior to commencing deployment.
1.1
Applicability
Users are encouraged to use Release 2.2.9 which supersedes this release and
is now Generally Available to all users.
This release should be used in conjunction with DSMI MIB package V4.01 (or
later). Please note that due to a correction of syntax errors within the MIB
this MIB is not fully backwards compatible with the previous release however
an option is provided to allow the SS7G41 to operate in accordance with the
old MIB to ease migration. Please note the section on SNMP MIB Compatibility
below.
1.2
Resolved Customer Issues
The following customer issues are resolved in this release: IPY00115900,
IPY00115902, IPY00115903, IPY00115914, IPY00116128, IPY00116129 and
IPY00116136.
2
New Functionality
2.1
SNMP MIB Compatibility
The SNMP DSMI Notification MIB has been restructured to remove syntax
errors encountered with certain SNMP managers. This release should be used
in conjunction with V4.01 or later of the DSMI MIB package.
Due to the nature of the changes to the Notification and Alarm MIBs the
notifications transmitted by the system are not compatible with SNMP
manager using MIB packages earlier than V4.00. To provide for continued
backwards compatibility with earlier MIB packaged a new parameter, MIB,
has been introduced on the CNSNS command. By default this parameter is
set to a value of V4 however if a SNMP manager wishes to continue to use
MIB packages earlier than V4 the MIB parameter can be set to PRE_V4.
2.2
Enhanced config.txt Command Syntax
This release rolls out enhanced format config.txt command syntax for the
majority of the currently supported commands (whilst maintaining backwards
compatibility so that existing config.txt files continue to function as normal).
The new syntax allows parameters to be entered in any order and allows
optional parameters to be omitted. Each parameter is entered in terms of
parameter name and parameter value as follows:
<command>:<parameter1>=<value1>,<parameter2>=<value2>;
For example:
MTP_LINKSET:LINKSET=0,OPC=321,APC=320,LABEL=Paris;
Many commands support an optional user-provided text ‘LABEL’ parameter to
improve readability. This label parameter is used in both user output and
SNMP where applicable.
Full details of command syntax (and which commands support the new
format) are contained in
SS7G41 Operator’s Manual, Issue 9
.
