You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying do integrate SuiteCRM to Asterisk, but at this procedure step, one AsteriskLogger.php error happens. It seens to be a database issue connection. Plases, anybody can help me? Regards!
Selecting DB Name: bitnami_suitecrm
PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /opt/bitnami/apps/suitecrm/htdocs/custom/modules/Asterisk/asteriskLogger.php:152
Stack trace:
#0 {main}
thrown in /opt/bitnami/apps/suitecrm/htdocs/custom/modules/Asterisk/asteriskLogger.php on line 152
The text was updated successfully, but these errors were encountered:
Hi @edslopes77 , this plugin it's unmaintenance and you should update a lot of code. This error occurs because the deprecated mysql methods are used. You must use MySQLi API, not legacy MySQL API, but when you refactor this call functions (in many points of the code), will you have update the plugin for your Asterisk AMI version.
Dears,
I am trying do integrate SuiteCRM to Asterisk, but at this procedure step, one AsteriskLogger.php error happens. It seens to be a database issue connection. Plases, anybody can help me? Regards!
$ sudo php /opt/bitnami/apps/suitecrm/htdocs/custom/modules/Asterisk/asteriskLogger.php
******** Asterisk Logger Starting **************
Sugar root set to [/opt/bitnami/apps/suitecrm/htdocs/custom/modules/Asterisk/../../../]
Logging to: asteriskLog.txt
Callout prefix is []
Callin prefix is [+1]
asteriskMatchInternal = /^(sip/[1-9][0-9][0-9]?[0-9]?-|Local)/i
(Config processed)
Selecting DB Name: bitnami_suitecrm
PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /opt/bitnami/apps/suitecrm/htdocs/custom/modules/Asterisk/asteriskLogger.php:152
Stack trace:
#0 {main}
thrown in /opt/bitnami/apps/suitecrm/htdocs/custom/modules/Asterisk/asteriskLogger.php on line 152
The text was updated successfully, but these errors were encountered: