Difference between revisions of "About Repro"

From reSIProcate
Jump to: navigation, search
Line 41: Line 41:
* Robert Sparks
* Robert Sparks
* Scott Godin
* Scott Godin
* [http://www.pocock.com.au|Daniel Pocock]
* [http://www.pocock.com.au Daniel Pocock]
=== Licensing ===
=== Licensing ===

Revision as of 21:35, 5 August 2012


What is repro?

repro is an open-source, free SIP server. SIP is changing the way people communicate using the Internet. It is not only about making phone calls over the Net. The SIP protocol and its extensions defines the way of establishing, modifying and ending interactive sessions, no matter if they are voice, video, IM or a combination of them. At the heart of SIP architecture, there are certain services which need to be provided at some place in the network. repro provides SIP proxy, registrar, redirect, and identity services. These services are the foundation needed to run a SIP service.

Where can repro be used?

  • As the central rendezvous service for peer-to-peer voice, IM, and presence services
  • As the core of large scale internet telephony services
  • As a tool to enforce policy at the boundary between networks or domains
  • As an edge server, providing Outbound (RFC5626) and/or SIP protocol conversion services

What makes repro unique and valuable?

  • Easiest SIP proxy to install and configure
  • Quickest way to start using SIP in Federated VoIP (analogous to running a public mail server)
  • Closely tracks the evolving standardization efforts
  • Focuses on large-scale operation, including high availability
  • Pays careful attention to both provider and subscriber security issues


repro officially born with this message from Cullen. It is based on the reSIProcate SIP stack.

Project Team

Although repro is an open-source project and thus several people is contributing to its development effort, there is a very talented and well reconignized project team leading this effort. Belonging to this team are:

  • Adam Roach
  • Byron Campen
  • Rohan Mahy
  • Jason Fischl
  • Derek MacDonald
  • Cullen Jennings
  • Robert Sparks
  • Scott Godin
  • Daniel Pocock


repro is distributed under the Vovida Software License v1.0 (Vovida)

Key Features

  • Correct and comprehensive implementation of the relevant standards from the SIP working groups
  • Support for multiple transport protocols (UDP/TCP/TLS/DTLS) over both IPv4 and IPv6
  • Rigorous security mechanisms, including the newest SIP Security IETF efforts
  • Simple user management through an embedded configuration web server
  • Use of readily available databases (currently Berkeley DB and MySQL) to store user data.
  • Extendable to support provider enhanced features while processing requests
  • Ability to syncronize active registration database with another node for high availability
  • Outbound (RFC5626) Support
  • Federated VoIP based on RFC 5922 (from v1.8 onwards)

Upcoming Features

  • Support for Postgres
  • Being an Event Server
    • Presence Server
    • SIP Dialog Package Server
  (note several people think this is a bad idea)


The repro users can discuss with other users about their doubts/questions to the repro users mailing list. Several companies are in the process of putting together commercial support plans for repro, reSIProcate and DUM that are targeted at application developers and service providers. More detail to follow.

How to Participate

You can discuss repro ongoing development at [repro developer mailing list http://list.resiprocate.org/mailman/listinfo/repro-devel]. Currently repro is held as a subtree of the reSIProcate source base at http://svn.resiprocate.org/rep/resiprocate/. You can read how to use subversion with reSIProcate at Quick Subversion Checkout and Compilation HOWTO

Project Details

Working with Repro

Current Features

  • Transports: UDP, TCP, TLS, DTLS (v4 and v6)
  • Platforms: Win32, Linux, Mac OS X
  • RFC 2976 compliant: INFO method
  • RFC 3261 compliant proxy and registrar
  • RFC 3263 compliant: NAPTR, SRV, A, AAAA
  • RFC 3581 compliant: Symmetric Response Routing (rport)
  • RFC 3891 compliant: Replaces header
  • RFC 3320 and RFC 4077: SigComp Compression (see SigComp Support])
  • RFC 5626 compliant: Managing Client-Initiated Connections in SIP
  • Extendable features
  • In-memory location server
  • Embedded web server and user database for basic administration
  • Full support for RFC4474 - SIP Identity Header
  • IPv6