[asterisk-dev] AST-2017-014: Crash in PJSIP resource when missing a contact header

Asterisk Project Security Advisory - AST-2017-014 ProductAsterisk SummaryCrash in PJSIP resource when missing a contact header

[asterisk-dev] Asterisk 13.18.5, 14.7.5, 15.1.5 and 13.18-cert2 Now Available (Security)

The Asterisk Development Team would like to announce security releases for Asterisk 13, 14 and 15, and Certified Asterisk 13.18. The available releases are released as versions 13.18.5, 14.7.5, 15.1.5 and 13.18-cert2. These releases are available for immediate download at

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Regarding the func_redis module linked here - I contributed a couple of patches to it and I spoke to Sergio (the original author) and he is no longer associated with the IT Departament of the University of La Laguna Tenerife Spain, who currently owns this repository. He says that the current

Re: [asterisk-dev] tags on the main branches [was: Re: Minor Release Branches]

On 12/22/2017 12:36 PM, George Joseph wrote: On Fri, Dec 22, 2017 at 9:50 AM, Corey Farrell > wrote: On 12/22/2017 10:22 AM, George Joseph wrote: On Thu, Dec 21, 2017 at 1:44 PM, Corey Farrell >

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

I hope we consider creating a res_redis first, then base everything off that.  If a redis library can be used directly by any module that would fine but I'd like to see us avoid following the example of curl where everything uses a dialplan function to perform requests.  Dialplan functions

Re: [asterisk-dev] tags on the main branches [was: Re: Minor Release Branches]

On Fri, Dec 22, 2017 at 9:50 AM, Corey Farrell wrote: > On 12/22/2017 10:22 AM, George Joseph wrote: > > > > On Thu, Dec 21, 2017 at 1:44 PM, Corey Farrell wrote: > >> George asked that I post some scenarios where this would be useful. >> 1. You are about to

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Well, We can start with that implementation as a base for learning, and go from there. Looks like I have some homework for tonight. Nir On Fri, Dec 22, 2017, 18:44 Matt Fredrickson wrote: > On Fri, Dec 22, 2017 at 10:23 AM, Ivan Poddubny > wrote:

Re: [asterisk-dev] tags on the main branches [was: Re: Minor Release Branches]

On 12/22/2017 10:22 AM, George Joseph wrote: On Thu, Dec 21, 2017 at 1:44 PM, Corey Farrell > wrote: George asked that I post some scenarios where this would be useful. 1. You are about to create updated asterisk package and want to

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

On Fri, Dec 22, 2017 at 10:23 AM, Ivan Poddubny wrote: > Hi, > > There is an out-of-tree implementation of func_redis: https://github. > com/tic-ull/func_redis. > I don't use it in production, but it worked fine for me on a test machine. > With slight modifications it

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Hi, There is an out-of-tree implementation of func_redis: https://github.com/tic-ull/func_redis. I don't use it in production, but it worked fine for me on a test machine. With slight modifications it works with Asterisk 13+. Unfortunately, the project seems to be abandoned and the author did not

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

On Fri, Dec 22, 2017 at 6:58 AM, Nir Simionovich wrote: > Abhay, > > Migrating astsb from SQLlite to redis isn't the topic here. I'm talking > adding a new type of storage engine. For example, func_redis, that will > implement the relevant key/value operations that are

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Hi, On 12/22/2017 7:22 AM, Nir Simionovich wrote:   Every, and I do mean every, Asterisk application requires a key/value store of some form. Most developers will basically butcher (would have used stronger words, but refraining from doing so) AstDB in the process, which will then result in a

Re: [asterisk-dev] tags on the main branches [was: Re: Minor Release Branches]

On Thu, Dec 21, 2017 at 1:44 PM, Corey Farrell wrote: > George asked that I post some scenarios where this would be useful. > 1. You are about to create updated asterisk package and want to quickly > scan the changes to 13 since latest 13.x.0 release to see if anything is a >

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

I would have an immediate use case for something like func_redis. I think it would be very useful.  On December 22, 2017 at 8:02:28 AM, Nir Simionovich (nir.simionov...@gmail.com) wrote: Abhay, Migrating astsb from SQLlite to redis isn't the topic here. I'm talking adding a new type of

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

On Fri, Dec 22, 2017 at 5:22 AM, Nir Simionovich wrote: > Hi All, > > Following a discussion on JIRA [https://issues.asterisk.org/ > jira/browse/ASTERISK-27383], I truly believe that > adding a scaleable, robust and most importantly - accepted key/value store >

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Abhay, Migrating astsb from SQLlite to redis isn't the topic here. I'm talking adding a new type of storage engine. For example, func_redis, that will implement the relevant key/value operations that are commonly used by people. Nir On Fri, Dec 22, 2017, 14:33 Abhay Gupta

Re: [asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Hi All, I had a program where I have implemented a project using REDIS wherein the client is made using a socket library and no other third party client library in C . This REDIS database has 400 million records and performs extremely well though the memory requirement for such a large

[asterisk-dev] Adding a Key/Value Store mechanism to Asterisk

Hi All, Following a discussion on JIRA [ https://issues.asterisk.org/jira/browse/ASTERISK-27383], I truly believe that adding a scaleable, robust and most importantly - accepted key/value store mechanism to the Asterisk dialplan is a worthwhile effort. Every, and I do mean every, Asterisk