User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.3.8

6.15 SCTP/ SCTPN – Default Rx Window Size

This release addresses an issued identified with some Linux kernel SCTP

implementations which could result in the association failing under heavy

load. When configured in conjunction with s7_mgt from this release SCTPN

allows the kernel to use the system default receive window size.

Previously s7_mgt explicitly requested SCTP/SCTPN to use a receive window

size of 64K bytes. Now it requests SCTP/SCTPN to use the default window

size and within SCTP this is set to 64K bytes whilst for SCTPN it is set to the

default kernel value.

6.16 SCTPN - Default SACK Delay value

This release sets the default SACK delay value to 10ms which is more

appropriate for use in a telecoms network than the previous 200ms value.

6.17 SCTPN – Preventing unnecessary Tx message

discard

This release contains corrections to SCTP transmit operation to prevent

unnecessary message discard as the underlying transmit buffer reaches

capacity.

6.18 SCTP / SCTPN - Management Event Indications

SCTP and SCTPN now generate event indications to management whenever

the state of an association or a path within an association changes. The

messages (SCTP_MSG_STATUS_CHANGE, SCTP_MSG_NETWORK_STATUS &

SCTP_MSG_CONG_STATUS) are identical in format to the messages

documented within the SCTP Programmer’s Manual which are issued to the

SCTP user. The events are fully decoded by the updated s7_log binary.

6.19 SCTP - Long Heartbeat Memory Leak

This release corrects an issue where a received Heartbeat message in excess

of 300 bytes would cause a memory leak within the SCTP association and

eventually lead to association failure requiring module restart.

6.20 M3UA - Management error messages

Management error messages received from an M3UA peer contain a range of

‘Tags’, some of which were erroneously being rejected. The module has been

updated to accept all tags that can be present. In addition the range of error

codes allowed has been extended.

6.21 M3UA - MBM local traffic mode

A backwards compatibility issue for systems where MBM configuration

messages are still used has been rectified. The issue affected systems using

message based configurations where the ‘local traffic mode’ was set using the

MBM_MSG_CFG_AS (0x72f7) message. The traffic mode was not sent in ASP-

ACTIVE requests to the peer, but has now been rectified.