User guide
Dialogic
®
DSI Development Package for Linux - Release Notes Release 6.6.1
5
3 Other Changes
3.1 gctload – Missing data for –t4 mode (IPY00102752)
In the previous release the gctload module would only return correct license
data when using the ‘-t4’ mode if the command was run as root or run by the
user who originally started gctload. This release corrects the handling to
permit use of the ‘-t4’ by any user with appropriate normal user permission.
3.2 ISUP – Reset Circuits
This release modifies ISUP behavior so that on reception of a circuit reset or
group circuit reset from the network ISUP will now send a release with
clearing cause value 41 (temporary failure) rather than the previous of 31
(normal unspecified).
3.3 BICC – Auto-Blocking
This release corrects operation of the BICC protocol so that ISUP correctly re-
asserts blocking following receipt of a single circuit reset from the network on
a locally blocked circuit by issuing a CGB message. Previously blocking was
not re-asserted in this case.
3.4 SCCP – Additional Diagnostics
SCCP now generates Selective Trace messages when certain Software Events
or Maintenance Events occur. This contains the message that caused the
software or maintenance event to occur.
SCCP tracing has been enhanced to support tracing of messages broadcast to
the partner instance and error messages.
SCCP will now generate a Maintenance Event with event_code=18
(SCPEV_CO_NOT_CONFIGURED) if a Connection Request message
(SCPPT_N_CONNECT_REQ) is received from the SCCP User but Connection
Oriented operation has not been configured.
When configuration or management messages are rejected due to having
insufficient length of data in the parameter area the status value is now set to
value 11 (SCPE_BAD_MSG_LEN).
3.5 SCCP – SCCP Module ID configuration
SCCP now ignores the ‘module_id’ field in the module configuration message
(SCP_MSG_CONFIG). To run with a different module_id use the command
line option –m.
3.6 SCCP – Confirmation Messages
When confirming messages, SCCP will now issue the confirmation message
after processing the original message (previously some confirmation
messages were issued prior to processing).