| 00:01.45 | X-Rob | file: can I ask your opinion on https://issues.asterisk.org/jira/browse/ASTERISK-24695 -- am I doing something blatantly wrong there, or is it a real bug? (That's the MixMonitor B option one breaking when chanspy gets confused about codecs) |
| 00:02.34 | file | sounds like a real bug |
| 00:06.26 | X-Rob | <3 file thanks |
| 00:06.36 | X-Rob | I'll stop trying to figure out what I've done wrong then. |
| 00:06.45 | file | without diving in I make no guarantees |
| 00:06.58 | X-Rob | heh |
| 00:07.12 | file | but fairly certain |
| 00:07.23 | file | do you guys have codec_resample? I'd imagine so |
| 00:08.34 | X-Rob | file: *checking* |
| 00:09.05 | X-Rob | file: lno |
| 00:09.27 | X-Rob | https://www.irccloud.com/pastebin/d7CxCoOV |
| 00:10.09 | file | hrm! I wonder if it's choosing a slin8/slin16 path, and since no codec_resample it doesn't work... |
| 00:11.04 | file | regardless, requires investigation! |
| 00:11.06 | X-Rob | file: it's the same with ulaw->ulaw |
| 00:11.15 | file | ack |
| 00:11.23 | X-Rob | anyway, all good. |
| 00:11.31 | X-Rob | I'll stop stressing about it |
| 00:11.51 | file | stress about other things |
| 00:11.57 | file | such as a comet coming down and striking you |
| 00:13.31 | X-Rob | That's not something I've ever stressed about |
| 00:13.45 | X-Rob | I stress more about it coming down and NOT striking me |
| 00:13.59 | X-Rob | so I die slowly and painfully, rather than instantly and painlessly |
| 00:14.27 | file | who said it would kill you? |
| 00:15.43 | X-Rob | Well, if a comet struck me, I would either die, or only barely notice, depending on the size. There's not much chance of it being in between those ranges |
| 00:16.00 | file | it might take off part of you |
| 00:16.24 | X-Rob | No, you're thinking of ninjas now. |
| 00:16.31 | file | ninja comets... |
| 00:16.33 | file | BRILLIANT |
| 00:16.37 | X-Rob | That's something I -should- stress about. |
| 00:17.06 | file | I'm reminded that I should check the storm status for tomorrow |
| 00:17.22 | file | unexciting |
| 00:17.25 | X-Rob | file: did you see my awesome lightning pic from the other day? |
| 00:17.32 | file | yes |
| 00:17.38 | file | I SEE ALL |
| 00:17.46 | file | except certain spectrums |
| 00:17.58 | X-Rob | Heh |
| 00:18.36 | X-Rob | I have about 50 or 60 almost black photos |
| 00:18.42 | X-Rob | and two with decent lighting strikes |
| 00:18.58 | X-Rob | and after all of that, there was bugger all rain. |
| 00:19.32 | X-Rob | (for those that missed the awesomeness -- https://www.dropbox.com/s/q2hdn6gtyeyq1d3/DSC_0243.JPG is the link) |
| 00:26.26 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-uzsturluntdwvbrd) |
| 00:40.00 | *** join/#asterisk-dev mjordan (~mjordan@75.76.55.191) |
| 00:40.00 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 00:40.57 | *** part/#asterisk-dev mjordan (~mjordan@75.76.55.191) |
| 00:59.58 | *** join/#asterisk-dev mjordan (mjordan@nat/digium/x-dfhgpdmwbrsdyofe) |
| 00:59.58 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 01:06.38 | *** join/#asterisk-dev superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 01:30.40 | *** join/#asterisk-dev sgriepentrog (~sgriepent@162-239-32-132.lightspeed.brhmal.sbcglobal.net) |
| 03:29.30 | *** part/#asterisk-dev mjordan (mjordan@nat/digium/x-dfhgpdmwbrsdyofe) |
| 03:32.06 | *** join/#asterisk-dev leedm777 (~leedm777@50-81-28-152.client.mchsi.com) |
| 03:36.03 | *** join/#asterisk-dev angler (angler@pdpc/sponsor/digium/angler) |
| 04:28.15 | *** part/#asterisk-dev angler (angler@pdpc/sponsor/digium/angler) |
| 07:04.27 | *** join/#asterisk-dev bulkorok (~Benjamin@85.183.61.47) |
| 07:23.58 | *** join/#asterisk-dev ayrjola (~ayrjola@80.248.109.192) |
| 07:29.00 | *** join/#asterisk-dev ayrjola (~ayrjola@80.248.109.192) |
| 07:39.51 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 07:39.51 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 08:04.04 | *** join/#asterisk-dev hehol (~hehol@217.9.101.222) |
| 08:11.41 | wdoekes | X-Rob: nice |
| 08:14.37 | X-Rob | wdoekes: it was an impressive light show |
| 08:16.24 | wdoekes | I can imagine |
| 08:49.18 | skrusty | wow - impressive! |
| 10:00.17 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 10:00.17 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 10:05.12 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 10:05.12 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 11:41.25 | *** part/#asterisk-dev bulkorok (~Benjamin@85.183.61.47) |
| 11:43.58 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 11:43.59 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 11:52.08 | *** join/#asterisk-dev bulkorok (~Benjamin@85.183.61.47) |
| 12:30.31 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 12:30.31 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 12:35.08 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 12:35.09 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 12:42.51 | seanbright | is the SOP still to wait for two ship-its before committing? |
| 12:46.32 | file | seanbright, you don't have to - but it's generally polite to wait 24 hours before commit just in case |
| 12:46.46 | seanbright | k |
| 12:50.56 | wdoekes | I just filed a bug report for a customer observed crash ( ASTERISK-24726 ). does anyone have a clue why/how ast_hangup() could be called while we're in the middle of file.c waitstream_core ? |
| 13:06.32 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 13:06.32 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:11.35 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 13:11.36 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:26.48 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 13:26.48 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:27.16 | file | wdoekes, it shouldn't occur - I won't say it's not possible because if you have a pointer to the channel you can naturally call ast_hangup and bad stuff will happen |
| 13:28.00 | *** join/#asterisk-dev [TK]D-Fender (~chatzilla@216-191-106-163.dedicated.allstream.net) |
| 13:30.39 | *** join/#asterisk-dev Marquis42 (~mrbmw@d14-69-246-193.try.wideopenwest.com) |
| 13:32.34 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 13:32.34 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:40.45 | wdoekes | yea.. afaik the customer runs no special stuff. only a bit of agi and ami. unfortunately no verbose/debug logging that helps |
| 13:46.25 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 13:46.26 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:12.36 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 14:12.36 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:17.46 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 14:17.46 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:18.30 | *** join/#asterisk-dev leedm777 (leedm777@nat/digium/x-slqcljguuebiupsw) |
| 14:23.14 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 14:23.14 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:42.12 | *** join/#asterisk-dev sruffell (sruffell@asterisk/the-kernel-guy/sruffell) |
| 14:42.13 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 14:44.51 | *** join/#asterisk-dev oej (~Adium@static-213-115-47-11.sme.bredbandsbolaget.se) |
| 14:44.51 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:58.12 | *** join/#asterisk-dev leedm777 (leedm777@nat/digium/x-hovfguyyywtgjnnm) |
| 15:01.36 | *** join/#asterisk-dev sgriepentrog (~sgriepent@2602:30a:2ef2:840:20c:29ff:fe4f:cac8) |
| 15:05.49 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-qfavxifwzycvuuew) |
| 15:11.59 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-lkatqgbkdvbjoepg) |
| 15:15.36 | file | ponders |
| 15:19.27 | *** join/#asterisk-dev jameswf (uid27319@gateway/web/irccloud.com/x-qctgwiipwzetvcbf) |
| 15:22.21 | *** join/#asterisk-dev mjordan (mjordan@nat/digium/x-qoooelnlsmdeuqac) |
| 15:22.21 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 15:39.56 | *** join/#asterisk-dev newtonr (newtonr@nat/digium/x-wurskokzzwhgrfvt) |
| 15:39.56 | *** mode/#asterisk-dev [+o newtonr] by ChanServ |
| 15:46.16 | file | https://reviewboard.asterisk.org/r/4378/ could use a review |
| 15:47.14 | file | rmudgett, particularly you as I moved something in bridging :P |
| 15:47.24 | file | to make something you said shouldn't happen.... not happen |
| 15:47.54 | mjordan | yeah... |
| 15:48.05 | mjordan | the message ordering will change, but I'm not sure if that's a bad thing. |
| 15:48.21 | mjordan | we will drop to a single channel in a bridge before the second gets pushed in |
| 15:48.29 | mjordan | but I'm not sure that's a bad thing |
| 15:48.58 | file | yeah - I thought the same |
| 15:49.19 | mjordan | I'll pull it down and run it through the CDR shenaniganry |
| 15:49.30 | mjordan | since that cares a lot about message ordering |
| 15:49.36 | mjordan | if it survives that, it probably won't negatively impact much |
| 15:49.46 | file | I *can* make the ordering as it is... but the consequence would be that the channel wouldn't really be in there for a brief moment |
| 15:50.20 | mjordan | nah |
| 15:50.27 | mjordan | I wouldn't do that unless we absolutely had to |
| 15:50.31 | rmudgett | file: I was already looking at it. |
| 15:50.31 | file | that's why I didn't do it |
| 15:50.33 | mjordan | the whole "let's lie to our consumers" feels bad |
| 15:52.02 | mjordan | welp. |
| 15:52.06 | mjordan | 8 CEL unit tests failed |
| 15:52.31 | file | so, lies are great |
| 15:52.32 | mjordan | er |
| 15:52.35 | mjordan | nah |
| 15:52.37 | mjordan | don't trust that just yet |
| 15:52.40 | mjordan | heh |
| 15:52.41 | file | :P |
| 15:52.43 | mjordan | I had autoload => no |
| 15:52.44 | mjordan | :-P |
| 15:52.57 | Qwell | worse config option ever |
| 15:53.19 | mjordan | Qwell: not when you're trying to have a predictable system |
| 15:53.32 | Qwell | bah, predictability |
| 15:53.53 | mjordan | "my middle name is 'danger'." |
| 15:54.24 | mjordan | file: yay, 0 when I bothered to load the bridging modules |
| 15:54.40 | file | one does not simply... not load bridging modules |
| 15:55.36 | *** join/#asterisk-dev ipengineer (~zconkle@static-71-252-134-63.dllstx.fios.verizon.net) |
| 15:56.33 | *** join/#asterisk-dev superscrat (asanders@nat/digium/x-ebstiovcdvhfdgld) |
| 16:00.02 | *** join/#asterisk-dev sgriepentrog (sgriepentr@nat/digium/x-wmcpompthccwiarx) |
| 16:20.21 | mjordan | file: looks like we're good. I had one CDR test boink out, but I suspect that's due to res_parking being mean |
| 16:20.45 | file | nods |
| 16:20.52 | file | I suspect I'm going to back/forth with rmudgett |
| 16:24.14 | file | others feel free to join in |
| 16:31.55 | mjordan | chimed in |
| 16:32.48 | file | mjordan, merci! |
| 16:58.36 | rmudgett | file: Rats. It just occurred to me that the channel being pulled is the swap channel and not the new channel that has the swap pointer set. So my suggestion won't work. |
| 16:58.47 | rmudgett | Your previous version will. |
| 16:59.09 | file | ah, yeah |
| 16:59.21 | rmudgett | I just didn't like temporarily clearing the flag because that implied knowledge of how the called function works. |
| 16:59.44 | file | rolled back |
| 17:09.28 | *** join/#asterisk-dev leedm777 (leedm777@nat/digium/x-ggjzbgjukfohrmng) |
| 17:11.18 | *** join/#asterisk-dev oej (~Adium@192.36.80.8) |
| 17:11.19 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 17:24.08 | file | ACHOO |
| 17:27.55 | mjordan | file: I'd say go ahead and ship in https://reviewboard.asterisk.org/r/4378/ |
| 17:28.03 | mjordan | file: if we have some testsuite blow ups, I'd rather catch them tonight |
| 17:29.18 | file | you got it |
| 17:33.20 | file | if stuff breaks I'd expect it to be ordering |
| 17:35.37 | file | mic. dropped. |
| 17:47.02 | *** join/#asterisk-dev putnopvut (putnopvut@asterisk/master-of-queues/mmichelson) |
| 17:47.02 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 18:15.34 | tzafrir | sruffell, ping |
| 18:15.41 | sruffell | pong |
| 18:44.39 | WIMPy | You probably have seen http://voice.yeti.dk/Asterisk_vs_ISDN/ where I collected some of that stuff. |
| 18:44.56 | WIMPy | Wrong Window |
| 18:54.44 | superscrat | Bless you, file. |
| 18:56.15 | superscrat | I have a question... I would appreciate it if anyone has a second to take a stab at this. |
| 18:56.33 | file | superscrat, ask and ye shell maybe receive |
| 18:56.38 | file | or shall |
| 18:57.44 | WIMPy | Security advisory: Send a meta question to file and gain shell access. |
| 19:09.17 | superscrat | This was presented in the code review for my testsuite fix (https://reviewboard.asterisk.org/r/4377/), but it applies to the asterisk patch as well (https://reviewboard.asterisk.org/r/4374/). During development, I went back and forth with the best way to implement this. On the one hand, the RFC for http headers has a clear definition of the correct number of values necessary to include header fields. On the other hand, the principle |
| 19:10.46 | superscrat | of least astonishment may be violated by the decision to omit a header field in the event that the user left out a value in the configuration on purpose. Specifically, this is in response to point #3. In the end, I went with least astonishment, but technically, honoring the RFC is correct. I would appreciate any thoughts anyone has on this. Thanks =) |
| 19:13.01 | file | I don't know why a user setting an empty server name would want/expect it to be present |
| 19:15.17 | file | personally I'd expect it to not be present |
| 19:22.45 | seanbright | does rusty hang out on irc? |
| 19:23.04 | file | newtonr, ^^^ |
| 19:23.17 | newtonr | newton rusty |
| 19:23.19 | superscrat | =) |
| 19:23.23 | newtonr | that is me! |
| 19:23.28 | seanbright | newtonr: ! |
| 19:23.43 | seanbright | r4379 <3 |
| 19:24.10 | newtonr | lawl |
| 19:24.21 | newtonr | many of us have wanted something like this for a long while |
| 19:24.48 | file | ah, SAC |
| 19:24.51 | *** join/#asterisk-dev ipengineer_ (~zconkle@static-71-252-134-63.dllstx.fios.verizon.net) |
| 19:25.07 | seanbright | well it's awesome |
| 19:25.11 | seanbright | and i heart it |
| 19:25.12 | seanbright | that's all |
| 19:26.12 | file | oh, boo |
| 19:27.12 | newtonr | seanbright, have you read the phase 1 spec on the wiki yet? malcolmd wrote it and it is hilarious. |
| 19:29.09 | file | I feel the need to link this: https://www.youtube.com/watch?v=zt2uIhAvQZ8 |
| 19:31.30 | seanbright | i have read it |
| 19:31.39 | seanbright | it's pretty funny |
| 19:32.34 | seanbright | might want to turn the humor down a notch though... it makes it a bit noisy |
| 19:32.45 | seanbright | is monday morning quarterbacking |
| 19:34.21 | superscrat | thank ye, file. |
| 19:34.50 | superscrat | On a side-note, completely unrelated, I think we should celebrate more "talk like a pirate" days. |
| 19:40.14 | *** join/#asterisk-dev sgriepentrog (sgriepentr@nat/digium/x-rrmjasfljxgzbgkv) |
| 19:45.44 | *** join/#asterisk-dev ipengineer (~zconkle@static-71-252-134-63.dllstx.fios.verizon.net) |
| 19:49.46 | mjordan | jrose_atDigium: you're going to need to go back through your commits and update them with the ASTERISK issue (ASTERISK-24721) |
| 19:50.01 | jrose_atDigium | Alright |
| 19:52.19 | jrose_atDigium | mjordan: fixed |
| 19:56.24 | superscrat | okay, thanks. |
| 19:58.24 | superscrat | I just needed to verify that this wouldn't breach the expected behavior of asterisk. |
| 20:00.25 | superscrat | seanbright, I believe so. Yes. |
| 20:02.52 | *** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net) |
| 20:02.52 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 20:07.35 | kharwell | bad file descriptor message review for interested parties: https://reviewboard.asterisk.org/r/4380/ |
| 20:16.55 | mjordan | reviewed |
| 20:23.11 | *** join/#asterisk-dev russellb_ (~russellb@redhat/russellb) |
| 20:23.11 | *** mode/#asterisk-dev [+o russellb_] by ChanServ |
| 20:23.30 | *** join/#asterisk-dev terryw (~otherwise@2605:a601:437:1:862b:2bff:fead:2cce) |
| 20:35.29 | mjordan | er: kharwell, reviewed |
| 20:36.19 | kharwell | mjordan: thanks! |
| 20:37.12 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 20:37.12 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 20:40.13 | *** part/#asterisk-dev mjordan (mjordan@nat/digium/x-qoooelnlsmdeuqac) |
| 20:55.10 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-murkviuvjjtncldk) |
| 20:58.56 | *** join/#asterisk-dev JunK-Y (~junky@pdpc/supporter/active/junk-y) |
| 21:51.58 | *** join/#asterisk-dev [TK]D-Fender (~joe@64.235.216.2) |
| 21:55.04 | gtjoseph | pjsip auth question... It appears that the incomint auth/username must be the same as the endpoint id, yes? |
| 21:55.12 | gtjoseph | s/incomint/incoming |
| 21:56.07 | gtjoseph | and therefore you can't share an auth across multiple endpoints |
| 21:56.26 | gtjoseph | for incomint |
| 21:56.35 | gtjoseph | s/incomint/incoming/ |
| 21:58.30 | file | it shouldn't have to be |
| 21:58.54 | gtjoseph | experimentation says it does. :) |
| 21:59.11 | gtjoseph | if it's different, auth rejected |
| 21:59.46 | sgriepentrog | That has been my experience as well. |
| 22:00.33 | file | I'll add this: it shouldn't have to be but due to the way some devices are configured it may have to be |
| 22:01.14 | gtjoseph | further experimentation reveals I may be an idiot... |
| 22:04.20 | sgriepentrog | I would love to hear what you figured out. |
| 22:05.04 | gtjoseph | it's weird. Now i'm getting 500s. still playing. |
| 22:06.29 | gtjoseph | ok, file's right (of course). If your device can specify separate uri user and auth user, you're ok. |
| 22:06.41 | gtjoseph | the uri user has to match the endpoint id |
| 22:06.52 | gtjoseph | and the auth user has to match the auth/username |
| 22:07.03 | file | yes |
| 22:07.50 | sgriepentrog | Hmm. That actually makes sense. So if you're not setting them different on the endpoint, then you have to have a matching auth entry for each in pjsip. |
| 22:08.53 | gtjoseph | you still need a matching auth entry if you're authing. |
| 22:09.31 | gtjoseph | I was testing with the CSipSimple basic wizard which doesn't separate the uri user from the auth user. |
| 22:09.49 | sgriepentrog | Oh, so you still can't share a single auth entry between multiple endpoints, because you have to set the uri to match the endpoint? |
| 22:10.00 | gtjoseph | nope, that works |
| 22:10.13 | gtjoseph | IF your device can separate the two |
| 22:10.32 | sgriepentrog | Okay, right. So a single auth is fine, but the auth name must match the []s. |
| 22:11.17 | gtjoseph | Nope, it on't has to match the user in the authenticate message |
| 22:11.21 | gtjoseph | only |
| 22:11.27 | sgriepentrog | Although that wouldn't work if you were using the md5auth method. |
| 22:11.34 | file | watches |
| 22:12.06 | gtjoseph | why wouldn't work for md5sum? |
| 22:12.41 | sgriepentrog | Oh. Nevermind. I was thinking that the user portion of the md5sum would be wrong, but it should be the auth value. |
| 22:12.50 | sgriepentrog | That would work just fine. |
| 22:13.08 | sgriepentrog | now wants to rewrite his pjsip.conf |
| 22:18.21 | *** join/#asterisk-dev gtjoseph (~gtj0@unaffiliated/gtj) |
| 22:22.11 | *** join/#asterisk-dev malcolmd (malcolmd@pdpc/sponsor/digium/malcolmd) |
| 22:22.11 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 22:38.55 | *** join/#asterisk-dev superscrat (asanders@nat/digium/x-njqoyjilftufoqtc) |
| 22:39.29 | *** join/#asterisk-dev malcolmd (malcolmd@pdpc/sponsor/digium/malcolmd) |
| 22:39.30 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
