Accidentally replied directly.
From: Jeff Clay Sent: Wednesday, December 9, 2015 11:11 AM To: 'awotipe oluwaseun' <[email protected]> Subject: RE: asterisk odbc Yeah, the instructions on the site are to use ODBC which isn’t necessary since asterisk has native access to mysql. Make sure that the file you specified for dbsock actually exists. I’m using centos and the mysql socket is /var/lib/mysql/mysql.sock. Also, change the highlighted portions below. [general] ;dbhost=127.0.0.1 dbname=open306 dbuser=root dbpass=M##tOp#n ;dbport=3306 dbsock= /var/lib/mysql/mysqld.sock dbcharset=utf8 requirments=warn This change is necessary because you can’t have two of the same extensions. [rooms] exten => _42XX!,1,GotoIf($[${DB_EXISTS(openmeetings/rooms/${EXTEN})}]?ok:notavail) exten => _42XX!,n(ok),SET(PIN=${DB(openmeetings/rooms/${EXTEN})}) exten => _42XX!,n,Set(CONFBRIDGE(user,template)=sip_user) exten => _42XX!,n,Set(CONFBRIDGE(user,pin)=${PIN}) exten => _42XX!,n,Confbridge(${EXTEN},default_bridge,) exten => _42XX!,n,Hangup exten => _42XX!,n(notavail),Answer() exten => _42XX!,n,Playback(invalid) exten => _42XX!,n,Hangup Your other settings look the same as mine. Be sure that you’re also configuring red5phone to fully integrate asterisk into the OM rooms. From: awotipe oluwaseun [mailto:[email protected]] Sent: Wednesday, December 9, 2015 10:58 AM To: Jeff Clay <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: asterisk odbc thanks jeff, below is my configurations, the rsult that i get is different from what the instruction said. res_config_mysql.conf [general] dbhost=127.0.0.1 dbname=open306 dbuser=root dbpass=M##tOp#n dbport=3306 dbsock= /var/lib/mysql/mysqld.sock dbcharset=utf8 requirments=warn extensions.conf [rooms] exten => _42XX!,1,GotoIf($[${DB_EXISTS(openmeetings/rooms/${EXTEN})}]?ok:notavail) exten => _42XX!,n(ok),SET(PIN=${DB(openmeetings/rooms/${EXTEN})}) exten => _42XX!,n,Set(CONFBRIDGE(user,template)=sip_user) exten => _42XX!,n,Set(CONFBRIDGE(user,pin)=${PIN}) exten => _42XX!,n(ok),Confbridge(${EXTEN},default_bridge,) exten => _42XX!,n,Hangup exten => _42XX!,n(notavail),Answer() exten => _42XX!,n,Playback(invalid) exten => _42XX!,n,Hangup [rooms-originate] exten => _42XX!,1,Confbridge(${EXTEN},default_bridge,sip_user) exten => _42XX!,n,Hangup [rooms-out] [rooms-red5sip] exten => _42XX!,1,GotoIf($[${DB_EXISTS(openmeetings/rooms/${EXTEN})}]?ok:notavail) exten => _42XX!,n(ok),Confbridge(${EXTEN},default_bridge,red5sip_user) exten => _42XX!,n(notavail),Hangup /opt/red5/webapps/openmeetings/WEB-INF/classes/openmeetings-applicationContext.xml <!-- Should be uncommented and updated with real values for Asterisk --> <constructor-arg><value>127.0.0.1</value></constructor-arg> <constructor-arg><value>5038</value></constructor-arg> <constructor-arg><value>openmeetings</value></constructor-arg> <constructor-arg><value>12345</value></constructor-arg> Connected to Asterisk 11.19.0 currently running on openmeetings2 (pid = 54300) openmeetings2*CLI> database show /dundi/secret : +2BIS+zVbgEis7lSqNJtAw==;CjuOOOsUgx7+tbp6NblJZw== /dundi/secretexpiry : 1449681730 2 results found. thanks On Wednesday, December 9, 2015 10:13 AM, Jeff Clay <[email protected]<mailto:[email protected]>> wrote: The database in res_config_mysql.conf is supposed to be the mysql database of OM. The database mentioned in the extensions.conf file is actually referring the local astdb which is an internal database used by asterisk. Check out https://wiki.asterisk.org/wiki/display/AST/Asterisk+Internal+Database for more information on the astdb. Make sure that “dbname” in res_config_mysql.conf is the same name as you used for OM installation. From: awotipe oluwaseun [mailto:[email protected]] Sent: Wednesday, December 9, 2015 10:04 AM To: [email protected]<mailto:[email protected]> Subject: Re: asterisk odbc hi maxim, thanks for the fix but there is still one questions that need to be answered, the database mentioned in the line below in next line is the same metioned in /etc/asterisk/res_config_mysql.conf _400X!,1,GotoIf($[${DB_EXISTS(openmeetings/rooms/${EXTEN})}]?ok:notavail) the rreson is that most new OM release does have Database name after version which does not work for me even after i changed the name in res_config_mysql.conf. please pardone me if i am asking silly question. thanks On Tuesday, December 8, 2015 2:55 AM, Maxim Solodovnik <[email protected]<mailto:[email protected]>> wrote: docs are fixed: http://openmeetings.apache.org/red5sip-integration_3.0.html hope I did everything right :) On Fri, Nov 13, 2015 at 8:53 AM, Maxim Solodovnik <[email protected]<mailto:[email protected]>> wrote: Thanks! Will try these settings and will update the steps! On Fri, Nov 13, 2015 at 4:45 AM, Jeff Clay <[email protected]<mailto:[email protected]>> wrote: The settings below are confirmed working. No need to mess with ODBC or anything. This tells asterisk to find its sip users in the db. /etc/asterisk/extconfig.conf [settings] sippeers => mysql,general,sipusers /etc/asterisk/res_config_mysql.conf [general] dbname = om dbuser = root dbpass = MYPASS dbsock = /var/lib/mysql/mysql.sock dbcharset = utf8 requirements=warn From: Maxim Solodovnik [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, September 29, 2015 3:27 PM To: Openmeetings user-list <[email protected]<mailto:[email protected]>> Subject: Re: asterisk odbc it is necessary to make asterisk to use OM DB, please propose doc change in case you know how to simplify it :) On Tue, Sep 29, 2015 at 11:56 PM, Jeff Clay <[email protected]<mailto:[email protected]>> wrote: Is the purpose of setting up the ODBC settings only to accomplish realtime sip in the mysql database? Asterisk has several realtime drivers already built-in (including mysql) which don’t require near as much configuration. ________________________________ DISCLAIMER: This email may contain confidential information and is intended only for the use of the specific individual(s) to which it is addressed. If you are not the intended recipient of this email, you are hereby notified that any unauthorized use, dissemination or copying of this email or the information contained in it or attached to it is strictly prohibited. If you received this message in error, please immediately notify the sender at Cyient and delete the original message. -- WBR Maxim aka solomax -- WBR Maxim aka solomax -- WBR Maxim aka solomax
