Arch Linux User Repository

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.

Since Asterisk 19 the log file has been renamed to "messages.log". Logrotate should be updated accordingly.
https://github.com/asterisk/asterisk/blob/master/UPGRADE.txt#L25

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
   compress
   missingok

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

Fix for broken PKGBUILD

diff --git a/PKGBUILD b/PKGBUILD
index 28df614..c106727 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -163,7 +163,7 @@ build() {
        --prefix=/usr \
        --sysconfdir=/etc \
        --localstatedir=/var \
-       --sbindir=/usr/bin \
+       --sbindir=/usr/bin
    make menuselect.makeopts
    ./menuselect/menuselect --disable BUILD_NATIVE
    make

@nimrod_mack Those files serve as both the examples and as the default config. It's pretty standard on Arch to dump default configs in place. Instead of just deleting them (which as you note just means they come back) you should edit them to your liking. For the ones you don't want to load change the import commands or blank them out, but keep them in place. That way pacman will handle the configs using the backup mechanism and prompt you to handle pacnew files for any that changed (and only ones that changed) since the last package update.

@alerque Currently, this package installs example configurations files in /etc/asterisk. As I don't need many of the modules, I also delete many of these files again. They would be installed again during upgrades, though. Therefore, I usually modify the PKGBUILD to install the provided config files to /usr/share/doc/asterisk/examples instead.

@tosie That patch does look useful, but per Arch packaging guidelines adding features & fixing bugs is something we try to avoid in packages except for urgent security things or if something won't actually build or run without the fix. That patch looks like something you need to submit upstream for inclusion. Please consider doing that so everybody can benefit.

I'll look into the imap voicemail app.

In my own build I usually add the two things below. Maybe that would be helpful for others.

• Make queues support the device state "BUSY" (see diff regarding app_queue.c, applied via patch -Np1 < "${srcdir}/12-app_queue.c.patch" in the prepare() function of PKGBUILD)
• Enable app_voicemail_imap (via ./menuselect --disable BUILD_NATIVE --enable app_voicemail_imap, depends on c-client)

--- $pkgname-$pkgver/apps/app_queue.c
+++ $pkgname-$pkgver/apps/app_queue.c
@@ -2323,6 +2323,13 @@
                break;
            }
            goto default_case;
+       // This has been added as this device state is reported by PJSIP when a device is in a call.
+       case AST_DEVICE_BUSY:
+           if (conditions & QUEUE_EMPTY_INUSE) {
+               ast_debug(4, "%s is unavailable because his device state is 'busy'\n", member->membername);
+               break;
+           }
+           goto default_case;
        case AST_DEVICE_RINGING:
            if (conditions & QUEUE_EMPTY_RINGING) {
                ast_debug(4, "%s is unavailable because his device state is 'ringing'\n", member->membername);

By the way, get your votes in on your favorite asterisk codec packages on the AUR too, if licenses are in order I might be able to bring in some of those to [community] as well but having more votes on the packages helps justify the move.

I'm going to track this package for migration to the official [community] repositories. If anybody knows anything that should be done differently for prebuilt packages please speak up now, it's easier to iterate here before it moves than after.

The biggest change for those of you with this in production will probably be the location of temporary files to fit better with official systemd stuff.

@nkukard I'll be tweaking the coding style a bit prior to moving — not to step on your toes (I try to match style when I'm co-maintainer) but since it will be my responsibility in the official repos I'll use my style.

@JerryXiao Can you confirm that it is possible to build asterisk on a system without gsm and later use it with the gsm module working on a system that does have the dependency?

"gsm" is not a makedep, it is at least a optdepend as it is required for the asterisk gsm module to work.

@C0rn3j Thanks for the extra feedback, and I think I agree with your conclusion.

I am not familiar with anything Asterisk, but building chan_mobile adds 0.12MB to the package.

But it probably requires some BT dependencies. And unfortunately does not work with Bluez 5, it has to be ran in --compat mode for Bluez 4 stuff to work.

I am not sure how useful it would be to others, but I would be certainly be grateful if I didn't have to keep rebuilding from my own PKGBUILD, but if it adds a hard BT dependency, maybe it's not the best idea since I assume chan_mobile is a fringe use case.

