Project Summary
Sippy B2BUA is a RFC3261-compliant SIP Back-to-back user agent (B2BUA).
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.
Sippy B2BUA supports RADIUS AAA protocol, which is compatible with Cisco VoIP gateways allowing it to be seamlessly integrated into existing networks.
In a Nutshell, Sippy SIP B2BUA...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a small development team
with decreasing Y-O-Y commits -
...
took an estimated 3 years of effort (COCOMO model)
starting with its first commit in February, 2012
ending with its most recent commit about 1 month ago
Quick Reference
GNU General Public License v2.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
use of OSS increased in 65% of companies in 2016
-
...
anyone with an Open Hub account can update a project's tags
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
check out hot projects on the Open Hub
30 Day SummaryOct 19 2025 — Nov 18 2025
|
12 Month SummaryNov 18 2024 — Nov 18 2025
|
