Package Details: python2-sipsimple 3.1.1-5

Git Clone URL: (read-only)
Package Base: python2-sipsimple
Description: Python SDK for development of SIP end-points
Upstream URL:
Keywords: SIP
Licenses: LGPL, custom:MIT
Submitter: promike
Maintainer: ljmf00
Last Packager: Niklas
Votes: 7
Popularity: 0.126739
First Submitted: 2016-06-01 14:02
Last Updated: 2018-08-19 21:47

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

ngld commented on 2017-05-09 22:53

Apparently this package isn't compatible with openssl 1.1.0.
It simply aborts with "error: PJSIP TLS support was disabled, OpenSSL development files probably not present on this system".

Here's a changed the PKGBUILD which compiles against openssl-1.0:

The new PKGBUILD fixed the problem for me.

ogarcia commented on 2017-03-01 10:23


Many thanks!!!

promike commented on 2017-03-01 10:22


Good luck with it :)

ogarcia commented on 2017-03-01 09:22

Package updated!

As I can see, seems that AG Projects are maintaining the packages in GitHub and not in their own "devel".

This not is a -git version cause not are based in master. Is using a tagged release ;).

promike commented on 2017-02-11 09:35


I wish I could have been more help.
Anyway, according to the sipsimple is still up-to-date.

If you have problems with your Blink;
a) you can try compiling Blink 2.0 from here:

b) you can try ogarcia's version of sipsimple. Somewhere around here:

I purged Blink from my machine, so I don't know which works the best :/

theforeigner commented on 2017-02-11 04:29

I noticed it as well, that AG Projects has a very messy repository and different versions in different locations. I've taken on to studying and understanding the Arch Build System, maybe one day I'll feel frisky enough to take on and maintain some package myself. Thanks for the great work you've done!

promike commented on 2017-01-30 17:28

I'm not going to maintain this package any more. It cannot be followed!
There are so many sources and this can't suit to every single version, e.g. Ogarcia's package which uses a completely different source, whereas I stuck with the stable one
(But there is a third source just to see it's not that easy: )
If you visit the site: you can see that sipsimple is up-to-date and this package was not supposed to be -git version.
I don't think it's a good idea to mix them, so I decided not to struggle with this.

Sooo, long story short. This package and it's dependencies can be adopted.

ogarcia commented on 2017-01-26 17:10

I send out of date to maintainer. In meantime you have an updated PKGBUILD here

Sprunge is out of quota, you have a copy in pastebin

promike commented on 2017-01-04 12:07

You tell me? I think I provide all the AUR dependencies of Blink. I didn't create all the PKGBUILDs, though, just forked them. It took some time to find all of them.
Respect due to the original coders!

I recommended that you should get rid of Yaourt for multiple reasons.
1) SipSimple works here, and I don't use Yaourt. It's easier to locate errors if you leave out unnecessary things, like Yaourt.
2) Yaourt is rather notorious, and it probably earned this title for good reasons. I understand it's very convenient, but it's not the only AUR helper out there. If you have time, and desire check 'Pacaur' out.
I don't think it has any drawbacks, in fact, according to this table Pacaur is superior.

doctorcolossus commented on 2017-01-04 03:54

Thanks, @promike.
I had the same version of gcc installed as you, but I reinstalled it as you suggested, and today sipsimple compiled fine for me with yaourt. My end-goal was to compile Blink (accomplished!), which has many AUR dependencies, and yaourt really makes life easier - it just runs the same makepkg commands as I would otherwise have to run manually for each and every dependency, except that resolves all dependencies on its own, like pacman does. I don't know what your problem with yaourt is. I still have no idea what the problem was, but I doubt it had anything to do with yaourt. I am not sure if reinstalling gcc was what fixed it either, but maybe - thanks either way. :)