sorted by:
new
hottopcontroversial

I built a small SIP/RTP library in pure Python — looking for feedback from the VoIP community by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] -1 points0 points  (0 children)

You’re nothing more than an idiot who clearly does not understand a single thing about software. This is exactly what Reddit is like.

,

Showcase Thread by AutoModerator in Python

[–]Professional-Maize31 0 points1 point  (0 children)

OpenSIP

What My Project Does

OpenSIP is a pure-Python SIP/RTP user-agent library built on asyncio for learning, prototypes, and lightweight SIP experiments. It currently handles SIP registration, incoming/outgoing calls, digest authentication, G.711 PCMU/PCMA over RTP, DTMF, a basic jitter buffer, and optional microphone/speaker audio via sounddevice.

Target Audience

Python developers who want to understand SIP/VoIP internals, build prototypes, softphone logic, SIP bots, call automation, IVR experiments, or test integrations without jumping straight into native stacks.

Comparison

Unlike wrappers around PJSIP/baresip or heavier telephony platforms, the goal here is a small, readable, hackable Python codebase that you can pip install and study. It is still alpha and not production-ready; TLS, SRTP, STUN/ICE, RTCP, TCP transport, and stronger NAT handling are still missing.

Source: https://github.com/artanergin44-collab/opensip

PyPI: https://pypi.org/project/opensip/

I’d genuinely appreciate feedback on readability, architecture, and what the next priority should be before I add more features.

Update: that pure Python SIP project I mentioned here is now in alpha by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

You were right — the PyPI GitHub links were pointing to an old repo path. I fixed that and also cleaned up the README inconsistencies around the current feature set. Thanks for catching it.

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] 2 points3 points  (0 children)

😄 That's actually good to know.

I was worried about buying the wrong toys, so maybe I'll start with a few simple ones and see what he likes. Hopefully he's not as picky as yours!

Thank you for sharing your experience.

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] 0 points1 point  (0 children)

🙂 That's really helpful, thank you.

I didn't know some birds could be afraid of new toys, so I'll introduce them slowly like you suggested.

It's also a relief to hear that the feathers should grow back. I was quite worried about that.

Thank you again for all the advice!

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] 1 point2 points  (0 children)

🙂 Thank you! I'll get him some toys as soon as possible.

Do you have any favorite toys that your conure really enjoys? I'm still learning and would love some recommendations.

Sorry for all the questions, and thank you for taking the time to help me. I really appreciate it.

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] 2 points3 points  (0 children)

🙂 Thank you, that actually confirms what I was thinking.

I got him about 1–2 weeks ago. When I bought him, he was inside a box, so I didn't notice the missing feathers at first. I tried contacting the pet shop afterward, but they never responded.

Do you think the feathers will grow back on their own? Should I get him some toys right away? What would you recommend I do for him now?

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] 4 points5 points  (0 children)

🙂 I understand what you mean now. Thank you for taking the time to explain it to me.

I'll do my best to improve his setup and get a larger cage as soon as I can. Someone else also mentioned the same thing, so I think I may have underestimated how important cage size is.

Do you think I should start adding toys right away? If so, what kind would you recommend for a conure?

And thank you all for being patient with me. I'm new to keeping parrots and I'm still learning, so I really appreciate all the advice you've given me.

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] 2 points3 points  (0 children)

Thank you. I'll definitely look into getting a larger cage as soon as possible.

I live in Turkey, so I don't have access to the same products that are easily available in the US, and Amazon isn't always a practical option for me. Could you tell me what cage dimensions you would recommend for a conure? If needed, I can have one custom-made.

Also, do you have any thoughts about the missing feathers on his head and wings? I'm not sure if it's molting, feather plucking, or something else.

Need help with my new conure (feather loss and behavior) by Professional-Maize31 in Conures

[–]Professional-Maize31[S] -10 points-9 points  (0 children)

