Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Tree [e871b5] master /
History



File Date Author Commit
rtp_cluster 2014-04-03 Maksym Sobolyev Maksym Sobolyev [f15d86] o in the up_command, properly use local_ip modi...
sippy 2014-06-06 Maksym Sobolyev Maksym Sobolyev [e871b5] Add ability to bind UDP command client to a spe...
socket_server 2013-01-09 sobomax sobomax [fe2c44] Provide declarations for certain functions that...
.gitignore 2012-08-20 Maksym Sobolyev Maksym Sobolyev [d511c8] Merge branch 'master' of ../sippy
COPYING 2012-08-20 Maksym Sobolyev Maksym Sobolyev [d511c8] Merge branch 'master' of ../sippy
MANIFEST.in 2012-08-20 Maksym Sobolyev Maksym Sobolyev [d511c8] Merge branch 'master' of ../sippy
README 2012-08-20 Maksym Sobolyev Maksym Sobolyev [d511c8] Merge branch 'master' of ../sippy
setup.py 2012-08-20 Maksym Sobolyev Maksym Sobolyev [d511c8] Merge branch 'master' of ../sippy

Read Me

Sippy B2BUA is a RFC3261-compliant Session Initiation Protocol (SIP)
Back-to-back user agent (B2BUA) server software. 

The B2BUA is a SIP call controlling component. Unlike a SIP proxy server,
which only maintains transaction state, the B2BUA maintains complete call
state and participates in all call requests. For this reason it can perform
number of functions that are not possible to implement using SIP proxy, such
as for example accurate call accounting, pre-paid rating and billing, fail
over call routing etc. Unlike PBX-type solutions such as Asterisk for example,
the B2BUA doesn't perform any media relaying or processing, therefore it
doesn't introduce any additional packet loss, delay or jitter into the
media path. 

Features:

 o 5,000-10,000 simultaneous sessions per server;

 o 150-200 call setups/tear-downs per second;

 o Realtime calls control and call data records (CDRs) generation;

 o Optional ability to use Sippy RTPproxy for media relaying;

 o Optional ability to perform Cisco-compatible RADIUS AAA (Authentication,
   Authorization and Accounting);

 o RFC3261 compliance;

 o Seamless compatibility with majority of popular SIP software and hardware on
   the market today;

 o Robustness and Resilience;

 o Simple and clean, yet flexible, internal design making implementing new
   features and services easy;

 o B2BUA could be easily combined with other Open Source software, such as SIP
   Express Router / OpenSIPS to build complete softswitch solution.