sipster
Toying around with using aiosip for agent/scenario testing similar to how SIPp works. Lost of stuff to do, but looking very, very promising.
Currently almost non-functional, part of a fast answer scenario is implemented, and that requires a customized aiosip install which I haven’t published yet - its stuff I want to get upstreamed.
To run it:
Example
python -m sipster.scenarios.fastanswer
TODO
Upstream API changes where makes sense
Integrate RTP and DTMF support from aiortp
pytest integration via plugin
Provide a set of useful general SIP compliance tests
Metadata
Release files for sipster 0.0.1
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 | Actions |
|---|---|---|---|---|
| sipster-0.0.1.tar.gz | 8.2 kB | Without provenance | Details for sipster-0.0.1.tar.gz |
Release files / sipster-0.0.1.tar.gz
| Download URL | sipster-0.0.1.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57689f54c167158f8a8005e32ea2eb27fc534a4daf0b96acca2d285539af48cb
|
|
BLAKE2b-256 checksum How to use checksums |
f43a7f3490e67c0437a4ccce4fff799bba0cb0c101dc8558fae23f8018032cd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sipster 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.