Package Details: asterisk 21.2.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
Submitter: pressh
Maintainer: nkukard (alerque)
Last Packager: nkukard
Votes: 112
Popularity: 0.000416
First Submitted: 2008-01-27 13:42 (UTC)
Last Updated: 2024-03-28 07:09 (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 2 3 4 5 6 7 8 9 10 .. 24 Next › Last »

nkukard commented on 2020-12-15 06:32 (UTC)

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

brackenhill-mob commented on 2020-12-14 18:07 (UTC)

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

Astroturf commented on 2020-12-05 19:16 (UTC) (edited on 2020-12-05 19:17 (UTC) by Astroturf)

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

romainhumbert commented on 2020-08-26 07:49 (UTC) (edited on 2020-08-26 07:51 (UTC) by romainhumbert)

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

hytrax commented on 2020-07-16 12:42 (UTC)

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

alerque commented on 2020-07-15 12:07 (UTC)

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

hytrax commented on 2020-07-15 09:24 (UTC)

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.

alerque commented on 2020-05-03 13:55 (UTC)

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

hytrax commented on 2020-05-03 10:48 (UTC)

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

alerque commented on 2020-05-02 20:36 (UTC)

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