Technical data

147
[9]
If you do not know which applications or drivers access interfaces of Dialogic
®
Diva
®
drivers or you cannot stop
these applications, proceed as follows:
• Execute sh /usr/lib/opendiva/divas/cfg/cfg_util.sh 2. This removes the symbolic links
S03DIVA4LINUX from the /etc/rc.d/rc...d or /sbin.init.d/rc...d directories.
• Restart your system.
The Diva drivers are not loaded on system startup and can be uninstalled. You can identify the applications or
drivers that accessed Diva drivers by error messages on the console and in the var/log/messages file.
[10]
If you do not know the name of the installed RPM package, execute rpm -q -a | grep divas4linux to get the
package name from the database maintained by RPM.
[11]
Based on the information from the management interface it is possible to clear calls that meet specific criteria,
e.g., calling party number, fax ID, and fax polling address.
[12]
The "-w" parameter can only be used with variables that have the "W" attribute.
[13]
The "-e" parameter can only be used with variables of the "MI_EXECUTE" type.
[14]
"-m", "-a", and "-g" parameters can be used in combination.
[15]
If you use the mantool from scripts, i.e., not interactively, add the "-b" option to turn the interactive mode off.
[16]
Whenever Dialogic
®
Diva
®
Media Board health monitor is running, the XLOG interface is busy and cannot be
used by other utilities.
[17]
To find out the state of a logical adapter <x>, execute: /usr/lib/opendiva/divas/divactrl load -c <x> -
CardState.
[18]
Execute this command after the Dialogic
®
Diva
®
Media Board is in a trapped state.