@C0rn3j Thanks for the info, hopefully it helps somebody. Out of curiosity (since I'm not familiar with it), is chan_mobile perhaps something we should be enabling by default?

make menuselect does not work on zsh for whatever reason (does not affect packaging, just when trying to configure things manually), had to switch to bash temporarily

I wanted to build/compile chan_mobile.so, and for that I had to add

./menuselect/menuselect --enable chan_mobile below the existing menuselect line.

Hope this helps someone.

Many plugins have additional dependencies not listed here - is there a specific reason those are not included as depends/optdepends? I had to install libvpx gsm lua53 neon to get the modules I need running.

I guess, lua51 can therefore be dropped as it seems they have switched to lua53. Also, gsm is already listed as a makedepends, but is (at least in my case) also needed for running it.

@brackenhill-mob Upon further investigation it seems like archlinux c-client does not include imap/linkage.c. You can manually build a package that includes it like this (maybe the paths might not be right, but you should be able to follow along):

mkdir -p ~/builds
cd ~/builds
git clone --single-branch -b packages/imap https://github.com/archlinux/svntogit-packages.git ~/builds/c-client
cd ~/builds/c-client/trunk
# Add the following line to PKGBUILD at the end of the `package_c-client` function:
# install -D -m644 c-client/c-client.a $pkgdir/usr/lib/c-client.a
makepkg
sudo pacman -U c-client-2007f-*.tar.xz

The last line installs the newly build package including the linkage.c file.

I had to change the PKGBUILD of the asterisk package, too:

Replace

./menuselect/menuselect --disable BUILD_NATIVE

with

./menuselect/menuselect --disable BUILD_NATIVE --enable app_voicemail_imap

I guess as long as getting imap/linkage.c is a manual process it won't be possible for the asterisk package to officially enable the IMAP support.

This has been added as a bug report: https://bugs.archlinux.org/task/69016

@brackenhill-mob You might want to try the c-client package. It includes imap/linkage.h.

@nkukard I "borrowed" linkage.c from my Ubuntu server - I now have a working build. I can't find which package contains this file on Ubuntu - many moons ago it was in the uw-imap source code from Uni of Washington but I could find their repository to download it.

@brackenhill-mob You have a very good point there, I wrongly assumed just enabling imap support with --with-imap=system sorted it out :(

I get the same build error as you, missing imap/linkage.c

@nkukard OK I've just looked at my scripts for Ubuntu. --with-imap=system is required.

But my build fails with a missing /usr/lib/imap/linkage.c which is not in the c-client nor imap packages (it exists in Ubuntu).

Please can you set app_voicemail_imap in menuselect and try your build to see if it completes.

@nkukard I downloaded the snapshot for 18.1.0-2 as it hadn't hit the repositories at the time, and app_voicemail_imap is not checked in menuselect so the .so is still not being built

HTH

@nkukard I'm new to running Asterisk under Arch (coming from Ubuntu Server) so I may not understand how the Arch system works in this case. So at the risk of telling you stuff you already know... ;)

The 3 voice mail options if you run make menuselect manually create 3 different .so files. With your 18.1.0 package, only app_voicemail.so was created but the /etc/asterisk/modules.conf file told the server to load app_voicemail_imap.so which didn't exist. I've always built Asterisk from source and used make menuselect to setup the system for my needs, so in this case I would check all 3 options to generate the 3 .so files and let the user decide what to load in modules.conf. If you check those settings do you need a build dependency?

HTH

@Astroturf, thanks for the link. Updated to use bundled version.

@brackenhill-mob, please see https://www.asterisk.org/announcing-a-new-compile-option-for-app_voicemail-storage/. As far as I can see "imap" was never a build dependency, nor could of of worked due to the imap linking issue. Nonetheless, I've added imap as a build dep and fixed the linker options. Not sure I like it though. Willing to take improvement suggestions.

Agree with @Astroturf re pjproject (especially as it would not compile for me!).

So I downloaded v18.1 from your repository and you appear to have compiled the wrong app_voicemail - I've got app_voicemail.so when it should be app_voicemail_imap.so.

If you've renamed the .so file for some reason, then /etc/modules.conf is wrong.

TIA

What is the reason the bundled version of pjproject is not used? It is the recommended default since Asterisk 15. Asterisk crashes for me when using the pjproject dependency. It works just fine when removing --with-pjproject-bundled=no from PKGBUILD. The bundled version of pjproject also has a very specific config_site.h & a few extra patches (https://github.com/asterisk/asterisk/tree/master/third-party/pjproject/patches).

I post here but it's not because of the package upload here it's more the asterisk source related, if it can help someone .

checking for pkg-config... no
checking for LIBEDIT... no
checking for history_init in -ledit... no
configure: error: *** Please install the 'libedit' development package.
==> ERROR: A failure occurred in build().
Aborting...
error making: asterisk


But i install # git sudo binutils make gcc fakeroot wget patch libedit gettext

in reality without the package ' pkg-config ', the compilation fail and say

' Please install the 'libedit' development package '

Maybe i do something wrong, but the error message is misleading

@caleb afaik sadly they are not. The use the "DIGIUM END-USER LICENSE AGREEMENT ". I think this is also why they do not just bundle them with asterisk per default but download them every time you build it.

@hytrax If the extra files are GPL licensed we could add them to the package sources array, place them where they need to be as part of prepare(), then build.

After some searching around, I found: a) Asterisk support Opus upstream. b) when one uses the graphical menuconfig to select Opus support it the downloads some files necessary from Digium. If you download those files for a normal installation and put them in the appropriate places then Opus works (that is what I did) c) no menuselect.makeopts flag I could find made it download the files while building. At least, none that I found.

