Hi, Not sure if it is related, but when I tried to look at the commits correcting a bug I was interested on (https://freeswitch.org/jira/browse/FS-10904), I got the message "You don't have access to view all related commits. Please contact your administrator." Looks like the reporter got the same message too. screenshot: https://imgur.com/y29ysyT Best Regards, -- Vallimamod Abdullah vma@sip.solutions linkedin.com/in/vallimamod .
On 26 Jun 2018, at 11:19, David Villasmil <david.villasmil.work@gmail.com> wrote:
Hello all, Is this true??? Bug fixes aren't available for the general open source community for EIGHTEEN MONTHS??? This seems REALLY wrong to me... I'm pretty sure there are better ways of making money from freeSWITCH...
Now I'm very concerned, and probably a lot of people will, if/when they find out about this...
David
On Tue, Jun 26, 2018, 02:57 Matteo via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> wrote:
---------- Forwarded message ---------- From: Matteo <mbrancaleoni@voismart.it> To: freeswitch-users <freeswitch-users@lists.freeswitch.org> Cc: Bcc: Date: Wed, 20 Jun 2018 11:50:26 +0200 (CEST) Subject: Re: [Freeswitch-users] Enterprise/Production Quality? Well I agree too.
Since the introduction of the FSA (term not cited anywhere on website), we started evaluating a subscription.
But a lot of things are really, really vague and keeping us away:
* What is in the FSA? What we get for the money? * What about prices? * What is the release cycle? When things gets pushed into the OSS version? * What is the FSA? please add a blog post to clarify this shift in policy and how things "works" from now on.
Basically there's no communication about that and everything appears really vague.
Other OSS projects with similar policy have a very clear release path, what is in, what is not, when new things will appear in OSS and so on.
And then a suggestion: Why not offer a "basic" FSA with just access to latest git? And not provide dedicated support, but use traditional channels?
This should be cheaper and interesting for companies that are autonomous into investigating and fixing issues by themselves.
And about bugfixes... well I agree with others... they should be released because affects something that's already out.
Not doing that may backfire because the OSS product may be perceive buggy (especially if using latest features which may not be debugged properly yet)
Keep in mind that from a company perspective, if the things are free you can be loose on how the project is handled, because is free after all. But if you want to get payed (which is completely natural and needed to keep things go on), you must be very clear and communicative on what you give for the price.
Just my 2 cents.
Matteo
----- Il 30-mag-18, alle 21:00, Michael Avers michael@mailworks.org ha scritto:
I agree. I think they are doing it wrong. I obviously believe they need to make money and get paid for their work, I have no problem with that at all, and my company has bought quite a few licenses of their commercial modules and we attend Cluecon every other year. So we have no problem paying but we need to know what we are paying FOR.
This kind of vague state of things where you just don't know if bugs are now going to be fixed for everyone or just for the privileged ones is not a good path to go down.
Bug fixes really should be made available to everyone (assuming they are in previously public modules, of course).
The Freeswitch team should focus their efforts on creating commercial modules, ready-made apps and setups, pro versions of older modules, say enhanced mod_callcenter or whatever. Things like that. But to tell someone to get a premium subscription just to get a bug fixed... that's simply wrong.
Just my 2 cents
Mike
On Wed, May 30, 2018, at 11:37 AM, William Simon wrote:
I thought stability fixes were going to be included in the open source release whereas new features are covered under FSA release cycle. What I am seeing here is unfortunate. Open source users should just accept instability for the 18-month release cycle?
On May 30, 2018, at 12:35 PM, Michael Jerris < mike@jerris.com > wrote:
Michael-
This is a specific bug that I know we have fixed. We spent months of work tracking it down, I am very familiar with the issue. This issue is not at all with verto, and is specifically with the sip secure web socket support. We have never recommended the use of sip web socket support for webrtc, we think that verto is typically a better solution, and is more stable.
Mike
On May 30, 2018, at 12:16 PM, Michael Avers < michael@mailworks.org > wrote:
LOL... The issue he describes can be due to several different reasons. I don't even think we have enough information at this point to determine it let alone narrow it down to one specific bug fix.
Is saying "Oh this is fixed in our paid product" going to be the standard moving forward?
In any case, a response such as this basically tells potential Verto users that they shouldn't bother because it's going to break at 150 concurrent users anyway.
Mike
On Wed, May 30, 2018, at 8:58 AM, Michael Jerris wrote:
Geoff-
I believe this issue is fixed in https://freeswitch.org/jira/browse/FS-10762 which is available to FSA customers.
Mike
On May 30, 2018, at 10:45 AM, Geoff Mina < gmina@connectfirst.com > wrote:
Is anyone out there actually using FS successfully in an enterprise environment?
We have deployed a handful of servers in an extremely simple configuration to allow standard SIP infrastructure to communicate with WebRTC clients.
We run ~150 concurrent users per host and we can’t go a week without something in the core of Sofia failing. We have seen hung profiles that simply don’t respond to REGISTER requests (tried every suggested tweak to no avail) as well as seeing FS hang every call in a RINGING state without actually ringing the end client.
These seem like pretty fundamental components we are struggling with. Our use case seems quite simple - yet the software (1.6.19) seems like it has never even seen a production deployment.
Anyone out there have a drastically different experience?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
“The information transmitted is intended only for the person or entity to which it is addressed and may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer.” _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com
---------- Forwarded message ---------- From: Matteo via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> To: freeswitch-users <freeswitch-users@lists.freeswitch.org> Cc: Bcc: Date: Mon, 25 Jun 2018 17:57:02 -0700 (PDT) Subject: Re: [Freeswitch-users] Enterprise/Production Quality? _________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com _________________________________________________________________________ Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com