| 00:03.18 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-kzotzhwdvvrinqxl) |
| 00:04.20 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-ujaxpgtzppiayaac) |
| 00:04.20 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 00:12.35 | *** join/#asterisk-dev pchero (~pchero@dhcp-077-249-058-090.chello.nl) |
| 01:23.15 | seanbright | tm1000: roger, roger |
| 01:25.43 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 01:34.41 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 01:45.00 | *** topic/#asterisk-dev by gtjoseph -> Take the March 2019 Asterisk User Survey! https://goo.gl/forms/xL1VUHRsf95saly13 |
| 01:57.11 | *** topic/#asterisk-dev by gtjoseph -> Take the March 2019 Asterisk User Survey! https://goo.gl/forms/xL1VUHRsf95saly13 -- Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 04:33.45 | *** join/#asterisk-dev coreyfarrell (~coreyfarr@24-181-237-90.dhcp.oxfr.ma.charter.com) |
| 04:33.45 | *** mode/#asterisk-dev [+o coreyfarrell] by ChanServ |
| 04:53.42 | *** join/#asterisk-dev DivideBy0 (~DivideBy0@unaffiliated/divideby0x0) |
| 04:53.42 | *** join/#asterisk-dev jpsharp (~jsharp@linode.fivecats.org) |
| 04:53.42 | *** join/#asterisk-dev wdoekes (~walter@wjd.osso.nl) |
| 04:53.42 | *** join/#asterisk-dev jsmith (~jsmith@fedora/jsmith) |
| 04:53.42 | *** mode/#asterisk-dev [+ooo DivideBy0 wdoekes jsmith] by hitchcock.freenode.net |
| 05:22.28 | *** join/#asterisk-dev CELYA_ (~Thunderbi@pub9-47.mobius.fr) |
| 05:38.53 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 05:47.52 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 06:52.49 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 07:08.11 | *** join/#asterisk-dev pchero_work (~pchero@87.213.240.121) |
| 07:46.27 | *** join/#asterisk-dev Bordr (~Bordr@c-75-70-117-92.hsd1.co.comcast.net) |
| 08:31.37 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 08:32.05 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 09:13.03 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 09:42.05 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 09:51.34 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 10:37.19 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-fxadewzlkhtfehgu) |
| 10:37.19 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 10:40.51 | *** join/#asterisk-dev pchero_work (~pchero@87.213.240.121) |
| 10:46.16 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 11:01.24 | *** join/#asterisk-dev pchero_work (~pchero@87.213.240.121) |
| 11:34.10 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 11:42.52 | *** join/#asterisk-dev pchero_work (~pchero@87.213.240.121) |
| 11:53.58 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 12:14.16 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 12:16.18 | *** join/#asterisk-dev stevedav_ (~stevedavi@197.155.252.3) |
| 12:19.57 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 12:24.23 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 12:39.35 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 12:45.27 | file | pchero_work: https://www.irccloud.com/pastebin/VnqpEBvG/ |
| 12:47.43 | file | that's with tweaked topic names, guaranteed to be unique |
| 12:50.22 | file | argh sun |
| 12:51.15 | tsearle | no sun here, a nice hail storm at the moment :D |
| 12:53.17 | file | all hail the hail? |
| 12:53.18 | pchero_work | file: ah. About the https://gerrit.asterisk.org/c/asterisk/+/11013 ? |
| 12:53.21 | file | pchero_work: yes |
| 12:53.35 | pchero_work | I've added comment just few sec ago, could you please check that? |
| 12:54.13 | file | hrm |
| 12:54.41 | file | so you want to allow arbitrary subscription to stasis topics? |
| 12:54.56 | pchero_work | Yes. That was plan. :P |
| 12:55.01 | file | hrm |
| 12:55.26 | pchero_work | PUB/SUB for ARI. |
| 12:57.56 | file | I think this is something that needs to be fully defined specifically how it would work, how it would be used by people from the ARI side with use cases, what that interaction would look like |
| 12:58.15 | file | because this is taking ARI down a different road, it's not just a small feature at that point |
| 12:59.40 | pchero_work | Agree. I've sent a mail to Asterisk-dev once before. What can do for next? May I send it again? |
| 13:00.10 | file | I'm going to re-read your original post |
| 13:00.12 | pchero_work | Want to discussion about this. Cause I think this is good idea. :) |
| 13:00.17 | pchero_work | Thanks. :) |
| 13:00.18 | file | because I don't remember you stating it like this |
| 13:01.24 | file | so before it was about subscribing to receive messages from specific resources or all resources |
| 13:01.26 | file | has that changed? |
| 13:01.38 | pchero_work | That's the things. |
| 13:01.43 | pchero_work | Resource means topic. |
| 13:02.06 | pchero_work | And.. to subscribe the topic, the user(ari) needed to know which topics are subscribable. |
| 13:02.16 | file | that was not conveyed originally |
| 13:02.26 | file | I thought you meant subscribing to receive messages from a specific module |
| 13:02.30 | file | not subscribing to an arbitrary topic |
| 13:03.23 | pchero_work | Yes, you're right. But the modules are publishing the there messages(Events) via the topic. |
| 13:03.54 | file | that's an implementation detail |
| 13:04.17 | file | from the ARI side topics aren't a thing or known about |
| 13:05.37 | pchero_work | Agree.. hm. |
| 13:06.09 | file | so in your original email I interpreted resource to mean module |
| 13:06.23 | file | that is: an ARI consumer can subscribe to receive events from a specific module |
| 13:06.35 | file | I think that's fine, the consumer doesn't know or care about the implementation |
| 13:06.44 | file | for example you could subscribe to module:app_queue |
| 13:06.50 | file | what that does internally is an implementation detail |
| 13:07.23 | file | ideally it would be a first class citizen for events - so you could subscribe to all, or queue:sales |
| 13:07.53 | pchero_work | Okay, I agree with that. But in fact subscribing the topic is more better, after implemented the feature. |
| 13:08.37 | pchero_work | It makes possible to subscribe to specified resource(topic). i.e. Queue:Test_Queue_! |
| 13:09.25 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 13:09.51 | file | I don't think allowing subscription to topic names, provided by an ARI consumer, is good either because it exposes that implementation detail outside of the system |
| 13:10.04 | file | and means it can never be changed |
| 13:11.00 | file | unless we do store an "ARI mapping" name as you've kind of done |
| 13:13.01 | pchero_work | Right. That's not the use-case of the ARI. Having some security issues. |
| 13:15.21 | pchero_work | But also, I still think this is good feature for ARI. Because as ARI user, it's always painful to use the another channels to getting those events such as AMI. |
| 13:15.51 | pchero_work | Is it OK to send an another asterisk-dev proposal for this? |
| 13:16.01 | file | sure, but you need to expand further |
| 13:16.59 | pchero_work | Sure, thanks. :) |
| 14:19.56 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 14:30.56 | seanbright | so what's the next big thing? |
| 14:31.13 | seanbright | ... IN ASTERISK |
| 14:34.35 | file | performance! we're going to run on a 1MHz CPU |
| 14:34.51 | seanbright | i like it |
| 14:37.34 | seanbright | you know what i don't like? trying to figure out the correct libcurl-dev package to install on ubuntu |
| 14:37.59 | gtjoseph | maybe we should deliver asterisk as a snap package |
| 14:38.55 | file | make it happen, in a snap |
| 14:39.08 | seanbright | could you have jenkins build them? |
| 14:39.17 | seanbright | if so that'd be pretty fancy |
| 14:39.22 | file | probably. |
| 14:39.29 | seanbright | official yum and debian repos would be awesome too |
| 14:39.29 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 14:39.30 | seanbright | thanks |
| 15:21.45 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-pphihvapikruxici) |
| 15:21.45 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 16:02.49 | bford | any opinions on merging all the UPGRADE files into one, with version sections like CHANGES? |
| 16:03.20 | gtjoseph | +100000 |
| 16:05.54 | seanbright | -99999 |
| 16:05.57 | seanbright | where does that leave us? |
| 16:06.18 | file | hungry for lunch? |
| 16:13.45 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 16:15.11 | kharwell | bford: I'm good with that |
| 16:30.48 | *** join/#asterisk-dev sahmed (~sahmed@cpe-70-114-236-63.austin.res.rr.com) |
| 16:36.55 | bford | looks like one file it is, then |
| 16:37.03 | file | is all alone |
| 17:03.04 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 17:12.42 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 17:28.41 | seanbright | with pjsip, if i have 5 other asterisk servers that i want to call (and i pick which one to call), does each one need to be a separate endpoint & contact in configuration? |
| 17:28.53 | seanbright | or is there something fancier i can do? |
| 17:29.06 | file | you can use a single endpoint and specify the URI in the Dial string if you want |
| 17:29.50 | seanbright | nifty. i'll give that a whirl. |
| 17:30.02 | file | PJSIP/endpoint/sip:bob@somewhere.com |
| 18:02.18 | seanbright | we need a new function... |
| 18:02.43 | seanbright | MAKE_DIAL_STRING("SIP", "endpoint", "to") |
| 18:03.07 | seanbright | because not having it means i have to do more work... and i don't like doing more work, as you know |
| 18:06.05 | file | seanbright: DSaaS, Dial Strings as a Service |
| 18:06.47 | seanbright | YES |
| 18:06.52 | seanbright | genius |
| 18:08.01 | file | seanbright: you just need to use GraphQL |
| 18:08.08 | file | and node.js |
| 18:08.10 | file | and Kubernetes |
| 18:09.20 | seanbright | it's almost too easy |
| 19:13.20 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 19:24.55 | seanbright | #asterisk is such a disaster sometimes, but it's hilarious |
| 19:25.24 | gtjoseph | Fender? |
| 19:25.39 | seanbright | drmessano, [TK]D-Fender, Samot... |
| 19:25.43 | seanbright | the list goes on and on |
| 20:15.19 | *** join/#asterisk-dev pchero (~pchero@dhcp-077-249-058-090.chello.nl) |
| 20:34.10 | coreyfarrell | csavinovich: can we revert https://gerrit.asterisk.org/#/c/asterisk/+/10890/ (it was reverted from the release branches but not master) |
| 21:15.54 | *** join/#asterisk-dev pchero_work (~pchero@dhcp-077-249-058-090.chello.nl) |
| 21:25.41 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 21:34.48 | *** join/#asterisk-dev stevedavies (~stevedavi@197.155.252.3) |
| 22:05.50 | *** join/#asterisk-dev snuff-work (~snuff-wor@202-161-112-134.tpgi.com.au) |
| 22:05.50 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 22:26.46 | seanbright | coreyfarrell: json.c: Error building JSON from '{s: o?, s: o, s: O?}': Expected format 's', got '?'. |
| 22:26.57 | seanbright | is that a jannson-is-too-old error? |
| 22:28.13 | rmudgett | seanbright: I looked at that typo patch and couldn't see the typo. I finally had to have gerrit show me where that typo was. |
| 22:28.44 | seanbright | rmudgett: my vision is ON POINT |
| 22:28.55 | seanbright | ... and asterisk was bitching about that line when i installed samples |
| 22:34.27 | coreyfarrell | seanbright: the `?` pack options were added in jansson 2.8, oddly enough if you're talking about ASTERISK-28329 the config.log says that 2.11 was detected. |
| 22:34.37 | seanbright | yeah, that is what i am talking about |
| 22:36.32 | seanbright | https://github.com/asterisk/asterisk/blob/16/main/rtp_engine.c#L3433-L3436 |
| 22:36.45 | seanbright | anything look weird/wrong about that? |
| 22:38.54 | coreyfarrell | seanbright: I'm the one who made that change so I'm going to automatically say no :) |
| 22:39.00 | seanbright | heh |
| 22:39.26 | coreyfarrell | it definitely will not work with jansson < 2.8 though, but Asterisk 16 should block those older versions. |
| 22:39.53 | seanbright | it's not the most useful error message |
| 22:43.10 | coreyfarrell | seanbright: we could create __ast_json_pack and __ast_json_vpack functions that take file/line/func to be passed to the logger (though it would be an ABI change so probably master only). |
| 22:43.32 | seanbright | it's not that there is no location, i just don't grok the error message. |
| 22:43.42 | seanbright | like... why were you expecting an 's?' |
| 22:44.12 | seanbright | it's not something that needs fixing. if you understand it, that is good enough for me. |
| 22:46.03 | coreyfarrell | seanbright: just so you are aware comma, colon and whitespace are insignificant to the json_pack format string. so json_pack("{s: o, s: o, s: o}", ...) is functionally identical to json_pack("{sososo}", ...) |
| 22:46.16 | seanbright | gotcha, so it has to be a versioning issue |
| 22:46.29 | seanbright | or at least that would make the most sense |
| 22:50.33 | pchero | There's no type for the message. I've seen that before, but I wasn't sure about that. But now I can see it. |
| 22:50.54 | pchero | RTCPReceived/RTCPSent |
| 22:51.22 | seanbright | hmm? |
| 22:52.09 | pchero | I wasn't sure that's the bug or not atm, but I can see that's bug. |
| 22:54.53 | coreyfarrell | seanbright: https://gist.github.com/coreyfarrell/5353e74f83c13a52c604072ef34d67ca |
| 22:56.08 | seanbright | can you reproduce with the same format string as the one in question? |
| 22:56.16 | seanbright | or is that a PITA? |
| 22:58.58 | coreyfarrell | seanbright: not a problem, still works fine. updated the gist. |
| 22:59.15 | seanbright | ok, well then that is weird |
| 22:59.54 | seanbright | probably has multiple versions of jansson installed |
| 23:02.04 | coreyfarrell | hmmm I thought that asterisk 16 used json_sprintf() but apparently it does not. so although ./configure enforces use of jansson >= 2.11 I think libc would load jansson-2.7 because we don't use any symbols which are not available in that version. |
| 23:02.44 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-pphihvapikruxici) |
| 23:03.03 | seanbright | just throw a bogus call to json_sprintf() in main/json.c somewhere and we're all set. |
| 23:10.48 | coreyfarrell | seanbright: will post a review for that shortly. |
| 23:11.12 | seanbright | i was half kidding, but if it works... |
| 23:21.13 | coreyfarrell | was easy enough |
| 23:23.08 | seanbright | the empty string? come on... we can do better than that |
| 23:23.19 | seanbright | "Sean & Corey - BFFs" |
| 23:23.34 | seanbright | "JSON Bourne" |
| 23:24.44 | seanbright | or other things. i ran out of ideas. |