Yaku 🐗
boosted
Leo
boosted
La pubblicità della SIP è stata un’allucinazione collettiva, vero? VERO?!
La pubblicità della SIP è stata un’allucinazione collettiva, vero? VERO?!
Stefano Marinelli
boosted
As I wrote before (https://mastodon.bsd.cafe/@evgandr/115912395421390028) I tried to use TURN server for communication with my relatives, but failed to setup secure enough solution. So, I decided to try an old and reliable solution — Asterisk. With the help of a book "Asterisk: The Definitive Guide" from J.V. Meggelen & R. Bryant & L. Madsen, of course.
First, I was forced to build the asterisk package by myself (from ports, ofc), since the binary version from NetBSD repository compiled with the all DB support, except my favourite PostgreSQL database.
By the way, adding users and writing dialplan with the help of aforementioned book was not so hard as I expected 
. Same for network setup. Since, I'm using PJSIP I just opened SIPS port and a range of UDP ports for RTP protocol on the my firewall. Despite, my home network hidden behind NAT on the router, there are no big problems with networking — end-user devices and an Asterisk server connected with use of simple star topology.
Surpisingly, the quality of the voice call is excellent comparing with service, provided by local cellular network operators. I suppose, that the secret in used codecs, or it is because there are not so much users (only 2) of my service.
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something 😒
Of course, it is impossible, since anonymous access or any other access without right key is impossible. But, there are no IPs of attackers in the log file, even wth "Verbose" directive — only my local and public IPs and my server's hostname 
Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?
As I wrote before (https://mastodon.bsd.cafe/@evgandr/115912395421390028) I tried to use TURN server for communication with my relatives, but failed to setup secure enough solution. So, I decided to try an old and reliable solution — Asterisk. With the help of a book "Asterisk: The Definitive Guide" from J.V. Meggelen & R. Bryant & L. Madsen, of course.
First, I was forced to build the asterisk package by myself (from ports, ofc), since the binary version from NetBSD repository compiled with the all DB support, except my favourite PostgreSQL database.
By the way, adding users and writing dialplan with the help of aforementioned book was not so hard as I expected . Same for network setup. Since, I'm using PJSIP I just opened SIPS port and a range of UDP ports for RTP protocol on the my firewall. Despite, my home network hidden behind NAT on the router, there are no big problems with networking — end-user devices and an Asterisk server connected with use of simple star topology.
Surpisingly, the quality of the voice call is excellent comparing with service, provided by local cellular network operators. I suppose, that the secret in used codecs, or it is because there are not so much users (only 2) of my service.
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something 😒
Of course, it is impossible, since anonymous access or any other access without right key is impossible. But, there are no IPs of attackers in the log file, even wth "Verbose" directive — only my local and public IPs and my server's hostname
Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?
RE: https://mstdn.social/@rysiek/116007605131589165
I use IRC to stay in touch with my wife.
@delta for me #voip #sip @Belledonne_Communications is a game changer for decentralized audio/video calls.
Mostly talking about private use case.
Sabrina Web :privacypride: 📎
boosted
Does anyone know of a FREE SIP phone for MacOS or Android that can register multiple lines?
Does anyone know of a FREE SIP phone for MacOS or Android that can register multiple lines?
Claudius Link
boosted
Neu im #CCC Event-Blog: Telefonie auf dem #39C3
Alle Infos zu Vorbereitung, Hardware, SIM/eSIM und Betrieb vor Ort findet ihr im Blogpost:
https://events.ccc.de/2025/12/23/39c3-poc/
New on the CCC event blog: Telephony at 39C3
Find all details on preparation, hardware, SIM/eSIMs and on-site operation here:
https://events.ccc.de/en/2025/12/23/39c3-poc/
#ChaosCommunicationCongress #Telephony #DECT #SIP #GSM #ISDN #amazingtimetomarket
3 media
Neu im #CCC Event-Blog: Telefonie auf dem #39C3
Alle Infos zu Vorbereitung, Hardware, SIM/eSIM und Betrieb vor Ort findet ihr im Blogpost:
https://events.ccc.de/2025/12/23/39c3-poc/
New on the CCC event blog: Telephony at 39C3
Find all details on preparation, hardware, SIM/eSIMs and on-site operation here:
https://events.ccc.de/en/2025/12/23/39c3-poc/
#ChaosCommunicationCongress #Telephony #DECT #SIP #GSM #ISDN #amazingtimetomarket
3 media
I don’t know what I was expecting but it looks more and more like the Messaging Interoperability the EU promised will be each gatekeeper essentially publishing their client to server protocol and then you can either use multi protocol messengers or transports. No s2s federation.
Looks like one might be able to log in through the (propriety) c2s API with third party IDs though.
@daniel that's sad but not unexpected.
Another point of view is to work with small actors to build that together.
And I think of course to #XMPP and #matrix and #Sip but also to #threema #wire and #deltachat for example!
Having a working instant messaging operability between open source actor looks like a good first step, isn't it?
C++ implementation of SIP, ICE, TURN and related protocols
marc0s
boosted
#FOSDEM announced the devrooms for #fosdem2026 and I have some good news and some bad news.
The good news is that my submission for a #MusicProduction devroom got accepted, yay! Finally #music will have a well deserved place at FOSDEM! It'll be on Sunday afternoon, expect a CfP soon 🙏
The (super)bad news is that they rejected the #RTC devroom, though... 😢 I can't remember the last time that happened, I think it's always been there? No room for #webrtc #sip and other stuff this time around...
#FOSDEM announced the devrooms for #fosdem2026 and I have some good news and some bad news.
The good news is that my submission for a #MusicProduction devroom got accepted, yay! Finally #music will have a well deserved place at FOSDEM! It'll be on Sunday afternoon, expect a CfP soon 🙏
The (super)bad news is that they rejected the #RTC devroom, though... 😢 I can't remember the last time that happened, I think it's always been there? No room for #webrtc #sip and other stuff this time around...