* Package name    : freeswitch
  Version         : 0.0.rev2838-1
  Upstream Author : Anthony Minessale II <anthmct@yahoo.com>
* URL             : http://www.freeswitch.org/
* License         : MPL 1.1
  Programming Lang: C
  Description     : Modular Media Switching Software Library and Soft-Switch Application.

 FreeSWITCH makes it possible to build a PBX system or a VoIP switching
 platform as well as unite various technologies such as SIP, IAX2, Jingle
 (GoogleTalk), H.323, LDAP, Zeroconf, etc.
 .
 FreeSWITCH can also be used to interface with other open source PBX
 systems such as Asterisk, Bayonne, OpenPBX or YATE, and supports many
 TDM hardware.

Hello,

This is an automatic mail sent to close the ITP you have reported or
are involved with.

Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

 reopen 389591
 stop

Further comments on the work done in the bug sent to
389591@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

Greetings,

FS was on an very early stage when I made the ITP. However the software
is a lot more mature now and I've been using it, and working on this
package lately and therefore I want to reopen the ITP wnpp bug.

Regards,

About 6 months later... How is the ITP progressing ?


  Sjoerd

Hi,

FreeSWITCH v1.0 was released recently.

Is there any progress in packaging it, please? Do you have an WIP
pacakges to be tested?

I notice that upstream has a debian/ directory and they give
instructions to build a package at
<http://wiki.freeswitch.org/wiki/Installation_Guide#Debian_Linux> - has
anyone tested this to see if it is suitable for inclusion in the archive?

Regards,

Hi,

I haven´t been able to work very much on this package.

As you just said, the first stable version was recently published.

I'm still interested in working on this package for Debian, but it needs a
lot of work and unfortunely for me, time to do it is something I don't
seem to have in the short term.

If someone wants to work on the FS package, it might find an easier way
than when I first made the ITP.

FS it's a great software and deserves the best packaging.

Regards,

also sprach Juan Manuel Coronado Z. <juan.coronado@avatar.com.co> [2008.06.05.1941 +0200]:

Any news on this?

FreeSwitch is undergoing rapid development and builds cleanly on i386 / amd64 with the native debian/ directory in the SVN and tar ball.

What is needed to get this package added to unstable or testing?  The shipping stable package is 1.0.4pre9 which is plenty stable for insertion.

Thank You for Considering this Addition.

Is there any new news on this? What are the problems that prevent the
packaging?

Thanks in advance,

Jelle

The FreeSwitch tarball has some 10MB-20MB of code and more than 100MB of
extra libraries included inline. Most (if not all) of them are included
in Debian. One of them not included is openzap .

IIRC it installs under /opt (but I may be confusing it with another
program).

In short, there's some Debianization work to do.

I'm currently busy with some other things, and thus it's rather low on
my priority list.

I confirm the current freeswitch upstream package installs in /opt:

    Library directory : ................... /opt/freeswitch/lib
    Program directory : ................... /opt/freeswitch/bin
    Pkgconfig directory : ................. /opt/freeswitch/lib/pkgconfig
    HTML docs directory : ................. /opt/freeswitch/share/doc/libsndfile1-dev/html

...which is rather silly.

The upstream is now at 1.0.4:

http://www.freeswitch.org/node/184

... even though bug reports are not accepted for that version anymore
(!):

http://freeswitch.org/node/221

The latest "official" release is 1.0.5 Pre-release 10:

http://files.freeswitch.org/freeswitch-1.0.5pre10.tar.gz

but developers seem to be encouraging use of the SVN version, so an
unstable package should probably be built straight from SVN then follow
1.0.5 once it's released. 1.0.4 could also be considered as a starting
point.

I also confirm that a lot of third party libraries are builded with the
upstream distribution, which packs a hefty 63M of size for 1.0.5
snapshot available on latest.freeswitch.org. Compare this to 31M for the
1.0.4 release.

Here are the libraries in libs/

apr         esl      libdingaling  libsndfile   pcre       speex   tiff-3.8.2  xmlrpc-c
apr-util    iksemel  libedit       libteletone  portaudio  sqlite  udns        yaml
broadvoice  ilbc     libg722_1     miniupnpc    sofia-sip  srtp    unimrcp
curl        js       libnatpmp     openzap      spandsp    stfu    win32

