| 00:06.44 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.126.221) |
| 01:47.41 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-qcffdvndvnmozkak) |
| 01:47.41 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 01:58.00 | *** join/#asterisk-dev snuff-work (~snuffy@203.63.71.233) |
| 01:58.00 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 02:23.05 | *** join/#asterisk-dev file (~file@asterisk/developer-and-muffin-lover/file) |
| 02:23.05 | *** mode/#asterisk-dev [+o file] by ChanServ |
| 02:38.22 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.126.221) |
| 05:16.46 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.126.221) |
| 06:21.49 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.126.179) |
| 06:24.33 | *** join/#asterisk-dev hrolf (~hrolf@unaffiliated/hrolf) |
| 06:49.11 | *** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:c9a7:4b2:6435:26ae) |
| 07:00.16 | *** join/#asterisk-dev drmessano (~nonya@pdpc/supporter/active/drmessano) |
| 07:06.52 | *** join/#asterisk-dev vlad_starkov (~vlad_star@195.239.220.131) |
| 07:44.42 | hrolf | Why in SIP is it that the To: and From: headers have the IP Addresses same even though both extensions are on different servers? |
| 09:12.45 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 09:12.45 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 09:49.52 | *** join/#asterisk-dev vlad_starkov (~vlad_star@195.239.220.131) |
| 09:50.30 | *** join/#asterisk-dev vlad_starkov (~vlad_star@195.239.220.131) |
| 10:14.40 | *** join/#asterisk-dev Greenlight (~email@cpc1-dund9-0-0-cust142.16-4.cable.virginmedia.com) |
| 10:29.16 | *** join/#asterisk-dev vlad_starkov (~vlad_star@195.239.220.131) |
| 11:01.31 | *** join/#asterisk-dev vlad_sta_ (~vlad_star@212.44.137.202) |
| 11:02.42 | *** join/#asterisk-dev vlad_st__ (~vlad_star@195.239.220.131) |
| 11:11.24 | *** join/#asterisk-dev pc-m (~pcm@modemcable094.94-70-69.static.videotron.ca) |
| 11:53.44 | *** join/#asterisk-dev vlad_starkov (~vlad_star@195.239.220.131) |
| 11:56.20 | *** join/#asterisk-dev bulkorok (~chatzilla@85.183.61.47) |
| 12:00.47 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-qcffdvndvnmozkak) |
| 12:36.39 | *** join/#asterisk-dev jsmith (~jsmith@fedora/jsmith) |
| 12:36.39 | *** mode/#asterisk-dev [+o jsmith] by ChanServ |
| 12:53.49 | file | wobbles |
| 12:56.29 | jsmith | falls over and lands on his bad shoulder |
| 12:56.35 | jsmith | Morning file |
| 12:56.37 | jsmith | Greetings all |
| 12:59.09 | file | g'morning |
| 13:06.36 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-ezdfmvpsrbwcqskz) |
| 13:06.36 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 13:07.40 | file | all I ever wanted... all I ever needed... is here in my arms |
| 13:22.17 | *** join/#asterisk-dev VictorSierra (~a.b@151.237.234.154) |
| 13:22.43 | *** part/#asterisk-dev VictorSierra (~a.b@151.237.234.154) |
| 13:40.50 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 13:40.59 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 14:02.24 | putnopvut | "I must not allow myself to exceed the scope of my assignment" |
| 14:02.32 | putnopvut | This shall be my mantra while working with app_queue this week |
| 14:03.15 | file | putnopvut, Uncle Josh says: Don't become a victim of scope creep. |
| 14:05.55 | leifmadsen | putnopvut: +1 |
| 14:07.01 | *** join/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net) |
| 14:07.18 | mjordan | putnopvut: http://www.jasonmillsdesign.com/wp-content/uploads/2013/06/scope.jpg |
| 14:07.52 | putnopvut | mjordan: classic |
| 14:08.23 | putnopvut | I like how "programmer" is misspelled in the fourth frame |
| 14:08.26 | putnopvut | or panel |
| 14:08.30 | putnopvut | are they frames or panels? |
| 14:09.22 | mjordan | I would call them panels |
| 14:09.38 | putnopvut | All right. It's official. "Panels" it is. |
| 14:12.09 | file | I heard you're idea's and their definately good. |
| 14:12.54 | putnopvut | someone is an xkcd reader |
| 14:13.40 | file | perhaps |
| 14:18.30 | mjordan | did you smash your computer in rage? |
| 14:19.23 | putnopvut | mjordan: In app_queue.c in trunk, you added two BUGBUG comments to wait_for_answer (lines 4340 and 4345 in my working copy) that say "We shouldn't have to set anything here, as each individual dial attempt should have set that CDR to busy". AFAICT, we're not actually setting anything in those cases, so I don't understand why there are BUGBUG messages there or what they are referring to. |
| 14:50.29 | jsmith | putnopvut: Just out of morbid curiosity, what are you doing to app_queue this week? |
| 14:50.45 | jsmith | putnopvut: ast_obj2-ification? |
| 14:50.52 | jsmith | putnopvut: Something more drastic? |
| 14:51.08 | mjordan | putnopvut: looking |
| 14:51.16 | mjordan | jsmith: we might have broken it. Slightly. |
| 14:51.25 | putnopvut | jsmith: there are vast chunks of app_queue in trunk that are commented out because of changes made in bridging. I'm fixing those sections back up. |
| 14:51.32 | jsmith | putnopvut: Gotcha :-) |
| 14:51.43 | jsmith | Please break a few eggs and make an omelette :-) |
| 14:52.02 | mjordan | jsmith: omelettes were made with chan_agent. |
| 14:52.06 | putnopvut | Mostly it relates to how we handled transfers before, but there are some other miscellaneous items that are marked with "BUGBUG" comments that I need to get to the bottom of. |
| 14:52.20 | putnopvut | chan_agent? What's that? |
| 14:53.24 | file | putnopvut, a dark memory... that is best erased |
| 14:53.51 | mjordan | putnopvut: so, some of those are wrong, but partly it's related to the goofiness that is dialing in app_queue |
| 14:54.14 | mjordan | putnopvut: in general, we should be raising dial messages when we attempt to dial a member and can't because they are unavailable, busy, or what have you |
| 14:54.41 | mjordan | those bugbugs are there because we've determined that members are busy (and, IIRC, there used to be CDR code there that explicitly set the CDRs to busy) |
| 14:54.54 | mjordan | however, the fact that a member if busy is determined based on the dial messages now, not on explicit CDR code |
| 14:55.15 | mjordan | so, it's more of a note to make sure that we notify stasis whenever we realize a member can't be dialed. |
| 14:55.26 | mjordan | if you look at ring_entry, we don't quite dot hat |
| 14:55.28 | mjordan | do that |
| 14:56.09 | jsmith | mjordan: I remember seeing something to that effect before I went on vacation, but my memory is hazy -- mind pointing me to more details on the chan_agent_(something) omelette, and how I can start testing it? |
| 14:56.14 | mjordan | we don't publish a dial begin until line 3993, which is at the end of the routine. If we determine that the member is busy or unavailable prior to that, we don't raise any notification, which is probably wrong |
| 14:56.23 | mjordan | jsmith: sure - it should be going into trunk relatively soon-ish |
| 14:57.00 | mjordan | code review is here, which shows some dialplan using the new approach: https://reviewboard.asterisk.org/r/2657/ |
| 14:57.07 | mjordan | basically, chan_agent is dead, but the use case lives on |
| 14:57.23 | mjordan | be back in a bit |
| 15:04.34 | jsmith | mjordan: Gotcha -- looks interesting. |
| 15:23.26 | file | opticron, I'm going to go for the approach of a defined structure in res_sip_session.h which has a pointer to the channel specific implementation pvt, and the session itself |
| 15:44.17 | opticron | file, I'm still not sure I like the idea of a channel pvt having meaning outside the channel code, but of the options presented that sounds like the best |
| 15:47.30 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 15:47.30 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 15:49.18 | tzanger | file: does Joshua Colp know about bash? |
| 15:49.26 | tzanger | I know he knows HOW to bash, but I want to be accurate for linkedin. :-) |
| 15:49.48 | file | Ugh endorsements |
| 15:49.51 | file | Do not want |
| 15:49.54 | tzanger | yep they're a timesink |
| 15:49.58 | tzanger | don't worry I didn't endorse you |
| 15:50.13 | tzanger | although if you added a smart-ass tag I'd endorse the shit of of that |
| 15:50.13 | jsmith | endorses file for "quoting random rock lyrics on IRC" |
| 15:54.24 | file | How are we today? |
| 15:55.27 | tzanger | we're good. playing with image sensors |
| 15:56.13 | WIMPy | Image sensors? In case someone missed it: |
| 15:56.18 | WIMPy | http://i.imgur.com/XLQIsnH.gif |
| 15:58.11 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 15:58.11 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 15:59.52 | tzanger | heh eyah I caught that |
| 15:59.58 | tzanger | my work isn't for the NSA or anything related |
| 16:00.13 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-oswlasgzgigboddf) |
| 16:06.11 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.127.18) |
| 17:07.06 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.125.163) |
| 17:10.32 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 17:10.32 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 17:26.56 | *** join/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net) |
| 17:30.40 | *** join/#asterisk-dev hexanol (~bibi@modemcable094.94-70-69.static.videotron.ca) |
| 17:34.47 | putnopvut | General compiler question: anyone have a good idea why the same compiler error message would appear 20 times when compiling a file? The error is easy to fix, but I'm baffled as to why the compiler feels the need to spit out the exact same error message 20 times. |
| 17:35.11 | file | it's persistent |
| 17:35.15 | putnopvut | I suppose it could be due to several macros being expanded or something... |
| 17:35.29 | putnopvut | But 20 seems high |
| 17:36.23 | putnopvut | But this is a straight strcmp() of two variables, so shouldn't even be any macros being expanded. |
| 18:13.28 | file | give me the fax, nothin' but the fax |
| 18:26.17 | mjordan | FTT |
| 18:46.33 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.127.65) |
| 18:57.10 | *** join/#asterisk-dev philipp64 (~chatzilla@66-232-81-197.ctcweb.net) |
| 19:37.41 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.127.65) |
| 19:53.05 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.127.65) |
| 19:56.39 | *** join/#asterisk-dev tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 19:56.39 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 20:08.34 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 20:08.34 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 20:18.21 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 20:20.37 | *** join/#asterisk-dev tm1000 (tm1000@2600:3c01::f03c:91ff:fe70:fce6) |
| 20:25.43 | *** part/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net) |
| 20:40.08 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-tvtmhifabjptbhww) |
| 21:01.57 | *** join/#asterisk-dev [TK]D-Fender (~chatzilla@64.235.216.2) |
| 21:28.03 | Qwell | leedm777: Sorry about that - I assumed that it was documented, since it was in the sample config. |
| 21:28.37 | leedm777 | Qwell: nope. I only remember to document config stuff when I see the errors on startup :-D |
| 21:38.06 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 21:38.06 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 22:28.06 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 22:28.06 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 22:37.06 | *** join/#asterisk-dev snuff-work (~snuffy@203.63.71.233) |
| 22:37.06 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 22:54.45 | *** join/#asterisk-dev vlad_starkov (~vlad_star@109.188.125.179) |
| 23:09.15 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-ezdfmvpsrbwcqskz) |
| 23:27.49 | *** join/#asterisk-dev serafie (~erin@user-24-214-173-250.knology.net) |
| 23:59.40 | *** join/#asterisk-dev [TK]D-Fender (~chatzilla@64.235.216.2) |
