IRC log for #asterisk-dev on 20171213

00:01.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
00:09.28*** part/#asterisk-dev kharwell (kharwell@nat/digium/x-tsslgbixusffopnv)
00:12.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
00:29.09*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
00:39.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
00:44.54*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
01:07.06*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
01:18.31*** join/#asterisk-dev infobot (ibot@rikers.org)
01:18.31*** topic/#asterisk-dev is 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
01:21.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
01:28.08*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
01:57.09*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
02:02.25*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
02:07.41*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
02:12.43*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
02:24.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
02:43.09*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
02:48.25*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
02:54.12*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
02:59.43*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
03:04.59*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
03:10.44*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
03:21.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
03:26.43*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
03:32.13*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
03:37.14*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
03:43.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
03:48.43*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
03:53.43*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
04:05.55*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
04:26.09*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
04:32.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
04:43.08*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
04:48.24*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
04:56.36*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
05:01.43*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
05:06.59*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
05:13.08*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
05:19.38*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
05:24.43*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
05:29.43*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
05:34.59*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
05:49.09*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
05:54.25*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
06:00.42*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
06:05.43*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
06:11.09*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
06:16.56*** join/#asterisk-dev CELYA_1 (~Thunderbi@a6634-0468527749.pck.nerim.net)
06:23.28*** join/#asterisk-dev sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com)
06:28.08*** join/#asterisk-dev CELYA_1 (~Thunderbi@62.212.111.67)
06:33.37*** join/#asterisk-dev CELYA_ (~Thunderbi@a6634-0468527749.pck.nerim.net)
06:38.53*** join/#asterisk-dev CELYA_ (~Thunderbi@62.212.111.67)
06:55.38*** join/#asterisk-dev jkroon (~jkroon@uls-154-73-35-201.wall.uls.co.za)
07:27.44*** join/#asterisk-dev tsearle (~tsearle@37.19.10.33)
07:27.44*** mode/#asterisk-dev [+o tsearle] by ChanServ
07:40.48*** join/#asterisk-dev CELYA_ (~Thunderbi@AMontsouris-682-1-26-103.w90-87.abo.wanadoo.fr)
08:06.04*** join/#asterisk-dev wdoekes (~walter@wjd.osso.nl)
08:06.05*** mode/#asterisk-dev [+o wdoekes] by ChanServ
08:15.47*** join/#asterisk-dev pchero_work (~pchero@109.70.54.56)
08:54.03*** join/#asterisk-dev jkroon_ (~jkroon@165.16.204.36)
09:06.20*** join/#asterisk-dev jkroon_ (~jkroon@uls-154-73-35-201.wall.uls.co.za)
10:05.06*** join/#asterisk-dev CELYA_ (~Thunderbi@AMontsouris-682-1-26-103.w90-87.abo.wanadoo.fr)
10:13.40*** join/#asterisk-dev CELYA_ (~Thunderbi@AMontsouris-682-1-26-103.w90-87.abo.wanadoo.fr)
13:18.34fileI got the existing qualify tests working against my new code last night, bit by bit
13:32.22seanbrightyayay
13:32.27seanbrightis oddly excited
13:40.14filemight take me longer to get it all sorted, there's tests I want to add too
13:40.16file:P
14:15.34fileseanbright: time flies!
14:22.41seanbrightfile: indeed. i require "bulk change" permission in jira.
14:22.46seanbrightpleas and thank you.
14:22.53filelet's see...
14:23.02fileuse it wisely... if I can grant it
14:23.06seanbrightwill do
14:26.37filehrm
14:27.29filekicks JIRA
14:28.36fileseanbright: done
14:33.39seanbrightfile: thanks
14:43.45*** join/#asterisk-dev bford (d8cff501@gateway/web/freenode/ip.216.207.245.1)
14:43.46*** mode/#asterisk-dev [+o bford] by ChanServ
14:45.33fileseanbright: what are you doing? O.o
14:45.42seanbrightfile: fixing chan_sip bugs
14:45.51filenot that, but adding odd comments
14:45.51seanbrightwell... organizing chan_sip bugs
14:45.58seanbrightthe comments are with the links
14:46.10seanbrighti guess that is unclear
14:46.18seanbrightwhen you link issues you specify a comment
14:46.26filesilly JIRA
14:46.31fileyou don't have to
14:46.54filecomment be optional there yo
14:47.29seanbrightdeleted
14:47.32seanbrightsorry to BOTHER YOU
14:47.54fileha it wasn't that - I thought you were trying to do tagging or something
14:47.59seanbrightnah
14:48.15seanbrightbut that's a good idea
14:49.33*** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com)
14:49.33*** mode/#asterisk-dev [+o tzafrir] by ChanServ
15:01.10*** join/#asterisk-dev cresl1n (Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
15:01.11*** mode/#asterisk-dev [+o cresl1n] by ChanServ
15:14.15*** join/#asterisk-dev kharwell (kharwell@nat/digium/x-zqihomlaobzmsthj)
15:14.16*** mode/#asterisk-dev [+o kharwell] by ChanServ
15:20.55coreyfarrelldoes anyone have an opinion on updating some of the public CLI completion generators to use ast_cli_completion_add?  Talking about ast_complete_channels for example.
15:21.02tzafrirIs there any objection to add "/.pc" to the .gitignore file? It helps with the Debian packaging (with quilt-style patches)
15:35.56seanbrightcresl1n: hi
15:36.06seanbrighttzafrir: not that i can think of. put it up for review.
15:36.15seanbrightcoreyfarrell: would it change api?
15:36.18coreyfarrelltzafrir: are debian packages built from an asterisk git clone?  sorry for naive question RPM only works from tarballs.  if multiple ignores are required I'd like them to be together in the root .gitignore but otherwise I'm indifferent.
15:37.06cresl1nseanbright!!!!
15:37.14seanbrightcresl1n: how you doin' buddy?
15:37.37cresl1nComing out of the post "Asterisk 15: Under the Hood" webinar funk
15:37.48cresl1nOther than that good :-)
15:37.50filecresl1n: never again?
15:37.57cresl1nI think that every year
15:37.59seanbrightsuper. i have a request.
15:38.03cresl1nbut then a lot of people show up to it
15:38.18cresl1nseanbright: your request will be answered in the order that it was submitted
15:38.23cresl1nyou are currently #1 in the queue
15:38.36seanbrightnice. codec_opus that dynamically links against libopus.
15:38.44seanbrighthow do i get that moved up in the internal digium queue?
15:38.47coreyfarrellseanbright: yes, kind of.  any function which uses ast_cli_completion_add would return NULL instead of an allocated string.
15:39.00cresl1nseanbright: great question
15:39.02seanbrightcresl1n: i can think of two options - i throw some money at digium
15:39.08cresl1nlet me talk to my peoples about it
15:39.12seanbrightcresl1n: or you let me do it after signing an NDA
15:39.28seanbrightcoreyfarrell: ah, right.
15:39.56cresl1nseanbright: do you mind me asking what your goal is with dynamic linking?
15:40.06cresl1nJust so that libopus bupgrades are easier?
15:40.12cresl1n*upgrades
15:40.38seanbrightlibopus has many code paths that take advantage of the native processor's SIMD instructions
15:40.46cresl1nAhhhhhhhhhhhhhhh
15:40.57seanbrightbased on a conversation with file many moons ago, you disable those
15:40.58tzafrircoreyfarrell, There are generally multiple ways of building deb packages from git. In the one used in the asterisk package, we don't use Upstream's git directly,
15:41.05cresl1nthe more channels/processor-mips angle?
15:41.08tzafrirbut rather use all the files from there
15:41.17seanbrightcresl1n: correct
15:41.20seanbrightcresl1n: HOWEVER
15:41.59seanbrightsomething that could benefit everyone (even with the statically linked version), is to enable up to SSE2 (might be SSE3) on the 64 bit builds
15:42.06cresl1nok
15:42.16seanbrightbecause x86_64 requires one of those (i don't remember which)
15:42.21seanbrightso you know they are there
15:42.49seanbright"A x64 native (AMD64 or Intel 64) processor is only mandated to support SSE and SSE2."
15:43.26seanbrightso at a minimum it would be great to have those
15:44.08seanbrightbut according to mjordan at astricon, digium isn't modifying the libopus they are statically linking, so i don't necessarily understand the rationale for statically linking
15:44.19seanbrightother than potentially making installation easier
15:44.21cresl1nseanbright: that's exactly what I'm gonna dig into
15:44.29cresl1nI was trying to remember that exact same thing
15:44.50seanbrighti'm happy to throw some money at you if that speeds things along
15:45.04seanbrighti'm also happy to do it, but that is obviously more complicated
15:45.46coreyfarrellseanbright: I'm looking at ASTERISK-21038.  see https://github.com/asterisk/asterisk/blob/master/main/cli.c#L1386 - if a->word doesn't match "all" then the completion would be wrong (a->n - 1 passed to ast_complete_channels).
15:46.17seanbrightcoreyfarrell: if you're changing API i think you're kinda stuck. maybe add new API? or maybe change the implementation so that it only returns NULL if you pass in "magic" arguments of some kind
15:46.46seanbrightsomething that wouldn't get passed in to those functions in the wild
15:46.52coreyfarrellseanbright: you mean like passing -1 instead of a->n?  hmmm that could work.
15:47.55seanbrightyeah, something along those lines
15:51.23*** join/#asterisk-dev Worldexe (~Worldexe@95-107-33-134.dsl.orel.ru)
15:53.31*** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-znmakrgnpyxkqlsq)
15:53.31*** mode/#asterisk-dev [+o rmudgett] by ChanServ
17:14.13*** join/#asterisk-dev pchero (~pchero@109.70.54.56)
17:27.26rmudgettcoreyfarrell: The core set verbose command got screwed up when the ability to set verbose level per console was added.
17:28.12rmudgettIt used to send all verbose messages to every console and the consoles would filter them appropriately.  However, this was very CPU expensive.
17:28.56rmudgettI fixed it so the core filtered to the max level currently active.
17:29.24rmudgettand then to filter fore each console.
17:31.59coreyfarrellyes the filtering happens on the daemon which means that the rasterisk process should just print whatever it is given.
17:33.04coreyfarrellI'm guessing my change should be cherry-picked to 15 but I'm unsure about 13.
17:33.54rmudgettIt was left in for backwards compatibility.
17:35.29*** join/#asterisk-dev sruffell (sruffell@asterisk/the-kernel-guy/sruffell)
17:35.30*** mode/#asterisk-dev [+o sruffell] by ChanServ
17:35.36coreyfarrellrmudgett: so in 13.0.0 rasterisk was responsible for filtering?  before 15.0.0 the daemon filtered so I think it can go in 15?
17:35.42*** join/#asterisk-dev sruffell (sruffell@asterisk/the-kernel-guy/sruffell)
17:35.43*** mode/#asterisk-dev [+o sruffell] by ChanServ
17:46.25coreyfarrellrmudgett: actually asterisk 13.0.0 already had the comment about the remote console processing core set verbose for compatibility with older versions, so I think it could be removed from 13 as well (especially since doing so fixes a bug)
18:15.46*** join/#asterisk-dev jkroon (~jkroon@165.16.204.166)
18:21.28rmudgettv11 had to have that for backward compatibility since I fixed the performance penalty in the middle of v11.
18:23.51rmudgettv12 also had to have it for the same reason.
18:27.28rmudgettIf we no longer care about using rasterisk with other branches then v13 won't need it.  Some of your or seanbright's recent command line processing changes in master at least have removed that requirement. :)
18:54.24*** join/#asterisk-dev Demon_VoIP (~demon@109.60.222.253)
19:47.20rmudgettfile: Re: https://issues.asterisk.org/jira/browse/ASTERISK-27440  To determine if a RTP stream is video I was going to look at the payload types for the codec types.  However, if the stream changes types from audio to video then I would likely pick the wrong learning strategy.
19:47.57rmudgettI was wondering if we care or if I should have the channel driver tell me what stream type is being used.
19:48.43rmudgettHaving the channel drivers tell me requires touching more modules.
19:49.43filefor anything pre-15 we wouldn't use the same RTP instance
19:49.48fileand I think that also applies to 15+
19:50.26fileyeah, we don't reuse there either
19:50.50fileso an RTP instance itself will never be reused when going audio->video or video->audio
19:51.38gtjosephcoreyfarrell: what markdown dialect are the README files in?
19:53.37coreyfarrellgtjoseph: I wasn't aware there were multiple dialects.  I used github and daring fireball docs as references when I made those files.
19:54.12gtjosephyeah confluence (atlassian) has it's own version of course and there are a few other flavors
19:54.21gtjosephgithub's fine though
20:16.27*** join/#asterisk-dev maruen (~maruen@2804:431:d718:35e3:45b8:aa3d:6949:7eaf)
20:16.50maruenHello everybody
20:17.20maruenIs it possible to have any script that could change the IMEI on the dongles? My carrier had blocked all dongles through it's IMEI
20:17.28maruenAny help on it, I would appreciate
20:18.13fileI don't think this is the right place to ask such questions...
20:21.29maruenDo you know some other place where I can ask such thing?
20:23.01*** join/#asterisk-dev tzafrir (~tzafrir@62-90-199-170.barak.net.il)
20:23.01*** mode/#asterisk-dev [+o tzafrir] by ChanServ
20:43.46*** join/#asterisk-dev Gugge (gugge@92.246.2.105)
20:58.32seanbrightwhat is an IMEI?
20:59.07seanbrightand how does it relate to the development of the asterisk open source PBX?
21:10.43*** join/#asterisk-dev CELYA_ (~Thunderbi@185.204.210.40)
21:15.00*** join/#asterisk-dev CELYA_1 (~Thunderbi@185.218.32.32)
21:25.01cresl1nIMEI is a device specific mobile ID, IIRC
21:25.43cresl1nDon't know about the second
21:25.52cresl1nmaruen: wrong room for this sort of thing
21:28.05*** join/#asterisk-dev CELYA_1 (~Thunderbi@185.218.32.31)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.