IRC log for #asterisk-dev on 20080501

00:05.35*** join/#asterisk-dev moy (n=moyhu@189.169.90.74)
00:10.13macli<PROTECTED>
00:10.15*** part/#asterisk-dev macli (n=macli@nmc.brc.ubc.ca)
00:31.23*** join/#asterisk-dev Iamnacho (i=Iamnacho@ip68-103-153-140.ks.ok.cox.net) [NETSPLIT VICTIM]
00:31.23*** join/#asterisk-dev ccesario (n=ccesario@189-19-9-100.dsl.telesp.net.br) [NETSPLIT VICTIM]
00:31.23*** join/#asterisk-dev _charly_ (i=kroseneg@sunrise.schmidham.net) [NETSPLIT VICTIM]
00:41.07*** join/#asterisk-dev anthm (n=anthm@72.60.187.48)
00:41.29*** join/#asterisk-dev ccesario (n=ccesario@189-19-9-100.dsl.telesp.net.br)
00:41.54*** join/#asterisk-dev _charly_ (i=kroseneg@sunrise.schmidham.net) [NETSPLIT VICTIM]
01:00.34*** join/#asterisk-dev jeffg (n=jeffg@pdpc/supporter/active/jeffg)
01:12.42*** join/#asterisk-dev file (n=file@asterisk/developer-and-muffin-lover/file)
01:12.42*** join/#asterisk-dev DarkRift (i=dark@bas10-montreal02-1177584477.dsl.bell.ca) [NETSPLIT VICTIM]
01:12.42*** join/#asterisk-dev VoicePulse_ (n=contact@unaffiliated/voicepulse) [NETSPLIT VICTIM]
01:12.42*** join/#asterisk-dev Daviey (n=dave@ubuntu/member/daviey) [NETSPLIT VICTIM]
01:12.42*** join/#asterisk-dev citats (n=james@mrplow.gnuinternet.com) [NETSPLIT VICTIM]
01:12.43*** join/#asterisk-dev paravoid (n=paravoid@zebra.cslab.ece.ntua.gr) [NETSPLIT VICTIM]
01:12.43*** join/#asterisk-dev corramor (n=corramor@216.207.245.1) [NETSPLIT VICTIM]
01:12.43*** join/#asterisk-dev Juggie (i=Juggie@CPE001601df17fb-CM001a6682d7b6.cpe.net.cable.rogers.com) [NETSPLIT VICTIM]
01:12.43*** mode/#asterisk-dev [+o file] by irc.freenode.net
01:12.48*** join/#asterisk-dev tzafrir_laptop (n=tzafrir@local.xorcom.com)
01:12.48*** join/#asterisk-dev floppp (n=flopp@nat-staff.b3g-telecom.com)
01:12.48*** mode/#asterisk-dev [+o tzafrir_laptop] by irc.freenode.net
01:13.29*** join/#asterisk-dev seanbright (n=sean@c-69-251-175-43.hsd1.md.comcast.net)
01:13.30*** join/#asterisk-dev jmls_home (n=jmls_hom@mail.tessera.co.uk) [NETSPLIT VICTIM]
01:13.30*** join/#asterisk-dev _Vile (n=vile@208.100.152.234) [NETSPLIT VICTIM]
01:16.46Juggiecodefreeze: ping
02:21.45codefreeze-lapJuggie: how do?
02:22.03codefreeze-lapSorry for the wait
02:38.15Juggiecodefreeze, i just saw something odd go into your branch
02:38.26Juggiesome patch i posted like forever ago which should of been auto merged forever ago
02:38.35Juggiebecause it went into trunk
02:44.19codefreeze-lapJuggie: newcdr's been idle for a long time. Trying to bring it back up to date. A ***BIG*** merge.
02:47.11Juggieic
02:47.16Juggiei guess my commit just ended up at the top
02:47.23Juggieodd i was just curious :)
02:55.39*** join/#asterisk-dev snuff-home (n=snuff-ho@60-240-117-7-nsw-pppoe.tpgi.com.au)
03:07.38codefreezeJuggie-- luck of draw, methinks.
03:10.27*** join/#asterisk-dev VoipForces (n=courchea@bas7-montreal02-1096626715.dsl.bell.ca)
03:10.47VoipForcesCorydon76-dig: you around?
03:11.09snuff-homemmm newcdr.. that's the CEL stuff right?
03:16.14codefreezesnuff-home: yep. CEL. I'm going to play again.
03:21.25snuff-homelook forward to it
03:22.15snuff-homegoes fetches some provisions
03:30.06*** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
03:30.11*** mode/#asterisk-dev [+o lmadsen] by ChanServ
03:32.54*** join/#asterisk-dev jameswf-home (n=james@ip72-223-0-183.ph.ph.cox.net)
03:44.39*** join/#asterisk-dev CunningPike (n=arodgers@S010600095b33697f.vc.shawcable.net)
04:04.53*** join/#asterisk-dev moy (n=moyhu@189.169.83.74)
04:35.02Corydon76-digVoipForces: I am now
04:35.17Corydon76-digSorry, earlier I was messing with the guts of my laptop
04:54.14*** join/#asterisk-dev korihor (n=humberto@190.39.161.145)
05:09.50Juggiedid you make it bleed.
05:11.55Corydon76-digNew hard drive
05:12.46Corydon76-digI wouldn't call it painless; Apple screws the Torx screws in hella tight
05:13.03Qwellneed more torque for the torx
05:14.05Corydon76-digI finally just removed the bumpers on the drive and used a set of pliers to get the right amount of leverage
05:14.21Juggiesounds awefully painful
05:14.42Corydon76-digYou should try it sometime.  ;-)
05:14.52Juggiei've never done a laptop hdd
05:15.01Juggiebut i've had my dells stripped down pretty good
05:15.12Juggiereplace a lcd, add a wifi card, ram etc.
05:15.15Corydon76-digIf this wasn't the Pro laptop, the upgrade is supposedly easy
05:15.49Corydon76-digbut since this was the Pro, I had to remove the keyboard to get to the HD
05:15.50Juggiedid you have screws left over? :P
05:16.00Corydon76-digOf course not.  :-P
05:16.01Juggieah, this laptop i'm now has a laptop door
05:16.04Juggiewhich is handy.
05:16.07Juggieer, hdd door
05:16.09Juggiei mean
05:16.23Corydon76-digYour laptop has a laptop?
05:16.36Juggieindeed
05:16.39Juggieits super smart.
05:16.54Juggieit looks like its on rails slides out of the side like a dvd drive or something
05:17.27Corydon76-digYeah, I've got bumpers, not rails
05:17.54Corydon76-digI'm sure that does quite a bit for damage resistance
05:18.43Juggiewell i'm just guessing
05:18.54Juggietheres two screws to remove, and it should slide out of the side
05:18.58Juggienot sure what its mounted on
05:19.34Juggiehah
05:19.35Juggienothing
05:19.40Juggiejust the piece of plastic on the front
05:19.47Juggieno rails or bumpers.
05:27.08*** join/#asterisk-dev tuxd00d (n=tuxd00d@128.187.132.25)
05:37.40*** join/#asterisk-dev steliosk (n=Stelios@athedsl-311591.home.otenet.gr)
07:04.55*** join/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-96-193.bredband.comhem.se)
07:45.28*** part/#asterisk-dev pnlarsson (n=pnlarsso@c83-248-96-193.bredband.comhem.se)
08:40.52steliosktzafrir : was able to get the isdn card working only with signalling set as bri_cpe. If i set it to bri_cpe-_ptmp for some reason it fails to bring the D channel up
08:41.27stelioskthe only way to get it up, is for the asterisk to receive a call and then reload chan_zap
08:42.05steliosklooks like a bug but not sure where yet
08:45.04tzafrirsteliosk, what version of asterisk? bristuffed?
08:46.23stelioskkernel 2.6.25 zaptel 1.2.25, BRIstuffed-0.3.0-PRE-1y-q  asterisk Asterisk 1.2.28
08:48.38steliosktzafrir : plus oslec for EC
09:03.45tzafriris it connected to a service provider?
09:04.01tzafrir(if so: maybe it only supposrts ptp on that line?)
09:07.11steliosktzafrir : its connected. If it was a provider issue then it should not work at all.
09:07.58stelioskthe thing is that if the card gets an *incoming* call and reload chan_zap, it can then place calls
09:08.43stelioskif it was a provider issue it should not
09:10.16tzafrirsorry, I fail to parse that. What exactly work? What doesn't?
09:11.18stelioskif signalling is set to pri_cpe_ptmp then asterisk can receive calls but fails to place call from the bri
09:12.15stelioskpri show span 1 shows as status  Provisioned, Down, Active
09:12.37steliosksory signalling is set to bri_cpe_ptmp
09:13.31stelioskOnce a call is received then status changes to : Provisioned, Up, Active but still can't place outgoing calls
09:13.48stelioskif i reload chan_zap then outgoing calls get placed
09:14.34tzafrirafter a reload: still incoming but not outgoing?
09:14.36stelioskif i use bri_cpe as signaling then the bri can place/receive calls without any problem
09:15.19stelioskafter a reload (and signaling bri_cpe_ptmp) without an incoming call first then still no outgoing
09:16.24stelioskfor some reason bri_cpe_ptmp needs an incoming call to bring the D channel up and then to reload chan_zap
09:18.41stelioskso incoming calls work with bri_cpe_ptmp but not outgoing calls, unless an incoming call comes in first and then you reload chan_zap
09:18.49stelioskbri_cpe has no issues
09:19.31stelioskis it clear now or still looks Greek  ? :)
09:25.49tzafrirDo outgoing calls start an ISDN dialog? (as can be seen in 'bri debug span NN')?
09:27.51steliosktzafrir : No they don't
09:28.17steliosktzafrir : it fails at app.dial with error code 0
09:28.42tzafrirI guess no channel is available
09:28.55stelioskyes
09:32.04steliosktzafrir : can you think of any reason that it would fail ? For me it looks like libpri does not provide correct info when in bri_cpe_ptmp mode and asterisk thinks channel is down
09:33.54tzafrirsteliosk, or rather that it actually provides the correct information?
09:37.04steliosktzafrir : i have tried 2 different nt devices (one from intracom and one from siemens) and the issue is there. I know the nt's provide p2mp as i can have multiple isdn phones without any issue
09:37.41stelioskeach nt provides 2 S0 buses
09:38.30stelioskMy last try would be to have 2 asterisk boxes one in NT one in TE more and see if the problem is still there
09:38.42steliosks/more/mode
11:25.13*** join/#asterisk-dev RoyK (n=roy@ip-115-24-149-91.dialup.ice.no)
12:00.43*** join/#asterisk-dev ZaVoid (n=zavoid@66-95-182-90.client.dsl.net)
12:03.09ZaVoidmorning
12:07.36*** join/#asterisk-dev oej (n=olle@206.166.206.34)
12:07.36*** mode/#asterisk-dev [+o oej] by ChanServ
12:27.30*** join/#asterisk-dev jeffg (n=jeffg@pdpc/supporter/active/jeffg)
12:53.19*** join/#asterisk-dev VoipForces (n=courchea@office.prival.ca)
12:53.36VoipForcesCorydon76-dig: you around?
12:56.16ZaVoidanyone know when 1.4.20 might be out?
13:02.46*** join/#asterisk-dev snuff-home (n=snuff-ho@60-240-117-7-nsw-pppoe.tpgi.com.au)
13:09.29*** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
13:09.29*** mode/#asterisk-dev [+o lmadsen] by ChanServ
13:11.44Corydon76-digZaVoid: we'll go through release candidates first
13:11.47Corydon76-digVoipForces: pong
13:11.54ZaVoidaight
13:12.05ZaVoidwas just wondering roughly weeks/months etc etc
13:12.11ZaVoidit has that realtime fix.. and some other fixes
13:12.17Corydon76-digweeks
13:12.21ZaVoidgotcha
13:12.22ZaVoidthanks man
13:12.34Corydon76-digprobably hours until the first release candidate
13:12.40ZaVoido rlly?
13:12.52Corydon76-digyarly
13:13.04ZaVoidlooks i got work for one my techs today then lol
13:14.31ZaVoidi noticed sometimes there are RC's.. and sometimes. not... why is that/
13:14.31Corydon76-digIf more people tested the branch.....
13:15.02Corydon76-digWe previously only did RCs on the release of a major revision
13:15.05ZaVoidi guess if people tested the branch the realtime mistake woulda showed up too huh?
13:15.16ZaVoiderr "more people" i mean
13:15.18Corydon76-digThe community has requested that we do them on every release
13:15.33ZaVoidahh
13:15.47ZaVoidwe test each release.. we can start testing rc's or branches if you want
13:16.08Corydon76-digIf you could start testing the 1.4 and 1.6.0 branches, that would be appreciated
13:16.15ZaVoid1.6.0 argh
13:16.21ZaVoidi think i'll have to rewrite all my code for that
13:16.41Corydon76-digBoth branches have a release coming up
13:16.42ZaVoidi haven't even fully looked at the changes for it yet i should really do that do
13:17.57ZaVoidi gotta work on a iax load balancer too
13:19.47ZaVoidis there any easy place to see dialplan syntax changes from 1.6 to 1.4 for comparison?
13:20.14VoipForcesCorydon76-dig: Tested what you suggested last night for bug 12123, but still the same. Added feedback in mantis. Any ideas welcome.
13:23.20*** join/#asterisk-dev Iamnacho (i=Iamnacho@ip68-103-153-140.ks.ok.cox.net)
13:25.17*** join/#asterisk-dev putnopvut (n=putnopvu@216.207.245.1)
13:25.17*** mode/#asterisk-dev [+o putnopvut] by ChanServ
13:29.20VoipForcesZaVoid: found this yesterday, but only shows diff between 1.2 and 1.4, but I guess they might add 1.6 in a near future: http://www.the-asterisk-book.com/unstable/applikationen.html
13:29.38*** join/#asterisk-dev coppice (n=chatzill@218.0.192.80)
13:29.49ZaVoidthanks VoipForces
13:29.51ZaVoidlet me look
13:30.02*** part/#asterisk-dev coppice (n=chatzill@218.0.192.80)
13:30.08ZaVoidohh 1.2/1.4 :(
13:32.40*** join/#asterisk-dev oej (n=olle@206.166.206.34)
13:32.40*** mode/#asterisk-dev [+o oej] by ChanServ
13:40.45*** join/#asterisk-dev anthm (n=anthm@CPE-72-131-113-50.wi.res.rr.com)
13:48.23VoipForcesAnyone who has inputs on bug 12123, shoot, ready to try anything at this point...
13:59.40ZaVoidwhat big is that?
13:59.42ZaVoidbug
14:00.02fileM12323
14:00.03MuffinMan[assigned] [Asterisk] Channels/chan_sip/Registration 0012323: Asterisk gives up on registration after receiving 408 Timeout response once reported by voipdealer (Karma: neutral) http://bugs.digium.com/view.php?id=12323
14:00.11fileerm
14:00.12fileM12123
14:00.14MuffinMan[feedback] [Asterisk] Applications/NewFeature 0012123: [patch] Sending DTMF when receiving the PROGRESS status reported by VoipForces (Karma: neutral) http://bugs.digium.com/view.php?id=12123
14:01.29ZaVoidWHAT KIND of account code services VoipForces ?
14:01.40VoipForcesAllstream PRI servuce
14:01.42VoipForcesservice
14:02.13ZaVoidhmm
14:02.33VoipForcesthe account code, for some reason, is asked during the progress phase
14:06.48*** join/#asterisk-dev CunningPike (n=arodgers@204.239.12.183)
14:14.34*** join/#asterisk-dev joshaidan (n=joshaida@S01060090f8009fa6.tb.shawcable.net)
14:19.19seanbrightmornin'
14:21.11*** join/#asterisk-dev xrg_ (n=panos@77.83.40.166)
14:21.15filenods to seanbright
14:25.12*** join/#asterisk-dev isamar (i=1000@voice.maxirede.net)
14:25.16isamarhi folks
14:26.18ZaVoidhi isamar
14:27.55isamarZavoid
14:28.10isamarnot sure if I am offtopic here..
14:28.22isamarbut I am facing a problem with openser+asterisk+no rtp proxy
14:29.03isamarall my UAs register to Openser but outbound calls go thru openser->asterisk->openser->destination UA
14:29.09isamarand I am having the following error:
14:29.11ZaVoidi don't use openser
14:31.05isamarDisconnecting call 'SIP/X.X.X.X-085340d0' for lack of RTP activity in 11 seconds
14:31.11lmadsenisamar: you are quite off topic
14:31.23isamarok. thanks
14:43.51*** join/#asterisk-dev snuff-home (n=snuff-ho@60-240-117-7-nsw-pppoe.tpgi.com.au)
14:57.29*** join/#asterisk-dev snuff-home (n=snuff-ho@60-240-117-7-nsw-pppoe.tpgi.com.au)
14:59.54*** join/#asterisk-dev russellb (n=russell@asterisk/developer-and-stable-maintainer/drumkilla)
14:59.54*** mode/#asterisk-dev [+o russellb] by ChanServ
15:10.39*** join/#asterisk-dev joetester2 (n=joeteste@216.191.34.13)
15:19.52sruffelltzafrir: ping
15:20.44tzafrirsruffell, pong
15:21.47sruffelltzafrir: have anything you would want in a 1.4.10.1 release?
15:21.50sruffellof zaptel..
15:23.15tzafrirthere were a few small fixes:
15:25.40tzafrirr4193, r4187, r4165
15:26.56tzafrirThere's a small and nasty bug that I still have not fully tested . When do you want to release?
15:27.53sruffellWe were thinking about today because of the issue with the udev rules.....how much time would you like?
15:29.50sruffellhindsight being what it is...I should have started to move on a 1.4.10.1 after jsmith first brought the issue to my attention.
15:29.57sruffelloh well...
15:39.03*** join/#asterisk-dev Cresl1n (n=matt@216.207.245.1)
15:39.03*** mode/#asterisk-dev [+o Cresl1n] by ChanServ
15:39.19*** part/#asterisk-dev isamar (i=1000@voice.maxirede.net)
15:42.33tzafririf it is today then that specific issue of mine will probably wait
15:43.21Cresl1nhey tzafrir
15:43.33Cresl1nheard you have a list of a few patches you'd like to see go into a 1.4.10.1 release :-)
15:46.00Cresl1nif you could get that too me, I'm working on rolling a 1.4.10.1 right now
15:48.37sruffellCresl1n: r4193, r4187, r4165 are the revisions he posted earlier....
15:51.28ctooleyCorydon76-dig, BTW I was looking through all my old bug reports, 10363 can be closed, later bugs/patches resolve the issue.
15:52.09ctooleyit's purely a cosmetic thing as it's already "suspended" but it's unnecessary.
15:52.22*** join/#asterisk-dev outtolunc (n=me@adsl-66-218-53-172.dslextreme.com)
15:54.45tzafrirCresl1n, <tzafrir> r4193, r4187, r4165
15:57.06*** join/#asterisk-dev RoyK (n=roy@c51008389.inet.catch.no)
16:30.57*** join/#asterisk-dev atis_home (n=chatzill@193.238.213.215)
16:31.51Corydon76-digCresl1n: ping
16:31.58Cresl1npong
16:32.32Corydon76-digPer community feedback, what would you say to making a 1.4.11 RC instead of a 1.4.10 release?
16:32.56Cresl1nI don't know if I'd do one instead of a 1.4.10
16:33.03Cresl1n1.4.10 has a bug that needs to be fixed
16:33.27Cresl1nif we do a 1.4.11, we need to do a full regression test, and there are a couple of things we're working on getting into 1.4.11 as well that aren't there yet
16:33.54Corydon76-digAh
16:33.54Cresl1nWhy do you ask, pray tell?
16:34.19Corydon76-digWe've gotten heat for making releases "that aren't well tested"
16:34.47Cresl1nYeah, that's something I'm planning on changing
16:34.49Corydon76-digIf we make release candidates instead, first, that may help with some of the accusations
16:34.52Cresl1nI've been wanting to do it for a while
16:35.12lmadsenI like the idea of RC's for zaptel like we have for asterisk now
16:35.24Cresl1nwe're going to start making a release branch to give a few days of testing before releasing
16:35.54Cresl1nwell, it's also that we can still have branch/1.4 be active and not hold progress on it for an extended period of time
16:36.00Cresl1nduring release testing
16:36.09Corydon76-digRelease branch or release tag?
16:36.14Cresl1nsame thing in svn
16:36.23Cresl1nthe branch will be the tag
16:37.35Cresl1nAlthough I suspect that even doing that would not fix the bug that Steve Totaro complained about
16:37.50Cresl1nthat was a regression due to all the makefile madness that has been going on
16:38.11Corydon76-digCresl1n: yes, but you can throw it back at Totaro... "well, you didn't catch it during the RC series, either"
16:38.20Cresl1nyeah
16:38.50Corydon76-digNot that this is a blame game, but it's open source.  We aren't hiding the development branch from anybody.
16:39.17Cresl1nthere are arguments in both directions
16:39.57russellbon a slightly different yet related topic ...
16:40.04russellbI'd like to start release candidates for Asterisk 1.4.20
16:40.04Cresl1nI've been wanting to do a release branch for a few days before release (during testing) anyways, so we don't have to freeze branches/1.4 for that long
16:40.06russellbanyone opposed?
16:40.15Corydon76-digrussellb: sounds good
16:40.35Corydon76-digrussellb: Ready for release candidate signing?
16:40.40Corydon76-digchomps at the bit
16:42.15ZaVoidi'd like to test rc 1.4.20 for the realtime fix
16:42.34russellbCorydon76-dig: not yet
16:42.47russellbI just wanted to do a quick ping before I built the RC
16:43.01russellbfile: I request your ACK on this subject
16:43.06russellbputnopvut: you too.
16:43.21russellband anyone else :)
16:43.37ZaVoidACK ;)
16:43.53russellbcool :)
16:44.27russellband Qwell ^^^
16:44.44russellbmust be lunch time.
16:44.51ZaVoidlol
16:44.51seanbrighthorrible idea.
16:44.59seanbrightducks
16:45.03ZaVoidso what happened with the realtime bug russel?
16:45.10russellbZaVoid: I have no idea what you're talking about
16:45.22russellbbug #?
16:45.48ZaVoidintroduced in 1.4.19.. the one where you can't dial a sip outbound from a realtime peer.
16:45.49russellbkeep in mind that i look at 29384729384 bugs
16:45.49ZaVoidlet me get bug #
16:45.53ZaVoidi know:)
16:46.22ZaVoidapparently my techs are slacking off today they are working on installing osX on their pc's
16:46.43russellbheh, you allow them to install illegal software on work pcs?
16:46.50russellbmust be a small shop :)
16:46.50filerussellb: ACK
16:47.06ZaVoidno its there pc's they brought in
16:47.12russellbah ..
16:47.13ZaVoidlong as i don't own em i don't care
16:47.21russellbnods
16:47.44russellbok, well i'm building the RC ..
16:48.58paravoidplease include ABI changes to your regression testing
16:49.07paravoidwe've bitten by this multiple times in te past
16:49.56russellbyou mean your regression testing?
16:49.59russellb;-p
16:50.14ZaVoid0012362
16:50.17russellbi think we're doing better about that now.  I am specifically watching for those changes now
16:50.17ZaVoidthats the one
16:50.21russellbM12362
16:50.22MuffinMan[closed] [Asterisk] Channels/chan_sip/General 0012362: Asterisk crashes everytime i try to dial a realtime peer. e.g.DIAL(SIP/peer/number,60,tTwW) reported by vinsik (Karma: +0.50) http://bugs.digium.com/view.php?id=12362
16:50.37russellbah, well it's closed, so I guess it's fixed :)
16:51.26ZaVoidyeah
16:51.31ZaVoidbut it got broken in first place ;)
16:51.47russellbsorry!!!
16:51.48ZaVoidi guess not a lot of us use realtime?
16:51.54ZaVoidhehe not giving you shit russelb
16:51.56russellbbegs for forgiveness
16:52.01ZaVoidjust saying i'll test it when the rc comes out today
16:52.09ZaVoidit'll get my guys to stop installing osx at least lol
16:52.09russellbthanks for the testing help :)
16:52.12russellbi know you weren't giving me shit ...
16:52.25ZaVoidfigure i can start testing more now.. or at least try too
16:52.42russellb98 fixes since 1.4.19
16:52.43russellbnot bad
16:53.06fileevery issue is my fault
16:53.26Qwellassigns all open bugs to file
16:53.29russellbfile: obviously.
16:53.32ZaVoidwho can i blame for iax? ;)
16:53.41seanbrightZaVoid: russel
16:53.47ZaVoidperfect
16:53.49seanbrights/russel/russell/
16:53.55ZaVoidthanks to russel i gotta support another protocol ;)
16:53.57paravoidthis may be a horrible idea, but have you thought of concetrating all the external-ABI-parts to a single header file
16:54.08seanbrightactually, s/l/ll/ would have been easier, heh.
16:54.10ZaVoidi'm actually having 500 iax devices built now.. so i gotta build me an iax load balancer now :(
16:54.17paravoidso that eyebrows can be raised more easily on ABI changes?
16:54.40paravoidthis may sound silly and/or not be feasible
16:55.06*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
16:56.02ZaVoid2 line iax devices.. junk!
16:57.14russellbparavoid: that header file would be massive ...
16:57.50paravoidprobably :P
16:57.51seanbrightuse PCHs
16:57.56seanbrighti think gcc supports them
16:58.03seanbrightlooks
16:58.07paravoidoh well, I'm trying to think a way to easily detect such changes
16:58.23seanbrightyup -> http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html
16:58.33ZaVoidhey russ
16:58.44russellbhey ZaVoid
16:58.49ZaVoidi was looking for a doc that shows the major dialplan changes between 1.4 and 1.6... but i'm stupid and couldn't fidn it....
16:58.57ZaVoidcuz i wanted to test out 1.6 soon too
16:59.00russellbUPGRADE.txt includes that info
16:59.05ZaVoidi figure i gotta re-write half my scripts
16:59.12ZaVoidoh the one i didn't check... figures
16:59.13ZaVoidbrb
16:59.34ZaVoidthat wold make sense too.....
17:01.04russellbwe really try not to make sense, so I guess that was a failure :(
17:01.13ZaVoidgood job sir
17:01.32Qwellbbryant: feature request!  .read method for AGC() and DENOISE() :)
17:01.42ZaVoidhey you use a MBP right russ?
17:01.57Qwellmight be useful to tell what they're set to
17:02.32bbryantQwell: that's true
17:02.51bbryanti can add that pretty easily, too
17:02.54Qwell!! always throws me off, heh
17:03.18ZaVoidMacro() is now deprecated. :(
17:03.23ZaVoidyer killing me lol
17:03.58ZaVoidoo the read change is nice
17:07.02ZaVoidcan i ask a nother stupid question?
17:07.09ZaVoidThe concise versions of various CLI commands are now deprecated. We recommend
17:07.10ZaVoid<PROTECTED>
17:07.31Qwellall of them
17:07.34ZaVoido
17:07.43Qwellanything with a 'concise'
17:10.51tzafrirhmm... in zaptel we have both ARCH and UNAME_M . One has to override both of them?
17:11.28tzafrirAlso, is overriding Kbuild's ARCH is a good idea?
17:12.18tzafrirARCH is set from the kernel config directory, isn't it?
17:13.53ctooleyoej around?
17:14.05ctooleyapparently not, autocomplete didn't work.
17:17.03russellbI don't expect we'll actually remove Macro anytime soon, it's so widely used
17:17.18russellbmaybe we could write some sort of compatability mode that uses GoSub internally
17:17.24QwellI thought macro used gosub stuff internally now?
17:17.30russellbdoes it?
17:17.36Corydon76-digIt does not
17:17.38Qwelloh
17:17.41Qwellwell, couldn't it?
17:17.48Corydon76-digNope, not really
17:17.54russellbwhy not?
17:17.58Qwellseems a bit silly to remove something so widely used as macro
17:18.01Corydon76-digMacro exits on hangup.  gosub does not.
17:18.04russellbyou'd have to hack something up to automatically return
17:18.12Corydon76-digMacro returns implicitly.  Gosub does not.
17:18.15russellbcome on, it's doable :)
17:18.28russellbthat's what i mean, if run as a macro, automagically return
17:18.50ZaVoidautomagically is the best word
17:18.50Corydon76-digI dunno
17:19.39Corydon76-digMacro eats thread stack for breakfast.  Gosub doesn't really affect the stack
17:20.18Corydon76-digOn the whole, Gosub is massively lightweight
17:20.22russellbsure
17:20.29ZaVoidanyof you ever install asterisk on os x for testing?
17:20.34russellbhow does that affect being able to make Macro use GoSub internally?
17:20.47russellbZaVoid: yes, a lot of us have macs
17:20.56Corydon76-digrussellb: Totally different model
17:21.05ZaVoidany special build for em? i was gonna try it tonight on mine
17:21.17ZaVoidjust wondering if anything i should know before i give it a go
17:21.21Corydon76-digMacro runs its own internal call loop.  Gosub exits almost immediately
17:21.51ctooleyCorydon76-dig, the internal functionality of GoSub is so dramatically different it couldn't be made to externally appear to function like Macro?
17:22.23Corydon76-digIn fact, there is one thing we could do to make Macro eat less stack:  manage the Macro recursion
17:22.24russellbmy point is, that I'm really not ok with removing Macro
17:22.34russellbit has been there for way too long, and too many dialplans depend _heavily_ on it
17:22.52ctooleyI know mine all do.
17:22.58russellbctooley: you're not alone
17:23.27Corydon76-digWell, we'll see what shakes out during the 1.6 cycle
17:23.45ctooleythough, actually, most of mine will likely be moved to either EIVR apps, AGI apps, or would perform better with GoSub.
17:23.52russellbmind if I change the UPGRADE.txt to reflect that so people don't freak out?
17:24.18Corydon76-digrussellb: experimentally deprecated?
17:24.43Corydon76-digrussellb: if we're going down that road, I suppose AgentCallbackLogin would have the same status
17:25.00russellbwell, i'd say it's deprecated for performance reasons, and for new dialplans, this other usage is encouraged
17:25.07russellbbut that we won't remove it for backwords compatability reasons
17:25.21russellbso people dont' freak out based on existing dialplans that use it heavily
17:25.46Corydon76-digrussellb: additionally, warn people that mixing the two is heavily discouraged
17:25.58ZaVoidcould i  bug one of you for 4-5 mins of help getting it compile on my MBP?  i get this configure:2441: error: no acceptable C compiler found in $PATH  I've never installed a compiler seperately i'm guessing i need to?
17:26.04russellbCorydon76-dig: sounds good
17:26.14QwellZaVoid: well..yeah
17:26.20russellbZaVoid: on mac?  install xcode tools
17:26.31ZaVoidok i can do that thanks
17:27.11*** join/#asterisk-dev oej (n=olle@65.42.208.134)
17:27.11*** mode/#asterisk-dev [+o oej] by ChanServ
17:27.22ctooleyoej, I was just looking for you. :)
17:28.53russellboej: run!!!!!
17:30.05ctooleyI was just going to ask if the SIP failover code was going to be able to go into 1.6
17:30.26russellb1.6 is always fair game
17:30.34Qwellctooley: yes.  the real question is whether it would go in 1.6.x
17:30.40russellbif it doesn't make it into 1.6.X, it is fair game for 1.6.X+1
17:31.35ctooleyIt's well tested in 1.4 already... we've "failed over" dozens of times since we got the patch in.
17:32.11ctooleyI know it can't go in 1.4 BTW
17:32.18ctooleyI was just making a comment.
17:32.55russellbfails over
17:35.54oejyes it will go to trunk
17:36.27oejwaits at O'hare...
17:36.52fileoej: are you flying over me again?
17:37.07oej'helmet on
17:42.44oejBack later...
17:44.27*** join/#asterisk-dev elguero (n=elguero@ns1.nashuacs.com)
17:46.35ZaVoidbah 2 hours left for xcode tools :(
17:46.53ZaVoidhey russ when you think 1.4.20 RC will be out today?
17:47.03russellbyou can check it out of the svn tag if you want it now
17:47.09russellbi just have to collect gpg signatures first
17:47.16russellbsvn co asterisk/tags/1.4.20-rc1
17:47.18ZaVoidnah i'll ait for the real deal
17:47.22russellbk
17:47.33ZaVoidotherwise internally i'll have to retest it again
17:47.50Corydon76-digZaVoid: if you want it faster, write the release announcement for Russell
17:48.14ZaVoidNEWSFLASH: 1.4.20 RC1 RELEASED!!!!!!!!
17:48.18ZaVoidhows that?
17:48.26ZaVoidnot enuff !!! ?
17:48.29russellblammmme
17:48.42ZaVoidhmm
17:49.30ZaVoidThe Asterisk development team has released version 1.4.20 RC 1 This release fixes over 98 issues over 1.4.19.1 We expect you'll love it and we promise there is nothing borked in this release!
17:49.32ZaVoidbetter?
17:50.42Corydon76-digAlmost there.  You also need to say where it can be found
17:51.03ZaVoidAll releases are available for download from the following location: http://downloads.digium.com/pub/telephony/asterisk/
17:51.04ZaVoid:)
17:51.27ZaVoidi'm available for parties as well thanks thanks very much
17:51.31Corydon76-digand thank people for flying Asterisk  ;-)
17:51.59ZaVoidThank you for your continued support of Asterisk!(r)
17:52.40Corydon76-digrussellb: wanna do a release announcement that looks like an IRC conversation?
17:52.51russellbheh
17:52.55russellbthat could be amusing.
17:53.09QwellOH HAI.  1.4.20-RC1 CAN HAZ RELEASE?
17:54.04Corydon76-digWe need to make "can haz cheezburger" a native CLI command
17:54.25russellbdo it!
17:54.43russellbwouldn't that be, "cheezburger can haz" ?
17:54.43Qwellmake it part of a larger commit
17:54.44Corydon76-digI'm not sure what it would do, though
17:54.45jsmithrussellb: Wouldn't that be <module> can haz cheezburger
17:54.54Qwellcheezburger haz can
17:54.57*** join/#asterisk-dev RoyK (n=roy@253.80-203-34.nextgentel.com)
17:55.30ZaVoid1.4.20-RC1 2 31337 4 U!!!
17:56.16ZaVoidcore show application bitchx  needs to be there too or toolz or infinity
17:57.12ZaVoidcome on some of you old timers gotta know toolz or infinity
17:58.08Corydon76-digSorry, I was using sirc at the time
17:58.27Corydon76-digOddly, I still am using sirc.
17:58.57ZaVoidreally?
17:59.07Corydon76-digwith a wrapper
17:59.24ZaVoidahh old ircII users.. and loved my delphi vax irc client :)
17:59.32Qwellepic
17:59.39Corydon76-digsirc > ircii
17:59.53Corydon76-digI used ircii before I discovered sirc
18:00.20Corydon76-digEven built myself a /nuke command in sirc
18:00.24russellbmy first IRC client was mIRC :(
18:00.36putnopvutditts from me.
18:00.39ZaVoid:(
18:00.44Corydon76-digAh, Windows 95... those were the days
18:00.45ZaVoidefnet 4 life Corydon76-dig
18:00.50Juggierussellb, it better have been on windows 3.1
18:00.52seanbrightircle!
18:01.03russellbJuggie: probably windows 95 or 98
18:01.05Juggiewith trumpet winsock
18:01.06Corydon76-digI wasn't using Win95, but I sure did enjoy sending a BSOD to everybody who was
18:01.08russellbi'm pretty new school
18:01.40Juggiewin3.11+trumpet winsock+win32bit dlls, hawt.
18:01.44ZaVoidport 139 cory
18:01.47seanbrightthe author of ircle tested his video streaming changes by streaming porn to me from .nl
18:01.52seanbrightit was _awesome_
18:01.56seanbrightheh
18:01.56russellblol
18:02.03Corydon76-digZaVoid: nuke was OOB data
18:02.53Juggieyes, teardrop was fun
18:02.55ZaVoidyou remember the old mac irc client... what was it... had simpsons references in for os 7xxx
18:03.16seanbrightwrote a cron job that sent that to a coworkers PC every hour... forgot to turn it off
18:03.18ZaVoidhad big switchs for channel settings lol
18:03.36seanbrightZaVoid: oh yeah... can't remember either
18:03.40Corydon76-dighttp://www.iagora.com/~espel/sirc/scripts/winnuke.pl
18:03.44seanbrightgoes to puremac
18:03.45ZaVoidyou know what i;'m talking about though sean :)
18:03.51Corydon76-digMy first ever published software code
18:03.53seanbrightZaVoid: i do
18:05.28*** join/#asterisk-dev joetester2 (n=joeteste@216.191.34.13)
18:05.28seanbrightZaVoid: homer?
18:05.28ZaVoidi had a mansion BBS and the mac WWIV bbs software too
18:05.28ZaVoidhomer!!!!
18:05.28ZaVoidthats it!!
18:05.28seanbright"Said to be slow and buggy, and not updated since 1995, but good for beginners. Many Homer users have moved to iRCle. Homer lacks some basic features such as DCC."
18:05.32ZaVoidhttp://www.ircreviews.org/clients/homer.html
18:05.40ZaVoidlol
18:05.40ZaVoidgreat interface though
18:05.48seanbrightfox probably sued them
18:11.10ZaVoidbrb phone
18:15.48ZaVoidno plans for the tcb400 to transcode ilbc right?
18:17.25russellbcorrect
18:17.26kpflemingZaVoid: correct
18:17.32ZaVoid:(
18:17.38russellb#define ilbc g729
18:17.39russellbyes
18:24.38ZaVoidyes?
18:25.02fileZaVoid: he means no.
18:25.08russellbif by ilbc, you mean g729, then yes
18:25.08ZaVoidah
18:25.12ZaVoiderr
18:25.14ZaVoidno
18:25.51ZaVoidor g723r63 :(
18:26.07russellbactually, that's not completely true
18:26.13russellbwe now properly accept 63
18:26.17russellbbut we will always sent 53
18:26.22russellbi think ..
18:26.25files/sent/send/
18:26.28russellbyes.
18:26.41fileasks for one of russellb's grapes
18:26.46russellbalready ate them all
18:26.48russellbsry
18:26.51filelame
18:27.13ZaVoidwont' send r63? meh
18:27.27*** join/#asterisk-dev oej (n=olle@2.234.241.83.in-addr.dgcsystems.net)
18:27.27*** mode/#asterisk-dev [+o oej] by ChanServ
18:27.51Corydon76-digThe encoder isn't capable of that variant
18:28.14ZaVoidmain variant used by crap carriers :(
18:28.27russellbwell, they should be able to accept 53 :)
18:28.30ZaVoidactually i could just send them g729
18:28.39ZaVoidheh ever deal with grey market termination russel?
18:28.47russellbnope.
18:28.55ZaVoidconsider yourself lucky :)
18:28.57russellbi don't deal with any "real" usage issues :-p
18:29.02ZaVoidouch
18:29.16russellbi just try to fix things for the people that do
18:29.16ZaVoidi deserved that huh lol
18:29.42russellbit wasn't a slam ... just saying
18:29.51russellbi don't directly deal with using asterisk in production :)
18:30.08filethank god Digium is not a VoIP provider
18:30.20Corydon76-digbut it is
18:30.25Corydon76-digthrough iaxtel
18:30.33russellbiaxtel hasn't existed for like a year
18:30.55ZaVoidany reason won't send r63.. or just time to code it?
18:30.56Corydon76-digShows you how often I use it.  ;-)
18:31.12Corydon76-digZaVoid: it's all licensed code
18:31.24ZaVoidr53/r63 different license?
18:31.30russellbshrugs
18:31.35Corydon76-digDifferent firmware
18:31.53Corydon76-digThe firmware that we use is not capable
18:32.14ZaVoidahh so not even a chance.. gotcha
18:32.25Corydon76-digHey, if you really want small, use LPC10
18:32.27ZaVoidbut if the r63 recieve is fixed i'll try em again..
18:32.30ZaVoidmaybe take some load off my servers
18:32.34ZaVoid80 load is no fun :(
18:33.50oejyet another airport.
18:34.36Corydon76-digoej: you should get your pilot's license and fly direct.  ;-)
18:34.39Qwellbbryant: you rock
18:34.48ZaVoidairport?
18:34.53oejCorydon: or just get Mark to fly me...
18:36.01russellbheh, i dont' think mark's plane can cross the pond
18:40.45ctooleyoej, which airport now?
18:41.14oejThe all so wonderful extravagant luxury Chicago O'Hare - on my way home again
18:43.08ZaVoidDA BEARS
18:43.27russellbheh
18:43.37ZaVoideagles fan here actually
18:43.42Corydon76-digda bulls
18:44.10russellbi haven't chosen a team ...
18:44.23russellbmostly because i don't really care.
18:45.16Corydon76-digSo you're saying you don't have Titan Fever?
18:45.38ZaVoidsoon the tc400b 120 bi directional g729a... what if i have more then 120 active calls? i can install 2?
18:45.47ZaVoidyou guys lost pacman!
18:46.01Corydon76-digGood riddance
18:46.05russellbyes, you can install 4 if you want
18:46.09oejAdtran just released an IP pbx...
18:46.18Corydon76-digor 7, if you have enough PCI slots
18:46.18ZaVoidnah 1U boxes.. can't install 4 lol
18:46.24russellboej: orly?
18:46.29russellboej: link?
18:46.30ZaVoidprobably not even 2 come to think about it
18:46.38oejhttp://www.voipplanet.com/solutions/article.php/3743901
18:48.56ctooleyYeah, we've had a demo unit in house for a few days.  Not too bad.
18:50.41ctooleyThe sales droids like it cuz it is easy.  The sales engineers like it cuz it passed the certification process.  The techsupport people... yeah, not so much.
18:50.56ZaVoidi can't even find a place to download homer seanbright
18:52.47ZaVoidhaha found it!
18:53.53ZaVoidbah it won't open
18:53.56russellbctooley: easier than switchvox, though?  I doubt it!  :)
18:55.36*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
18:55.51ctooleyrussellb, depends on what you're doing.  We're a telephone company, having something that we can easily "auto-provision" in house the way Switchvox auto-provisions is handy.  And since we use Adtrans in a lot of other places it has some draw.  We do however recommend ABE to a lot of people that need more than "Press 1 for sales,..." auto-attendants.
18:56.13russellbcool :)
18:56.22ctooleyrussellb, we've also never gotten a switchvox box to "certify" on our network... because I expect it to be soooo different than ABE.
18:56.30russellbi don't mean to be applying any pressure ... that's really not my place
18:56.39russellbwe're supposed to be agnostic around -dev :)
18:56.53russellbctooley: yeah, it will likely be different
18:57.00ctooleyeh, I don't make those decisions either way.  I do however, hear all the crap.
18:57.25ctooleyHow would it possibly be different?  They still use the same PRI cards and the same SIP stack, don't they?
18:57.56ctooleyWe don't care how the configuration screens look, we really only care whether the PRIs talk to our switch or the SIP stack talks to our SBCs.
18:58.23russellbyeah, they do, but switchvox is currently based on 1.2
18:58.31ZaVoidwhich sbc's ctooley ?
18:58.37russellbsession border controller
18:58.38ctooleypeople who aren't using at least a PRI for voice... they're probably not our customers so we don't even bother with FXO ports.
18:58.45ZaVoidnextone/sansay/acme?
18:59.00ctooleyWe use several different ones, but ACME is our primary customer facing ones.
18:59.03russellbZaVoid: oh, i thought you were asking what SBC stood for, heh
18:59.10ZaVoidno russellb
18:59.16russellbi should have known, sorry
18:59.19ctooleyI personally can't stand the ACMEs, but some people like them.
18:59.23ZaVoidyou like them? i hear bad things about thier routing.. we use mostly nextone's and sansays
18:59.30ZaVoidguess that answers it lol
18:59.56ZaVoidsansay has my favorite tag line.. "masters of voip"
19:00.00ctooleyI had Netrake nCite's at my last job, they're a giant pain in the but to get the routing set up on, but once you do, they're great.
19:00.14ZaVoidentice?
19:00.19ZaVoidfrom texas?
19:00.40ctooleyNetrake was the company name, Audiocodes bought them.  Yeah, they were from Dallas.
19:00.48ctooleyI think their tag line was "not cheap"
19:01.36ZaVoidactually i'm thinking o stratus they are called now
19:01.58ZaVoidhttp://www.stratus.com/telecom/ <-- THESE GUYS? woah caps
19:02.34ctooleyah, nope.
19:03.24ZaVoidahh ok
19:03.37ZaVoideverr work with nextone much?
19:04.25ctooleyNextone refused to sell me an SBC on the schedule I needed it delivered on (which was measured in weeks) the first time I dealt with them.  Afterwards, I never looked back.  Plus, at the time, they were not able to do the port density I needed.
19:04.44ZaVoidreally?
19:04.59ZaVoidhow long ago was that?
19:05.06ctooleycouple years go
19:05.08ZaVoidhmm
19:05.18ZaVoidwe had one pair of MSW's doing 20k concurrent calls at one point
19:05.27ZaVoidand that was on the "OLD" hardware
19:05.37Corydon76-diglmadsen: ping
19:11.31*** join/#asterisk-dev elguero (n=elguero@ns1.nashuacs.com)
19:11.42oejcorydon: I'll tell him when I fly by...
19:13.44ZaVoidwtf.. Classic enviroment no longer supported in 10.5?
19:24.08elgueroquit
19:24.14elguerooops...
19:33.36oejRussell: We missed something yesterday.
19:34.12oejrussellb: I already have a queue entry for state notifications with a flag. The patch adds the ability to send SIPfrags, which is not handled properly yet.
19:34.19seanbrightbefore i try something stupid and screw this up... can i do two svnmerges in a row without committing in between?
19:34.26oejrussellb: So the question remains... Why doesn't it work?
19:34.39Qwellseanbright: no, svnmerge will check for modifications and fail if it finds any
19:34.48seanbrightQwell: oh right.  good call.
19:34.50Qwellyou can, however, merge two revisions
19:35.09oejLogging off for a while...
19:35.10Qwellsvnmerge merge -r<rev1>,<rev2>
19:35.39seanbrightmeh... i'll just commit in between :)
19:37.07*** join/#asterisk-dev RoyK (n=roy@253.80-203-34.nextgentel.com)
19:38.29*** join/#asterisk-dev putnopvut (n=putnopvu@216.207.245.1)
19:38.29*** mode/#asterisk-dev [+o putnopvut] by ChanServ
19:41.40seanbrightahhh... much better.
19:42.19*** join/#asterisk-dev elguero (n=elguero@ns1.nashuacs.com)
19:47.14*** join/#asterisk-dev miguel3239 (n=elguero@ns1.nashuacs.com)
19:47.32*** part/#asterisk-dev miguel3239 (n=elguero@ns1.nashuacs.com)
19:54.01*** join/#asterisk-dev CrashHD (n=CrashHD@65.74.161.225)
19:56.11*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
19:57.32lmadsenCorydon76-dig: pong
19:58.12ctooleylmadsen, you're supposed to wait until you see the:  Corydon-dig has quit
19:58.24lmadsenoh crap... I've screwed up again
19:58.28lmadsenI already know what he wants :)
19:58.30lmadsenM10540
19:58.32MuffinMan[assigned] [Asterisk] Functions/func_timeout 0010540: timeout value should accept floating point numbers reported by spendergrass (Karma: neutral) http://bugs.digium.com/view.php?id=10540
19:58.43lmadsenI have no update yet... maybe tonight after a couple of these consulting calls I have scheduled :(
19:59.02Juggielmadsen, slacker.
19:59.12lmadsenactually... I'm doing anything but slacking today :)
19:59.21ZaVoidsean you on 10.4 or 10.5?
19:59.21lmadsenyesterday however... that's a different story
20:02.31ZaVoidhey russellb ?   xcode and dashcode i should install?
20:02.31seanbrightZaVoid: 10.4 at home
20:02.47ZaVoidyou can ron homer then still seanbright ... i forgot classic was taken out of 10.5
20:02.53filexcode.
20:02.56ZaVoidthanks file
20:02.59filetools.
20:03.03ZaVoidyep
20:03.16seanbrightZaVoid: i'm sure i could... but why would i want to? :)
20:03.24ZaVoidanything esle i should know file?
20:03.28seanbrightis pissed that the iPhone SDK only runs on 10.5
20:03.33ZaVoidseanbright: take a screenshot with skitch and share it with us :)
20:03.36fileyes, I'm sleepy.
20:03.43ZaVoidneed a bed time story?
20:03.51filealas no
20:03.54seanbrightthere once was a man from nantucket
20:04.53Corydon76-diglmadsen: actually, I was going to ask you to give a quick run-through on 12402
20:05.09Corydon76-digespecially since you have access to busy systems which would benefit
20:05.14ZaVoidno 10.5 seanbright ? older mac?
20:05.29seanbrightZaVoid: haven't really been using it.  not worth buying the upgrade.
20:05.34ZaVoidah
20:05.38seanbrightZaVoid: 1st gen mbp
20:05.46seanbrightZaVoid: supports 10.5 i believe
20:05.50ZaVoidwith intel chip?
20:05.52seanbrightaye
20:06.01seanbrightyou could fry an egg on it
20:06.01ZaVoidso core2.. not duo
20:06.01Corydon76-digseanbright: which one did you get?
20:06.02seanbrightheh
20:06.18seanbrightCorydon76-dig: the 15 inch
20:06.20ZaVoidi put a 250gb drive in m mbp... it burns my leg
20:06.33Corydon76-digZaVoid: first gen was core duo, not core 2 duo
20:06.40seanbrightcorrect
20:06.43seanbrightthats what i gots
20:06.51Corydon76-dighas 2nd gen
20:06.52ZaVoidright thats what i said i think?
20:06.58ZaVoidi got 2nd gen too
20:07.12Corydon76-digjust upgraded the HD to 320GB
20:07.24ctooleyCorydon76-dig, that a trunk patch or a 1.4 patch?
20:07.26seanbrightjust upgraded to a dell m1330 ;)
20:07.33seanbrightwith a 64GB SSD
20:07.34ctooleyCorydon76-dig, 12402 I mean.
20:07.35seanbrightbam
20:07.43Corydon76-digctooley: I'm sure it would work on 1.4, but it was against trunk
20:07.58ZaVoid320 in the mbp?
20:08.03ctooleyCorydon76-dig, I'll try applying it to 1.4 and if it works iti
20:08.04ZaVoidthats gotta be hot
20:08.09ZaVoid5400rpm though right?
20:08.13Corydon76-digright
20:08.16ctooleyit'll be on a busy server in 20 minutes or so.
20:08.22ZaVoidmy buddy but a 7200 in his. i shoulda done the same
20:08.26Corydon76-digctooley: sweet
20:08.42ctooleyCorydon76-dig, that bug breaks some of our monitoring tools. :)
20:08.44Corydon76-digI'm not concerned with HD speed, only capacity
20:08.52Corydon76-digctooley: woot
20:08.58ZaVoidso Corydon76-dig other then installiny xcode.. anything special i need to worry about compiling asterisk on mac os?
20:09.14Corydon76-digZaVoid: just one thing
20:09.30Corydon76-digThe poll(2) interface on OS X is badly broken
20:09.51ZaVoidhuh?
20:10.17Corydon76-digIf you attempt to use the builtin poll function in OS X, you will be sorry
20:10.46Corydon76-digThere is no other way to put that.
20:10.57ZaVoidok
20:11.30Corydon76-digThere are two bugs on the bugtracker recently which come back to that point
20:15.00ctooleyCorydon76-dig, everything applied but a log message inside logger.c
20:15.10ctooleyless logging is good sometimes. :)
20:17.38Corydon76-digHeh
20:18.38bbryantdoes anyone know where console commands are in the source tree?
20:20.28seanbrightbbryant: all over
20:20.46seanbrightbbryant: unless you mean just main/cli.c
20:20.53bbryantseanbright: that's what i figured
20:20.59seanbrightbbryant: they are registered in individual modules though
20:20.59bbryanti'm trying to find an example of one
20:21.07Corydon76-digctooley: you figure it out?
20:21.07seanbrightbbryant: search for AST_CLI_DEFINE in trunk
20:21.15bbryantthanks
20:21.40ZaVoidnice its compiling now
20:24.58ctooleyCorydon76-dig, the patch? yeah, I just ignored the log line.
20:25.18Corydon76-digctooley: new patch for 1.4 uploaded
20:25.56Corydon76-digctooley: if you ignore it, then you get a garbage character in any log file with VERBOSE set
20:26.08ctooleyah
20:26.23ctooleyI was more worried about how well the rest of the patch worked.
20:26.29Corydon76-digI used a single character preamble on all verbose messages
20:26.54Corydon76-digand then filter it at the display level
20:27.03ctooleyah
20:27.14ZaVoiddamn it froze on make
20:27.21ZaVoidapp_getcpeid.c
20:27.53Corydon76-digZaVoid: that would probably mean that you have hardware heat issues
20:28.15ZaVoidcome on
20:28.18Corydon76-digYou might want to think about getting a laptop coolor
20:28.34ZaVoid90 degrees celcius is not too hot!
20:28.44Corydon76-digHeh
20:29.03ZaVoidand you wunder why it burned my leg
20:29.18Corydon76-digI don't wonder.  I wear jeans.
20:29.45ZaVoidso do i
20:29.53ZaVoidmakes em toasty in the winter
20:30.24Corydon76-digand I don't keep my knees together.  It's cooler on the outside edges
20:30.39ZaVoidenuff about you on your knees please
20:31.10Corydon76-digHey, I have a reputation to uphold
20:31.29Corydon76-digor would that be downhold?
20:31.59ZaVoidZING
20:32.12lmadsenM12402
20:32.13MuffinMan[new] [Asterisk] Core/NewFeature 0012402: [patch] Restrict what is printed during -rx output reported by Corydon76 (Karma: +418.25) http://bugs.digium.com/view.php?id=12402
20:33.09Corydon76-diglmadsen: That's a long-running pet peeve of a good many people
20:33.18lmadsenindeed
20:33.44lmadsenI'm trying to think of who I could apply this to...
20:33.57Corydon76-digctooley is working on it...
20:34.04Corydon76-digthough on 1.4, only
20:34.13lmadsenthe client with the really busy boxes running OS is no longer a client of mine...
20:34.17lmadsenand everyone else is running ABE :)
20:34.23Corydon76-digAh, heh
20:34.25lmadsenoh glad that ctooley is picking up me slack
20:34.54Corydon76-diglmadsen: which leaves you to go back and distclean the 10540
20:34.57Corydon76-dig;-)
20:35.02ZaVoidrc is out
20:35.05ZaVoidnice thanks
20:35.24lmadsenCorydon76-dig: I have 30 mins to kill... let me do that
20:35.35lmadsentries to remember the IP of the test box...
20:35.58Corydon76-diglmadsen: you need your own domain, to keep those IPs in DNS
20:36.18Corydon76-digIt's why I bought vcch.net...
20:36.29Corydon76-digEvery client of VCCH is in that domain
20:36.45lmadsenI do have my own domain (several of them in fact), but I'm running dd-wrt, and I haven't figured out how to make it DHCP_BROADCAST the name instead of having to setup each VM manually
20:36.58Corydon76-digAh...
20:37.09lmadsensince they are temp boxes... so setting them up manually makes little sense...
20:37.22Corydon76-digWell, I do all of my DNS manually anyway
20:37.35lmadsenI'd even run a VM for the DNS as long as I knew how to get DHCP_BROADCAST to work (it works at Digium nicely.. maybe I'll ask how they do it)
20:38.09Corydon76-digThere's some integration between ISC named and dhcpd
20:38.29lmadsenya, exactly
20:39.01lmadsenmight be as easy as setting up named and adding some custom setting in dd-wrt... who knows
20:39.10Corydon76-digHeh
20:39.31lmadsenI haven't looked into it very closely... but I'm near that point now since I have my website back up, virtual machine server up, and wiki up for documentation
20:40.02lmadsenso basically all infrastructure is actually starting to come together :)
20:40.45lmadsenthat's my last pet peeve
20:41.28Juggielmadsen, dd-wrt uses dnsmasq
20:41.30Juggielook at that
20:41.47lmadsenya... I enabled it... but it didn't seem to just work out of the box... but maybe I'll give it a shot again
20:43.45Juggieworks out of the box for me i have DNSMasq for dhcp enabled
20:43.47Juggieand dns
20:43.53Juggieinfact i think it was enabled by default
20:44.59lmadsenwhat version you happen to be running?
20:45.04lmadsenof dd-wrt
20:45.28Juggiev24rc5
20:45.47Juggie(thats the last version worth running)
20:46.07lmadsenhrmmm... v23sp2 here
20:46.14lmadsenmaybe time to upgrade
20:46.19Juggieya, perhaps
20:49.14Juggieservices
20:49.36Juggiegrr, services tab is where yuo will find the dnsqmasq config
20:50.14Juggieso you can put like dhcp-option=16,192.168.1.1
20:50.14Juggieor whatever
20:52.21ctooleylmadsen, http://my-mili.eu/matt/docs/dynamic-dns-with-dhcp-and-bind-9/
20:53.36lmadsenthx ctooley
20:55.58*** join/#asterisk-dev tuxd00d (n=tuxd00d@128.187.132.25)
20:56.32ctooleyCorydon76-dig, It's building (had a delay) but I have a child emergency so I have to go.  It'll have to wait until tonight or tomorrow.
20:56.46*** join/#asterisk-dev atis_work (n=atis_wor@193.238.212.171)
20:56.46Corydon76-digctooley: okay, thank you for testing
20:57.12ctooley"testing"? Live production traffic. :)
20:58.13ctooleyis waiting on his wife to get back with the injured child.
21:03.44ctooleyis off. later folks.
21:04.01lmadsenlates
21:06.49*** join/#asterisk-dev fakhir (n=fakhir@unaffiliated/fakhir)
21:37.32*** join/#asterisk-dev ZaVoid (n=zavoid@c-67-165-25-195.hsd1.pa.comcast.net)
21:48.52*** join/#asterisk-dev ZaVoid (n=zavoid@c-67-165-25-195.hsd1.pa.comcast.net)
21:53.22lmadsenCorydon76-dig: 10540 looks good now
21:53.51Corydon76-diglmadsen: so distclean fixed it?
21:53.55lmadsenyes sir
21:54.03Corydon76-digExcellent.  Thank you.
21:54.04lmadsentested both absolute and response timeouts with success
21:54.38putnopvutYay, now my calls can be set to time out in 4.523 seconds.
21:54.54lmadsenyes they can!
21:54.59lmadsen5.2 seconds for my response timeout
21:55.10Qwellcan I do 5.2ms?
21:55.31QwellI guess that would just be like 0.0052
21:57.38Corydon76-digNo, only down to the millisecond in precision
21:57.55Corydon76-digWell, no, wait
21:58.26Corydon76-digHmmm.  I think that while it will represent down to the microsecond, only millisecond precision is actually supported
22:04.04*** join/#asterisk-dev anthm (n=anthm@70-9-119-28.area4.spcsdns.net)
22:39.31*** join/#asterisk-dev snuff-home (n=snuff-ho@60-240-117-7-nsw-pppoe.tpgi.com.au)
22:41.32Corydon76-digputnopvut: ping
22:41.43putnopvutCorydon76-dig: pong
22:41.59Corydon76-digawhile ago, you added a comment to the header file in sched.h
22:42.19putnopvutlet me pull that up.
22:42.21Corydon76-digI think the comment was based on a misunderstanding of the code in question, and I wanted to clarify it with you
22:42.30putnopvut1.4 or trunk?
22:42.37Corydon76-dig1.4
22:43.12putnopvutAh, the comment above AST_SCHED_DEL?
22:43.28Corydon76-digRight
22:43.49Qwellhmm, would somebody mind reviewing the patch on 12161?
22:43.50QwellM12161
22:43.51MuffinMan[closed] [Asterisk] Resources/res_agi 0012161: res_agi.c can still tell you to use DeadAGI for hung up channels reported by explidous (Karma: +1.25) http://bugs.digium.com/view.php?id=12161
22:43.54Qwell12161-lockfail.diff
22:44.13Qwell12162, rather
22:44.15Corydon76-digBecause it's a macro, if the ID changes, then since the location of the ID is referenced, the new ID is thus referenced
22:44.39Corydon76-digHence, I don't think the comment is really correct
22:44.55snuff-homeanyone help callguy for bug 12555
22:44.58russellbtakes the blame for that
22:45.03putnopvutI don't understand what you mean by "the location of the ID is referenced"
22:45.09Qwellrussellb: 12162 :D
22:45.13russellbQwell: not that
22:45.15Corydon76-digsecond argument to the macro
22:45.23QwellI'm volunteering you to review :p
22:45.24russellbwhat Corydon76-dig is talking about ...
22:45.27Qwellit's locking stuffage
22:45.30russellbQwell: but what if i don't wanna
22:45.32Corydon76-digIs the location of the ID value
22:45.38Qwellthen...
22:45.41Qwell~lart russellb
22:45.41jbotforces russellb to use Outlook Express
22:45.50russellbeep
22:45.51putnopvutCorydon76-dig: that doesn't really make sense to me.
22:46.13Corydon76-digputnopvut: a macro is just a code substitution, right?
22:46.17putnopvutright.
22:46.39Corydon76-digSo if you take one of the cases, and you do the substitution, you'll see what I'm talking about
22:47.36Corydon76-digBasically, the macro does exactly what you said it doesn't do
22:47.45putnopvutCorydon76-dig: I may not have expressed myself clearly in that comment...
22:48.29putnopvutBasically what I was saying is that if you try to delete an id that isn't in the scheduler queue, then it doesn't make sense to loop.
22:48.35Corydon76-digThe 3rd paragraph, in particular, is completely wrong
22:49.23Corydon76-digputnopvut: right, but the code can't know that.  The only way to know that there is no scheduled process is if the value is -1
22:49.38putnopvutno, not necessarily.
22:49.47Corydon76-digIf the value is positive, then it's assumed that the schedule is still active
22:49.59putnopvutassumed, but not necessarily.
22:50.02Corydon76-digThe scheduled process should set it back to -1 otherwise
22:50.15Corydon76-digputnopvut: unless there's a bug.  ;-)
22:50.35Corydon76-digwhich is precisely what we're trying to track down there
22:50.56putnopvutrussellb: you mentioned the use of the scheduler in chan_iax2 when you were telling me about that macro.
22:51.32putnopvutCorydon76-dig: what prompted me to add that comment was a discussion I had with Russell which was a tangent to a conversation about a bug that was happening in chan_sip.c
22:51.45russellbyeah, so ... like i mentioned, i think this is my fault
22:51.48Corydon76-digRight, chan_iax2 sometimes doesn't set the value back to -1, and we really need to track down why
22:52.27putnopvutAnd basically it came from the fact that if you are trying to delete a scheduled entry, it may be silly to loop to try to delete an entry when it simply does not exist in the scheduler queue any more.
22:52.50Corydon76-digI'd really like to see most of that commit reverted, but I need to do it the right way... by convincing you... ;-)
22:53.20Corydon76-digbut if it doesn't exist, then there's a bug.
22:53.26russellbso, i guess the macro is safe as long as the scheduled item either finishes and reschedules, or sets the val to -1, within 10 context switches
22:53.33putnopvutWhy is there a bug?
22:53.48russellbbecause if it doesn't get rescheduled, then it should be setting the scheduler ID to -1
22:53.56Corydon76-digrussellb: right, that was the assumption... that a scheduled process won't last longer than 10 context switches
22:54.01russellbnods
22:54.28russellbputnopvut: I wasn't thinking about the fact that it was a macro, and that it would take into account the possibility of the ID changing when the callback reschedules itself ...
22:54.37russellbi still don't think that should be a WARNING message
22:54.39Corydon76-digwhich should be a full second, unless the scheduled process is yielding
22:54.57Corydon76-digrussellb: it was a DEBUG before
22:55.11Corydon76-dighttp://svn.digium.com/view/asterisk/branches/1.4/include/asterisk/sched.h?r1=106704&r2=108227
22:55.23putnopvutBut it was a warning before that.
22:55.34putnopvutAnd a lot of people wrote e-mails to the users list asking about it.
22:55.40Corydon76-digOh, okay
22:55.59Corydon76-digWell, I have no problem with it being DEBUG, but I think the comment should go away
22:56.33russellbok, i'm fine with the comment going away
22:56.41russellbbut i am not ok with it being a higher log level than debug
22:56.46Corydon76-digThe reason why I made it a WARNING originally is that I thought that being unable to cancel something meant that we had a condition that was likely to cause a crash
22:56.49russellbputnopvut: i apologize for the confusion ...
22:56.55putnopvutI'm still confused as hell.
22:56.57Corydon76-digsince generally we cancel stuff before freeing memory
22:57.15Corydon76-digand a scheduled job on freed memory... ouch...
22:57.56russellbyes, that is bad
22:58.01russellbputnopvut: i'll come talk to you in a bit in person
22:58.04russellbor, let's get on the phone
22:58.05russellbthat is better
22:58.11snuff-homemm maybe that's what happens with 12555 ?
22:58.12russellblet me go look at bbryant's code real quick first
22:58.20putnopvutrussellb: can it wait until after I've thrown the ball some? :)
22:58.27putnopvutah, perfect then.
22:58.35putnopvutI'll talk to you in about 10 mins or so.
22:59.01Corydon76-digsnuff-home: it wouldn't be the first time... anywhere we have corrupted memory, it's a fair chance it's due to a scheduled job not being cancelled properly before memory was freed
22:59.33Corydon76-digIt's not the only cause of corrupted memory, but it certainly has been popular
23:01.09snuff-homeok could that bug be assigned or related to another so not to get lost..
23:01.33russellbhm ... i think i want to throw the ball now.
23:02.08snuff-homei also added a small patch on that bug to check before ast_string_copy..  since it appears it can be null as the initial person reported
23:06.59Corydon76-digM12555
23:07.01MuffinMan[feedback] [Asterisk] Channels/chan_sip/General 0012555: Crash is sip_destroy reported by callguy (Karma: +2.75) http://bugs.digium.com/view.php?id=12555
23:08.23*** join/#asterisk-dev RoyK (n=roy@ip-115-24-149-91.dialup.ice.no)
23:09.07*** part/#asterisk-dev RoyK (n=roy@ip-115-24-149-91.dialup.ice.no)
23:09.45codefreezeCorydon76-dig: what happened to ast_odbc_direct_execute?
23:14.14Corydon76-digWhat do you mean?
23:14.25codefreezenot finding it in trunk
23:14.48Corydon76-digIt's in 1.6.0
23:15.06Corydon76-digand it's in trunk
23:15.26Corydon76-digAre you looking in include/asterisk/res_odbc.h ?
23:15.30codefreezein res_odbc.h?
23:15.38Corydon76-digIt's the second to last function there
23:16.06Corydon76-digLine 111
23:16.55codefreezevery interesting. It is in trunk, but my branch based on trunk doesn't have it.
23:18.44Corydon76-digThat could be a problem, especially when you try merging it
23:19.25codefreezehmmm. I'm infestigating it right now.
23:22.58Corydon76-digcodefreeze: btw, have you taken care of the out of disk space condition on parsetree.com yet?
23:23.08fileCorydon76-dig: probably should have used attribute_deprecated
23:23.20Corydon76-digfile: what do you mean?
23:23.50Corydon76-digThat's the attribute as listed in the gcc manual
23:23.56filethere's autoconf stuff to determine whether compiler attributes exist, and #defines allow them to work even if they don't exist
23:24.23fileso if deprecated is valid then __attribute__((deprecated)) will be put in, otherwise nothing
23:24.25Corydon76-digShow me?
23:24.36file'tis include/asterisk/compiler.h
23:25.22Corydon76-digfile: err, what happens when you want to have two different attributes?
23:26.25Corydon76-digThe compiler wants both to be inside the (( )), separated by a comma
23:26.49filethen we could not currently
23:27.10filewonders if we even use the stuff in compiler.h
23:27.45filewe do, good...
23:28.15filejust in utils.h...
23:28.23Corydon76-digAh
23:29.47Corydon76-digThere's a ton of places that we don't, though
23:29.53filecorrect
23:33.30putnopvutCorydon76-dig: http://pastebin.ca/1004460
23:33.35putnopvutIs that a better version of the comment?
23:34.58Corydon76-digIt was never passed by value
23:35.20Corydon76-digWhat's important is that you reference the location in the struct where the value is actually stored, not a copy
23:35.30putnopvut...which is what the comment says to do.
23:35.56Corydon76-digYeah, but by reference vs by value is the wrong explanation
23:36.03putnopvutby name vs. by value.
23:36.30Corydon76-digI see what you're trying to say, but I think it's confusing that way
23:37.29putnopvutWhy is it confusing that way? It clears up the confusion I had earlier, which was that I was thinking in a purely by-value way.
23:37.53putnopvutThis way it makes it clear to whoever sees the comment that the value is passed by name to the macro, which is what makes it work.
23:38.34Corydon76-dig"by storage location" makes more sense to me than "by name"
23:39.19Corydon76-digbecause you're trying to check the storage location each time, and the value in the storage location may have changed
23:40.16putnopvutI used "by name" because that's the formal name for that type of parameter passing.
23:40.52Corydon76-digHmm, I never learned macros formally.  ;-)
23:41.05Corydon76-digWell, not macros that took parameters, anyway
23:41.25Corydon76-digBack when I was learning, we used macros as constants
23:42.03russellbback when I was learning, we didn't have macros
23:42.32denonso is asterisknow's setup wizard in the web gui post-install?
23:42.58denonI mean, there's no ncurses stuff besides just installing and partitioning and stuff, right?
23:43.19putnopvutdenon: no idea, man. I know next to nothing when it comes to using Asterisknow.
23:43.27denonyeah, me either :)
23:43.47denonbut Ive gotta walk an enduser through setting up an asterisk box .. who's never touched linux/etc
23:43.57denonat least walk them far enough that I can get into it remotely
23:44.04denonasterisknow is probably the best way to do that
23:44.12putnopvutCorydon76-dig: I guess I'll just go ahead and remove the comment altogether since, from what I understand, we don't ever pass a copy of the schedule ID to that macro anyway.
23:45.41Corydon76-digputnopvut: that's true, but some documentation is good...
23:46.00putnopvutOh, and...
23:46.06putnopvuthttp://www.cs.sfu.ca/~cameron/Teaching/383/PassByName.html
23:46.09Corydon76-digputnopvut: I'm not trying to frustrate you; I'm trying to make it clear...
23:46.17putnopvutAn interesting article about Algol and pass-by-name parameters.
23:46.22denonman, i'm really scared of having to use a gui though :)
23:54.34*** join/#asterisk-dev ZaVoid (n=zavoid@c-67-165-25-195.hsd1.pa.comcast.net)

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