User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.5.1

3.5 ssdm - LIU Statistics Gathering

This release corrects a threading issue which could result in the loss of LIU

statistics request messages which in turn could result in exhaustion of

messages in the software environment.

The condition was triggered either when multiple outstanding requests for LIU

statistics are present on the same port or when an LIU was reconfigured

whilst an outstanding statistics request was being processed. Both conditions

are now handled correctly.

3.6 SCCP – Round-robin routing using Load Share tables

This release adds an SCCP global title load share table option to provide

round robin selection of point codes. This option is bit 1 of the ‘options’ field

of the SCP_MSG_GLST_ADD message. When set to 1, successive messages

are sent to the next available destination point code in a round-robin manner

(irrespective of the SLS value in the message). When set to zero the SLS

value is used to determine route selection.

3.7 SCCP – Generating UDTS or SST response using RSP

pc_mask

This release corrects operation when generating UDTS or an SST response

towards a point code where the configured RSP (Remote Signaling Point) is

identified by a pc_mask (rather than an explicit match of the point code. This

ensures that the National Indicator is appropriately set from the configured

RSP data.

3.8 SCCP –Routing label format in API_MSG_TX_REQ id

SCCP can now optionally indicate the routing label format in the id field of

API_MSG_TX_REQ messages. This is achieved when using config.txt by

setting bit 2 in the <options2> parameter of the SCCP_CONFIG command.

For message-based configurations set bit 2 (SCPX2F_PC_SIZE) in the

‘ext2_options’ field of the SCP_MSG_CONFIG message.

When enabled the id field in the API_MSG_TX_REQ message will be set to 0

for 14-bit, 1 for 24-bit and 2 for 16-bit point codes.

3.9 ISUP - 8 Bit SLS Operation

This release corrects generation of 8 bit SLS values when using bit 22 of the

ext_1_options field for Circuit Group Configuration (ISPX1GOP_SLS8).

3.10 ISUP - Circuit group supervision message type

handling (IPY00100673)

On receipt of a Circuit Group (Un)Blocking message or acknowledgement

containing an invalid ‘Circuit Group Supervision Message Type Indicator’ field,

ISUP will now generate a Confusion Message with ‘cause’ set to 110.