Certainly hole punching [1] (via PCP, UPnP IGD) is still needed for P2P clients like home video games and consoles, but most home/CPE routers support that, and there's not much more infrastructure needed.
P.S. / N.B.: And just because you have a globally routable address on your home computer does not mean that the address is globally reachable: stateful firewalls (on D-Link, Asus, Linksys, Netgear, etc) are a thing.
[1] https://en.wikipedia.org/wiki/Hole_punching_(networking)
Those IPv6 addresses would need hole punching, the same as IPv4. IPv6 isn't simplifying this use case. It's more complexity than just IPv4.
Yes, IPv6 needs hole punching like IPv4.
But IPv4 needs hole punching and a whole bunch of extra crud. A whole bunch of crud can be thrown out the window if you have globally routable addresses on your machine.
> IPv6 isn't simplifying this use case. It's more complexity than just IPv4
Not needing ICE/TURN/etc seems like simplification to me.
But when I looked into it very briefly it seemed most sip stuff is geared calling and receiving calls from phone numbers (which I'm completely uninterested in) and what I had in mind is surprisingly complicated to set up.
Would this project be suitable for my usecase?
OpenSIPS will do what you need. But configuring it requires a bit of reading. There's no easy way in the VoIP world unfortunately.
just_mc•2mo ago
Most other open source SIP stacks available either don't have the feature depth and breadth required for a serious SIP project: are only usable from a specific programming language, have been long abandoned, or have impermissive licenses.
j1elo•2mo ago
Is that not the case for this library? It's written in C++, and didn't find any mention whatsoever about usage from other languages being an expected use case in the README. C++ can be used via FFI from other languages, but it's my understanding that it is difficult and error prone, unlike C which seems the perfect fit for multi-language libraries.