Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

On Wed, Oct 12, 2016 at 2:43 PM, Matt Fredrickson wrote: > I've been deliberately waiting to weigh in on this discussion - > however, my thoughts are as follows: > > 1.) Marking a module as deprecated is *not* the same thing as moving > it out of the code base. It simply

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

I've been deliberately waiting to weigh in on this discussion - however, my thoughts are as follows: 1.) Marking a module as deprecated is *not* the same thing as moving it out of the code base. It simply means that there is no maintainer, and something better exists in the code base to move to.

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

On Mon, Oct 10, 2016 at 10:39 AM, Matthew Jordan wrote: > > On Fri, Oct 7, 2016 at 10:31 AM, Corey Farrell wrote: > > Many people don't like chan_sip, most people hate working with the code. > > The rush to throw out chan_sip when PJSIP isn't ready to be the

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

On Fri, Oct 7, 2016 at 10:31 AM, Corey Farrell wrote: > Many people don't like chan_sip, most people hate working with the code. > The rush to throw out chan_sip when PJSIP isn't ready to be the only SIP > stack annoys me a bit. Nobody is forcing anyone to use or contribute to >

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

Many people don't like chan_sip, most people hate working with the code. The rush to throw out chan_sip when PJSIP isn't ready to be the only SIP stack annoys me a bit. Nobody is forcing anyone to use or contribute to chan_sip. Digium changed chan_sip from core to extended support so they can

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

Michael, What would be amazing is for you to tell us which features you are missing (or were missing when you tried) If we start a working group around PJSIP migration then these points will help drive that forward. Dan feedback on marketing features over chan_sip (and not only

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

On Thu, Oct 6, 2016 at 10:01 AM, marek cervenka wrote: > > Michael, >> >> What would be amazing is for you to tell us which features you are >> missing (or were missing when you tried) >> >> If we start a working group around PJSIP migration then these points will >> help

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

t > > > > > > support PJSip - familiarity will breed use. > > > > > > > > > > > > 2. One suggestion to do this was to declare that Chan_Sip would be > > > > > > depreciated in version 15 or 16. This would not mean removing it from > > the > > > > > > code, but that going forward (for 1 or 2 more releases) it would only > > get > > > > > > security fixes and no more development. This would have the benefit > > > > > > of everyone would have 3-5 years to learn and transition to PJSip > > without > > > > > > breaking anything that is currently working, while releasing > > development > > > > > > staff to improving the interface and problems with PJSip and other > > parts of > > > > > > Asterisk. > > > > > > > > > > > > Eric Klein > > > > > > VP of Customer Experience > > > > > > GreenfieldTech > > > > > > Mobile +972-54-666-0933 > > > > > > Email eric.kl...@greenfieldtech.net > > > > > > Skype: EricLKlein > > > > > > Web: http://www.greenfieldtech.net/ > > > > > > > > > > > > > > > > > > > > > > > >> Message: 5 > > > > > >> Date: Tue, 4 Oct 2016 17:46:52 -0700 > > > > > >> From: James Finstrom <jfinst...@gmail.com> > > > > > >> To: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com> > > > > > >> Subject: [asterisk-dev] Viva Chan_Sip, may it rest in peace > > > > > >> Message-ID: > > > > > >>

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

> > > depreciated in version 15 or 16. This would not mean removing it from > the > > > > code, but that going forward (for 1 or 2 more releases) it would only > get > > > > security fixes and no more development. This would have the benefit > > > > of everyone wo

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

fieldTech > > Mobile +972-54-666-0933 > > Email eric.kl...@greenfieldtech.net > > Skype: EricLKlein > > Web: http://www.greenfieldtech.net/ > > > > > > > >> Message: 5 > >> Date: Tue, 4 Oct 2016 17:46:52 -0700 > >> From: James Finstrom <jfinst...@gmail.com> > >> To: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com> > >> Subject: [asterisk-dev] Viva Chan_Sip, may it rest in peace > >> Message-ID: > >>

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

sage: 5 >> Date: Tue, 4 Oct 2016 17:46:52 -0700 >> From: James Finstrom <jfinst...@gmail.com> >> To: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com> >> Subject: [asterisk-dev] Viva Chan_Sip, may it rest in peace >> Message-ID: >>

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

e > GreenfieldTech > Mobile +972-54-666-0933 > Email eric.kl...@greenfieldtech.net > Skype: EricLKlein > Web: http://www.greenfieldtech.net/ > > > >> Message: 5 >> Date: Tue, 4 Oct 2016 17:46:52 -0700 >> From: James Finstrom <jfinst...@gmail.com> >>

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

://www.greenfieldtech.net/ > Message: 5 > Date: Tue, 4 Oct 2016 17:46:52 -0700 > From: James Finstrom <jfinst...@gmail.com> > To: Asterisk Developers Mailing List <asterisk-dev@lists.digium.com> > Subject: [asterisk-dev] Viva Chan_Sip, may it rest in peace > Message-ID: >

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

digium.com <asterisk-dev-boun...@lists.digium.com> on behalf of Olle E. Johansson <o...@edvina.net> *Sent:* 05 October 2016 10:42 *To:* Asterisk Developers Mailing List *Cc:* Olle E Johansson *Subject:* Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace Hi! From my perspective I know

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

: Olle E Johansson Subject: Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace Hi! >From my perspective I know that maintaining a SIP stack requires *A LOT* of >effort, so I understand that a project can't maintain two of them. I suggest that a working group is created for the transition

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

Hi! From my perspective I know that maintaining a SIP stack requires *A LOT* of effort, so I understand that a project can’t maintain two of them. I suggest that a working group is created for the transition and that the first task is to compare the functionality. Last time I checked the

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

If chan_sip really has to go, then perhaps the place to start would be a marketing effort? * Why is PJSIP better? * What does PJSIP do that chan_sip does not? * Is there anything in chan_sip that PJSIP does not do, and how do you solve that? ... This can then be followed with bribery * What

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

On Wed, Oct 5, 2016 at 8:21 AM, Leandro Dardini wrote: > Your analysis of the chan_sip/PJSIP is really great and I agree with you. > Being a grey haired tech, I can check what drives similar changes in the > latest 20 years. We moved from Netware networks to TCP/IP, we moved

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

Your analysis of the chan_sip/PJSIP is really great and I agree with you. Being a grey haired tech, I can check what drives similar changes in the latest 20 years. We moved from Netware networks to TCP/IP, we moved from Windows 3.11 to Windows 95, we moved from IE to Chrome... in all these past

Re: [asterisk-dev] Viva Chan_Sip, may it rest in peace

On 10/04/2016 05:46 PM, James Finstrom wrote: > So the discussion of deprecating chan_sip came up at the devcon this year and > it caused a bit of a stir. The end result was the need for broader discussion > with a wider > audience. So let's discuss. > > Currently, Asterisk is running dual sip

[asterisk-dev] Viva Chan_Sip, may it rest in peace

So the discussion of deprecating chan_sip came up at the devcon this year and it caused a bit of a stir. The end result was the need for broader discussion with a wider audience. So let's discuss. Currently, Asterisk is running dual sip stacks. The argument is that to deprecate PJSIP there must