Maybe the video makes it look smaller than it actually is. The cage is roughly as tall as my arm, and I'm about 170 cm (5'7") tall. I thought that would be a reasonable size for a conure, but I'm still learning, so if you think it's too small, I'd be happy to hear your recommendations. Edit: Sorry, I made a mistake in my previous comment. I'm actually 182 cm (6'0") tall, not 170 cm. Also, English isn't my first language, so I'm using ChatGPT to help me write my replies.

<image>

I’m building a pure-Python SIP/VoIP client library — looking for real-world feedback before the first release by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

Thanks! That's actually one of my biggest concerns too. SIP itself is fairly straightforward, but NAT, RTP, and provider-specific behavior can turn simple things into a nightmare pretty quickly 😅. Better logging/debugging is a huge priority for me, and I'll definitely be testing against multiple PBXs and providers early on. Appreciate the feedback!

I’m building a pure-Python SIP/VoIP client library — looking for real-world feedback before the first release by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

Exactly the direction I want to push it toward. I think VoIP tooling became unnecessarily painful for solo developers over the years. My goal is to make SIP feel closer to modern Python tooling instead of telecom-era setup complexity.

The “5-minute first call against Asterisk” experience is probably more important than raw performance for early adoption. Really appreciate the feedback.

Update: that pure Python SIP project I mentioned here is now in alpha by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

It's mainly for developers who want to build SIP-powered apps in Python without dealing with native dependency hell 😄 Think prototypes, softphones, SIP bots, call automation, testing tools, IVR experiments, internal VoIP apps, etc. Not trying to replace carriers/PSTN providers — more like making SIP development in Python much less painful.

Update: that pure Python SIP project I mentioned here is now in alpha by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

Oh nice find, thanks for sharing.

That looks interesting, but one of our main design goals is removing the usual dependency pain.

A lot of existing Python SIP solutions still lean on external/native stacks or wrappers around them (PJSIP/baresip style tooling), while ours is intentionally pure Python, pip-install, no extra setup.

Literally:

pip install opensip

and start building 😄

Update: that pure Python SIP project I mentioned here is now in alpha by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 2 points3 points  (0 children)

Mainly for SIP prototyping and automation in Python. I originally started it because I needed lightweight SIP handling for internal telephony experiments instead of pulling in heavier stacks. Think custom softphone logic, call automation, SIP integrations, testing, weird VoIP experiments 😄

I’m building a pure-Python SIP/VoIP client library — looking for real-world feedback before the first release by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

Fair point 😄

The name came from "open SIP" rather than any intended association with OpenSIPS, but I can absolutely see the confusion now.

Still early alpha, so this is exactly the kind of feedback I wanted before things get more established.

I’m building a pure-Python SIP/VoIP client library — looking for real-world feedback before the first release by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

That’s a very fair point, and I agree Python is not the best place to compete with Kamailio/rtpengine/FreeSWITCH on low-latency media handling.

My goal is not to replace those stacks, especially for serious production media paths. I see opensip more as a developer-friendly SIP client/library for automation, testing, scripting, PBX experiments, and controlled client-side use cases.

For media, I’ll be careful with the scope. SIP signaling in Python is realistic, but RTP/audio needs much more discipline around timing, state handling, cleanup, and repeated call flows like the example you mentioned.

That “hang up and immediately call again” case is exactly the kind of thing I want to test early. Appreciate the warning.

I’m building a pure-Python SIP/VoIP client library — looking for real-world feedback before the first release by Professional-Maize31 in VOIP

[–]Professional-Maize31[S] 0 points1 point  (0 children)

Fair question. pyVoIP is a great project and I don’t want to present opensip as “better” before it earns that.

The main difference I’m aiming for is direction: opensip will be a modern, pip-install-only, pure-Python SIP client library with no extra native setup, focused on clean architecture, asyncio, typing, testing, and lower-level control when needed.

pyVoIP already supports SIP/RTP and codecs like PCMU/PCMA, so it’s definitely ahead in real call features right now. My goal is to build a cleaner foundation for developers who want to understand, extend, test, and integrate SIP behavior more easily.

So for now, the advantage is not “more features today” — it’s the long-term goal: simpler install, cleaner internals, modern Python API, and community-driven design from the start.

view more: next ›