| 00:33.29 | *** join/#asterisk-dev lister_ (~lister@scarda1.lnk.telstra.net) |
| 01:12.32 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 01:51.27 | *** join/#asterisk-dev moy_ (~moy@69.158.118.39) |
| 03:51.38 | *** join/#asterisk-dev otherwiseguy (~terry@adsl-67-65-45-231.dsl.ksc2mo.swbell.net) |
| 04:02.33 | *** join/#asterisk-dev DocAwesome (~DocAwesom@asterisk/documenteur-extraordinaire/blitzrage) |
| 04:02.33 | *** mode/#asterisk-dev [+o DocAwesome] by ChanServ |
| 04:53.08 | *** join/#asterisk-dev mickecarlsson (~Micke@h10n3c1o1101.bredband.skanova.com) |
| 05:07.52 | *** join/#asterisk-dev otherwiseguy (~terry@69.76.217.40) |
| 05:24.03 | *** join/#asterisk-dev irroot (~irroot@pbx.distrotech.co.za) |
| 05:30.04 | *** join/#asterisk-dev tzafrir (~tzafrir@212.179.75.202) |
| 05:30.04 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 06:16.10 | *** join/#asterisk-dev schmidts (~schmidts@Lo20-rt01.lm33.sil.at) |
| 06:16.33 | schmidts | good morning |
| 06:18.17 | *** join/#asterisk-dev otherwiseguy (~terry@69.76.217.40) |
| 06:22.04 | irroot | hi there morning |
| 07:20.20 | *** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:803e:c38:8e35:3720) |
| 08:12.35 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 08:12.35 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 08:26.19 | *** join/#asterisk-dev oej (~olle@ns.webway.se) |
| 08:26.19 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 08:29.05 | oej | Hello folks |
| 08:29.05 | irroot | oej yo there |
| 08:29.18 | oej | looks down |
| 08:29.23 | irroot | get my coments on your s@default bits |
| 08:29.36 | oej | ok, listening |
| 08:30.00 | schmidts | morning oej |
| 08:30.05 | irroot | need to add it to extensions.conf sample and UPGRADE file the n00bs will blow it |
| 08:33.42 | oej | Why extensions.conf? I don't see a natural place for it there. UPGRADE would work. |
| 08:33.57 | oej | The extensions.conf stuff would be important for change to the originate app |
| 08:34.03 | oej | Thinking |
| 08:34.28 | irroot | in the [default] section think put a reason that exten => s, is not a good idea and in the past it would come here but does not any more |
| 08:35.51 | oej | The question is when they would come there? Apart from originate, I haven't found any apps that end up there (in the svn). Apps on the outside might though. |
| 08:35.58 | irroot | also did a check on chan_misdn it will not be affected as it sends a '' or 's' both cases will be covered by having a s in the context |
| 08:37.15 | irroot | im thinking that n00bs set up there dialplans see it magicially work and rely on it for months / years they may come back to look at this config as a template or for people starting out to avoid the issue going forward |
| 08:37.35 | irroot | or worse somone folloing advice from voip-info |
| 08:39.49 | oej | I follow you. |
| 09:25.28 | *** join/#asterisk-dev pnlarsson (~niklas@fw1.gml.g.icnet.infracom.se) |
| 10:59.40 | *** join/#asterisk-dev Dovid (Dovid@office.mypbxmanager.net) |
| 10:59.48 | Dovid | how do I find this in the form of a patch: 2011-08-16 15:06 +0000 [r332021-332026] Matthew Nicholson <mnicholson@digium.com> |
| 11:03.37 | irroot | svn diff -r 332021:332026 |
| 11:03.54 | Dovid | i guess i need to grab svn for tha t;) |
| 11:03.56 | Dovid | that* |
| 11:04.04 | Dovid | iroot: Any way to do this on the web ? |
| 11:04.07 | irroot | could use svnview |
| 11:04.45 | Dovid | or do you think i should go with rc7 ? right now i am on 1.8.60 |
| 11:07.55 | irroot | Dovid go 7-rc1 ive rolled it out and there so far almost no reversions |
| 11:08.16 | irroot | rc2 will be out soon [hours/days] |
| 11:09.11 | Dovid | iroot: What is the diff betweeb 1.8.6 and 7-rc-1? i guess the way to see the changes is in the changelog? |
| 11:10.44 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 11:10.44 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 11:10.45 | irroot | yip |
| 11:10.54 | irroot | OJ for the boss ?? :P |
| 11:12.32 | kpfleming | boss? meh. not at 6AM. |
| 11:13.30 | irroot | lol thats the way to rock |
| 11:29.16 | oej | Good morning, kpfleming |
| 11:30.11 | kpfleming | yes, i hope so |
| 11:30.16 | kpfleming | a bit rainy here, but that's not terrible |
| 11:44.54 | file | curls up in a corner and cries |
| 11:48.42 | oej | sends a hug to file |
| 11:48.44 | Dovid | here in the middle east we go 6 months with out rain. i LOVE it |
| 11:50.55 | oej | I love it if we go 6 hours without rain in September |
| 11:51.36 | Dovid | haha |
| 11:52.00 | irroot | Dovid yeah but bet you got more sand than me :P |
| 11:59.48 | Dovid | iroot: Actually not. I am not in the desert. but yea a bit more than you |
| 12:00.28 | irroot | was in the subtropics last week rather too little rain than too much humidity |
| 12:03.07 | Dovid | Florida sux |
| 12:03.11 | Dovid | atleast in the summer |
| 12:03.20 | Dovid | didn't know this was #weather ;) |
| 12:07.54 | leifmadsen | Dovid: well it's prior to 9am for many in north america, so this channel gets a little silly |
| 12:08.23 | oej | Are you excusing us europeans to be silly? leifmadsen! |
| 12:08.43 | Dovid | lol |
| 12:12.50 | irroot | the africans object and concur europeans are silly |
| 12:17.45 | *** join/#asterisk-dev tamiel (~tamiel@213.30.183.226) |
| 12:17.52 | leifmadsen | oej: nope, it just doesn't matter what time of day it is for you :) |
| 12:18.06 | oej | leifmadsen: That is correct ;-) |
| 12:41.44 | irroot | leifmadsen rc2 official or just cut |
| 12:42.54 | *** join/#asterisk-dev Fritz09 (~Adium@pop1-2551.catv.wtnet.de) |
| 12:44.39 | leifmadsen | irroot: it'll go out today, I just had to do all the signing stuff and all that, so it's always a delay, and if it happens near the end of the day, I'm away from my desk |
| 12:45.11 | leifmadsen | I start about 3 hours earlier than most of Digium, so I'm usually out earlier than others too :) |
| 12:45.13 | irroot | no prob ive pulled it from svn |
| 12:45.25 | *** join/#asterisk-dev oej_ (~olle@ns.webway.se) |
| 12:45.25 | *** mode/#asterisk-dev [+o oej_] by ChanServ |
| 12:45.26 | leifmadsen | (and I had dodgeball last night) |
| 12:46.03 | irroot | bruised much ?? or is that code for some newly married thing ?? |
| 12:47.38 | leifmadsen | irroot: lol no, I'm not bruised (in this league they use smaller foam balls instead of those big rubber ones you see usually). I pulled a hamstring a little bit last night, but it's not too bad today. Just means I'm out of shape :( |
| 12:50.36 | tzanger | morning |
| 12:59.32 | leifmadsen | tzanger: yo |
| 13:01.45 | *** join/#asterisk-dev mvanbaak (~michiel@asterisk/contributor-and-bug-marshal/mvanbaak) |
| 13:01.45 | *** mode/#asterisk-dev [+o mvanbaak] by ChanServ |
| 13:05.23 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-indmnnkbbgerzuud) |
| 13:07.31 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-pgokadmracvlfsbc) |
| 13:07.31 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 13:13.57 | oej | hello all, welcome to today's discussion. |
| 13:44.27 | acidfoo | good morning ;) |
| 13:50.08 | oej | I opened an issue about strictrtp in rtp.conf. Why is it "no" by default? |
| 13:51.26 | irroot | oej what the down sides ?? |
| 13:51.51 | oej | The up side of changing it is that you're less vulnerable to attacks. |
| 13:52.24 | oej | The downside is that if you have systems that start sending without re-inviting, audio will disappear. This applies to Asterisk 1.2 and older - and other systems that are working the same way. |
| 13:53.01 | irroot | that is a pain |
| 13:56.03 | *** join/#asterisk-dev anonymouz666 (~anonymouz@187-28-37-118.poolip.RJO.embratel.net.br) |
| 13:58.12 | oej | Define "pain" - why |
| 14:00.18 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 14:00.18 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 14:06.53 | irroot | oej what is dependent on early audio ?? |
| 14:10.11 | irroot | if there are only fringe users im highly in favor |
| 14:11.53 | oej | early media is in SDP so that is not affected. |
| 14:12.18 | *** join/#asterisk-dev otherwiseguy (~terry@cpe-69-76-217-40.kc.res.rr.com) |
| 14:12.28 | oej | This is if you have a device that injects audio to an RTP socket without being in the SIP dialog |
| 14:12.39 | oej | Or being part of the SDP offer/answer |
| 14:13.42 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 14:13.42 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 14:18.35 | irroot | oej so the avg user will not be affected |
| 14:18.48 | irroot | make it so no 1 |
| 14:19.13 | oej | I don't think so, but want to hear what the rest of you say. |
| 14:30.42 | *** join/#asterisk-dev The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 14:30.42 | *** mode/#asterisk-dev [+o The_Boy_Wonder] by ChanServ |
| 14:35.16 | acidfoo | Anyone is aware how the AstriDevCon is organised ? I mean, do we have to put our name on a list or we just arrive there with our AstriCon pass and it's enough ? |
| 14:35.17 | acidfoo | thank you |
| 14:36.47 | russellb | in the past it has been you just show up |
| 14:36.53 | Qwell | O.o |
| 14:37.09 | Qwell | We've always had an invitationy/approval process, sir. |
| 14:37.23 | Qwell | or maybe that was just Atlanta. |
| 14:37.23 | russellb | hmmmmm |
| 14:37.25 | kpfleming | not this time |
| 14:37.29 | acidfoo | russellb, good, kpfleming just said the same |
| 14:37.31 | russellb | maybe you're right, i don't know what i'm talking about |
| 14:37.39 | russellb | goes back into his cave |
| 14:38.21 | kpfleming | i'll post something to the lists about the lack of invitations being necessary this time |
| 14:43.38 | *** join/#asterisk-dev bspidel (~IceChat77@63.134.128.4) |
| 14:45.08 | bspidel | Is there a reason why /usr/sbin/asterisk would have a different size than .../main/asterisk? |
| 14:45.27 | kpfleming | not an obvious one, no |
| 14:46.06 | Corydon76-home | Sure, because you altered flags and recompiled since the last time you did a 'make install' |
| 14:46.36 | bspidel | so a make without install would do it. |
| 14:46.44 | Corydon76-home | Yes |
| 14:47.04 | kpfleming | well, yes, possibly |
| 14:47.26 | Corydon76-home | If the sources and flags were the same, though, the compile would produce the identical binary... A compile is a deterministic process. |
| 14:47.51 | bspidel | I have production system with about 10 source trees and am trying to determine which was last installed |
| 14:48.01 | kpfleming | not quite... gcc includes some random seed stuff and it causes slight variations in the headers of the binary. there can also be date/time stamps in the binaries. |
| 14:48.08 | kpfleming | the object code would not differ, though. |
| 14:48.36 | Corydon76-home | Heh. Fair enough. |
| 14:48.43 | bspidel | one source tree has about 20k size difference but has date within a minute |
| 14:49.00 | kpfleming | this gets brought up on gcc-help every now and again, as people are trying to test automated build systems and wonder why they don't get identical binaries. |
| 14:49.18 | Corydon76-home | bspidel: Subversion tree versus source package? |
| 14:49.44 | bspidel | source package |
| 14:50.25 | irroot | Corydon76-home added some messages as we spoke about https://reviewboard.asterisk.org/r/1442/ |
| 14:51.55 | bspidel | I am concerned because I want to add another and need to be able to restore to previous if something goes wrong and now I am not certain that installing from other source will give me what is currently running |
| 14:52.58 | irroot | bspidel what i do is install it into a diff destdir and then us those files as list to tar and backup all files that will be overwriten then continue |
| 14:55.39 | bspidel | irroot, good idea |
| 14:58.30 | Corydon76-home | You could even create a body of symlinks that point into various DESTDIRs |
| 14:59.56 | kpfleming | a corpus, if you will |
| 15:05.27 | bspidel | Quit |
| 15:21.01 | kpfleming | oej: i don't think the strictrtp change really needs to go on ReviewBoard :-) |
| 15:23.50 | Qwell | actually.. |
| 15:24.01 | Qwell | I do have a comment! |
| 15:26.10 | irroot | oej dont forget CHANGES file ... |
| 15:27.10 | oej | Irroot: Thanks. |
| 15:27.18 | oej | kpfleming: Just to follow procedure :-) |
| 15:27.41 | kpfleming | what procedure states that a 2-line change needs to go on ReviewBoard? |
| 15:27.58 | kpfleming | ReviewBoard is for *code review*, not discussion and consensus gathering |
| 15:28.04 | oej | Thanks - that was I wanted to hear. |
| 15:28.26 | oej | But I also wanted to make the change well-known... |
| 15:28.43 | kpfleming | sure, and you already started a list thread about it. that should be adequate. |
| 15:28.54 | oej | Thanks. I like that. |
| 15:28.56 | leifmadsen | didn't we determine small changes by experienced developers didn't require RB? |
| 15:28.58 | kpfleming | give it a couple of days for people to comment if they want to, and then move ahead if the consensus is that you should |
| 15:29.06 | kpfleming | leifmadsen: that too |
| 15:29.12 | leifmadsen | asked and answered :) |
| 15:29.54 | irroot | think its also if you not sure throw it out there |
| 15:30.50 | irroot | like 1442 its helping me in production and there plenty issues about it but the patch i use is more a plaster / prevent user issues |
| 15:33.05 | kpfleming | no. it's for code review, not getting opinions on whether a particular change should or should not be made. if the approach to solving the problem is in question, then it could be appropriate. |
| 15:33.38 | oej | I tried to say that a year ago: Please move architecture discussions to asterisk-dev and use reviewboard for code reviews. |
| 15:35.51 | irroot | kpfleming oej id rather put up a patch on RB and then discuss it discard it latter instead of using pastebin for licencing concerns |
| 15:36.44 | kpfleming | that's not the point. if the idea has been agreed to and you are just proposing a solution, then posting a patch is fine. if you aren't even sure whether the approach is sound, there's no need to post a patch at all; just describe the approach in an email and discuss it. |
| 15:37.10 | kpfleming | in those cases, the discussion should be focused on 'why' and not 'how' |
| 15:37.22 | kpfleming | reviewboard is for the 'how' part :-) |
| 15:37.37 | leifmadsen | pabelanger: ping |
| 15:38.01 | pabelanger | leifmadsen: pong |
| 15:38.12 | oej | I think we agree about reviewboard. I see progress. |
| 15:38.19 | leifmadsen | pabelanger: your changes to configuration files -- they should reflect the default configuration option right? |
| 15:39.14 | pabelanger | leifmadsen: no. The patches made sure we parsed the config files to same way |
| 15:39.46 | leifmadsen | pabelanger: right, but you were discussing (or we discussed once) that the configuration file options that are documented should reflect the default setting if it were never set |
| 15:39.50 | leifmadsen | I believe |
| 15:40.43 | pabelanger | Hmm... possible, I can't remember right now. But I do agree the config files need cleaning |
| 15:41.58 | leifmadsen | pabelanger: ok, then I will give you an example -- Qwell suggests that strictrtp=yes (which appears to be the new default), be changed in the configuration file to strictrtp=no, which will not be the default |
| 15:41.59 | *** join/#asterisk-dev Corydon76-home (eleven@c-69-137-80-31.hsd1.tn.comcast.net) |
| 15:41.59 | *** mode/#asterisk-dev [+o Corydon76-home] by ChanServ |
| 15:42.09 | leifmadsen | pabelanger: I'm just trying to make sure we're being consistent, or moving towards consistency |
| 15:42.33 | *** join/#asterisk-dev Corydon76-home (six@c-69-137-80-31.hsd1.tn.comcast.net) |
| 15:42.33 | *** mode/#asterisk-dev [+o Corydon76-home] by ChanServ |
| 15:43.10 | pabelanger | nods |
| 15:43.20 | irroot | im in favor of the config files in samples reflecting defaults but commented out it makes it more user/n00b friendly |
| 15:46.22 | pabelanger | irroot: https://wiki.asterisk.org/wiki/display/~pabelanger/sample+config |
| 15:46.33 | pabelanger | something I was playing with a few months ago |
| 15:46.52 | pabelanger | leifmadsen: perhaps something for AstriDevCon :D |
| 15:47.25 | jsmith-busy | pabelanger: Don't do it -- it's a trap! |
| 15:47.36 | jsmith-busy | pabelanger: If we give users that much information, they might actually use it! |
| 15:47.43 | jsmith-busy | is only kidding, of course |
| 15:47.47 | leifmadsen | jsmith-busy: blasphemy! |
| 15:47.47 | Qwell | I wonder if we could just generate the sample configs.. |
| 15:47.49 | tzanger | zomg. pabelanger is canjian? |
| 15:47.58 | leifmadsen | tzanger: yep, ottawa yo |
| 15:47.58 | tzanger | we really are infiltrating digium |
| 15:48.07 | leifmadsen | tzanger: Digium is mostly Canadian :) |
| 15:48.08 | jsmith-busy | pabelanger: May I suggest that we also give them a set of simplified sample configs as well? |
| 15:48.14 | leifmadsen | jsmith-busy: already working on it |
| 15:48.19 | leifmadsen | I have a branch for it |
| 15:48.26 | jsmith-busy | pabelanger: (along the lines of "make simple-samples" or something? |
| 15:48.28 | jsmith-busy | leifmadsen: Oh, you do? |
| 15:48.29 | leifmadsen | 'make something-useful' |
| 15:48.37 | tzanger | why not just have proper man pages for the config files? I've always found HUGE default configs unwieldy |
| 15:48.38 | leifmadsen | jsmith-busy: aye |
| 15:48.48 | Qwell | tzanger: patches welcome |
| 15:48.52 | jsmith-busy | leifmadsen: You should probably talk w/ Kenny about that -- try to coordinate those sample configs with what they use in training |
| 15:48.57 | pabelanger | Qwell: Yar, was thinking about that too. Something like xmldoc or something... |
| 15:49.13 | jsmith-busy | leifmadsen: That'll make things easier for both of you -- he already has simple sample configs for several of the common config files |
| 15:49.23 | tzanger | Qwell: I'm just throwing the idea out as a possible direction. writing up a half dozen man pages and submitting a patch that nobody really wants is kind of wasteful, innit? |
| 15:49.25 | jsmith-busy | can't share them with leifmadsen anymore, unfortunately |
| 15:49.35 | pabelanger | jsmith-busy: indeed! |
| 15:49.55 | Qwell | tzanger: well, I think combined with the simple samples they're talking about, a manpage would be quite useful |
| 15:50.05 | jsmith-busy | <impression source="The A-Team">I love it when a plan comes together</impression> |
| 15:50.06 | leifmadsen | +1 |
| 15:50.09 | tzanger | Qwell: if it's something that people might enjoy, I just may take on that particular task, as it's an excellent refresher for me |
| 15:50.10 | Qwell | then make samples could just always be the simple stuff, and you could do `man sip.conf` for more betterness. |
| 15:50.22 | irroot | pabelanger love the idea but rather large janitor task that do we need the "since" field as that is covered in CHANGES and we assume reversions will be unlikely |
| 15:50.27 | Qwell | tzanger: maybe just pick 1 or 2 to start, for proof of concept |
| 15:50.31 | tzanger | exactly |
| 15:50.54 | tzanger | is encroaching on leifmadsen's territory... documentation :-) |
| 15:50.56 | leifmadsen | goes to lunch on some chinese food |
| 15:50.59 | leifmadsen | tzanger: GOOD |
| 15:51.01 | irroot | perhaps a API for configs where options are registered ?? |
| 15:51.01 | tzanger | serves him right for trying to be a dev |
| 15:51.20 | Qwell | irroot: see above re; generated. that's kinda the idea I was going for |
| 15:51.21 | jsmith-busy | tzanger: We need all the help we can get in that regard :-p |
| 15:51.23 | tzanger | irroot: ? |
| 15:51.47 | leifmadsen | someone should like..... write this down..... perhaps using some sort of..... wiki like concept |
| 15:52.18 | Marquis42 | leifmadsen: That idea is just crazy enough that it might work! |
| 15:52.26 | Qwell | that'll never work |
| 15:52.31 | Qwell | naysays |
| 15:52.49 | irroot | tzanger the idea is that a blob of code app/func/res/.... will register its global settings with a API not have whole collection static declerqations |
| 15:52.58 | oej | There are no screams on asterisk-users about the change in pbx-start(). I guess most people just did not understand. At least we can say "we asked you" :-) |
| 15:53.07 | leifmadsen | if someone would write it down, then we could actually discuss it at AstriDevCon and come up with a game plan |
| 15:53.11 | oej | One guy had misread the Asterisk book and blamed the book for his own fault. |
| 15:53.23 | leifmadsen | reading is a dangerous thing |
| 15:53.25 | irroot | no blame leifmadsen not the book |
| 15:53.29 | tzanger | hey I like that idea |
| 15:53.54 | tzanger | all the config file options that it looks for are registered, and that can serve as a starting point for what is available |
| 15:53.59 | tzanger | that's a major undertaking though |
| 15:54.22 | tzanger | alhtough with the various GUIs out there this might already be half implemented |
| 15:54.29 | tzanger | I haven't looked at asterisk code since 1.4.2x |
| 15:54.44 | Qwell | tzanger: it's still pretty code-like |
| 15:54.54 | Qwell | it's got functions and stuff |
| 15:54.56 | tzanger | 1.4.23.1 in fact |
| 15:55.30 | tzanger | oej: that's the problem with documentation... people try to hold you to it :-) |
| 15:55.31 | Qwell | I've gotta get that to our marketing dept. |
| 15:55.37 | Qwell | "Asterisk: It's got functions and stuff" |
| 15:55.41 | tzanger | Qwell: hahaha |
| 15:55.50 | irroot | leifmadsen i read somewhere smoking caused cancer i gave up smoking then read drinking causes liver disease and stoped drinking read sex can lead to various ailments ... i gave up reading |
| 15:55.50 | tzanger | "Asterisk: make your phones ring and shit, yo." |
| 15:56.14 | oej | pabelanger: old work, but related: http://www.codename-pineapple.org/doc/html/sip3_8h-source.html |
| 15:56.50 | tzanger | there are already configuration parsers in asterisk... t'wouldn't be too much to extend that to exporting what it's looking for |
| 15:56.50 | irroot | oej like sponge bob square pants loves pineapple ?? |
| 15:58.03 | Qwell | tzanger: could make config verifiers too.. |
| 15:58.29 | oej | In that code, I had "sip show config" and an array with all the config names and options and a description |
| 15:58.54 | tzanger | Qwell: indeed |
| 15:59.01 | tzanger | this ties in nicely with some of the work I have to do |
| 16:03.30 | Qwell | There's really no reason the data couldn't include acceptable values. For instance a port field should be limited to 1-65535 (65536?). Some things only use on/off/enabled/etc. |
| 16:05.40 | oej | Pabelanger: I think we need to separate reference docs from sample configs. The reference for the config files has to be within the source, like the rest of the XML docs. |
| 16:06.33 | Qwell | oej: tzanger was suggesting man pages. see above! |
| 16:06.44 | Qwell | <Qwell> then make samples could just always be the simple stuff, and you could do `man sip.conf` for more betterness. |
| 16:07.01 | oej | If we have xml, we can produce anything. |
| 16:09.14 | tzanger | we can use XML to produce XML-wrapped docbook formatted pdf pages for HTML! |
| 16:09.36 | tzanger | I think that almost makes sense too |
| 16:10.45 | tzafrir | oej, but you also want a format that is simple to edit |
| 16:10.58 | irroot | planning on commiting the SRTP taglen patch this is for 10/trunk update the SRTP sip API to support multiple taglen and add support via config for 32 leaving default 80 |
| 16:11.02 | irroot | i dont see this for 1.8 even if its buggy i see it more a missing feature |
| 16:11.36 | malcolmd | agree |
| 16:12.00 | Qwell | tzanger: and autogenerated configuration webpages! |
| 16:12.00 | Qwell | SOMEONE THINK OF THE CHILDREN |
| 16:12.02 | Qwell | (but seriously, that would actually be doable - though perhaps a bit useless) |
| 16:12.53 | oej | tzafrir: We already agreed on the existing XML, so we have to live with that anyway. |
| 16:13.29 | tzafrir | So now you need to: |
| 16:13.42 | tzafrir | 1. encode existing sample config as "XML" |
| 16:14.09 | tzafrir | 2. figure out how to regenerate valid config from "XML" |
| 16:14.10 | oej | No. Let's scrap the existing and write a reference doc in XML. |
| 16:14.26 | oej | And then get a new "sample" configuration that people will understand. |
| 16:15.16 | oej | The problem is to explain where each config option fits in - for SIP we have configuration options for devices, authentication and the channel. Some applies in multiple places. |
| 16:16.32 | oej | Time for dinner. I'm sure you can figure this out :-) |
| 16:16.48 | tzafrir | What's wrong with the way sip.conf.sample is structured now? |
| 16:16.59 | tzafrir | (the order and such, not the format) |
| 16:17.02 | Qwell | [ line 59/1384 (4%) |
| 16:17.03 | Qwell | that. |
| 16:17.13 | Qwell | the sample is 1384 lines long. That's absurd. |
| 16:17.30 | pabelanger | well, our samples config files are more like documentation |
| 16:17.33 | oej-away | The structure is something I've tried to keep an eye over, so it should work. |
| 16:17.57 | tzafrir | Unless you'll split it, it will be long in whatever format. The current format is actually rather terse |
| 16:18.03 | oej-away | But I'm not sure that all options are explained properly - so that people understand that this is a general option ONLY and this one actually is documented in general but also works for devices |
| 16:18.06 | Qwell | tzafrir: that's the idea |
| 16:18.39 | Qwell | sample configuration should be simple. If they want more advanced stuff, read the documentation for that config file. |
| 16:19.07 | tzafrir | yeah, I agree that sample and reference should not be the same thing |
| 16:19.36 | Qwell | I don't think anyone would really disagree with that statement. The trick is proposing it, and then actually doing something about it. |
| 16:19.47 | leifmadsen | ya that ;) |
| 16:20.01 | tzafrir | In the above I meant: "what's wrong with the sample file as a layout for the future reference file" :-) |
| 16:20.29 | leifmadsen | heh that is certainly a different statement :) |
| 16:27.23 | kpfleming | leifmadsen: you are a different statement |
| 16:27.40 | leifmadsen | kpfleming: sometimes! |
| 16:29.16 | *** join/#asterisk-dev dms (~dms@nat/digium/x-qectwhokclhrcdhx) |
| 16:45.02 | mjordan | If anyone has any time today, could they look at https://reviewboard.asterisk.org/r/1443/? Thanks! |
| 16:54.27 | tzanger | hmm, confluence said my password was reset but I still can't log in |
| 17:02.01 | tzanger | gah. gonna need one of the confluence admins to assist. it's definitely not working right |
| 17:03.21 | irroot | mjordan on the todo list |
| 17:03.58 | russellb | R1443 |
| 17:04.13 | russellb | no bot, nm.. |
| 17:04.22 | irroot | mjordan have looked at it and makes sense if i have moment ill dig deeper |
| 17:05.06 | mjordan | irroot: thanks! |
| 17:05.46 | irroot | on way home so may be latter or in am mytime looks right sofar |
| 17:18.18 | *** join/#asterisk-dev Corydon76-home (~quassel@c-69-137-80-31.hsd1.tn.comcast.net) |
| 17:18.18 | *** mode/#asterisk-dev [+o Corydon76-home] by ChanServ |
| 17:33.15 | *** join/#asterisk-dev irroot (~irroot@41.49.174.238) |
| 17:41.11 | irroot | mjordan home read through patch R1443 seems good nothing stands out |
| 17:49.07 | mjordan | cool, thanks |
| 18:12.49 | *** join/#asterisk-dev irroot (~irroot@41.52.147.110) |
| 18:21.10 | *** join/#asterisk-dev oej (~olle@ns.webway.se) |
| 18:21.10 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 18:28.48 | *** join/#asterisk-dev oej (~olle@ns.webway.se) |
| 18:28.48 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 18:29.08 | oej | Evening |
| 18:35.36 | irroot | oej o/ |
| 18:50.11 | anonymouz666 | oej: please don't speed up my day - strictdaytime=yes :P |
| 19:07.41 | anonymouz666 | how is controlled the commits that went to branch 1.8 still waiting to be included in the next releases? |
| 19:08.38 | anonymouz666 | is there a list or something like this, that could be listed? |
| 19:09.32 | leifmadsen | anonymouz666: huh? |
| 19:09.43 | leifmadsen | anything in the 1.8 branch will be in the following 1.8 RC1 |
| 19:09.52 | leifmadsen | it is pulled directly from the branch |
| 19:10.02 | leifmadsen | anything in the 1.8 branch is thus then included in the next RC |
| 19:10.16 | anonymouz666 | fixA/fixB/fixC was committed into branch 1.8 before -rc2 |
| 19:10.28 | anonymouz666 | when rc2 was release didn't include A, b or C |
| 19:10.39 | leifmadsen | right, so it isn't in rc2 |
| 19:10.45 | leifmadsen | only certain issues are merged into rc1+x |
| 19:10.52 | leifmadsen | typically regressions found in rc1 |
| 19:12.07 | anonymouz666 | hmmm so it is ok to expect these fixes in versin 1.8.8.0-rc1 |
| 19:12.47 | leifmadsen | yes because all changes in the 1.8 branch are copied into the 1.8.8.0-rc1 tag |
| 19:13.25 | anonymouz666 | understood the process, thanks! |
| 19:29.01 | leifmadsen | p |
| 19:29.01 | leifmadsen | np |
| 19:34.17 | kpfleming | the process which has been discussed many times and is documented on the wiki, IIRC |
| 19:54.58 | leifmadsen | I think it is, but not sure where :) |
| 19:55.10 | leifmadsen | if anything, yes, it has been discussed and documented on mailing lists several times :) |
| 20:00.16 | russellb | leifmadsen: you blogged about it, but it is kinda confusing, so not surprising that it comes up |
| 20:00.43 | russellb | (not that I think there's anything wrong, I like the process) |
| 20:00.54 | *** join/#asterisk-dev moy (~moy@173.239.155.74) |
| 20:07.10 | leifmadsen | russellb: well I would like to make it not confusing, because I don't think the process is that difficult to understand |
| 20:08.56 | russellb | i don't think it's hard to understand, it's just a high volume of changes going on, and requires either decent svn skills or lots of date comparissons to figure things out, the info is scattered around |
| 20:09.12 | russellb | i think one nice thing would be having every issue tagged with the version the fix will appear in |
| 20:09.33 | *** join/#asterisk-dev zerohalo (~zerohalo@173-13-92-27-NewEngland.hfc.comcastbusiness.net) |
| 20:09.36 | russellb | i don't know of a good way to make that happen automatically though |
| 20:09.43 | leifmadsen | ya... |
| 20:09.53 | russellb | but if commiters could be trained to do it when they close issues ... |
| 20:10.34 | leifmadsen | I think until we have a template system in jira like we had in mantis, that's going to be hard to do |
| 20:10.55 | russellb | how does a template help? |
| 20:11.11 | russellb | also, related note, i started a tempalte script - repotools/astcommitmsg.py |
| 20:11.19 | russellb | i don't remember how far i got |
| 20:11.34 | leifmadsen | russellb: it helps by allowing people to select what the next versions are -- it's hard to get people to know what the next version is |
| 20:11.55 | russellb | mantis didn't have anything like that in the template? |
| 20:12.03 | russellb | JIRA has way better version tracking support than mantis did |
| 20:12.13 | leifmadsen | we also didn't have people putting in what the next version of Asterisk a change would show up in |
| 20:12.26 | russellb | nods |
| 20:12.42 | russellb | but if you keep the version list up to date, it'll be available in the Target Version list |
| 20:12.46 | russellb | i think that's the field ... |
| 20:12.58 | leifmadsen | anyways, basically all changes should be assumed to be in the next RC1 unless specifically listed in the Tasks that I create for each release |
| 20:13.23 | russellb | well I understand that :-) |
| 20:13.32 | russellb | i'm just trying to think about it from the general user standpoint |
| 20:13.45 | leifmadsen | right, I understand |
| 20:14.08 | russellb | so like anonymouz666 ... he has links to the issues he cares about that were recently fixed presumably. it would be nice to be able to just go there and see right there what he wants to know which is, when will the fix for this issue be available in a release |
| 20:14.49 | russellb | anyway, i think that should be the goal, figure out how all JIRA issues that resulted in commits can also indicate the release the fix is targeted for |
| 20:15.45 | leifmadsen | aye |
| 20:15.46 | russellb | which I think is a combination of keeping the version list up to date, and having all devs update the fixed version (or whatever the right field is) when they close something |
| 20:15.54 | leifmadsen | I'd like to get the workflow fixed first though |
| 20:16.04 | russellb | makes sense |
| 20:16.13 | leifmadsen | version list should be up to date most (if not all) the time |
| 20:16.17 | russellb | cool |
| 20:16.21 | leifmadsen | since it's part of the release process |
| 20:16.42 | russellb | so you could email asterisk-dev then about everyone setting "fixed release" (check the field name, i don't remember) |
| 20:16.47 | russellb | fixed version maybe, whatever |
| 20:17.12 | leifmadsen | aren't they closed automatically during the commit? |
| 20:17.24 | leifmadsen | if so, I think it's going to be really really really really hard to get devs to go into the jira issue and set the fixed field |
| 20:17.30 | leifmadsen | (I would love that though) |
| 20:17.31 | russellb | well i tried that and it didn't work, maybe I formatted it wrong? |
| 20:17.57 | leifmadsen | I wonder if there is another way to go about this.... |
| 20:18.04 | leifmadsen | so... |
| 20:18.29 | russellb | can do it after the fact with a script ... if someone feels like writing the script |
| 20:18.38 | leifmadsen | there is the subversion commit stuff that goes with an issue, and if we could make it so a particular release was associated with a revision number, then potentially that should help determine when changes would be going in? |
| 20:19.11 | russellb | it's just software. |
| 20:21.45 | leifmadsen | indeed |
| 20:35.27 | leifmadsen | ASTERISK-18566 |
| 20:35.31 | DocAwesome | [ASTERISK-18566] [Status: Triage] G.729 RTP Payload Size - https://issues.asterisk.org/jira/browse/ASTERISK-18566 |
| 20:35.37 | leifmadsen | I don't think I consider that a bug.... |
| 20:35.44 | leifmadsen | anyone more informed on the matter than I? |
| 20:37.30 | oej | DOn't add another process, russellb. This has to be automatic. |
| 20:37.58 | russellb | i'm not adding anything, just providing ideas, it's not my call. |
| 20:38.21 | russellb | and manual is the only option unless someone steps up to automate it (which I'm not going to do) |
| 20:39.06 | oej | That still won't catch changes that goes directly to svn. You have to base it on svn. |
| 20:41.21 | oej | Added a comment to that issue, leifmadsen. |
| 20:41.40 | oej | Are the old bug guidelines gone? We used to require SIP debug on those issues. That would make the process go faster. |
| 20:42.34 | leifmadsen | oej: no they still exist, but if people don't follow them, then they don't |
| 20:42.41 | leifmadsen | all of this exists on the wiki |
| 20:43.03 | oej | I did not see a pointer there when reporting an issue. |
| 20:43.20 | leifmadsen | we never had a pointer there when reporting an issue |
| 20:43.24 | oej | Ok, then I know that I still can refer to them. |
| 20:43.25 | leifmadsen | it didn't exist on mantis either |
| 20:43.43 | oej | Oh, there was a link with yellow background in Mantis. And a link on the front page. |
| 20:44.09 | leifmadsen | we don't have a news page on jira afaik |
| 20:44.45 | oej | I suspect there's a way to add information to forms or sections. |
| 20:55.56 | oej | I can't argue with people that "you should have found out that we have bug guidelines on a totally different site hidden somewhere and you should have read them before going to this site in order to help us fix our bugs" |
| 20:56.20 | leifmadsen | oej: I get it, thanks |
| 20:57.02 | oej | SO I guess someone should kindly suggest a change with Erin |
| 20:58.05 | leifmadsen | Erin is busy working on other things right now, so I doubt that'll get looked at for a while |
| 20:58.36 | russellb | there is a project on issues.asterisk.org for JIRA requestions |
| 20:58.44 | russellb | JA - JIRA Administration, IIRC |
| 20:58.47 | Qwell | requestions!@ |
| 20:58.50 | russellb | that would be the appropriate place. |
| 20:58.59 | russellb | Qwell: lol, nice word actually |
| 20:59.01 | oej | Great. THanks |
| 20:59.29 | russellb | np |
| 21:02.33 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 21:10.26 | oej | What does status: triage mean in Jira? |
| 21:12.07 | leifmadsen | means the issue needs to be triaged |
| 21:12.20 | leifmadsen | think of it like "New" in Mantis |
| 21:12.25 | oej | Ok |
| 21:12.32 | leifmadsen | (someone hasn't triaged the issue yet) |
| 21:12.50 | oej | There's some quite substantial changes that doesn't go through reviewboard. Do they take another route somewhere? |
| 21:12.58 | leifmadsen | what do you mean? |
| 21:13.33 | oej | I see commits that change behaviour and important code that has no reference to reviewboard. Just curious and trying to learn what the process is. |
| 21:13.51 | leifmadsen | exaples? |
| 21:13.53 | leifmadsen | examples? |
| 21:14.15 | oej | The commit just made that I got in the mailing list. |
| 21:14.46 | oej | By kmoore |
| 21:14.56 | oej | Closes Asterisk-18044 |
| 21:14.59 | DocAwesome | [ASTERISK-18044] [Status: Closed] [Assigned: kmoore] extenpatternmatchnew breaks ability for caller to exit queue - https://issues.asterisk.org/jira/browse/ASTERISK-18044 |
| 21:14.59 | oej | But no reviewboard |
| 21:16.42 | mjordan | oej: that was reviewed. If the commit message didn't link the reviewboard message, that's an error in the commit message. |
| 21:17.00 | mjordan | er, review, not reviewboard message. You know what I mean :-) |
| 21:17.11 | oej | Ok then. |
| 21:19.02 | leifmadsen | oej: are you talking about this one? http://lists.digium.com/pipermail/svn-commits/2011-September/069304.html |
| 21:19.08 | mjordan | oej: https://reviewboard.asterisk.org/r/1367/ |
| 21:20.08 | leifmadsen | mjordan: ya and I don't see any error in the commit message |
| 21:20.12 | oej | mjordan clarified the issue, leif. |
| 21:20.33 | leifmadsen | oej: yes he just beat me to it, I see that |
| 21:20.48 | leifmadsen | I was looking to see if there was an issue with the commit message -- there is not as far as I can see |
| 21:20.56 | mjordan | sounds like the auto-linkage is funkified :-( |
| 21:21.25 | *** join/#asterisk-dev tzafrir (~tzafrir@bzq-218-155-145.cablep.bezeqint.net) |
| 21:21.25 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 21:43.01 | oej | leifmadsen: The cdr-pgsql-status is ready to be committed. If you want to, I can commit it to 10 - otherwise just trunk |
| 21:45.14 | leifmadsen | malcolmd: ^^^ |
| 21:45.58 | malcolmd | i don't have any problem w/ a commit to 10, also. anyone have any objections? |
| 21:48.39 | Corydon76-home | While you're at it, it's probably a quick add to cel_pgsql.c, too |
| 21:48.53 | russellb | mjordan: what auto linkage? |
| 21:50.16 | oej | And propabl res_pgsql.c too - but that's out of scope for the customer unfortunately. I'll add it to the "when I have free time" list |
| 21:50.57 | Corydon76-home | I'm just saying because cel_pgsql.c was basically a copy of cdr_pgsql.c... |
| 21:51.22 | Corydon76-home | All of the cel modules originated that way, then were modified to support CEL records |
| 21:51.40 | oej | Ok. I'll see if I can take a look. |
| 21:51.43 | Corydon76-home | So the structure of the code is essentially identical |
| 21:52.00 | oej | If you help me review :-) |
| 21:52.05 | Corydon76-home | Can do |
| 21:53.20 | oej | Got released by customer. Finally bedtime! Good night! |
| 21:53.33 | leifmadsen | ok, ya, if we're going to add a feature to cdr_mysql I'd prefer it to also be in cel_mysql |
| 21:53.38 | leifmadsen | since we're suggesting people move to that |
| 21:53.48 | leifmadsen | s/mysql/pgsql/ |
| 21:56.45 | mjordan | russellb: none, apparently. My linkage was wrong. |
| 21:56.53 | russellb | oic |
| 21:58.05 | leifmadsen | mjordan: what was wrong? it didn't look wrong... did it need to be in the braces? |
| 22:00.36 | mjordan | nope, its fine. User error <-- |
| 22:01.13 | leifmadsen | mjordan: no that's what I mean -- what did you type wrong? |
| 22:04.39 | leifmadsen | ASTERISK-18253 |
| 22:04.42 | DocAwesome | [ASTERISK-18253] [Status: Triage] Init service isn't compatible with LSB - https://issues.asterisk.org/jira/browse/ASTERISK-18253 |
| 22:04.50 | leifmadsen | anyone know if he is right? If so, that change is so easy to fix. |
| 22:05.01 | mjordan | I didn't. I was look at oej's issue link, and mised the commit history |
| 22:05.09 | mjordan | er, looking. |
| 22:05.16 | mjordan | I am having trouble completing my words apparently. |
| 22:05.25 | leifmadsen | words are hard |
| 22:06.19 | jsmith | leifmadsen: smart is hard? |
| 22:07.53 | leifmadsen | jsmith: so hard |
| 22:08.01 | leifmadsen | ...ahem |
| 22:08.41 | Corydon76-home | That's what he said |
| 22:10.04 | russellb | leifmadsen: yes, he is right in that issue |
| 22:11.58 | leifmadsen | russellb: ok then I shall make a commit :) |
| 22:12.01 | russellb | k |
| 22:49.17 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 22:49.17 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 22:59.31 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 22:59.31 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 23:11.20 | *** join/#asterisk-dev elguero (~miguel323@2001:470:1f06:12c4::2) |
| 23:15.09 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-pgokadmracvlfsbc) |
| 23:21.35 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 23:21.35 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 23:39.07 | *** join/#asterisk-dev elguero (~miguel323@2001:470:1f06:12c4::2) |