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?