What E1/T1 hardware are you using? Libpri is maintained by a larger group. They had started to get QSIG last time I checked - they also have basic SS7 for simple ISUP calls in libss7. The stack itself is a maintenance problem, but Digium has the strength to maintain it - and in the end that is all that matters unless you want to maintain things yourself. Jan -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Helmut Kuper Sent: 9. juli 2010 14:37 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Native stacks -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jan, yes, Stefan Knoblich (stkn@freeswitch.org) is working or has worked on a new ISDN stack supporting timers for the call states. I have and using a openzap Q931StateTE stack which is basing on his early work. A added and fixed some stuff on it, so that it works quite good for basic calls on a Avaya-PRI as well as on a EWSD-PRI. The changes I did I have sent to Stefan, but got no new informations from him since a few months. Maybe he is busy, maybe things are passed to Sangoma, maybe there is no big interest in a native stack, dunno... At least I have a need for a reliable slim isdn stack supporting Q931 and if possible QSIG. It looks that libpri is the better choice as a future safe stack. But I've never tested it with FS. regards from sunny and hot germany Helmut On 09.07.2010 14:01, Jan Berger wrote:

Hi,

Creating a new thread.

If it is any interest for a native stack in FreeSWITCH we could address it later. It lacks the state-engine. Actually, last time I asked I was told someone in Germany was working on this?

But, as I looked at it recently I concluded that with Sangoma supporting their own boards, and Digium maintaining libpri for theirs - we basically have covered a majority of the E1/T1 boards that is used in here. Correct me if I am wrong.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFMNxfk4tZeNddg3dwRAqMxAJ0Vh5NnUY3HBEexz7ps8zR3GfGa6ACfTdhk Z+nSJ/7WC12tJyG/F3UxIEY= =5nmh -----END PGP SIGNATURE----- _______________________________________________ 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

because you need to SLEEP a few seconds before you answer just like you do in Asterisk. /b On Jul 9, 2010, at 8:46 AM, Phone wrote:

I am interested in this discussion of the PRI stack. We are currently using libpri with a Samgoma B601DE. Things are working fine, except for the fact that we are not receiving Caller_ID "Name" on incoming calls. In examining traces, it appears that the name comes along milliseconds later in a separate facility message, and FS is not picking this up?

I am curious if others using libpri with FS and Sangoma are getting Caller-ID "Name" delivery. Not sure if we are not configured quite right, or if there is some other libpri issue with FS.

Why are you using libpri with Sangoma boards? I am not that familiar with Sangoma boards myself, but looking at FreeTDM I would expect this to be the most optional path for Sangoma hardware? Jan -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Phone Sent: 9. juli 2010 15:46 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Native stacks I am interested in this discussion of the PRI stack. We are currently using libpri with a Samgoma B601DE. Things are working fine, except for the fact that we are not receiving Caller_ID "Name" on incoming calls. In examining traces, it appears that the name comes along milliseconds later in a separate facility message, and FS is not picking this up? I am curious if others using libpri with FS and Sangoma are getting Caller-ID "Name" delivery. Not sure if we are not configured quite right, or if there is some other libpri issue with FS. Jan Berger wrote:

What E1/T1 hardware are you using?

Libpri is maintained by a larger group. They had started to get QSIG last time I checked - they also have basic SS7 for simple ISUP calls in libss7. The stack itself is a maintenance problem, but Digium has the strength to maintain it - and in the end that is all that matters unless you want to maintain things yourself.

Jan

-----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Helmut Kuper Sent: 9. juli 2010 14:37 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Native stacks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi Jan,

yes, Stefan Knoblich (stkn@freeswitch.org) is working or has worked on a new ISDN stack supporting timers for the call states.

I have and using a openzap Q931StateTE stack which is basing on his early work. A added and fixed some stuff on it, so that it works quite good for basic calls on a Avaya-PRI as well as on a EWSD-PRI.

The changes I did I have sent to Stefan, but got no new informations from him since a few months.

Maybe he is busy, maybe things are passed to Sangoma, maybe there is no big interest in a native stack, dunno...

At least I have a need for a reliable slim isdn stack supporting Q931 and if possible QSIG.

It looks that libpri is the better choice as a future safe stack. But I've never tested it with FS.

regards from sunny and hot germany

Helmut

On 09.07.2010 14:01, Jan Berger wrote:

...

Hi,

Creating a new thread.

If it is any interest for a native stack in FreeSWITCH we could address it later. It lacks the state-engine. Actually, last time I asked I was told someone in Germany was working on this?

But, as I looked at it recently I concluded that with Sangoma supporting their own boards, and Digium maintaining libpri for theirs - we basically have covered a majority of the E1/T1 boards that is used in here. Correct

me

...

if I am wrong.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)

iD8DBQFMNxfk4tZeNddg3dwRAqMxAJ0Vh5NnUY3HBEexz7ps8zR3GfGa6ACfTdhk Z+nSJ/7WC12tJyG/F3UxIEY= =5nmh -----END PGP SIGNATURE-----

