RE: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
Hi all, Where can we find a roadmap of asterisk 1.4 release ? Harry --- Olle E Johansson [EMAIL PROTECTED] a écrit : Welcome to the Asterisk users community! Asterisk is the leading Open Source Telephony platform, with support both for classical telephony and IP telephony. Asterisk.org is a fast moving project. New code is added every day. Our community is also growing fast and we're having a lot of interaction, on the IRC and on the mailing lists. It's great to have you participating in this Open Source project - building an Open Source PBX. Here are a few things to know and remember while working with the project. I have just returned from one week in Tokyo, testing the Asterisk SIP channel with a large number of other SIP stacks. Since last SIPit, the SIP stack has improved quite a lot. It looks really promising for the 1.4 release of Asterisk this summer. Things are progressing well. At the next SIPit in New Hampshire this fall, I hope to have the first version of chan_sip3 for testing. Asterisk is a world wide project with many members. In Tokyo, I met Japanese Asterisk users and learned quite a lot on how they use Asterisk. An Open Source project is not only about software, it's also about the people involved. You are all very important, your feedback and support are our keys to success. Again, welcome to the Asterisk.org Open Source PBX Project! Meet you on the IRC channel, the bug tracker or on the mailing list! /oej ** Asterisk European Tour - MeetAsterisk.com! This week and next week there's a European tour with Asterisk seminars for beginners, named MeetAsterisk. The event is organized by Edvina.net in cooperation with Digium, Xorcom and local Asterisk distributors and consultants. Register now to make sure you have a seat! - http://www.meetasterisk.com ** Asterisk version information At this moment we have two current versions of Asterisk, the developer version and the release version. The release version is distributed as .tar.gz archives on several servers. The current released version of Asterisk is 1.2.7.1. The release version is fixed, we are adding no new functions and only changes it when bugs are fixed. Current versions: - Asterisk Version 1.2.7.1 - Zaptel Version 1.2.5 - Libpri Version 1.2.2 - Addons Version 1.2.2 - Sounds Version 1.2.1 The development version is to be used by people that can test new functions and live with bugs and unexpected shortcomings. The development version is branded 1.3 and will be the basis for the next release version, version 1.4. There are also a lot of development branches in our subversion repository, hosting new functionality developed for testing by you, the Asterisk community. For more information about these, please visit http://www.voip-forum.com/index.php?p=189more=1 ** The mailing list is growing Today, we propably have over 10,000 readers on the -users list. This means that everything anyone write to this mailing list, is sent to thousands of mailboxes that are already flowing over with messages. That's why we all need to follow some simple rules on how to use the mailing list and the other tools that are available. ** Think before sending a message, think twice I would like to stress the fact that you have to think before you send a message to such a big list. Do *not* send out personal replies on the list. If you offer services to someone, do *not* CC: or reply to the list, it will annoy more potential customers than get you new customers. If you send out a message by mistake, you don't have to apologize to all of us, we understand you're embarassed. We will get more annoyed by your apology than over your first message. And please do not send out test messages to the list. ** Try finding the answer first, then ask the list The Asterisk Wiki at http://www.voip-info.org is an important knowledge base for the project. Go there to find your answer first, then search the mailing list archives (Google or http://search.voip-forum.com) and then go to the IRC channel. The IRC channel is populated with Asterisk gurus around the clock (literally) and they'll help you move forward. * IRC info: http://www.asterisk.org/index.php?menu=support#irc * There's many links to Asterisk web pages on the documentation page at http://www.asterisk.org * The Asterisk FAQ is found on the wiki http://www.voip-info.org/wiki-Asterisk+FAQ * The Asterisk documentation project (which needs your help) is at http://www.asteriskdocs.org You can download their new book from the web site or buy it from the bookstore. * Asterisk Daily news is at http://www.sineapps.com/news.php * VoIP-search (Asterisk mailing list etc) http://search.voip-forum.com Finally, if you don't find the answer elsewhere, try the list. **
Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
[EMAIL PROTECTED] wrote: Where can we find a roadmap of asterisk 1.4 release ? Harry... please use proper mailing list etiquette when posting to these lists. It is very tiresome to see you quote an entire long message, without changing the subject, and insert a one-line unrelated comment at the top of your reply. To answer your question: there is no roadmap for 1.4. We just began the 'scheduled release' cycle with this release, and we are still trying to feel our way into the process and learn how much work we can accomplish in a release cycle. Once 1.4 is done, I expect we will be putting together a roadmap for 1.6, although given that the project gets a great deal of its code from volunteer contributions, putting something on a roadmap is in no way any guarantee that it will be part of that release. ___ --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] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
Ok, Im not a developper but what do you think of both a wish list . Harry To answer your question: there is no roadmap for 1.4. We just began the 'scheduled release' cycle with this release, and we are still trying to feel our way into the process and learn how much work we can accomplish in a release cycle. Once 1.4 is done, I expect we will be putting together a roadmap for 1.6, although given that the project gets a great deal of its code from volunteer contributions, putting something on a roadmap is in no way any guarantee that it will be part of that release. ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set ___ --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] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
On Thu, Jul 22, 2004 at 01:28:50AM +0900, Sunrise Ltd said: snip There is also some stuff that could be done automatically to keep the noise level down. For example ... - any post to the list with the digest in the subject line or the digest in the body, should be auto-rejected. - any post containing any kind of HTML, should be auto-rejected. Agree 1000%. Any attachments other than PGP / SMIME signatures should be rejected or stripped. If people want to post stuff, use a web or FTP site and post a pointer. - any post containing with a very low new content to quotation ratio (ie 20 lines of quotation for a single line of new content) should have the quotation part automatically cut to size (ie no more than 5 lines of quotation per single line of new content apparently responding to that quotation) snip Rather than cutting quoted material automagically, if the system just rejected any post with multiple copies of the mailing list footer that would go a LONG way towards improving etiquette. Refering users to RFC 1855 may be helpful as well. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 22 Jul 2004, Walt Reed wrote: Agree 1000%. Any attachments other than PGP / SMIME signatures should be rejected or stripped. If people want to post stuff, use a web or FTP site and post a pointer. Sounds good to me, except - what about ascii attachments of logs, etc. When searching the archives for references to a problem it's often useful to see the relevent logs which may since have been removed from someone's own website. - -- - Steve Jabber: [EMAIL PROTECTED] Web: http://www.nexusuk.org/ Servatis a periculum, servatis a maleficum - Whisper, Evanescence -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Public key available at http://www.nexusuk.org/pubkey.txt iD8DBQFA/7yj5zUOsIV3bqERAjXRAJ9qD57idEbL3ZFHPZcNHBwwChuunQCeKDbu /51octH0LpyB64Kpttnil44= =zIKo -END PGP SIGNATURE- ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
Walt Reed [EMAIL PROTECTED] wrote: On Thu, Jul 22, 2004 at 01:28:50AM +0900, Sunrise Ltd said: snip There is also some stuff that could be done automatically to keep the noise level down. For example ... - any post to the list with the digest in the subject line or the digest in the body, should be auto-rejected. - any post containing any kind of HTML, should be auto-rejected. Agree 1000%. Any attachments other than PGP / SMIME signatures should be rejected or stripped. If people want to post stuff, use a web or FTP site and post a pointer. I wouldn't even allow those. This is not a repository for legal documents, so signatures are irrelevant. Rather than cutting quoted material automagically, if the system just rejected any post with multiple copies of the mailing list footer that would go a LONG way towards improving etiquette. Agreed. There are just too many lazy people in the world. Anything that helps to give them a well-deserved slap can only be good. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
On Thu, Jul 22, 2004 at 02:09:51PM +0100, [EMAIL PROTECTED] said: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 22 Jul 2004, Walt Reed wrote: Agree 1000%. Any attachments other than PGP / SMIME signatures should be rejected or stripped. If people want to post stuff, use a web or FTP site and post a pointer. Sounds good to me, except - what about ascii attachments of logs, etc. When searching the archives for references to a problem it's often useful to see the relevent logs which may since have been removed from someone's own website. Good point. Maybe check the mime types and have a select few that are allowed. I'm a little leary on this though - if someone attaches a large log instead of a snippit, it gets multiplied 50,000 times. Maybe a size check on attachments. That also allows for reasonable patches and such, but the bug DB is a better place for that stuff anyway. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
Are we on this again? How about letting the list-owner(s) decide what's appropriate here, rather than wasting bandwidth discussing what you guys think is proper list-etiquette. Some people differ from your opinions and their reasons are just as valid as yours. What gets me is that people with signatures like this: -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ are talking about well deserved slaps and telling others what not to do. The noive. -Original Message- From: Walt Reed [mailto:[EMAIL PROTECTED] Sent: Thursday, July 22, 2004 8:36 AM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW * On Thu, Jul 22, 2004 at 02:09:51PM +0100, [EMAIL PROTECTED] said: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 22 Jul 2004, Walt Reed wrote: Agree 1000%. Any attachments other than PGP / SMIME signatures should be rejected or stripped. If people want to post stuff, use a web or FTP site and post a pointer. Sounds good to me, except - what about ascii attachments of logs, etc. When searching the archives for references to a problem it's often useful to see the relevent logs which may since have been removed from someone's own website. Good point. Maybe check the mime types and have a select few that are allowed. I'm a little leary on this though - if someone attaches a large log instead of a snippit, it gets multiplied 50,000 times. Maybe a size check on attachments. That also allows for reasonable patches and such, but the bug DB is a better place for that stuff anyway. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
On Thu, Jul 22, 2004 at 10:52:11AM -0500, Jay Milk said: Are we on this again? How about letting the list-owner(s) decide what's appropriate here, rather than wasting bandwidth discussing what you guys think is proper list-etiquette. Some people differ from your opinions and their reasons are just as valid as yours. The problem is that the community is growing. It's no longer a few guys in their basement playing with phones. The mailing list volume is growing right along with it. You have to remember that this mailing list is one of the few real support channels that exist for *. The S/N ratio is getting pretty bad. Most of us don't have the time to spend all day long to sort the wheat from the chaff. The lack of good ettiquette has destroyed the digest version of this list, and the archives are close behind. How is a noob going to research before posting when the list is full of crap, threads are broken by lazy outlook users, etc? A few bytes spent urging the list admin to become more proactive in improving the quality of ths list is a great investment if the end result is an improvement in the content and usability of this list. I realize he's probably overworked and has a bazillion other things to do, but this really is a problem that needs to get fixed for the good of the community. I've seen what happens to mailing lists that degenerate like this one is. I would prefer that this not happen with *-users. FYI, one typical post by an apathetic user who doesn't trim probably uses more bandwidth than this entire thread. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
Jay Milk [EMAIL PROTECTED] wrote: Are we on this again? How about letting the list-owner(s) decide what's appropriate here, rather than wasting bandwidth discussing what you guys think is proper list-etiquette. Some people differ from your opinions and their reasons are just as valid as yours. What gets me is that people with signatures like this: [snip: same as below] are talking about well deserved slaps and telling others what not to do. The noive. My signature is 4 lines long and starts with a valid signature marker (-- ). I don't like long signatures that stretch into hundreds of lines (Best regards, name, address telephone, fax, mobile, cat's name etc.) but I see nothing wrong with a 4-line signature. You may want to check with RFC1855 (Netiquette Guidelines), which says If you include a signature keep it short. Rule of thumb is no longer than 4 lines. In fact, you should read it anyway, because you clearly don't know (or care) how to quote in context. (Lazily top-posted original message deleted). -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
I am on many mailing lists and lots of them have similar problems with people posting messages they could better answer themselves. Since many of these messages are from people posting for the first time, I think to some degree this is a failing of the mailing list structure itself. I've wondered if a mechanism like this would help: For the first N messages you post to the mailing list, your post does not automatically get posted. Instead you get a message similar to Olle's below, ending with something like: If you still want to send your message to the mailing list, just reply to this message Jim James H. Thompson [EMAIL PROTECTED] - Original Message - From: Olle E. Johansson [EMAIL PROTECTED] To: Users Asterisk [EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 11:40 PM Subject: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW * Welcome to the Asterisk users community! Asterisk.org is a fast moving project. New code is added every day. Asterisk is the leading Open Source Telephony platform, with support both for classical telephony and IP telephony. Our community is also growing fast and we're having a lot of interaction, on the IRC and on the mailing lists. It's great to have you participating in this Open Source project - building an Open Source PBX. Here are a few things to know and remember while working with the project. ** The mailing list is growing The lead programmer of Asterisk, Mark Spencer at Digium, inc, recently wrote: The Asterisk community is growing at a remarkable pace. I know there are thousands of you out there -- in fact there are over eight *thousand* subscribers to asterisk-users alone, and almost one *thousand* registered users on the bug tracker. This means that everything anyone write to this mailing list, is sent to over 8.000 mailboxes that is already flowing over with messages. ** Think before sending a message, think twice I would like to stress the fact that you have to think before you send a message to such a big list. Do *not* send out personal replies on the list. If you offer services to someone, do *not* CC: or reply to the list, it will annoy more potential customers than get you new customers. If you send out a message by mistake, you don't have to apologize to all of us, we understand you're embarassed. We will get more annoyed by your apology than over your first message. ** Looking for or offering a commercial service? Use the asterisk-biz list for discussions on who offers what and for offering your business services. ** Try finding the answer first, then ask the list The Asterisk Wiki at http://www.voip-info.org project is an important knowledge base for the project. Go there to find your answer first, then search the mailing list archives (Google or http://search.voip-forum.com) and then go to the IRC channel. The IRC channel is populated with Asterisk gurus around the clock (literally) and they'll help you move forward. * IRC info: http://www.asterisk.org/index.php?menu=support#irc * There's many links to Asterisk web pages on the documentation page at http://www.asterisk.org * The Asterisk FAQ is found on the wiki http://www.voip-info.org/wiki-Asterisk+FAQ * The Asterisk documentation project (which needs your help) is at http://www.asteriskdocs.org Their handbook The hitchhiker's guide to Asterisk is already well worth reading. Finally, if you don't find the answer elsewhere, try the list. ** Mailing lists For developers, there is a developer's list, asterisk-dev. For BSD users (FreeBSD, NetBSD, OpenBSD and OS/X) there's a list called asterisk-bsd. There is also a business list for those that want to ask for commercial services and inform their community about new services. You'll find all lists on http://lists.digium.com, which is the site where you manage your subscription to this list as well. Please, do not crosspost the same message to multiple mailing lists. It will not help you, it will only add to the mail flow and get people that read both lists irritated. ** Reporting bugs If you think you have found a bug, report it. We need bug reports. Read this document http://www.digium.com/bugtracker.html and then go to the bugtracker http://bugs.digium.com to file a report. If you are unsure, find a bug marshal on the IRC channel to help you. They're appointed to support you with how to handle bugs. Please check the bugtracker thoroughly before posting a new bug; often, your bug or feature already exists but is simply slowly making it's way through the system. Duplicate reports slow things down for everyone, so please spend a few minutes searching first. The bug tracker is also a place where you add your contribution to Asterisk. If you have coded extra functionality, make sure you give it back to the project so it can be added to the code base.
Re: [Asterisk-Users] * INSTRUCTIONS FOR THE ASTERISK COMMUNITY - PLEASE READ NOW *
James H. Thompson wrote: (B (BI've wondered if a mechanism like this would help: (BFor the first N messages you post to the mailing list, (Byour post does not automatically get posted. (BInstead you get a message similar to Olle's below, (Bending with something like: (B (B "If you still want to send your message to (B the mailing list, just reply to this message" (B (BThis might cause more harm than it does good. However, I (Bcan see no harm in sending an auto-reply to each newbie (Bposter (for the first n messages) that asks something like (B"Did you read the rules?" in the subject line containing (B'the rules of conduct" for the list in the body, but (Bwithout the "reply to confirm your post" thing. (B (BThere is also some stuff that could be done automatically (Bto keep the noise level down. For example ... (B (B- any post to the list with the digest in the subject line (Bor the digest in the body, should be auto-rejected. (B (B- any post containing any kind of HTML, should be (Bauto-rejected. (B (B- any post containing with a very low new content to (Bquotation ratio (ie 20 lines of quotation for a single (Bline of new content) should have the quotation part (Bautomatically cut to size (ie no more than 5 lines of (Bquotation per single line of new content apparently (Bresponding to that quotation) (B (BNote: if it is essential that the quotation is left uncut (Bin the resulting post, the responding poster would have to (Buse markup to indicate that the quotation should not be (Bstripped nor cut. For example: (B (B--===[LONG QUOTATION]===--- (B (B very long quotation not to be touched by the ML engine (B (B--===[/LONG QUOTATION]===--- (B (BThis would cut down on excessive laziness quoting. (B (BIt would also be possible to rate each poster's posting (Bquality and send the results to the list every week or (Bmonth. There is a utility that can be used to assess how (Bmuch new content somebody posted and how much quoting (Bposts contained. The utility is called style and has been (Baround for ages, since Bell Labs' early Unix releases. (B (BOf course all this requires a bit of work to do and thus (Btime we all have so little of. (B (BBut at the very least the mailing list's mail host should (Bbe configured to reject anything that contains HTML. This (Bis fairly easy to do and it would go a long distance. (B (Brgds (Bbenjk (B (B (B-- (BSunrise Telephone Systems Ltd (B9F Shibuya Daikyo Bldg., 1-13-5 Shibuya, Shibuya-ku, Tokyo, Japan (B (B__ (BDo You Yahoo!? (BGANBARE! NIPPON! (Bhttp://mail.ganbare-nippon.yahoo.co.jp/ (B (B___ (BAsterisk-Users mailing list (B[EMAIL PROTECTED] (Bhttp://lists.digium.com/mailman/listinfo/asterisk-users (BTo UNSUBSCRIBE or update options visit: (B http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS FOR MEMBERS OF THE COMMUNITY * Please read
On Tuesday 11 May 2004 01:10, Olle E. Johansson wrote: References: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Welcome to the Asterisk users community! Might I make the request that the next time you post this, you do NOT reply to a message that's two months old? Those of us with threaded mail readers have to page back two months in our histories to read your message. -Tilghman ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS
Might I humbly request someone, somewhere in the community establish a dummies guide to asterisk kind of site, that explains in detail what the cryptic scripts actually do, line by line. The Wiki is helpful, but unless you were in on the movie from the first part, the scene discussions are moot. Im grateful for all the most helpful people who have assisted me, and I expect to actually be able to talk to someone with the * soonrite now, IAXTEL isn't recognizing me (after registering and following the thread thru changing my pwd)...Ive put the FWD connection on hold... I know it's a hard stretch for a lot of you who are experts at this, to accommodate the new users. Some explanations as to what each line IS and what it does might be helpful...man, IF I could get mine working (and its for lack of time presently, Im sure the scripts Ive been sent will eventually work) I'd be happy to write something to help people get a simple solution to get it talking so they would be interested in exploring furtherto look at the test scripts, is a exercise in futility (IMHO). I dont say this lightly, I worked commercial switches and SS7 for years...but Im still going DUHIm sure Ill eventually master it, but I sincerely believe we need some real * 101 instructional stuffone of these days Im sure the light will switch on, and I'll say I wonder how I didn't get it, just like you are in that position now. This is NOT a criticism, please dont take it that way...its merely a suggestion for easing the transition into understanding, and thus sparking interest in further exploration and hopefully a greater user base. Marc, with hopefully positive advice...and to all who contacted me, THANK YOUvery much.. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS
On Friday 23 April 2004 07:55 am, tmpm wrote: Might I humbly request someone, somewhere in the community establish a dummies guide to asterisk kind of site, that explains in detail what the cryptic scripts actually do, line by line. The Wiki is helpful, but unless you were in on the movie from the first part, the scene discussions are moot. I know it's a hard stretch for a lot of you who are experts at this, to accommodate the new users. Some explanations as to what each line IS and what it does might be helpful...man, IF I could get mine working (and its for lack of time presently, Im sure the scripts Ive been sent will eventually work) I'd be happy to write something to help people get a simple solution to get it talking so they would be interested in exploring furtherto look at the test scripts, is a exercise in futility (IMHO). I dont say this lightly, I worked commercial switches and SS7 for years...but Im still going DUHIm sure Ill eventually master it, but I sincerely believe we need some real * 101 instructional stuffone of these days Im sure the light will switch on, and I'll say I wonder how I didn't get it, just like you are in that position now. This is NOT a criticism, please dont take it that way...its merely a suggestion for easing the transition into understanding, and thus sparking interest in further exploration and hopefully a greater user base. As a not-quite-so-newbie on the brink of understanding the hugeness of Asterisk, I am greatly compelled to agree with everything written above. BTW - I contributed to the Wikki on more than a few occasions when I _finally_ had an epiphany understanding Asterisk, and I plan to do so more in the future. Anon ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS
Roger that, Ill grep. er google for it...thanks... At 04:10 4/23/2004, you wrote: There is the handbook on the homepage and then there is the hitchhikers guid,just not sure where it is ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS
Im hoping that light bulb will glimmer on any day now...heh... BTW - I contributed to the Wikki on more than a few occasions when I _finally_ had an epiphany understanding Asterisk, and I plan to do so more in the future. Anon ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS
On Fri, 23 Apr 2004 03:55:57 -0400, tmpm [EMAIL PROTECTED] wrote: Might I humbly request someone, somewhere in the community establish a dummies guide to asterisk kind of site, that explains in detail what the cryptic scripts actually do, line by line. The Wiki is helpful, but unless you were in on the movie from the first part, the scene discussions are moot. If you haven't seen the movie yet, the hardest part will be understanding the dial plan. http://www.asteriskdocs.org/stable/docs-html/c511.html gives some insight, but http://www.loligo.com/asterisk/current/ is a working example. I finally figured out what was going on by poring over his extensions.conf ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] * INSTRUCTIONS FOR NEW MEMBERS OF THE COMMUNITY * Please read
snip These are exiting times for Asterisk.org. We're getting close to a Ehh, you surely don't mean 'exiting' time :)? Not a good idea to tell new members to jump off the ship just after they boarded. Suggestion, can this message be sent as part of the list welcome message? Cheers. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
