Menu
▾
▴
iaxclient-devel — Development Discussion List
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(3) |
Mar
(16) |
Apr
(11) |
May
(3) |
Jun
(109) |
Jul
(70) |
Aug
(22) |
Sep
(19) |
Oct
(4) |
Nov
(25) |
Dec
(46) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(68) |
Feb
(52) |
Mar
(54) |
Apr
(57) |
May
(13) |
Jun
(15) |
Jul
(16) |
Aug
(3) |
Sep
(43) |
Oct
(95) |
Nov
(106) |
Dec
(142) |
| 2005 |
Jan
(62) |
Feb
(190) |
Mar
(75) |
Apr
(117) |
May
(123) |
Jun
(64) |
Jul
(122) |
Aug
(95) |
Sep
(63) |
Oct
(102) |
Nov
(99) |
Dec
(85) |
| 2006 |
Jan
(59) |
Feb
(64) |
Mar
(138) |
Apr
(82) |
May
(62) |
Jun
(62) |
Jul
(72) |
Aug
(50) |
Sep
(21) |
Oct
(95) |
Nov
(95) |
Dec
(29) |
| 2007 |
Jan
(26) |
Feb
(36) |
Mar
(45) |
Apr
(12) |
May
(53) |
Jun
(38) |
Jul
(19) |
Aug
(87) |
Sep
(63) |
Oct
(272) |
Nov
(102) |
Dec
(63) |
| 2008 |
Jan
(54) |
Feb
(19) |
Mar
(84) |
Apr
(111) |
May
(17) |
Jun
(26) |
Jul
(18) |
Aug
(10) |
Sep
(14) |
Oct
(9) |
Nov
(4) |
Dec
(12) |
| 2009 |
Jan
(5) |
Feb
(7) |
Mar
(4) |
Apr
(8) |
May
(4) |
Jun
(7) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(6) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Steven S. <ss...@so...> - 2004-03-11 16:31:19
|
Amit, 1. You won't hear the tones (ring, busy, reorder, dial tone, etc.) when running in the VB IDE. The IDE does not allow the dynamic loading of resources, which prevents the tones (stored as resource items) from loading/playing. This will not impact the ability of the tones to play = when you compile the code. 2. Please do not send anything else telling me how urgent and desperate this is. I do IAX Phone for fun and as a learning tool (for myself and = for others). If you want _urgent_ help, please contact me off-list and we = can make arrangements for you to purchase a license and/or support time. Regards, Steven Steven Sokol Owner/Manager Sokol & Associates, LLC Phone:=A0 816.822.1807 IaxTel: 700.613.9004 Web:=A0=A0=A0 http://www.sokol-associates.com ________________________________________ From: iax...@li... [mailto:iax...@li...] On Behalf Of amit chowrasia Sent: Thursday, March 11, 2004 9:54 AM To: iax...@li... Subject: [Iaxclient-devel] no sound when executing the iax phone when i am executing the iax phone source code and trying to make calls i = am unable to listen any ringing tone =A0i have already registered in registry the dx8vb.dll file for the = sound=20 pls help me out deep trouble need help urgent my=A0os is win2k = professional --=20 ___________________________________________________________ Sign-up for Ads Free at Mail.com http://www.mail.com/?sr=3Dsignup ------------------------------------------------------- This SF.Net = email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by = Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli= ck _______________________________________________ Iaxclient-devel mailing = list Iax...@li... https://lists.sourceforge.net/lists/listinfo/iaxclient-devel=20 |
|
From: amit c. <ami...@pr...> - 2004-03-11 16:04:39
|
<P>when i am executing the iax phone source code and trying to make calls i am unable to listen any ringing tone</P> <P> i have already registered in registry the dx8vb.dll file for the sound </P> <P>pls help me out deep trouble need help urgent my os is win2k professional</P><BR> -- <p>___________________________________________________________<br>Sign-up for Ads Free at Mail.com<br> <a href="http://mail01.mail.com/scripts/payment/adtracking.cgi?bannercode=adsfreejump01" target="_blank">http://www.mail.com/?sr=signup</a></p> |
|
From: Steven S. <ss...@so...> - 2004-03-10 18:33:58
|
Sorry for replying to this via the list. I tried to respond directly to Amit, but his mail server rejected my message because it uses that bloody SORBS spam database which refuses to accept any mail from hosts on dynamic IP addresses (such as mine). [Sorry for that totally Off Topic moment]. >> REPLY START HERE If you are tying to compile and execute IAX Phone from anywhere other than the default installation directory, you will need to copy the wiax2.dll file from the install directory (C:\Program Files\Sokol & Associates\IaxPhone) to your computers Winnt\System32 folder (i.e. the System folder). You should also copy libsndfile.dll, wiax1.dll and all of the EUsb*.dll files to the system folder. If you are trying to develop using the IAX Phone source code, you will need to download the win.tlb file that came with Hard Core Visual Basic. It can be downloaded here: http://www.themandelbrotset.com/Technical/Typelib.asp You need to have the ANSI version (ASCII) of the type library installed. NOTE: YOU CANNOT USE THE WIAX2.DLL FILE FROM Dan Toma's DIAX. IT IS NOT COMPATIBLE WITH IAX PHONE. YOU MUST USE THE VERSION OF WIAX2.DLL THAT INSTALLS WITH IAXPHONE. Regards, Steven Steven Sokol Owner/Manager Sokol & Associates, LLC Phone: 816.822.1807 IaxTel: 700.613.9004 Web: http://www.sokol-associates.com _____ From: iax...@li... [mailto:iax...@li...] On Behalf Of amit chowrasia Sent: Wednesday, March 10, 2004 9:06 AM To: iax...@li... Subject: [Iaxclient-devel] wiax2.dll loading error in running the source code when i am executing the source code of iax phone its show thats wiax2.dll file not found and run time error 53 my operating system is windows 2000 professional i have downloaded update wiax2.dll file but still not working. can anybody help me its urgent |
|
From: amit c. <ami...@pr...> - 2004-03-10 15:16:00
|
<P><BR>when i am executing the source code of iax phone its show thats wiax2.dll file not found and run time error 53</P> <P>my operating system is windows 2000 professional</P> <P>i have downloaded update wiax2.dll file but still not working.</P> <P>can anybody help me its urgent</P><BR> -- <p>___________________________________________________________<br>Sign-up for Ads Free at Mail.com<br> <a href="http://mail01.mail.com/scripts/payment/adtracking.cgi?bannercode=adsfreejump01" target="_blank">http://www.mail.com/?sr=signup</a></p> |
|
From: Olivier K. <ka...@ka...> - 2004-03-10 11:25:46
|
Oups ... responding to my self: I'm using the latest beta for Firefox, and download seems broken.. many apologizes Kalou On Wed, 10 Mar 2004, Olivier Kaloudoff wrote: >Hi ! > > > I just discovered IaxComm, which seems to be >a really cool voip app; I choose iaxcomm because it has >Mac OSX support, thank you for this. > > I'd be glad to download it from your page, unfortunatelly >all download links are broken, and no files have been published >on the sourceforge "Files" section. > > Let me know when links are fixed :) > > >Best Regards, > > >Olivier Kaloudoff > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >Iaxclient-devel mailing list >Iax...@li... >https://lists.sourceforge.net/lists/listinfo/iaxclient-devel > -- Olivier Kaloudoff --- |
|
From: Olivier K. <ka...@ka...> - 2004-03-10 11:20:53
|
Hi ! I just discovered IaxComm, which seems to be a really cool voip app; I choose iaxcomm because it has Mac OSX support, thank you for this. I'd be glad to download it from your page, unfortunatelly all download links are broken, and no files have been published on the sourceforge "Files" section. Let me know when links are fixed :) Best Regards, Olivier Kaloudoff |
|
From: Steve K. <st...@st...> - 2004-03-09 15:30:40
|
Michael Van Donselaar wrote: >I'm sure that most everyone here also follows asterisk-dev and asterisk-users, >so you probably saw my response to Matt's question about where to ask questions >about DIAX and iaxComm. > >I may have spoken out of turn. While I want to hear of any user problems with >iaxComm, DIAX or IAX Phone, maybe everyone else doesn't. > >My thinking was that while a problem with one of the iaxclient based softphones >might not be related to the library, we all can benefit from seeing how a >problem is solved in another softphone. > >Does anyone have any objection to pointing users here? Or should we create >iaxclient-users? > I think that we can have questions about all iaxclient-applications here iaxclient lists, whether they're front-end or library questions [especially since users often won't know]. I'm certainly interested in what people are doing with iaxclient. If there ends up with too much traffic for people, we can make a new -users list for direct user-support issues. Personally, I expect to be subscribed to both lists, and get them in my INBOX (as opposed to the asterisk lists, which get put into a different mailbox which I don't read as often). However, if people who are on this list would rather make two lists now, I'd be happy to go and do that. -SteveK |
|
From: Michael V. D. <mv...@va...> - 2004-03-09 15:19:08
|
I'm sure that most everyone here also follows asterisk-dev and = asterisk-users, so you probably saw my response to Matt's question about where to ask = questions about DIAX and iaxComm. I may have spoken out of turn. While I want to hear of any user problems= with iaxComm, DIAX or IAX Phone, maybe everyone else doesn't. My thinking was that while a problem with one of the iaxclient based = softphones might not be related to the library, we all can benefit from seeing how a problem is solved in another softphone. Does anyone have any objection to pointing users here? Or should we = create iaxclient-users? |
|
From: Mark S. <mar...@di...> - 2004-03-08 00:51:54
|
> After reading this, I was thinking that asterisk with iLBC (which is > currently built by default, right?) is no longer under the GPL itself, > and then cannot actually be linked with other GPL code, unless the > author of the other GPL code grants the same exception [in which case > it's no longer actually GPL]. If you do not use iLBC, G.729, or OpenH323, you can link with other GPL code, but we cannot accept GPL code into the Asterisk code base for this very reason. > I almost reconsidered that, because these exceptions make the license > less restrictive. You can always link GPL software against software > with less restrictive licenses. However, in order to link asterisk + > iLBC + some GPL software, you would still then be linking the GPL > module with iLBC, which you can't do, because then you'd be linking the > GPL module with something more restrictive. Precisely. > Licenses give me headaches. I guess it would be a lot simpler if there > was just Modified-BSD, GPL, and LGPL, instead of the multitude of > incompatible free-software licenses we have today. Different licenses have different goals, so to some degree that is going to be a problem. The GPL has a lot of strengths and is very popular to use, but strict GPL does not permit us to use some legacy technologies (e.g. G.729, iLBC etc) that need methods of being supported. Mark |
|
From: Steve K. <st...@st...> - 2004-03-07 23:06:13
|
On Mar 7, 2004, at 12:10 PM, Mark Spencer wrote: >> Hmm, maybe Mark can chime in on asterisk licensing. It sounds like it >> would be GPL-incompatible. > > As I understand it iaxclient is LGPL anyway. Since Digium either has > title to, or unrestricted rights to use, all the code in Asterisk, it > is > uniquely in the position of making granting exceptions to the GPL > license, > as we have in the case of open_h323, iLBC, and G.729. This is part of > why > we require disclaimers in order to merge the code into the main > Asterisk > codebase. Hmm. After reading this, I was thinking that asterisk with iLBC (which is currently built by default, right?) is no longer under the GPL itself, and then cannot actually be linked with other GPL code, unless the author of the other GPL code grants the same exception [in which case it's no longer actually GPL]. I almost reconsidered that, because these exceptions make the license less restrictive. You can always link GPL software against software with less restrictive licenses. However, in order to link asterisk + iLBC + some GPL software, you would still then be linking the GPL module with iLBC, which you can't do, because then you'd be linking the GPL module with something more restrictive. Licenses give me headaches. I guess it would be a lot simpler if there was just Modified-BSD, GPL, and LGPL, instead of the multitude of incompatible free-software licenses we have today. -SteveK |
|
From: Mark S. <mar...@di...> - 2004-03-07 17:19:01
|
> Hmm, maybe Mark can chime in on asterisk licensing. It sounds like it > would be GPL-incompatible. As I understand it iaxclient is LGPL anyway. Since Digium either has title to, or unrestricted rights to use, all the code in Asterisk, it is uniquely in the position of making granting exceptions to the GPL license, as we have in the case of open_h323, iLBC, and G.729. This is part of why we require disclaimers in order to merge the code into the main Asterisk codebase. Mark |
|
From: James H. C. Jr. <cl...@jh...> - 2004-03-06 22:19:27
|
>>>>> "Steve" == Steve Kann <st...@st...> writes: Steve> However, even totally proprietary stuff can be LGPL-compatible; Steve> LGPL allows you to link it to code under more restrictive Steve> licenses. There is some debate on what constitutes linking vs extending in this context. Distributing both parts in a single archive is argued to be extending no matter how the chunks of code communicate w/ each other. However, if they are completely separate packages -- and even better if they communicate by generic means -- it should be OK. But yes, I was tunnel-visioning a bit there when I included lgpl in the first post. -JimC |
|
From: Steve K. <st...@st...> - 2004-03-06 21:42:17
|
On Mar 6, 2004, at 1:22 PM, James H. Cloos Jr. wrote: >>>>>> "Steve" =3D=3D Steve Kann <st...@st...> writes: > > Steve> 2) I _think_ iLBC's license is also some kind of modified BSD > Steve> license. I'm pretty sure that it isn't GPL, and since it was > Steve> presumably compatible with the GPL for asterisk, it's probably > Steve> LGPL compatible for us to use as well. > > Actually, unless they gave Digium different terms than the ones on > their web site, ilbc is unfortunately not gpl or lgpl compatable. > > There is a clause that says you cannot use the code except to create > or decode iLBC bit streams, and said bit streams must be exactly the > same as what the reference code does. That clause makes compatability > with the gpl, lgpl and some other floss licences=B9 impossible. > > Were they do follow Xiph's example and license the code and the > trademark under separate terms, freeing the code but requiring > the current license's bit-stream compatability to use the iLBC > trademark, things would be much better indeed. We'd also be > able to improve the reference code's speed by adding support > for the various simd intruction sets, et al. Hmm, maybe Mark can chime in on asterisk licensing. It sounds like it=20= would be GPL-incompatible. However, even totally proprietary stuff can be LGPL-compatible; LGPL=20 allows you to link it to code under more restrictive licenses. So, you could, for example, use LGPL iaxclient with iLBC and a=20 proprietary, BSD, or LGPL-licensed UI (assuming you made the source=20 available to the LGPL portion, and linkable binary object code=20 available for the non-LGPL portions), but you could not use it with a=20 GPL-licensed UI. |
|
From: James H. C. Jr. <cl...@jh...> - 2004-03-06 18:30:02
|
>>>>> "Steve" == Steve Kann <st...@st...> writes: Steve> 2) I _think_ iLBC's license is also some kind of modified BSD Steve> license. I'm pretty sure that it isn't GPL, and since it was Steve> presumably compatible with the GPL for asterisk, it's probably Steve> LGPL compatible for us to use as well. Actually, unless they gave Digium different terms than the ones on their web site, ilbc is unfortunately not gpl or lgpl compatable. There is a clause that says you cannot use the code except to create or decode iLBC bit streams, and said bit streams must be exactly the same as what the reference code does. That clause makes compatability with the gpl, lgpl and some other floss licences¹ impossible. Were they do follow Xiph's example and license the code and the trademark under separate terms, freeing the code but requiring the current license's bit-stream compatability to use the iLBC trademark, things would be much better indeed. We'd also be able to improve the reference code's speed by adding support for the various simd intruction sets, et al. -JimC ¹ The exact list of which is left as an exercise for the reader. :-/ |
|
From: Adam H. <ad...@te...> - 2004-03-03 22:24:48
|
Steven Sokol wrote: >>I've created a g729 plugin for firefly but licensing it from sipro is >>yet to come :| Voiceage = sipro so sounds like I'm in for some fun. >>When we license it, I'm happy for us to sell it as a plugin (ie dll) and >>you could use it with iaxcomm. I'd have to implement some kind of >>security sheme (I assume?) but it should be a simple http request and >>reply. >> >>thoughts? >> >>-Adam >> >> > >Sounds good to me, but I'm writing for Windoze too. We may want to look at >a way to make it cross platform. Have you done anything at all for Mac or >Xnix? > >What kind of cost would we be looking at? Comparable to the $10.00 that >Digium is charging? Would the administration headache (licensing, etc.) >drive the cost up for you guys? > > > Well we wouldn't want to compete / undercut with digium so either $10 or windows only. It'd be rather simple having it for all platforms though, from a technical prospective. I'd like to hear from Mark (maybe privately) why he wasn't allowed to implement his own chan_g729 instead of having to distribute theirs. |
|
From: Steven S. <ss...@so...> - 2004-03-03 19:53:59
|
> I've created a g729 plugin for firefly but licensing it from sipro is > yet to come :| Voiceage = sipro so sounds like I'm in for some fun. > When we license it, I'm happy for us to sell it as a plugin (ie dll) and > you could use it with iaxcomm. I'd have to implement some kind of > security sheme (I assume?) but it should be a simple http request and > reply. > > thoughts? > > -Adam Sounds good to me, but I'm writing for Windoze too. We may want to look at a way to make it cross platform. Have you done anything at all for Mac or Xnix? What kind of cost would we be looking at? Comparable to the $10.00 that Digium is charging? Would the administration headache (licensing, etc.) drive the cost up for you guys? Thanks, Steve |
|
From: Steven S. <ss...@so...> - 2004-03-02 16:52:10
|
> > You're not the only one doing this. > > Another list member has already told us (off-list) that he has iaxComm > (not just iaxclient, but all of Michael's UI) working on an iPaq. He's > even made a more compact GUI interface for it. I've just sent you his > e-mail off-list. I would recommend that if you guys work on this > together, keep the list updated. I don't have any of these gizmos, and > neither does Michael (a.k.a. Steve V), and I'm not sure about the other > devs on the list. > I have a Toshiba PPC e740 if somebody wants to try to port it to Windows CE. The 740 uses the Arm XScale 400 MHz processor and has integrated 802.11b. I don't use it much, but it might make a cool communicator. In fact, if there's an easy way to convert it to Linux, I might be willing to give that a try. Steven Sokol Owner/Manager Sokol & Associates, LLC Phone: 816.822.1807 IaxTel: 700.613.9004 Web: http://www.sokol-associates.com |
|
From: Steve K. <st...@st...> - 2004-03-02 16:33:42
|
Stephan, You're not the only one doing this. Another list member has already told us (off-list) that he has iaxComm (not just iaxclient, but all of Michael's UI) working on an iPaq. He's even made a more compact GUI interface for it. I've just sent you his e-mail off-list. I would recommend that if you guys work on this together, keep the list updated. I don't have any of these gizmos, and neither does Michael (a.k.a. Steve V), and I'm not sure about the other devs on the list. As far as the CPU stuff; I'd start by turning off _all_ the input post-processing. Disable echo-cancellation [doesn't work yet anyway], noise reduction and VAD. If they're all disabled, you won't run the post-processor at all. -SteveK On Mar 2, 2004, at 11:16 AM, S wrote: > Hi Steve, > > thanks for your last mail. Before I comment your last mail I like to > explain what I try to do. > > I like to write a IAX Telephone Client for the Zaurus PDA. The Zaurus > PDA run's Linux and use a Srong ARM RISC 1110 CPU with about 137 > BogoMips. > As basis for this project I use the iaxclient lib and parts of > simpleclient. Also I use portaudio with some little changes for my > Zaurus. > > So back to your last mail: > > You wrote : > > If you're using portaudio, then audio.input should be pa_input, > which > is a simple function, which just looks to see if the > RingBuffer has > > data in it. Unless something is causing things to run very slowly > for > > you, then it should only have data occasionally. > > This sounds the Zaurus ARM CPU is to slow. For this reason I have to > find out where the time goes in iaxclib. > My Phone client is still a simple program with out any GUI. > I suspect there is something wrong in the send_encoded_audio || > input_postprocess chain, because I never get silent back (I tried it > on my power full PC never silent). > If you have some other idea where the problem is let me know. > > So here is my IAX observation : > > One of the main problem porting the IAX lib to the ARM CPU is, the IAX > protocol is not word align. > Word align mean every integer, short or pointer need to be on a > address which is divisible thru 4 (4*8bit = 32bit, and ARM CPU is a > 32bit CPU). > For this reason I have made some changes in the libiax2 part. > I will send you the changes later because I like to get the phone > client running first. > In different mail I have seen notice from people who write they run > iaxclib and asterisk on RISC machines without problems. I can't > believe this. This code will crash an any RISC machine sone. > > For more details I will send you the libiax2 changes later. > > Regards > > Stephan > > > |
|
From: S <s...@ka...> - 2004-03-02 16:22:13
|
Hi Steve, thanks for your last mail. Before I comment your last mail I like to explain what I try to do. I like to write a IAX Telephone Client for the Zaurus PDA. The Zaurus PDA run's Linux and use a Srong ARM RISC 1110 CPU with about 137 BogoMips. As basis for this project I use the iaxclient lib and parts of simpleclient. Also I use portaudio with some little changes for my Zaurus. So back to your last mail: You wrote : > If you're using portaudio, then audio.input should be pa_input, which > is a simple function, which just looks to see if the RingBuffer has > data in it. Unless something is causing things to run very slowly for > you, then it should only have data occasionally. This sounds the Zaurus ARM CPU is to slow. For this reason I have to find out where the time goes in iaxclib. My Phone client is still a simple program with out any GUI. I suspect there is something wrong in the send_encoded_audio || input_postprocess chain, because I never get silent back (I tried it on my power full PC never silent). If you have some other idea where the problem is let me know. So here is my IAX observation : One of the main problem porting the IAX lib to the ARM CPU is, the IAX protocol is not word align. Word align mean every integer, short or pointer need to be on a address which is divisible thru 4 (4*8bit = 32bit, and ARM CPU is a 32bit CPU). For this reason I have made some changes in the libiax2 part. I will send you the changes later because I like to get the phone client running first. In different mail I have seen notice from people who write they run iaxclib and asterisk on RISC machines without problems. I can't believe this. This code will crash an any RISC machine sone. For more details I will send you the libiax2 changes later. Regards Stephan |
|
From: Adam H. <ad...@te...> - 2004-03-01 23:52:00
|
Steve Kann wrote: > > 4) As far as asterisk code itself, Mark _can_ give us permission to > include it in iaxclient under the LGPL, since he (well, Digium) has > the complete copyright on it, and can license it anyway they want, > including GPL and/or any other license they want. So if there was code > in asterisk that was helpful to us, we could ask Mark nicely, and I'm > guessing he may be amenable to donating it to us for LGPL use. > Yes, I'm sorry, you're right. I forgot about that disclaimer thingy (even though I've signed it) |
|
From: Steve K. <st...@st...> - 2004-03-01 23:44:24
|
Adam Hart wrote: > Steven Sokol wrote: > >> I'd just look at asterisk's implementation for ideas [although not >> code, because asterisk is GPL]. >> >> “I’m a bit fuzzy on the whole good/bad thing, Egon. What do you mean >> bad.” >> >> I guess my understanding of GPL is a bit weak. Is this to say that >> the code in Asterisk can be freely used, and modified (so long as >> changes are returned to Digium) but only when used as part of the >> whole? I.e. the libiax2 is LGPL and that allows it to be used as a >> separate library, but the ilbc and speex codec code is simply more of >> Asterisk, so it can’t be used in iaxClient… >> >> So, could we ask Mark if he would be willing to allow us to use the >> code, or could we license it from him under some kind of code-sharing >> arrangement (if that’s possible under the LGPL license)? >> >> I understand that Intellectual Property is important stuff. I just >> find the license sub-types confusing and frustrating. >> >> Regs, >> >> Steven >> Yes, this is all confusing. I'd like to clarify some of Adam's points, though. > Mark couldn't give you permission, unforunately. You shouldn't need > the ilbc or speex code, just get it from the respective sites. GPL > says if you have any GPL'd code in your source, the entire program > must be available under GPL. Hence, if you have iaxcomm use some GPL, > it must in turn become GPL, which causes program that uses it to turn > GPL. Oh the fun :) As far as the codecs themselves go: 1) Speex is licensed under a LGPL compatible licence (modified BSD); We just get it from them, and can use it in our code. 2) I _think_ iLBC's license is also some kind of modified BSD license. I'm pretty sure that it isn't GPL, and since it was presumably compatible with the GPL for asterisk, it's probably LGPL compatible for us to use as well. 3) G711a/u itself is simple enough that you really don't need to use anyone else's code. 4) As far as asterisk code itself, Mark _can_ give us permission to include it in iaxclient under the LGPL, since he (well, Digium) has the complete copyright on it, and can license it anyway they want, including GPL and/or any other license they want. So if there was code in asterisk that was helpful to us, we could ask Mark nicely, and I'm guessing he may be amenable to donating it to us for LGPL use. As to why we use LGPL and not GPL: The answer is on the website, but basically it is because it allows people to: a) Link with proprietary codecs and stuff, like the encumbered G.xxx stuff. b) Create proprietary UI code. This is what allows Adam to make a proprietary Firefly application on top of libiax2, which is also LGPL. > I see no reason why iaxcomm would need any of asterisk's code. The > iLBC and speex stuff is just a wrapper around the libraries. Right; and the particulars of the implementation in asterisk is probably not what we want and/or need inside of iaxclient. The basic idea of modularization, though, is something we need, similarly to how we have modularized the audio interface (there are actually 2 mostly modularized audio interfaces: portaudio, and "file", the latter of which is a simple debugging tool for now). -SteveK |
|
From: Adam H. <ad...@te...> - 2004-03-01 23:43:31
|
> Mark couldn't give you permission, unforunately. You shouldn't need > the ilbc or speex code, just get it from the respective sites. GPL > says if you have any GPL'd code in your source, the entire program > must be available under GPL. Hence, if you have iaxcomm use some GPL, > it must in turn become GPL, which causes program that uses it to turn > GPL. Oh the fun :) > > I see no reason why iaxcomm would need any of asterisk's code. The > iLBC and speex stuff is just a wrapper around the libraries. > > -Adam > > Just a quick note there: Mark could give you permission to code he has written but not the entire of asterisk. Nor would he want to I believe. |
|
From: Adam H. <ad...@te...> - 2004-03-01 23:32:45
|
Steven Sokol wrote: > I'd just look at asterisk's implementation for ideas [although not=20 > code, because asterisk is GPL]. > > =93I=92m a bit fuzzy on the whole good/bad thing, Egon. What do you mea= n bad.=94 > > I guess my understanding of GPL is a bit weak. Is this to say that the=20 > code in Asterisk can be freely used, and modified (so long as changes=20 > are returned to Digium) but only when used as part of the whole? I.e.=20 > the libiax2 is LGPL and that allows it to be used as a separate=20 > library, but the ilbc and speex codec code is simply more of Asterisk,=20 > so it can=92t be used in iaxClient=85 > > So, could we ask Mark if he would be willing to allow us to use the=20 > code, or could we license it from him under some kind of code-sharing=20 > arrangement (if that=92s possible under the LGPL license)? > > I understand that Intellectual Property is important stuff. I just=20 > find the license sub-types confusing and frustrating. > > Regs, > > Steven > Mark couldn't give you permission, unforunately. You shouldn't need the=20 ilbc or speex code, just get it from the respective sites. GPL says if=20 you have any GPL'd code in your source, the entire program must be=20 available under GPL. Hence, if you have iaxcomm use some GPL, it must in=20 turn become GPL, which causes program that uses it to turn GPL. Oh the=20 fun :) I see no reason why iaxcomm would need any of asterisk's code. The iLBC=20 and speex stuff is just a wrapper around the libraries. -Adam |
|
From: Steven S. <ss...@so...> - 2004-03-01 23:24:16
|
I'd just look at asterisk's implementation for ideas [although not code, because asterisk is GPL]. "I'm a bit fuzzy on the whole good/bad thing, Egon. What do you mean bad." I guess my understanding of GPL is a bit weak. Is this to say that the code in Asterisk can be freely used, and modified (so long as changes are returned to Digium) but only when used as part of the whole? I.e. the libiax2 is LGPL and that allows it to be used as a separate library, but the ilbc and speex codec code is simply more of Asterisk, so it can't be used in iaxClient. So, could we ask Mark if he would be willing to allow us to use the code, or could we license it from him under some kind of code-sharing arrangement (if that's possible under the LGPL license)? I understand that Intellectual Property is important stuff. I just find the license sub-types confusing and frustrating. Regs, Steven |
|
From: Adam H. <ad...@te...> - 2004-03-01 23:19:35
|
Steve Kann wrote: > > I'd just look at asterisk's implementation for ideas [although not > code, because asterisk is GPL]. > > The 20ms frame size vs 30ms preferred frame size for iLBC will be an > issue that needs to be dealt with when you make codecs modularized. > Personally, I'd say that one should start with G711a/u, because the > implementation of that will be about 50 lines of C code for coding and > decoding (maybe less), and the bulk of the work will be in just > modularization. To be sure you get the modularization right, make > G711 work with 20ms or 30ms frame sizes. Then once that's working > (and you haven't broken GSM, because you'll need to modularize that as > well), adding any of the other codecs will be just a matter of the > proper cross-platform Makefile-fu plus a small amount of glue code, > and you'll have two examples of how to do the glue code. > > An experienced programmer should be able to do this (G711, GSM, iLBC) > in somewhere like 5 - 20 hours or so. > > Unforunately, Asterisk only supports 30ms iLBC frame size :| I was going to try and fix it but I'm always wary of changing asterisk in many places. If you modularise codecs, it's very easy to add new ones. I added g729 and g723.1 in a few hours. (as dlls though :p) I'll do speex when I can be bothered. |
72 messages has been excluded from this view by a project administrator.
