Package Details: asterisk 19.6.0-1

Git Clone URL: (read-only, click to copy)
Package Base: asterisk
Description: A complete PBX solution
Upstream URL:
Keywords: sip, telephony, voip
Licenses: GPL
Submitter: pressh
Maintainer: nkukard (alerque)
Last Packager: nkukard
Votes: 111
Popularity: 0.012231
First Submitted: 2008-01-27 13:42 (UTC)
Last Updated: 2022-09-28 09:26 (UTC)

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 pacman without messing around with building from the AUR.

Latest Comments

1 2 3 4 5 6 .. 23 Next › Last »

Astroturf commented on 2022-06-11 18:28 (UTC) (edited on 2022-06-11 18:28 (UTC) by Astroturf)

Since Asterisk 19 the log file has been renamed to "messages.log". Logrotate should be updated accordingly.

diff --git a/asterisk.logrotated b/asterisk.logrotated
index f03d0ac..4bf367b 100644
--- a/asterisk.logrotated
+++ b/asterisk.logrotated
@@ -1,4 +1,4 @@
-/var/log/asterisk/*_log /var/log/asterisk/messages {
+/var/log/asterisk/*_log /var/log/asterisk/messages.log {
   create 640 asterisk asterisk

Marc_Eberhard commented on 2022-06-07 07:36 (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?

fs_developer commented on 2022-06-07 06:08 (UTC)

@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.

Marc_Eberhard commented on 2022-06-06 15:58 (UTC)

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?

nkukard commented on 2022-05-27 13:38 (UTC)

@ectospasm I took a quick look and there are some good suggestions, I'll see what I can do.

ectospasm commented on 2022-05-27 01:52 (UTC)

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.

jwh commented on 2022-04-19 13:29 (UTC)

@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

nkukard commented on 2022-03-30 02:50 (UTC)

@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.

jwh commented on 2022-03-29 15:09 (UTC)

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

nkukard commented on 2022-03-27 09:02 (UTC)

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.