| 00:02.40 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-igucirkubtoyngwx) |
| 00:19.11 | *** join/#asterisk-dev zerohalo (~zerohalo@74.60.136.128) |
| 00:40.22 | *** join/#asterisk-dev tzafrir (~tzafrir@212.179.75.202) |
| 00:40.23 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 00:43.53 | *** join/#asterisk-dev otherwiseguy (~otherwise@rrcs-173-197-0-67.west.biz.rr.com) |
| 01:54.55 | *** join/#asterisk-dev tamiel (~tamiel@ip-183.net-81-220-86.toulouse.rev.numericable.fr) |
| 02:14.58 | *** join/#asterisk-dev CoderForLife (~Miranda@unaffiliated/coderforlife) |
| 02:39.10 | *** join/#asterisk-dev elred_ (~elred_@unaffiliated/elred-/x-5010831) |
| 03:09.42 | *** join/#asterisk-dev otherwiseguy (~otherwise@rrcs-173-197-0-67.west.biz.rr.com) |
| 03:57.34 | *** join/#asterisk-dev irroot (~gregory@197.106.4.99) |
| 04:04.16 | *** join/#asterisk-dev otherwiseguy (~otherwise@rrcs-173-197-0-67.west.biz.rr.com) |
| 04:45.37 | *** join/#asterisk-dev otherwiseguy (~otherwise@69.76.221.79) |
| 06:00.58 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 06:00.58 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 06:08.16 | *** join/#asterisk-dev mnicholson (~mnicholso@nat/digium/x-urfxpcoyazsjmxab) |
| 06:08.16 | *** mode/#asterisk-dev [+o mnicholson] by ChanServ |
| 07:10.09 | *** join/#asterisk-dev otherwiseguy (~otherwise@cpe-69-76-221-79.kc.res.rr.com) |
| 07:12.27 | *** join/#asterisk-dev otherwiseguy (~otherwise@69.76.221.79) |
| 07:51.30 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 07:51.31 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 08:37.44 | *** join/#asterisk-dev oej (~olle@static-213-115-251-100.sme.bredbandsbolaget.se) |
| 08:37.44 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 08:48.30 | *** join/#asterisk-dev Gugge (gugge@kriminel.dk) |
| 08:53.16 | *** join/#asterisk-dev irroot (~gregory@197.172.126.33) |
| 08:53.50 | *** part/#asterisk-dev irroot (~gregory@197.172.126.33) |
| 09:09.02 | *** join/#asterisk-dev fazool (~ada_has@182.185.185.85) |
| 09:09.09 | fazool | i have an issue |
| 09:09.43 | fazool | i want to call to agent insted of placing call in queue |
| 09:09.59 | fazool | mean want to dail directly to agent |
| 09:10.05 | tzafrir | fazool, so go ahead. But why do you want to do that? |
| 09:10.21 | fazool | i am facing transfer issue |
| 09:10.21 | tzafrir | If the agent is SIP/1234 , just Dial(SIP/1234) |
| 09:10.34 | tzafrir | oops. Wrong channel. Ask in #asterisk |
| 09:10.37 | fazool | its Agent/1003 |
| 09:11.14 | tzafrir | fazool, please ask in #asterisk |
| 09:15.29 | fazool | i am transfering call between agents |
| 09:15.57 | fazool | i want to report log in some application |
| 09:16.23 | fazool | any idea? |
| 09:21.38 | *** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:5d7b:425a:59c5:fef4) |
| 09:26.34 | fazool | help me to fetch infromation of call tranferd by agent in a queue |
| 10:13.26 | *** join/#asterisk-dev otherwiseguy (~otherwise@69.76.221.79) |
| 10:17.45 | *** join/#asterisk-dev irroot (~gregory@197.172.126.33) |
| 11:16.41 | *** join/#asterisk-dev irroot (~gregory@197.111.5.192) |
| 11:46.23 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 11:46.23 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 13:18.46 | *** join/#asterisk-dev Juggie (~Juggie@unaffiliated/juggie) |
| 13:34.05 | anonymouz666 | huh, a deadlock on chan_iax2 running asterisk 1.8 ... :/ |
| 13:34.48 | anonymouz666 | "auto-congestion on slow response"... and no more iax2 calls being delivered |
| 13:34.56 | anonymouz666 | core restart now and everything working again |
| 13:35.48 | pabelanger | anonymouz666: what timing module are you using? |
| 13:36.58 | anonymouz666 | Using the 'DAHDI' timing module for this test. |
| 13:38.57 | anonymouz666 | I have a backtrace threads when that happened |
| 14:05.12 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-wogcdflutoealbzn) |
| 14:12.12 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-yzwvdlpknjivpjdb) |
| 14:12.12 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 14:17.45 | *** join/#asterisk-dev irroot (~gregory@197.168.117.108) |
| 14:36.55 | WIMPy | What do you guys think about adding a BOB feature to Dial()? |
| 14:38.22 | jsmith | BOB? |
| 14:38.55 | WIMPy | busy on busy |
| 14:39.01 | leifmadsen | o.O |
| 14:39.13 | leifmadsen | I think it sounds silly |
| 14:39.39 | jsmith | Busy on busy? |
| 14:39.44 | jsmith | I'm not sure I understand |
| 14:39.51 | leifmadsen | same |
| 14:40.29 | WIMPy | The function would be to abprt Dial() if any of the dialled channels signals busy or reject. |
| 14:40.45 | leifmadsen | that's not how it works now? |
| 14:41.04 | jsmith | If *any* of them do? |
| 14:41.16 | jsmith | doesn't see how that would be useful |
| 14:41.19 | WIMPy | yes, *any*. |
| 14:41.39 | jsmith | Well, you're going to get a lot of short rings that way |
| 14:41.49 | jsmith | Let's say you dial SIP/bob&SIP/alice |
| 14:42.08 | jsmith | Bob's phone starts ringing, and then Alice's phone responds with '486 Busy Here' |
| 14:42.12 | file | Bob and Alice always get so many calls... if they get any more they might explode! |
| 14:42.25 | jsmith | So then Bob's phone would stop ringing |
| 14:42.29 | WIMPy | Thats useful if you have multiple phones, e.g. in a an SOHO or in the bosses big office. |
| 14:42.54 | jsmith | OK, I guess I see some *very limited* use for it |
| 14:43.02 | WIMPy | Say you dial bosses desk and bosses conference table. |
| 14:43.08 | jsmith | If you really want that functionality, why not just do it in dialplan logic with device states? |
| 14:43.18 | jsmith | It's not hard |
| 14:43.24 | WIMPy | Now if you reject a call on one phone, you don;t want the other one to continue ringing. |
| 14:44.38 | WIMPy | Because device states are pretty useless for two reasons: |
| 14:45.07 | WIMPy | 1. you wouldn't be able to signal call waitung in order to manually reejct the call and |
| 14:45.24 | WIMPy | 2. there might be multiple numbers/accounts involved. |
| 14:51.33 | *** join/#asterisk-dev pnlarsson (~niklas@fw1.gml.g.icnet.infracom.se) |
| 14:56.04 | *** join/#asterisk-dev irroot (~gregory@197.110.160.96) |
| 15:14.49 | *** join/#asterisk-dev sustav (~alfa@nat/digium/x-wpiuxealzpnxchtf) |
| 15:16.49 | *** join/#asterisk-dev zerohalo (~zerohalo@74-94-141-204-ma.hfc.comcastbusiness.net) |
| 15:26.40 | *** join/#asterisk-dev otherwiseguy (~otherwise@69.76.221.79) |
| 15:32.17 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 15:32.17 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 15:40.28 | *** join/#asterisk-dev irroot (~gregory@197.170.28.118) |
| 15:40.29 | Qwell | Corydon76-home: Since everywhere that didn't use \n was removed, might it now make sense to check for \n in ast_verbose, and yell if it sees that? |
| 15:40.53 | Qwell | where "that" == "ast_verbose without \n" |
| 15:41.12 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 15:41.12 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 15:47.02 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 16:14.24 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 16:14.24 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 16:21.34 | Corydon76-home | Qwell: That's an extra scan through the end of each string for every ast_verbose(). That might be something for AST_DEVMODE only. |
| 16:24.37 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 16:24.37 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 16:25.24 | *** join/#asterisk-dev irroot (~gregory@197.170.148.167) |
| 16:25.31 | Qwell | Corydon76-home: true enough |
| 16:41.31 | wdoekes2 | Corydon76-home: http://lists.digium.com/pipermail/asterisk-commits/2011-November/052661.html <-- why a do{if(!out)break;...}while(0) and not an if(out){...} ? |
| 16:52.43 | Corydon76-home | wdoekes2: Oh, I dunno. Style, I guess |
| 16:53.13 | Corydon76-home | wdoekes2: comes out to exactly the same code |
| 16:54.56 | Corydon76-home | wdoekes2: I originally wrote that style when I had the potential for more than one place to break |
| 17:02.40 | *** join/#asterisk-dev irroot (~gregory@41.55.70.198) |
| 17:30.16 | *** join/#asterisk-dev joshaidan (~brianj@S0106001c1023e838.tb.shawcable.net) |
| 17:41.27 | *** part/#asterisk-dev joshaidan (~brianj@S0106001c1023e838.tb.shawcable.net) |
| 17:41.58 | *** join/#asterisk-dev joshaidan (~brianj@S0106001c1023e838.tb.shawcable.net) |
| 17:47.49 | *** join/#asterisk-dev joshaidan (~brianj@S0106001c1023e838.tb.shawcable.net) |
| 17:53.48 | *** join/#asterisk-dev Netgeeks-laptop (~chris@gw1.netgeeks.net) |
| 18:11.00 | tzanger | I guess I should write this patch at some point :-) |
| 18:20.15 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 18:20.15 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 18:31.24 | *** join/#asterisk-dev oej (~olle@87.96.134.129) |
| 18:31.24 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 18:35.11 | *** join/#asterisk-dev vrban (~party@g231036094.adsl.alicedsl.de) |
| 18:40.18 | vrban | hello, i reported a remote crash vulnerability +patch in chan_sip a month ago: ASTERISK-18805, nobody like to fix? |
| 18:42.03 | oej | THat sounds awful. Will check. |
| 18:42.35 | *** join/#asterisk-dev opticron (~opticron@pianoben.ch) |
| 18:42.35 | *** mode/#asterisk-dev [+o opticron] by ChanServ |
| 18:44.09 | oej | Oh. When I search Jira informs me "you have tried to perform an operation which you are not permitted to perform" |
| 18:44.40 | anonymouz666 | same here |
| 18:45.04 | oej | Ok, can't do anything. Do you have any more information urban? |
| 18:45.40 | jsmith | vrban: Do you have more details? |
| 18:46.47 | oej | That issue seems blcoked from view even for developers |
| 18:47.03 | vrban | more? use the sipp scenario to reproduce the crash. |
| 18:47.05 | oej | I am now aware of two security reports more than a month old which haven't been handled and not reported. |
| 18:47.19 | oej | urban: We can not access your report. It's closed in a bad way. |
| 18:47.48 | oej | If Digium put on therself to handle security issues without discussing with the rest of the world, Digium needs to handle this more quickly |
| 18:48.01 | oej | End of irritated messages from me. |
| 18:48.33 | oej | ANy IPv6 issues. What's going on with IPv6 in your world, Jsmith? |
| 18:48.48 | jsmith | oej: I have a hard enough time with IPv4 connectivity, as you may recall |
| 18:49.22 | jsmith | vrban: Not all of us have access to the ticket :-/ |
| 18:50.14 | oej | jsmith: And the Fedora project: Are you responding to my rant? :-) |
| 18:50.21 | vrban | ok, I do not know. Now I see it, that it is closed to the public |
| 18:50.35 | pabelanger | FWIW: ASTERISK-18805 is on somebodies sprint for this month |
| 18:50.53 | jsmith | oej: We're doing what we can to make sure IPv6 works well from the Fedora distro |
| 18:50.53 | vrban | perhaps even better... |
| 18:51.21 | jsmith | oej: And our infrastructure team is eagerly awaiting some data center upgrades to be able to have many of our services available over IPv6 |
| 18:51.29 | oej | pabelanger: Why can't developers see it? Are non-digium staff excluded nowadays? |
| 18:51.48 | mjordan | oej: I'm not sure why, but the issue reporter set the security permissions to be only themselves and Digium |
| 18:52.03 | oej | jsmith: Great! We just need some UI improvements for the IPv6 stuff too. |
| 18:52.03 | file | actually leifmadsen changed it |
| 18:52.24 | mjordan | file: whoops, missed that, thanks |
| 18:52.49 | oej | Digium puts more and more burden on yourself only. Just make sure you can handle the load. |
| 18:53.33 | oej | The community puts a lot of trust in you guys fixing stuff - and you only. |
| 18:53.48 | pabelanger | lots of moving parts for a security release I would guess |
| 18:53.52 | oej | jsmith: DId you read my text on ipv6friday.org recently? |
| 18:54.03 | jsmith | oej: Nope... can't say that I have :-( |
| 18:54.41 | oej | jsmith: Read the linux section of this, it's short: http://ipv6friday.org/blog/2011/11/desktop-support/ |
| 18:55.32 | pabelanger | oej: BTW, what is the 1st security report |
| 18:59.39 | oej | pabelanger: I don't know, I can't access it - ASTERISK-18805 you mentioned before. |
| 19:00.25 | oej | The other one I haven't got an issue for, I just got a CC from my customer on the mail to security@asterisk.org a long time ago. Neither I or the customer have heard anything since. |
| 19:03.04 | oej | Not handling security issues in a prompt way opens up for a lot of bad talk and backlashes on the project as a whole. It's bad for all of us. |
| 19:03.50 | oej | If Digium development can't handle it we need to expand the team and include community developers in the discussion to speed up the process. No one put the burden on you alone, you took it and do not deliver. |
| 19:04.11 | *** join/#asterisk-dev irroot (~gregory@197.175.131.141) |
| 19:04.26 | oej | Even when I provided a patch and code to prove an issue, it took too long for the report to be published. |
| 19:07.32 | pabelanger | how long is responsible? |
| 19:08.29 | oej | More than a month is bad. There are live systems out there that we all need to protect. |
| 19:08.43 | oej | If you ahve code and examples, I would say ten working days maximum. |
| 19:09.16 | oej | On the other side, projects related to us have no security policy at all (something which I'm working to resolve). |
| 19:09.36 | oej | We have the policy, but I do feel we need to fix execution. |
| 19:09.51 | oej | But I might be alone in this opinion. :-) |
| 19:10.34 | pabelanger | FWIW: In November there was both Astricon and US Thanksgiving. Not saying that is the reason for it. |
| 19:12.32 | oej | Many of us had no Astricon and no Thanksgiving. The community is large and world-wide, Paul. |
| 19:13.10 | oej | I used to be able to see those reports, but somehow lost that authorization. You're on your own. |
| 19:13.31 | jsmith | pabelanger: Even so if Thanksgiving and AstriCon were the reason, there should be some sort of feedback loop |
| 19:13.37 | jsmith | pabelanger: "We're still working on this" |
| 19:13.50 | jsmith | pabelanger: or "We have higher priority things, but we haven't forgotten you" |
| 19:14.31 | jsmith | knows several different people who have had bad experiences w/ not getting feedback from security@asterisk.org |
| 19:14.35 | oej | A customer that reports a security incident in private and see that nothing happens will publish it in the wild or not at all next time. THat will hurt us. |
| 19:15.12 | oej | Basically when you violate community trust like this, you will loose it. It wasn't good for Microsoft either. |
| 19:15.21 | pabelanger | jsmith: responsible, sometimes hard to do when you have an issue tracker with over 900 issues. But I agree, maybe a better way to priorities them |
| 19:16.04 | oej | There has to be someone in charge of handling security reports. Either de-classifying them as not-security related and pushing them into the 900 list or making sure that enough resources are allocated to fix it. |
| 19:16.16 | oej | It can't be part of the 900 list and "just another bug report". |
| 19:16.42 | oej | If it's handled that way, we have a problem, pabelanger. |
| 19:17.41 | pabelanger | I'm all for the community getting more involved in testing patches, just look to the issue tracker. We already have a lot on there. Regardless if it is a security issue, bug fix or new feature. |
| 19:18.07 | oej | Let's focus discussion on security. |
| 19:18.30 | oej | Those needs to be handled separately. |
| 19:18.55 | jsmith | pabelanger: Again, I was only talking about security issues expressly sent to security@asterisk.org. I agree with have other problems with the issue tracker, but that's another topic for another day |
| 19:19.26 | pabelanger | FWIW: I have no idea where emails to security@asterisk.org go |
| 19:19.32 | pabelanger | I've never seen one |
| 19:20.25 | oej | Maybe to /dev/null... |
| 19:20.54 | oej | I should be able to answer these kind of questions when I meet the community, and I can't |
| 19:21.09 | oej | That makes me very upset. I've been part of Asterisk for many, many years. |
| 19:22.20 | oej | Anyway - any thoughts on NAT and IPv6 from anyone here? Trying to write a new article for ipv6friday. |
| 19:23.27 | Corydon76-home | pabelanger: At one time, the emails went to Kevin |
| 19:23.53 | Corydon76-home | pabelanger: And I believe I was on that distribution list, as well. |
| 19:24.37 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 19:24.37 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 19:25.38 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 19:25.38 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 19:26.29 | jsmith | oej: Sure -- clueless managers will want to use NAT with IPv6, because they think that NAT is a magic way of adding security to their network |
| 19:27.14 | Corydon76-home | jsmith: well, it does add _some_ security. It's just not a silver bullet. |
| 19:27.42 | kpfleming | oej: pabelanger: jsmith: emails to security@asterisk.org come to me, Qwell and others. we address them as soon as we see them. |
| 19:28.07 | Corydon76-home | Especially not with Windows machines that are as often as not infected with some user-installed malware |
| 19:28.21 | jsmith | oej: You could always write something regarding IPv6, NAT, and asymetrical routes |
| 19:29.07 | oej | mmm |
| 19:33.38 | *** join/#asterisk-dev The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 19:33.38 | *** mode/#asterisk-dev [+o The_Boy_Wonder] by ChanServ |
| 19:46.13 | oej | corydon76: thanks for the feedback |
| 19:51.43 | *** join/#asterisk-dev jrose_atDigium (~jon@nat/digium/x-aycisdmafphqxqle) |
| 20:26.19 | tzanger | hm, is it considered a bug that autocreated peers emit TWO identical manager PeerStatus events? |
| 20:29.11 | *** join/#asterisk-dev moy (~moy@216.172.42.74) |
| 20:29.32 | tzanger | one comes from parse_register_contact() and one comes from parsing the return code of parse_register_contact() which seems unique to autocreated peers. |
| 20:29.43 | kpfleming | that does seem silly |
| 20:30.22 | tzanger | I'm almost loathe to "fix" it because I really want to be able to see in AMI which peers were autocreated |
| 20:30.46 | tzanger | and the way it is now makes it easy to do (by modifying the event sent when parsing the result of parse_register_contact() |
| 20:30.57 | tzanger | urg, meeting |
| 21:12.28 | tzanger | actually I can fix it and still add the event line |
| 21:12.43 | tzanger | basically there's a "Cause" field for de-registration |
| 21:12.52 | tzanger | I was going to add one for registration |
| 21:14.16 | tzanger | I can look at the rt flag and emit a Cause: Realtime or something ... although "cause" isn't right there. source maybe |
| 21:15.31 | tzanger | peer->is_realtime |
| 21:15.33 | kpfleming | tzafrir: Incepter |
| 21:15.42 | kpfleming | oops... not tzafrir, tzanger |
| 21:15.50 | tzanger | Incepter? that's a funky word |
| 21:15.57 | tzanger | did you find that on your word of the day calendar this morning? |
| 21:16.01 | kpfleming | no |
| 21:16.07 | tzanger | or do you just really want to hae that in the code. :-) |
| 21:16.15 | kpfleming | i thought i had made it up, but it turns out to be real |
| 21:16.28 | tzanger | Inceptor: Realtime |
| 21:16.29 | tzanger | that works |
| 21:16.32 | tzanger | and sounds badass |
| 21:16.34 | kpfleming | we should have more obcsure words in our code |
| 21:16.53 | kpfleming | s/bcs/bsc/ |
| 21:17.00 | kpfleming | infobot: botsnak |
| 21:17.06 | kpfleming | infobot: botsnack |
| 21:17.06 | infobot | :), kpfleming |
| 21:18.41 | tzanger | manager_event(EVENT_FLAG_SYSTEM, "PeerStatus", "ChannelType: SIP\r\nPeer: SIP/%s\r\nPeerStatus: Registered\r\nAddress: %s\r\n%s", peer->name, ast_sockaddr_stringify(&peer->addr), (peer->is_realtime) ? "Inceptor: Realtime\r\n" : ""); |
| 21:18.56 | tzanger | something like that? Are ternary strings frowned upon? |
| 21:20.51 | kpfleming | no, we use ternary operators in other places |
| 21:23.05 | tzanger | Ok, two-line patch for that, working on the autocreatepeer enhancements |
| 21:24.42 | tzanger | hm, autocreated peers aren't considered realtime |
| 21:27.40 | tzanger | selfdestruct or dynamic might be better flags |
| 21:35.09 | *** join/#asterisk-dev citywok (~citywok@67-134-194-33.dia.static.qwest.net) |
| 21:38.05 | *** part/#asterisk-dev vrban (~party@g231036094.adsl.alicedsl.de) |
| 22:04.18 | *** join/#asterisk-dev vrban (~party@g231036094.adsl.alicedsl.de) |
| 22:08.40 | wdoekes2 | otherwiseguy: test for r1533 is up for review |
| 22:09.07 | otherwiseguy | wdoekes2: awesome. I'll take a look at it in a second. Thanks! |
| 22:14.51 | tzanger | loves how using . instead of _ causes the compiler to explode in C |
| 22:22.11 | wdoekes2 | (p.s. I did use my patched sipp to test this.. should be ok though..) |
| 22:22.24 | *** join/#asterisk-dev vrban (~party@g231039067.adsl.alicedsl.de) |
| 22:32.23 | tzanger | awesome the patch works. ship it! |
| 22:40.03 | tzanger | wtf |
| 22:40.11 | tzanger | does anyone else get something REALLY weird when they go to bugs.digium.org? |
| 22:40.31 | pabelanger | tzanger: define weird |
| 22:40.40 | pabelanger | also, it is issues.asterisk.org |
| 22:40.44 | kpfleming | digium.org? what the heck is that |
| 22:40.45 | tzanger | yes I know |
| 22:41.00 | tzanger | but it's ... "welcome montreal user, enter your email address, survey, blah blah" |
| 22:41.14 | pabelanger | looks like a redirect site |
| 22:41.36 | kpfleming | yeah,i don't get the montreal thing |
| 22:41.48 | pabelanger | changes each time you visit |
| 22:43.03 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-yzwvdlpknjivpjdb) |
| 22:43.04 | tzanger | wonder how much malware it tries to jam in your interface |
| 22:49.56 | tzanger | hmm, my signed license agreement didn't get transitioned into jira. |
| 22:50.31 | kpfleming | that's sub-optimal |
| 22:50.53 | tzanger | indeed. I have working code, not like the kind of patches file tends to commit. |
| 22:51.07 | file | I commit NOTHING to Asterisk, so ha! |
| 22:51.46 | tzanger | in soviet russia, asterisk commits YOU |
| 22:53.55 | tzanger | kpfleming: is this a bit you can twiddle in Jira or is there something additional I should do on my side? |
| 22:54.16 | kpfleming | if it's not there, your only option is to sign the new license agreement in jira |
| 22:54.35 | tzanger | let me see if I can find where the jira it is. |
| 22:55.40 | leifmadsen | tzanger: top bar |
| 22:55.52 | tzanger | oh I see, it's all electronical now. |
| 22:56.03 | leifmadsen | "Sign a License Agreement" |
| 22:56.05 | tzanger | yeah |
| 22:56.09 | leifmadsen | no more fax! :) |
| 22:56.14 | tzanger | the first time I signed it I had to fax it to Kevin |
| 22:56.55 | tzanger | I think I have two NDAs and a license agreement with Digium now. One more and I get the golf shirt! |
| 22:57.10 | tzanger | (actually I already have a nice golf shirt from them) :-) |
| 23:10.50 | tzanger | yay! patches added |
| 23:35.49 | *** join/#asterisk-dev zerohalo (~zerohalo@74.60.136.128) |
| 23:44.19 | *** join/#asterisk-dev sustav (~alfa@nat/digium/x-mhsguusvfkleajpz) |
| 23:49.31 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 23:49.31 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 23:49.58 | *** join/#asterisk-dev tzafrir_laptop (~tzafrir@bzq-218-155-148.cablep.bezeqint.net) |
| 23:49.58 | *** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ |
| 23:50.09 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 23:50.10 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 23:55.49 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 23:55.49 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 23:56.30 | *** join/#asterisk-dev mnicholson (~mnicholso@nat/digium/x-dkofobznfiffoukq) |
| 23:56.30 | *** mode/#asterisk-dev [+o mnicholson] by ChanServ |