Asterisk And CentOS 8
At the current time, we do not recommend attempting to build Asterisk on CentOS 8. Many packages Asterisk uses are not yet available and would require building from their sources. The Asterisk packages are also not available in the EPEL 8 or CentOS 8 repositories yet for the same reason.
We’ll update you when we think it’s safe.
5 thoughts on - Asterisk And CentOS 8
They only problem I have found so far is while trying to install Alembic for SQLAlchemy (for realtime configs). Those are the only packages that I cannot get working properly. Vanilla Asterisk works fine with the only extra package needed being libedit-devel that is not included in any “official” repo. You need to download the Fedora Core
29 packages to in order to successfully compile Asterisk. That being said, I would not recommend trying to put this in production any time soon.
Hello George, Hope this finds you well!
I wonder if there has been any progress on this matter?
I’ve been working to have Asterisk running on CentOS 8 and our jump from CentOS 6 to 8 doesn’t look too bad…. The missing packages found are:
gmime-devel, iksemel-devel, corosynclib-devel, libresample-devel, hoard and python-devel. Python-devel could be replaced by python2-devel or python3-devel (python36-devel), but I am not sure if there is any python incompatibility… gmime-devel, iksemel-devel and hoard seems of no use
(and they were already missing for CentOS 6 too), so only corosynclib (if you are using it) and libresample may be a problem…. Does anyone knows what is the use of libresample-devel package?
Just to share the experience so far, to build Asterisk it is needed to install the epel-release and enable PowerTools. By ignoring the missing packages, the compilation works and we can start Asterisk. My only concern was about the libresample-devel because in the past I think its absence caused issues when loading/starting pjsip modules, but it didn’t happen this time (but I am not using pjsip, I just loaded it with the sample config files)…. Following on and making Asterisk a systemd service instead of using init.d, I first checked the service file under contrib/systemd but it seems to serve a different purpose, so it could not be used. Instead a very simple one does the job. Just make sure your exec cmd does not have the ‘-c’
option (used in safe_asterisk), because this was causing me a 100% CPU
usage (related to this:
https://unix.stackexchange.com/questions/191621/systemd-service-using-100-of-my-cpu-when-it-doesnt-if-i-start-it-without-syste/368037#368037
)
Be aware that SELinux may cause permissions and access problems when running as systemd service…. It took me a whole day to figure out that under our configuration (that have included files outside the /etc/asterisk folder) the “problem” was SELinux. Finally, configure firewalld to allow the SIP and RTP ports and you should be ready to go. Also, we are using rpmbuild to create an Asterisk package. rpmbuild (or new red hat policies) is more strict and now complains about the python shebangs that do not have a version (files contrib/script/ref*.py -> what is this used for??). When using the DONT_OPTMIZE flag the compiler warns for every single file saying, so it is quite annoying but does not to cause issues:
/usr/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]. Anyway, these problems do not happen if you manually build with the simple configure and make commands.
Cheers, Patrick Wakano
–000000000000a44aa205a55faa83
Content-Type: text/plain; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable
Sorry, I missed this last week. We have an internal issue open to revisit CentOS 8 and it’s at the top of our backlog right now so we should have something in the next few weeks.
Thanks for sharing your experience!
–0000000000003b4ac805b61061cf Content-Type: text/plain; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable
In case anyone out there is working with CentOS, you might reconsider that decision: https://blog.CentOS.org/2020/12/future-is-CentOS-stream/
–0000000000003b4ac805b61061cf Content-Type: text/html; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable
–0000000000003b4ac805b61061cf
10.12.2020 03:25, Patrick Wakano пишет:
—