Eric Einstein

Well I answered it. For anyone interested: apt-get install apt-transport-https lsb-release ca-certificates wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg

That was an older install. Now with a new install using the latest image file I get this: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php buster InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <deb@sury.org> W: Failed to fetch https://packages.sury.org/php/dists/buster/InRelease The following signatures were invalid:...

Anyone?

This is what I get when running rapbx-upgrade. Any ideas what this means? Is it my end or on the repository end, and what's the fix? root@raspbx:/etc/apt/sources.list.d# raspbx-upgrade RasPBX upgrade tool Run "raspbx-upgrade --help" for additional options Base version: 11-11-2019 Installed upgrade: 29 Local upgrade available: 29 Online upgrade available: 29 Checking repositories for updated packages... Hit:1 https://packages.sury.org/php buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian...

I'm wondering if Asterisk 18 is supported and if so, how to upgrade from 16 to 18? Or will it simply be included in raspbx-upgrade once it has been tested and confirmed stable?

Crazy. I was beating my head with this for an hour. Thanks. It would be nice if the loopback was disabled

I'm having a similar issue. Only multiple presses of the same button eventually "wake" lirc to the point where it is recognizing button presses correctly. Based on the logs (pared down and attached) it can't match to the remote unless it's in the "woken" state.Maybe something to do with the header, the pre and the pre_data settings, but I'm fairly lost about how to troubleshoot this from here. My .conf file is downloaded from the lirc archive (attached) and was working on a previous installation...