On Tue, Dec 22, 2015 at 5:42 PM, Maxim Solodovnik <solomax...@gmail.com> wrote:
> > ---------- Forwarded message ---------- > From: Maxim Solodovnik <solomax...@gmail.com> > Date: Tue, Dec 22, 2015 at 6:12 PM > Subject: Re: asterisk odbc > To: Awotipe Oluwaseun <awotipeoluwas...@yahoo.com> > > > Actually it depends on how you set up your Asterisk > during our tests (couple of years ago) we were able to call to to the room > using both soft phone and mobile phone > > On Tue, Dec 22, 2015 at 1:15 AM, Awotipe Oluwaseun < > awotipeoluwas...@yahoo.com> wrote: > >> Hi, >> To call into a meeting in OM, do I need to call via VoIP application or >> just dia extensions given in diaplan on just regular phone. >> Sorry for my dump question. >> >> oluwaseun >> On Dec 13, 2015 1:48 AM, Maxim Solodovnik <solomax...@gmail.com> wrote: >> >> OM is not using "insecure" column, it uses encrypted password only >> you can manually add this column if it is necessary for you >> >> On Sat, Dec 12, 2015 at 3:12 AM, awotipe oluwaseun < >> awotipeoluwas...@yahoo.com> wrote: >> >> jeff, thanks alot for your response, i finally get the res_config >> connected to the database, but when i dial one of the room extentions i get >> the below error in asterisk cli, >> any ideal of what might be causing this. >> >> [Dec 11 15:00:12] WARNING[41160][C-00000001]: res_config_mysql.c:499 >> realtime_multi_mysql: MySQL RealTime: Failed to query database: Unknown >> column 'insecure' in 'where clause' >> [Dec 11 15:00:12] WARNING[41160][C-00000001]: res_config_mysql.c:499 >> realtime_multi_mysql: MySQL RealTime: Failed to query database: Unknown >> column 'insecure' in 'where clause' >> >> >> >> On Wednesday, December 9, 2015 10:09 PM, Maxim Solodovnik < >> solomax...@gmail.com> wrote: >> >> >> couple of days ago I have updated the instructions with 13.6.0 sources >> and menuselect >> >> sudo contrib/scripts/install_prereq install >> sudo make menuconfig >> >> >> >> Make sure you have selected Add-ons -> res_config_mysql, Press F12 to >> save >> >> >> On Thu, Dec 10, 2015 at 2:01 AM, Jeff Clay <jeff.c...@cyient.com> wrote: >> >> No, sqlite won’t work. You should see “res_config_mysql” as an option >> under “Add-ons” when you run “make menuselect” when compiling asterisk. The >> option is right underneath “format_mp3”. If the mysql option is greyed >> out, you will see the packages that it requires listed at the bottom at >> “Depends on:” You might try searching google for a tuturial on installing >> 13.6.0 on whichever distro you’re using. >> >> >> >> *From:* awotipe oluwaseun [mailto:awotipeoluwas...@yahoo.com] >> *Sent:* Wednesday, December 9, 2015 12:11 PM >> >> *To:* user@openmeetings.apache.org >> *Subject:* Re: asterisk odbc >> >> jeff, >> i notced that res_config_mysql was not loaded, when i did modules show, >> so i decided to upgrade to asterisk 13.6.0, but to my suprise there no >> res_config_mysql module in menuconfigselect, instead res_config_sqlite3 >> that is there. >> please advice if can use that, but i know my database is mysql. >> thanks >> >> >> On Wednesday, December 9, 2015 11:17 AM, Jeff Clay <jeff.c...@cyient.com> >> wrote: >> >> >> Accidentally replied directly. >> >> >> *From:* Jeff Clay >> *Sent:* Wednesday, December 9, 2015 11:11 AM >> *To:* 'awotipe oluwaseun' <awotipeoluwas...@yahoo.com> >> *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:awotipeoluwas...@yahoo.com >> <awotipeoluwas...@yahoo.com>] >> *Sent:* Wednesday, December 9, 2015 10:58 AM >> *To:* Jeff Clay <jeff.c...@cyient.com>; user@openmeetings.apache.org >> *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 <jeff.c...@cyient.com> >> 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:awotipeoluwas...@yahoo.com >> <awotipeoluwas...@yahoo.com>] >> *Sent:* Wednesday, December 9, 2015 10:04 AM >> *To:* user@openmeetings.apache.org >> *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 < >> solomax...@gmail.com> 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 <solomax...@gmail.com> >> wrote: >> >> Thanks! >> Will try these settings and will update the steps! >> >> On Fri, Nov 13, 2015 at 4:45 AM, Jeff Clay <jeff.c...@cyient.com> 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:solomax...@gmail.com] >> *Sent:* Tuesday, September 29, 2015 3:27 PM >> *To:* Openmeetings user-list <user@openmeetings.apache.org> >> *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 <jeff.c...@cyient.com> 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 >> >> >> >> >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> > > > -- > WBR > Maxim aka solomax > > > > -- > WBR > Maxim aka solomax > -- Thanks & Regards, Gangadhar *Gangadhar Kadam* Team Leader New Indictrans Technologies Pvt. Ltd. - Pune Office: +91-20-65700800 | Mobile: +91-9960066444 Linkedin:-https://www.linkedin.com/in/gangadharkadam www.indictranstech.com | Lat: 18.501994 Lon: 73.79766 This e-mail has arrived in your e-mail Inbox from New Indictrans Technologies Private Limited, Pune. Please do visit http://www.indictranstech.com/ to know more about New Indictrans Private Limited. This email is not spam. We follow 'US Unsolicited Electronic Mail Act of 2000', which states that an e-mail cannot be considered SPAM if it contains contact/removal information, which this e-mail does. This e-mail may contain proprietary and confidential information and is sent for the intended recipient(s) only. If, by an addressing or transmission error, this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or it's attachment(s) other than by its intended recipient(s) is strictly prohibited. Any opinions expressed in this email are those of the individual and not necessarily of the organisation. Before opening attachment(s), please scan the attachment for viruses.". In case & if you do not wish to receive e-mail (the way you have received it today for what so ever cause or reasons) in near future? Reply back to this email saying "Remove e-mail ID". Within two working days your ID will be removed.
