kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-10-12 15:45:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

document var_metric so no bugreports will come in when it's actually a configuration issue.

Browse Source 
(issue #12151)
Reported and patched by: caio1982
1.4 patch by me


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@106178 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Michiel van Baak
2008-03-05 21:12:36 +00:00
parent 461e3fea79
commit ba6b7abe61
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/realtime.txt
View File

@@ -41,6 +41,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
----------------------
The SIP realtime objects are users and peers that are loaded in memory