[Freeswitch-users] Enterprise/Production Quality?

Michael Avers michael at mailworks.org
Wed May 30 19:00:40 UTC 2018


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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:
> http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20180530/8dadb649/attachment.html>


More information about the FreeSWITCH-users mailing list