similar to: Asterisk 10 EOL Notice

Hello everyone! On December 15th, 2013, Asterisk 10 officially reached its End of Life [1]. As a Standard Release, Asterisk 10 received one year of bug fix support, followed by one year of security fix support. Users of Asterisk 10 should consider moving to Asterisk 11 at their earliest possible convenience. Asterisk 11 is a Long Term Support (LTS) Release, and will continue to receive bug fix

Hello! This is a friendly reminder that the official End of Life of Asterisk 10 is approaching soon. As a Standard release of Asterisk, Asterisk 10 received one year of maintenance fixes followed by one year of security fixes; that final year is now just about up. After 2013-12-15 (December 15th), releases of Asterisk 10 will no longer be made. Users of Asterisk 10 are encouraged to move to the

Hey everyone! Way back in the murky days of 2010, the Asterisk project released the first version of Asterisk 1.8. This was the first release following a new policy of alternating Long Term Support (LTS) releases and Standard releases. As the first LTS release, Asterisk 1.8 was quite the milestone -- as a project, we officially committed ourselves to its maintenance for four years! Since its

Howdy, I am proud to announce that after a good bit of development, community feedback, testing, and code review, the brand new ConfBridge application has been officially merged into Asterisk Trunk!!! http://svnview.digium.com/svn/asterisk?view=revision&revision=314598 If you are already familiar with ConfBridge from Asterisk 1.6.X and 1.8, forget everything you know. This is a completely

Thanks for your (fast) reply ! Le ven. 18 janv. 2019 à 16:32, Joshua C. Colp <jcolp at digium.com> a écrit : > On Fri, Jan 18, 2019, at 11:22 AM, Olivier wrote: > > Hello, > > > > I've just read in [1] about SIP MESSAGE addition to both chan_pjsip and > > ConfBridge. > > It seems very interesting addition as it brings the capability to mix > >

On Mon, Aug 26, 2019, at 2:00 PM, Dan Cropp wrote: > Thank you Joshua. > > Out of curiosity, what is the maximum capacity you have heard for > simultaneous ConfBridges in a single box? (Looking at 3-4 channels per > ConfBridge) with recording. I don't really remember any specific values. 100? 200? -- Joshua C. Colp Digium - A Sangoma Company | Senior Software Developer

On Wed, Dec 17, 2014 at 1:09 PM, sean darcy <seandarcy2 at gmail.com> wrote: > I've got a confbridge set up which works if dialed locally: > > -- Executing [266 at internal:1] Answer("DAHDI/1-1", "") in new stack > -- Executing [266 at internal:2] SendDTMF("DAHDI/1-1", "1") in new stack > -- Executing [266 at internal:3]

On Wed, Aug 21, 2019, at 1:54 PM, Doug Lytle wrote: > Dan, > > I don't run Asterisk on AWS, but I do on ESXi. Are you running a > version of Asterisk before 13? Newer versions Asterisk handle timing > better that don't require a hardware timing source. > > I'm running Asterisk 13 on a small 60 phone system without issues under ESXi 6.0 Ultimately it still

CentOS Errata and Security Advisory CESA-2011:0219 This is the 1 year notification for the End of Life for the CentOS 4 distribution. The upstream provider will discontinue public updates of their EL4 product on February 29th, 2012. The CentOS Project will end support for CentOS 4 on the same date. CentOS 4, as well as all previously released versions of CentOS, will continue to be available

CentOS Errata and Security Advisory CESA-2011:1240: This is the 6-month notification for the End of Life for the CentOS 4 distribution. The upstream provider will discontinue public updates of their EL4 product on February 29th, 2012. The CentOS Project will end support for CentOS 4 on the same date. CentOS 4, as well as all previously released versions of CentOS, will continue to be available

Hi, I cannot take any more arches for official maintenance at current state of the CentOS-project. I'll keep it security updated until end of August, 2006. After that it's not supported (unless someone else picks it up). I am sorry it has to be this way. Sparc itself is kind of fun/challenging arch to work with. -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/

Hi, I cannot take any more arches for official maintenance at current state of the CentOS-project. I'll keep it security updated until end of August, 2006. After that it's not supported (unless someone else picks it up). I am sorry it has to be this way. Sparc itself is kind of fun/challenging arch to work with. -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/

recreate Echo, if that is possible. trying to recode all dialplan to stasis application > On 22 May 2015, at 19:29, Scott Griepentrog <sgriepentrog at digium.com> wrote: > > Nick- > > Are you wanting to recreate the dialplan Echo() application in stasis? > > Why not just send the call to Echo() instead of Stasis()? > > On Fri, May 22, 2015 at 11:25 AM, Matthew

Thank you Kevin. Any idea if Google developers may decide to reset the decoder, per Joshua’s experience? Or perhaps asterisk developers would consider eventually add the rewrite support in asterisk? Always fun dealing with newer technology as it goes through several revisions. Have a great day! Dan From: asterisk-users <asterisk-users-bounces at lists.digium.com> On Behalf Of Kevin

I'm pretty sure there isn't a way to do that currently. ?My best guess would be that a new special type of bridge technology could be created that would implement the per-channel echo (no audio bridged between channels in the bridge). That would require new C code in Asterisk for the bridge, and then the usual methods of moving channels in to bridges with ARI could be used.? On Sat, May

On Tue, Apr 2, 2019 at 4:18 PM Joshua C. Colp <jcolp at digium.com> wrote: > On Tue, Apr 2, 2019, at 8:15 PM, BJ Weschke wrote: > > I get the desired use case to run app_amd from within a Stasis > > application, but I’m not sure about app_queue. You have everything at > > your disposal within ARI itself to replicate all of the functionality > > of app_queue and

The G.729.1 "wideband" codec is starting to show a slight bit of traction. There is a possibility that Asterisk could support G.729.1 - would you use it or buy it if it was available? More importantly, does any equipment with which your systems currently exchange traffic support G.729.1? Currently, the number of devices supporting G.729.1 seems to be fairly limited and it

Nick- Are you wanting to recreate the dialplan Echo() application in stasis? Why not just send the call to Echo() instead of Stasis()? On Fri, May 22, 2015 at 11:25 AM, Matthew Jordan <mjordan at digium.com> wrote: > On Fri, May 22, 2015 at 4:41 AM, Nick Awesome <jleed at me.com> wrote: > > Can anyone tell me how can I create echo test using ARI stasis > application?

Hey everyone! This is a friendly reminder that Asterisk 12 will be entering security fix only mode soon. As a Standard release of Asterisk, Asterisk 12 received one year of maintenance fixes, and will receive one year of security fixes. Asterisk 12 was first released on 2013-12-20 - the one year anniversary of which is just around the corner! After 2014-12-20, additional releases of Asterisk 12

Hi, I wanted to follow up on this thread about WB support on the MeetMe bridge that is in 1.6.2. Does it only work for G722 or any WB codec ? I am working with another 16k WB codec that I can transcode to 722 and vice versa. I was curious if the 1.6.2 MeetMe bridge can also mix 722 with any other WB codec natively(without downscaling). Thanks, Serhad Doken ------------------> Razza wrote: