Package Details: asterisk 22.3.0-1

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.065008
First Submitted: 2008-01-27 13:42 (UTC)
Last Updated: 2025-04-01 00:02 (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

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 24 Next › Last »

emersonjr commented on 2019-01-30 16:38 (UTC)

It seems there's problem again with pjproject 2.8

checking for RAII support... checking for gcc -fnested-functions... no
checking for clang strsep/strcmp optimization... no
checking for embedded pjproject (may have to download)... configuring
[pjproject]  Downloading https://raw.githubusercontent.com/asterisk/third-party/master/pjproject/2.8/pjproject-2.8.tar.bz2 to /tmp/pjproject-2.8.tar.bz2
[pjproject]  Retrying download
[pjproject]  Downloading https://raw.githubusercontent.com/asterisk/third-party/master/pjproject/2.8/pjproject-2.8.tar.bz2 to /tmp/pjproject-2.8.tar.bz2
make: *** [Makefile:90: /tmp/pjproject-2.8.tar.bz2] Error 4
make: *** Deleting file '/tmp/pjproject-2.8.tar.bz2'
failed
configure: Unable to configure third-party/pjproject
configure: error: Re-run the ./configure command with 'NOISY_BUILD=yes' appended to see error details.
==> ERRO: Uma falha ocorreu em build().
    Abortando...

How can it be solved?

DragonX256 commented on 2018-12-29 11:12 (UTC)

Fixed problems which were described by @jeremyvisser.

nimbius commented on 2018-12-21 15:48 (UTC)

the systemd service type for asterisk needs to be changed to basic. notify type causes errors when executing the dialplan application System() with bash redirections, or dialplan variables.

in addition, executed System() calls can report success when unable to create a file on the system.

jeremyvisser commented on 2018-12-19 11:07 (UTC) (edited on 2018-12-19 11:08 (UTC) by jeremyvisser)

When I try to install the package, I get these errors:

chown: invalid user: ‘asterisk:asterisk’ chown: invalid user: ‘asterisk:asterisk’ chown: invalid user: ‘asterisk:asterisk’ chown: invalid user: ‘asterisk:asterisk’ chown: invalid user: ‘asterisk:asterisk’ error: command failed to execute correctly

I suspect this is because the post-install script is executed before the sysusers.d configuration is loaded.

Also, I noticed the post-remove script does a "killall -q asterisk". However, it's possible to get Asterisk to spawn subprocesses, so it would be better to do a "systemctl stop asterisk.service" in the post-remove script instead.

br3schweiz commented on 2018-10-29 21:50 (UTC) (edited on 2018-10-30 09:52 (UTC) by br3schweiz)

if you sideloaded opus-support from Digium, remember to update it too. Otherwise you'll get a segfault and won't be able to start asterisk again (what, for whatever reason doesn't happen with 16.0.0-rc3)...

post-factum commented on 2018-10-09 18:44 (UTC)

FYI, starting from 16.0.0 Asterisk requires libedit.

post-factum commented on 2018-09-08 15:31 (UTC)

systemd .service file can be used from the contrib folder now. Also, I'm not sure why termcap is needed.

Next, it seems, it won't work with pjproject v2.8, so it would be better to switch to bundled one.

Also, consider using sysusers feature to avoid creating users manually in the post-inst hook.

linuxuserarch commented on 2018-09-06 20:55 (UTC)

Since downloads.asterisk.org supports TLS, might be sensible to switch PKGBUILD source to "https://downloads.asterisk.org/pub/telephony/asterisk/releases/${pkgname}-${pkgver}.tar.gz".

alerque commented on 2018-02-28 07:29 (UTC) (edited on 2018-02-28 07:31 (UTC) by alerque)

That's an interesting idea @bberlin, if I'd manually compiled it at some point and left scraps on the system I could see that happening, but I've tested this on systems that didn't have asterisk and wouldn't have ever had libsrtp and am getting the same results.

Here is from my production Asterisk server:

❯❯❯ find /usr/lib -iname '*srtp*' -exec pacman -Qo {} \;
/usr/lib/libsrtp2.a is owned by libsrtp 1:2.1.0-1
/usr/lib/libsrtp2.so.1 is owned by libsrtp 1:2.1.0-1
/usr/lib/pkgconfig/libsrtp2.pc is owned by libsrtp 1:2.1.0-1
/usr/lib/libsrtp2.so is owned by libsrtp 1:2.1.0-1
/usr/lib/asterisk/modules/res_srtp.so is owned by asterisk 15.2.0-1

I don't see anything amiss there do you?

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 24 Next › Last »