O ok thanks for the clarification. Just have to make sure to include
<br>that in my web server code to make sure that table is always there
<br>then.
<br><br>On Wed, Feb 2, 2011 at 4:11 AM, Bogdan-Andrei Iancu-2 [via OpenSIPS
<br>(Open SIP Server)] <<a href="/user/SendEmail.jtp?type=node&node=5985847&i=0" target="_top" rel="nofollow">[hidden email]</a>>
<br>wrote:
<div class='shrinkable-quote'><br>> Hi Ambert,
<br>>
<br>> Just to be sure it is clear. When you configure a DB connection for a
<br>> certain module, OpenSIPS will use that particular connection to check in
<br>> a version table for the entries corresponding to that module.
<br>>
<br>> So, for your case, opensips will check in the remote DB, in the version
<br>> table, only for the version of the "subscriber" table (used by auth_db)
<br>> module ; for the rest of the modules (pointing to local DB), the version
<br>> from the local Db will be queried.
<br>>
<br>> Regards,
<br>> Bogdan
<br>>
<br>> ambertch wrote:
<br>>> I pointed auth_db at a remote DB and table via the following:
<br>>>
<br>>> modparam("auth_db", "db_url", "mysql://user:pass@server/MY_REMOTE_DB")
<br>>> ...
<br>>> if (!www_authorize("serve.name", "users")) {
<br>>>
<br>>>
<br>>> Doing this, it complains that the table "MY_REMOTE_DB.version" doesn't
<br>>> exist.
<br>>> When I create MY_REMOTE_DB.version and copy over opensips.version, it then
<br>>> complains about users not being the correct version.
<br>>>
<br>>> I addressed this by noting a db entry in opensips.version for the default
<br>>> user storage table of subscriber = 7 and adding users = 7 that into
<br>>> MY_DB_NAME.version
<br>>>
<br>>>
<br>>> It works, but it looks to me that pointing to a remote db, some logic in
<br>>> OpenSIPS is expecting the same things as if auth_db were pointed locally.
<br>>> Is
<br>>> there any way to address this so I can remove the opensips version table
<br>>> from MY_REMOTE_DB?
<br>>>
<br>>> Thanks!
<br>>> Ambert
<br>>>
<br>>>
<br>>
<br>> --
<br>> Bogdan-Andrei Iancu
<br>> OpenSIPS Event - expo, conf, social, bootcamp
<br>> 2 - 4 February 2011, ITExpo, Miami, USA
<br>> OpenSIPS solutions and "know-how"
<br>>
<br>>
<br>> _______________________________________________
<br>> Users mailing list
<br>> [hidden email]
<br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_top" rel="nofollow" link="external">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>>
<br>>
<br>> ________________________________
<br>> If you reply to this email, your message will be added to the discussion
<br>> below:
<br>> <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Pointing-auth-db-at-remote-database-OpenSIPS-is-expecting-a-local-like-schema-tp5983295p5984529.html?by-user=t" target="_top" rel="nofollow" link="external">http://opensips-open-sip-server.1449251.n2.nabble.com/Pointing-auth-db-at-remote-database-OpenSIPS-is-expecting-a-local-like-schema-tp5983295p5984529.html</a><br>> To unsubscribe from Pointing auth_db at remote database, OpenSIPS is
<br>> expecting a local-like schema?, click here.
<br></div>
<br><hr align="left" width="300">
View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Pointing-auth-db-at-remote-database-OpenSIPS-is-expecting-a-local-like-schema-tp5983295p5985847.html">Re: Pointing auth_db at remote database, OpenSIPS is expecting a local-like schema?</a><br>
Sent from the <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html">OpenSIPS - Users mailing list archive</a> at Nabble.com.<br>