User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.2.3

3.5 TCAP - Configurable trace module id

A Trace Module ID can now be defined in the TCAP Module Configuration

message (TCP_MSG_CONFIG). The new ‘trace_id’ field uses a previously

reserved field in the message. If trace_id is defined as non-zero, then all

trace messages are sent to that module id. If trace_id is set to zero, trace

messages are sent to the Management Module ID (mngt_id) as for previous

releases. For further information refer to the TCAP Programmer's Manual.

3.6 MAP - Message generation after MAP-NOTICE-IND

and/or TC-U-REJECT

For previous releases, MAP was not correctly handling some situations that

required MAP-NOTICE-IND messages to be sent to the user and/or U-REJECT

to be sent to TCAP and the dialog was left in an inappropriate state. MAP

should either close the dialog and send a MAP-CLOSE-IND message or move

to a next state and send the user a MAP-DELIMITER-IND message. This

release ensures that it is correctly handled.

In order to prevent unexpected behaviour in some MAP applications this

change can be disabled using a MAP configuration option.

It is recommended that this option should only be set when the messages

now being generated cause problems for the MAP application. Otherwise the

flag should be set to 0.

For further information refer to MAP Programmer's Manual.

3.7 SCTP - Bundled chunks (IPY00091767)

This release corrects the handling of multiple SCTP chunks in a single

message to ensure that all chunks are correctly delivered to the user.

Previously if more than ten chunks were received bundled in a single SCTP

message, delivery to the user was not guaranteed.

3.8 SCTPN - Preferred Path Selection

A new configuration option has been added to SCTPN to cause automatic

selection of the preferred path for routing whenever that path is available.

This means that in the event of recovery of the preferred path, traffic will

automatically revert back to the preferred path rather than continue using the

alternative path. This first host IP address configured for the association is

designated as the preferred path.

The functionality is activated by setting bit 5 in the options field of the SCTP

configuration message (SCTP_MSG_CONFIG). This can be achieved in

config.txt using the following command:

CNOPS:MODULE=SCTP,OPTIONS=0x0020;

3.9 SCTPN - Recovery from Congestion

Previously a problem within SCTPN resulted in a failure to recover correctly

from software environment congestion. Consequently SCTPN associations

would fail. This issue, which was introduced in the Development Package for

Linux 6.3.0, has been corrected.