User guide

Dialogic
®
DSI Development Package for Linux - Release Notes Release 6.5.1
17
When used with configurations that include MTP User protocols such as ISUP
or MAP, LAS1 will be configured with the appropriate Service Indicator and
Module ID automatically. For all other LAS values the MTP_USER_PART
command should be used. s7_mgt does not configure protocols which run
above LAS2, LAS3 and LAS4.
To define the service indicator and the module ID of the application or
module to process messages for a specific LAS, the MTP_USER_PART
command should be used.
LAS ID value
Network Context Value
Default M3UA Module ID
1
NC0
0xd2
2
NC1
0xd6
3
NC2
0xd7
4
NC3
0xd8
For example:
MTP_USER_PART NC0 05 0x2d
MTP_USER_PART NC1 05 0x3d
MTP_USER_PART NC2 05 0x6d
MTP_USER_PART NC3 05 0x5d
To send traffic for additional LAS’ the following lines need to be present in the
system.txt file, to send messages to the correct module ID.
LOCAL 0xd2 * M3UA module
REDIRECT 0xc2 0xd2 * Management task
REDIRECT 0xd6 0xd2 * M3UA LAS2/NC1
REDIRECT 0xd7 0xd2 * M3UA LAS3/NC2
REDIRECT 0xd8 0xd2 * M3UA LAS4/NC3
The CNOPS and CNNCI commands now support multiple network contexts.
The optional “NC” parameter can be used to identify the M3UA network
context for which the remaining parameters apply. The M3UA network
context is linked to the LAS as described in the table above. If the “NC”
parameter is omitted the configuration applies to NC 0/LAS 1.
CNOPS:MODULE=M3UA,MOD_ID=0x6d;
CNOPS:MODULE=M3UA,MOD_ID=0xfd,NC=1;
2.14 M3UA – Routing Key Management
This release adds support for the Routing Key Management (RKM) procedures
when operating as an ASP. M3UA will send REG_REQ and DREG_REQ
messages and handle the respective REG_RSP and DREG_RSP responses.
Further details are available on request.