Package Details: freeswitch 1.6.17-2

Git Clone URL: https://aur.archlinux.org/freeswitch.git (read-only)
Package Base: freeswitch
Description: An opensource and free (libre, price) telephony system, similar to Asterisk.
Upstream URL: http://freeswitch.org/
Licenses: MPL
Conflicts: freeswitch-fixed, freeswitch-git
Provides: freeswitch
Submitter: None
Maintainer: sanerb
Last Packager: sanerb
Votes: 14
Popularity: 0.000043
First Submitted: 2009-03-02 18:40
Last Updated: 2017-06-24 00:11

Pinned Comments

sanerb commented on 2018-07-06 05:31

further confirmation per https://freeswitch.org/jira/browse/FS-11170:

"Hi.

Arch is not supported and there are no plans to support it in the future.

Feel free to reopen if you can reproduce it with Debian.

Regards,

Alex"

i'm open to suggestions on how to proceed from here. i'm guessing it's time to just delete the package, but again- open on how to proceed.

needless to say, i am very disappointed in this move from FreeSWITCH/Signalwire and their sudden shift in choosing to no longer be a part of the opensource community.

sanerb commented on 2018-05-30 15:03

so, bad news.

after opening the jira issue, a sales representative from the parent company of FreeSWITCH, Signalwire, contacted me with the following email reproduced in full:

Hi Brent,

My name is Ryan over here at FS. I'm reaching out because I was notified of the JIRA you sent in. As you know there is the open source version 1.6 of FS available yet there isn't much support available any longer. That is due to the recent change to commercialize the newest version so we can better provide support. In order to help you and your company please see the below.

We have developed an enterprise release of FS that pre-dates the open source release (on average 18-24mo) and contains commercial-only solutions. Our effort over the last 12 years to build FS has left us with an amazing base platform on which we are currently building a more professional public-facing offering in both a localized and cloud-hosted version.

The FSA program gives you access to this enterprise branch of FS and is the only version supported by the core developers. We continue to offer professional services as part of the FSA program and have been upgrading our current customers to the FSA subscription.

As a commercial customer you will have your own dedicated HipChat channel for your resources to interface with ours, an account manager and technical contact, and we are available 24x7 excluding US holidays. We have really made a big effort in dedicating our resources to our commercial customers now. The open source community and release will still exist but will only receive security updates, all patches and features will be reserved for the enterprise version.

The only additional information I would like to provide is around pricing and terms, we have done away with all hourly or project based support. All terms are either 12, 24 or 36 months and pricing carries a base fee of $5,000 per month. I would love to learn more about your deployment and can put together an official quote if its of interest.

Please let me know any additional questions, Id be happy to speak with you as well.

Thanks

Ryan

this has been confirmed via a direct freeswitch contact address.

so it looks like not only will this bug not be fixed any time soon, if ever, but it also means that they are closing shop on the opensource version.

i recommend either finding an alternative solution or forking the freeswitch project. if someone does fork it, please let me know and i would be happy to maintain an AUR package for it if desired.

Latest Comments

sanerb commented on 2018-07-06 05:31

further confirmation per https://freeswitch.org/jira/browse/FS-11170:

"Hi.

Arch is not supported and there are no plans to support it in the future.

Feel free to reopen if you can reproduce it with Debian.

Regards,

Alex"

i'm open to suggestions on how to proceed from here. i'm guessing it's time to just delete the package, but again- open on how to proceed.

needless to say, i am very disappointed in this move from FreeSWITCH/Signalwire and their sudden shift in choosing to no longer be a part of the opensource community.

sanerb commented on 2018-05-30 15:03

so, bad news.

after opening the jira issue, a sales representative from the parent company of FreeSWITCH, Signalwire, contacted me with the following email reproduced in full:

Hi Brent,

My name is Ryan over here at FS. I'm reaching out because I was notified of the JIRA you sent in. As you know there is the open source version 1.6 of FS available yet there isn't much support available any longer. That is due to the recent change to commercialize the newest version so we can better provide support. In order to help you and your company please see the below.

We have developed an enterprise release of FS that pre-dates the open source release (on average 18-24mo) and contains commercial-only solutions. Our effort over the last 12 years to build FS has left us with an amazing base platform on which we are currently building a more professional public-facing offering in both a localized and cloud-hosted version.

The FSA program gives you access to this enterprise branch of FS and is the only version supported by the core developers. We continue to offer professional services as part of the FSA program and have been upgrading our current customers to the FSA subscription.

