User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.4.0

3.6 TCAP - User Information in P-ABORT-IND

TCAP, when operating in ITU-T mode, has been enhanced to report User

Information from a received TC-P-ABORT Dialogue Portion to the user in the

‘TCPPN_USER_INFO’ parameter which is now optional for this message.

Previously User Information was only reported for TC-U-ABORT.

3.7 MAP - Accept MAP Refuse PDU from a TCAP P-ABORT

This release detects and decodes User Information contained in received P-

ABORT-IND messages. If the information is for a MAP-Dialogue PDU with

Refuse Info reason = ‘invalidDestinationReference’ or

‘invalidOriginationReference’, the module will send a MAP-OPEN-CNF message

to the MAP-User setting the appropriate MAPPN_refuse_rsn and with

MAPPN_result = ‘dialogue refused’ (1).

This results in a received MAP Dialogue Refuse PDU being reported to the

MAP-User in the same way, whether reported by TCAP as a P-ABORT or a U-

ABORT.

3.8 MAP - Reports timeout on Abort from TCAP

The TCAP module has an option (TCPF_DLG_TIM_ABORT) that will

automatically abort dialogues after a timeout period. MAP has been updated

to recognise these aborts and close the associated MAP dialog. When this

happens MAP will send a MAP-DIALOGUE-IND, MAP-P-ABORT-IND message to

the MAP-User with the new provider reason (MAPPN_prov_rsn) =

MAPPR_idle_timeout (7).

3.9 MAP - Diagnostic corrected when L_REJECT received

An invalidly formatted response message causes TCAP to send an L_REJECT

message (problem code = Badly Structured Component) to MAP and MAP will

then send a MAP-NOTICE-IND message with a problem diagnostic

(MAPPN_prob_diag) to the MAP-User. Previously MAP reported the problem

diagnostic ‘Response Rejected by Peer’ (1) with the Notice message. This has

been corrected for this release to report the problem diagnostic ‘Abnormal

Event Received from Peer’ (2).

3.10 MAP - ASN.1 BIT STRING encodings

This release ensures that sufficient parameter octets are available to convey

the maximum amount of ASN.1 BIT STRING encoded data required by the

MAP specifications. Previously some parameters only supported a single octet

which was insufficient.

The MAPPN_mwd_status parameter (which is the only parameter

encoded/decoded within the MAP module) now always sends six ASN.1 BIT

STRING encoded bits but will support receipt of three, four or six bits of

validly formatted ASN.1 BIT STRING data.