IRC log for #asterisk-dev on 20091125

01:39.17*** join/#asterisk-dev moy (n=moy@CPE001cdfec4cee-CM00080dab8485.cpe.net.cable.rogers.com)
02:35.38*** join/#asterisk-dev elguero (n=elguero@ns1.nashuacs.com)
03:09.20*** join/#asterisk-dev lmsteffan (n=laurent@195.221.84.4)
03:12.24*** join/#asterisk-dev leifmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
03:12.24*** mode/#asterisk-dev [+o leifmadsen] by ChanServ
03:20.47*** join/#asterisk-dev leifmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
03:20.47*** join/#asterisk-dev xpot (n=xpot@70-91-210-233-BusName-Utah.hfc.comcastbusiness.net)
03:20.47*** join/#asterisk-dev felipe_ (n=felipe@my.nada.kth.se)
03:20.47*** join/#asterisk-dev Marquis42 (n=bfhbmw0@65.127.126.34)
03:20.47*** join/#asterisk-dev MuffinMan (n=muffinma@asterisk/issue-tracker-bot/muffinman)
03:20.47*** join/#asterisk-dev ChanServ (ChanServ@services.)
03:20.47*** mode/#asterisk-dev [+oo leifmadsen ChanServ] by irc.freenode.net
03:28.24*** join/#asterisk-dev obnauticus (n=obnautic@about/windows/regular/obnauticus)
06:05.49*** join/#asterisk-dev obnauticus (n=obnautic@about/windows/regular/obnauticus)
06:27.37*** join/#asterisk-dev elguero (n=elguero@ns1.nashuacs.com)
06:27.37*** join/#asterisk-dev ecrane (n=ecrane@o1-69-19-166-10.static.o1.com)
06:27.37*** join/#asterisk-dev Katty (n=asterisk@mail.copi-rite.com)
06:27.37*** join/#asterisk-dev jmworx__ (n=jeval@mail.octasic.com)
06:27.37*** join/#asterisk-dev ccesario (n=ccesario@189-19-6-236.dsl.telesp.net.br)
06:28.11*** join/#asterisk-dev mvanbaak (n=michiel@asterisk/contributor-and-bug-marshal/mvanbaak)
06:28.11*** join/#asterisk-dev micols (n=mio@rlogin.dk)
06:28.11*** mode/#asterisk-dev [+o mvanbaak] by irc.freenode.net
06:54.21*** join/#asterisk-dev |Cybex| (n=John@atwork-20.r-212.178.82.atwork.nl)
07:33.11*** join/#asterisk-dev alecdavis (n=alec@202-78-149-14.cable.telstraclear.net)
07:55.53*** join/#asterisk-dev mpe (n=mpe@gate.ipvision.dk)
07:56.21*** join/#asterisk-dev Marquis42 (n=bfhbmw0@65-127-126-34.dia.static.qwest.net)
08:07.31*** join/#asterisk-dev jmworx (n=jeval@mail.octasic.com)
08:31.58*** join/#asterisk-dev tamiel (n=tamiel@213.30.183.226)
08:56.11*** join/#asterisk-dev NirS (n=NirS@212.199.197.7)
09:01.35*** join/#asterisk-dev NirS (n=NirS@212.199.197.7)
09:05.07*** join/#asterisk-dev sgimeno (n=sgimeno@226.Red-80-33-64.staticIP.rima-tde.net)
09:44.13*** part/#asterisk-dev alecdavis (n=alec@202-78-149-14.cable.telstraclear.net)
09:58.37*** join/#asterisk-dev sgimeno (n=sgimeno@226.Red-80-33-64.staticIP.rima-tde.net)
10:37.06*** join/#asterisk-dev lmsteffan (n=laurent@114.69.191.131)
11:13.49*** join/#asterisk-dev caio1982 (i=caio1982@CAcert-br/caio1982)
12:16.38*** join/#asterisk-dev Omorika (n=omorika@89.201.165.226)
12:16.39Omorikahi guys
12:16.58Omorikai have a question regarding an issue i'm experiencing
12:17.46Omorikamy asterisk box is crashing when calling jb_destroy at jitterbuf.c:103
12:17.55Omorikait seems that reference count drops to -1 for ao2obj
12:19.22mvanbaakcan you create a ticket for that please ?
12:19.45Omorikaok, i'm asking coz its 1.6.2.0-rc1
12:20.07Omorikaand i thought maybe some1 rembembers if some1 already reported this kind of problem
12:20.30mvanbaakIf someone reported it, it will be on https://issues.asterisk.org
12:21.06mvanbaakpersonally I'm not really familiar with the jitterbuffer in asterisk, so I dont know
12:21.24mvanbaakand I think the devs that know are not awake yet
12:21.55mvanbaakso to make sure this problem will be addressed, you should open a ticket for it.
12:29.35Omorikaok, thanls
12:29.40Omorika*ok, thanks
12:53.42tzafrirOmorika, however, if this is a new install, and it is isntalled from source, better try it with -rc6 first
12:54.17*** join/#asterisk-dev kpfleming (n=kpflemin@asterisk/digium-director-of-software-tech/kpfleming)
12:54.17*** mode/#asterisk-dev [+o kpfleming] by ChanServ
12:56.12mvanbaakmornin Kevin
12:58.44kpflemingmorning
13:02.28*** join/#asterisk-dev bala (i=dce39c91@gateway/web/freenode/x-iunzddoiorgliccs)
13:03.20balai am running asterisk-svn-18-11-09,
13:04.04balaand, mixmonitor start SIP/whatever test.wav doesn't seem to work
13:04.48balahowever, if i run " mixmonitor start <chan_name> test.wav", it records the first channel availabe,
13:04.59baladoes anybody know how i could fix this?
13:16.05Omorikatzafrir: no, it's not a new setup, it's actually our production server so it will take a while to upgrade
13:18.43mvanbaaknice, people running release-candidates in production
13:37.20Omorikawell... i had no choice
13:37.28*** join/#asterisk-dev qdk (n=qdk@193.169.208.32)
13:45.09*** join/#asterisk-dev oej (n=olle@eduroam-193-157-113-208.uio.no)
13:45.09*** mode/#asterisk-dev [+o oej] by ChanServ
13:47.07oejAfternoon, folks
13:47.22mvanbaakgood mornin oej
13:48.22mvanbaakhaving fun with ldap ?
14:05.49tzafrirLet's Dance And Party!
14:17.31*** join/#asterisk-dev Marquis42 (n=bfhbmw0@65-127-126-34.dia.static.qwest.net)
14:24.42*** join/#asterisk-dev putnopvut (n=putnopvu@asterisk/master-of-queues/mmichelson)
14:24.42*** mode/#asterisk-dev [+o putnopvut] by ChanServ
14:31.05*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
14:55.25*** part/#asterisk-dev Omorika (n=omorika@89.201.165.226)
14:59.36*** join/#asterisk-dev TheDavidFactor-H (n=chatzill@c-68-34-116-180.hsd1.md.comcast.net)
15:00.12TheDavidFactor-Hrussellb, ping
15:00.49TheDavidFactor-Hnm, see that he's out
15:01.57*** join/#asterisk-dev davidbrillert (n=aragon12@216.235.8.130)
15:02.58TheDavidFactor-HI've got an issue that was raised where EIVR double closes file descriptors; I was wondering if anyone who has more C knowledge then I do would be willing to assist me with this.
15:07.33Corydon76-digdouble closing file descriptors shouldn't cause a problem
15:09.13TheDavidFactor-HM16305
15:09.16MuffinMan[feedback] [Asterisk] Applications/app_externalivr 0016305: [patch] ExternalIVR confuses AGI by double closing FDs reported by diLLec (Karma: +3.50) https://issues.asterisk.org/view.php?id=16305
15:09.59TheDavidFactor-Hthe issue that was reported is that, the first close frees the FD which is then given to another process and then the second close closes the FD for the new process
15:11.06TheDavidFactor-Hthe reporter said it is only seen under high load
15:14.55*** join/#asterisk-dev kpfleming (n=kpflemin@asterisk/digium-director-of-software-tech/kpfleming)
15:14.55*** mode/#asterisk-dev [+o kpfleming] by ChanServ
15:20.14Corydon76-digTheDavidFactor-H: ah, the problem then is that the field needs to get reset to -1
15:20.33Corydon76-digafter the close succeeds initially
15:21.13Corydon76-digIs that a direct enough indication as to what you need to change?
15:21.42TheDavidFactor-Halso, it's using fclose in one place and close in another. is there a difference between using fclose and close?
15:23.20Corydon76-digI advise you to read the manpages
15:23.40kpflemingTheDavidFactor-H: i already answered that exact question for you a couple of days ago
15:24.49TheDavidFactor-Hyes you did, I apologize for asking it again, but I didn't copy what you wrote and I lost it. It was about this same bug report.
15:25.04kaiito be honest, i'm too lazy to read all the changelogs to find this out, so hopefully someone can answer me here..    Is it intended, that a voicemail gets deleted from inbox when "delete=yes" and email=""(nothing)?
15:25.20kaiiin 1.2 when email was not set, the voicemail would not be deleted
15:25.33kpflemingTheDavidFactor-H: they apply to completely different types of objects... as Corydon76-dig said, read the manpages
15:25.51Corydon76-digkaii: I'm too lazy to answer you
15:26.09TheDavidFactor-Hbut they're being done on the same object in this code, which is what is confusing me
15:26.18*** join/#asterisk-dev moy (n=moy@74.12.130.190)
15:26.34Corydon76-digTheDavidFactor-H: No, it's being done on a slightly different object in the code
15:26.52kaiiCorydon76-dig:
15:27.31TheDavidFactor-Hoh
15:27.45Corydon76-digkaii: translation of your request:  "My time is more important than yours.  Please spoon feed me"
15:28.35kaiiCorydon76-dig: actually you got this wrong ..  reading all changelogs between latest 1.2 and current 1.4 takes ... mhj .. lots of time. and it doesnt event guarantee a useful answer
15:29.07Corydon76-digThen you better get to reading
15:29.30kaiithx
15:29.32atis_workkaii: svn blame
15:30.13Corydon76-digatis_work: he's too lazy to learn new things
15:30.16kaiiatis_work: yeah ... didnt look at the source so far. just thought maybe some core developer knows why this has been changed
15:30.42atis_workkaii: well, then you first have to find developer changing most of code there
15:30.48kpflemingyou are asking people about a change that happened more than 2 years ago, if it happened at all
15:31.17kaiiyou're right .. my question was pointless.
15:32.10kaiisometimes you know, there are things that are discussed .. things people know reasons for and can remember ... sry for trying that easy route
15:33.22Corydon76-digkaii: if you had omitted the part about being too lazy to read changelogs, you might have received a better response.  That was a disrespectful thing to say to core developers
15:33.55kaiiCorydon76-dig: i just realized that in the moment i read your answer :-)
15:34.09Corydon76-digYou seriously implied that your time was more important than ours
15:34.21kaiiit isn't
15:34.36kaiii was just hoping somebody would know instantly
15:34.40seanbrightmorning folks
15:34.44seanbrighthappy pre-turkey day
15:34.47mvanbaakmaybe he's european and taking revenge this way ?
15:35.11atis_workmvanbaak: then he would try to save the turkeys :p
15:35.14Corydon76-digseanbright: Nuts.  I've been required to start cooking the turkey tonight
15:35.35mvanbaakCorydon76-dig: ugh :(
15:35.36seanbrighti am not on cooking duty this year
15:35.53seanbrightthough i do want to fry a turkey before the year is out
15:36.28Corydon76-digMy job is the only the turkey.  Others prepare the rest of the food
15:36.53*** join/#asterisk-dev leifmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
15:36.53*** mode/#asterisk-dev [+o leifmadsen] by ChanServ
15:36.58mvanbaakCorydon76-dig: good deal there
15:37.28Corydon76-digReason my job is the turkey is that I have a technique for cooking that results in a very moist bird
15:37.44Corydon76-digSeared on a grill
15:38.13mvanbaakchecks last-minute tickets
15:38.36atis_workmvanbaak: you don't have to go to usa to get turkey
15:38.57atis_workmvanbaak: i'm having one as i work in american company
15:39.01mvanbaakbut I do have to if I want to taste this very moist bird Corydon76-dig is cooking
15:40.45Corydon76-digmvanbaak: 800 degree charcoal grill
15:41.01atis_workaah, they also have wrong degrees..
15:41.20Corydon76-digSear the bird, first, then steam for 8 hours
15:41.52TheDavidFactor-Hatis_work, try 427 degrees
15:42.32mvanbaakCorydon76-dig: sounds good
15:43.25kaiiin app_voicemail.c, voicemails get deleted if "delete=yes" .. regardless if it is distributed anywhere else (email, broadcast,..) or not.   that means, when a voicemail has no pager, no email, no broadcasting, but delete=yes, any voicemail is immediately deleted and lost.
15:43.37kpflemingthat is correct
15:43.40kaiithat sucks
15:43.47kpflemingso don't tell the system to do that
15:44.02kaiii knew that would come next
15:44.21Corydon76-digThe delete option wasn't designed to outsmart the admin.
15:44.21*** join/#asterisk-dev Deeewayne (n=dwayne@75.76.254.162)
15:44.22*** mode/#asterisk-dev [+o Deeewayne] by ChanServ
15:46.07*** join/#asterisk-dev |Cybex| (n=John@212.178.82.20)
15:47.01kaiiCorydon76-dig: the admin is actually a database view for all extensions that have personal_mailbox=1
15:47.56kaiiso i need a new admin ;-)
15:54.00*** join/#asterisk-dev elguero (n=elguero@12.187.84.162)
15:59.21kpflemingkaii: FYI, there are actually people who intentionally configure voicemail boxes in the way you describe... so if that functionality was changed, there would be users who would complain
16:02.19mvanbaakI am one of those
16:05.40*** join/#asterisk-dev TheDavidFactor-H (n=chatzill@c-68-34-116-180.hsd1.md.comcast.net)
16:10.22*** join/#asterisk-dev codefreeze-lap (n=murf@72.21.67.40)
16:10.22*** mode/#asterisk-dev [+o codefreeze-lap] by ChanServ
16:16.35kaiimvanbaak: just curious, why does anyone (you?) want to delete voicemails directly after they were written to disk?
16:18.16kpflemingif they have configured a greeting-only mailbox, for example
16:18.41kpflemingor.. you are going to be gone for two weeks, and you dont' want your mailbox full of stuff when you get back, so you change your greeting to tell people to email you instead
16:18.47kpflemingthere are cases :-)
16:19.36*** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
16:19.36*** mode/#asterisk-dev [+o lmadsen] by ChanServ
16:25.27kaiii see ..
16:29.03tzangerleif got k-lined?
16:29.35tzangerkpfleming: that would be very helpful for the email-me-my-voicemails crowd
16:34.10*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
16:43.44*** join/#asterisk-dev marv[work] (n=timr@router.asteriasgi.com)
16:44.06*** join/#asterisk-dev qdk (n=qdk@0x573d8df9.bynqu1.dynamic.dsl.tele.dk)
16:55.59*** part/#asterisk-dev mpe (n=mpe@gate.ipvision.dk)
16:57.57*** join/#asterisk-dev anthm (n=anthm@freeswitch/developer/anthm)
17:27.46*** join/#asterisk-dev TheDavidFactor-H (n=chatzill@c-68-34-116-180.hsd1.md.comcast.net)
17:29.03TheDavidFactor-His it normal for printf to print before ast_verb, and is this due to multi-threading?
17:29.17fileif using recent Asterisk versions, yes
17:29.25TheDavidFactor-Husing trunk
17:29.30filethen yes.
17:29.36TheDavidFactor-Hok, thanks
17:29.54TheDavidFactor-Hjust wanted to make sure before making an assumption
17:34.12*** join/#asterisk-dev Kobaz (n=kobaz@its.kobaz.net)
17:34.24Kobazwhat's the procedure for submitting new features
17:35.07fileeverything goes through the issue tracker.
17:35.11Kobazsounds good
17:35.30Kobazand i assume, i should write based off of trunk?
17:35.36fileyes.
17:35.47Kobazallrightey
17:35.57Kobazall kinds of good stuff i'm working on
17:37.25Kobazoh
17:37.49Kobazi know there's some developments towards a format independent data layer
17:37.55Kobazwhere can I find some info's about that
17:38.14Kobazlike, apparently via the AMI, getting xml/json/etc data
17:39.29Kobazand also... i was told the preferred new way to get lists of stuff via dialplan is via iterators... ie: getting a list of groups
17:39.42Kobazwould you guys happen to know where I could find an example
17:41.49kpfleminganything in the funcs directory that uses datastores is an example
17:52.43Kobazk
17:52.58Kobazand what about the ami?
17:56.50Corydon76-digWhat about it?
18:02.56*** join/#asterisk-dev mpe (n=mpe@85.24.86.40.generic-hostname.arrownet.dk)
18:19.16*** join/#asterisk-dev TheDavidFactor-H (n=chatzill@c-68-34-116-180.hsd1.md.comcast.net)
18:31.12*** join/#asterisk-dev errotan (n=errotan@81.0.115.3)
18:34.09*** join/#asterisk-dev mpe (n=mpe@85.24.86.40.generic-hostname.arrownet.dk)
18:34.37*** join/#asterisk-dev DarkRift (n=dark@modemcable015.68-200-24.mc.videotron.ca)
18:38.37Kobazoh
18:38.49KobazCorydon76-dig: well i heard some peoples talking about a generic data api for the ami
18:39.21Corydon76-digIt's not for AMI; it's a completely separate interface
18:39.51Kobazoh okay
18:39.55Kobazwhat's it called?
18:40.10Corydon76-digProjest PineMango
18:41.08Kobazheh
18:41.13Kobazreally?
18:41.27Corydon76-digYes
18:42.14Kobazah okay, so yeah it's a whole new thing i see from the diagrams
18:45.38Kobazis there any work towards a more centralized event system?
18:45.59seanbrightjust waiting for an eager and able developer
18:46.04Kobazlike... most of the modules send out their own events
18:46.14Kobazand they are pretty inconsistant for the most part
18:46.15Kobazheh
18:46.22Kobazseanbright: yeah, we've been fixing up some stuff
18:46.40seanbrightconverting all of the manager events to use async events and callbacks
18:46.42Kobazlike, import sends out a VARSET
18:46.45seanbrightthat was a suggested GSoC project
18:47.00Kobazvarset should probably be part of the core
18:47.21Kobazcallbacks are nice
18:47.44Kobazthe biggest thing we're trying to tackle right now is tracking channel creation from an originate
18:48.15Kobazpretty much all the subsequent events have no context whatsoever as to where they came from
18:48.44Kobazprobably by the end of the year we'll have patches put together
18:58.24Kobazwhat's alloca()?
18:59.31Kobazoh, weird... it's a std lib function
18:59.33kpfleming$ man alloca
18:59.57Kobazyeah i found it
19:00.24Kobazshouldn't modules use ast_calloc and friends
19:00.28Corydon76-digalloca is not a function
19:00.42Kobazyeah it is
19:00.46Corydon76-dignor is it in any library
19:00.52KobazDESCRIPTION The  alloca()  function allocates size bytes of space in the stack frame of the caller.
19:00.53putnopvutoh poopnugget!
19:00.54Corydon76-digNo, it's a compiler directive
19:01.22Corydon76-digIt looks like a function, but it is implemented as a compiler directive
19:01.34Kobazmmm, yeah i see
19:01.37Corydon76-digIt resides within gcc itself, not within a library
19:01.39Kobaz<PROTECTED>
19:03.05snuff-homeCorydon76-dig: is there an easy way to convert that ast_str_set() macro to a normal 'function' ?
19:03.30Corydon76-digsnuff-home: It IS a normal function
19:03.55Corydon76-digjust has some syntactic sugar
19:04.21snuff-homewell.. i mean something so i can workout what is complaining about the casting
19:04.21Kobazmmmm sugar
19:05.03Corydon76-digsnuff-home: the problem you had was with stringfields, not the dynamic strings
19:05.20Corydon76-digThose are completely different beasts
19:05.41snuff-homeah my bad..
19:05.50snuff-homei haven't looked since other day
19:07.24Corydon76-digStringfields are quite different, because most of them are set once for the entire lifetime
19:08.23snuff-homeok
19:17.18*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
19:17.26Kobazis there a doxygen online for the 1.6.0 branch
19:17.41Kobazthe old site doesn't seem to exist
19:20.34seanbrighthttp://www.asterisk.org/doxygen/asterisk1.6.0/index.html
19:21.25Kobazoh, excellent
19:24.22Kobazwhat's the max length of a channel?
19:24.33seanbrightuse the source, my child.
19:24.33kpflemingthat question makes no sense
19:24.39seanbrightchannel name
19:24.42seanbrightthat's my guess
19:24.43Kobazyeah channel name
19:24.46kpflemingthen ask that
19:24.49seanbrightheh
19:24.50Kobazheh
19:24.53Kobazprefix = alloca(strlen(args.chan) + 2);
19:24.58Kobazthat just looks really bad
19:25.05Kobazwhy would you want to allocate that on the stack
19:25.11kpflemingwhy not?
19:25.27Kobazwhat if it's obnoxiously long and overflows the stack
19:25.56Kobaz<PROTECTED>
19:26.01kpflemingif this is in a dialplan application, it can't be more than 4KB, because the buffer for passing args to applications is 4KB
19:26.25Kobazmm, k
19:27.12kpflemingand stack allocation is vastly more efficient than heap allocation
19:27.20Kobazyeah
19:27.34Kobazjust wanna make sure there's sane limits
19:27.42*** join/#asterisk-dev jozza (n=chatzill@BSN-77-186-224.dsl.siol.net)
19:28.37jozzahi, i am debugging asterisk from main() and it exists on deamon(). How do i make it run all the way under debugger?
19:29.16Kobazs/exists/exits/  ?
19:29.20jozzayea
19:29.26jozzai was just about to correct
19:29.33jozzaexits
19:29.36kpflemingrun it with -c so it wont' daemonize
19:29.54Kobazyeah, asterisk forks into th background
19:30.30Kobazmmm, i think i finished my module... time to test
19:33.04jozza-c works
19:33.15jozzai did -vvvvvc before and it didnt
19:34.01jozzahow do i interact with console in debugger?
19:35.00jozzai mean the cli
19:35.15QwellIt should just put you in the CLI when you run it
19:35.30jozzai am using KDevelop :))
19:35.45Kobazwhat i like to do... is run asterisk as a seperate daemon, and then use gdb to attach
19:36.00jozzayes i believe that
19:36.07Kobazyou can't easily debug the startup though, using that method... but
19:36.18*** part/#asterisk-dev |Cybex| (n=John@212.178.82.20)
19:36.18Kobazif you insert a pause in the startup, you can
19:36.19jozzabut if you want to start debuging from main()?
19:36.27jozzaok
19:36.33Kobazin main().... add some code that asks for a keypress to continue
19:36.47Kobazso you can run asterisk, attach, hit a key, and then debug main()
19:36.53jozzayea
19:37.03Qwellor just run asterisk ingdb :p
19:37.15jozzaso -c should show a console?
19:37.23Kobazyeah but then you have both asterisk and gdb in the same console, and it gets annoying/confusing
19:37.25Qwellin gdb, yes
19:37.45kpflemingand as soon as threads get created, debugging gets monumentally harder
19:37.54*** join/#asterisk-dev outtolunc (n=me@98.248.96.110)
19:38.08jozzai believe that
19:38.22*** join/#asterisk-dev |Cybex| (n=John@atwork-20.r-212.178.82.atwork.nl)
19:43.03jozzaso now i start it with kdevelop debugger and then connect to cli with -r
19:43.06jozzaits ok
19:43.21jozzalets get some serious work done now!
19:45.33Kobazcerial!
19:46.16tzangerkpfleming: http://www.mixdown.ca/~andrew/dump/threaddebug.gif
19:46.30tzangerI think that guy even looked like you before the stache came off
19:47.13Kobazheh, looks like a far side comic
19:47.54tzangeryeah, it was a /. banner ad YEARS ago
19:57.49*** join/#asterisk-dev oej (n=olle@85.19.87.179)
19:57.50*** mode/#asterisk-dev [+o oej] by ChanServ
20:00.00Kobazi brokedicated it
20:01.10QwellKobaz: brokified is the canonical way to say that
20:02.05kpflemingor brokezored
20:03.05Kobazmajor epic borken
20:03.24Kobazwhoops
20:04.22Kobazbad this happen when you forget to unlock a channel
20:05.58*** join/#asterisk-dev tzafrir_laptop (n=tzafrir@212.179.75.202)
20:05.58*** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ
20:06.38*** join/#asterisk-dev janinges (i=j@ninge.net)
20:17.09*** join/#asterisk-dev kerframil (n=kerframi@gentoo/user/kerframil)
21:14.39*** join/#asterisk-dev oej (n=olle@85.19.87.179)
21:14.40*** mode/#asterisk-dev [+o oej] by ChanServ
21:36.25*** part/#asterisk-dev |Cybex| (n=John@atwork-20.r-212.178.82.atwork.nl)
21:59.20*** join/#asterisk-dev xpot-mobile (n=xpot@173-14-232-121-Utah.hfc.comcastbusiness.net)
22:11.20*** join/#asterisk-dev mpe (n=mpe@0x4dd624b2.adsl.cybercity.dk)
22:12.16*** join/#asterisk-dev anthm (n=anthm@freeswitch/developer/anthm)
22:15.22*** join/#asterisk-dev lmsteffan (n=laurent@reef.ac-noumea.nc)
22:16.17lmsteffanHello
22:16.59lmsteffanI am wondering about a possible bug in __ast_queue_frame whereby a channel seems to not be released
22:18.18lmsteffanwhen the function returns abnormally. Could someone confirm that the channel should always be released within the body of that function ?
22:18.55lmsteffanIf that's the case I can submit a bug report with the patch to the bug tracker.
22:25.26Corydon76-digWhy do you think it should be released?
22:26.23Corydon76-digOh, you mean unlocked, not released
22:26.49Corydon76-digYes, looks like the unlock is missing there
22:26.49*** join/#asterisk-dev xpot-mobile (n=xpot@173-14-232-121-Utah.hfc.comcastbusiness.net)
22:27.51lmsteffanoh yes, unlocked indeed! guess I'm not fully awake yet...
22:39.14Corydon76-digOkay, fixed in all branches
22:41.14lmsteffanNo need for a bug report then ?
22:42.21*** join/#asterisk-dev jameswf (n=james@unaffiliated/jameswf-home)
23:00.23Corydon76-digNope, no need

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