_______________________________________________ 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

_______________________________________________ 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

_______________________________________________ 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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jan, sounds great to me SS7 and QSIG ... would be too nice. I use Sangoma A101 and A104d. regards On 09.07.2010 15:16, Jan Berger wrote:

What E1/T1 hardware are you using?

Libpri is maintained by a larger group. They had started to get QSIG last time I checked - they also have basic SS7 for simple ISUP calls in libss7. The stack itself is a maintenance problem, but Digium has the strength to maintain it - and in the end that is all that matters unless you want to maintain things yourself.

Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)

iD8DBQFMNzo/4tZeNddg3dwRAnS2AJkBBNLQMY56ofyoLdlbbLvyJzoQfgCdGO1j 4wRzrKPmE0cud5Kg5SR/GPI= =yZ8N -----END PGP SIGNATURE-----

Hi, After reading through this email, I was looking up for inconsistencies between GPL and MPL, and have come across this link: http://www.gnu.org/licenses/license-list.html#MPL <http://www.gnu.org/licenses/license-list.html#MPL>While that does not make MPL compatible with GPL, but it does allow for some sort of progress, if needed. Regards HASSAN On Fri, Jul 9, 2010 at 21:18, Anthony Minessale <anthony.minessale@gmail.com

wrote:

I want the native stack to succeed because our goal was to have an open source BSD licensed free ISDN stack so we can put an end to people selling it for ungodly fees.

The libpri is fine to use if a user assembles it himself but ultimately it's GPL and there is a grey-area license conflict with using with FS. Technically OpenZAP/FreeTDM is BSD and compat with libpri but according to the greedy GPL, when you load it the GPL infects the whole code and makes it also GPL. FS is MPL and is happily compat with OpenZAP/FreeTDM but there is a philosophical debate as to if the BSD lib in the middle that completely abstracts the 2 entities, protects FS from the GPL

FreeTDM is still OpenZAP, just with another name. Sangoma is only working on their own modules for FreeTDM and the API as a whole still supports everything OpenZAP does. I think stkn will merge his stack back into FreeTDM and it can continue to be developed for those who don't have Sangoma cards.

On Fri, Jul 9, 2010 at 10:03 AM, Helmut Kuper <helmut.kuper@ewetel.de>wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi Jan,

sounds great to me SS7 and QSIG ... would be too nice.

I use Sangoma A101 and A104d.

regards

On 09.07.2010 15:16, Jan Berger wrote:

...

What E1/T1 hardware are you using?

Libpri is maintained by a larger group. They had started to get QSIG last time I checked - they also have basic SS7 for simple ISUP calls in libss7. The stack itself is a maintenance problem, but Digium has the strength to maintain it - and in the end that is all that matters unless you want to maintain things yourself.

Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)

iD8DBQFMNzo/4tZeNddg3dwRAnS2AJkBBNLQMY56ofyoLdlbbLvyJzoQfgCdGO1j 4wRzrKPmE0cud5Kg5SR/GPI= =yZ8N -----END PGP SIGNATURE-----

_______________________________________________ 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

-- Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900

_______________________________________________ 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 GPL is the license that would require change not the MPL. (there already is such a change called LGPL btw) The GPL says if you link to anything GPL, your whole program and anything that links to it is GPL. Once that happens all your rights to use the software for business are gone unless you are the sole owner of the code. Therefore it's not possible for FreeSWITCH to be compatible with the GPL. If you look at the obvious use case: someone takes libGPLgoodies and wraps it in a 10 line exe and sells it for $20, its construed as unfair. Probably true...... so the GPL narrow-mindedly focuses on this paradigm. Now turn the tables and imagine MongoAPP that does all kinds of different functions that has mod_GPL_Hello_World.so that just prints hello world on the console. That too would cause all of MongoAPP to become GPL which is enough to make you spit out your drink in disbelief. The only way around it is to avoid GPL software which is our common practice and has worked well for us thus far. We just choose not to get involved with it due to difference of opinion. On Tue, Jul 27, 2010 at 12:40 PM, Mathieu Parent <math.parent@gmail.com>wrote:

On Fri, Jul 9, 2010 at 5:18 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:

...

I want the native stack to succeed because our goal was to have an open source BSD licensed free ISDN stack so we can put an end to people selling it for ungodly fees. The libpri is fine to use if a user assembles it himself but ultimately it's GPL and there is a grey-area license conflict with using with FS. Technically OpenZAP/FreeTDM is BSD and compat with libpri but according to the greedy GPL, when you load it the GPL infects the whole code and makes it also GPL. FS is MPL and is happily compat with OpenZAP/FreeTDM but there is a philosophical debate as to if the BSD lib in the middle that completely abstracts the 2 entities, protects FS from the GPL FreeTDM is still OpenZAP, just with another name. Sangoma is only working on their own modules for FreeTDM and the API as a whole still supports everything OpenZAP does. I think stkn will merge his stack back into FreeTDM and it can continue to be developed for those who don't have Sangoma cards.

