Sippy B2BUA
Sippy B2BUA is a RFC3261-compliant Session Initiation Protocol (SIP) stack and Back-to-back user agent (B2BUA).
The Sippy B2BUA is a SIP call controlling component. Unlike a SIP proxy server, which only maintains transaction state, the Sippy 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 Sippy 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.
News
- Support for WebRTC clients has been added via RFC7118-compatible secure
websocket (
wss) interface. Combined with the functionality provided by the RTPProxy'sdtls_gwandice_litemodules allows building high-capacity WebRTC<->SIP gateways.
Features
- 5,000-10,000 simultaneous sessions per server
- 150-400 call setups/tear-downs per second
- Real-time calls control and call data records (CDRs) generation
- Optional ability to use Sippy RTPproxy for media relaying
- Optional ability to perform Cisco-compatible RADIUS AAA (Authentication, Authorization and Accounting)
- RFC3261 compliance
- Seamless compatibility with majority of popular SIP software and hardware on the market today
- Robustness and Resilience
- Simple and clean, yet flexible, internal design making implementing new features and services easy
- Sippy B2BUA could be easily combined with other Open Source software, such as SIP Express Router / OpenSIPS to build complete softswitch solution
Installation
Install latest stable version
pip install sippy
Install latest development version
pip install git+https://github.com/sippy/b2bua
Running
To get started, you can use the b2bua_simple implementation. The following example will cause the b2bua run in the foreground so you can see the SIP messaging. If you make a call to the IP address of your host machine, the b2bua will recieve the call on its UAS side, and it will send a new call leg out its UAC side to the IP address 192.168.1.1. It is expected that 192.168.1.1 is some sort of SIP switch or termination gateway.
b2bua_simple -f -n 192.168.1.1
Documentation
See documentation/documentation.md
Support us on Patreon!
Sippy B2BUA is available for use at the most liberal Open Source license there is and we promise to keep it this way. If you like our software, find it useful and want to support us moving it forward consider becoming a patron here Sippy Labs Patreon Page. In turn, we would give a priority to bugs and feature requests from our Patrons.
1 maintainer
Metadata
1 maintainer
Release files for sippy 2.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sippy-2.5.0.tar.gz | 136.2 kB | With provenance | Details |
Release files / sippy-2.5.0.tar.gz
| Download URL | sippy-2.5.0.tar.gz |
|---|---|
| Size | 136.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a883701155c6863be88f131135ce6210d2bb6cb0f158b7d014ed97ff7963c00
|
|
BLAKE2b-256 checksum How to use checksums |
35f825cc3b98c3f77051af43d95a905478dcf1cea69feff81b8e8a16b5cabd01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logSecurity for sippy 2.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for sippy-2.5.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
