Right, Here is its (res_mysql.conf) content: [general] dbhost = 127.0.0.1 dbname = asterisk dbuser = voipadmin dbpass = secret dbport = 3306 dbsock = /tmp/mysql.sock dbcharset = latin1 requirements=warn ; or createclose or createchar
The file didn't exists on the systemm so i had to create it. I kept it identical to res_config_mysql.conf Hans On Mon, 2011-05-23 at 14:03 +0100, Andrew Thomas wrote: > It's the contents of res_mysql.conf that's really needed - as > extconfig.conf has to match what's in it. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Hans > Witvliet > Sent: 23 May 2011 13:42 > To: [email protected] > Subject: [asterisk-users] [Fwd: FW: extconfig.conf] > > Hi Andrew, > > OK, (the simple fact that those machines are not connected to internet > makes that i have to go to those machines and copy them on a usb-stick, > so it causes some delay each time...) > > > > -------- Forwarded Message -------- > Sorry - I meant extconfig.conf - not cdr_mysql.conf (my mistake). > > I use (and done for a long time) mySQL for realtime storage - and it's > never let me down (touch wood). > -------- Forwarded Message -------- > > > ; > > ; Static and realtime external configuration ; engine configuration ; > ; Please read doc/extconfig.txt for basic table ; formatting > information. > > ; > > [settings] > > ; > > ; Static configuration files: > > ; > > ; file.conf => driver,database[,table[,priority]] > > ; > > ; maps a particular configuration file to the given ; database driver, > database and table (or uses the ; name of the file as the table if not > specified) ; ;uncomment to load queues.conf via the odbc engine. > > ; > > ;queues.conf => odbc,asterisk,ast_config ;extensions.conf => > sqlite,asterisk,ast_config ; ; The following files CANNOT be loaded from > Realtime storage: > > ; asterisk.conf > > ; extconfig.conf (this file) > > ; logger.conf > > ; > > ; Additionally, the following files cannot be loaded from ; Realtime > storage unless the storage driver is loaded ; early using 'preload' > statements in modules.conf: > > ; manager.conf > > ; cdr.conf > > ; rtp.conf > > ; > > ; > > ; Realtime configuration engine > > ; > > ; maps a particular family of realtime ; configuration to a given > > database driver, ; database and table (or uses the name of ; the > > family if the table is not specified ; ;example => > > odbc,asterisk,alttable,1 ;example => mysql,asterisk,alttable,2 > > ;example2 => ldap,"dc=oxymium,dc=net",example2 ; ; Additionally, > priorities are now supported for use as failover methods ; for > retrieving realtime data. If one connection fails to retrieve any ; > information, the next sequential priority will be tried next. This ; > especially works well with ODBC connections, since res_odbc now caches ; > when connection failures occur and prevents immediately retrying those ; > connections until after a specified timeout. Note: priorities must ; > start at 1 and be sequential (i.e. if you have only priorities 1, 2, ; > and 4, then 4 will be ignored, because there is no 3). > > ; > > ; "odbc" is shown in the examples below, but is not the only valid > realtime ; engine. There is: > > ; odbc ... res_config_odbc > > ; sqlite ... res_config_sqlite > > ; pgsql ... res_config_pgsql > > ; curl ... res_config_curl > > ; ldap ... res_config_ldap > > ; > > ;iaxusers => odbc,asterisk > > ;iaxpeers => odbc,asterisk > > ;sipusers => odbc,asterisk > > ;sipusers => mysql,asterisk,sip_devices ;sippeers => > > mysql,asterisk,sip_devices ;sipusers => mysql,general,sip_devices > > ;sippeers => mysql,general,sip_devices sipusers => > > mysql,default,sip_devices sippeers => mysql,default,sip_devices > > ;sippeers => odbc,asterisk ;sipregs => odbc,asterisk ;voicemail => > > odbc,asterisk ;extensions => odbc,asterisk ;meetme => mysql,general > > ;queues => odbc,asterisk ;queue_members => odbc,asterisk ;musiconhold > > => mysql,general ;queue_log => mysql,general ; ; ; While most dynamic > > realtime engines are automatically used when defined in ; this file, > 'extensions', distinctively, is not. To activate dynamic realtime ; > extensions, you must turn them on in each respective context within ; > extensions.conf with a switch statement. The syntax is: > > ; switch => Realtime/[[db_context@]tablename]/<opts> > > ; The only option available currently is the 'p' option, which > disallows ; extension pattern queries to the database. If you have no > patterns defined ; in a particular context, this will save quite a bit > of CPU time. However, ; note that using dynamic realtime extensions is > not recommended anymore as a ; best practice; instead, you should > consider writing a static dialplan with ; proper data abstraction via a > tool like func_odbc. > > > > so i have: > sipusers => engine, context, table_name > sippeers => engine, context, table_name > (tried both 'default' as 'general' as context value. > > I previously tried: > sipusers => engine, db_name, table_name > sippeers => engine, db_name, table_name > > but with same results.... > > Hans > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > If you have received this communication in error we would appreciate > you advising us either by telephone or return of e-mail. The contents > of this message, and any attachments, are the property of DataVox, > and are intended for the confidential use of the named recipient only. > If you are not the intended recipient, employee or agent responsible > for delivery of this message to the intended recipient, take note that > any dissemination, distribution or copying of this communication and > its attachments is strictly prohibited, and may be subject to civil or > criminal action for which you may be liable. > Every effort has been made to ensure that this e-mail or any attachments > are free from viruses. While the company has taken every reasonable > precaution to minimise this risk, neither company, nor the sender can > accept liability for any damage which you sustain as a result of viruses. > It is recommended that you should carry out your own virus checks > before opening any attachments. > > Registered in England. No. 27459085. > > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
