History Logging - Dialogic Brooktrout Digital Board Installation And Configuration Manual

History Logging

March 2013
Configuring Boston driver:
Phys buf size 32768
App buffer size 10240
Machine ID 1
History size 1024000
Num phys hist bufs 0
Num apl hist bufs 0
The maximum number of PCI hardware modules can be left at its
default. However, if fewer modules are in use, to conserve memory,
this value can be set to a smaller number. Each hardware module
uses approximately 60K.
When the Dialogic® Brooktrout® driver is installed, history logging
is disabled by default. When you manually install the driver using
dinstall, the default is set to disable history logging (you can choose
to override this option). History logging is a powerful debugging tool,
especially when working with Dialogic Technical Services and
Support. However, it does consume a significant amount of CPU
time when running very high call loads. Therefore, leave history
logging off for systems that have high call loads and are CPU-bound.
For low-load systems or when debugging, enable history logging.
Leave the number of physical and application channel histories at 0
unless you are directed to change this by Dialogic Technical Services
and Support. If you change the physical or application buffer size, do
not change the value to one smaller than the default.
If you specify a number for the physical channel histories, dinstall
asks if you want to restrict the physical channels to administrative
channel 1.
Restrict physical channels to admin channel 1 (default 1):
Choose the default (enable).
Configuring the Driver Manually
40