| Git Clone URL: | https://aur.archlinux.org/asterisk.git (read-only, click to copy) |
|---|---|
| Package Base: | asterisk |
| Description: | A complete PBX solution |
| Upstream URL: | https://www.asterisk.org |
| Keywords: | sip, telephony, voip |
| Licenses: | GPL-2.0-only |
| Submitter: | pressh |
| Maintainer: | nkukard (alerque) |
| Last Packager: | nkukard |
| Votes: | 112 |
| Popularity: | 0.046397 |
| First Submitted: | 2008-01-27 13:42 (UTC) |
| Last Updated: | 2024-10-18 07:11 (UTC) |
@fs_developer I'm using the repo from alerque and both systemd and systemd-libs are installed:
alerque/asterisk 19.3.1-1 [installed] A complete PBX solution alerque/asterisk-g729 1:1.4.3.r4.3855cec2ef26-3 [installed] G.729 codec for Asterisk open source PBX
core/systemd 251.2-1 [installed] system and service manager core/systemd-libs 251.2-1 [installed] systemd client libraries
So, it must be something else that's missing... question is how can I narrow this down?
@Marc_Eberhard I had the same problem when building in a clean chroot without systemd and systemd-libs package installed. The asterisk autoconfig script tries to detect if systemd is installed and only enables systemd-notify support if it is found at buildtime. Maybe it would be better to add systemd to the list of dependencies.
It seems that Type=notify in /usr/lib/systemd/system/asterisk.service is not working properly. I see the Asterisk process being restarted every 90 seconds. Changing it to type simple solves the issue. I'm running Asterisk as user asterisk, e.g. not as root, which might be the reason notify isn't working for me, but I'm not a systemd expert... Would it make sense to change to type simple instead of notify or am I doing something really stupid and it should work?
@ectospasm I took a quick look and there are some good suggestions, I'll see what I can do.
I've been developing asterisk-lts-18, which is based on this asterisk PKGBUILD. The first comment on my post from loqs suggests some changes to improve the PKGBUILD.
I realize that this package has been maintained since 2008, so it is very likely to contain some very old ways of doing things. Before I go hacking up my PKGBUILD, I wanted to get the opinions of the maintainers/contributors of this asterisk PKGBUILD.
@nkukard fair enough, it's fine in isolation and/or if you know what you're doing (and I think modules conf still has noload by default) but I understand, thanks
@jwh You're more than welcome to adjust your copy of the PKGBUILD, but I do not think this is in the best interest of the users of this package. chan_sip was deprecated due to having no maintainer (as the deprecation message said since 17.0). This poses a grave security risk (if you keep up with the changelog you will see). I am not comfortable enabling it, sorry.
Any chance you can add --enable chan_sip? Some of us still live in the past and/or have issues with pjsip, but its disabled by default in 19
You have a good idea there. I think "asterisk-lts-18" would be the best naming scheme. Generally I'd say people would use the LTS version for long term support of other software and integrations (I certainly would), they may not want a major version change in the case of "asterisl-lts" and then have to figure out how to install the previous version. Lets see if alerque has any input.
What are the plans when Asterisk 20 is released, sometime around the third week of October, 2022? I've modified the main asterisk PKGBUILD to use Asterisk 18 (the current LTS version), but I haven't published it yet. I'm calling my package asterisk-lts, but when 20 is released I'd think that asterisk would be the LTS release. I'd think that the asterisk-lts package would be renamed asterisk-lts-18 or something similar when Asterisk 20 LTS is released. The asterisk package would be 20 until 21 is released, sometime in October 2023 if I'm reading https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions correctly.
I don't want to step on any toes by submitting my asterisk-lts PKGBUILD, it looks like a lot of work has gone into the asterisk PKGBUILD, and I've merely modified it to work with Asterisk 18 LTS.
Pinned Comments
alerque commented on 2020-02-22 06:10 (UTC) (edited on 2020-02-22 06:34 (UTC) by alerque)
PSA: I've started hosting this and all its dependencies as prebuilt packages (x86_86 only) in my repository for those that want to install them using
pacmanwithout messing around with building from the AUR.