I might look into this more at a later point in time.

@hytrax Does upstream Asterisk support opus transcoding at all? If so there may be an extra option that needs to be set at build time. I'm happy to consider adding it if it doesn't incur more dependencies than the default. Let me know if you figure out what it is.

@caleb I have built it with the PKGBUILD and Opus passthrough support seems to be there but it cannot transcode from, say, G.722 to Opus. "core show translation" does not list it.

@hytrax The build in my user repository is compiled with the PKGBUILD exactly as posted here (most recently updated by me). There is a dependency on opus so I would have expected it to be found at build time and support to be built in. Do you get something different when you build this PKGBUILD yourself?

It's possible they changed something in recent releases and we need to explicitly enable support now, but I missed anything about that in the change logs.

Is it not compiled with opus enabled? If I use the package form the alerque repo the opus modules are missing and thus transcoding does not work.

@post-factum Thanks for the heads up. It's building now, if it looks like it runs alright I'll post the update shortly.

Thanks for the heads up @Thulinma, updated package coming shortly.

Hey there! Asterisk no longer installs headers by default, but dependent packages expects them to be installed. To re-enable headers, simply add the line:

make DESTDIR="${pkgdir}" install-headers

after the existing line

make DESTDIR="${pkgdir}" install

And that'll do the trick.

@nkukard Have you ever messed with fixing this build so it works with Lua 5.3 instead of 5.1? Asterisk supports it, their configure.ac just detects it in the wrong order. I messed with patching it some but didn't get it quite working. I wondered if you'd tried to go down that road before.

I've not tired that myself, I'd prefer to stick with what Asterisk detects, but as you say its in the wrong order, so I think it should be fine to change it if you want.

Also I don't think that should be an optdepend because it cannot be added or removed by installing Lua after the fact, it has to be build in, which means it has to be there at build time. I think it should be a makedepend, and the Arch configuration should just support it out of the box. This is consistent with the way many many other packages that optionally have Lua support handle are handled. Would you mind if I flip that around like that?

Agreed, feel free to flip that around :)

@nkukard Have you ever messed with fixing this build so it works with Lua 5.3 instead of 5.1? Asterisk supports it, their configure.ac just detects it in the wrong order. I messed with patching it some but didn't get it quite working. I wondered if you'd tried to go down that road before.

Also I don't think that should be an optdepend because it cannot be added or removed by installing Lua after the fact, it has to be build in, which means it has to be there at build time. I think it should be a makedepend, and the Arch configuration should just support it out of the box. This is consistent with the way many many other packages that optionally have Lua support handle are handled. Would you mind if I flip that around like that?

