User guide

Dialogic
®
DSI Development Package for Linux - Release Notes Release 6.2.9
46
3.19 MST - M3UA Message Parse Error
Previous releases incorrectly calculated padding bytes following variable
length parameters when recovering received M3UA messages. This resulted
in some lost messages and an incrementing count in the ‘Bad Format’ of the
per-module statistics. This fault, which typically only impacted messages
containing the optional ‘Correlation ID’ parameter, has been corrected.
3.20 s7_log - Additional Decode
s7_log now provides a full decode of all M2PA and M3UA status messages and
notifications. In addition when displaying TCAP software events, if an
unknown event is encountered it will display the <event_code> as an integer.
3.21 s7_mgt - Board Failure Diagnostics
s7_mgt now forwards SSD event notifications (MGT_MSG_EVENT_IND and
MGT_MSG_DIAG_IND) to module_id 0xef (REM_API_ID) to allow the events
to be logged by s7_log.
3.22 User Part Examples - Support for 64-bit Build
The User Part Development (UPD) make script, makeall.sh, has been updated
to allow the UPD examples to be built as 32-bit (default) or 64-bit binaries.
The commands to build the UPD modules as 32-bit binaries are:
./makeall clean
./makeall.sh 32bit
The commands to build the UPD modules as 64-bit binaries are:
./makeall clean
./makeall.sh 64bit
3.23 Device driver version written to kernel log
To facilitate diagnostics, the version number of the device driver is now
written to the kernel log. This version number is the same as the release of
the Development Package.
Dialogic
13-Apr-11