| 02:41.21 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 03:27.35 | *** join/#asterisk-dev DarkRift (i=dark@bas10-montreal02-1177583123.dsl.bell.ca) |
| 04:01.47 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 04:21.02 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 05:06.50 | *** join/#asterisk-dev dseeb_ (n=dcb@CPE-124-179-235-116.vic.bigpond.net.au) |
| 05:19.08 | Corydon76-dig | Qwell: ping |
| 05:20.29 | Corydon76-dig | I'm about to go ballistic on the Sangoma whore |
| 05:28.57 | Qwell | eh? |
| 05:29.11 | Corydon76-dig | Totaro |
| 05:29.22 | Qwell | which list? |
| 05:29.27 | Corydon76-dig | -dev |
| 05:29.45 | Qwell | I don't see anything from him |
| 05:29.48 | Corydon76-dig | I just formulated a message, then deleted it without sending it |
| 05:30.00 | Corydon76-dig | Oh, sorry, -users |
| 05:30.03 | Qwell | oh |
| 05:32.33 | Corydon76-dig | He seems to delight in sending snarky messages, with character assassinations on anyone he perceives to be a competitor |
| 05:32.45 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 05:33.45 | Corydon76-dig | Someone posted a guide on using Hylafax with Asterisk and he accused them of plagiarizing his work |
| 05:38.23 | Corydon76-dig | It's a good thing I don't have the launch codes for tactical nukes |
| 05:55.28 | *** join/#asterisk-dev Zuchmir (n=dddddd@123-2-65-142.static.dsl.dodo.com.au) |
| 05:55.48 | Zuchmir | is there an astxs for 1.4? |
| 06:07.47 | jameswf-home | ~1.4 |
| 06:07.55 | jameswf-home | ~astxs |
| 06:08.03 | jameswf-home | nah |
| 06:13.16 | Corydon76-home | Zuchmir: nope, sorry. |
| 06:13.43 | Corydon76-home | Zuchmir: if you move it into the directory structure, though, it gets automatically picked up by menuselect |
| 06:15.41 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 06:34.20 | Zuchmir | ok, thanks |
| 06:36.27 | *** part/#asterisk-dev dseeb_ (n=dcb@CPE-124-179-235-116.vic.bigpond.net.au) |
| 07:28.32 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 07:34.54 | *** join/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-96-159.bredband.comhem.se) |
| 07:40.28 | snuff-home | :P |
| 09:08.28 | *** join/#asterisk-dev jmls (n=jmls@62.49.235.130) |
| 09:59.25 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 10:28.49 | *** join/#asterisk-dev cathyal (n=cathy@unaffiliated/cathyal) |
| 10:50.58 | *** join/#asterisk-dev oej (n=olle@soll4-125.cust.blixtvik.net) |
| 10:50.58 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 11:19.25 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 12:54.44 | *** join/#asterisk-dev RoyKa (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 13:02.07 | *** join/#asterisk-dev oej (n=olle@soll4-125.cust.blixtvik.net) |
| 13:02.07 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:16.12 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 14:06.29 | *** join/#asterisk-dev _charly_ (i=kroseneg@sunrise.schmidham.net) |
| 14:53.20 | *** join/#asterisk-dev tzafrir_laptop (n=tzafrir@62.90.10.53) |
| 14:53.20 | *** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ |
| 14:58.49 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 15:32.14 | *** join/#asterisk-dev bkw_ (n=brian@adsl-64-149-41-151.dsl.tul2ok.sbcglobal.net) |
| 15:32.56 | *** part/#asterisk-dev bkw_ (n=brian@adsl-64-149-41-151.dsl.tul2ok.sbcglobal.net) |
| 16:40.57 | *** join/#asterisk-dev mamep (i=fallen@helios.edu.uoc.gr) |
| 16:41.28 | mamep | hey..just a simple question |
| 16:42.04 | mamep | anyone experienced with h323 and asterisk integration? |
| 16:42.13 | Corydon76-dig | Please ask on #asterisk |
| 16:42.30 | Corydon76-dig | This channel is for the development of Asterisk itself. |
| 16:43.16 | mamep | yeah got it ..but i'm having some major problems with the design of h323 channel |
| 16:43.25 | mamep | and i can't find anywhere a good stuff to read |
| 16:43.28 | Corydon76-dig | Which one? |
| 16:43.38 | Corydon76-dig | To the best of my knowledge, there are 3 |
| 16:43.55 | Corydon76-dig | h323, oh323, ooh323 |
| 16:44.07 | tzafrir | mamep, I see that Corydon76-dig is also on #asterisk ... |
| 16:44.08 | mamep | i tried with h323 |
| 16:44.27 | mamep | and tried to debug it at trace level 5 |
| 16:44.42 | mamep | it seems to be something with h245 controll messages timeout |
| 16:45.02 | mamep | tzafrir : thx for the notice but i've been asking for days now in #asterisk and nothing usefull |
| 16:45.03 | mamep | :( |
| 16:45.06 | Corydon76-dig | Without knowing more about the H.323 protocol, I am not equipped to assist you. |
| 16:45.52 | Corydon76-dig | mamep: you do know that you've been asking in the middle of an American holiday weekend, when a lot of people are off, right? |
| 16:46.04 | mamep | don't know that |
| 16:46.13 | mamep | but i'm searching for some stuff to read |
| 16:46.22 | mamep | and try to fix the problem.. |
| 16:46.32 | mamep | btw i think that ooh323 stands better than h323 |
| 16:46.51 | Corydon76-dig | That's because it's a different library implementation |
| 16:47.32 | mamep | and what's the deal with oh323? |
| 16:47.41 | mamep | i think the authors was some greek guys |
| 16:47.49 | Corydon76-dig | InAccess Networks |
| 16:48.10 | Corydon76-dig | They wrote theirs first |
| 16:48.48 | Corydon76-dig | Then JerJer wrote a competing implementation, because he wasn't satisfied with their implementation, which is h323 |
| 16:48.58 | *** join/#asterisk-dev fakhir (n=fakhir@unaffiliated/fakhir) |
| 16:48.58 | tzafrir | oh323 actually predated h323 |
| 16:49.20 | Corydon76-dig | and finally, Digium wasn't satisfied with the stability of either, so they contracted to get ooh323 built |
| 16:49.26 | mamep | hehe trying to reach JerJer |
| 16:49.27 | tzafrir | Corydon76-dig, writes faster :-) |
| 16:49.28 | mamep | i 'c |
| 16:49.43 | mamep | well and what's your suggetion? |
| 16:49.55 | tzafrir | He's not the current maintainer. I think that the current maintainer is pcadech (sp?) |
| 16:49.56 | mamep | also found something intresting with chan_woomera |
| 16:50.17 | mamep | and h323+ ? |
| 16:50.21 | Corydon76-dig | I don't have a suggestion. Like I said, I am not equipped to help you with questions about the inner workings of any of them |
| 16:51.08 | Corydon76-dig | I know it exists, I've even deployed solutions with chan_h323. |
| 16:51.48 | Corydon76-dig | That was my first experience with running two Asterisk daemons on the same box |
| 16:52.01 | mamep | k thx |
| 16:52.12 | Corydon76-dig | so that when h323 crashed, it only took other h323 calls with it, not every call on the machine |
| 16:52.55 | mamep | yeah a little bit hard one is h323 |
| 16:53.11 | mamep | i can get incoming calls although but with outgoing i can't get voice :P |
| 16:53.15 | mamep | wired problem |
| 16:54.16 | Corydon76-dig | Almost sounds like a NAT issue |
| 16:57.27 | mamep | well actually |
| 16:57.31 | mamep | i can call someone |
| 16:57.33 | mamep | the phone rings |
| 16:57.39 | mamep | and if the calleee answers |
| 16:57.52 | mamep | the caller continues ringing |
| 16:57.56 | mamep | and i don't use nat |
| 17:14.10 | *** join/#asterisk-dev blitzrage (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 17:14.10 | *** mode/#asterisk-dev [+o blitzrage] by ChanServ |
| 17:17.06 | Corydon76-dig | tzafrir: would some of the problems you have with packaging config files be helped if we came up with a syntax for specifying in what version a particular option is added, so it can be merged into an existing config seamlessly? |
| 17:18.04 | tzafrir | what type of syntax? |
| 17:18.26 | tzafrir | Corydon76-dig, do you think that this is just a packaging problem? |
| 17:18.29 | Corydon76-dig | I dunno, maybe something similar to the MODINFO syntax we use in source files |
| 17:19.14 | Corydon76-dig | tzafrir: I think we could definitely implement this kind of upgrade logic in 'make upgrade', as well |
| 17:19.56 | tzafrir | for one version it might work, but I'm trying to think how this can scale accross varius versions |
| 17:21.20 | Corydon76-dig | Well, the version number that a file was started at would be embedded in the file and changed at each upgrade |
| 17:23.12 | Corydon76-dig | Maybe something as simple as storing the revision number in the config file, then running an svn diff with revision numbers to get the diffs and apply those diffs to the config file |
| 17:24.07 | Corydon76-dig | That's more likely to get you rejected segments, which is what we'd want: if you can't merge cleanly, don't merge at all |
| 17:24.23 | tzafrir | I think that there are some config changes some of the users will not like applied automatically |
| 17:24.36 | Corydon76-dig | (and then tell the admin that config file changes were unable to be merged) |
| 17:24.52 | mvanbaak | as long as you make it optionally |
| 17:24.53 | tzafrir | I think that if something that needs fixing, it is the defaults, rather than the configs |
| 17:25.21 | Corydon76-dig | There's nothing wrong with the defaults, until the defaults change |
| 17:26.28 | tzafrir | Actually, I gave an example in the thread of a case where the "default" in the config file differs from Asterisk's default |
| 17:26.41 | tzafrir | modules.conf=> [modules]=>autoload |
| 17:26.42 | Corydon76-dig | If you change the defaults, you're going to introduce far more problems than giving people the knowledge of new options |
| 17:27.49 | tzafrir | Without that, you might as well have started by defualt without modules.conf, and all was well |
| 17:28.05 | Corydon76-dig | I agree with the current approach with modules.conf and autoload. With no config, you get no modules loaded |
| 17:28.29 | Corydon76-dig | With the sample config, all modules are loaded |
| 17:28.36 | tzafrir | so asterisk really "doesn't work" |
| 17:29.14 | tzafrir | In what scenario would you want no module to load? |
| 17:29.18 | Corydon76-dig | Right, which implies that you need the config files |
| 17:29.48 | Corydon76-dig | because Asterisk doesn't do much, even if you load all modules, if you don't have anything in extensions.conf |
| 17:30.29 | tzafrir | I'm looking at it one at a time. I'll get to extensions.conf :-) |
| 17:30.50 | Corydon76-dig | Or are you advocating that we load a default extensions logic if the file doesn't exist? That's horrible. |
| 17:31.21 | tzafrir | I don't advocate that. But there are ways to write a dialplan not through extensions.conf |
| 17:31.44 | Corydon76-dig | You mean AEL or LUA? |
| 17:32.00 | Corydon76-dig | or (gag) pbx_realtime? |
| 17:32.01 | tzafrir | right. And ael is also enabled in the default config |
| 17:32.38 | Corydon76-dig | Yes, but AEL has no default config without a config file. Nor does LUA |
| 17:34.01 | tzafrir | Right. But I can think about other functional defualts. |
| 17:34.29 | tzafrir | anyway, besides the dialplan, is there any other such essential part? |
| 17:34.40 | tzafrir | You need some functioning channel |
| 17:34.54 | Corydon76-dig | Right |
| 17:35.13 | Corydon76-dig | and automatically configuring channels is a security risk |
| 17:35.25 | tzafrir | And that can be sip, iax, alsa/oss, or for less common hardware: zap, misdn and such |
| 17:35.58 | tzafrir | automaitcally configuring alsa/oss is not, but it hogs on your sound card :-( |
| 17:36.22 | Corydon76-dig | Right, so we shouldn't do that without a config, either |
| 17:36.23 | tzafrir | Or was that changed? |
| 17:36.48 | Corydon76-dig | Have we established yet that doing nothing without config files is sane? |
| 17:36.56 | tzafrir | Actually we currently do that. The first one of alsa/oss to load wins, IIRC |
| 17:37.08 | tzafrir | On Debian we have an explicit unload for both of them |
| 17:37.40 | Corydon76-dig | The default config file only selects one of them for loading |
| 18:52.05 | *** join/#asterisk-dev oej (n=olle@soll4-125.cust.blixtvik.net) |
| 18:52.05 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 19:23.56 | *** join/#asterisk-dev bkw_ (n=brian@adsl-64-149-41-151.dsl.tul2ok.sbcglobal.net) |
| 19:26.03 | De_Mon | I thought I was safe changing the default to noloading stuff I knew I didn't want and letting asterisk autoload everything else, but that's proven untrue with debian :) |
| 19:45.10 | *** join/#asterisk-dev RoyK (n=roy@ip-216-23-149-91.dialup.ice.no) |
| 19:58.47 | *** join/#asterisk-dev anonymouz666 (n=anonymou@200.218.193.6) |
| 20:07.02 | *** join/#asterisk-dev fakhir (n=fakhir@unaffiliated/fakhir) |
| 21:26.45 | *** join/#asterisk-dev ctooley (n=ctooley@doc-72-47-33-80.maryville.mo.cebridge.net) |
| 22:29.20 | *** join/#asterisk-dev anonymouz666 (n=anonymou@200.218.193.6) |
| 23:03.34 | *** join/#asterisk-dev mashroom_ (n=tasty@89-138-132-186.bb.netvision.net.il) |
| 23:12.34 | *** join/#asterisk-dev file (n=file@asterisk/developer-and-muffin-lover/file) |
| 23:12.34 | *** mode/#asterisk-dev [+o file] by ChanServ |
| 23:17.42 | *** join/#asterisk-dev ManxPower (n=manxpowe@70.sub-70-220-221.myvzw.com) |
| 23:29.51 | *** join/#asterisk-dev file (n=file@asterisk/developer-and-muffin-lover/file) |
| 23:29.51 | *** mode/#asterisk-dev [+o file] by ChanServ |