Next MPL version might be compatible with GPL. It is in the spec list http://mpl.mozilla.org/scope/ . As MPL 2.0 is scheduled for fall 2010, we will know more then. Also FreeSWITCH is MPL 1.1 and not "MPL 1.1 or later" so it will need to be relicensed.

Talking about relicensing, why not relicense FreeSWITCH under MPL/LGPL/GPL as Mozilla does, and for the same reasons (see http://www-archive.mozilla.org/MPL/relicensing-faq.html#why-relicensing for explanation)?

Regards

Mathieu Parent

_______________________________________________ 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

-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900

My position has already been stated. On Tue, Jul 27, 2010 at 4:26 PM, Mathieu Parent <math.parent@gmail.com>wrote:

I understand your position. IANAL but I want to go a bit deeper on some points.

On Tue, Jul 27, 2010 at 7:56 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:

...

The GPL is the license that would require change not the MPL. (there already is such a change called LGPL btw)

As Nyamul pointed, MPL "has some complex restrictions that make it incompatible with the GNU GPL". It means that, according to FSF, you can't link a module under current MPL 1.1 and another under GPL 2 or 3. This part may be solved in MPL 2.0.

...

The GPL says if you link to anything GPL, your whole program and anything that links to it is GPL. Once that happens all your rights to use the software for business are gone unless you are the sole owner of the code.

Not exactly. The whole program can't be relicensed without agreement of the copyright holders. Until this, you cannot link with GPL-code. Or more precisely, you cannot redistribute your code when linked against GPL-code. This means that you can link FreeSWITCH with a GPL-ed lib *at home* without license problem.

...

Therefore it's not possible for FreeSWITCH to be compatible with the GPL. If you look at the obvious use case: someone takes libGPLgoodies and wraps it in a 10 line exe and sells it for $20, its construed as unfair. Probably true...... so the GPL narrow-mindedly focuses on this paradigm.

But someone can still sell GPL code for $20. GPL doesn't forbid selling.

...

Now turn the tables and imagine MongoAPP that does all kinds of different functions that has mod_GPL_Hello_World.so that just prints hello world on the console. That too would cause all of MongoAPP to become GPL which is enough to make you spit out your drink in disbelief.

By using MPL/GPL/LGPL triple license as Mozilla does, you will allow somebody (or yourself) to propose a bundle with FreeSWITCH and some GPL libs. Currently this is not possible.

Mozilla FAQ ( http://www-archive.mozilla.org/MPL/relicensing-faq.html#why-lgpl) explains this precisely. Currently solutions can be build with FreeSWITCH under either MPL or proprietary license. With trilicensing, you add two more possibilities which give access to the tons of GPL softwares.

For example, If I want to create a FS module that uses openchange to access toM$ Exchange servers to read calendar, I can't because openchange is licensed, as samba4, under GPL3 (Website: http://www.openchange.org/). Same if I want to create a TTS mod_espeak (GPL2+).

...

The only way around it is to avoid GPL software which is our common practice and has worked well for us thus far. We just choose not to get involved with it due to difference of opinion.

OK.

Regards

Mathieu Parent

_______________________________________________ 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

-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900

It is still my plan to merge the work From stkn back into freetdm, but time has not permitted as of yet to get this done. Mike On Jul 9, 2010, at 11:18 AM, Anthony Minessale wrote:

I want the native stack to succeed because our goal was to have an open source BSD licensed free ISDN stack so we can put an end to people selling it for ungodly fees.

The libpri is fine to use if a user assembles it himself but ultimately it's GPL and there is a grey-area license conflict with using with FS. Technically OpenZAP/FreeTDM is BSD and compat with libpri but according to the greedy GPL, when you load it the GPL infects the whole code and makes it also GPL. FS is MPL and is happily compat with OpenZAP/FreeTDM but there is a philosophical debate as to if the BSD lib in the middle that completely abstracts the 2 entities, protects FS from the GPL

FreeTDM is still OpenZAP, just with another name. Sangoma is only working on their own modules for FreeTDM and the API as a whole still supports everything OpenZAP does. I think stkn will merge his stack back into FreeTDM and it can continue to be developed for those who don't have Sangoma cards.

http://oss.axsentis.de/gitweb/?p=libisdn.git;a=summary http://oss.axsentis.de/gitweb/?p=ftmod_isdn.git;a=summary Mike On Aug 15, 2010, at 8:33 PM, Jan Berger wrote:

Has he actually done anything? Can I find the code somethere?

Jan

-----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris Sent: 16. august 2010 01:24 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Native stacks

It is still my plan to merge the work From stkn back into freetdm, but time has not permitted as of yet to get this done.

Mike