| 04:27.45 | *** join/#asterisk infobot (ibot@96-86-209-99-static.hfc.comcastbusiness.net) |
| 04:27.45 | *** topic/#asterisk is #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.35.0 (2020/07/16) 16.12.0 (2020/07/16) Standard: 17.6.0 (2020/07/16); DAHDI: 3.0.0 (2018/11/15); libpri 1.6.0 (2017/01/27) -=- Wiki: wiki.asterisk.org -=- Code of Conduct: bit.ly/1hH6P22 |
| 04:53.23 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.241) |
| 05:40.07 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
| 06:12.05 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 06:15.44 | post-factum | dmacias: why not using lua? |
| 06:27.36 | *** join/#asterisk rjt (~anon@wsip-70-184-216-165.om.om.cox.net) |
| 06:43.33 | drmessano | lua wow |
| 06:46.47 | *** join/#asterisk lankanmon (~LKNnet@CPEb4fbe4e331bd-CM64777d632380.cpe.net.cable.rogers.com) |
| 06:54.52 | *** join/#asterisk tehgooch (tehgooch@unaffiliated/tehgooch) |
| 07:13.03 | *** join/#asterisk tehgooch (tehgooch@unaffiliated/tehgooch) |
| 07:24.39 | *** join/#asterisk tehgooch (tehgooch@unaffiliated/tehgooch) |
| 07:38.56 | *** join/#asterisk defsdoor (~Andrew@cpc120600-sutt6-2-0-cust232.19-1.cable.virginm.net) |
| 07:40.54 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 07:48.22 | *** join/#asterisk jkroon (~jkroon@165.16.204.35) |
| 07:55.32 | *** join/#asterisk AsteriskRoss (~AsteriskR@r01.nt-r1.nor.gb.voicehost.co.uk) |
| 08:41.57 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 08:45.55 | *** join/#asterisk puzzola (~puzzola@unaffiliated/puzzola) |
| 08:47.49 | *** join/#asterisk rjt (~anon@wsip-70-184-216-165.om.om.cox.net) |
| 08:53.40 | *** join/#asterisk Jesterboxboy (~Thunderbi@84-115-150-8.cable.dynamic.surfer.at) |
| 09:00.21 | *** join/#asterisk luckman212 (luckman212@unaffiliated/luckman212) |
| 09:07.16 | *** join/#asterisk pa (~pa@unaffiliated/pa) |
| 09:18.18 | *** join/#asterisk cryptic (~cryptic@142.196.139.17) |
| 09:19.53 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.81) |
| 09:20.38 | *** join/#asterisk mmlj4 (~mmlj4@ip68-11-51-163.no.no.cox.net) |
| 09:44.56 | *** join/#asterisk Grommish (~quassel@2600:2b00:932c:ff00:e848:977e:9e20:773b) |
| 10:11.25 | *** join/#asterisk Grommish_ (~quassel@dsl-50-5-33-79.fuse.net) |
| 10:23.50 | *** join/#asterisk fstd_ (~fstd@unaffiliated/fisted) |
| 10:46.45 | *** join/#asterisk FH_thecat (~FH_thecat@75.11.25.212.ftth.as8758.net) |
| 11:11.51 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 11:28.00 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.241) |
| 11:44.23 | *** join/#asterisk i9zO5AP (~BQcdf9eiZ@gateway/tor-sasl/ai9zo5ap) |
| 12:01.05 | *** join/#asterisk rpifan_ (~rpifan@p200300d2670e442000b1d0a862494d3f.dip0.t-ipconnect.de) |
| 12:08.33 | *** join/#asterisk sekil (~sekil@79-101-174-239.dynamic.isp.telekom.rs) |
| 12:44.22 | *** join/#asterisk n0tiz (~n0tiz@82-69-15-38.dsl.in-addr.zen.co.uk) |
| 12:45.33 | *** join/#asterisk beardy (~beardy@unaffiliated/beardy) |
| 12:46.21 | n0tiz | Hey, got a quick question. I've created my local branch according the asterisk issue identifier, however when I'm committing, there's no change id being generated. Should I be pushing the branch to remote prior to committing, and will that then append the change id? |
| 12:48.23 | file | git review will automatically see you have no change-id, download the hook that adds it, amend your commit, and then put it up for review |
| 12:52.55 | sibiria | i have a question about Asterisk's port allocation: if i in rtp.conf set the range 10000-20000, does this mean that the last RTP port will be 19999 and its RTCP port 20000, or will it be 20000 and 20001? |
| 12:53.51 | *** join/#asterisk retentiveboy (~retentive@c-76-97-11-199.hsd1.ga.comcast.net) |
| 12:54.47 | sibiria | (afaik it's not a hard requirement that RTCP is on an odd port) |
| 12:55.18 | file | 20000 and 20001 I believe |
| 12:55.34 | file | it's a hard requirement in practice |
| 12:56.03 | file | at least from my past experience, some remote implementations for whatever reason don't like it otherwise |
| 12:56.12 | *** join/#asterisk paulgrmn (~paulgrmn@c-98-250-183-21.hsd1.mi.comcast.net) |
| 12:56.33 | sibiria | yeah it's not a requirement per specs, i meant, but probably should be assumed to be so in practical applications |
| 12:58.13 | *** join/#asterisk spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
| 13:06.56 | seanbright | > For UDP and similar protocols, RTP SHOULD use an even destination port number and the corresponding RTCP stream SHOULD use the next higher (odd) destination port number. |
| 13:07.04 | seanbright | 'should' is my least favorite RFC word |
| 13:07.15 | sibiria | same. we should get a beer together |
| 13:07.21 | seanbright | totes |
| 13:07.53 | sibiria | https://github.com/asterisk/asterisk/blob/c84d962eae394946b777c769522dc9541f1e4540/res/res_rtp_asterisk.c#L3776-L3803 |
| 13:08.21 | sibiria | someone should apply some lookup(r) table(tm) technology(r)(tm) on this |
| 13:08.30 | sibiria | i can imagine it getting a bit juicy when the range is large and starved |
| 13:09.26 | seanbright | patches. welcome. |
| 13:09.54 | sibiria | but but, i do too much programming at my day job already |
| 13:10.02 | seanbright | it would be easier if other processes on the box couldn't bind to ports in that range |
| 13:11.05 | sibiria | stupid other processes and their shenanigans |
| 13:17.57 | *** join/#asterisk schangg (~besnard@lputeaux-656-1-124-218.w92-154.abo.wanadoo.fr) |
| 13:17.59 | schangg | Hello |
| 13:18.12 | seanbright | i don't like your tone... |
| 13:18.13 | schangg | I would like to run asterisk in a NATed environment |
| 13:18.58 | seanbright | ok, go for it |
| 13:18.58 | schangg | I have followed various resources found on the internet. But in SIP messages, I still see the internal LAN IP being advertised like "o=root 1359187237 1359187237 IN IP4 172.18.0.4" |
| 13:19.10 | seanbright | chan_sip or chan_pjsip? |
| 13:21.20 | schangg | also, some resources refer to externip in sip.conf (which I can not find documented anywhere in the default sip.conf file). Is this parameter still current ? |
| 13:23.46 | sibiria | chan_sip - just say no. it's more dangerous than copying that floppy |
| 13:42.01 | schangg | still working on my NAT problem. When running tcpdump on the asterisk host, I see that it gets my RTP trafic. But it is not sending anything to me |
| 13:42.09 | seanbright | chan_sip |
| 13:42.14 | schangg | like not even trying something it would not be able to reach |
| 13:42.34 | seanbright | you should post your sip.conf somewhere that we can see it (do not paste it in the channel) |
| 13:42.37 | seanbright | ~pb |
| 13:42.38 | infobot | well, pastebin is a web-based service where you should paste anything over 3 lines so you don't flood the channel. Here are links to a few: http://pastebin.ca, http://channels.debian.net/paste, http://paste.lisp.org, http://bin.cakephp.org/; or install pastebinit with yum or aptitude. |
| 13:42.46 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 13:42.47 | seanbright | not sure many of those work anymore |
| 13:43.53 | schangg | https://hastebin.com/ateyokusiv.md |
| 13:46.22 | *** join/#asterisk kharwell (uid358942@gateway/web/irccloud.com/x-xpzgwdwdztfbpliu) |
| 13:46.22 | *** mode/#asterisk [+o kharwell] by ChanServ |
| 13:47.27 | schangg | did that help |
| 13:48.19 | seanbright | run 'sip set debug on' from the asterisk CLI, capture the output of a failed call and pastebin it |
| 13:51.08 | Samot | I have a question, how is this behind NAT? |
| 13:51.15 | schangg | https://hastebin.com/zufexaxopi.makefile |
| 13:51.26 | schangg | asterisk running inside a docker |
| 13:51.57 | schangg | the frist traces are the registration as you'll certainly see so you probably want to skip to the very end |
| 13:52.16 | Samot | OK so you have 172.16.0.0 as your local nat |
| 13:52.30 | schangg | right |
| 13:52.31 | Samot | Yet the device you are testing from is on 192.168.1.x |
| 13:52.44 | schangg | and 192.168.1.x is the actual network calls com from |
| 13:52.58 | Samot | OK so you don't have it listed as a local network. Which it is. |
| 13:53.02 | schangg | so not really NAT as if it were facing the internet but I'd assume this is the same anyways |
| 13:53.06 | Samot | Because your phones are on it. |
| 13:53.16 | schangg | phones are on 192.168.1.x |
| 13:53.21 | Samot | Right |
| 13:53.25 | Samot | So that's a LOCAL network |
| 13:53.32 | Samot | Which should be listed as such |
| 13:53.46 | Samot | The NAT stuff only works if it knows the network is supposed to be local or not. |
| 13:54.14 | schangg | so I should add a line with localnet=192.168.1.x ? |
| 13:54.23 | Samot | Correct. |
| 13:54.44 | schangg | for me local is 172 (where the asterisk is running) |
| 13:54.54 | schangg | not sure why 192 should also be local |
| 13:55.11 | schangg | what difference does it make if instead of 192 it were the all internet then ? |
| 13:55.37 | Samot | Dude. |
| 13:55.46 | Samot | Your devices are on the 192.168.1.x network. |
| 13:55.56 | Samot | Your PBX has an IP of 192.168.1.x |
| 13:56.02 | Samot | These are all LOCAL to the PBX |
| 13:56.10 | Samot | You want to PBX to treat them as local networks. |
| 13:56.34 | schangg | my pbx has 192.168.1 address only because there is a NAT rule for that (NAT rule that translates 192.168.1.6 to the 172 IP of the asterisk server) |
| 13:56.51 | Samot | I'll say this one more time. |
| 13:56.56 | schangg | okok got it |
| 13:56.58 | Samot | Your phones are on the 192.168.1.x network |
| 13:57.22 | schangg | I'm just asking because what I should mention is that (later on) the phone will be on the internet |
| 13:57.24 | Samot | Asterisk will only apply the exteraddr and NAT settings to those that are in *local networks* |
| 13:57.49 | schangg | as I knew I would strufgle with NAT I have first thought that I'll try first with a first level of NAT and then add the second |
| 13:58.14 | schangg | being understood that it will be like public IP > 192.xxx > 172.xxx |
| 13:58.45 | Samot | Why would you double NAT this? |
| 13:59.14 | schangg | because when you run something in a docker it is always running inside the docker daemon which has its internal network |
| 13:59.29 | Samot | OK and this is why docker is never recommended for this. |
| 13:59.36 | Samot | NAT is already a problem for SIP |
| 13:59.42 | Samot | It can be a major PITA. |
| 13:59.45 | schangg | so to access asterisk from the local 192 I first need to tell docker to forward stuff to that docker |
| 13:59.49 | Samot | Double NATing is just asked for more problems. |
| 14:00.23 | schangg | Samot I get that and this is why I wanted to first overcome the first layer of NAT before moving to the second one |
| 14:00.31 | n0tiz | @file, thanks for your advise, review automatically added the change id when i used the git review command. |
| 14:00.41 | Samot | You'll need to find someone that can help with this then. |
| 14:01.10 | Samot | I have never put Asterisk on a container/docker. Never would. |
| 14:01.14 | schangg | anyways, still not working after adding localnet=192.168.1.1/255.255.255.0 |
| 14:01.27 | Samot | That's not right, is it? |
| 14:01.35 | schangg | Samot no, not working |
| 14:01.37 | Samot | 192.168.1.1/255.255.255.0 <-- That look proper? |
| 14:01.46 | Samot | For adding an entire /24? |
| 14:02.13 | schangg | I though you mean adding the entire network where phone are currently located |
| 14:02.24 | Samot | I did. |
| 14:02.32 | Samot | 192.168.1.1/255.255.255.0 is wrong. |
| 14:03.04 | schangg | https://hastebin.com/uwozigorut.ini |
| 14:03.11 | schangg | why is it wrong ? |
| 14:03.23 | file | n0tiz: no prob |
| 14:03.24 | schangg | should be only the NAT IP ? 192.168.1.6 in my case |
| 14:04.01 | Samot | Sigh |
| 14:04.06 | Samot | Are you phones all using that IP? |
| 14:04.16 | Samot | Or do they have different IPs on that 192.168.1.x network? |
| 14:04.21 | Samot | They have different IPs. |
| 14:04.24 | Samot | You want the NETWORK |
| 14:04.27 | Samot | Not individual IPs. |
| 14:04.32 | schangg | my phones haves IPs like 192.168.1.178 for example |
| 14:04.53 | Samot | localnet=192.168.1.0/255.255.255.0 <-- That is correct |
| 14:04.58 | schangg | 192.168.1.178 is the IP of the phone that I have in my tests |
| 14:05.33 | schangg | Samot ah ok |
| 14:05.47 | Samot | Because that's how you correctly denote a /24 |
| 14:06.19 | schangg | anyways my cnf is 192.168.1.0/255.255.255.0 (see https://hastebin.com/uwozigorut.ini pasted before) |
| 14:06.27 | sibiria | chan_sip can do regular CIDR as well |
| 14:06.38 | sibiria | e.g. 172.31.0.0/16 etc. |
| 14:06.50 | Samot | Yes. |
| 14:06.50 | sibiria | (for localnet) |
| 14:07.09 | schangg | the default config file uses /255.255xxxx so I thought why not doing the same |
| 14:07.27 | Samot | Though, 172.31.0.0/16 would be bad. |
| 14:07.33 | Samot | As it would bleed into public spaces. |
| 14:08.50 | sibiria | hm no that should be within the 20 bit 172.16.0.0/12 thingy |
| 14:08.57 | sibiria | 172.16.0.0 - 31.255.255 |
| 14:10.03 | Samot | No, I did the math wrong. |
| 14:10.09 | schangg | not quite sure to follow here |
| 14:10.25 | Samot | sibiria: Yeah, I calculated it wrong. |
| 14:10.31 | schangg | do you recomment that I put 192.168.1.1/24 or 192.168.1.0/255.255.255.0 ? |
| 14:10.36 | sibiria | schangg: i was just digressing. your /255.255.255.0 netmask format is entirely fine |
| 14:10.42 | Samot | Either works. |
| 14:10.51 | schangg | ok |
| 14:11.00 | schangg | but that still does not work for me at the moment :) |
| 14:11.30 | schangg | Samot what what I have pasted looks god to you right ? |
| 14:11.54 | Samot | What's not working? |
| 14:13.21 | schangg | not hearing anything when I call an IVR extension |
| 14:14.57 | Samot | Wait, so you're calling an IVR and then pressing an option to get to the extension? |
| 14:14.58 | schangg | and also, before, with tcpdump running on the asterisk server, I was seeing RTP raffic coming from the phone (and nothing going out fro asterisk to the phone) while now there is just no rtp trafic at all |
| 14:15.46 | schangg | which can certainly be explained by the fact that I now see 172 again in the SIP messages "o=root 196894813 196894813 IN IP4 172.18.0.4 |
| 14:16.20 | Samot | Where did that IP come from? |
| 14:17.34 | schangg | shoot there is something wrong here |
| 14:17.37 | sibiria | have you remembered to set externhost or externaddr? |
| 14:17.39 | schangg | 172.18 instead of 172.16 |
| 14:18.34 | schangg | fixing that in first place before I come back :) |
| 14:19.14 | schangg | to sume it up |
| 14:19.16 | schangg | I have |
| 14:19.17 | schangg | localnet=172.18.0.0/255.255.0.0 |
| 14:19.17 | schangg | localnet=192.168.1.0/255.255.255.0 |
| 14:19.17 | schangg | externip=192.168.1.6 |
| 14:20.07 | seanbright | that externip looks wrong if 192.168.1.0/24 is a localnet |
| 14:20.08 | schangg | and when I cann from my phone which IP is 192.168.1.178 I see with asterisk sip debug on that the RTP target given to my phone is 172.18.0.4 (the IP of asterisk) |
| 14:20.24 | seanbright | what is the IP address of the asterisk server? like at the OS level |
| 14:20.33 | schangg | 172.18.0.4 |
| 14:20.46 | schangg | it is NATed behing 192.168.1.6 |
| 14:20.59 | schangg | and phones are on 192.168.1.1/24 |
| 14:21.57 | schangg | seanbright so doe my conf look alright to you ? |
| 14:22.06 | seanbright | ok, then 192.168.1.0/24 should not be a localnet, unless i am confused |
| 14:22.18 | seanbright | although Samot disagrees |
| 14:22.23 | seanbright | and he is usually correct |
| 14:23.43 | Samot | It shouldn't? |
| 14:23.48 | *** join/#asterisk bford (uid283514@gateway/web/irccloud.com/x-fssnrhpycplxpbwa) |
| 14:23.49 | *** mode/#asterisk [+o bford] by ChanServ |
| 14:23.50 | Samot | The phones on that network shouldn't be local? |
| 14:23.53 | Samot | OK. |
| 14:24.28 | Samot | I mean this is some docker mess with double NATing.. |
| 14:24.29 | schangg | I am a bit confused, sorry |
| 14:24.38 | Samot | Perhaps those phones shouldn't be because they are "remote" |
| 14:24.43 | schangg | simple NATing so far (wait for it :) ) |
| 14:27.47 | seanbright | if the phones cannot access 172.18.0.4 without going through the NAT, then the 192 network is indeed remote and should not be localnet |
| 14:28.51 | schangg | seanbright so I have removed the line that says 192.168 is localnet |
| 14:28.58 | seanbright | great |
| 14:29.38 | schangg | and when I do that, I see RTP traffic going from the phone the asterisk |
| 14:29.46 | seanbright | great |
| 14:29.47 | schangg | (using tcpdump on th asterisk host) |
| 14:29.51 | seanbright | great |
| 14:29.57 | schangg | but nothing going out of the asterisk host |
| 14:30.00 | seanbright | great |
| 14:30.31 | seanbright | 'sip set debug on' capture the bad call, and pastebin the output |
| 14:30.37 | schangg | sure |
| 14:30.37 | seanbright | a fresh example |
| 14:32.04 | schangg | https://hastebin.com/uhecahudep.makefile |
| 14:32.10 | schangg | fresh |
| 14:33.40 | schangg | and here and sample of the tcpdump capture: https://hastebin.com/wicajukopo.css |
| 14:35.33 | *** join/#asterisk rmudgett (~rmudgett@170.249.191.178) |
| 14:35.34 | *** mode/#asterisk [+o rmudgett] by ChanServ |
| 14:36.42 | seanbright | from the asterisk console: rtp set debug on |
| 14:36.44 | seanbright | run another test |
| 14:38.33 | schangg | ok |
| 14:39.32 | schangg | https://hastebin.com/amepasicuq.makefile |
| 14:40.21 | schangg | or better this : https://hastebin.com/umelivutoy.makefile |
| 14:40.55 | *** join/#asterisk Grommish (~quassel@2600:2b00:932c:ff00:e848:977e:9e20:773b) |
| 14:48.05 | schangg | seanbright any ideas ? |
| 14:48.22 | Samot | 172.18.0.4 <-- What IP is that? |
| 14:48.23 | seanbright | i see no RTP at all |
| 14:48.35 | seanbright | Samot: the asterisk box |
| 14:49.05 | seanbright | so asterisk is not seeing the RTP that your phone is sending and therefore you have a firewall/nat problem |
| 14:49.24 | seanbright | seemingly unrelated to asterisk |
| 14:49.36 | Samot | I'm sure it's container related. |
| 14:51.32 | schangg | Samot ok, so because asterisk does not see my rtp traffic then it wont send any ? |
| 14:51.47 | schangg | the thing is that the tcpdymp capture is run from the docker that runs asterisk |
| 14:52.12 | schangg | so the traffic must be coming in if I see it from within the host (docker) that runs asterisk |
| 15:12.23 | *** join/#asterisk chendy (~alexc@120.229.53.102) |
| 15:35.48 | *** join/#asterisk MarcinWieczorek (~marcin@87-205-119-219.adsl.inetia.pl) |
| 15:41.46 | *** join/#asterisk forgotmynick (uid24625@gateway/web/irccloud.com/x-szizbjvsuordijni) |
| 16:09.24 | *** join/#asterisk drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 16:17.58 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 16:59.01 | *** join/#asterisk akp55 (~akp55@c-73-148-15-31.hsd1.va.comcast.net) |
| 17:07.39 | *** join/#asterisk Ai9zO5AP (~BQcdf9eiZ@gateway/tor-sasl/ai9zo5ap) |
| 17:35.38 | *** join/#asterisk Janos (~textual@201.204.94.76) |
| 17:46.33 | *** join/#asterisk paulgrmn (~paulgrmn@c-98-250-183-21.hsd1.mi.comcast.net) |
| 17:46.33 | *** join/#asterisk beardy (~beardy@unaffiliated/beardy) |
| 17:46.33 | *** join/#asterisk thansen (~thansen@192.74.130.86) |
| 17:46.33 | *** join/#asterisk yoavz (~yoavz@82.166.176.37) |
| 17:46.33 | *** join/#asterisk rolek (~rolek@D57D3382.static.ziggozakelijk.nl) |
| 17:46.33 | *** join/#asterisk javi404 (~quassel@unaffiliated/javi404) |
| 17:48.16 | *** join/#asterisk retentiveboy (~retentive@c-76-97-11-199.hsd1.ga.comcast.net) |
| 17:49.32 | *** join/#asterisk irrgit (~ch33se@192.241.175.183) |
| 18:24.14 | *** join/#asterisk drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 18:43.22 | *** join/#asterisk i9zO5AP (~BQcdf9eiZ@gateway/tor-sasl/ai9zo5ap) |
| 18:50.18 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 19:03.46 | *** join/#asterisk Jesterboxboy (~Thunderbi@84-115-150-8.cable.dynamic.surfer.at) |
| 20:28.21 | *** join/#asterisk spatel (~spatel@70-88-243-6-ma-nh-me-ne.hfc.comcastbusiness.net) |
| 20:31.42 | *** join/#asterisk overyander (~overyande@216.163.24.236) |
| 20:32.59 | *** join/#asterisk overyander (~overyande@216.163.24.236) |
| 20:33.27 | *** join/#asterisk overyander (~overyande@216.163.24.236) |
| 21:13.19 | *** join/#asterisk Typhon (~Typhon@dslb-088-066-099-079.088.066.pools.vodafone-ip.de) |
| 21:19.24 | *** join/#asterisk ledoktre (~textual@216.51.224.229) |
| 21:21.02 | ledoktre | Greetings all. Anyone in here aware of any "bugs" with parking with recent 17.x versions, like 17.6.x 17.7.x? Im having an issue thats been present at least on the latest 17.7 RC plus 17.6 where it does not announce parked call extensions. |
| 21:21.13 | ledoktre | Does not even attempt it, according to CLI output |
| 21:21.20 | file | did you try rc2? |
| 21:21.34 | ledoktre | I did not. I only did rc1 and then went back to 17.6 |
| 21:21.48 | file | there's a fix in rc2 |
| 21:22.04 | ledoktre | Hmm. thats music to my ears. specifically for parking issues? |
| 21:22.13 | file | specifically for that |
| 21:22.30 | ledoktre | AWESOME. I am glad to hear that. @file, pat on your back, virtually |
| 21:26.00 | Samot | This is just for a dev/sandbox machine right? |
| 21:26.41 | *** join/#asterisk andy09usa (~user@unaffiliated/andy09usa) |
| 21:27.07 | ledoktre | Samot: It was on a production machine. I have 17.6.0 on it. If you know of the latest version thats "safe" with this issue I can go that route too. I'd probably prefer it, I was just looking to try and figure out when the bug was introducted (what version) |
| 21:27.28 | Samot | 17.6 is the latest version. |
| 21:29.06 | ledoktre | Right. I just mean, I have 17.6.0 now, and its not playing the park extension message - so if the bug @file: mentioned was the culprit, I wonder whats the version prior to when the bug was introduced. Just poking around on the change log trying to figure it out |
| 21:29.39 | Samot | What version was it on previously? |
| 21:29.55 | ledoktre | Last version I had used was 17.4.x (not sure which subversion) |
| 21:30.06 | Samot | Was it an issue there? |
| 21:30.15 | ledoktre | I dont believe so? |
| 21:30.36 | Samot | OK because the last version of 17 I did was 17.3 and it worked fine. |
| 21:30.38 | file | 17.6.0 |
| 21:30.43 | file | er |
| 21:30.44 | file | 17.5.0 |
| 21:30.45 | *** join/#asterisk eppigy (~Dave@snugglenets.com) |
| 21:30.50 | eppigy | Hello |
| 21:30.52 | eppigy | I am Dave |
| 21:30.53 | Samot | Yup. |
| 21:31.07 | Samot | .5 or .6 would have been my guess on it being introduced. |
| 21:31.50 | Samot | I would roll back to 17.4 and wait. |
| 21:32.04 | file | if all goes well I'll be doing the releases on Thursday |
| 21:32.05 | Samot | I would not run RC in production if that can be avoided. |
| 21:32.06 | ledoktre | Wait until 17.7.0 is out of RC? |
| 21:32.19 | Samot | Correct. |
| 21:32.23 | Samot | It works in 17.4 |
| 21:32.30 | ledoktre | ok. |
| 21:32.30 | Samot | You were just updating to be current. |
| 21:32.36 | ledoktre | correct |
| 21:32.37 | Samot | Not for a specific reason. |
| 21:32.50 | Samot | Roll back, wait for the full release which has the fix. |
| 21:32.58 | ledoktre | No one caught it right away, so I can only say it happened since the last update. |
| 21:33.07 | ledoktre | I can do that. Thank you ! |
| 21:34.52 | ledoktre | How does 13.35.0 line up with 17? What version i mean. I see on the bug report it was introduced in 13.35.0. Im working on 17.4 now but just curious. |
| 21:39.34 | file | releases occur at the same time |
| 21:39.46 | file | 13.35.0, 16.12.0, and 17.6.0 were all released at the same time |
| 21:39.53 | file | and any applicable bug fixes would be in all of them |
| 21:40.34 | ledoktre | That was exactly what I was asking. I was curious what version 13.35.0 corresponded to. You just said 17.6, so in theory 17.5 ought to be fine. Im compiling 17.4 now was just curious. |
| 21:40.37 | ledoktre | Thanks |
| 21:41.05 | file | it's not that... simple... |
| 21:41.31 | file | but yes, I believe 17.5.0 is fine in regards to the parking issue |
| 21:42.43 | ledoktre | Thats why I was asking. I understand that all 3 must share some common code. More than anything I was just curious when (in the 17 branch) the bug was introducted. Im sure it is a lot more to it than as simple as I worded it. Curiousity.... cat.. you know |
| 21:43.16 | ledoktre | Im just sticking 17.4 back on irregardless was just a point of curiousity i guess |
| 21:58.24 | ledoktre | @file: 17.4.0 did resolve it BTW. Im sure you probably knew that, but Im confirming it. Thanks @file: and Samot: for the heads up on the bug. |
| 22:03.10 | *** join/#asterisk pppingme (~pppingme@unaffiliated/pppingme) |
| 22:23.32 | *** join/#asterisk akp55_ (~akp55@c-73-148-15-31.hsd1.va.comcast.net) |
| 22:53.25 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
| 22:59.53 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
| 23:01.14 | *** join/#asterisk pchero (~pchero@2a02:a210:2241:6480:7db8:620c:b98c:a791) |
| 23:05.14 | *** join/#asterisk n0tiz (~n0tiz@82-69-15-38.dsl.in-addr.zen.co.uk) |
| 23:35.42 | *** join/#asterisk Oatmeal (~Suzeanne@ip68-4-181-8.oc.oc.cox.net) |
| 23:36.45 | *** join/#asterisk Oatmeal (~Suzeanne@ip68-4-181-8.oc.oc.cox.net) |