I would like to see an XML based configuration format for the static configuration files. This can be done through the ARA realtime subsystem - without support for the dynamic objects, only static configurations. This would just be a wrapper around the current configuration files, but could optionally add some error-checking with XML schemas.
Example:
<device type=”peer” name=”ollesphone”><secret>terces</secret><host type=”dynamic”/><codecs><disallow>all</disallow><allow>gsm</allow><allow>ulaw</allow></codecs> </device>
Now, app_meetme read “meetme.conf” file for each MeetMe() execution, this is an issue when using Static Realtime for meetme as I reported here:http://bugs.digium.com/view.php?id=11786Note that this report has been quickly closed as “no change required” because:”You’re right, the reason that this happens is because meetme.conf gets re-read at every execution of the application. However, I do not consider this a bug, but instead a request for an enhancement, which we do not currently process on bugs.digium.com”.So then I post it here ;)The problem using meetme in Static Realtime is that for each MeetMe() execution a big SQL query is done:—————-SELECT cat_metric, category, var_name, var_val FROM meetme WHEREfilename=’meetme.conf’ AND commented=0 ORDER BY cat_metric DESC, var_metricASC, category, var_name—————-Note that this query gets ALL the rows containing a conference, that could be a resource pain if there exist multiples conferences.So I propose to improve “app_meetme” in order to avoid reading “meetme.conf” file (or DB table in static realtime) for each MeetMe() execution.It could be great too a new CLI function:CLI> meetme reload
