User guide

Dialogic
®
DSI Development Package for Linux - Release Notes Release 6.6.1
6
3.7 TCAP - Event Indication Messages
The TCAP Maintenance Event Indication and Software Event Indication
messages have been enhanced to include a 12 octet parameter area for
additional diagnostic information as defined in the TCAP Programmer’s
Manual.
3.8 TCAP – Tracing TCAP Management messages
The ability to trace management messages has been added to the TCAP
module.
3.9 TCAP/MAP – Sending NC to TCAP
This release corrects a fault where Network Context (NC) is not sent to TCAP
after the user sends a MAP_MSG_DLG_REQ, MAP-OPEN-REQ message with a
NC parameter (MAPPN_NC). This only happened when the user doesn’t send
any Service Requests (MAP_MSG_SRV_REQ), but follows the MAP-OPEN-REQ
with a MAP-DELIMITER-REQ message. This release corrects the fault and will
include a TCAP NC parameter in the TCAP BEGIN message if no TCAP Invokes
were sent (the TCAP Invoke message is normally used to pass NC). The NC
parameter is only passed to TCAP if its value is non-zero (the default NC).
TCAP now correctly processes NC if received in a Dialog request.
3.10 SCTP/SCTPD – Path Selection (IPY00102645)
This release corrects an issue handling the situation where a lack of heartbeat
on the active path is detected. The previous release would send a message
on the failed path before resending on the correct alternative path. This
release uses the alternative path as soon as the heartbeat failure is detected.
3.11 SCTPN – Peer Addr Stats (IPY00102687)
In the previous release, if an address value greater than the number of peers
was used in the SCTP_MSG_R_PEER_ADDR_STATS then an erroneous
address could be returned. In the new release the module will return a null
address (0.0.0.0) and the status will be marked as inactive.
3.12 SCTPN – INIT Operation
This release corrects the number of INIT retransmissions to agree with the
user configured RTXI parameter in the SNSLI command and corrects the
value of the SCTP T1i timer as configured using the CNTOS command.
The ability to optionally user-configure the maximum number of consecutive
INIT retransmissions on a single path has been added using the new RTXP
parameter in the SNSLI command. The valid range is 1 to 20.
3.13 M2PA – Japan Priority Support
This release adds support for the PRI field in the M2PA header field for use in
Japanese networks. To invoke this feature, bit 4 should be set in the M2PA
per-link options. When using s7_mgt this is achieved using a new
M2PA_OPTIONS parameter for the SNLSI command as follows: