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?
While your issues definitely should be troubleshooted to find the cause of your problem, I will just answer your question if anyone has different experience, I have been using freeswitch in production for over 10 years with no major issues even with much higher load, and so have many others. On Wed, 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
Hi, Are you using wss or verto for webrtc endpoints? For my experience FS is very stable in production environment, but the use of webrtc with sip (wss) introduces/causes random lock issues, i've open issues about this problem: https://freeswitch.org/jira/browse/FS-10474 https://freeswitch.org/jira/browse/FS-10638 https://freeswitch.org/jira/browse/FS-10676 https://freeswitch.org/jira/browse/FS-10721 The best solution for webrtc is to use verto, and leave sofia for sip only, that's how i managed to solve all the issues... i never figure out the source of the problem only that is cause by wss endpoints. On 05/30/2018 05:29 PM, Abaci B wrote:
While your issues definitely should be troubleshooted to find the cause of your problem, I will just answer your question if anyone has different experience, I have been using freeswitch in production for over 10 years with no major issues even with much higher load, and so have many others.
On Wed, May 30, 2018 at 10:45 AM, Geoff Mina <gmina@connectfirst.com <mailto: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 <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com>
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org <http://confluence.freeswitch.org> http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org
_________________________________________________________________________ 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
-- Saludos / Regards / Cumprimentos Anónio Silva
Hello Geoff and Freeswitch-users: Currently I have a Freeswitch server in development mode on Amazon EC2 instance and another, working in production, as a physical machine. Both are mounted on Linux Debian 8 - 64 bits and the Freeswitch version is 1.6.18 64bit in development and 1.6.19 64bit in production. Also I’ve another Freeswitch servers in development and production, but this servers only work with TCP/UDP, no WSS and they haven’t this trouble. These systems keep Sip and WSS-SipJs clients connected through their internal context. In both cases, they are connected to Proxies where they register and take calls with other external carriers. All user accounts, connection information with proxies, etc. they are maintained through externals Mysql databases, (different for each system). Everything works correctly but, on occasion, any of the Freeswitch systems working with WSS stops working without, apparently, offering information about the reason. This occurs every 2-3 weeks and it can happen to one of the two servers, the state that keep in this case the following: The Freeswitch instance remains up. The console maintains the connection and accepts the input of commands. The internal and external interface appear to be up when the sofia status statement is executed. There is connectivity with the MySQL databases. No alerts or error messages are displayed in the console. THERE ARE NO REGISTERED USERS, when executing the sofia status profile internal reg command, 0 registered users appear. When executing the sofia status, I can’t see the internal profile but I can see the others profiles. When executing the sofia status profile internal command, usually, the CLI is bloked and I need to exit with Ctrl+C. Through netstat, it can be seen that the ports and protocols are kept correctly raised. I have compared netstat results with the affected and functioning instances and there are no differences. Obtaining traces, for example, with ngrep, it is observed that Freeswitch does not respond to requests for registration or invites made by SIP clients on the intenal interface. It receives the requests correctly but does not return a response. SIP and WSS clients can not register either. Obtaining traces on the port of the external interface, it is observed that Freeswitch sends registration requests to the proxy, which are answered by this with the typical unauthorized message and information to do the digest proces, which is not managed by Freeswitch and this returns to send new registers requests without negotiating digest of the previous answers. If one of the interfaces is restarted, for example, with the sofia profile internal restart command, on some occasions the console remains dead without activity and, in others, the sentence is executed and ended correctly, but when consulting the state of the interfaces with, for example, sofia status, the internal context has disappeared. It also happens with the external context. The only way to get the Freeswitch instance working correctly is to perform a reset of this, using the systemctl stop freeswitch / systemctl star freeswitch linux command, for example. After raising the bank again, everything goes back to work properly, the registration is made against the proxies and the clients Sip and Wss re-register correctly and the calls are processed again. Checking the log of logs, (/usr/local/freeswitch/logs/freeswitch.log), there are no warnings, errors or anything that shows clues about the reason for the fall. Simply repeat attempts to register clients and against the proxy. After restarting the instance and running, the time until the next incident is repeated is random. It can be a few hours or weeks. I have no way to reproduce it or induce the fault. If you think of any reason that might lead Freeswitch to have this behavior or if you have suffered similar incidents, please, I would be very grateful if you can throw some light on me. Best Regards. Miguel J. Lopez. De: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] En nombre de Abaci B Enviado el: miércoles, 30 de mayo de 2018 17:30 Para: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Asunto: Re: [Freeswitch-users] Enterprise/Production Quality? While your issues definitely should be troubleshooted to find the cause of your problem, I will just answer your question if anyone has different experience, I have been using freeswitch in production for over 10 years with no major issues even with much higher load, and so have many others. On Wed, May 30, 2018 at 10:45 AM, Geoff Mina <gmina@connectfirst.com <mailto: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 <mailto: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 <mailto: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 --- El software de antivirus Avast ha analizado este correo electrónico en busca de virus. https://www.avast.com/antivirus
see my previous response in this thread.
On May 30, 2018, at 12:46 PM, Miguel Jesús López Valverde <mjlopez@smartic.es> wrote:
Hello Geoff and Freeswitch-users:
Currently I have a Freeswitch server in development mode on Amazon EC2 instance and another, working in production, as a physical machine. Both are mounted on Linux Debian 8 - 64 bits and the Freeswitch version is 1.6.18 64bit in development and 1.6.19 64bit in production.
Also I’ve another Freeswitch servers in development and production, but this servers only work with TCP/UDP, no WSS and they haven’t this trouble.
These systems keep Sip and WSS-SipJs clients connected through their internal context. In both cases, they are connected to Proxies where they register and take calls with other external carriers.
All user accounts, connection information with proxies, etc. they are maintained through externals Mysql databases, (different for each system).
Everything works correctly but, on occasion, any of the Freeswitch systems working with WSS stops working without, apparently, offering information about the reason. This occurs every 2-3 weeks and it can happen to one of the two servers, the state that keep in this case the following:
Geoff- I believe this issue is fixed in https://freeswitch.org/jira/browse/FS-10762 <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?
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
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 <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 <mailto: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?
On Wed, 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
Where is this recommendation posted? The Freeswitch 1.8 textbook seems to imply they are equally usable.
As a Freeswitch implementer I agree the optics of this aren't very good. I'm happy to treat FS as a commercial offering and evaluate it's value on that basis, if that's what it has become. But touting it as OSS then not supporting key bug fixes to the OSS community isn't really a good look.
I'd like to hear how the organization supporting the Advantage program views the legality of distributing patches to MPL code to program partners but not the community. Isn't that one of the core properties of the MPL license? Sure, you can link non-MPL software to it if you create a separate commercial module from whole cloth. But if you modify MPL code with the intent to distribute outside the boundaries of your organization, my understanding is that you must freely publish those modifications to all. Dual licensing software is a simple matter if you own 100% copyright to the code. You absolutely have the right to do that ( see Qt's GPL vs commercial license ). But to re-license code that is a collection of patches from multiple authors, you need the consent from all of those that have contributed before changing that license. A lot of projects have gone through the pain of re-licensing code and it involved reaching out to all contributing parties and gaining their consent ( search the mailing lists of the Xen project or Wine for examples ). All that being said, I completely understand the need for a commercial arm of a software project. You can't feed your family on good will. I don't think anyone would argue that it shouldn't be done. But a typical model for this involves additional commercial module offerings and commercial support offerings. Can you help us understand how your early release program works with respect to code code that's licensed under the MPL? Thanks, -Matthew On 5/30/2018 12:28 PM, Tom Hartnett wrote:
On Wed, May 30, 2018 at 12:35 PM, Michael Jerris <mike@jerris.com <mailto: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
Where is this recommendation posted? The Freeswitch 1.8 textbook seems to imply they are equally usable.
As a Freeswitch implementer I agree the optics of this aren't very good. I'm happy to treat FS as a commercial offering and evaluate it's value on that basis, if that's what it has become. But touting it as OSS then not supporting key bug fixes to the OSS community isn't really a good look.
_________________________________________________________________________ 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
Hi Mike, how can we, as users of the project, tell what is included/fixed in Freeswitch Advantage that isn't generally available to the public? The splash page on your website doesn't really give much detail at all, not even pricing. Mike On Wed, May 30, 2018, at 9:35 AM, Michael Jerris 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
Things marked as fixed in 1.8.0 are not in a 1.6 release. Some of those fixes are in the master branch but not yet in a public release.
On May 30, 2018, at 2:10 PM, Michael Avers <michael@mailworks.org> wrote:
Hi Mike, how can we, as users of the project, tell what is included/fixed in Freeswitch Advantage that isn't generally available to the public? The splash page on your website doesn't really give much detail at all, not even pricing.
Mike
On Wed, May 30, 2018, at 9:35 AM, Michael Jerris 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 <mailto: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 <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 <mailto: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?
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<mailto: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<mailto: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<mailto: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<mailto: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.”
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
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
participants (10)
-
Abaci B
-
antonio
-
Geoff Mina
-
Matteo
-
Matthew Grooms
-
Michael Avers
-
Michael Jerris
-
Miguel Jesús López Valverde
-
Tom Hartnett
-
William Simon