| 01:34.06 | *** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir) |
| 02:04.47 | *** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir) |
| 03:07.41 | *** join/#asterisk-bugs codefreeze-lap (n=murf@216.166.159.235) |
| 04:27.37 | *** join/#asterisk-bugs infobot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 04:27.37 | *** 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. -=- Best overall issue count: 272 -=- Monitor new reports in #asterisk-commits -=- Test bugs marked Ready For Testing -=- Mantis happy now. |
| 06:25.46 | *** join/#asterisk-bugs fabled (n=fabled@xdsl-83-150-94-239.nebulazone.fi) |
| 06:26.49 | *** join/#asterisk-bugs oej (n=olle@ns.webway.se) |
| 06:30.07 | *** join/#asterisk-bugs jmls_net (n=asterisk@host217-36-208-155.in-addr.btopenworld.com) |
| 06:44.26 | *** join/#asterisk-bugs oej (n=olle@ns.webway.se) |
| 11:07.35 | *** join/#asterisk-bugs DagMoller (n=aguirre@unaffiliated/dagmoller) |
| 11:41.59 | *** join/#asterisk-bugs caio1982 (i=caio1982@CAcert-br/caio1982) |
| 11:59.22 | *** join/#asterisk-bugs fabled (n=fabled@xdsl-83-150-94-239.nebulazone.fi) |
| 12:26.02 | *** join/#asterisk-bugs mbranca (n=matteo@mi-gw1.voismart.net) |
| 12:34.40 | *** join/#asterisk-bugs fabled (n=fabled@xdsl-83-150-94-239.nebulazone.fi) |
| 13:05.15 | *** join/#asterisk-bugs JunK-Y (n=junky@modemcable153.55-201-24.mc.videotron.ca) |
| 13:05.15 | *** mode/#asterisk-bugs [+o JunK-Y] by ChanServ |
| 13:32.02 | *** join/#asterisk-bugs caio1982 (i=caio1982@CAcert-br/caio1982) |
| 13:48.10 | *** join/#asterisk-bugs bbryant (n=brett@216.207.245.1) |
| 13:48.10 | *** mode/#asterisk-bugs [+o bbryant] by ChanServ |
| 13:49.11 | *** join/#asterisk-bugs jpeeler (n=jpeeler@216.207.245.1) |
| 14:26.44 | *** join/#asterisk-bugs mackes-Office (n=root@74.10.229.35) |
| 14:43.27 | *** join/#asterisk-bugs Corydon76-lap (n=Corydon7@pdpc/supporter/bronze/Corydon76-home) |
| 14:43.27 | *** mode/#asterisk-bugs [+o Corydon76-lap] by ChanServ |
| 14:44.31 | *** join/#asterisk-bugs russellb (n=russell@asterisk/developer-and-stable-maintainer/drumkilla) |
| 14:44.31 | *** mode/#asterisk-bugs [+o russellb] by ChanServ |
| 15:14.36 | file | M12671 |
| 15:14.38 | MuffinMan | [feedback] [Asterisk] Applications/app_queue 0012671: Dynamic queue member does not survive reboot/restart when using aliases reported by b_plessis (Karma: neutral) http://bugs.digium.com/view.php?id=12671 |
| 15:14.45 | putnopvut | Hello file |
| 15:14.47 | file | putnopvut: I wholeheartedly agree with your last note |
| 15:14.57 | putnopvut | Yeah, I just want to be certain though. |
| 15:29.22 | file | M12681 |
| 15:29.24 | MuffinMan | [new] [Asterisk] Core/General 0012681: Command Line - "core show channels" reported by visu (Karma: neutral) http://bugs.digium.com/view.php?id=12681 |
| 15:29.26 | file | meh |
| 15:31.46 | *** join/#asterisk-bugs infobot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 15:31.46 | *** 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. -=- Best overall issue count: 272 -=- Monitor new reports in #asterisk-commits -=- Test bugs marked Ready For Testing -=- Mantis happy now. |
| 15:31.48 | jsmith | It sure does... |
| 15:31.53 | jsmith | ... and thanks to tab completion, who cares? |
| 15:32.29 | putnopvut | I wasn't doubting that it does, I guess I just like to see output which demonstrates the problem, no matter what that problem may be. |
| 15:32.42 | file | concise won't truncate. |
| 15:32.54 | jsmith | file: I thought concise was deprecated |
| 15:33.05 | file | I'm in 1.4 land right now |
| 15:33.12 | file | so that is entirely possible |
| 15:34.04 | *** join/#asterisk-bugs infobot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 15:34.04 | *** 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. -=- Best overall issue count: 272 -=- Monitor new reports in #asterisk-commits -=- Test bugs marked Ready For Testing -=- Mantis happy now. |
| 15:36.00 | file | jsmith: want to comment on 12681? :D |
| 15:39.38 | *** join/#asterisk-bugs infobot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 15:39.38 | *** 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. -=- Best overall issue count: 272 -=- Monitor new reports in #asterisk-commits -=- Test bugs marked Ready For Testing -=- Mantis happy now. |
| 16:00.37 | *** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir) |
| 16:22.09 | Qwell | M12683 |
| 16:22.11 | MuffinMan | [assigned] [Asterisk] Applications/app_queue 0012683: Queue timeout not overided by the timeout parameter on the Queue command reported by daren (Karma: neutral) http://bugs.digium.com/view.php?id=12683 |
| 16:22.13 | Qwell | Should that be closed then? |
| 16:22.38 | Qwell | maybe document it better, or something? |
| 16:23.52 | putnopvut | Qwell: I haven't looked at that yet. |
| 16:23.54 | putnopvut | Let me check... |
| 16:24.45 | putnopvut | Ah, I'll have to check the documentation a bit more closely. The confusing thing is that both of the timeouts are called "timeout" |
| 16:24.53 | Qwell | yeah.. |
| 16:25.17 | Qwell | at first, it seems that changing "timeout" in the Queue() to something else would make sense, but that's what Dial() and everything else calls it |
| 16:25.29 | putnopvut | Right. Here's an idea: |
| 16:25.38 | Qwell | maybe...change config option, and keep timeout? |
| 16:25.43 | putnopvut | For trunk, allow an alternate term for timeout in the config. |
| 16:25.47 | Qwell | right |
| 16:25.51 | putnopvut | So we could accept "timeout" and ... |
| 16:25.56 | putnopvut | ringtime ? |
| 16:25.56 | Qwell | no need to deprecate timeout, IMO |
| 16:26.04 | Qwell | what does the option do, exactly? |
| 16:26.19 | putnopvut | It's the amount of time that it rings a member's phone before giving up. |
| 16:26.30 | putnopvut | Then it waits "retry" seconds before attempting to ring another member. |
| 16:26.36 | Qwell | and what about timeout on Queue()? |
| 16:26.54 | putnopvut | That's like an absolute time that a caller can stay in the queue before he gets dropped. |
| 16:27.04 | putnopvut | The QUEUESTATUS is set accordingly when that happens. |
| 16:27.08 | Qwell | right |
| 16:27.38 | Qwell | ringtime sounds good |
| 16:43.18 | jsmith | Qwell: calltimeout vs. membertimeout? |
| 16:43.37 | Qwell | "call" sort of seems post-answer to me |
| 16:44.01 | Qwell | might just be me though |
| 16:44.16 | jsmith | Qwell: Depends on your definition of "answer" |
| 16:44.29 | jsmith | Qwell: By answer, you mean connected to a queue member, right? |
| 16:44.34 | Qwell | yeah |
| 16:44.54 | jsmith | "It depends on what your definition of *is* is!" |
| 16:56.46 | *** join/#asterisk-bugs atis_work (n=atis_wor@193.238.212.171) |
| 17:43.02 | Qwell | M12670 |
| 17:43.03 | MuffinMan | [new] [Asterisk] Core/RTP 0012670: some RTP packets sent to NAT IP instead of public IP; breaks built-in jitterbuffer on some phones reported by jolan (Karma: neutral) http://bugs.digium.com/view.php?id=12670 |
| 17:43.11 | Qwell | sounds like that can be closed |
| 17:43.28 | file | go ahead eh |
| 17:43.44 | Qwell | comments first |
| 17:43.54 | Qwell | 12615 was from the same reporter too, and said it would probably be resolved too |
| 17:51.59 | *** join/#asterisk-bugs jmls_net (n=asterisk@host217-36-208-155.in-addr.btopenworld.com) |
| 17:52.19 | *** join/#asterisk-bugs bkruse (n=bkruse@216.207.245.1) |
| 18:40.00 | *** join/#asterisk-bugs mackes-Office (n=root@mail.deltasoniccarwash.com) |
| 18:56.56 | *** join/#asterisk-bugs atis_work (n=atis_wor@193.238.212.171) |
| 19:05.38 | *** join/#asterisk-bugs msetim (n=msetim@200.195.161.164) |
| 19:06.08 | msetim | I'm using asterisk 1.4.18 and I'm getting segfault, using bt full I see reference to ast_enum_reload and the last full log make reference to func_enum |
| 19:06.19 | msetim | I see a change in func_enum in 1.4.18 version http://bugs.digium.com/view.php?id=11958 |
| 19:07.23 | msetim | someone have some idea? |
| 19:08.52 | jsmith | msetim: One other note... you'll want to post your backtrace somewhere (asterisk.pastebin.com, for example), post the URL, and then wait for a response. The bug marshalls and developers are pretty busy, and sometimes it takes a while for them to be able to look at the backtrace. |
| 19:09.42 | JunK-Y | msetim: pastebin ur gdb output for bt |
| 19:10.21 | msetim | JunK-Y, o.k... I will do |
| 19:14.25 | JunK-Y | juste paste the 4 first frames here |
| 19:15.04 | *** join/#asterisk-bugs shido6 (n=shido6@74-130-120-3.dhcp.insightbb.com) |
| 19:17.51 | msetim | http://pastebin.com/m4d991e95 |
| 19:18.17 | msetim | JunK-Y, I hope done right |
| 19:19.46 | JunK-Y | lot of ?? in there |
| 19:20.57 | msetim | JunK-Y, sorry... I don't understand |
| 19:23.37 | *** join/#asterisk-bugs fakhir_ (n=fakhir@unaffiliated/fakhir) |
| 19:24.50 | *** join/#asterisk-bugs deeperror (n=deeperro@69-215-202-195.ded.ameritech.net) |
| 19:25.15 | deeperror | I've got an odd bug that seems to be changing contexts on zap channels |
| 19:25.23 | deeperror | http://pastebin.ca/1023050 |
| 19:25.33 | deeperror | view Context's on both channel 7 and 8 |
| 19:26.03 | deeperror | they should be the same...every few days a channel will have this occur |
| 19:26.07 | deeperror | any way to dig deeper on this |
| 19:26.09 | *** join/#asterisk-bugs jmls (n=asterisk@host217-36-208-155.in-addr.btopenworld.com) |
| 19:30.11 | msetim | deeperror, right :) I will do |
| 19:31.12 | deeperror | It's really hard to pinpoint the exact cause but i know it's memory related |
| 19:31.30 | deeperror | perhaps bad ram? but it seems like bad ram would cause an issue all the time |
| 19:42.49 | msetim | deeperror, no... it's a ibm series and this error throw after update from 1.4.11 to 1.4.18 |
| 19:43.09 | msetim | deeperror, zap channels have same contexts :( |
| 19:43.24 | deeperror | i'm on a custom machine |
| 19:43.43 | deeperror | zapata has channel=1-96 going to same context |
| 19:50.19 | msetim | deeperror, I'm checking at all now |
| 19:54.22 | deeperror | thanks :) |
| 19:56.35 | *** join/#asterisk-bugs atis_work (n=atis_wor@193.238.212.171) |
| 19:56.37 | msetim | deeperror, from 0-30 we have extensions-1 and 32-XX we have inbound-routes.. however it's was configured propositionally |
| 20:01.45 | deeperror | ? |
| 20:01.52 | deeperror | is that your setup? |
| 20:26.34 | msetim | deeperror, http://pastebin.ca/1023140 it is my zapata.conf |
| 20:27.05 | deeperror | i added a new queue and when I performed a dialplan reload the channel started working again |
| 20:28.42 | deeperror | mine is fairly similar |
| 20:48.07 | *** join/#asterisk-bugs dsfr (n=dsfr@pdpc/sponsor/digium/dsfr) |
| 20:57.10 | *** join/#asterisk-bugs atis_work (n=atis_wor@193.238.212.171) |
| 21:29.01 | *** join/#asterisk-bugs putnopvut (n=putnopvu@216.207.245.1) |
| 21:29.01 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 21:39.37 | *** part/#asterisk-bugs deeperror (n=deeperro@69-215-202-195.ded.ameritech.net) |
| 21:46.19 | *** join/#asterisk-bugs lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 21:46.19 | *** mode/#asterisk-bugs [+o lmadsen] by ChanServ |
| 23:50.40 | *** join/#asterisk-bugs jtodd (n=jtodd@blob.fox-den.com) |
| 23:51.48 | Qwell | jtodd: ! |
| 23:52.16 | jtodd | qwell: !? |
| 23:52.27 | Qwell | hi |
| 23:52.46 | Qwell | see msg :D |
| 23:52.54 | jtodd | Greetings. I'll start showing up here more now. :-) As long as I'm not in meetings. |
| 23:52.55 | Qwell | also! welcome to Digium |
| 23:56.49 | jtodd | Thanks. More news on that shortly. :-) |