Quick Subversion Checkout and Compilation HOWTO

From reSIProcate
Jump to navigation Jump to search

Information current as of: 2004-12-03 01:00 GMT



First, make sure you have the requisite version of subversion installed. This number, and other helpful information is available on the subversion info page at http://www.resiprocate.org/. You can find out what version you have on linux by running 'svn --version'. If you wind up accidentally using an old version of subversion, the sources you get will be unreliable and you will be faced with ridiculously difficult to diagnose problems. Don't do that.

Getting the Sources

Next, check out the sources. subversion is a little disk space intensive, and your initial check out may take a fairly long time. To do this on linux, run:

 svn checkout https://scm.sipfoundry.org/rep/resiprocate/main  resiprocate

This will create a 'resiprocate' subdirectory under whatever your current working directory is. Furthermore, svn commands will work inside and below that directory.

External Libraries

The build system relies on the following external packages, which may or may not be installed on your system by default (names in parentheses indicate common names for packages [e.g. for yum or similar]):

  • Berkeley DB (db4, db4-devel) - Windows users can use the version under contrib/db
  • Gnu Perfect Hash (gperf) - You can get by without this on Windows if you won't be adding headers, methods, or parameters. You might be able to get by on other systems without it, but the make system is as likely as not to hose some source files if you do -- see "Known Issues," below. Consequently, non-Windows users are urged to play it safe and install gperf before attempting to build.
  • Boost (boost, boost-devel)
  • Open SSL (openssl, openssl-devel)
    • You need version 0.9.8 or later if you want to use DTLS
    • Windows users can compile from source or may be able to save time by downloading the installable version from Shining Light
  • POPT (popt) - Windows users can use the version under contrib/popt
  • Perl Compatible Regular Expression Library (pcre) - Windows users can use the version under contrib/pcre


Now, you should be ready to compile the sources.

Unix Systems

Over resiprocate's history, there have been, at times, two different build systems, which often weren't kept in particularly good sync with each other. Currently (as of 02/2006), only one build system works reliably. To use it, change into the resiprocate directory and run "./configure". This guides you through a brief questionairre; you can accept default values by hitting "enter".

Once you're finished with the configure, and assuming you have all the prerequisites described above installed, you should be able to just type 'make' and have evreything build properly.

(There is some outdated build information at Configuration and Building a stack.)

Known Issues

The make system makes some assumptions about where certain things are installed and what they are called.

  • On some systems (e.g. debian), #include <db4/db_cxx.h> may need to be changed to #include <db_cxx.h>
  • On some systems (e.g. FC4), it is necessary to create a symbolic link from /usr/lib/libdb.so to the appropriate version of the db4 library (e.g. /usr/lib/libdb-4.3.so)
  • On some systems (e.g. FC4), it is necessary to create a symbolic link from /usr/lib/libdb_cxx.so to the appropriate version of the db4 library (e.g. /usr/lib/libdb_cxx-4.3.so)
  • If you attempt to build without gperf installed, you may end up with empty resip/stack/ParameterHash.cxx, resip/stack/HeaderHash.cxx, and/or resip/stack/MethodHash.cxx files. You will need to install gperf and delete these files to recover from this situation.

Windows Systems

This section needs to be filled out a bit more. The general thrust is that there are solution (.sln) files that you should be able to load up into Visual Studio 7.1 or later, and then just do the normal windows build voodoo. You'll want to build things in the following order:



Once that completes without error, you will have the library and a number of test programs compiled. To test the library, you can use the following test drivers. (These programs are also really useful in figuring out how to use the library)

Client Test

 resip/stack/test/testClient debug 'sip:you@some.legal.address.com;transport=udp'

This command will send an INVITE to the specified address. When the connection is established, testClient will send a BYE and then start the whole process over again. To get out of this loop, Ctrl-C testClient, and establish a connection. You can then send a BYE, which will time out, but the end result will be a disconnection.

Server Test

 resip/stack/test/testServer debug 5 udp

This command will listen on port 5070 for SIP messages, and accept 5 connections. You can then use a user agent to call that testServer 5 times.

  • NOTE: I'm sure that these tests are designed to be run together, and talk to eachother, but I have not gotten that to work. Instead, I use a SIP phone to interact with the two tests.
  • NOTE: The parameter 'debug' to both of the above programs is incorrect, but will have the desired effect.

Proxy Sanity Test

 tfm/sanityTests > sanityTestLog.txt

This comand will run a suite of tests on the repro proxy. It takes a while to run. While running, it will spit out a "." for each successful test, and a random, arbitrary capital letter for each test failure. At this point in time (02/2006), many of these tests fail. If you're feeling restless, you can go in and fix the code and/or tests as appropriate.