User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.3.8

Operation of the MVD_MSG_LIU_STATUS and LIU_MSG_R_STATE messages

have been corrected to ensure the correct line interface status is always

reported.

When monitoring MTP2 Low Speed Links or Q.703 Annex A High Speed Links

using the SS7MD board, changes in the state of the MTP2 Backward Indicator

Bit are counted and stored in the NACK_count field of the MTP2

measurements.

Value validation for VCI/VPI values has been corrected and some restrictions

relaxed. For VPI values a maximum of 4 bits can be set and for VCI values a

maximum of 10 bits can be set. The total number of bits set applies across all

boards in a system. For systems where this constraint is too restrictive,

further information on VCI/VPI configuration can be supplied on request.

6.5 ssdl – Messages longer than 256 Octets

This release includes a correction within SSDL to ensure messages containing

more than 256 octets are correctly handled.

6.6 SCCP –Connection ID allocation

The method of allocating incoming SCCP Connection ID’s for Connection

Oriented operation has been enhanced so Connection ID’s will cycle through

the full range of values before reusing previous values.

6.7 TCAP - ASN.1 non-minimum length encodings are

now accepted

The TCAP specification Q.773 states that when ASN.1 encoding messages,

length encodings should use as few as possible octets, e.g. encodings such as

0x8174 and 0x820074 should both be sent as 0x74. Previously both the TCAP

module would reject received network messages that did not conform to this

rule. This restriction has been relaxed to accept messages use ASN.1 non-

minimal length encoding. Outgoing message are always encoded in

accordance with the TCAP specification using the minimum number of octets

for ASN.1 lengths.

6.8 MAP - GPRS Node Indicator parameter support

MAP services SendRoutingInfoForLCS and SubscriberLocationReport now

support the GPRS Node Indicator parameter, MAPPN_gprs_node_ind (123).

6.9 MAP - Correction to Ellipsis parameter processing

Unrecognised parameters in received MAP messages are stored in the MAP

Ellipsis parameter (MAPPN_ellipsis). This release corrects a problem (for some

services including CHECK_IMEI) that previously caused only the first

unrecognised parameter to be stored. A potential problem with ellipsis

parameter formatting has also been corrected.