Getting the Source Code Distribution

  1. Getting the Release tarball
  2. Getting from GitHub
  3. Source Directories Layout
    1. Top-Level Directory Layout
    2. Individual Directory Inside Each Project

All libraries (PJLIB, PJLIB-UTIL, PJSIP, PJMEDIA, and PJMEDIA-CODEC) are currently distributed under a single source tree, collectively named as PJPROJECT or just PJ libraries. These libraries can be obtained by either downloading the release tarball or getting them from the source repository, the "Subversion trunk".

Getting the Release tarball

Getting the released tarball, in ZIP or TGZ format, which is a certain snapshot in time.

The latest released tarball can always be downloaded from the

You view all releases on

Getting from GitHub

You can get the latest, most up-to-date source code from

Be mindful that the most up-to-date code may not have gone through as rigorous tests as official releases.

Source Directories Layout

Top-Level Directory Layout

The top-level directories (denoted as $TOP here) in the source distribution contains the following sub-directories:


Contains makefiles that are common for all projects.


Contains MMP files for building Symbian target.


Contains header and source files of PJLIB. PJLIB is the base portability and framework library which is used by all other libraries


Contains PJLIB-UTIL header and source files. PJLIB-UTIL is an auxiliary library that contains utility functions such as scanner, XML, STUN, MD5 algorithm, getopt() implementation, etc.


Contains PJNATH header and source files. PJNATH contains STUN, TURN, and ICE implementation.


Contains PJMEDIA and PJMEDIA-CODEC header and source files. The sources of various codec wrappers (such as GSM, Speex, and iLBC) can be found under this directory. The codec libraries themselves normally will be put under $TOP/third_party directory


Contains PJSIP header and source files. This library is the SIP protocol stack implementation.


Contains source code for PJSUA and various sample applications, including the Python wrapper.


Contains various unit tests for the libraries.


Contains source code for various third party libraries, such as Speex, iLBC, and GSM codecs.

Individual Directory Inside Each Project

Each library directory further contains these sub-directories:


Contains binaries produced by the build process.


Contains build scripts/makefiles, project files, project workspace, etc. to build the project. In particular, it contains one Makefile file to build the project with GNU build systems, and a *.dsw workspace file to build the library with Microsoft Visual Studio 6 or later.


The build/output directory contains the object files and other files generated by the build process. To support building multiple targets with a single source tree, each build target will occupy a different subdirectory under this directory.


Contains Doxygen configuration file (doxygen.cfg) to generate online documentation from the source files. The output documentation will be put in this directory as well (for example, docs/html directory for the HTML files).

(to generate Doxygen documentation from the source tree, just run "doxygen docs/doxygen.cfg" in the individual project directory. The generated files will reside in docs directory).


Contains the header files for the project.


Contains libraries produced by the build process.


Contains the source files of the project.

Last modified 3 years ago Last modified on Oct 1, 2020 3:10:27 AM