of those, the following are duplicates of Debian, AFAIK:

apr
apr-util
curl
iksemel
libsndfile
pcre
portaudio
sofia-sip
speex
sqlite
spandsp
srtp
tiff
udns
yaml?

There may be more, others mentionned openzap but I couldn't find it
using a quick apt-cache search.

I don't think I'll have the time to work more on this, but I'm also
interested in seeing this enter the archive and volunteer for testing
in my rare spare time.

A.

http://files.freeswitch.org/downloads/libs/celt-0.7.0-1.tar.gz

I have no idea what that is or if it's already been packaged for debian.
There could also be other files downloaded and built on the fly like
this during the build, I haven't thoroughly checked.

So after a good hour or two of compiling the world, I was able to
generate debian packages out of the 1.0.5-20100101-0400 snapshot.

freeswitch can be started with:

/opt/freeswitch/bin/freeswitch -u freeswitch -c -nf

I'm not sure everything is in order. I can't get the IVR demo to work
and i'm also having trouble with conferences. But simple SIP routing,
echo tests and the nice tetris song work well.

all in all, there are a few more libraries dynamicall downloaded during
the build process, which makes the end picture look like this:

apr                  json-c-0.8.tar.gz         libsndfile     sqlite
apr-util             lame-3.97                 libteletone    srtp
broadvoice           lame-3.97.tar.gz          miniupnpc      stfu
celt-0.7.0-1         libdingaling              mpg123         tiff-3.8.2
celt-0.7.0-1.tar.gz  libedit                   mpg123.tar.gz  udns
curl                 libg722_1                 openzap        unimrcp
esl                  libmemcached-0.32         pcre           win32
iksemel              libmemcached-0.32.tar.gz  portaudio      xmlrpc-c
ilbc                 libnatpmp                 sofia-sip      yaml
js                   libshout-2.2.2            spandsp
json-c-0.8           libshout-2.2.2.tar.gz     speex

So the externally downloaded (which are probably also duplicates of
existing packages too) are:

celt-0.7.0-1, json-c-0.8, lame-3.97, libmemcached-0.32, libshout-2.2.2
and mpg123

I suspect that lame and mpg123 are also non-free.

I haven't found out how to get rid of those internal dependencies.
Everything is hidden under a pile of automake stuff in upstream's
Makefile.am. I *think* it all revolves around the CORE_LIBS variable,
but that's as far as I got.

So the way forward here would be probably to ask upstream how we're
supposed to integrate this with existing distributions that already
bundle those libraries. I can't believe we're actually support to
package it this way, there's gotta be an easier way. Namely, upstream
should provide a simpler tarball without all those libraries, and a way
to link with existing ones in the automake toolchain directly.

Then the package will need to be fixed to move out of /opt. I think that
we could start with /usr/lib/freeswitch for now, but that's not quite
standard, as we will need to split things around /usr... not sure how to
do that by looking at the Makefile.am.

Finally, non-free bits should be removed (lame and mpg123 come to mind).

So bottomline, what's missing here is this:

 1. get rid of the duplicate libraries, which involves:
   a. asking help upstream, which will imply:
   b. removing the library code from the tarball, and;
   c. link with existing libraries.
 2. move the binaries out of /opt:
   a. try to move to /usr/lib/freeswitch, then;
   b. split configuration files, libraries and binaries in proper paths
   (/etc/freeswitch, /usr/lib, /usr/bin, etc)
 3. remove non-free bits (mpg123 and lame on the radar right now)

We're not there yet, but at least that looks like a reasonable task
list...

A.

I opened an issue upstream about the build system:

http://jira.freeswitch.org/browse/FSBUILD-227

... and another one about the files location:

http://jira.freeswitch.org/browse/FSBUILD-228

We'll see how it goes.

So, I had a lenghty discussion with upstream that is summarized here:

http://jira.freeswitch.org/browse/FSBUILD-227#action_18819

Basically, things are not as bright as I thought they were. Looking back
at the original plan:

 1. get rid of the duplicate libraries, which involves:
   a. asking help upstream, which will imply:
   b. removing the library code from the tarball, and;
   c. link with existing libraries.
 2. move the binaries out of /opt:
   a. try to move to /usr/lib/freeswitch, then;
   b. split configuration files, libraries and binaries in proper paths
   (/etc/freeswitch, /usr/lib, /usr/bin, etc)
 3. remove non-free bits (mpg123 and lame on the radar right now)

