| 01:43.18 | *** join/#asterisk-bugs pabelanger (~pabelange@50.22.5.41-static.reverse.softlayer.com) |
| 01:43.18 | *** mode/#asterisk-bugs [+o pabelanger] by niven.freenode.net |
| 01:51.05 | *** join/#asterisk-bugs pabelanger (~pabelange@50.22.5.41-static.reverse.softlayer.com) |
| 01:51.05 | *** mode/#asterisk-bugs [+o pabelanger] by niven.freenode.net |
| 03:32.19 | *** join/#asterisk-bugs elguero (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 06:55.20 | *** join/#asterisk-bugs infobot (~infobot@rikers.org) |
| 06:55.20 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Join #asterisk-testing for help with testing issues marked Ready for Testing -=- http://xkcd.org/583/ -=- An issue tracker full of activity is a sign of a healthy project |
| 08:17.47 | *** join/#asterisk-bugs tzafrir (~tzafrir@local.xorcom.com) |
| 10:11.18 | *** join/#asterisk-bugs infobot (~infobot@rikers.org) |
| 10:11.18 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Join #asterisk-testing for help with testing issues marked Ready for Testing -=- http://xkcd.org/583/ -=- An issue tracker full of activity is a sign of a healthy project |
| 12:07.05 | *** join/#asterisk-bugs infobot (~infobot@rikers.org) |
| 12:07.05 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Join #asterisk-testing for help with testing issues marked Ready for Testing -=- http://xkcd.org/583/ -=- An issue tracker full of activity is a sign of a healthy project |
| 14:21.35 | *** join/#asterisk-bugs elguero (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 14:46.28 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:46.28 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 14:58.54 | *** join/#asterisk-bugs elguero (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 15:16.29 | *** join/#asterisk-bugs miguel3239 (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 15:19.02 | *** join/#asterisk-bugs The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 15:32.01 | *** join/#asterisk-bugs miguel3239 (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 16:49.52 | *** join/#asterisk-bugs tzafrir (~tzafrir@local.xorcom.com) |
| 17:00.37 | *** join/#asterisk-bugs zerohalo (~zerohalo@173-13-92-27-NewEngland.hfc.comcastbusiness.net) |
| 17:04.53 | *** join/#asterisk-bugs zerohalo (~zerohalo@173-13-92-27-NewEngland.hfc.comcastbusiness.net) |
| 17:48.26 | *** join/#asterisk-bugs miguel3239 (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 17:51.07 | *** join/#asterisk-bugs elguero (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 18:16.16 | *** join/#asterisk-bugs miguel3239 (~miguel323@17.140.211.66.inaddr.G4.NET) |
| 18:22.53 | *** join/#asterisk-bugs MuffinMan (~muffinman@asterisk/issue-tracker-bot/muffinman) |
| 18:33.29 | *** join/#asterisk-bugs Juggie (~Juggie@unaffiliated/juggie) |
| 18:33.29 | *** mode/#asterisk-bugs [+o Juggie] by ChanServ |
| 19:02.35 | *** join/#asterisk-bugs zerohalo (~zerohalo@173-13-92-27-NewEngland.hfc.comcastbusiness.net) |
| 19:54.57 | *** join/#asterisk-bugs otherwiseguy (~terry@69.76.221.65) |
| 19:55.35 | leifmadsen | M18919 |
| 19:55.37 | MuffinMan | [new] [Asterisk] Channels/chan_sip/SRTP 0018919: Announced transfert with Aastra not works reported by Bernard Merindol https://issues.asterisk.org/view.php?id=18919 |
| 19:55.44 | leifmadsen | could that be a bug, or a configuration issue |
| 19:55.45 | leifmadsen | ? |
| 19:55.52 | leifmadsen | or maybe not enough info? I have no idea how I should triage that. |
| 19:57.51 | otherwiseguy | Could be a bug. They could post a pcap file as long as they aren't also using TLS. In any case, probably something that we would just try to reproduce and go from there. |
| 19:58.09 | leifmadsen | ok, I will ask for more information but I will import anyways |
| 20:20.25 | leifmadsen | Corydon76-home: ping? |
| 20:20.31 | leifmadsen | M18910 |
| 20:20.33 | MuffinMan | [new] [Asterisk] PBX/pbx_ael 0018910: After update from asterisk-1.6.2.14 to asterisk-1.6.2.17 Gosub(macro,s,1(args)) stopped working reported by alexandrekeller https://issues.asterisk.org/view.php?id=18910 |
| 20:22.50 | Corydon76-home | leifmadsen: I'm sure it did, because he should be doing ¯o(args) |
| 20:30.26 | leifmadsen | Corydon76-home: so basically using AEL wrong? |
| 20:30.40 | Corydon76-home | Yep |
| 20:31.03 | leifmadsen | ok noting |
| 20:31.20 | Corydon76-home | He's depending upon an implementation detail of subroutines |
| 20:31.35 | leifmadsen | ok great, thanks! |
| 20:31.47 | Corydon76-home | when the implementation detail changed, that broke |
| 20:32.26 | Corydon76-home | There's nothing that says the extension is named "s" or even that it starts at priority 1 |
| 20:33.03 | leifmadsen | gotcha |
| 20:33.05 | leifmadsen | I closed the issue :) |
| 20:33.08 | Corydon76-home | For all he knows, the starting priority could be 98723 |
| 20:33.50 | Corydon76-home | And I wonder if we should change it to something like that, just to impress people upon the point. Assuming that you know where the macro starts executing is a pretty stupid assumption |
| 20:36.15 | leifmadsen | just additional documentation to point to would proably help a bit |
| 20:39.13 | Marquis42 | leifmadsen: We're stepping on eath other's toes. I was just commenting on that bug too. |
| 20:39.19 | Marquis42 | s/bug/issue/ |
| 20:39.54 | leifmadsen | Marquis42: burn! :) |
| 20:40.00 | leifmadsen | sorry about that |
| 20:40.08 | leifmadsen | I will let you close it when you're done -- I have nothing further to add |
| 20:40.35 | Marquis42 | No worries, just trying to help out. You put in the same information. If he adds more, I'll smack him down. ;) |
| 20:40.53 | leifmadsen | perfect! |
| 20:41.01 | leifmadsen | I didn't like his response :) |
| 20:41.53 | Marquis42 | Me either, because he didn't read what was written. He just knee-jerked. |
| 20:42.46 | leifmadsen | indeed |
| 20:53.04 | leifmadsen | Marquis42: get him! |
| 20:53.05 | leifmadsen | :) |
| 20:53.22 | leifmadsen | basically my response would be, 'you were never using things correctly to begin with' |
| 20:54.31 | Marquis42 | Yeah, that's exactly correct. I'll try to be as diplomatic as possible about it, but really. He doesn't seem to have understood how AEL works in the first place and now he's whining as a result. |
| 20:55.07 | leifmadsen | agreed, and he blamed Digium when it was resolved by a community developer. |
| 20:55.23 | leifmadsen | I'm deleting what I just typed because I'm sure you'll be more diplomatic :) |
| 20:55.36 | Marquis42 | heh |
| 20:56.26 | leifmadsen | (not that there was anyone to 'blame' as it seems he was relying on functionality outside of AEL) |
| 20:56.34 | Marquis42 | Right |
| 20:57.03 | leifmadsen | anyways, much obliged |
| 20:57.14 | Marquis42 | Not a problem. |
| 21:01.00 | Marquis42 | leifmadsen: haha, I just noticed the fix that went in that this guy is complaining about was for an issue reported by my boss. :O |
| 21:01.16 | Marquis42 | So as it turns out I'm uniquely qualified for handling this new issue. :D |
| 21:03.56 | leifmadsen | w00t |
| 21:07.45 | *** join/#asterisk-bugs alecdavis (~alec@202.36.76.21) |
| 21:15.20 | leifmadsen | Marquis42: you could mention too that he is always welcome to revert the patch locally |
| 21:15.32 | leifmadsen | Marquis42: do you have bug marshal skills to close the issue? |
| 21:16.40 | Marquis42 | I think so, not entirely sure. :) |
| 21:17.48 | Marquis42 | Maybe not, I don't see that option. |
| 21:58.31 | leifmadsen | can you change the status of an issue? |
| 21:58.33 | leifmadsen | Marquis42: |
| 22:10.41 | Marquis42 | I don't think I can, unless I'm just too dumb to see how. :) |
| 22:11.00 | Marquis42 | BTW, nice referral to asterisk-users. At this point, that's definitely the right place to go. |
| 22:12.03 | leifmadsen | I closed, he reopened to bitch, I closed with no comment |
| 22:13.06 | Marquis42 | Ugh, can't that guy get a clue? It's not an "issue". |
| 22:24.23 | Corydon76-home | Ooooh, I just thought of something we COULD do... make the starting macro priority change on every reload |
| 22:28.24 | Marquis42 | lol |
| 22:28.56 | Corydon76-home | Then it becomes pretty much impossible to target it correctly from outside AEL |
| 22:29.24 | Marquis42 | I like it, if for no other reason than it would simply make this guy's head explode. ;) |
| 22:31.16 | Corydon76-home | However, for the sake of sanity, maybe we should create an application CallAELsub() which allows one to call subroutines defined in AEL from outside, then we do whatever is necessary to ensure that the redirect remains sane, even if/when we change the implementation |
| 22:32.19 | Marquis42 | I think that would at least allow for the use case this guy seems to want. It seems to me that at least one other person brought up a similar scenario. |