User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.3.8

5.2 SCCP – Segmentation/Re-Assembly for XUDTS

This release extends segmentation and re-assembly functionality to include

XUDTS messages. SCCP now handles segmentation and re-assembly for

XUDTS messages in the same manner as XUDT messages.

5.3 TCAP - Include TCAP Version in outgoing messages

This release adds an option to force the TCAP module to include TCAP

Protocol Version information in the messages it sends to SCCP. The TCAP

Version information sent for ITU identifies Q.771-5 1997 (and 1993)

specifications and for ANSI T1.114 1996.

This option is enabled by setting bit 12 of the ‘options’ parameter in the

TCAP_MSG_CONFIG message or bit 12 of the <options> field in the

TCAP_CONFIG command in config.txt.

5.4 TCAP - Option to stop sent address being replaced

by received address

This release adds an option to force TCAP to always use the original Called

Party Address throughout an outgoing dialogue rather than allowing it to be

replaced by the address received in the first response received from the far

end. To activate this feature, bit 11 of the <options> parameter in the

TCAP_CONFIG command should be set to 1.

5.5 MAP - Selective Tracing enabled by default

Selective Tracing within MAP, as documented within the MAP Programmer’s

Manual, is now enabled by default for all events. If required the

MAP_MSG_S_SELTRACE_MASK message can be used to modify which events

are selectively traced.

5.6 M3UA - SLS Rotation – 8 bit option

The ‘options’ field of the M3U_MSG_CNF_INT_NA message has been extended

to support a new option to allow full 8 Bit SLS rotation. Bit 0 should be set to

1 to activate SLS rotation. When SLS rotation is activated, ‘options’ bit 1 is

set to 1 to select 8 bit SLS rotation or set to zero for default SLS rotation

based on MTP label format.

5.7 M3UA - Selective Tracing

M3UA operation has been enhanced to automatically generate a trace of any

received message that results in generation of an M3U_MSG_M3U_EVENT

(0x02ee) event indication. The trace is intended to assist with problem

diagnosis and is sent to the trace module id (0xef by default but may be

configured with the TRACE_MOD_ID <trace_id> command)