| 00:22.36 | tzafrir_home | moy, there's a difference between linking against a LGPL library and borrowing code from a LGPL library |
| 00:23.54 | moy | tzafrir_home: thats what I am trying to clarify to myself. See if there is any potential conflict |
| 00:24.02 | tzafrir_home | Generally there would have been no issue with the latter. Only in the case of Asterisk the owners want to keep full ownership (or actually: possibility to relicence) of the whole codebase |
| 00:25.58 | moy | however, since right now I have not disclaimed my library to Digium, and I just released it as LGPL, there is no added issue by adding other's library LGPL'd code, I think |
| 00:26.57 | moy | into my library, not into Asterisk code base I mean |
| 00:52.41 | tzafrir_home | sure |
| 00:52.44 | tzafrir_home | no problem |
| 02:01.38 | *** join/#asterisk-dev Cresl1n (n=matt@65.4.25.58) |
| 02:01.38 | *** mode/#asterisk-dev [+o Cresl1n] by ChanServ |
| 02:23.04 | *** join/#asterisk-dev obnauticus (n=obnautic@c-67-160-187-7.hsd1.wa.comcast.net) |
| 02:29.44 | *** join/#asterisk-dev mvanbaak_ (n=michiel@vanbaak.xs4all.nl) |
| 02:49.32 | *** join/#asterisk-dev Cresl1n (n=matt@65.4.25.58) |
| 02:49.32 | *** mode/#asterisk-dev [+o Cresl1n] by ChanServ |
| 02:50.23 | *** join/#asterisk-dev sruffell (n=sruffell@adsl-074-185-078-025.sip.bhm.bellsouth.net) |
| 02:50.23 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 03:33.41 | *** part/#asterisk-dev Cresl1n (n=matt@65.4.25.58) |
| 04:18.33 | *** part/#asterisk-dev sruffell (n=sruffell@adsl-074-185-078-025.sip.bhm.bellsouth.net) |
| 05:41.31 | *** join/#asterisk-dev puzzled (n=patrick@puzzled.xs4all.nl) |
| 05:42.14 | puzzled | hi |
| 06:20.15 | *** join/#asterisk-dev jsolis (n=jimmy@201.240.109.172) |
| 08:27.44 | *** join/#asterisk-dev RoyK (n=roy@ip-5-49-149-91.dialup.ice.no) |
| 10:20.29 | *** join/#asterisk-dev steliosk (n=Stelios@athedsl-291059.home.otenet.gr) |
| 10:37.34 | *** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.139) |
| 10:55.50 | *** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.139) |
| 11:11.34 | *** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.139) |
| 12:18.09 | *** join/#asterisk-dev RoyK (n=roy@c51008389.inet.catch.no) |
| 12:18.53 | *** part/#asterisk-dev jmls_home (n=jmls_hom@mail.tessera.co.uk) |
| 12:24.28 | *** join/#asterisk-dev jmls_home (n=jmls_hom@mail.tessera.co.uk) |
| 12:33.52 | *** join/#asterisk-dev ctooley (n=ctooley@209.33.110.169) |
| 13:31.40 | *** join/#asterisk-dev puzzled (n=patrick@puzzled.xs4all.nl) |
| 13:44.36 | *** join/#asterisk-dev RoyK (n=roy@062249179121.customer.alfanett.no) |
| 14:22.13 | *** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.139) |
| 14:41.18 | *** join/#asterisk-dev snuff-home (n=snuff-ho@60-240-117-7-nsw-pppoe.tpgi.com.au) |
| 15:27.28 | *** join/#asterisk-dev sergee (n=serg@voip1.west-call.com) |
| 16:43.42 | *** join/#asterisk-dev jeffg (i=D8ZciOa5@pdpc/supporter/active/jeffg) |
| 16:56.16 | *** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171) |
| 17:07.09 | *** join/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-96-193.bredband.comhem.se) |
| 17:17.43 | *** join/#asterisk-dev RoyK (n=roy@ti211310a080-7540.bb.online.no) |
| 17:21.53 | *** join/#asterisk-dev DarkRift (i=dark@bas10-montreal02-1177582051.dsl.bell.ca) |
| 17:48.27 | *** join/#asterisk-dev Greek-Boy (n=email@41.221.58.14) |
| 18:19.21 | *** join/#asterisk-dev xrg_ (n=panos@cpe028238.netone.gr) |
| 18:33.16 | *** join/#asterisk-dev jeffspeff2 (n=jeff@c-68-53-81-14.hsd1.ky.comcast.net) |
| 18:55.32 | *** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171) |
| 19:20.02 | *** join/#asterisk-dev putnopvut (n=putnopvu@c-71-228-178-34.hsd1.al.comcast.net) |
| 19:20.11 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 19:56.07 | *** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171) |
| 20:14.43 | *** join/#asterisk-dev gitguy (n=diego@adsl-134-171.click.com.py) |
| 20:15.10 | *** join/#asterisk-dev RoyK (n=roy@ti211310a080-7540.bb.online.no) |
| 20:52.01 | gitguy | hi guys, do you have plans to improve asterisk, based on this critics: http://www.freeswitch.org/eg/How%20does%20FreeSWITCH%20compare%20to%20Asterisk.pdf -- i don't meant to troll or anything... just being curious about it |
| 20:56.42 | *** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171) |
| 20:59.43 | ectospasm | gitguy: I'm reading... |
| 21:00.03 | *** join/#asterisk-dev lisandropm (n=lisandro@190.1.22.76) |
| 21:00.23 | *** part/#asterisk-dev lisandropm (n=lisandro@190.1.22.76) |
| 21:04.23 | gitguy | tell me what you think |
| 21:05.09 | ectospasm | well... like he says,"Asterisk is a PBX and FreeSWITCH is a soft switch" |
| 21:05.18 | ectospasm | so they fill different niches. |
| 21:06.05 | ectospasm | I didn't see him so much as bashing Asterisk, just pointing out some of the flaws in an older version.... |
| 21:08.48 | gitguy | hehe |
| 21:11.13 | gitguy | can you guys make meetme() zaptel-independent in the future? or is the timing really important? |
| 21:11.30 | gitguy | i know there is app_conference, but meetme has the features that i need |
| 21:12.07 | gitguy | timing independent would be nice (optionally) i think |
| 21:13.01 | ectospasm | I think the timing is crucial, but I'm not advanced enough to really know why |
| 21:15.42 | gitguy | so those flaws that anthm mentions aren't in newer versions of asterisk anymore? |
| 21:16.53 | Qwell | You assume he's correct about them being flaws in the first place. |
| 21:19.06 | gitguy | no, i don't assume he's correct or anything, i asked that because ectospasm said: "just pointing out some of the flaws in an older version...." |
| 21:19.44 | gitguy | :) |
| 21:20.26 | ectospasm | for basic argument's sake, when is a deadlock not a flaw? That was the only thing he really argued for, and he said the reason was the underlying architecture... mind you he was talking about 1.2 (or so I gathered from my quick skim) |
| 21:21.06 | Qwell | it talks about more than just deadlocks |
| 21:23.34 | ectospasm | like I said, I just skimmed it quickly |
| 21:23.36 | gitguy | i like asterisk, from a user perspective is very easy to configure and works well most of the time |
| 21:24.31 | gitguy | i had some troubles with zaptel on XEN environments but that's not a big problem anyway |
| 21:25.01 | gitguy | i needed it for ztdummy/meetme |
| 21:25.55 | gitguy | my fix for that was to move my asterisk server on real hardware |
| 21:29.02 | ectospasm | yeah... I've never heard about too much success in virtualized environments |
| 21:29.20 | ectospasm | but again, I don't pay attention that much. Not as much as I should. |
| 21:46.06 | gitguy | how does a a telephone switch differences from a pbx |
| 21:48.23 | file | there already exists a conference app that does not use Zaptel that will be merged in later |
| 21:49.38 | gitguy | cool |
| 21:50.14 | gitguy | does it have the features of meetme() ? |
| 21:50.23 | file | most, yes. |
| 21:50.29 | gitguy | nice |
| 22:00.17 | gitguy | file: is there a patch somewhere or something where i could look? |
| 22:00.48 | file | it's a branch for bridging... http://svn.digium.com/svn/asterisk/team/file/bridging - the conference app is app_confbridge.c in the apps directory |
| 22:01.00 | gitguy | thanks |
| 22:02.07 | file | runs off |
| 22:10.17 | gitguy | so that can create conferences without zaptel and it doesn't require meetme too? |
| 22:10.36 | file | sure. |
| 22:10.49 | file | it can use zaptel if present, or operate without it |
| 22:10.59 | gitguy | nice |
| 22:11.06 | gitguy | will that be merged for 1.6? |
| 22:11.15 | file | it'll go into a future 1.6 release, yes |
| 22:11.33 | gitguy | nice |
| 22:12.47 | gitguy | will make life easier for a lot of people i think |
| 22:13.10 | gitguy | well, i don't think, i'm sure |
| 22:13.32 | file | the timing inside a virtualized environment might still be flaky... don't know |
| 22:16.03 | *** join/#asterisk-dev RoyK (n=roy@ip-177-22-149-91.dialup.ice.no) |
| 22:18.02 | gitguy | will have pin/password options? |
| 22:18.49 | gitguy | that and the option to know who comes in and goes out of a conference is what i would need |
| 22:18.49 | file | not currently. |
| 22:19.47 | gitguy | hehe ok, i'm fine meetme atm |
| 22:20.00 | gitguy | with meetme* |
| 22:23.43 | gitguy | does asterisk provides the option to write dialplans in other languages (ruby, etc)? |
| 22:24.29 | *** part/#asterisk-dev RoyK (n=roy@ip-177-22-149-91.dialup.ice.no) |
| 22:24.30 | file | there is one for lua right now, but nobody has written a module to use other languages |
| 22:24.44 | gitguy | i see |
| 22:33.32 | *** join/#asterisk-dev gitguy (n=diego@adsl-134-171.click.com.py) |
| 22:34.07 | gitguy | dial out from conferences would be nice too |
| 22:34.26 | gitguy | if i were coder i would contribute, but i'm not... i could donate some money tho |
| 22:43.40 | Qwell | gitguy: there is, of course, also AGI |
| 22:43.51 | Qwell | probably not quite the level you're looking for, but.. |
| 22:44.35 | gitguy | will check it out |
| 22:47.17 | gitguy | thx |
| 23:02.04 | *** join/#asterisk-dev gitguy (n=diego@adsl-134-171.click.com.py) |
| 23:14.33 | *** join/#asterisk-dev shido6 (n=shido6@74-130-51-159.dhcp.insightbb.com) |
| 23:15.57 | gitguy | does chan_sip works with tcp? is sip in asterisk rfc compliant? |
| 23:16.40 | shido6 | wow |
| 23:16.46 | shido6 | have you been under a rock? |
| 23:17.08 | gitguy | me? |
| 23:17.12 | shido6 | gitguy what do youu want to do with asterisk? |
| 23:17.38 | gitguy | shido6: i use asterisk every day |
| 23:18.24 | gitguy | i just heard that the sip implementation in asterisk is not "rfc compliant" so i wanted to ask the devs |
| 23:18.43 | shido6 | if it isnt, then what :) |
| 23:18.50 | gitguy | "is not rfc complaint because is lacking tcp support" or something like that |
| 23:19.18 | shido6 | tcp support? thats kind of weird. |
| 23:19.32 | file | gitguy: chan_sip has been called the most interoperable SIP implementation at the SIP interop tests |
| 23:19.46 | file | and TCP support exists in 1.6 |
| 23:19.51 | gitguy | awesome |
| 23:21.47 | file | there's being RFC compliant... and then the real world... we are slack in what we accept, and strict in what we send |
| 23:23.20 | gitguy | hmm |
| 23:26.13 | gitguy | hehe |
| 23:27.31 | gitguy | i guess so, but both are good, aren't them? ;) |
| 23:37.29 | gitguy | s/good/important |
| 23:37.36 | gitguy | compliance and the real world |
| 23:42.08 | *** join/#asterisk-dev outtolunc (n=me@c-67-170-211-86.hsd1.ca.comcast.net) |
| 23:45.23 | *** join/#asterisk-dev anthm (n=anthm@68-31-153-205.area4.spcsdns.net) |
| 23:46.56 | Qwell | compliance? not really |
| 23:47.17 | Qwell | a compliant SIP channel is a non-working SIP channel |