2 and 3 shouldn't be a problem. 3 will be a patch local to Debian
(although a flag to disable those libraries would probably be accepted
upstream). 2 is being worked on in:

http://jira.freeswitch.org/browse/FSBUILD-220

and

http://jira.freeswitch.org/browse/FSBUILD-228

1 is much harder. The problem is that the duplicate libraries have a
very good reason for living in the FreeSWITCH tree: they fix stuff. They
have been working on those to fix crashes and performance issues all
over the place. Simply linking against system libraries (1.c) will just
not work and FreeSWITCH just crashes on startup when compiled like this
(according to MikeJ).

FreeSWITCH will probably keep on bundling patched third-party libraries
and *require* those to function properly, for the foreseeable future

This means that those libraries will have to be in some cases repackaged
to comply with the Debian Policy (section 4.13). A good example is
libiax: upstream is refusing the patches, so there's no way for those
guys to make libiax work for them and they made a fork. In the long run,
they will try to make that fork official and switch to a different
namespace so that those forks can be officially packaged by distros.

In other cases, it's just a matter of merging the patches into the
third-party libraries upstream. A good example is APR: the FS folks have
implemented fixes for threaded environments and memory allocation that
will eventually be accepted in APR, but since they break the API, that
won't happen before 1.4 is released (and which is not in Debian yet).

All that said, our roadmap here becomes:

 1. fix the duplicate code problem, which involves:
    a. namespace separation between forked and official libraries (e.g.
       libiax)
    b. upstream merge (and release!) of fixes for non-forked libs (e.g.
       APR)
    c. dropping the other libraries (e.g. sqlite)
 2. move out of /opt:
    a. create flags for various locations
    b. use those flags in the official debian package
 3. remove non-free bits

1 is followed up in http://jira.freeswitch.org/browse/FSBUILD-227

2.a is http://jira.freeswitch.org/browse/FSBUILD-220

2.b is http://jira.freeswitch.org/browse/FSBUILD-228

So there we are.

Hello,

I would really like to see Freeswitch in Debian.

Some suggestions:

1. For an initial version of the package, just create (yes duplicate)
private libraries, maybe in /usr/lib/freeswitch - it sounds like doing
this correctly will take a lot of time.

2. For a long term solution for 1, where upstream is not interested in
merging changes, maybe the Debian maintainers might be more open?

3. For /etc I suggest following the example of shorewall - leave the
conf directory empty, and allow the system administrator to copy demo
files from /usr/share/doc/freeswitch/examples if desired. I think
freeswitch configuration is sufficiently complex enough that we don't
really want to try and manage the configuration files automatically.

Thanks for your efforts,

Hello,

I have started to work on this.

There is a patch in
http://jira.freeswitch.org/browse/FSBUILD-279
that fixes several small issues.

Among other things, the source format was upgraded to 3.0 (quilt). This
allows more flexibility in patching things specifically for one distro or
another.

Upstream authors are going to keep linking statically to their own copies
of libs and want to remain able to build a .deb package this way, so this
should be taken into account when submitting changes to them. Also they do
not want to hear about bugs that cannot be reproduced with their own static
libs.

As a first step I am currently working on a debian-specific patch to remove
the dependency on the local copy of sqlite. This copy could then be
excluded from the orig tarball. The same approach can probably be used for
most of the other libraries in there.

Next I plan to implement configurable filesystem layouts in main configure
script to avoid things in /opt.

As a point of reference there is a guide to install on Debian here:

http://wiki.freeswitch.org/wiki/Installation_Guide

This is a package that would do well as a Debian package.


Proposed Package description:
Multi-Protocol Soft Switch with support for Skype, SIP, H.323 and GoogleTalk. Interfaces with other
open source PBX systems such as sipXecs, Call Weaver, Bayonne, YATE or Asterisk.

FreeSWITCH supports many advanced SIP features such as presence/BLF/SLA as well as TCP TLS and sRTP.
It also can be used as a transparent proxy with and without media in the path to act as a SBC
(session border controller) and proxy T.38 and other end to end protocols. FreeSWITCH supports both
wide and narrow band codecs

