Package Details: freeswitch-git 1.7.0.r34100.053be38506-1

Git Clone URL: https://aur.archlinux.org/freeswitch-git.git (read-only, click to copy)
Package Base: freeswitch-git
Description: An opensource and free (libre, price) telephony system, similar to Asterisk (git version).
Upstream URL: http://freeswitch.org/
Licenses: MPL
Conflicts: freeswitch, freeswitch-fixed
Provides: freeswitch
Submitter: bougyman
Maintainer: None
Last Packager: sanerb
Votes: 12
Popularity: 0.000000
First Submitted: 2010-10-26 03:23 (UTC)
Last Updated: 2020-01-09 17:58 (UTC)

Required by (0)

Sources (13)

Latest Comments

1 2 3 4 5 6 Next › Last »

sanerb commented on 2020-03-16 21:11 (UTC)

@faddat-

did you find any others besides libtiff and ffmpeg?

faddat commented on 2020-03-13 10:55 (UTC)

It seems that the build is missing some dependencies.

I'm not sure if they're dependencies when it's running or dependencies at build time. I'll try and figure that out:

  • libtiff
  • ffmpeg

sanerb commented on 2019-04-14 16:57 (UTC)

NOTE:

Thanks to Alex from FreeSWITCH reaching out. He said that what the Signalwire sales representative has relayed to me is inaccurate and that FreeSWITCH itself remains opensource.

As such, I have done some investigation and can get it building again on Arch with gcc8.

An updated package will hit shortly.

trialreg commented on 2018-08-27 12:40 (UTC)

So i fixed the Errors as followed:

/etc/makepkg.conf:

Adding to CFLAGS="-Wno-format-truncation" Adding to CXXFLAGS="-Wno-format-truncation"

and everything is done.......

sanerb commented on 2018-05-30 15:06 (UTC)

so, bad news.

after opening a jira issue (for the versioned release package), 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 the above 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 2017-07-24 18:46 (UTC)

@mlody_salceson- no problem! it's my pleasure. :)

mlody_salceson commented on 2017-07-24 09:30 (UTC)

@sanerb- package builds cleanly and runs fine on my machine, thanks for fast response!

sanerb commented on 2017-07-23 09:12 (UTC)

@mlody_salceson- yeah, true- pushed but untested, let me know if it broke'd

mlody_salceson commented on 2017-07-23 08:36 (UTC)

Hello, I believe the necessary fixes are in the repository now and the package builds fine without recent code modifications. The new openssl can be also used.

sanerb commented on 2016-06-26 04:41 (UTC) (edited on 2017-09-01 22:45 (UTC) by sanerb)

Please note the following additions: # Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.) Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically. GPG signature "errors" are explained here: https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds Please read; it's not a bug. Thanks!

1 2 3 4 5 6 Next › Last »