Dialogic DSI SS7G41 How to use

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes
1
Dialogic®DSI SS7G41 Signaling Server
SIU Mode Release Notes
Document Reference: RN001LGD
Contents
Release 2.4.3................................................................................................................2
Release 2.4.1................................................................................................................3
Release 2.3.9................................................................................................................5
Release 2.3.2................................................................................................................9
Release 2.2.9..............................................................................................................12
Release 2.2.3..............................................................................................................18
Release 1.3.9..............................................................................................................28
Release 1.3.6..............................................................................................................29
Release 1.2.10 ............................................................................................................35
Release 1.2.5..............................................................................................................38
Release 1.2.3..............................................................................................................39
Release 1.1.1..............................................................................................................43
Release 1.1.0..............................................................................................................45
Release 1.0.5..............................................................................................................47
Release 1.0.2..............................................................................................................50

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.4.3
2
Release 2.4.3
1Overview
This release is a maintenance release which includes support for multiple host
modules in DTS mode as well as providing further changes and corrections as
detailed below.
This is the first release since Release 2.4.1 and it is fully backwards
compatible with that previous release.
1.1 Applicability
This release is suitable for all users.
2Changes
2.1 DTS –Per-LSS User module_id’s
When using DTS between SCCP and the Local Sub-System (ie. DTS Mode A),
this release enhances operation of the SCCP_LSS command to allow Local
Sub-Systems using DTS to make use of different USER_ID (module_id)
values (rather than having to use the fixed DTC module_id).
This facilitates additional flexibility in designing systems with multiple hosts
and multiple Local Sub-Systems (including the ability for traffic to bypass DTC
as it passes up the stack). By default incoming SCCP traffic is shared across
all available hosts, however use of the DTS_ROUTE command allows the user
to create specific host assignments.
2.2 SCTP –Enhanced internal architecture
This release includes an updated SCTP implementation which has been
enhanced to spread the processing load over multiple CPU cores to provide
improved utilization of available CPU bandwidth.
The updates to SCTP also address a number of protocol issues and errors
including correcting an issue that could result in SCTP locking up and causing
a restart of the unit.
2.3 M3UA –Failure to Restore Link
This release corrects an issue within M3UA that potentially could result in a
failure to correctly restore an Association following failure of an active link.
2.4 Diagnostics
This release introduces some additional diagnostic capabilities and measures
to guard against excessively large system logs in the snapshot file.
Dialogic
13-Dec-16
Revised 14-Dec-16

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.4.1
3
Release 2.4.1
1Overview
This is a maintenance release which includes changes and corrections as
detailed below.
This is the first release since Release 2.3.9 and it is fully backwards
compatible with that previous release.
1.1 Applicability
This release is suitable for all users.
2Changes
2.1 MTP3 –STP Operation
This release includes important corrections to operation of MTP3 in STP
configurations when using C-links. These changes ensure reliable generation
of preventative TFP messages prior to routing over a link set and generation
of TFA messages after stopping using a link set to reach the destination.
2.2 ISUP –ISP_MSG_MAINT_IND
When operating with 128 circuit groups, ISUP will no longer generate
ISP_MSG_MAINT_IND (0x070a) messages.
2.3 ISUP –Application Heartbeat
The ISUP Application Heartbeat mechanism has been enhanced to require two
failed attempts prior to declaring the host as failed. Each attempt allows 4
seconds for receipt of a response. When operating with more than 128 circuit
groups, the period between successive heartbeats is reduced (to 7 seconds)
and the rate at which Circuit Groups are automatically blocked is increased
(to 100 groups per second). This ensures better detection and faster
response in the case of high capacity systems.
2.4 M3UA –Error Indications
This release limits the maximum number of event reports from M3UA to one
per DPC every 10 minutes when it is unable to send a message to a
Destination because it is unavailable or unknown.
2.5 M3UA –Load sharing
M3UA now correctly load shares across multiple associations in the case that
there are between 5 and 16 associations to a Remote Application Server or
Signaling Gateway. Previously the maximum supported was 4 associations.
2.6 M3UA –SCON without congestion level
This release will accept an SCON message with no congestion level parameter
and handle it as indicating congestion rather than no congestion.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.4.1
4
2.7 Message Router –SSF Spare Values
This release corrects the coding of the ITU MTP3 Sub-Service field when
interworking with other signaling variants (such as ANSI) so that spare bits
are correctly set to zero.
2.8 Message Router - Performance
This release includes an optimization within Message Router Origin operation
to improve performance in the case that the OGID values are not allocated
from a contiguous block commencing at a low number.
2.9 MMI –Press return to continue
If after waiting 30 seconds for the user to respond to the “Press return to
continue” on the MML interface the user has not entered anything the current
command will be aborted and the text “EXECUTED” displayed.
2.10 Snapshot Generation
This release corrects an issue which prevented successful generation of a
snapshot file as a result of exhaustion of internal file descriptors. The issue
also caused reports of disk drive failure and Ethernet port failure.
Dialogic
21-Sep-16

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.9
5
Release 2.3.9
1Overview
This is a maintenance release which includes a number of minor changes and
corrections as detailed below.
This is the first generally available release since Release 2.3.2 and it is fully
backwards compatible with that release.
1.1 Applicability
This release is suitable for all users.
1.2 Resolved Customer Issues
The following customer issues are resolved in this release: IPY00117001,
IPY00117190, IPY00117249, IPY00117305, IPY00117310, IPY00117345,
IPY00118008 and IPY00118009.
2New Functionality
2.1 SCCP –GTT Capacity
This release increases the number of Global Title Translations supported per
Network Context to 512.
3Other Changes
3.1 Software Licensing (IPY00117310)
During restart, on detection of a new software license the unit will
automatically perform a full hard restart so that the new license takes effect.
3.2 Disk Partition Full (IPY00118008)
This release corrects an issue that could, in the case of a large number of
failed login attempts, result in one of the partitions on a hard disk filling to
capacity. In turn this prevented correct creation of new user accounts with
the result that new users were unable to gain SFTP access to the unit. This
release corrects the issue by enforcing a limit on the maximum size of the
offending log file.
3.3 Management Hosts (IPY00117190)
This release corrects an issue introduced in Release 2.2.3 where configuration
of the optional second management host using the API_MSG_COMMAND
message resulted in a restart of the system.
3.4 CNBOS Command - Board Configuration
This release checks the mandatory BRDTYPE parameter for the CNBOS
command and rejects the command if the parameter is invalid or omitted.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.9
6
3.5 Use of ITU-T links at 56kb/s
This release includes a correction to allow ITU-T SS7 links to optionally
operate at 56kb/s. Previously only ANSI links supported 56kb/s operation.
3.6 SS7MD Link Congestion Count (IPY00118009)
This release contains corrections to the operation of two per-link
measurements for the SS7MD board, the ‘Congestion Count’ and ‘Tx
Messages Discarded’.
3.7 STSLP Command - SS7 Link Status
This release corrects operation of the STSLP command to allow use of the
LINK parameter to display status for a single link.
3.8 Message Router - Alias Point Code (IPY00117354)
Previously, if a Message Router concerned relationship was configured where
the concerned entity was in a different Network Context from the Point Code
it was concerned about an implicit route to an alias Point Code would be
created in the Network Context of the concerned entity. Configuration of an
SCCP RSP using this alias Point Code was rejected. This release corrects this
issue and allows a SCCP RSP to route to an alias Point Code.
3.9 Message Router –Concerned Entity
This release corrects operation of Message Router Concerned Entity mapping
in the case where the concerned domain is a User Part (ie
CONC_DOMAIN=UPART) and the concerned entity is in a different network
context to the affected entity (ie. CONC_NC != NC). Previously status
indications were not passed to the user part in this case.
3.10 Message Router –Message Priority
This release corrects an issue that potentially resulted in message priority
getting set to zero when a message passes through the Message Router
Function.
3.11 Message Router - Destination DPC (IPY00117249)
This release corrects an issue introduced in Release 2.2.9 which prevented
correct operation of the Message Router Destination DPC parameter when
using 24 bit point codes.
3.12 Message Router - Measurements
This release corrects the ‘period’ reported in measurements for Message
Router Origins, Routing Keys and Destinations. This applies both to the user
interface and to periodic measurements files.
3.13 SCCP Load Share Table - Dynamic Addition
This release corrects an issue which prevented dynamic addition of an
additional DPC to an SCCP Load Share Table.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.9
7
3.14 SCCP –GTT using Translation Type 2
This release corrects operation when configuring SCCP Global Title Translation
rules which use GT Translation Type 2. In previous releases, using an odd
number of GTAI digits in the pattern or address (including any separators)
would cause the Signaling Server to incorrectly pad the GTAI digits with an
additional zero. This has been corrected.
3.15 SIGTRAN Route - Congestion Level
When viewing the status of a SIGTRAN route (using the browser interface or
the STSRP command) the current congestion level is now displayed using the
CONG_LEVEL parameter.
3.16 SIGTRAN Link Port Validation (IPY00117305)
This release provides enhanced checking of SIGTRAN link configuration
parameters to prevent invalid configurations being accepted but subsequently
failing to operate. Specifically all associations using the same local port value
must use the same set of Local IP addresses.
3.17 SIGTRAN Link Measurements
This release corrects reporting of the ‘Out of Service Duration’ for M2PA links
and allows SIGTRAN Link measurements on page 1 (SCTP) and page 2
(M3UA) to be individually reset on a per-page basis.
3.18 DTS Routing (IPY00117001)
This release corrects the operation on the ‘Route on Billing ID’ when using
DTS in conjunction with host-based IS41.
3.19 ACPOS Command - Account Control Policy
This release corrects operation of the Account Control Policy Configuration
command, ACPOS when the WMSER parameter is set to HTTPS.
3.20 License Commands
The licensing configuration and status commands have been improved. The
CNLCP command now reports the actual licenses present on the system and
their throughput, where applicable, in link equivalents. The STLCP command
reports the actual capacity, in link equivalents, of the licensed transport layer
capabilities.
3.21 Log files
Following a restart, logging to the mmi, maintenance, stats and alarms log
files now appends to the existing file rather than starting a new file. This
ensures better utilization of the available disk capacity.
3.22 IP Logging
This release corrects an issue that previously could result in PCAP logging to
the syslog/iplog file stopping spontaneously.
Operation of IP has been enhanced so that it continues to operate during
periods of system overload. Previously logging was disabled during periods of
overload.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.9
8
3.23 Snapshot Generation
Generation of snapshot files for diagnostic purposes now takes place in the
background so that user access can continue whilst the snapshot is being
created. During creation, the snapshot is called snapshot_notready.tmp, once
read for use access it is renamed snapshot.tgz.
3.24 Security Enhancements
This release disables the ability for TLS encryption to be negotiated down to
SSLv3 or lower to reduce the potential for ‘POODLE’ type ‘man in the middle’
security attacks.
When executing the ACPOS command this release checks for a certificate
before accepting WMSER=HTTPS for configuration of ‘HTTPS only’ operation.
When using HTTPS certificate files it is no longer necessary to perform a
restart. Instead the unit checks for a certificate file at the point the IPWSS
command is used to set HTTPSCERT=FILE.
This release includes an update to the web server within the web
management interface in order to guard against potential vulnerabilities.
Dialogic
04-Apr-16
Revised 15-Jun-16

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.2
9
Release 2.3.2
1Overview
This release is a feature release which adds the ability to gather
measurements on a periodic basis and store them in CSV format.
Measurements are available for different layers of the protocol stack and are
useful for traffic measurements and performance monitoring.
The release also supports new load balancing capabilities within the Message
Router Functionality through the ability to configure SLS rotation and
inversion on a per Custom Profile basis.
The release provides a fourfold increase in capacity for PCAP trace files
allowing more information to be retained, includes enhancements to MAP
operation and further changes and corrections as detailed below.
This is the first release since Release 2.2.9 and it is fully backwards
compatible with that release.
1.1 Applicability
This release is applicable to all users.
The following user documentation describes fully the Periodic Measurement
Collection capability:
Dialogic®DSI SS7G41 Performance Measurements Reference Manual Issue 2.
2New Functionality
2.1 Periodic Measurement Collection
This release adds the ability to gather measurements on a periodic basis and
store them in CSV format. Measurements are available for different layers of
the protocol stack and are useful for traffic levels and performance
monitoring.
Traffic measurements include, for example, the number of messages sent and
received, the number of octets sent and received, the peak traffic rate and
peak link utilization. Performance monitoring includes features such as error
counts (to assist detection of transmission path issues), routing failure causes
(to detect possible configuration issues) and a number of other parameters to
assist with smooth operation of the network.
Measurements are collected on a per-entity basis (eg per-link, per-origin,
per-network context) basis according to the type of measurement. The
frequency of measurement collection can be selected on a per measurement
type basis from the following values: 5 min, 10 min, 15 min, 30 min, 1 hour,
4 hours and 1 day.
Measurements are logged to a file called “stats.csv” in the syslog/stats
subdirectory of the user account. The file will accumulate data until the file
size reaches a maximum at which point a new file will be created and the
original will be rotated into a file called “stats.n.csv” where n is a digit. A
maximum of 10 files will be retained.
This release supports collection of the following measurement types:

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.2
10
LIU port,
SCTP link,
M2PA link,
M3UA per network context,
M3UA per network context peak traffic,
M3UA per-link,
M3UA per-link peak utilization,
MTP2 link,
MTP3 link set,
MTP3 per link peak utilization
SCCP per network context
Message Router Origin,
Message Router Destination,
Message Router Routing Key.
Control of the period for each measurement is provided using the System
Administration > Server Management > Diagnostics > Stats Reports menu.
2.2 Message Router Load Balancing
This release adds the ability for a Message Router Custom Profile to provide
configurable SLS rotation or inversion on a Origin, Destination or Routing Key
basis to compensate for SLS imbalance on incoming traffic. The SLS
parameter for the MRF_CP defines the algorithm as follows. SLS parameter
values R0, R1, R2, R3 and R4 rotate the SLS 0, 1, 2, 3 or 4 bits respectively
whilst values I0, I1, I2,I3 and I4 values invert the SLS as well as rotating it.
2.3 Increased PCAP Trace Capacity
This release provides a fourfold increase in the capacity of PCAP format trace
logs in the syslog/trace subdirectory of the user account. The maximum file
size has increased from 5MByte to 20Mbyte.
2.4 MSSCP Command –SCCP Measurements
A new command, MSSCP, has been introduced to report global SCCP
measurements for each Network Context.
2.5 MSSTP Command –M3UA Measurements
The SIGTRAN link measurement command, MSSTP, has been extended to
report M3UA peak utilization on page 3 of the command.
2.6 MAP –Additional Services
This release enhances support for the Provide Subscriber Information service
in line with MAP specification 3GPP TS 29.002 V8.12.0 as well as introducing
support for the proprietary MAP service –Update Device Configuration (UDC).
The coding and usage of these services is documented in the MAP
Programmer’s Manual.
3Other Changes
3.1 SS7LD Clock Operation
This release corrects a clock recovery issue which in some circumstances
resulted in the unit either attempting to recover clock from the wrong E1/T1
interface or entering holdover mode rather than switching to the next highest
priority clock recovery source.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.3.2
11
Operation of the SS7LD board is that when set to recover clocks it will always
use the lowest numbered interface that contains a suitable signal. When
using drop and insert to pass bearer circuits to a media processor, the user
should take care to use the lowest number interfaces for network facing
connections and the highest numbered interfaces for local (media)
connections.
3.2 IP Logging
This release corrects operation of the IPLGI command by ensuring that the
command is only accepted if the IPADDR parameter is set to an actual IP
address value. Previously IP logging could be inadvertently disabled.
3.3 Alarms - Severity
The setting of the ‘Alarm Severity’ field in the alarm log has been corrected
so that the original severity is retained even when the alarm has cleared. The
‘Alarm State’ should be used to determine which alarms are currently active.
3.4 Alarms –SCTP Path Failure
This release corrects an issue with the SCTP Path Failure alarm which
sometimes prevented the alarm clearing when the path recovered.
3.5 MSSLP Command –Peak Utilization Monitor
The per link Peak Utilization Monitor on page 3 of the MSSLP command now
reports Peak Rate to one decimal place and Peak Load to two decimal places
in Erlangs for MTP2 links and Link Equivalents for M2PA links.
3.6 M2PA –Timer T2
This release corrects an issue which, in some cases, resulted in failure to start
M2PA timer T2. This ensures that if the peer is not responding the link will
periodically drop back to Out of Service and then reattempt alignment.
Dialogic
28-Nov-14

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.9
12
Release 2.2.9
1Overview
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.
2New 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.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.9
13
NOTE: If a software release (old or new) is manually loaded and the unit
restarted without using the RESTART=PREVIOUS then the restoration
procedure will not revert to previous configuration files.
2.2 SCCP –Rebalance of Class 0 Traffic
This release introduces the ability for Connectionless Class 0 SCCP traffic to
be evenly balanced towards a Remote Signaling Point through regeneration of
the SLS in a cyclic manner.
The option can be selected on a per-RSP basis by setting bit 6 in the
rsp_flags field of the SCCP_SSR command when configuring the Remote
Signaling Point.
2.3 SCCP - Multiple Global Title Translation Tables
This release introduces the concept of multiple Global Title Translation Tables
which allows the MAP user to select a different SCCP routing plan on a per
dialogue basis.
Selection of the Translation Table is performed using a new integer parameter
RIID (Routing Indicator Identifier) which takes a value between 1 and 65535
and acts as a token to identify the table. Refer to the MAP Programmer’s
Manual for further details.
The RIID parameter is optional and can be used when configuring the GT
Translation (in the SCCP_GTT config.txt command), and when configuring a
Remote Signaling Point (in the SCCP_RSP command).
2.4 MAP –Update MAP LCS Services
This release updates the MAP Subscriber Location Report and Send Routing
Info for LCS services to MAP TS 29.002 v12.3.0 to allow more data to be sent
and received.
2.5 MAP –Options to Control Default TCAP QoS
This release adds two new global MAP options to control the default value for
the Quality of Service (QoS) parameter sent to TCAP (when QoS is not
explicitly specified by the MAP user). These options are supported in the
OPTIONS parameter of the MAP_CONFIG command as follows:
Bit 8, when set, causes the ‘Return on Error’ field to be set by default.
Bit 9, when set, causes Sequence Control to be disabled by default (selecting
Class 0 operation).
2.6 SCTP –Per-association options
The following new per-association options are supported in the OPTIONS
parameter of the STN_LINK command:
Bit 8, when set, disables use of the Nagle algorithm to ensure that outgoing
packets are transmitted without delay.
Bit 9, when set, disables path MTU discovery and selects a fixed MTU value of
1438.
Bit 10, when set, designates the path associated with the first remote IP
address (RIP1) as the primary SCTP path that if available will always be used.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.9
14
2.7 Message Router - Dynamic Configuration of Origins
This release adds two new commands, MROGI and MROGE, which (subject to
certain prerequisites) permit dynamic addition and removal of Message
Router Origins.
To add a new Origin, first add a new MRF_OG command to config.txt then
execute the MROGI command. To remove an Origin, first remove the
MRF_OG command from config.txt then execute the MROGE command.
To dynamically add Origins, there must already be at least one active origin
that uses the same NC / DOMAIN / SI combination. Likewise it is not possible
to dynamically remove the last Origin using a specific NC / DOMAIN / SI
combination.
2.8 Message Router –Alternative Destinations
The Message Router Function allows messages for a given destination to be
routed based on the availability of one or more DPCs associated with the
destination. The MRF_DE command supports a new DPC parameter. If
present the status of the configured DPC will be checked and the table row
will only be selected if the DPC is available. If available this DPC will be copied
into the routing label of the message.
3Other Changes
3.1 Alarms
A new alarm, "SS7 link cong", is reported when an SS7 link is in congestion.
A new alarm, "SCTP path fail", is reported for a SIGTRAN link when one or
more paths within an active SIGTRAN association have failed.
The release includes a correction to avoid incorrectly reporting “File Sys
Warning” alarms.
Parse errors are now reported on Page 2 of the active alarm list.
3.2 Dual Operation
This release corrects an issue that previously could result in a failure of two
units operating in a dual configuration to correctly exchange remote
accessibility data.
3.3 SS7LD Board –MTP2 T6 Timer Operation
MTP2 on the SS7LD Signaling Board has been corrected such that it no longer
starts the T6 timer upon reception of SIB when the link is in service and the
retransmission buffer is empty.
3.4 Message Router –Concerned Entities
This release enhances the operation of Message Router, Concerned Entity
notifications to prevent multiple identical notifications being issued at the
same time and to remove unnecessary delay when communicating status
changes to multiple entities.
This release also removed a restriction that previously allowed only one
Concerned Entity to be concerned about a specific DPC in a different Network
Context.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.9
15
3.5 LIU Control
This release provides the ability for test purposes to dynamically control Line
Interface Unit operation on E1/T1 interface ports. The Maintenance PCM Set
(MNPCS) MMI command allows the setting of diagnostic loopbacks,
generation of AIS and generation of PRBS data on the interface. The
command syntax is:
MNPCS:PORTID=[,AISGEN=][,LOOPMD=][,PRBSGEN=];
Current settings for the AISGEN, LOOPMD and PRBSGEN are displayed on the
PCM Status (STPCP) command. Modifications to the default values for the
parameters are not preserved over a system restart.
3.6 MSSLP Command - SIGTRAN Link Measurements
This release corrects the measurement period reported on page 2 of the
MSSLP command following change of system time.
3.7 STSTP Command –SIGTRAN Link Status
Page 2 of the SIGTRAN Link Status command (STSTP) has been enhanced to
include the status of implicitly configured paths (configured within the SCTP
INIT or INIT ACK). It also reports additional per-path attributes.
3.8 SCCP - Dynamic Global Title Configuration
This release corrects the operation of dynamic Global Title Configuration to
preserve the sequence in which entries in the table are used irrespective of
the sequence in which they are added. The entry with the lowest GTPID value
is always used first.
3.9 MAP –Update Location Data (IPY00116450)
This release corrects handling of the Update Location service to ensure that
any unexpected or unsupported parameters data from a received message
are passed to the user in the MAPPN_ellipsis parameter.
3.10 MAP –Reporting of User Error codes (IPY00116444)
This release corrects the reported User Error Code values when TCAP Reject
components are received with Invoke problem codes of ‘Initiating Release’ or
‘Resource Limitation’. The respective codes MAPUE_initiating_release (38)
and MAPUE_resource_limitation (37) are now used.
3.11 MAP –Authentication Data Ellipsis revised
Coding of the responses for SEND-AUTHENTICATION-INFO-ACK and SEND-
IDENTIFICATION-ACK has been corrected. A new parameter
MAPPN_auth_set_list_ellipsis (737) is used for AuthenticationSetList table
data and the MAPPN_ellipsis parameter is used for top-level response results
tables for both services.
The MAPPN_send_auth_info_resp_ellipsis parameter is now obsolete and
code (652) is no longer used. Applications that use MAPPN_ellipsis and/or
MAPPN_send_auth_info_resp_ellipsis with these service responses should be
reviewed and re-compiled with the new header file. Full details are contained
in MAP Programmer’s Manual.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.9
16
3.12 MAP –Authentication Data received in multiple
messages
This release ensures that MAP correctly handles response authentication data,
even when received in multiple TCAP messages using TCAP segmentation
(TC-RESULT-NL messages followed by a TC-RESULT-L). This affects the MAP-
SEND-AUTHENTICATION-INFO and MAP-SEND-IDENTIFICATION services.
3.13 MAP –SLR ‘cellIdOrSai’ Table Coding
To improve compatibility with other switches (eg Huawei MSC), this release
accepts received SUBSCRIBER-LOCATION-REPORT (SLR) messages where the
‘cellIdOrSai’ table is coded either with an ASN.1 Primary tag or a Constructed
tag. For outgoing SLR messages the Constructed tag is always used.
3.14 MAP –Diameter Identity Parameters
The maximum size of Diameter Identity parameters has been increased to
255 octets as specified by MAP TS 29.002 v12.3.0.
3.15 SCTP –Primary Address Down (IPY00116703)
This release corrects an issue where an association to a multi-homed peer,
failed to establish if the peer responded to the INIT from a different address
than the INIT had been sent to even if that address had previously been
configured as a valid peer address.
3.16 SCTP –Maximum Retransmissions
The maximum number of times a HEARTBEAT message is lost before the
network address marked failed and the maximum number of times a data
chunk will be retransmitted before the association is aborted have both been
changed from a default value of 2 to a default value of 3.
3.17 SCTP - Reverse Path IP Filter
By default, reverse path filtering is enabled. This ensures that packets
received from a remote source IP address are only accepted when the packet
is received on the interface that would be used to send packets to that IP
address. The purpose of reverse path filtering is to prevent receipt of spoofed
IP packets. In some situations, (eg asynchronous routing) it may be
necessary to disable this filtering for correct multi-path operation.
Reverse Path Filtering can be disabled by setting RPFILTER=0 in the ACPOS
command (System Policy Management). By default RPFILTER is set to 1.
3.18 SCTP - Secure Mode
This release corrects the operation of “Secure Mode” for an SCTP association
when operating in multi-homing mode.
3.19 M2PA –Timer Granularity and Default Values
M2PA now supports 100ms granularity for all per-link timers and default
timer values have been changed to align with ITU-T Q.703 recommendations
as follows: T1 45s, T2 30s, T3 1.2s, T4n 8.2s, T4e 0.5s, T6 5.5s and T7 1.7s.
This release also corrects an issue where, in certain circumstances, M2PA
timers T3 and T4 were started simultaneously which could result in links
prematurely exiting the proving state.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.9
17
3.20 DTS –Host Status Requests Cause Restart
(IPY00116844)
This release corrects an issue introduced in Release 2.2.3 where multiple calls
to the DTS Host Status MMI command STDHP eventually lead to the system
spontaneously restarting.
Dialogic
03-Oct-14
Revised 23-Oct-14

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.3
18
Release 2.2.3
1Overview
This release is a significant feature release which adds support for IPv6, adds
the ability to provide Mobile Number Portability in conjunction with the
Dialogic®ControlSwitch™ System and provides a number of OA&M
enhancements.
IPv6 is supported for the configuration of SIGTRAN protocol software as well
as SIU host links (RSI), NTP, SNMP, IP Gateways and firewalls. IPv6 access to
the unit is permitted using Browser, Telnet, FTP, SFTP and SNMP.
Mobile Number Portability (MNP) is supported in conjunction with the Dialogic
Directory Services Engine (DSE) which contains the MNP database.
This release supports enhanced syntax for config.txt commands. 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
The release also includes major enhancements to the Alarm List including
addition of new fields, addition of an Alarm Log (which list historic alarms)
and the additional logging of alarms to a text file for offline analysis.
This release includes major new SNMP enhancements including the ability to
view the active alarm list using SNMP and provision for SNMP notifications on
changes of state of alarms. In addition, this release addresses an important
syntax issue with respect to the SNMP MIB.
This release is fully backwards compatible with Release 1.3.9, however there
are some important differences as follows which should be read and
understood prior to commencing installation:
This release should be used in conjunction with SNMP MIB V4.xx, which
owing to the correction of a syntax error in the MIB is not fully backwards
compatible with the previous MIB. A mechanism is provided to allow
users to select the previous mode of operation as a short term option to
ease migration. See below for details of the changes and how to retain
compatibility if required.
IP configuration is maintained when upgrading to this release however
downgrading to an earlier (pre 2.0.3) release will result in the reset of the
system IP configuration to its default values. It is therefore important to
take a backup of the config.txt and config.CF3 files prior to upgrading to
this release.
The IP configuration commands for local IP address configuration have
changed. Instead of using IPEPP/IPEPS to configure local IP addresses the
commands IPNIC/IPNIP/IPNII/IPNIE should be used.
For local IP Address configuration, IP Gateway and IP firewall
configuration rather than using a separate SUBNET mask the IP address
and netmask should expressed in CIDR notation where the IP address
and netmask are separated by the '/' character and netmask is a integer
identifying the number of leading (i.e. significant) bits in the mask.
IP firewall configuration is maintained when upgrading to this release
however downgrading to an earlier (pre 2.0.3) release will result in the IP
firewall configuration reverting to the values it held prior to system
upgrade.

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.
2New 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.

