| Summary: | ASTERISK-18106: specifying features.conf to be loaded by static realtime is reported as bound when extconfig.conf is parsed but is ignored | ||
| Reporter: | Alex Epshteyn (aepshteyn) | Labels: | |
| Date Opened: | 2011-07-10 15:16:59 | Date Closed: | 2011-08-31 15:36:45 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_realtime |
| Versions: | 1.8.4 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) features_after_modules1.diff | |
| Description: | Specifying features.conf to be loaded by static realtime is reported as bound to a static realtime table when extconfig.conf is parsed (to be more accurate this is what is reported when issuing asterisk -r command) but is ignored. Could this be a problem with module loading order? This seems to happen only after Asterisk starts - issuing "features reload" loads configuration from the bound static realtime table | ||
| Comments: | By: Matthew Nicholson (mnicholson) 2011-08-31 15:00:52.110-0500 Test with the attached patch. By: Walter Doekes (wdoekes) 2011-08-31 15:23:16.826-0500 That patch does the trick (for me at least). By: Matthew Nicholson (mnicholson) 2011-08-31 15:36:19.887-0500 This patch isn't necessary. You can work around this issue by preloading your realtime modules in modules.conf. I tested this with postgresql so a snippet of my {{modules.conf}} looks like this: {noformat} [modules] preload => res_config_pgsql.so {noformat} Adapt for the realtime related module(s) you are using. | ||