User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.2.9

3.12 MAP – Invalid user-supplied Invoke id in response

If MAP receives an unknown Invoke ID in a response primitive in the

MAP_MSG_SRV_REQ message, a software event report will now be

generated. The event report uses the MAP_MSG_ERROR_IND message with

error code MAPSWE_USER_INVOKE_ID_UNKNOWN (27) with the id field set

to the UserDialogID and the first Diagnostic code set to the invalid InvokeID.

MAP will also optionally generate a selective trace message with trace reason

code MAPt_user_invoke_id_unknown (16).

3.13 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.14 SCTP - SCTP_MSG_TX_REQ Invalid Stream

If an invalid stream is passed from the user in a SCTP_MSG_TX_REQ

message it will now be rejected with a SCTPE_BAD_PARAM error code rather

than be rejected by the remote end after transmission of the message.

3.15 SCTP - Transmit Buffer Allocation

This release increases the number of SCTP Transmit Buffers allocated to

reduce the likelihood of entering congestion. Typically two buffers are used

for each data message and previously this resulted in congestion being

encountered at lower buffer occupancy than intended.

3.16 M3UA - Network Appearance Removal

Prior to this release M3UA would only process a M3U_MSG_UNMAP_NA

(0x72cd) message for M3UA links 0-3. This has been corrected and now

works for all M3UA links.

3.17 M3UA - Link Deactivation

Operation of the message M3U_MSG_DEACT_ASSOC (0x72cf) which causes

an association to shutdown has been changed back to the pre Release 6.2.3

operation such that an SCTP_MSG_ABORT (0x728c) is sent to SCTP to

requesting an immediate shutdown. This ensures more deterministic

behavior.

3.18 M3UA - DAVA causes crash

A problem within M3UA that potentially could cause the binary to crash upon

reception of DAVA (Destination Available message) from an SGP has been

corrected.