Dialogic®DSI SS7G41 Signaling Server –SIU Mode Release Notes Release 2.2.3
20
2.3 IPv6 Support and IPv4 Changes
This release adds IPv6 support and in doing so makes some changes to the
commands previously used for IPv4 configuration. IPv6 is supported for the
configuration of SIGTRAN protocol software as well as SIU host links (RSI),
NTP, SNMP, IP Gateways and firewalls. IPv6 access to the unit is permitted
using Browser, Telnet, FTP, SFTP and SNMP.
For both IPv4 and IPv6, static IP addresses are now specified in CIDR
notation containing IP address followed by the ‘/’ separator followed by the
subnet mask (which is an integer identifying the number of leading (i.e.
significant) bits in the mask).
To accommodate IPv6 configuration the old commands IPEPS/IPEPP have
been replaced (for IPv4 and IPv6) by the new commands IPNIC and IPNIP for
configuring IP Network Interfaces. The STEPP/MSEPP commands have been
replaced by STNIP and MSNIP which display status and measurements for the
network interfaces.
The IPGWx commands have been modified to support IPv6. As both IPv4 and
IPv6 networks can have a default gateway the ‘Default’ identification should
be assigned to the IPNW parameter rather than the IPGW id parameter.
When configuring non default gateways the IP Network and Network Mask are
both configured using the IPNW in CIDR notation.
A new config.txt command IP_TOKEN allows the user to create a token
associated with a numerical IPv6 (or IPv4) address. This token can then be
used throughout config.txt when configuring IP addresses without the need to
retype the full IP address each time.
2.4 SCCP_GTT Command
This release adds the ability to have separate Global Title Translation (GTT)
tables for incoming and outgoing messages. This is achieved by the addition
of a new optional parameter (GTTSRC) to the config.txt command SCCP_GTT.
When GTTSRC=LOCAL the command only applies for messages generated by
a local sub-system (ie. outgoing messages). When GTTSRC=REMOTE the
command only applies to messages passed up to SCCP from the network (ie.
incoming messages). If GTTSRC=ANY (or the parameter is omitted) the
command applies to all messages.
A new optional parameter (BAK_DUAL) has been added to the SCCP_GTT
command that when set to Y causes any SCCP messages that matches the
GTT pattern, but cannot be routed due to network failure, to be passed to
SCCP on the partner unit so that it can reattempt routing.
A new optional parameter (OPTIONS) which is reserved for future use has
been added to the SCCP_GTT command.
2.5 Mobile Number Portability Option
This release supports a purchasable run-time option which in conjunction with
Message Router functionality allows the SS7G41 to work in conjunction with
the Dialogic Directory Services Engine (DSE) which is an element of the
Dialogic®ControlSwitch™ System for the realization of Mobile Number
Portability. Further information on this feature is available on request.