Thanks for the add @nkukard. I've also added you to pjproject as it is the only other required dependency for this that is in the AUR. That way any future absence I make have won't hold up updates to this package ;-)

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.

@nkukard Would you consider adding me as a co-maintainer on this. I was the maintainer at some point until a period of extended travel where I wasn't around to bump it got it orphaned. I am the maintainer of pjproject (which this depends on) and I would now like to start hosting prebuild x86_64 packages for asterisk in my package repository. It would be nice to be able to bump this and fix issue without having to keep a fork around and possibly having miss-matches between the version in my repository and the AUR.

@isundil, can you perhaps post the error you're getting?

Hello,

There is a missing dependency reference to community/bcg729

Hi,

Here's a patch:

0001-Fix-most-illegal-instructions-when-shipping-asterisk.patch:

From 0b8eb034c73e858af14db5b9b3dd28da9114bd6d Mon Sep 17 00:00:00 2001
From: Denis 'GNUtoo' Carikli GNUtoo@cyberdimension.org
Date: Tue, 8 Jan 2019 16:00:50 +0100
Subject: [PATCH] Fix most illegal instructions when shipping asterisk.

While this works in AUR, because users are building the PKGBUILD,
distributions wanting to use this PKGBUILD as-is and ship packages
produced with it will result in illegal instructions at runtime.
Without that fix, if you build this packages on a machine with
a processor that supports avx (Advanced Vector Extensions),
libpjsip.so.2 ended up with vpxor instructions that were also
executed on machines with a processor that did not have such
extension, which resulted in an illegal instruction at asterisk
startup if the machine running it didn't have AVX.
Though for some reason, with this patch, building asterisk on a
machine with avx still results in res_pjsip_send_to_voicemail.so
having one vpxor instruction.
Hopefully even with that, asterisk can still start on machines
that do not have AVX.
To fix most illegal instructions:
- Native builds were disabled by using the ChangeLog documentation:
  "Those who need different -march= values, please, go for
   ./configure
   make menuselect.makeopts or make menuselect
  ./menuselect/menuselect --disable BUILD_NATIVE"
- The build configuration was changed to use an external
  pjproject library. The AUR PKGBUILD for pjproject also
  had several fixes to prevent it from causing illegal
  instructions.
On x86_64 I verified that most asterisk ELF files did not
have vpxor instructions anymore with:
  $ pacman -Q -l asterisk | \
                 awk '{print $2}' | xargs file | grep ELF | \
                 sed 's#:.*##' | xargs objdump -D | grep vpxor
Signed-off-by: Denis 'GNUtoo' Carikli GNUtoo@cyberdimension.org
PKGBUILD | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/PKGBUILD b/PKGBUILD
index d2fa84e..037bdcd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,10 +3,11 @@
 # Contributor: Xavier Devlamynck magicrhesus@ouranos.be
 # Contributor: Alessio Biancalana dottorblaster@gmail.com
 # Contributor: Maik Broemme mbroemme@libmpq.org
+# Contributor: Denis 'GNUtoo' Carikli GNUtoo@cyberdimension.org
pkgname=asterisk
 pkgver=16.4.0