--------------------------------------------------------------------------------
Karl Schmidt                                  EMail Karl@xtronics.com
Transtronics, Inc.                              WEB http://xtronics.com
3209 West 9th Street                             Ph (785) 841-3089
Lawrence, KS 66049                              FAX (785) 841-0434

Always do right. This will gratify some people and astonish the rest. -- Mark Twain

--------------------------------------------------------------------------------

retitle 389591 RFP: freeswitch -- Modular Media Switching Software Library and Soft-Switch Application.
noowner 389591
thanks

Hi,

This is an automatic email to change the status of freeswitch back from ITP
(Intent to Package) to RFP (Request for Package), because this bug hasn't seen
any activity during the last 6 months.

If you are still interested in adopting freeswitch, please send a mail to
<control@bugs.debian.org> with:

 retitle 389591 ITP: freeswitch -- Modular Media Switching Software Library and Soft-Switch Application.
 owner 389591 !
 thanks

However, it is not recommended to keep ITP for a long time without acting on
the package, as it might cause other prospective maintainers to refrain from
packaging that software. It is also a good idea to document your progress on
this ITP from time to time, by mailing <389591@bugs.debian.org>.

Thank you for your interest in Debian,

Hi all,

Is anybody working on this?

Cheers,
Georg

We currently have a couple of FreeSWITCH Community Developers work on
getting this to a point where we can submit it...

Anyone is welcome to join us on the weekly FreeSWITCH Community Call Wed at
1PM (13:00) EST to talk about this.

Ken Rice
FreeSWITCH Stable Maintainer

Submitting Intent To Package freeswitch.

Updating subject to reflect latest status.

Hello William, Ken.

It's been more than 2 years ago when this debian bug #389591 has been
update for the last time, changing its status from RFP to ITP (request
for packaging into intention to package).

Has anything changed since that time?

I'm trying to run freeswitch on debian now, but it seems it is still in
very far from acceptable state, because of the habit of embedding 3rd
party libraries when needed or not.  I can try to clean some of that
up (for example, libtiff, pcre, ldns, curl, speex, opus, ldap - at
least - should be easy to replace with system (debian-provided) libs),
but if something is already done, maybe I may try to use that instead
of re-doing things again.

Or are there no plans to make the software within linux distributions
exist anymore, or maybe that's a bad idea somehow?

(Yes I've read recent (and not so recent) posts about embedding 3rd
party libs into the distribution).

Thanks,

/mjt

There is work to enable use of system libs for some of these things. There
are others that wont happen at all ie: sofia-sip and spandsp... Patches are
welcome and you are welcome to join us on the weekly FreeSWITCH conference
calls to discuss this with the other devs to avoid duplication of efforts.

Since Ken posted above, I have done a lot more work to make this
happen. Please note that I am not (usually) a Debian user but we do
have a mutual interest in seeing these libraries unbundled. Patches to
optionally unbundle PCRE and Speex will almost certainly be merged
soon. libedit also looks likely but I am waiting on a non-critical bug
fix from upstream. Unbundling SQLite is very controversial but heavy
duty tests are being run as I type to determine whether the upstream
version really causes memory corruption. Once this first round of
patches is out of the way, I may look at unbundling other libraries,
time permitting, but some are simply not feasible.

You can follow progress at:
http://jira.freeswitch.org/browse/FS-353

Regards,
James

You have a new fax!

Please check your fax document in the attachment to this e-mail.

Processed in:          38 seconds
Quality:               100 DPI
Date:                  Wed, 28 Oct 2015 02:28:18 +0300
File size:             118 Kb
Pages number:          13
Author:                Armando Alexander
Document name:         scanned00915925.doc

Thanks for choosing Interfax!

Hello darling, I hope that you are fine , after going through your profile On Google I had to contact you cause I have been so lonely and need someone to talk to, am Christina M Hammock from American Samoa. born 1979 , I wish to know you and hope to hear from you ,Kisses

Hello darling, I hope that you are fine , after going through your profile On Google I had to contact you cause I have been so lonely and need someone to talk to, am Christina M Hammock from American Samoa. born 1979 , I wish to know you and hope to hear from you ,Kisses

Dear Customer,

Courier was unable to deliver the parcel to you.
Shipment Label is attached to this email.

