
12
Dialogic
®
Brooktrout
®
API (BFV) Debug Logs
BFV API= Dialogic
®
Brooktrout
®
Fax Voice API
Interface between Boston driver and application
Can be enabled via application or from Config Tool
– Application would use ‘BfvDebugFuncSet’, ‘BfvDebugModeSet’
– Enabled via some ‘switch’ in application
– Developer would need to code some way of turning this on using
those API functions
Especially vital in debugging issues with application communicating
www.dialogic.com
Slide 34
with Dialogic
®
Brooktrout
®
SR140 Fax Software or Dialogic
®
Brooktrout
®
TR1034 Fax Board, or issues faxing to/from certain
numbers or fax devices
Size of log and number of logs determined in Config Tool or via
application code
If application makes calls to debug API functions even if debugging is
not enabled, logs enabled via Config Tool will be of little value
– Only output from driver will be put in debug log
– Channel output will not be present
Dialogic
®
Brooktrout
®
Logs - ECC
www.dialogic.com
Slide 35
ECC (Enhanced Call Control)
ECC API handles call control
When enabling BFV logs, enable ECC in parallel
– Often good to know what ECC portion of code is doing even if
issue does not appear to be call control related
Always ensure “trace_file” points to a log file via absolute
www.dialogic.com Slide 36
– Leaving path relative may cause some ECC output to be
misdirected
When doing ECC logging, set all values to “Verbose”
When disabling ECC logging, set all values to “None” and
then click blue cross/red flag button to clear “trace_file” and
give the field a NULL value
Comentários a estes Manuais