[Asterisk-Users] RE: Size limitations of extensions.conf
If you need to do a couple differing operations on a list of many area/country codes, then you may consider using the database to let the dial plan choose what to do, rather than go through so many extensions. I mention this to keep your extensions.conf easier to read, not because I know whether or not a long extensions.conf will break things... Can someone tell me the size (or any other) limitations for the extensions.conf? We have managed to keep our file pretty small thanks to AGI but we are about to setup a bunch of call restrictions based on area and country code. One line per area code in the US alone adds a LOT of text to this file. Is it a bad thing to have 5 or 6000 lines of text in your extensions.conf on a production system? Will it affect the performance? Sincerely, Brent A. Torrenga Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 tel:+1 219 836 8918 x325 fax:+1 219 836 1138 email:[EMAIL PROTECTED] web:www.torrenga.com ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] RE: Size limitations of extensions.conf
Asterisk support the concept of configuration engine, this means that you can write a configuration engine to get the data from anywhere. The default configuration engine is text_file_engine, that reads the configuration from text files. This engine does not have any limit in the code, so the only limit is the performance hit of starting or reloading. Actually some limits exists for the size of context names, nested includes etc, but no for number of lines. Why dont use database engine? instead of large files? Regards On 6/5/06, Brent Torrenga [EMAIL PROTECTED] wrote: If you need to do a couple differing operations on a list of many area/country codes, then you may consider using the database to let the dial plan choose what to do, rather than go through so many extensions. I mention this to keep your extensions.conf easier to read, not because I know whether or not a long extensions.conf will break things... Can someone tell me the size (or any other) limitations for the extensions.conf? We have managed to keep our file pretty small thanks to AGI but we are about to setup a bunch of call restrictions based on area and country code. One line per area code in the US alone adds a LOT of text to this file. Is it a bad thing to have 5 or 6000 lines of text in your extensions.conf on a production system? Will it affect the performance? Sincerely, Brent A. Torrenga Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 tel:+1 219 836 8918 x325 fax:+1 219 836 1138 email:[EMAIL PROTECTED] web:www.torrenga.com ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org; ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] RE: Size limitations of extensions.conf
On Mon, 2006-06-05 at 11:24 -0500, Moises Silva wrote: Asterisk support the concept of configuration engine, this means that you can write a configuration engine to get the data from anywhere. The default configuration engine is text_file_engine, that reads the configuration from text files. This engine does not have any limit in the code, so the only limit is the performance hit of starting or reloading. Actually some limits exists for the size of context names, nested includes etc, but no for number of lines. Why dont use database engine? instead of large files? Regards That doesnt solve the root problem. The configuration engine would be called at startup/reload and load everything into memory. A better approach might be what some have done in private patches to read in realtime each customers and only each customers information on a per needed basis. Lets say you have a 'cluster' of asterisk servers that all feed off the same database and in total you have several thousand hosted customers. Each customer has many lines, possibly several hundred lines that would form their extensions.conf entries. If you load that into memory you are consuming a lot of memory on each box of your 'cluster' that will mostly be unused because not all of your customers will receive calls on all the same systems. Sifting through all of this the way that is done also has a certain cost (although I dont know the actual cost of doing it in a DB). If you load each customers configuration on demand you lower the memory footprint and add the ability to have easier updates all at the same time. You can do some of this with realtime dialplans, but you cant get the faster processing available that the one patch that does all of this gets. The way the dialplan works has its own problems (internally to asterisk) with large extensions.conf. For reference the one I am talking about would be close to 200M if printed out, and a real pain to manage via any of the standard 'engines'. -- Trixter http://www.0xdecafbad.com Bret McDanel Belfast IE +44 28 9099 6461DE +49 801 777 555 3402 Utrecht NL +31 306 553058 US WA +1 360 207 0479 US NY +1 516 687 5200 FreeWorldDialup: 635378 http://www.trxtel.com we pay you to terminate calls with us! signature.asc Description: This is a digitally signed message part ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] RE: Size limitations of extensions.conf
If by database you are referring to an external database, such as MySQL, you have to address failover, redundancy and performance issues if you go in that direction. -Original Message- From: Moises Silva [mailto:[EMAIL PROTECTED] Sent: Monday, June 05, 2006 10:24 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] RE: Size limitations of extensions.conf Asterisk support the concept of configuration engine, this means that you can write a configuration engine to get the data from anywhere. The default configuration engine is text_file_engine, that reads the configuration from text files. This engine does not have any limit in the code, so the only limit is the performance hit of starting or reloading. Actually some limits exists for the size of context names, nested includes etc, but no for number of lines. Why dont use database engine? instead of large files? Regards On 6/5/06, Brent Torrenga [EMAIL PROTECTED] wrote: If you need to do a couple differing operations on a list of many area/country codes, then you may consider using the database to let the dial plan choose what to do, rather than go through so many extensions. I mention this to keep your extensions.conf easier to read, not because I know whether or not a long extensions.conf will break things... Can someone tell me the size (or any other) limitations for the extensions.conf? We have managed to keep our file pretty small thanks to AGI but we are about to setup a bunch of call restrictions based on area and country code. One line per area code in the US alone adds a LOT of text to this file. Is it a bad thing to have 5 or 6000 lines of text in your extensions.conf on a production system? Will it affect the performance? Sincerely, Brent A. Torrenga Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 tel:+1 219 836 8918 x325 fax:+1 219 836 1138 email:[EMAIL PROTECTED] web:www.torrenga.com ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org; ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
