How to generate traces for SDK issues in Linux
This article describes how to enable a Dialogic® Diva® SDK trace in Linux.
There is no option to enable the Diva SDK trace via the Dialogic® Diva® System Release 9.6.xLIN Web GUI, so in order to activate the SDK trace, go to the Extended configuration as follows:
cd /usr/lib/opendiva/divas
./Config -extended
- select CAPI 2.0 interface and press OK
- you should now see the Diva Board selection. If your Dialogic® Diva® Media Boards are properly configured, you do not need to configure them again. In this case, you can select Continue and save configuration.
- the Extended configuration options will be displayed. Do not change any of the defaults except for the Diva SDK log level. Click on Please select DIVA SDK log level and select Profile 6 (all debug messages).
Click on the following image to view it full size
- next, you should see Please select Diva SDK log format. Select the default 2 Date and Time.
- for all further parameters, use the default settings.
- finally, save this configuration.
IMPORTANT NOTES:
1. The default directory for the SDK trace (dssdk.log) is /var/log/ which will run permanently in the background.
2. It is necessary to stop and restart the application after the logging level for the SDK has been changed, otherwise the changes will not take effect and the trace will not contain all desired information.
3. When the SDK trace is running in the background and the application has been restarted, reproduce the issue you have as quickly as possible and refrain from other activities or tests, since the Diva SDK trace may quickly become very large with this high logging level.
4. After you captured and saved a SDK trace, it is recommended to reset the SDK Logging Level to the one that was used previously, for example, profile 0 (OFF) or 1 (Error messages (default) to avoid unnecessary processor utilization and to conserve disk space. Remember to stop and restart the application for this changes to take effect.
5. For CAPI and ISDN level tracing, use the
./Trace utility, or in the SR 9.6.x LIN Web GUI, start traces via Debugging -> Trace/Debug.
See also:How to generate traces for SDK issues in Windows
How to generate a basic trace
Reporting SDK issues to Dialogic Support
First published: 22-May-2015
Open access: Product rule: ; Page rule: Auto
