Re: [asterisk-users] File structure question
On 05/09/06, Jay Moore [EMAIL PROTECTED] wrote: Perhaps if answering the simple things politely is too difficult for you, you'd be better off not answering at all. Someday, I hope, you'll find that 'simple' is a relative term. Perhaps if receiving accurate answers without biting off the hand of the person helping you is too difficult for you, you'd be better off paying for a support contract with some reputable organisation? That way you can do no work whatsoever yourself and enjoy never-ending handholding at $150 per incident. That may suit you better. Around peer-support lists, you tend to find an aversion to telling people things they could easily look up or find out for themselves in a few keystrokes. You'll also notice that I took the trouble not only to answer your question, but to come back and re-phrase my answer when I saw you hadn't understood my explanation. You got all that for free. Enjoy! Peter -- Peter Bowyer Email: [EMAIL PROTECTED] ___ --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] File structure question
Thanks Peter, I've also learned with your tips ;)On 9/5/06, Peter Bowyer [EMAIL PROTECTED] wrote: On 05/09/06, Jay Moore [EMAIL PROTECTED] wrote: Perhaps if answering the simple things politely is too difficult for you, you'd be better off not answering at all.Someday, I hope, you'll find that 'simple' is a relative term.Perhaps if receiving accurate answers without biting off the hand of the person helping you is too difficult for you, you'd be better offpaying for a support contract with some reputable organisation? Thatway you can do no work whatsoever yourself and enjoy never-endinghandholding at $150 per incident. That may suit you better. Around peer-support lists, you tend to find an aversion to tellingpeople things they could easily look up or find out for themselves ina few keystrokes.You'll also notice that I took the trouble not only to answer your question, but to come back and re-phrase my answer when I saw youhadn't understood my explanation. You got all that for free. Enjoy!Peter--Peter BowyerEmail: [EMAIL PROTECTED]___--Bandwidth and Colocation provided by Easynews.com --asterisk-users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users-- Com os melhores cumprimentos, Marco Mouta ___ --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] File structure question
Tzafrir Cohen wrote: On Thu, Aug 31, 2006 at 03:52:00PM -0500, Jay Moore wrote: I have a question on how I can better organize my .conf files. I have 3 different groups of people who use my VoIP service. Let's call them 'Office', 'Factory' and 'Public'. In my Asterisk directory, I have created three folders: 'office', 'factory' and 'public', inside each of which has a sip.conf and an extensions.conf file with appropriate account and extension information. Say, for example, I need to limit some users of the 'Public' group so they cannot make calls outside the building. Obviously I would create two separate contexts. One for users who can make calls outside the build, and one for users who cannot. I would then assign the appropriate context to each user. Right now, I have each appropriate context defined in the main extensions.conf. What I'd like to do is reduce the clutter in extensions.conf and move each context into the extensions.conf in the appropriate subfolder. How do I tell the main extensions.conf file to include the other extensions.conf files without putting an #include file in a context of its own? I hope what I've explained makes sense. If not, please ask questions and I'll try to answer. #include is a verbatim text include. if extensions.conf has: [main] exten = aaa,1,Line1 #include otherfile.conf exten = aaa,2,Line2 and othererfile.conf has: exten = aaa,2,OtherLine1 [other] exten = aaa,1,OtherLine2 You'll eventually get: main: aaa: 1. Line1 2. OtherLine1 other: aaa: 1. OtherLine2 2. Line2 Right, I guess I was wondering if it's possible to include a file without it being in a context. The goal I wanted to achieve was to have as few contexts in the main extensions.conf file as possible. Jay ___ --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] File structure question
On 04/09/06, Jay Moore [EMAIL PROTECTED] wrote: Right, I guess I was wondering if it's possible to include a file without it being in a context. The goal I wanted to achieve was to have as few contexts in the main extensions.conf file as possible. Did you try it? It would take... perhaps 30 seconds? A minute if you're a slow typist... Yes, you can do this. #include is a literal text include, as the last poster said. -- Peter Bowyer Email: [EMAIL PROTECTED] ___ --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] File structure question
So the #include could be made just after the [general] section o extensions.conf? outside of any specific context, i think this was the question.On 9/4/06, Peter Bowyer [EMAIL PROTECTED] wrote: On 04/09/06, Jay Moore [EMAIL PROTECTED] wrote: Right, I guess I was wondering if it's possible to include a file without it being in a context.The goal I wanted to achieve was to have as few contexts in the main extensions.conf file as possible.Did you try it? It would take... perhaps 30 seconds? A minute ifyou're a slow typist...Yes, you can do this. #include is a literal text include, as the last poster said.--Peter BowyerEmail: [EMAIL PROTECTED]___--Bandwidth and Colocation provided by Easynews.com --asterisk-users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Com os melhores cumprimentos,Marco Mouta ___ --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] File structure question
Marco: Ah I see. There's a [general] context. I'm pretty new to this Asterisk stuff and I didn't realize there was a general context that you could do things like global includes. Thanks, I'll give it a shot when I'm back in the office on Tuesday. Peter: No need to be an ass about it, pal. Not all of us are as adept at this as you are. Jay Marco Mouta wrote: So the #include could be made just after the [general] section o extensions.conf? outside of any specific context, i think this was the question. On 9/4/06, Peter Bowyer [EMAIL PROTECTED] wrote: On 04/09/06, Jay Moore [EMAIL PROTECTED] wrote: Right, I guess I was wondering if it's possible to include a file without it being in a context. The goal I wanted to achieve was to have as few contexts in the main extensions.conf file as possible. Did you try it? It would take... perhaps 30 seconds? A minute if you're a slow typist... Yes, you can do this. #include is a literal text include, as the last poster said. -- Peter Bowyer Email: [EMAIL PROTECTED] ___ --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 ___ --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] File structure question
On 04/09/06, Jay Moore [EMAIL PROTECTED] wrote: Marco: Ah I see. There's a [general] context. I'm pretty new to this Asterisk stuff and I didn't realize there was a general context that you could do things like global includes. Thanks, I'll give it a shot when I'm back in the office on Tuesday. Peter: No need to be an ass about it, pal. Not all of us are as adept at this as you are. You've still not got it. #include is a general text include - can be used anywhere. Well, perhaps it has to be at the start of a line. Contexts, not even the [general] section which isn't actually a context, has any relevance. It will insert the contents of the included file as though it was in the main file, wherever you put it. You could put the whole of the sip.conf file in an #include'd file. The whole of one context. One and a half contexts. 2 lines out of the [general] section. And so on. All of which, to repeat, could be experienced with a small investment of your time. It really does pay to experiment with the simple things, you find your learning curve is so much flatter than if you ask questions in a vacuum. Peter -- Peter Bowyer Email: [EMAIL PROTECTED] ___ --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] File structure question
Peter Bowyer wrote: On 04/09/06, Jay Moore [EMAIL PROTECTED] wrote: Marco: Ah I see. There's a [general] context. I'm pretty new to this Asterisk stuff and I didn't realize there was a general context that you could do things like global includes. Thanks, I'll give it a shot when I'm back in the office on Tuesday. Peter: No need to be an ass about it, pal. Not all of us are as adept at this as you are. You've still not got it. #include is a general text include - can be used anywhere. Well, perhaps it has to be at the start of a line. Contexts, not even the [general] section which isn't actually a context, has any relevance. It will insert the contents of the included file as though it was in the main file, wherever you put it. You could put the whole of the sip.conf file in an #include'd file. The whole of one context. One and a half contexts. 2 lines out of the [general] section. And so on. All of which, to repeat, could be experienced with a small investment of your time. It really does pay to experiment with the simple things, you find your learning curve is so much flatter than if you ask questions in a vacuum. Peter Perhaps if answering the simple things politely is too difficult for you, you'd be better off not answering at all. Someday, I hope, you'll find that 'simple' is a relative term. Jay ___ --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] File structure question
On Thu, Aug 31, 2006 at 03:52:00PM -0500, Jay Moore wrote: I have a question on how I can better organize my .conf files. I have 3 different groups of people who use my VoIP service. Let's call them 'Office', 'Factory' and 'Public'. In my Asterisk directory, I have created three folders: 'office', 'factory' and 'public', inside each of which has a sip.conf and an extensions.conf file with appropriate account and extension information. Say, for example, I need to limit some users of the 'Public' group so they cannot make calls outside the building. Obviously I would create two separate contexts. One for users who can make calls outside the build, and one for users who cannot. I would then assign the appropriate context to each user. Right now, I have each appropriate context defined in the main extensions.conf. What I'd like to do is reduce the clutter in extensions.conf and move each context into the extensions.conf in the appropriate subfolder. How do I tell the main extensions.conf file to include the other extensions.conf files without putting an #include file in a context of its own? I hope what I've explained makes sense. If not, please ask questions and I'll try to answer. #include is a verbatim text include. if extensions.conf has: [main] exten = aaa,1,Line1 #include otherfile.conf exten = aaa,2,Line2 and othererfile.conf has: exten = aaa,2,OtherLine1 [other] exten = aaa,1,OtherLine2 You'll eventually get: main: aaa: 1. Line1 2. OtherLine1 other: aaa: 1. OtherLine2 2. Line2 -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 jabber:[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.xorcom.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
[asterisk-users] File structure question
I have a question on how I can better organize my .conf files. I have 3 different groups of people who use my VoIP service. Let's call them 'Office', 'Factory' and 'Public'. In my Asterisk directory, I have created three folders: 'office', 'factory' and 'public', inside each of which has a sip.conf and an extensions.conf file with appropriate account and extension information. Say, for example, I need to limit some users of the 'Public' group so they cannot make calls outside the building. Obviously I would create two separate contexts. One for users who can make calls outside the build, and one for users who cannot. I would then assign the appropriate context to each user. Right now, I have each appropriate context defined in the main extensions.conf. What I'd like to do is reduce the clutter in extensions.conf and move each context into the extensions.conf in the appropriate subfolder. How do I tell the main extensions.conf file to include the other extensions.conf files without putting an #include file in a context of its own? I hope what I've explained makes sense. If not, please ask questions and I'll try to answer. Thanks much, Jay ___ --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
