Technical Helpweb

- more articles

How to generate traces for SDK issues in Windows

Depending on the nature of the problem it is often necessary to see which ISDN Cause Codes and CAPI error messages occurred. This may shed light on the possible cause of the issue. Apart from this, a Diva SDK trace is also required to see what is happening on the higher application layer. 

In general - unless Dialogic Support have given you specific instructions about the traces to take - it is recommended that you generate a Diva Diagnostic and corresponding SDK trace according to the following instructions: 

• Ensure that there are no other activities on the Diva Media board (e.g. incoming and outgoing calls), which are not related to the actual problem.
• Before you start the Diva Diagnostic trace with the red 'record' button:
  • Click on 'Select basic setting' ([B]) for all Driver and Adapter interfaces, except CAPI
  • For the CAPI interface click on 'Select extended setting' ([E])
• Start an SDK trace according as follows:
  • Launch CONFIG.EXE (SDK: in the \basic\bin\ directory)
  • Select the 'Logging' tab
  • Format: Time stamp included
  • If you use the Diva API: Select:
    • 'Debug messages level 2', if problem occurs during the connection establishment phase
    OR
    • 'Data transfer messages (large traces)', if the problem occurs during data transfer
  • If you use the Diva Component API:
    • Select the highest logging level: 'Debug messages level 4'
• Reproduce the problem with the SDK based application as quickly as possible and try to ensure that there are no other activities on the card during this time.
• As soon as the problem is reproduced, stop and save both the Diva Diagnostic trace and the SDK trace

Please note:

• It is necessary to stop and restart the application after the logging level for the SDK is changed. Otherwise the changes will not take effect and the trace may not contain all desired information.
• When the SDK trace is running in the background and the application is restarted please try to reproduce the problem as quickly as possible and refrain from other activities/tests, since the SDK trace quickly becomes very large.
• Below you see two screenshots for recommended logging levels depending on different problem types.

Type 1 - problem occurs during the connection establishment phase

SDK 5.5


 

Type 2 - problem occurs during data transfer

SDK 5.5