-pkgrel=1
+pkgrel=2
 pkgdesc="A complete PBX solution"
 arch=('i686' 'x86_64' 'aarch64' 'armv7h')
 backup=('etc/asterisk/acl.conf'
@@ -120,7 +121,7 @@ backup=('etc/asterisk/acl.conf'
         'etc/asterisk/xmpp.conf')
 url='http://www.asterisk.org'
 license=('GPL')
-depends=('alsa-lib' 'speex' 'popt' 'libvorbis' 'curl' 'libxml2' 'jansson' 'libxslt' 'opus' 'libedit')
+depends=('alsa-lib' 'speex' 'popt' 'libvorbis' 'curl' 'libxml2' 'jansson' 'libxslt' 'opus' 'libedit' 'pjproject')
 makedepends=('sqlite3' 'gsm')
 optdepends=('lua51' 'libsrtp' 'postgresql' 'unixodbc' 'libpri' 'libss7' 'openr2' 'iksemel' 'radiusclient-ng' 'dahdi')
 install=${pkgname}.install
@@ -135,7 +136,9 @@ sha256sums=('d870711299089d0b1f01708534b0e139c4e83d828cbb79dfc90ec59774be83fa'
build() {
   cd ${pkgname}-${pkgver}
-  ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --sbindir=/usr/bin
+  ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --sbindir=/usr/bin --with-pjproject-bundled=no
+  make menuselect.makeopts
+  ./menuselect/menuselect --disable BUILD_NATIVE
   make
 }
-- 
2.21.0

@tigran pkgconf lies in base-devel group. You should have installed this group in order to build packages from AUR.

A weird error in build macros: it gives message demanding libedit, while really it needs pkgconf.

You get that "please install libedit development package" configure message, you install it, and still keep getting the same message each time you try to build *, and you get driven crazy.

Just installing pkgconf sets the things.

@emersonjr @Thulinma I've tested 16.2.0 building in clean chroot. pjproject builts correct, and there's no dependency on uriparser for asterisk.

Hi! It looks like "uriparser" is an unlisted dependency.

Just insert the following command sed -i 's/,5,/,10,/g' third-party/Makefile.rules into PKGBUILD above the ./configure ... line, which succesfully corrects the problem.

The file should now be like below:

build() {
  cd ${pkgname}-${pkgver}
  sed -i 's/,5,/,10,/g' third-party/Makefile.rules
  ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --sbindir=/usr/bin
  make
}

Please @DragonX256 do the amendments

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?

Fixed problems which were described by @jeremyvisser.

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.

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.

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

FYI, starting from 16.0.0 Asterisk requires libedit.

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.

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

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?

@caleb, it is possible to have both versions of libsrtp installed, the latest gets installed as libsrtp2. Check /usr/lib and see if you have both. You may already have the older one from something else.

@bberline Thanks for responding, but I'm more mystified than before. I have not tried with libsrtp0 because none of the errors I'm getting seem to be related to that at all, but I have libsrtp-1:2.1.0-1 (from the extra repo, I'm assuming this is also the one that doesn't work for you) and that does work for me. Also I've tried with and without bcg729.

@caleb, I was able to get it to compile with your argument after installing libsrtp0 from AUR. Looks like it wants libsrtp version 1.x on there like @albertvaka says and doesn't need the latest 1:2.1.0. I hadn't noticed his comment before. I have pjproject 2.7.1-1 like you and I do not have bcg729 installed, not sure why you wouldn't be able to compile the other way.

@bberlin and @d9jWbb42kC3 just a thought, what versions of pjproject do you have installed when you tried and failed to build the way I have this packaged? Maybe a version needs to be added to that dependency. I've got pjproject 2.7.1-1 out of the current AUR.

@bberlin and @d9jWbb42kC3 I am following your comments but unsure what to do here. I have tried and tried again to compile this package without that flag and can't do it across any of my 4 systems. I get this error:

   [LD] abstract_jb.o acl.o adsi.o alaw.o alertpipe.o aoc.o app.o ast_expr2.o ast_expr2f.o asterisk.o astfd.o astmm.o astobj2.o astobj2_container.o astobj2_hash.o astobj2_rbtree.o audiohook.o autochan.o autoservice.o backtrace.o bridge.o bridge_after.o bridge_basic.o bridge_channel.o bridge_roles.o bucket.o callerid.o ccss.o cdr.o cel.o channel.o channel_internal_api.o chanvars.o cli.o codec.o codec_builtin.o config.o config_options.o conversions.o core_local.o core_unreal.o crypt.o datastore.o db.o devicestate.o dial.o dns.o dns_core.o dns_naptr.o dns_query_set.o dns_recurring.o dns_srv.o dns_system_resolver.o dns_test.o dns_tlsa.o dnsmgr.o dsp.o endpoints.o enum.o event.o features.o features_config.o file.o fixedjitterbuf.o format.o format_cache.o format_cap.o format_compatibility.o frame.o framehook.o fskmodem.o global_datastores.o hashtab.o heap.o http.o image.o indications.o io.o iostream.o jitterbuf.o json.o loader.o lock.o logger.o manager.o manager_bridges.o manager_channels.o manager_endpoints.o  manager_mwi.o manager_system.o max_forwards.o md5.o media_cache.o media_index.o message.o mixmonitor.o named_acl.o named_locks.o netsock.o netsock2.o optional_api.o parking.o pbx.o pbx_app.o pbx_builtins.o pbx_functions.o pbx_hangup_handler.o pbx_ignorepat.o pbx_include.o pbx_sw.o pbx_switch.o pbx_timing.o pbx_variables.o pickup.o plc.o poll.o presencestate.o privacy.o rtp_engine.o say.o sched.o sdp.o sdp_options.o sdp_srtp.o sdp_state.o sdp_translator.o security_events.o sem.o sha1.o sip_api.o slinfactory.o smoother.o sorcery.o sounds_index.o srv.o stasis.o stasis_bridges.o stasis_cache.o stasis_cache_pattern.o stasis_channels.o stasis_endpoints.o stasis_message.o stasis_message_router.o stasis_system.o stdtime/localtime.o strcompat.o stream.o stringfields.o strings.o stun.o syslog.o taskprocessor.o tcptls.o tdd.o term.o test.o threadpool.o threadstorage.o timing.o translate.o udptl.o ulaw.o uri.o utils.o uuid.o version.o xml.o xmldoc.o  -> asterisk
./libasteriskpj.so: undefined reference to `initBcg729EncoderChannel' 
./libasteriskpj.so: undefined reference to `bcg729Decoder'
./libasteriskpj.so: undefined reference to `bcg729Encoder'
./libasteriskpj.so: undefined reference to `initBcg729DecoderChannel'
./libasteriskpj.so: undefined reference to `closeBcg729EncoderChannel'
./libasteriskpj.so: undefined reference to `closeBcg729DecoderChannel'

I have the same version of libsrtp as you do, and I've tried it with and without the AUR packages for bcg729 and pjproject.

Any ideas on what other packages or system configs might be playing into this? Perhaps we should be comparing full outputs from ./configure?

Same exact situation as @d9jWbb42kC3 with libsrtp 1:2.1.0-1. Also took out --without-pjproject-bundled to get it to compile.

   [CC] pjsip/dialplan_functions.c -> pjsip/dialplan_functions.o
   [CC] pjsip/cli_commands.c -> pjsip/cli_commands.o
   [LD] chan_pjsip.o pjsip/dialplan_functions.o pjsip/cli_commands.o -> chan_pjsip.so
/usr/bin/ld: cannot find -lsrtp
collect2: error: ld returned 1 exit status
make[1]: *** [/build/yaourt-tmp-admin/aur-asterisk/src/asterisk-15.2.0/Makefile.rules:178: chan_pjsip.so] Error 1
make: *** [Makefile:377: channels] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Makepkg was unable to build asterisk.

If I compile asterisk without flag --without-pjproject-bundled, everything is ok. Installed extra/libsrtp is 1:2.1.0-1. Arch: x86_64

I've successfully compiled 15.2 for my systems, but only with something that looks like a regression in packaging. I'm not sure it's actually a bad thing or not, but it's the only way I can get 15.2 up and running. I added pjproject back to the dependency list and compiled with --without-pjproject-bundled.

If anybody has a problem with this arrangement and/or knows why the internal version throws bcg729 errors when compiling then I'm happy to hear it.

@albertvaka Could you contact me with any more details on how you got this to work. I have a production phone system that's offline with a broken asterisk install and am trying to get this fixed up. I also just adopted this package and will try to get it working better for everybody. I updated it to the last version, but I'm getting compile time errors ... the error you link to I get with 15.1.x, but on 15.2.x I'm seeing a different problem related to pj and/or bcg729. I'd be interested in hearing about what worked for you, either here, via email or if you want to collaborate I just mirrored this to Github: https://github.com/alerque/aur-asterisk

The current version only builds with libsrtp version 1.

If you have the latest libsrtp installed, it fails with this:

https://issues.asterisk.org/jira/browse/ASTERISK-27356