![Dialogic DSI SS7G41 Скачать руководство пользователя страница 40](http://html1.mh-extra.com/html/dialogic/dsi-ss7g41/dsi-ss7g41_release-notes_2493098040.webp)
Dialogic
®
DSI SS7G41 Signaling Server – SIU Mode Release Notes
Release 1.2.3
40
2.2
Message Router Functionality
This release includes new Message Routing Functionality. The Message Router
provides the ability to flexibly route messages between the Network Domain
(MTP or M3UA), User Parts and Sigtran Application Servers using M3UA. The
routing is based on the MTP routing label and allows messages from a specific
Origin to use individual Routing Keys to selectively match routing label
parameters and determine which Destination to be sent towards. The
Message Router can be configured to act as a Sigtran Signaling Gateway or
simple Signaling transfer Point (STP). The Signaling server can also behave
as an SCCP Router by configuring the Message Router to send traffic through
the local SCCP for Global Title Translation.
In addition to routing messages, the Message Router allows for the
maintenance and mapping of point code status across the Signaling Server.
The Message Router is able to respond to Signaling Route Set Test and
Sigtran Destination Audit messages and generate the appropriate Route
Status messages (eg Transfer Allowed/Transfer Prohibited and Sigtran
Destination Available/Unavailable) to adjacent for Point Codes. To preserve
operating flexibility, the user must explicitly configure the identity of nodes
that are concerned about the status of other nodes within the network. This is
achieved using the concept of Concerned Entities.
Measurements of traffic passing through each state of the Message Router
are automatically captured and accessible to the user. Message tracing can
optionally be enabled for diagnostic purposes to log to rotating file all
messages as they pass through the Message Router. In addition any
messages that are unable to be routed (either due to an inaccessible
destination or invalid routing configuration) are automatically logged as
selective traces to the trace log.
2.3
Deactivating Network Links on Loss of all Hosts
Normal SIU operation in the event that all host links have failed is to
deactivate any network facing links. This release extends the functionality by
allowing SIGTRAN M3UA links to be nominated on a link by link basis to be
considered as a ‘host’ link.
M3UA links can be nominated as ‘host’ links by setting bit 15 in the
<options> field of the STN_LINK command. If any SIGTRAN links have been
configured as ‘host’ M3UA links and all these links are down then all MTP and
any non ‘host’ M3UA links will be deactivated until at least one ‘host’ M3UA
link returns to service.
2.4
M3UA – Support for 4096 Routes
This release increases the maximum number of M3UA routes from 256 to
4096.
3
Other Changes
3.1
MNSSI command
The MNSSI takes a snapshot of key system data, storing it in a single file
(syslog.tgz) in the root directory of the ftpuser account. This release adds the
ability to include trace files in the snapshot file which is achieved by setting
the parameter TRACE=Y when executing the MNSSI command.