asterisk users - Sep 2010 - Upgrade from 1.4 to 1.6 : problems with realtimemysql

This is a problem with extconfig.conf - not your res_ or cdr_ ones.

In your case - extconfig.conf probably contained something like
'sippeers => mysql,MyDBase,sippeers'.  The 'problem' is that
the middle
parameter is no longer for the database name - it is for the context in
res_mysql.conf.  So, the above now becomes 'sippeers =>
mysql,general,sippeers'.  Give that a go...

Cheers
Andy


-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jonas
Kellens
Sent: 08 September 2010 15:48
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Upgrade from 1.4 to 1.6 : problems with
realtimemysql


Hello,

in asterisk 1.4.30 all realtime configurations go well.

In asterisk 1.6.2.11 the following appears on CLI :

[Sep  8 16:43:43] WARNING[1843]: res_config_mysql.c:325 realtime_mysql:
MySQL RealTime: Invalid database specified: MyDBase (check
res_mysql.conf)
[Sep  8 16:43:43] WARNING[1843]: res_config_mysql.c:325 realtime_mysql:
MySQL RealTime: Invalid database specified: MyDBase (check
res_mysql.conf)

res_mysql.conf :

[general]
dbhost = 127.0.0.1
dbname = MyDBase
dbuser = asterisk
dbpass = mysecret
dbport = 3306
dbsock = /tmp/mysql.sock
requirements=warn ; or createclose or createchar


What do I need to change to be conform asterisk 1.6 ?!

Reloading, restarting asterisk and restarting my CentOS-server all
doesn't help.


Jonas.


 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.