sipXtapi - User Agent Framework SDK From the main page: sipXtapi is a comprehensive client library and software development kit (SDK) for SIP-based user agents. It includes SIP signalling support as well as a media framework. A complete and very feature rich softphone can be built easily by adding a graphical user interface on top of sipXtapi. Alternatively, sipXtapi was engineered to be embedded into existing applications adding real-time communications to such applications. sipXtapi have full featured, well tested voice processing framework, and video processing framework will be available in near future. The sipX SIP stack fully supports all relevant SIP RFCs; in particular a very extensive framework for firewall and NAT traversal. The media framework is the same used by the sipX media server. The sipXtapi SDK is a C application programming interface for real-time voice and video communications over IP. Specifically, sipXtapi provides a generalized interface for real-time communications on top of the Session Initiation Protocol (SIP), RFC 3261, and the real-time Transport Protocol (RTP), RFC 1889. While the SIP and RTP protocols provide signaling and media transport infrastructure, sipXtapi includes many additional protocols and standards implementations needed for voice and video communications. build instructions: http://scm.sipfoundry.org/rep/sipX/branches/sipXtapi/readme.txt **** relevant USE flags: gsm speex requirements: dev-libs/libpcre dev-util/cppunit (speex ? >=media-libs/speex-1.1) (gsm ? >=media-sound/gsm-1.0.10) Anyone willing to write an ebuild? I'll try, but I can't guarantee.
BTW, it requires SVN checkout, and I don't have a clue on how to do that.
Use subversion.eclass, luke... :) Examples in the tree usually can be found in ebuilds w/ 9999 version.
I found an overlay here: http://scm.calivia.com/svn/sipx/gentoo/ However, IMHO it is quite bloated and should require some cleanup. More importantly, it specifies different repositories than the one I found, so investigation is needed.
This package does not meet the current criteria needed to be a viable candidate for the Portage tree since the upstream sources are no longer available at the location provided by the bug. This criteria is currently listed at the following URL: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/Maintainer_Wanted Metric: Upstream status: Exists; "Package must still be available and fetchable (did it move to github, bitbucket, ...?)" If you (or another user) are still wanting this package to make it into the Portage tree please let us know by re-opening this bug and include a new usable upstream source. Sadly, until that time we cannot move forward with this. Tom D