User guide

Dialogic

DSI Development Package for Linux - Release Notes Release 6.3.8

6.10 MAP - TC-REJECT parameters passed to user

On receipt of a valid TCAP REJECT component from the network, MAP now

uses two new parameters to pass additional TCAP component data to the MAP

user for diagnostic purposes.

MAPPN_tcap_rej_problem_code (584) contains the Problem Code (0 to 7) of

the REJECT component and MAPPN_tcap_rej_problem_type (585) contains

the Problem Code tag that was used (0x80 to 0x83). The interpretation of the

problem code value is dependent on the tag used.

Reception of a valid REJECT component will cause a MAP-NOTICE-IND dialog

message or a MAP-SERVICE-CNF message (with error parameter) to sent to

the MAP-User. In both cases the two new parameters will now be returned in

the messages. For the MAP-NOTICE-IND message, the existing parameter

MAPPN_invoke_id (14) will now also be returned with the new parameters to

identify the component referenced by the REJECT (MAPPN_invoke_id is

already returned by the MAP-SERVICE-CNF message).

6.11 MAP - ASN.1 indefinite length termination octets

being returned in ellipsis data

When MAP encounters unrecognised data in received messages, it is returned

to the MAP-User in the Ellipsis parameter. In the previous releases where the

unrecognised data has been encoded using ASN.1 indefinite length encoding,

it is possible for length termination octets ‘EOC’ (two 0x00 octets) to be

returned at the end of the Ellipsis parameter data. This release corrects the

fault. Ellipsis parameter data will not be incorrectly terminated by indefinite

length encoding termination octets.

6.12 MAP - Begin Subscriber Activity with single address

For previous releases if the MAP-User specified only one of MAPPN_dest_ref

(2) and MAPPN_orig_ref (4) parameters, sending of the BEGIN-SUBSCRIBER-

ACTIVITY (BSA) service would be attempted and fail with

MAPSWE_TX_FMT_ERR being reported. This has been corrected so that if only

one of the parameters is present, it is ignored and the BSA component is not

sent.

6.13 MAP - MAPPN_unk_sub_diag in MAP NOTE-MM-

EVENT service

MAP now allows the optional parameter MAPPN_unk_sub_diag (61) to be

used in the response for the MAP NOTE-MM-EVENT service when a User Error

of ‘Unknown Subscriber’ is returned.

6.14 MAP - User and Provider Errors supported for all

services

MAP now allows the error parameters MAPPN_user_err (21) and

MAPPN_prov_err (22) in all MAP services that return a response to the MAP-

User.