Package Details: pjsua 2.13-2

Git Clone URL: https://aur.archlinux.org/pjsua.git (read-only, click to copy)
Package Base: pjsua
Description: Open source command line SIP user agent
Upstream URL: http://www.pjsip.org/pjsua.htm
Licenses: GPL
Submitter: sputnick
Maintainer: chrko (thotypous)
Last Packager: thotypous
Votes: 16
Popularity: 0.000001
First Submitted: 2010-06-17 14:35 (UTC)
Last Updated: 2023-03-15 13:25 (UTC)

Latest Comments

1 2 3 Next › Last »

thotypous commented on 2024-02-05 13:23 (UTC)

@m040601 Thank you for pointing this out, I wasn't aware pjproject installed a pjsua binary (I thought it just installed the libs). I believe both packages existed when I started using this one, and I didn't test the pjproject package at the time.

I have been testing the pjproject package since you pointed this out and the only caveat I found is that it enables the portaudio backend, which is really buggy, and I didn't find a way to disable it at runtime. However, if you disable it by removing --with-external-pa from configure and portaudio from depends, it seems to work well.

I don't see this as a reason to maintain two different packages, though, unless one of them was named pjproject-no-portaudio or something like that.

Let's see what's @chrko opinion.

m040601 commented on 2024-02-02 23:10 (UTC) (edited on 2024-02-02 23:17 (UTC) by m040601)

There is another regurally updated PKGBUILD since 2007, "pjproject", https://aur.archlinux.org/packages/pjproject

It also installs a binary "pjsua".

I am not quite sure what the goals and differences of the different PKGBUILD's "pjsua" and "pjproject" are.

Apart from some optional dependencies.

Perhaps a "Conflicts: " tag is needed.

It would be nice if the PKGBUILD maintainers of both, collaborated, so that more eyes were available, and perhaps avoid reduplicating work.

With enough "Votes" maybe this could one day turn into an official Archlinux package.

It would also be less confusing for AUR end users to know which PKGBUILD to install exactly.

alessiotomelleri commented on 2023-03-15 13:51 (UTC)

@chrko ok... yes cloning and recompiling it's fine

chrko commented on 2023-03-15 12:22 (UTC) (edited on 2023-03-15 12:22 (UTC) by chrko)

@alessiotomelleri: As this is an aur package, I won't bump the pkgrel. Please just rebuild it. :)

alessiotomelleri commented on 2023-03-15 12:01 (UTC)

Hi,

it seems pjsua broken after latest ffmpeg updates.

$ pjsua pjsua: error while loading shared libraries: libavdevice.so.59: cannot open shared object file: No such file or directory

thotypous commented on 2022-04-14 18:28 (UTC)

@m040601 I use pjsua almost daily coupled with rlwrap:

rlwrap pjsua --config-file=/home/user/.config/pjsua

it works really well and I think it might be what you have been looking for.

Regarding the clean chroot, it is not a hack, but a standard Arch practice for building packages: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot. A package maintainer can't possibly anticipate how to deal with the environment of every possible user. By using a clean chroot, you reproduce exactly the same build environment as the maintainer. Of course it is not always needed, but it is the first thing you should try to do when building an AUR (or core/extra/community) package fails.

m040601 commented on 2022-04-14 16:35 (UTC) (edited on 2022-04-14 16:57 (UTC) by m040601)

@thotypous:

Thanks for your work keeping up and maintaining this PKGBUILD. Your last update to the PKGBUILD solved the problem. It both sends and receives call now. I'm using it like this:

pjsua --config-file ~/my_config_file

make sure you are building inside a clean chroot

Not sure what you mean by "chroot" here. I just try to install it like any other AUR. If it works, it works. If it doesnt work, I dont want to use any other hack.

use the prebuilt package from chaotic aur

Nice to know. Didnt know about this other option. Although, as above. I only use the AUR official repo, and what's in there. If it works, it works. IF it doesnt, I dont want to try any other third party thing to complicate my system.

These command line sip clients are already a pain in the ass to configure. Bad documentation, exotic and complicated configurations, and the developers assuming the end user must be an expert in "registrars", "proxy", "ports", "tcp/udp" and the whole sip vocabulary.

Maybe someone who masters this subject could contribute a little bit to the Archwiki with same basic concepts, report which sip clients are working and how to configure them.

There's only a page for, https://wiki.archlinux.org/title/Jami and a list (outdated) at https://wiki.archlinux.org/title/Soft-phone.

It would be nice if we had a generic Archwiki page with voip/sip information, catering, also, to command line users.

I'm a heavy command line proficient user. I prefer not use GUI sip/messenger clients. I've been testing, trying and reporting a lot of these sip commmand line clients in Archlinux. A lot of them are semi abandoned not well updated maintained in the AUR.

From all of them, pjsip/pjsua seems the most promising.

thotypous commented on 2022-04-14 15:39 (UTC)

@m040601 please make sure you are building inside a clean chroot or just use the prebuilt package from chaotic aur

m040601 commented on 2022-04-14 15:33 (UTC)

Currently fails with:

pjsua: error while loading shared libraries: libavdevice.so.58: cannot open shared object file: No such file or directory