Dialogic
®
DSI SS7G41 Signaling Server – SIU Mode Release Notes
Release 1.3.6
33
3.11
MAP - Multiple Network Contexts (IPY00102722)
This release corrects a fault when operating with Network Contexts other
than NC=0 when a MAP user sends MAP-OPEN-REQ followed by a MAP-
DELIMITER-REQ message without any Service Requests
(MAP_MSG_SRV_REQ)).
3.12
MAP - Formatting of Abort sent to TCAP
This release correctly formats the UABORT send from MAP to TCAP upon
receipt of an invalid or unknown DialogID in a message from TCAP.
3.13
MAP – Discarded ‘NotLast’ Components
This release corrects an issue that previously could cause parameters
received in a ‘NotLast’ Result response message from TCAP to be discarded.
This fault only occurred when the response was received in two or more parts
and parameter data was decoded for a ‘NotLast’ component and no
parameter data was decoded for the ‘Last’ component.
3.14
M3UA - Network Appearance
This release introduces the option to ignore the M3UA Network appearance
(NA) in received messages. This option is configured by setting bit 5 of the
STN_LINK options.
3.15
M3UA - Auditing of Congested Destinations
Previously when connecting to a Signaling Gateway, enabling the Destination
Audit (DAUD) option enables auditing of both unavailable and congested
destinations. This behavior has been modified so that congested destinations
are only audited in ANSI Network Contexts.
3.16
M3UA - Network Context Configuration
The STN_NC command requires that the <share> parameter be set when
multiple Network contexts are specified to ensure that the throughput is
correctly shared between different Network Contexts. Prior to this release this
rule was not fully enforced and it was possible to configure M3UA network
contexts without a share parameter that resulted in an incorrect distribution
of the License between the Network Contexts. This has been corrected to
ensure that <share> must always be set on the STN_NC command.
3.17
DTS Client and Routing Request Logging
The Signaling Server will now report DTS_ROUTING_REQ and
DTS_CLIENT_REQ messages to the management host and maintenance log
file.
3.18
Memory and File Sys Warning Alarms
The alarms “Memory failure” and “File sys err” have been renamed “Memory
warning” and “File sys warning” to reflect the less critical nature of the
condition. In the event that either of these warnings are indicated the user
should invoke a full system restart at the next suitable maintenance window
using the command MNRSI:RESTART=HARD;
3.19
SNMP – Memory Warning
SNMP operation has been modified such that if a memory warning alarm is
detected during startup an SNMP trap will be sent to the SNMP manager.
