[svn-commits] mvanbaak: branch 1.4 r106178 - /branches/1.4/doc/realtime.txt

[SVN commits to the Digium repositories]

Author: mvanbaak
Date: Wed Mar  5 15:12:36 2008
New Revision: 106178

URL: http://svn.digium.com/view/asterisk?view=rev&rev=106178
Log:
document var_metric so no bugreports will come in when it's actually a configuration issue.
(issue #12151)
Reported and patched by: caio1982
1.4 patch by me

Modified:
    branches/1.4/doc/realtime.txt

Modified: branches/1.4/doc/realtime.txt
URL: http://svn.digium.com/view/asterisk/branches/1.4/doc/realtime.txt?view=diff&rev=106178&r1=106177&r2=106178
==============================================================================
--- branches/1.4/doc/realtime.txt (original)
+++ branches/1.4/doc/realtime.txt Wed Mar  5 15:12:36 2008
@@ -40,6 +40,20 @@
 modules that read configurations, there's no difference between a static
 file in the file system, like extensions.conf, and a configuration loaded
 from a database.
+
+You just have to always make sure the var_metric values are properly set and
+ordered as you expect in your database server if you're using the static mode
+with ARA (either sequentially or with the same var_metric value for everybody).
+
+If you have an option that depends on another one in a given configuration
+file (i.e, 'musiconhold' depending on 'agent' from agents.conf) but their
+var_metric are not sequential you'll probably get default values being assigned for
+those options instead of the desired ones. You can still use the same
+var_metric for all entries in your DB, just make sure the entries
+are recorded in an order that does not break the option dependency.
+
+That doesn't happen when you use a static file in the file system. Although
+this might be interpreted as a bug or limitation, it is not.
 
 * Realtime SIP friends
 ----------------------