As a commercial customer you will have your own dedicated HipChat channel for your resources to interface with ours, an account manager and technical contact, and we are available 24x7 excluding US holidays. We have really made a big effort in dedicating our resources to our commercial customers now. The open source community and release will still exist but will only receive security updates, all patches and features will be reserved for the enterprise version.

The only additional information I would like to provide is around pricing and terms, we have done away with all hourly or project based support. All terms are either 12, 24 or 36 months and pricing carries a base fee of $5,000 per month. I would love to learn more about your deployment and can put together an official quote if its of interest.

Please let me know any additional questions, Id be happy to speak with you as well.

Thanks

Ryan

this has been confirmed via a direct freeswitch contact address.

so it looks like not only will this bug not be fixed any time soon, if ever, but it also means that they are closing shop on the opensource version.

i recommend either finding an alternative solution or forking the freeswitch project. if someone does fork it, please let me know and i would be happy to maintain an AUR package for it if desired.

sanerb commented on 2018-05-21 02:18

https://freeswitch.org/jira/browse/FS-11170

sanerb commented on 2018-05-21 01:03

@TheDarkula -

it's direct upstream, it'd have to be with Freeswitch devs. i'll do that now and post the link here so you can follow progress, moment please...

TheDarkula commented on 2018-05-20 21:52

@sanerb I'm pretty sure any branch isn't building (the git main isn't compiling anymore either). You filing it with freeswitch or arch devs?

sanerb commented on 2018-05-20 04:28

so if i try building WITH openssl 1.1.x, it complains about openssl.

if i have it use openssl 1.0.x, it gives a different error:

src/switch_regex.c: In function ‘switch_regex_compile’:
src/switch_regex.c:40:9: error: returning ‘pcre *’ {aka ‘struct real_pcre8_or_16 *’} from a function with incompatible return type ‘switch_regex_t *’ {aka ‘struct real_pcre *’} [-Werror=incompatible-pointer-types]
  return pcre_compile(pattern, options, errorptr, erroroffset, tables);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:2098: libfreeswitch_la-switch_regex.lo] Error 1
make[1]: Leaving directory '/opt/dev/arch/freeswitch/src/freeswitch'
make: *** [Makefile:1414: all] Error 2

so i'll have to file a bug upstream

sanerb commented on 2018-05-19 22:47

@TheDarkula-

testing now. i'll see if i can reproduce, though yeah- dunno why it'd stop working all of a sudden. may be a gcc version inconsistency

TheDarkula commented on 2018-05-19 19:04

Build fails :( I couldn't gather why from this output though.

CC libfreeswitch_la-switch_estimators.lo src/switch_regex.c: In function ‘switch_regex_compile’: src/switch_regex.c:40:9: error: returning ‘pcre ’ {aka ‘struct real_pcre8_or_16 ’} from a function with incompatible return type ‘switch_regex_t ’ {aka ‘struct real_pcre ’} [-Werror=incompatible-pointer-types] return pcre_compile(pattern, options, errorptr, erroroffset, tables); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors distcc[4941] ERROR: compile src/switch_regex.c on localhost failed make[1]: [Makefile:2098: libfreeswitch_la-switch_regex.lo] Error 1 make[1]: Waiting for unfinished jobs.... make: *** [Makefile:1414: all] Error 2

sanerb commented on 2018-01-05 22:43

@aztec102-

i see your flagging, and 1.6.19 is indeed out. however, it fails to build:

In file included from ./crypto/include/prng.h:17:0, from ./crypto/include/crypto_kernel.h:50, from ./include/srtp.h:53, from srtp/srtp.c:46: ./crypto/include/aes_icm_ossl.h:66:20: error: field ‘ctx’ has incomplete type EVP_CIPHER_CTX ctx; ^~~ In file included from srtp/srtp.c:50:0: ./crypto/include/aes_gcm_ossl.h:58:18: error: field ‘ctx’ has incomplete type EVP_CIPHER_CTX ctx; ^~~ make[1]: [Makefile:645: srtp.lo] Error 1 make[1]: Leaving directory '/opt/dev/arch/freeswitch/src/freeswitch/libs/srtp' make: [Makefile:3931: libs/srtp/libsrtp.la] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

so i'm gonna hold off on bumping for this release if that's alright.

sanerb commented on 2017-06-24 00:13

@mal- yep, all good points. removed the extraneous env vars, and didn't bother with an export- you can set env vars at runtime (as demonstrated in the file). moved the whole configure and patching etc. to the prepare function (which, honestly, i should have done a while ago) and confirmed it still successfully builds. however, that shouldn't have any bearing on jro not being able to build for some reason. looking at it, i'd guess he's not using the right openssl version or he hit an OOM or something. hard to tell without the entire build output.

All comments