Browse
 
Tools
Rss Categories

Deprecated - Known Issues with Asterisk

Reference Number: AA-01131 Views: 3275 0 Rating/ Voters

Deprecated Content

This page refers to outdated, obsolete, or deprecated products or software. This is provided for historical reference for users of older releases.

This page lists current issues and workarounds relating to Asterisk and the LumenVox Speech Engine integration. Full release notesare available for each version of the LumenVox software.



Virtual Machines

LumenVox versions 11.0 and later should work correctly in virtual environments, assuming the VM has been set up correctly. For LumenVox version 10, the License Server version did not support virtualized environments, though the other products would workin a virtual machine.

Missing Dependency: libjs.so.1

If you are getting an error about Missing Dependency: libjs.so.1 then be sure you haveread the "Libjs Problems on Red Hat ES or CentOS" section of our InstallationInstructions.

Cannot restore segment prot after reloc

If you are getting an error that includes a message about Cannot restore segment prot after relocthis is likely caused by SE Linux. The easiest solution is to disable SE Linux; the better solution is to configurean exception in SE Linux to allow LumenVox to load its libraries. However, as SE Linux is a third-party application,documenting it is beyond the scope of this guide.

LumenVox and Asterisk Startup

There was a previous known issue that sometimes caused the Connector Bridge (res_speech_lumenvox.so) to segfault during load. We believe this is fixed in LumenVox 10.0 and later.

The error will display as:

asterisk: symbol lookup error: /usr/lib/asterisk/modules/res_speech_lumenvox.so: undefined symbol: ast_speech_register

-or from the pstack:
Core was generated by `asterisk -cvvvvvv -d -g'. Program terminated with signal 11, Segmentation fault.

*It is possible that the issue may manifest with errors different than the examples above. If the Connector Bridge segfaults, proceed with the fix defined below.

To work around this issue, simply set theMODULE_STARTUP_MODEparameter of youretc/lumenvox/client_property.conffile to 1. Its default is 0.

You will then need to restart Asterisk.