![background image](http://html1.mh-extra.com/html/dialogic/dsi-ss7g41/dsi-ss7g41_release-notes_2493098046.webp)
Dialogic
®
DSI SS7G41 Signaling Server – SIU Mode Release Notes
Release 1.1.0
46
2.4
MAP - ProvideSubscriberLocation service
Support for the MAP ProvideSubscriberLocation service has been extended to
include additional parameters. The implementation is now compatible with
the MAP specification 3GPP TS 29 002 version 10.3.0 (Release 10).
2.5
MAP - ‘Additional Roaming Not Allowed Cause’
New MAP V3 services error parameters have been added in support of the
ProvideSubscriberLocation service. Additionally the new error parameter
‘Additional Roaming Not Allowed Cause’ is now supported. These new error
parameters are enabled for use by all MAP-V3 services supported by the MAP
implementation that use the applicable error codes.
2.6
M3UA - Multiple Local Point Codes
Configuration of Local Application Servers has been enhanced to allow Local
Application Servers to be configured within the same Network Context with
differing Originating Point Codes. M3UA will also support multiple local point
codes which operating in dual resilient mode while partnered with another
Signaling Server.
SCCP continues to support a single local point code per Network Context.
3
Other Changes
3.1
STTDP command - TCAP Dialog Status
The STTDP command now omits any dialogues that are in the IDLE state
resulting in a more compact display.
3.2
CNPCP command - PCM Status – Board Position
This release corrects the board position displayed by the CNPCP command
(which previously was one greater than it should have been).
3.3
MTP2 - HSL Links
This release corrects an issue which previously could result in restricted HSL
link throughput when operating over high latency links.
3.4
ISUP - 8 Bit SLS Rotation
This release corrects generation of 8 bit SLS values when using bit 22 of the
<options2> field for Circuit Group Configuration.
3.5
MAP - Ellipsis parameter in Dialog messages
When the MAP user specifies MAPPN_dest_ref and MAPPN_orig_ref
parameters together with MAP-V1 application context parameter in a MAP-
OPEN-REQ message, the MAP module automatically sends a Begin Subscriber
Activity (BSA) component to TCAP. Previously if the user also included the
MAPPN_ellipsis parameter in the message the MAP binary could terminate.
This issue has been corrected.
Dialogic
30-May-12