Thank you for choosing FedEx,
Jeffery Larson,
FedEx Operation Agent.

Dear Customer,

This is to confirm that your item has been shipped at February 24.

You can find more details in this e-mail attachment!

Sincerely,
Kenneth Curtis,
UPS Chief Office Manager.

Dear Customer,

We can not deliver your parcel arrived at March 07.

Please check delivery label attached!

Yours faithfully,
Julian Hines,
UPS Chief Station Manager.

Dear Customer,

This is to confirm that your item has been shipped at March 07.

Please review delivery label in attachment!

Respectfully yours,
Clyde Barker,
UPS Chief Support Manager.

Dear Customer,

Please review your parcel delivery label in the attachment!

FedEx

-----BEGIN PGP PUBLIC KEY BLOCK-----

iRKCQNv5I89taAc14nCarpiwAkXr44eaTLXsnHEsWO3jBWHt+PqPBZcK3cA1djVuow73b3zwL5LM
5ibJ07JGcKZy4fkXQnnALMQg5OcsN7AzKEUUv5U29/9fHubr/sPOcrULV5vp69vpfF/jqPtSAytr
8RkkPrXDtcaJ4XkFQj5n+drNwPn2XSfqMjf3WUw1tu9SDu0Gg6XnX1uTc80hzdskC0ctZgybQ7NR
az1WGng4hHiAPOkcwoT/DafjA3cQeZjVki21xErZFNEjpOz2+VMVp0pajmiL7fwOhEB8dt/5XaBh
qXqj/Q9Js6QvVUcH06DSEBjFzt7l0oxt/J4jC2v4Oq5bQP+v+iWdhft6g4PVgXToro3OTP1vNJwg
GPTWVY03Ah8nxMRBWzB73oNlMfZ3FXOouI2114CwxlBFFkthCWzYJiDzX1zQOIh339HRL/ObT2ej
xvXguvxJRTvfJeYcAFMWcJZgc3MWkUZtBif5TK3WgvKH3EYFjD2+o4YCdD6flFhYmuocAQ3SvEbn
WVkRtCOCPjXP4h0Vf38yntHuSfFSB3ILhlD4QzJ9fKs43Mq8caTR0MvVmR00aqItIzpK5evgAspf
wnDLdAVmx9GIzRlt5DmFWmXWCTszLSpFlQwboR5d+z7z/Kup614rtr/WwmPljhkRhF0P3hiUX4bU
6WdTzc3+Jp62XXSHaVC3nfABSNM1GdYLdwCMJxO/jNbBtRdah+ECxyz+eyjkZS533EgqwDzLpcx6
9RnjVxzQ0PMxz/8OML5wSj1ydjMtWaM8hWTPa/1ygj58EZC4HvsrfLOHwN+7B3CbcBqAAGF/q5iI
tsCairl9P73UUifipq2sOT4arPdnx8j943AFY8qY8Hs9ctLma4BW6GrQD/JVTDg7VXdmOUfKd38U
PLyhNFb3SCRJF71AB+HKduqjv4wwdooOGF3XrGqLcw3OZZQ0pnvqGM7CIGIRn4kPgaMtUKySsADK
cb/Ar2IKW1Hgf4HZ3ZPLxjOtAkCA+NJDQOHnQC5bxJUUWZC7tH/jFp6Mdj2isBlQQNx7KWo9gjHj
rNyYc0UUO06xUsbgd2flAfwUfU0IsJC4j9hmfGSClICUeXL8+MOHsY0vb+a1HiuAL8dDxQFa3jIE
bABm34a2m0AKH87Bxz45iHBlvKk5cCuWUy4ycgBb12dNBiHFBBO8cJSnm4Uled0vqNdhPb+/BNZa
ECCUx9sW6uQSVc8kf/bfBptr7c5L+gaL+ViMDZdLhv3VBp3Yrg+6Ued+MSjcjcawyXPXqXyLpI+O
FZKcaG7tUzgEjcPk2bFuptUHpMZzPTzFpE8jrRRhVg==

-----END PGP PUBLIC KEY BLOCK-----

Hi!

I did a superficial license review for the upstream code and noticed
multiple issues, for which I've filed a bug report upstream. As it is
this does not look like it could be distributed in Debian.

https://github.com/signalwire/freeswitch/issues/2092

Thanks,
Guillem