Re: [asterisk-dev] Mailing List Future
> On Dec 4, 2023, at 9:19 AM, Joshua C. Colp wrote: > > No changes have actually occurred as of yet, aside from me sending an email, > and I also gave 2 months of notice on purpose to allow people to think and > respond. > In your original email you wrote: > To that end, we’ve decided to discontinue the mailing lists effective > February 1st, 2024. This absolutely gives the impression of a decision/change being made. Regards, Fred Posner p: +1 (352) 664-3733 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Mailing List Future
Looks like the majority of responses are negative. I’m also disappointed in this decision/ > Over the past few years, the use of the Asterisk mailing lists has > diminished, with far more conversation happening on the Asterisk community > forums[1]. The state of email, to ensure reliable delivery, has also gotten > more complicated - emails get caught by spam filters, etc.. To continue the > mailing lists would require a huge time and resource investment, for minimal > use. I don’t want to get on a “which is better” argument, but will add that email is by far the most accessible method of communication available to a worldwide audience of different means, languages, and abilities. It is not prohibitive by those with limited sight, easily translated, easily indexed for searching, and simple for those on even the most basic non-gui systems. Of course there are also other benefits that I think would only result in wasted typing as it seems that this decision done. I will say the disappointment comes from making such a change without even taking the minimal effort of surveying the user/list base/community for what methods would be most desired. The complicated argument, in my opinion, is a bit exaggerated and the issues have been handled by so many other groups, that assistance can surely be provided if the project having trouble. To me personally, this shows how important it is to strengthen the community as a whole, to check the temperature now and then, and to consider feedback/audience/goal prior to making top down decisions. I remain disappointed; although to be honest, at this point, I’m not surprised by these decisions. Regards, Fred Posner p: +1 (352) 664-3733 > On Dec 4, 2023, at 8:06 AM, Jonathan Aquilina wrote: > > I would like to add my 2 cents here as a long tim follower of this list. > > I am aware of another mailing platform for such mailing lists. > > https://www.sympa.community/ > > Would something like this be considered as a replacement from what I am > assuming this list is based on which is mailman? > > Also if you do decide to upgrade the infra and mailing list. I would highly > recommend it is done internally at sangoma given then there are alot of GDPR > and other privacy concerns that woudl arise. > > Regards, > Jonathan Aquilina > From: asterisk-dev on behalf of > Joshua C. Colp > Sent: Monday, December 4, 2023 14:02 > To: aster...@phreaknet.org > Cc: Asterisk Developers Mailing List > Subject: Re: [asterisk-dev] Mailing List Future > On Mon, Dec 4, 2023 at 8:52 AM wrote: > I strongly object to not having an asterisk-dev list. Mailing lists are > essential for FOSS developer discussion. The majority of non-ephemeral > development discussion happens either on IRC or here on the asterisk-dev > list - just check the archives to see that it's still active. Most of us > are not on the community forums and/or couldn't be bothered to use them. > You can go and see now that "Development" on the community forums is > basically dead, because nobody wants to use it, so trying to push that > on everyone is a terrible idea. > > The "Development" category was done on a whim and hasn't really been > advertised or mentioned a huge amount. I presented it merely as an option, as > it was present. > > Even for users, I think the loss of asterisk-users will be a major loss. > Far more *discussion* is happening on the Discourse forum, but far more > *quality* discussion still happens on asterisk-users. Being on a mailing > list seems to be a natural weedout for junk questions. More serious > questions still seem to come through on the mailing list. The community > forums is far fuller of useless postings from people who can't tell a > hard drive from a memory stick. Nobody wants to wade through a bunch of > low-quality posts to find the few that might have some use. Thus, > getting rid of asterisk-users would see a significant drop in the > average quality of user engagement. But at least, even if the -users > list is dropped, the -dev list should stick around in some form. > > To be quite blunt, the quality is better on asterisk-users because few > actually use it. In the earlier days the quality wasn't as good when it was > actually used more. Even then, the quality still varies on the asterisk-users > list. > > I know the forums can have emails enabled that you can receive, and no, > that's not a proper replacement for a mailing list. > > GitHub Discussions aren't a proper mailing list, either, so ultimately I > think that will run into the same issue. GitHub has a lot of bells and > whistles but most of them aren't as built out as using the proper tool > they try to emulate. > > I think #3 is
Re: [asterisk-dev] AstriCon 2024: February 15th, 2024 - Fort Lauderdale, Florida
+1 regarding valentine’s day… Also, is AstriCon just one day this year? Regards, Fred Posner p: +1 (352) 664-3733 > On Sep 5, 2023, at 11:07 AM, Jared Smith wrote: > > > > On Tue, Sep 5, 2023 at 10:06 AM Joshua C. Colp wrote: > The 25th anniversary of Asterisk is upon us! We’ll be celebrating it at > AstriCon 2024 held on February 15th, 2024 in Fort Lauderdale, Florida as part > of IT Expo. We’d love it if you would join us. You can register here[1], and > if you would like to speak you can submit a speaking proposal by October 14th > here[2]. I look forward to seeing many of you there! > > Thanks for sharing this, Josh. Has there been any consideration of not doing > AstriDevCon (and AstriCon itself) around Valentines Day? I imagine I'm not > the only one who would prefer not to travel that week to help ensure domestic > tranquility. > > -Jared > > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] AstriCon 2024: February 15th, 2024 - Fort Lauderdale, Florida
Greetings, > On Sep 5, 2023, at 10:24 AM, Joshua C. Colp wrote: > > Everyone involved in AstriCon from Sangoma is in agreement that this is a > requirement and is being worked on. > Thanks. Looking forward to confirmation of this. Regards, Fred Posner -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] AstriCon 2024: February 15th, 2024 - Fort Lauderdale, Florida
Greetings. Is there any commitment from Sangoma to: 1) Take and upload videos of AstriCon talks? 2) Provide any Asterisk/FreePBX activities/events outside of general ITEXPO? Regards, Fred Posner > On Sep 5, 2023, at 9:14 AM, Joshua C. Colp wrote: > > Greetings all, > > The 25th anniversary of Asterisk is upon us! We’ll be celebrating it at > AstriCon 2024 held on February 15th, 2024 in Fort Lauderdale, Florida as part > of IT Expo. We’d love it if you would join us. You can register here[1], and > if you would like to speak you can submit a speaking proposal by October 14th > here[2]. I look forward to seeing many of you there! > > While not AstriCon specific I'm also doing a webinar next week called "The > Evolution of Asterisk" which will talk about the history, how Asterisk has > changed including philosophy on things, and give a glimpse into future > interests. You can register for that here[3]. I can promise I will say words > and they might mean things. > > For us developers AstriDevCon will be held physically the day before on > February 14th. I aim to have the entire Asterisk development team at Sangoma > present. For those unable to physically attend it will also be virtually > accessible. Details, including a signup page, will be provided closer to it. > Right now it's still months out and if past AstriDevCons have taught me > anything it's that we all forget we were doing it until the last moment > anyway and sometimes forget we even signed up and sign up multiple times. :D > > Cheers, > > [1] https://www.astricon.net/ > [2] > https://docs.google.com/forms/d/e/1FAIpQLSeECYs1Bltl0wdfEF57ngGiorTAq79l5Du-Uyn_MuvAut57jw/viewform > [3] https://register.gotowebinar.com/register/969603661543016283 > > -- > Joshua C. Colp > Asterisk Project Lead > Sangoma Technologies > Check us out at www.sangoma.com and www.asterisk.org > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Important!: Personal spaces on wiki.asterisk.org
Has there been a post on what is replacing this? Regards, Fred Posner > On Aug 4, 2023, at 12:41 PM, George Joseph wrote: > > When wiki.asterisk.org goes away (soon), any personal spaces you may have > created will also be going away. If you want the content, either grab it > yourself or email me directly and I'll export it for you and send you a link > to a tarball. Either way, you should do this before next Friday August 11th. > > -- > George Joseph > Asterisk Software Developer > Sangoma Technologies > Check us out at www.sangoma.com and www.asterisk.org > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Test HTML version of...Asterisk Release 20.3.0-rc1
Is this type of message going to be common now? Asking as it’s a departure from the lists general traffic. Regards, Fred Posner > On May 18, 2023, at 2:07 PM, Asterisk Development Team > wrote: > > The Asterisk Development Team would like to announce > release candidate 1 of Asterisk 20.3.0. > The release artifacts are available for immediate download at > https://github.com/asterisk/asterisk/releases/tag/20.3.0-rc1 and > https://downloads.asterisk.org/pub/telephony/asterisk > This release resolves issues reported by the community > and would have not been possible without your participation. > Thank You! > Change Log for Release 20.3.0-rc1 Summary: > • Set up new ChangeLogs directory > • .github: Add AsteriskReleaser > • chan_pjsip: also return all codecs on empty re-INVITE for late offers > • cel: add local optimization begin event > • core: Cleanup gerrit and JIRA references. (#57) > • .github: Fix CherryPickTest to only run when it should > • .github: Fix reference to CHERRYPICKTESTINGINPROGRESS > • .github: Remove separate set labels step from new PR > • .github: Refactor CP progress and add new PR test progress > • res_pjsip: mediasec: Add Security-Client headers after 401 > • .github: Add cherry-pick test progress labels > • LICENSE: Update link to trademark policy. > • chan_dahdi: Add dialmode option for FXS lines. > • .github: Update issue templates > • .github: Remove unnecessary parameter in CherryPickTest > • Initial GitHub PRs > • Initial GitHub Issue Templates > • pbx_dundi: Fix PJSIP endpoint configuration check. > • Revert "app_queue: periodic announcement configurable start time." > • respjsipstir_shaken: Fix JSON field ordering and disallowed TN > characters. > • pbx_dundi: Add PJSIP support. > • install_prereq: Add Linux Mint support. > • chan_pjsip: fix music on hold continues after INVITE with replaces > • voicemail.conf: Fix incorrect comment about #include. > • app_queue: Fix minor xmldoc duplication and vagueness. > • test.c: Fix counting of tests and add 2 new tests > • res_calendar: output busy state as part of show calendar. > • loader.c: Minor module key check simplification. > • ael: Regenerate lexers and parsers. > • bridgebuiltinfeatures: add beep via touch variable > • res_mixmonitor: MixMonitorMute by MixMonitor ID > • format_sln: add .slin as supported file extension > • res_agi: RECORD FILE plays 2 beeps. > • func_json: Fix JSON parsing issues. > • app_senddtmf: Add SendFlash AMI action. > • app_dial: Fix DTMF not relayed to caller on unanswered calls. > • configure: fix detection of re-entrant resolver functions > • cli: increase channel column width > • app_queue: periodic announcement configurable start time. > • make_version: Strip svn stuff and suppress ref HEAD errors > • reshttpmedia_cache: Introduce options and customize > • main/iostream.c: fix build with libressl > • contrib: rc.archlinux.asterisk uses invalid redirect. > User Notes: > • cel: add local optimization begin event > The new ASTCELLOCALOPTIMIZEBEGIN can be used by itself or in conert with the > existing ASTCELLOCAL_OPTIMIZE to book-end local channel optimizaion. > • chan_dahdi: Add dialmode option for FXS lines. > A "dialmode" option has been added which allows specifying, on a per-channel > basis, what methods of subscriber dialing (pulse and/or tone) are permitted. > Additionally, this can be changed on a channel at any point during a call > using the CHANNEL function. > • app_senddtmf: Add SendFlash AMI action. > The SendFlash AMI action now allows sending a hook flash event on a channel. > • res_mixmonitor: MixMonitorMute by MixMonitor ID > It is now possible to specify the MixMonitorID when calling the manager > action: MixMonitorMute. This will allow an individual MixMonitor instance to > be muted via ID. The MixMonitorID can be stored as a channel variable using > the 'i' MixMonitor option and is returned upon creation if this option is > used. As part of this change, if no MixMonitorID is specified in the manager > action MixMonitorMute, Asterisk will set the mute flag on all MixMonitor > audiohooks on the channel. Previous behavior would set the flag on the first > MixMonitor audiohook found. > • bridgebuiltinfeatures: add beep via touch variable > Add optional touch variable : TOUCHMIXMONITORBEEP(interval) Setting > TOUCHMIXMONITORBEEP/TOUCHMONITORBEEP to a valid interval in seconds will > result in a periodic beep being played to the monitored channel upon > MixMontior/Monitor feature start. If an interval less tha
Re: [asterisk-dev] AstriDevCon 2021
Any chance on switching from IRC to Matrix this year now that freenode is not saving the drama for mama? On 8/3/21 9:06 AM, Joshua C. Colp wrote: > Kia ora, > > It's that time again! AstriDevCon 2021 is fast approaching and signup > is now open[1]. AstriDevCon will be on Tuesday, September 28th, at the > Loews Royal Pacific in Orlando, Florida. If you would like to > attend, discussion is intended to be focused on developmental and > project level topics. Seating space is limited, so signing up sooner > rather than later is recommended. Due to the limited seating, > please wait for an acceptance email before making conclusive plans > to attend DevCon that day. > > Also, we plan on continuing our format from previous years to allow > people to submit talk proposals for DevCon. You can find information > in the signup form about how to include a proposal. > > Cheers, > > [1] https://wiki.asterisk.org/wiki/display/AST/AstriDevCon > <https://wiki.asterisk.org/wiki/display/AST/AstriDevCon> > > -- > Joshua C. Colp > Asterisk Technical Lead > Sangoma Technologies > Check us out at www.sangoma.com <http://www.sangoma.com> and > www.asterisk.org <http://www.asterisk.org> > -- Fred Posner -- qxork.com matrix: @fred:matrix.lod.com Need Fred? Call Fred. +1 (352) OMG-FRED -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Clear a secret from sip.conf and phone sill can dial
On 7/5/21 11:45 PM, SAMPro wrote: > > By endpoints you mean the phone? May you give me a guide about how to > check the endpoints? > An endpoint would refer to a phone or other device using SIP to connect to your Asterisk system. I don't have a script written for this, but you would be best suited to reach out to the users list rather than the dev list for such a question. -- Fred Posner -- qxork.com matrix: @fred:matrix.lod.com Need Fred? Call Fred. +1.336.HEY-FRED -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Clear a secret from sip.conf and phone sill can dial
On 7/5/21 1:51 PM, SAMPro wrote: > phones with inappropriate config That statement is the error you're having. The config is appropriate for an extension that should not be authenticated. This isn't so much an asterisk issue as a user issue. You can either comment out the entire extension, or you could probably write a script in your favorite scripting language that checks that all endpoints have passwords or makes an alert. -- Fred Posner -- qxork.com matrix: @fred:matrix.lod.com Need Fred? Call Fred. +1.336.HEY-FRED -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] External scripts for parsing the security logs
On Mon, 2020-11-23 at 16:22 -0500, Sean Bright wrote: > On 11/23/2020 4:09 AM, Mohit Dhiman wrote: > > can anyone please recommend any existing external scripts that can > > parse the Asterisk security logs and possibly take appropriate > > actions like IP blocking. > > Fail2ban I wrote one years ago that I still use: https://github.com/fredposner/scripts/blob/master/asterisk/check-failed-regs.pl You'll need to make a chain called "asterisk" in iptables. Also, we started providing a pro-active block to sip attacks with apiban in January. There's a go client that will update iptables as well: https://github.com/palner/apiban -- Fred Posner f...@qxork.com https://qxork.com Direct/SMS: +1 (336) 439-3733 Need Fred? Call Fred. 336-HEY-FRED Matrix: @fred:matrix.lod.com -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Module Deprecation, Default Not Building, and Removal
On Thu, 2020-10-01 at 20:14 +0100, Dan Jenkins wrote: > I'd argue two years isn't exactly quick... Especially with warnings > on previous minor releases after decisions have been made. 2 years > is fair - 4 is just too long. But if everyone else feels like 4 is > fine then I'll stop my protest ;) I think it's a good starting point to go with 4... and then easier to perhaps quicken that to 2 in the future. =) -- Fred Posner f...@qxork.com https://qxork.com Direct/SMS: +1 (336) 439-3733 Need Fred? Call Fred. 336-HEY-FRED Matrix: @fred:matrix.lod.com > > On Thu, 1 Oct 2020, 20:09 Joshua C. Colp, wrote: > > On Thu, Oct 1, 2020 at 3:56 PM Dan Jenkins wrote: > > > If there was an additional message attached to minor releases, > > > does that mean we can accelerate the steps? > > > > > > On the question of why I'm opposed to 4 years? 4 years is an > > > eternity to be in limbo - we've already seen this with chan_sip > > > - even though its deprecated in 17, people still start using > > > Asterisk today and use chan_sip because they don't know any > > > better and a crap load of documentation out on the internet uses > > > it. If the modules are deprecated, they're deprecated for a > > > reason - kill them as quickly as reasonably possible and be done > > > with it - it'll help everyone in the community long term. If > > > someone disagrees with say getting rid of chan_sip then they can > > > continue to run 17/18 or whatever - or they can take the > > > contents of chan_sip, and apply them as a patch themselves. I'm > > > picking on chan_sip here because its the current thing that > > > caused these conversations in the first place. > > > > > > > Okay, so you'd like to see it be faster because in your opinion > > its better for the user base long term to force the transition > > quickly. > > > > I think I personally hesitate to be so aggressive because long ago > > the project was that way. We would push to remove things faster > > and such, and the result was upset people and complaints. Years > > later I still had people coming up to me at AstriCon talking about > > that stuff and how it screwed them over. > > > > -- > > Joshua C. Colp > > Asterisk Technical Lead > > Sangoma Technologies > > Check us out at www.sangoma.com and www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
