User guide

Dialogic
®
DSI Development Package for Linux - Release Notes Release Notes for V5.11
68
3.10 AMI with Zero Code Suppression
In previous releases configuration of a T1 interface using AMI with Zero Code
Suppression (ZCS) line coding did not maintain transparency of the timeslot
for SS7 signaling links. ZCS is now disabled by s7_mgt for any timeslots
containing SS7 signaling links.
3.11 File permissions for log files
In earlier releases, log files created by the s7_log module could only be read
by the user that created the file. In this release any user can read them
(subject to appropriate setting of the system umask).
3.12 SS7HD Board Information
Previous releases could report out of date board information in multi-board
configurations using hot swap functionality. This problem has now been
resolved.
3.13 SCTP corrections within SCTPN
A number of protocol corrections have been implemented within the SCTPN
module as follows:
- Validation of remote address information when a connection is received
from a client application has been corrected to prevent unconfigured remote
hosts from connecting and to prevent two associations using the same host
port.
- Receipt of an ABORT primitive is now handled correctly.
- A problem when running on a multi-core / multi-processor system,
where SCTP would begin, after about five minutes, to send an invalid
sequence of messages if no peer SCTP socket were listening has been
corrected.
- A problem related to receipt of a "configure association request" on an
active association has been corrected.
3.14 Unwanted MGT_MSG_NTP_SYNC messages
Previous releases of the s7_mgt module would send an
MGT_MSG_NTP_CONFIG message to each SS7HD Signaling Processor
irrespective of whether MONITOR_LINKS are configured to use time
stamping. From this release the message is only sent to a Signaling Processor
if monitor links are configured to use time stamping.
3.15 MBM not waiting for ASP_UP response
Previous releases of the MBM module would send an AS_ACT_REQ message if
no response were received to an ASP_UP request before it's guard timer
expires. From this release it generates another ASP_UP request.