asterisk@io-networks.com
2005-Jul-04 00:05 UTC
[Asterisk-Users] #include not working with *1.0.9
We are running * V1.0.9 on a demo box. We have set up everything in our dialplan and we have a directory where we store individual extension settings. That directory is called "extensions-phones.d" and it contains a number of .conf files. In my extensions.conf file I have put a #include "extensions-phones.d/*.conf" in my [globals] context If we reload and restart *, and then try to dial one of the defined extensions in the included directory, nothing...just "Service Unavailable". If I copy and paste a few of the extensions that are in the .conf files directly into the [default] context of the extensions.conf file, the extensions work. So it seems to me that the include statement no longer works in 1.0.9 I figure this is the case, because we were running 1.0.5 and the same config file worked fine. Anybody know what's going on? Brent ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Just a thought, but I seem to recall that in the dialplan, inlcude and other similar statements are not prefixed by the hash character (#). Try "include => ". -Bryce On Jul 4, 2005, at 00:05, asterisk@io-networks.com wrote:> We are running * V1.0.9 on a demo box. > > We have set up everything in our dialplan and we have a directory > where we store > individual extension settings. That directory is called "extensions- > phones.d" > and it contains a number of .conf files. > > In my extensions.conf file I have put a > > #include "extensions-phones.d/*.conf" in my [globals] context > > If we reload and restart *, and then try to dial one of the defined > extensions > in the included directory, nothing...just "Service Unavailable". > > > If I copy and paste a few of the extensions that are in the .conf > files directly > into the [default] context of the extensions.conf file, the > extensions work. > > So it seems to me that the include statement no longer works in 1.0.9 > > I figure this is the case, because we were running 1.0.5 and the > same config > file worked fine. > > > Anybody know what's going on? > > Brent
On Jul 4, 2005, at 12:05 AM, asterisk@io-networks.com wrote:> We are running * V1.0.9 on a demo box. > > We have set up everything in our dialplan and we have a directory > where we store > individual extension settings. That directory is called > "extensions-phones.d" > and it contains a number of .conf files. > > In my extensions.conf file I have put a > > #include "extensions-phones.d/*.conf" in my [globals] contextThat happened to me in Jan or Feb of this year; just happened to be that on one particular day, the source I CVSed out had a broken * shell expander. I waited a day or two, redownloaded and recompiled and all was well. -- Robert Goodyear Brand Up LLC http://www.brand-up.com
On Mon, Jul 04, 2005 at 02:05:17AM -0500, asterisk@io-networks.com wrote:> We are running * V1.0.9 on a demo box. > > We have set up everything in our dialplan and we have a directory where we store > individual extension settings. That directory is called "extensions-phones.d" > and it contains a number of .conf files. > > In my extensions.conf file I have put a > > #include "extensions-phones.d/*.conf" in my [globals] contextThe support for globbing in #include has been merged into HEAD, and is also part of the Rapid packages. Either grab the debs from http://tzafrir.org.il/rapid108/ or use the debs source: deb http://tzafrir.org.il/rapid108 unstable/ or extract debian/patches//80_rapid-globinclude.dpatch from the asterisk diff in the above directory and apply it to the asterisk source you build. Despite my repetetive requests, the Debian package maintainers have not yet included this patch :-( -- Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir@cohens.org.il | | best ICQ# 16849755 | | friend
On Mon, Jul 04, 2005 at 03:13:26AM -0500, asterisk@io-networks.com wrote:> Tzafrir, > Do you have patch description file which explains what the different patches do?Extrat the asterisk_*.diff.gz using zcat that_file.diff.gz | patch -p1 in an empty directory. This will create a subdirectory "debian" with all the debian files in it. debian/patches/ should have all the actual source patches. Those will be "dpatch" executables, which are actual uniform diffs that the standard patch can use, but with a small header. In that header there should be a short description (DP:) although not all dpatches include one. I tryed to remember to add one to ones I have added. Also search for the name of the patch file in the debian/changelog file. -- Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir@cohens.org.il | | best ICQ# 16849755 | | friend