| 00:04.52 | *** join/#asterisk-dev ctooley (n=ctooley@209.33.109.32) |
| 00:54.52 | *** part/#asterisk-dev ctooley (n=ctooley@209.33.109.32) |
| 01:22.14 | *** join/#asterisk-dev jtodd (n=jtodd@188.sub-75-207-31.myvzw.com) |
| 01:27.14 | *** part/#asterisk-dev davevg-btwtech (n=davevg-b@nj-67-76-177-147.sta.embarqhsd.net) |
| 01:43.49 | *** join/#asterisk-dev puzzled (n=patrick@puzzled.xs4all.nl) |
| 01:59.44 | *** join/#asterisk-dev Damin (n=damin@nucleus.nacs.net) |
| 02:01.19 | dlynes_laptop | M11072 |
| 02:01.20 | MuffinMan | [new] [Asterisk] Resources/res_features 0011072: Parked call timeout features reported by dlynes http://bugs.digium.com/view.php?id=11072 |
| 02:22.49 | puzzled | hi |
| 02:23.55 | puzzled | if '#' is not the start of a valid comment in 1.4 then maybe someone wants to do %s/^#/;/g muted.conf |
| 02:24.03 | puzzled | 1.4.13 |
| 02:27.14 | d3wayne | 00 |
| 02:30.19 | Qwell | puzzled: muted is a separate app |
| 02:32.15 | puzzled | I see. pardon the noise |
| 02:40.24 | *** join/#asterisk-dev dlynes_laptop (n=dlynes@d154-20-34-39.bchsia.telus.net) |
| 02:42.34 | dlynes_laptop | russellb: I'm curious about how much work I would be in for, if I wanted to modify the SLA code so that it's configurable enough that if a call is initiated on one of the SLA's, that someone isn't able to pick up that line from another extension? |
| 02:42.48 | dlynes_laptop | russellb: i.e. so that two extensions aren't thrown into a conference/meetme room with the outside caller |
| 02:50.38 | d3wayne | hey qwell! Nina typed my last response |
| 03:23.37 | *** join/#asterisk-dev fakhir (n=fakhir@unaffiliated/fakhir) |
| 04:08.55 | *** join/#asterisk-dev mitcheloc (n=mitchel@ppp-67-126-240-11.dsl.irvnca.pacbell.net) |
| 04:29.23 | *** join/#asterisk-dev syle (n=blah@unaffiliated/syle) |
| 04:32.02 | *** join/#asterisk-dev syle2 (n=blah@unaffiliated/syle) |
| 04:32.11 | *** join/#asterisk-dev dlynes_home (n=dlynes@d154-20-34-39.bchsia.telus.net) |
| 04:34.00 | *** join/#asterisk-dev syle (n=blah@unaffiliated/syle) |
| 04:38.06 | *** join/#asterisk-dev dlynes__ (n=dlynes@d154-20-34-39.bchsia.telus.net) |
| 04:43.03 | *** join/#asterisk-dev syle (n=blah@unaffiliated/syle) |
| 04:50.35 | *** join/#asterisk-dev syle (n=blah@unaffiliated/syle) |
| 05:14.35 | *** join/#asterisk-dev snuff-home (n=snuffy@C-59-101-243-89.bur.connect.net.au) |
| 06:10.45 | *** join/#asterisk-dev dlynes_laptop (n=dlynes@d154-20-34-39.bchsia.telus.net) |
| 06:17.39 | *** join/#asterisk-dev mog (n=mog@c-71-207-220-220.hsd1.al.comcast.net) |
| 06:17.39 | *** mode/#asterisk-dev [+o mog] by ChanServ |
| 07:09.21 | *** join/#asterisk-dev mexuar-tim (n=mexuar-t@host-212-158-206-61.bulldogdsl.com) |
| 08:08.44 | *** join/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-12-187.bredband.comhem.se) |
| 08:15.09 | *** part/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-12-187.bredband.comhem.se) |
| 08:16.18 | *** join/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-12-187.bredband.comhem.se) |
| 08:35.50 | De_Mon | SLA? |
| 08:36.00 | De_Mon | what sla code? |
| 09:11.17 | mvanbaak | shared line appearance |
| 09:12.40 | jmls | Super Linux Architecture |
| 09:13.17 | mvanbaak | does that exist ? |
| 09:13.48 | jmls | in my mind ;) |
| 09:14.09 | mvanbaak | lol |
| 09:14.25 | mvanbaak | every OS sucks |
| 09:14.32 | mvanbaak | some just suck a little less then others |
| 09:15.00 | jmls | I thought that Winbloze ;) |
| 09:15.44 | mvanbaak | Vista++ |
| 09:15.45 | mvanbaak | ;) |
| 09:32.52 | *** join/#asterisk-dev ussrback (n=MAX@80.92.183.84) |
| 09:32.57 | ussrback | please help with odbc/mysql/voicemail issue |
| 09:33.07 | ussrback | http://pastebin.ca/751355 |
| 10:25.19 | *** join/#asterisk-dev pina (n=oax@unaffiliated/pina) |
| 10:25.23 | pina | hi |
| 10:27.45 | pina | i got asterisk running in binary form, source compile is not supported |
| 10:27.50 | pina | i mean disabled as hdd size is too less |
| 10:27.56 | pina | so i need to run all the things which trixbox provides from the USB w/o a HDD install |
| 10:28.00 | pina | and it must not crash |
| 10:28.55 | JT | this isn't trixbox support |
| 10:29.00 | pina | and if the luks setup fails? then insert the crashed USB and run the live cd again and it will open luks and run fsck and fix |
| 10:29.04 | pina | i know! |
| 10:29.10 | pina | but its asterisk related |
| 10:29.21 | pina | basically i need to make all that run in native mode from USB |
| 10:29.31 | pina | even after i apply squashfs-lzma it still should run all from that small USB drive 1 GB just like the live cd |
| 10:30.17 | JT | so we don't care |
| 10:32.09 | mvanbaak | pina: and your development related question is ? |
| 10:38.22 | tzafrir_home | pina, I wish you the best of luck |
| 10:38.52 | tzafrir_home | Generally I would, instead, find out what is it you really need |
| 10:41.07 | tzafrir_home | anyway, this is a question for #asterisk (or #trixbox , or whatever). I haven't noticed the channel |
| 10:59.17 | *** join/#asterisk-dev JunK-Y (n=junky@modemcable183.17-83-70.mc.videotron.ca) |
| 11:59.57 | *** join/#asterisk-dev qdk (n=qdk@0x573fe57e.bynqu2.broadband.tele.dk) |
| 13:16.58 | *** join/#asterisk-dev qdk (n=qdk@0x573fe57e.bynqu2.broadband.tele.dk) |
| 14:09.37 | *** join/#asterisk-dev puzzled (n=patrick@puzzled.xs4all.nl) |
| 14:11.00 | puzzled | hi |
| 14:36.34 | mvanbaak | yo |
| 15:22.43 | *** join/#asterisk-dev wunderkin (n=wunderki@ip72-208-16-104.ph.ph.cox.net) |
| 15:27.56 | *** join/#asterisk-dev _ys (n=yuri@80.70.236.69) |
| 15:46.22 | *** join/#asterisk-dev fakhir (n=fakhir@unaffiliated/fakhir) |
| 16:21.53 | *** join/#asterisk-dev Cresl1n (i=matt@nat/digium/x-33e8fe279b85ca31) |
| 16:21.53 | *** mode/#asterisk-dev [+o Cresl1n] by ChanServ |
| 17:21.50 | *** join/#asterisk-dev ManxPower (n=manxpowe@158.sub-75-202-230.myvzw.com) |
| 17:25.41 | *** join/#asterisk-dev blitzrage (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 17:27.21 | tzafrir_home | Cresl1n, here? |
| 17:28.49 | Cresl1n | yeah |
| 17:28.52 | Cresl1n | how's it going? |
| 17:29.37 | tzafrir_home | nice |
| 17:29.54 | tzafrir_home | Trying to split the kernel stuff in zaptel to a subdirectory |
| 17:31.21 | Corydon76-dig | Why move the kernel stuff, instead of moving all of the utils to a subdirectory? |
| 17:33.19 | tzafrir_home | I think that both are needed |
| 17:33.50 | tzafrir_home | The kernel stuff seems eaiser to separate |
| 17:34.48 | tzafrir_home | anyway, the firmwares subdir has a really unnecessary dependency: |
| 17:36.05 | tzafrir_home | Generation of a firmware object file depends on the "base" module for which it is generated |
| 17:37.04 | tzafrir_home | That dependency is solely for getting the values of bdfname and bdfarch in build_toos/make_firmware_object |
| 17:38.21 | *** join/#asterisk-dev mexuar-tim (n=mexuar-t@host-212-158-206-61.bulldogdsl.com) |
| 17:38.26 | tzafrir_home | any idea how to get that value (for target architecture) in autoconf? |
| 17:40.22 | *** join/#asterisk-dev UVSoft (n=ForeverY@83.243.68.5) |
| 17:41.03 | UVSoft | hi |
| 17:41.54 | UVSoft | can anyone please tell me what's going on with sip over tcp? |
| 17:45.09 | ManxPower | I'm having trouble escaping global variables. |
| 17:45.39 | ManxPower | \${UNIQUEID} in the dialplan still evaluates. |
| 17:46.04 | ManxPower | according to README.variables it should not. |
| 17:46.11 | ManxPower | is it a docs bug or an excape bug? |
| 17:46.16 | ManxPower | escape too |
| 17:57.26 | ManxPower | nevermind then. pointless to file a bug for 1.2 anywat. |
| 18:00.20 | ManxPower | Wow! Cool bug, though. |
| 18:00.44 | ManxPower | Works as expected: VERBOSE=$ [${UNIQUEID} ${EXTEN} ${CHANNEL} ${CONTEXT}]: |
| 18:00.53 | ManxPower | Does not work as expected: VERBOSE=[${UNIQUEID} ${EXTEN} ${CHANNEL} ${CONTEXT}]: |
| 18:06.30 | tzanger | say that again? |
| 18:06.38 | tzanger | "$ " ? |
| 18:06.54 | tzanger | dollarsign-space? |
| 18:07.30 | ManxPower | tzanger: Here is more info: http://pastebin.ca/751756 |
| 18:07.51 | ManxPower | I want the literal string ${UNIQUEID}, etc, so it can be evaluated later. |
| 18:08.28 | ManxPower | tzanger: That's what's so cool. $ is acting to escape the entire string. Not what I wanted, but still cool. |
| 18:09.33 | tzanger | so if you noop $VERBOSE1 you get the four variables evaluated at runtime?? |
| 18:11.59 | ManxPower | tzanger: no they are not. |
| 18:12.12 | tzanger | I've never seen dollarsign-space before :-) |
| 18:12.19 | tzanger | but yeah it seems like you're fucked... |
| 18:12.51 | ManxPower | see the bottom of http://pastebin.ca/751761 |
| 18:13.03 | ManxPower | tzanger: It was a random desperate act. |
| 18:13.08 | ManxPower | I don't CARE about the leading $ |
| 18:13.20 | ManxPower | I would remove it, but it still won't work. |
| 18:13.58 | tzanger | right I understand you are experimenting |
| 18:14.05 | ManxPower | if I remove the leading $, then the variables all evaluate at reload time. I want ${VERBOSE} to be set to LITERALLY, NOT EVALUATED variables. |
| 18:14.14 | tzanger | ManxPower: what about \$\{ ? |
| 18:14.22 | tzanger | you tried \${ and $\{ |
| 18:14.38 | tzanger | it looks like you'd unfortunately have to use a macro |
| 18:14.46 | ManxPower | tzafrir_home: the 2nd one is already on the pastebin and you can see what it does. |
| 18:15.08 | ManxPower | basically it looks like you cannot escape chars in the [globals] section at least. |
| 18:15.08 | tzanger | [macro-do-shit] exten => s,1,Verbose(1,${uniqueid} ${etc}) |
| 18:15.11 | tzanger | and that's it |
| 18:16.10 | ManxPower | tzanger: if I have to do that I might well as put "Verbose(1,[${UNIQUEID} ${EXTEN} ${CHANNEL} ${CONTEXT}]: This is a test" which is what I was trying to do. |
| 18:16.21 | tzanger | no |
| 18:16.27 | tzanger | if you use a macro you only define your verbose string once |
| 18:16.32 | ManxPower | I wanted to be able to do "Verbose(1,${VERBOSE} This is a test " |
| 18:16.38 | tzanger | right I understand |
| 18:16.40 | ManxPower | or actually |
| 18:16.42 | tzanger | how is that different from |
| 18:16.48 | ManxPower | "Verbose(${VERBOSE} This is a test " |
| 18:16.56 | tzanger | macro(my-verbose, "This is a test") |
| 18:17.37 | ManxPower | tzanger: I see your solution and it will work. Do you see the bug? |
| 18:17.50 | tzanger | in my solution, or in what you're trying to do? |
| 18:18.00 | ManxPower | your solution should work just fine. |
| 18:18.11 | tzanger | I see your bug and raise you a hackish solution |
| 18:18.17 | ManxPower | the way I tried doing it because \$ does not escape it. |
| 18:18.20 | syle2 | typically in programming if \$ does not negative it you do \\$ |
| 18:18.21 | tzanger | yes I know |
| 18:18.33 | ManxPower | BUT \$ is how README.variables TELLS YOU how to escape something. |
| 18:18.37 | tzanger | asterisk is full of these discrepancies, unfortunately |
| 18:18.46 | ManxPower | syle2: \\$ does not work either |
| 18:19.01 | syle2 | another trick is single quotes |
| 18:19.10 | syle2 | 'take this literally' |
| 18:19.11 | tzanger | syle2: refer to his pastebin |
| 18:19.24 | tzanger | he's tried all the standard ways, and several nonstandard |
| 18:19.26 | ManxPower | syle2: I really wish I had left for pastebin.ca the 20 or so ways of escaping that I tried |
| 18:21.21 | syle2 | why would someone want to escape it to begin with |
| 18:21.26 | ManxPower | What I find funny is that $<space> stops all further evaluation of the line. |
| 18:21.48 | tzanger | ManxPower: I wonder if you can use CUT to remove that $-space then :-) |
| 18:22.04 | ManxPower | syle2: read further back, I already explained it to tzanger |
| 18:22.24 | ManxPower | tzanger: even if you could, it doesn't make it much simplier. |
| 18:22.38 | tzanger | syle2: wouldn't you like to define a string in ONE place and use it in a hundred in order to have a consistent debug string? |
| 18:22.42 | tzanger | ManxPower: why not? |
| 18:23.04 | tzanger | ManxPower: verbose(1,$[CUT($VERBOSE1:2)] "This is a test") |
| 18:23.22 | tzanger | er $[CUT(${VERBOSE1}:2)] |
| 18:23.32 | ManxPower | tzanger: like most people with more than a few calls on the system, I'm being flooded with information on the CLI. I'm trying to Verbosify my dialplan. |
| 18:23.59 | tzanger | ManxPower: I know, I've been there, and I do it the ugly way :-) |
| 18:24.04 | tzanger | although now I think I'll use the macro way |
| 18:24.06 | ManxPower | tzanger: mostly because I bet the bug will be fixed in the future and then it will screw up everything |
| 18:24.17 | tzanger | well the macro will work in 1.2 and 1.4 |
| 18:24.29 | ManxPower | no, the CUT I mean |
| 18:24.37 | ManxPower | i.e. the $<space> bug. |
| 18:24.45 | tzanger | indeed |
| 18:24.49 | Corydon76-dig | ManxPower: that's already fixed in the latest version |
| 18:24.55 | ManxPower | so I don't want to rely on that. |
| 18:25.04 | tzanger | I dunno I'd just use the macro I think... it's not perfect but it works and is likely to work in future |
| 18:25.18 | ManxPower | Using a macro is what I'll end up doing. |
| 18:25.24 | tzanger | Corydon76-dig: asteriskNOW is the gui for asterisk that comes "standard" with asterisk 1.4+? |
| 18:25.37 | ManxPower | calling macros from macros is annoying anyway. |
| 18:25.49 | tzanger | yes, that's why GoSub came around |
| 18:25.52 | tzanger | but it's not in 1.2 |
| 18:26.32 | ManxPower | gosub is in 1.2, it just can't take additional parameters |
| 18:26.54 | tzanger | ah |
| 18:27.16 | ManxPower | If the macro [macro-fred] runs macro [macro-betty] I wonder what the value of MACRO_EXTEN would be in [macro-betty] |
| 18:27.22 | ManxPower | I guess I'll find out. |
| 18:27.39 | Corydon76-dig | ManxPower: I think you want to use EVAL, actually |
| 18:27.59 | ManxPower | Corydon76-dig: I would if it worked. |
| 18:28.09 | Corydon76-dig | Backslash your dollar signs and EVAL the result at runtime |
| 18:28.34 | Corydon76-dig | or in 1.2, it would need to be \\\$ |
| 18:28.41 | ManxPower | This is a result of EVAL: -- Executing NoOp("Zap/1-1", "$ ${UNIQUEID} ${EXTEN} ${CHANNEL} ${CONTEXT}") in new stack |
| 18:29.26 | Corydon76-dig | That's odd |
| 18:29.54 | ManxPower | Corydon76-dig: VERBOSE1=\\\${UNIQUEID} \\\${EXTEN} \\\${CHANNEL} \\\${CONTEXT} |
| 18:29.54 | ManxPower | <PROTECTED> |
| 18:30.13 | Corydon76-dig | What version are you using? |
| 18:30.18 | ManxPower | 1.2, of course. |
| 18:31.19 | ManxPower | Anyway, the discussion is moot since tzanger's suggestion of using a macro. |
| 18:31.42 | ManxPower | I understand nobody in the dev community cares about 1.2 anymore. |
| 18:31.59 | Corydon76-dig | Sure we do... we still post security fixes for 1.2 |
| 18:32.23 | ManxPower | Corydon76-dig: that doesn't show you care, just that you are afraid of lawsuits. |
| 18:32.26 | Corydon76-dig | but 1.2 is at its end of life |
| 18:32.34 | Corydon76-dig | Hah, lawsuits? |
| 18:32.42 | Corydon76-dig | check the warranty |
| 18:32.57 | ManxPower | *nod* The tradition of deprecating a version about the time it becomes usable for most people continues. |
| 18:33.14 | ManxPower | I expect that 1.6 will be released about the time 1.4 becomes stable enough. |
| 18:33.27 | Corydon76-dig | 1.6 is about to be released |
| 18:33.38 | Corydon76-dig | or at least, the first beta is |
| 18:33.52 | tzanger | it is frustrating... I mean I was never a fan of 1.2, but I use 1.4 a fair bit, and the stability of it is... not practical. it seems it is better for me to find a verson of svn trunk that is mostly good and stick with that |
| 18:34.00 | ManxPower | Corydon76-dig: *nod* Expected since 1.4 seems to be getting close to the production quality my users expect. |
| 18:34.44 | Corydon76-dig | And the 1.6 releases will be a lot closer in functionality to 1.4 |
| 18:35.01 | Corydon76-dig | All it really is is a new development model |
| 18:35.15 | tzanger | *nods* it's growing pains |
| 18:35.26 | file | and as for maintaining 1.2... there was simply not enough people/resources to keep it going |
| 18:35.41 | file | and there has been talk on the users list about people doing it, but nobody has done so |
| 18:35.44 | Corydon76-dig | closer to the Linux kernel... which means that we will no longer have a huge amount of time being new features and new releases |
| 18:36.15 | Corydon76-dig | Steve Totaro has said he will, but I haven't seen anything from him yet |
| 18:36.31 | Corydon76-dig | I think he underestimates the amount of attention that it takes |
| 18:36.42 | ManxPower | 1.2 should not need much work unless you are trying to backport features from a later version. |
| 18:36.50 | ManxPower | and that is not going to improve 1.2's stability. |
| 18:36.52 | file | that is what people want, plus bug fixes |
| 18:37.17 | Corydon76-dig | Yes, but bug fixes are what take all the attention |
| 18:37.30 | Corydon76-dig | It would be more than a single person's full time job to maintain 1.2 |
| 18:37.54 | ManxPower | The open source model of development seems to simply be contrary to the telcom industry's expectation of stability no matter what. |
| 18:37.56 | syle2 | you can;t expect developpers to maintain a million copies of old branches, if you want to stay up to date you should be in the stable branch a revision behind of the devel branch |
| 18:38.13 | ManxPower | syle2: not a million, THREE. |
| 18:38.17 | ManxPower | 1.2, 1.4, trunk |
| 18:38.33 | Qwell | might as well maintain 1.0 too |
| 18:38.36 | ManxPower | and 1.2 should not be needing much work, other than the bug fix here and there. |
| 18:38.37 | Qwell | and pre-1.0 CVS |
| 18:38.43 | Corydon76-dig | And now we're headed to THREE... 1.4, 1.6, and trunk |
| 18:39.53 | Corydon76-dig | except that we'll continue to post security fixes to 1.2, so it's really FOUR |
| 18:40.02 | tzanger | well I think it is silly to think you need to maintain 1.0 |
| 18:40.20 | tzanger | but many people use 1.2 due to stability that you simply CANNOT argue that 1.4 oes not have |
| 18:40.23 | Corydon76-dig | tzanger: yet we hear from people all the time on -users who are still running 1.0.9 |
| 18:40.26 | ManxPower | I suspect once 1.6 is out Digium will end up deciding to make 1.2 totally unmaintained. |
| 18:40.58 | tzanger | so to try and force the issue... well it seems like it's a bit like putting the cart before the horse... either get 1.4 stable or keep maintianing the only stable version you do have |
| 18:41.14 | ManxPower | tzanger: my thoughts exactly. |
| 18:41.28 | syle2 | it might very well be possible in the future, but for now asterisk has undergone big changes, making fixes in devel branch is only easily added to last stable branch typically, one day when code evens out i;m sure they will maintain 2 stable branches |
| 18:41.36 | ManxPower | tzanger: but nobody other than users seems to admit that 1.4 is not as stable as 1.2 for many things. |
| 18:42.11 | syle2 | but its also insulting to the developpers to be working on new devel branch and people not to upgrade to their last stable typically |
| 18:42.30 | tzanger | syle2: if the devs find it insulting then get the current stuff STABLE so we *CAN* upgrade |
| 18:42.34 | file | and we know why it's not as stable, which is what the new release and development scheme is going to address |
| 18:42.54 | tzanger | it's insulting to your users to assume that they are able or willing to put up with crashes and other instability in production environments |
| 18:42.58 | Qwell | it's not stable, because nobody used it. catch 22 |
| 18:43.00 | syle2 | its hard to make things stable when not enough people reports bugs |
| 18:43.13 | file | making it easier to test as we put things in step by step |
| 18:43.17 | ManxPower | file: because almost everyone wants to work on TRUNK and nobody wants to work on anything other than cool, new features. |
| 18:43.29 | tzanger | Qwell: not true. there are dozens and dozens of bugreports for 1.4. some of them are still present |
| 18:43.29 | file | ManxPower: I'm insulted by that |
| 18:43.37 | Qwell | ManxPower: when was the last time you saw anybody at Digium add a new feature? |
| 18:43.38 | file | ManxPower: I have not worked on a new feature in almost a month |
| 18:43.51 | file | lots of the Digium folk have given up working on new features to do bugs |
| 18:43.56 | Cresl1n | actually, it's kind of a shame |
| 18:43.57 | tzanger | file: that's because you're canadian. you get the leftovers from the americans. :-) |
| 18:44.02 | Cresl1n | in some ways |
| 18:44.11 | ManxPower | file: because they want to, or because their boss tells them to? |
| 18:44.12 | Corydon76-dig | My time is spent evenly between bugs and new features |
| 18:44.33 | file | ManxPower: because we want to and we realize that people want Asterisk to be stable and the bugs fixed |
| 18:44.41 | Corydon76-dig | and many of my new features are termed things that users expected should have worked anyway |
| 18:44.41 | Cresl1n | besides ManxPower, we won't have bugs to work on until people start using 1.4 |
| 18:44.42 | ManxPower | file / Qwell it is human nature to want to work on new things. |
| 18:44.50 | syle2 | new features are fun, maintaining new features is a different story |
| 18:44.54 | Cresl1n | like Qwell said, it's a catch 22 |
| 18:45.15 | ManxPower | just how many open bugs ARE there for 1.4? |
| 18:45.34 | Corydon76-dig | There are quite a few |
| 18:45.43 | Cresl1n | before we ask that, how many open bugs are for 1.4 that you have submitted |
| 18:45.49 | ManxPower | So users ARE reporting bugs then. |
| 18:45.50 | Cresl1n | (not trying to make the sound confronational) |
| 18:46.00 | Corydon76-dig | Many times it is difficult to get the kind of feedback that we need to diagnose, though |
| 18:46.01 | Cresl1n | it's just that we need people to submit them |
| 18:46.23 | ManxPower | Cresl1n: it is a hot topic. I have not submitted any 1.4 bugs because I do not have enough confidence in 1.4 to run 1.4. |
| 18:46.36 | Cresl1n | :-) |
| 18:46.39 | Cresl1n | my point exactly |
| 18:46.53 | Cresl1n | how can we get over that hump |
| 18:46.55 | Corydon76-dig | When users tell us that something crashed, but they can't help us debug the problem, it's quite frustrating |
| 18:46.56 | Cresl1n | that's the question |
| 18:46.57 | ManxPower | In the past month or so, people on #asterisk seem to be only experiencing oddball, hard to diagnose bugs, rather than "oh that's a bug, upgrade to the latest 1.4" |
| 18:47.48 | Corydon76-dig | Probably because we got all of the low hanging fruit already |
| 18:47.50 | Cresl1n | ManxPower: what kinds of things can we do to make you (and other users like you) update to 1.4 so we can start the REAL debugging? |
| 18:47.59 | Cresl1n | in all seriousness |
| 18:48.05 | Qwell | Cresl1n: fix all the bugs ;) |
| 18:48.06 | Cresl1n | is there something we can do better |
| 18:48.07 | Cresl1n | :-) |
| 18:48.10 | Cresl1n | no, no |
| 18:48.16 | Cresl1n | I'm really trying to brainstorm here |
| 18:48.18 | Corydon76-dig | Catch-22 |
| 18:48.26 | Cresl1n | we've got quite a chicken and egg problem |
| 18:49.10 | Cresl1n | somehow we've got to make it more desireable to update |
| 18:49.15 | ManxPower | Cresl1n: I watch the -users mailing list and #asterisk channel. When people are no longer having significant issues with 1.4 I'll consider upgrading. There is another issue of course. That is the CUSTOMER does not want me upgrading all their PBXs every 6 - 12 months. |
| 18:49.39 | ManxPower | they don't want the loss in stability and they do not want to see my consulting bills. |
| 18:49.41 | Cresl1n | That second issue is something I think we can't control |
| 18:50.03 | Qwell | well, if we were Cisco, we would have a release twice a year |
| 18:50.04 | ManxPower | Cresl1n: not all the problems with 1.4 have to do with Digium and the developers. 8-) |
| 18:50.09 | Cresl1n | The first is something that we can't directly control :-) |
| 18:50.13 | Qwell | then you would have to wait 6 months for a bug to be fixed |
| 18:50.21 | Cresl1n | but we can indirectly do something about with more testing by users |
| 18:50.22 | ManxPower | Cresl1n: are you familiar with phpGroupWare? |
| 18:50.22 | Qwell | that's the last thing we want |
| 18:50.28 | Corydon76-dig | or 3 years, in the case of some companies |
| 18:50.36 | Cresl1n | I'm not |
| 18:50.49 | Qwell | Corydon76-dig: referring to Windows? if so, then you probably won't even have you bug fixed :p |
| 18:51.15 | Corydon76-dig | Qwell: if the company won't upgrade but every 3 years... |
| 18:52.13 | Cresl1n | ManxPower: why do you ask? |
| 18:52.20 | ManxPower | Cresl1n: A troupe of clowns high on PCP could do a better job managing releases. Digium never got that bad, and they have been improving for a long time, but phpGroupWare is an example of most everything that can go wrong with releases. |
| 18:52.40 | ManxPower | they had at least TWO forks of the code. |
| 18:53.32 | syle2 | well technically you should provide incentive features for them to upgrade and make some money doing it |
| 18:53.38 | ManxPower | Cresl1n: did you see the thread on -users about NOBODY seeming to be able to get voicemail IMAP working in 1.2? |
| 18:54.18 | ManxPower | Cresl1n: Part of the problem is simply the history if Digium taking 6 months from a release to finally get to a release users can count on. |
| 18:54.47 | Cresl1n | that's what 1.6's goal is to fix |
| 18:54.56 | ManxPower | Cresl1n: I REALLY hope it is successful. |
| 18:54.57 | Cresl1n | 1.4 zaptel has already moved to this model |
| 18:55.19 | Cresl1n | for example, zaptel trunk is for the most part deprecated at the moment |
| 18:55.23 | file | it'll only be successful if we can get testing |
| 18:55.27 | Cresl1n | 1.4 is where the changes go in |
| 18:55.42 | Cresl1n | file: I think it'll be more successful |
| 18:55.50 | file | Cresl1n: I hope so |
| 18:55.51 | Cresl1n | it'll be easier to find changes that break things |
| 18:56.05 | ManxPower | Cresl1n: If 1.6 does not have lots of bugs I suspect I'll just go 1.2 directly to 1.6 |
| 18:56.15 | Cresl1n | since there won't be any kind of the same kind of 6monts-1yr spread between major releases |
| 18:57.29 | Cresl1n | 1.6 will have the same issues as 1.4 initially, IMHO |
| 18:57.31 | ManxPower | Cresl1n: there are two conflicting issues here. On the one hand, new features means new bugs. On the other hand, we don't want what happened to 1.0/1.2 to happen again (everyone was using trunk because it had so many useful features) |
| 18:57.45 | Cresl1n | since we're looking at a ~1-1.5 year release on that |
| 18:57.45 | Qwell | <ManxPower> Cresl1n: did you see the thread on -users about NOBODY seeming to be able to get voicemail IMAP working in 1.2? |
| 18:57.53 | Cresl1n | but in the long term it should be better |
| 18:57.55 | Qwell | ^^ That may be because IMAP doesn't exist in 1.2 |
| 18:58.01 | Cresl1n | ah |
| 18:58.05 | Cresl1n | well, that would do it |
| 18:58.07 | ManxPower | Qwell: sorry, I meant to say 1.4 |
| 18:58.14 | Qwell | there are plenty of people using it |
| 18:58.40 | Cresl1n | Mark M probably should have been on that thread |
| 18:58.46 | ManxPower | See Re: [asterisk-users] Is anyone successfully using IMAP storage |
| 18:58.55 | file | doesn't mean it doesn't take effort to get it working |
| 18:59.04 | ManxPower | Re: [asterisk-users] IMAP usage with Asterisk |
| 18:59.09 | Cresl1n | yeah, that's something we can do better though |
| 18:59.16 | Cresl1n | better mailing list participation on our part |
| 18:59.24 | ManxPower | and Re: [asterisk-users] Poll: Asterisk IMAP feedback |
| 19:00.07 | Qwell | bbl, food |
| 19:00.14 | Cresl1n | cya Qwell |
| 19:22.27 | *** join/#asterisk-dev mitcheloc (n=mitchel@ppp-67-126-240-11.dsl.irvnca.pacbell.net) |
| 19:30.00 | blitzrage | I've submitted lots of bugs for 1.4, and had them fixed very fast. I've always been extremely impressed by the speed the developers resolve my bug issues |
| 19:30.25 | blitzrage | now running 1.4 in production with no known issues |
| 19:30.49 | blitzrage | (in my environment obviously... you're milage will vary) |
| 19:30.57 | blitzrage | your* |
| 19:31.04 | tzanger | yeah but you're biased |
| 19:31.18 | tzanger | and your opinion is discounted just because you're nordic. :-) |
| 19:31.32 | ManxPower | blitzrage: you also don't run it in a corporate enviroment. |
| 19:31.55 | blitzrage | that's my advantage I guess |
| 19:32.05 | ManxPower | blitzrage: BTW, how many phones do you have on your largest PRODUCTION box? |
| 19:32.53 | ManxPower | Do you use ChanSpy or Monitor on all calls? |
| 19:33.16 | blitzrage | well... phones register to OpenSER... and we do vPBXs and trunks to people... so hard to say... but maybe 1000+? |
| 19:33.16 | blitzrage | sometimes |
| 19:33.18 | blitzrage | lightly |
| 19:33.22 | blitzrage | I found a few bugs there, and they got fixed |
| 19:33.28 | *** join/#asterisk-dev dlynes_ (n=dlynes@d154-20-34-39.bchsia.telus.net) |
| 19:33.28 | blitzrage | vPBX system for an ITSP is what I built |
| 19:34.05 | blitzrage | 4 asterisk boxes clustered behind OpenSER in 2 locations |
| 19:34.21 | blitzrage | (each location has an OpenSER + heartbeat backup with 2 Asterisk boxes behind it) |
| 19:34.45 | ManxPower | so you really don't have ANY phones connected to Asterisk. |
| 19:34.55 | blitzrage | not directly to asterisk -- like I said above |
| 19:34.58 | ManxPower | I imagine that would simplify things considerably. |
| 19:35.06 | ManxPower | (from Asterisk's point of view) |
| 19:35.18 | blitzrage | it doesn't have registrations, but all calls go through Asterisk sitll |
| 19:35.55 | ManxPower | ITSPs have different issues than corporate stuff. |
| 19:36.04 | blitzrage | I don't disagree with that statement |
| 19:36.06 | ManxPower | If 2 calls drop, I get yelled at. |
| 19:36.20 | ManxPower | in an ITSP's world, dropping a couple of calls seems pretty common. |
| 19:36.31 | ManxPower | Also in an ITSP users can't walk into your office to complain. |
| 19:37.42 | blitzrage | well... no one walks into my office -- I work from home |
| 19:37.56 | blitzrage | and I'd like to keep it that way, unless it's some hot chick |
| 19:37.57 | blitzrage | :) |
| 19:38.03 | blitzrage | then I'll make an exception |
| 19:40.32 | blitzrage | hmmm.... Qwell has the right idea... food time! |
| 19:42.36 | *** join/#asterisk-dev agx (n=badpengu@81-174-47-86.dynamic.ngi.it) |
| 19:44.08 | agx | my telco is sending a strange busypattern on hangup seems a congestion but instead of 200,200 it looks like 220,195: there is a way to track this in dsp.c or from the recorded audio of audacity? |
| 19:46.34 | mvanbaak | 1.0 is very stable |
| 19:47.20 | mvanbaak | agx: you can alter that kind of stuff in indications.conf |
| 19:50.19 | agx | mvanbaak, indications are ok; i've just have problem with chan_zap recognizing the hangup tone |
| 19:51.35 | mvanbaak | ah |
| 19:51.41 | mvanbaak | my zap experience is very limited |
| 19:54.08 | ManxPower | agx: busydetect and callprogress don't work well at all |
| 19:54.13 | ManxPower | don't use them |
| 19:59.47 | *** join/#asterisk-dev jameswf-home (n=that@ip72-204-222-2.ph.ph.cox.net) |
| 20:02.51 | agx | ManxPower really? so for FXO i've to use a gateway? |
| 20:05.47 | Cresl1n | agx: use kewlstart |
| 20:06.30 | agx | Cresl1n, signalling=fxs_ks already using it ; i just need to tune busy pattern a little i suppose |
| 20:06.46 | tzafrir_home | kewlstart ? in Italy? or maybe polarity? |
| 20:06.49 | Cresl1n | well, you can set busycount to something high |
| 20:07.02 | tzafrir_home | try hanguponpolarityswitch=yes |
| 20:07.07 | Cresl1n | but if it's not working right, that's not going to help very much |
| 20:07.11 | agx | well i've found a strange problem recording with ztmonitor |
| 20:07.45 | agx | on 1st call the audio is correct; on 2nd call there is a "return" over the channel (i mean a little TX overwriting the RX) ... this could make dps.c busydetect mad? |
| 20:08.41 | tzafrir_home | ztmonitor is independent of Asterisk |
| 20:09.06 | jmls | we run on 1.4 trunk - are very happy, with the exception of my bloody proprietry odbc driver. That bugger crashes all the time |
| 20:09.42 | jmls | 150+ phones, jabber, queues, dynamic meetme, mixmonitor 90+ zap channels |
| 20:09.52 | agx | http://rapidshare.com/files/65620841/prova1.zip.html |
| 20:10.03 | jmls | Corydon76-dig: btw, func_curl really really rocks |
| 20:10.16 | tzafrir_home | any idea how to get "bdfname" (e.g: "elf32-i386") from autoconf? |
| 20:10.23 | jmls | can do most of my odbc stuff faster in curl than through odbc ;) |
| 20:10.27 | tzanger | what the heck's prova1? |
| 20:10.35 | agx | could it be this the problem? i've uploaded a zipped wave of what happen; 1st call is ok; 2nd call i can hear in background the IVR overlapping the telco (maybe Zmonitor bug? ) |
| 20:10.54 | tzafrir_home | agx, please use a simple pastebin. They're much simpler to work with: |
| 20:10.57 | tzafrir_home | ~pb |
| 20:10.58 | jbot | A Pastebin is a place to paste your stuff without flooding the channel. Here are links to a few : http://www.pastebin.com , http://pastebin.ca , http://channels.debian.net/paste , http://paste.lisp.org , http://www.rafb.net/paste |
| 20:11.09 | agx | i know pastebin... but its a wave :) |
| 20:15.37 | tzafrir_home | anyway, do try enabling polarity reversal . If it happens to work, it'll make life simpler |
| 20:15.48 | agx | in Italy no one offer it |
| 20:18.08 | agx | if someone can pointing me out how to get the frequency and silence with audacity (i've recorded the audio) i can then fix it myself setting busypattern= to the excat value |
| 20:21.55 | tzafrir_home | audacity has a frequency spectrum display |
| 20:21.58 | tzafrir_home | I forgot its name |
| 20:22.36 | tzafrir_home | To meassure time mark it and look at the status line |
| 20:23.18 | agx | ah, wait, maybe i'm totally wrong :busypattern is frequency,duration or duration_tone,duration_silence ? |
| 20:24.27 | mvanbaak | movie time |
| 20:24.30 | mvanbaak | latero |
| 20:29.04 | *** join/#asterisk-dev davevg-btwtech (n=davevg-b@nj-67-76-177-147.sta.embarqhsd.net) |
| 20:40.26 | Qwell | agx: <duration on>,<duration off> |
| 20:43.20 | agx | http://www.pastebin.ca/751894 |
| 20:43.50 | agx | can you look at this? from the wave file it should be 200,200 but the dps.c detect diffrent values ... uhm... what could it be? |
| 21:10.06 | *** part/#asterisk-dev Cresl1n (i=matt@nat/digium/x-33e8fe279b85ca31) |
| 21:16.07 | jameswf-home | tzafrir_home: You have a deb distro right? |
| 21:16.28 | tzafrir_home | right |
| 21:17.05 | jameswf-home | is it debian or ubuntu |
| 21:17.18 | tzafrir_home | Debian |
| 21:17.54 | tzafrir_home | Anyway, I believe Ubuntu packagers mostly use pkg-voip stuff as well |
| 21:17.57 | jameswf-home | any direction on documentation, I wanna to try this with ubuntu-server.. |
| 21:18.17 | jameswf-home | a self installer with live option.. |
| 21:18.26 | tzafrir_home | what version? |
| 21:18.48 | jameswf-home | probably bleeding edge but maybe edgy |
| 21:19.02 | tzafrir_home | you want to create one? |
| 21:19.30 | jameswf-home | yeah I have done the redhat thing still am) but in reality I am not a redhat person |
| 21:19.57 | jameswf-home | didnt use redhat before asterisk.. |
| 21:20.16 | tzafrir_home | I don't really know Ubuntu's installer |
| 21:20.43 | tzafrir_home | I figure you can find instructions on customizing it to add a few pre-set packages |
| 21:21.02 | tzafrir_home | you can probably use pkg-voip's repo |
| 21:21.21 | tzafrir_home | Though I prefer to rebuild from them and do some testing |
| 22:05.09 | *** join/#asterisk-dev davevg-btwtech (n=davevg-b@nj-67-76-177-147.sta.embarqhsd.net) |
| 23:33.29 | *** join/#asterisk-dev zeroHalo-BB (n=zeroHalo@64.78.21.135) |
| 23:34.37 | *** join/#asterisk-dev moy (n=moyhu@189.169.56.210) |
| 23:35.43 | *** join/#asterisk-dev syle (n=blah@unaffiliated/syle) |
| 23:55.45 | snuff-home | mm murf.. that is the linked list vs b-tree.. for extensions/contexts |