IRC log for #asterisk-bugs on 20080211

01:15.05*** join/#asterisk-bugs russellb (n=russell@asterisk/developer-and-stable-maintainer/drumkilla)
01:15.06*** mode/#asterisk-bugs [+o russellb] by ChanServ
01:39.57*** join/#asterisk-bugs ZX81 (n=ZX81@202.49.106.158)
07:05.39*** join/#asterisk-bugs oej (n=olle@soll4-125.cust.blixtvik.net)
08:04.33*** join/#asterisk-bugs agx (n=AGX@host63-216-static.34-88-b.business.telecomitalia.it)
08:32.33*** join/#asterisk-bugs sx|lappy (n=sxpert@lgit-1225.obs.ujf-grenoble.fr)
08:33.31*** join/#asterisk-bugs the-moog (n=the-moog@static-195-248-121-199.adsl.hotchilli.net)
10:31.59*** join/#asterisk-bugs flujan (n=flujan@200-160-115-020.static.spo.ctbc.com.br)
12:29.04*** join/#asterisk-bugs agx (n=AGX@host63-216-static.34-88-b.business.telecomitalia.it)
12:29.30*** join/#asterisk-bugs russellb (n=russell@asterisk/developer-and-stable-maintainer/drumkilla)
12:29.30*** mode/#asterisk-bugs [+o russellb] by ChanServ
13:18.51*** join/#asterisk-bugs oej (n=olle@147.240.13.217.in-addr.dgcsystems.net)
13:38.19*** join/#asterisk-bugs oej (n=olle@147.240.13.217.in-addr.dgcsystems.net)
14:19.25*** join/#asterisk-bugs lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
14:19.25*** mode/#asterisk-bugs [+o lmadsen] by ChanServ
14:30.32*** join/#asterisk-bugs miguel3239 (n=elguerom@h-68-167-124-171.cmbrmaor.covad.net)
14:50.23*** join/#asterisk-bugs putnopvut (n=putnopvu@216.207.245.1)
14:50.23*** mode/#asterisk-bugs [+o putnopvut] by ChanServ
15:08.13lmadsendoes anyone wanna look at this bug?  http://bugs.digium.com/view.php?id=10543
15:08.19lmadsenif not... then I think I might as well just close it
15:08.23fileM10543
15:08.24MuffinMan[assigned] [Asterisk] Channels/chan_sip/Interoperability 0010543: Some characters (such as #) are not escaped in SIP headers reported by blitzrage  http://bugs.digium.com/view.php?id=10543
15:08.55lmadsenthis was something I ran into at a clients, but I'm not working for that client anymore
15:10.49jmlswhy close it off it there is a problem still ?
15:13.11lmadsenbecause I don't really expect it to get fixed unless someone sponsors it...
15:19.25*** join/#asterisk-bugs Docfxit (n=none@cpe-72-129-118-135.socal.res.rr.com)
15:20.34*** join/#asterisk-bugs miguel3239 (n=elguerom@h-68-167-124-171.cmbrmaor.covad.net)
15:21.42DocfxitHow can I start Asterisk with the -g option in Asterisknow? I'd like to do a backtrace. I couldn't find the backtrace.txt file in Asterisknow ver. 1.4.17
15:22.01lmadsenDocfxit: this is not the appropriate forum for that question...
15:24.47DocfxitSorry. I posed the question in the Asterisknow forum yesterday and today. Where should I pose this question?
15:39.52lmadseneither the asterisknow forum, #asterisk, or perhaps the asterisk-users mailing list (not sure if there is an asterisknow ML or not)
16:06.58*** join/#asterisk-bugs infobot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt)
16:06.58*** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Overall issue count: 328 -=- Monitor new reports in #asterisk-commits -=- Want to help? Test bugs marked Ready For Testing
16:29.38*** join/#asterisk-bugs magumbade (n=magumbad@p5497D8DE.dip.t-dialin.net)
16:43.08*** join/#asterisk-bugs putnopvut (n=putnopvu@216.207.245.1)
16:43.08*** mode/#asterisk-bugs [+o putnopvut] by ChanServ
16:47.48d1maswhen 1.6 release is planned ?
16:52.35putnopvutd1mas: I think the plan with that is to release once the betas are considered to be stable enough for release.
16:52.45putnopvutHowever, the metric of "stability" is hard to define.
16:53.01d1mashehe... less unstable than usually :)
16:54.35d1masso there is no plan... :(
16:58.19*** join/#asterisk-bugs Corydon76-lap (n=Corydon7@pdpc/supporter/bronze/Corydon76-home)
16:58.19*** mode/#asterisk-bugs [+o Corydon76-lap] by ChanServ
17:29.39BBHossd1mas, the betas are actually quite stable, i've only found a few faults with dundi and other less-used areas
17:30.55d1masbbhoss: lucky you then. Every time I updated _stable_ 1.4 from SVN something was broken
17:37.01jsmithBBHoss: Did you file a bug for the dundi problem?
17:37.10BBHossyes
18:30.49mvanbaakyup, the dundi bug is out there
18:34.04russellbyeah, i have been meaning to lab up that dundi issue
18:34.21russellbit seems like it shouldn't be too hard if it just plain won't work
18:34.29russellbi think i did a lot of "code cleanup" on that module
18:34.31russellbi may have broken it
18:35.52russellbmaybe one more beta ...
18:36.01russellbthen rc1 within the next month or so
18:40.47mvanbaakgood plan
18:41.12mvanbaakI have to setup some sort of multiserver testbed here as well
18:41.49mvanbaakI need more phones
18:42.05mvanbaakservers is not a problem (/me pats his xen setup)
18:54.47mvanbaakfile is fast today
18:55.22fileI am no longer sick.
18:55.28fileback to my regular self!
18:55.52mvanbaakgreat news
18:56.07mvanbaakI was going to close 11257 the moment the mail arrived in my mailbox
18:56.16mvanbaakclicked the link to find out you already did that
18:56.30fileI'm crazy like that
18:56.46mvanbaakmust be some mailbox monitoring script
18:56.53filemore like IRC :d
18:56.56file:D
18:57.42mvanbaakif $commenter == $poster && preg_match("/.*can be closed.*/", $text) run_close_issue($id);
18:58.21*** join/#asterisk-bugs sx|lappy (n=sxpert@abo-180-6-68.ech.modulonet.fr)
19:00.26mvanbaakhhmm, are we going to apply those 'make rpm' patches to the tree sometime ?
19:01.06russellbif someone who knows that stuff verifies they are good
19:01.09mvanbaakor do we leave that as an exercise to the package maintainer ?
19:01.14russellbi assigned them to Qwell because i know that he knows that stuff :)
19:01.39russellbi agree that it is mostly an exercise for the package maintainer, but i don't mind making it easier for people to make their own packages
19:01.44russellbthe ones in Fedora are amazing, i hear
19:01.53russellblots of sub-packages for all the things with dependencies
19:02.03mvanbaakuhhuh, same as debian
19:02.45mvanbaakI'm tempted to close them. almost every distro has it's own locations etc for stuff
19:03.05russellbwell ... we have spec files in the tree
19:03.12mvanbaakok
19:03.12russellbif they totally suck, and those are better, applying them is fine IMO
19:03.22russellbif they suck and we don't want to deal with it, it should all be removed
19:04.10mvanbaakI'll leave to qwell
19:04.23mvanbaakI never had to deal with rpm
19:09.08jsmithThe ones in Fedora *are* amazing
19:09.22jsmithThe spec file we have in the sources is *awful*
19:09.30jsmith(Anything would be better than what we ship with now)
19:11.20mvanbaakfile: can we close 10451 ?
19:11.41fileM10451
19:11.42MuffinMan[feedback] [Asterisk] Channels/chan_zap 0010451: Sending caller ID to ZAP Extension fails if sendcalleridafter=0 or sendcalleridafter=1 reported by rjenkins  http://bugs.digium.com/view.php?id=10451
19:12.17fileif Corydon's workaround works, sure
19:13.14mvanbaakI'll ping the reporter
19:15.59fileM11826
19:15.59MuffinMan[new] [Asterisk] Resources/res_features 0011826: Call transfer with 4 and more participants reported by aiker  http://bugs.digium.com/view.php?id=11826
19:15.59mvanbaakAPPLICATION WARNING #user_get_field() for NO_USER:
19:15.59mvanbaakmeh !
19:15.59mvanbaaknice
19:15.59putnopvut11826 is a fun one...
19:15.59mvanbaakLogged in as: mvanbaak (Michiel van Baak - manager)
19:15.59fileputnopvut: I would say... that is the way it was written to be...
19:16.51putnopvutWell, sort of. Qwell and I actually looked at that one a while back.
19:16.51mvanbaakI should update the skinny transfer patch as my ast_debug( patch that file committed really makes it not apply
19:16.51mvanbaakbut I'm dead tired
19:17.27putnopvutAnd we agreed that the way SIP does its transfers in that situation is correct.
19:17.49filebut that bug does not involve SIP transfers
19:18.05putnopvutRight, in other words, if the builtin transfers behaved the same way as SIP transfers, it would be correct.
19:18.27putnopvutBut the way the builtin transfer works when you initiate a second transfer in the middle of another transfer is odd...
19:20.41fileso what is the verdict?
19:22.03Qwellfile: feature transfers are b0rked..
19:22.23filewhere?
19:22.31mvanbaakI'm off for today
19:22.33putnopvutJust in general.
19:22.33fileas in, what branch
19:22.36filemvanbaak: peace!
19:22.43fileoh you mean how they work in general
19:22.46Qwellyeah..
19:22.54putnopvutfile: trunk is worse, since it leaves all sorts of extra dead channels up.
19:23.08putnopvutDo the experiment in 11826 and then do core show channels.
19:23.15putnopvutYou'll see 6 channels listed.
19:23.17filethen we acknowledge the issue so it doesn't creep up on file's radr
19:23.18fileand radar
19:26.22QwellWhat did I do? :(
19:27.06fileM11835
19:27.06MuffinMan[new] [Asterisk] Applications/app_meetme 0011835: Marked conference mode not working properly! reported by alanmcmillan  http://bugs.digium.com/view.php?id=11835
19:29.08fileQwell: didn't you mess with the flags awhile back...
19:29.58Qwellthat was to make moh not play until...something.
19:30.42Qwelloh, to make moh stop playing after the new person records their name
19:30.51QwellA92617
19:30.53MuffinMan[92617] Committed by qwell on 2007-12-12 17:15:45: Don't increment user count until after name has been recorded (if enabled).
19:31.01filesilly.
19:47.00*** join/#asterisk-bugs agx (n=badpengu@81-174-44-244.dynamic.ngi.it)
19:55.50*** part/#asterisk-bugs agx (n=badpengu@81-174-44-244.dynamic.ngi.it)
20:23.05*** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir)
20:33.39*** join/#asterisk-bugs Juggie (i=Juggie@CPE001601df17fb-CM001a6682d7b6.cpe.net.cable.rogers.com)
20:33.39*** mode/#asterisk-bugs [+o Juggie] by ChanServ
21:18.41d1masrussellb: are you there?
21:18.45russellbno
21:19.07d1mas:)
22:17.00russellbA103314
22:17.02MuffinMan[103314] Committed by file on 2008-02-11 12:17:15: Add support for allowing a native bridge to happen when the L option is enabled. The RTP bridging could already handle this, it just needed to be enabled in the main bridging code.
23:15.25d1masrussel: still not here? :)
23:15.52d1massorry, russellb

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.