User guide
Dialogic
®
DSI Development Package for Linux - Release Notes Release 6.5.1
16
2.11 M3UA – Additional Licenses
This release adds support for new higher capacity licenses of 384, 512 and
768 equivalent links. The full range of supported M3UA licenses and the
capacity of each is detailed in the table below:
Designation
Throughput
Max
Associations
TDM Link
Equivalents*
SS7SBHSTM3UAU
312kb/s
4
4
SS7SBHSTM3UAS
1,232kb/s
16
16
SS7SBHSTM3UAR
2,464kb/s
32
32
SS7SBHSTM3UAL
4,920kb/s
64
64
SS7SBHSTM3UAK
9,832kb/s
128
128
SS7SBHSTM3UAJ
19,664kb/s
256
256
SS7SBHSTM3UAM
29,496kb/s
256
384
SS7SBHSTM3UAN
39,328kb/s
256
512
SS7SBHSTM3UAP
58,984kb/s
256
768
SS7SBHSTM3UAG
78,648kb/s
256
1024
*This comparison assumes the use of 64kb/s links at a maximum loading of
0.6 Erlang. Individual user deployments may exhibit different characteristics
from this in which case it may be necessary to provision more or less capacity
accordingly.
2.12 M3UA – Support for 4096 Routes
This release increases the number of M3UA routes supported to 4096.
2.13 M3UA – Multiple Local AS support
This release supports the configuration and operation of multiple Local
Application Servers (LAS). Changes to the configuration model now enable
up to 4 LASs to be defined. Each LAS can be active across one or more
shared associations with traffic distinguished by Routing Context (RC).
A peer IPSP or SGP would typically have an entry in its routing table for each
LAS with a 1:1 mapping of routing key to LAS. For each routing key a RC is
defined which accompanies the traffic on the association, to identify the LAS-
server relationship to which it belongs. Previously all traffic was received by
the single LAS and then distributed based on SI to the user parts. With
Multiple LAS, traffic for a particular routing key from the peer SG or RAS is
treated separately and when it arrives at the ASP it is distributed to the
correct LAS, based on the RC. Each LAS-server relationship may be activated
or deactivated independently of any other.
This new functionality can be configured using s7_mgt using the “LAS”
parameter in place of the “AS” parameter in the SNAPI and SNLBI
commands. The RC value should now be specified on the SNLBI command.