[OpenSIPS-Users] Pointing auth_db at remote database, OpenSIPS is expecting a local-like schema?

[Bogdan-Andrei Iancu]

Hi Ambert,

Just to be sure it is clear. When you configure a DB connection for a 
certain module, OpenSIPS will use that particular connection to check in 
a version table for the entries corresponding to that module.

So, for your case, opensips will check in the remote DB, in the version 
table, only for the version of the "subscriber" table (used by auth_db) 
module ; for the rest of the modules (pointing to local DB), the version 
from the local Db will be queried.

Regards,
Bogdan

ambertch wrote:
> I pointed auth_db at a remote DB and table via the following:
>
> modparam("auth_db", "db_url", "mysql://user:pass@server/MY_REMOTE_DB")
> ...
> if (!www_authorize("serve.name", "users")) {
>
>
> Doing this, it complains that the table "MY_REMOTE_DB.version" doesn't
> exist. 
> When I create MY_REMOTE_DB.version and copy over opensips.version, it then
> complains about users not being the correct version.
>
> I addressed this by noting a db entry in opensips.version for the default
> user storage table of subscriber = 7 and adding users = 7 that into
> MY_DB_NAME.version
>
>
> It works, but it looks to me that pointing to a remote db, some logic in
> OpenSIPS is expecting the same things as if auth_db were pointed locally. Is
> there any way to address this so I can remove the opensips version table
> from MY_REMOTE_DB?
>
> Thanks!
> Ambert
>
>   


-- 
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
OpenSIPS solutions and "know-how"