Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Baresip – An Open Source modular SIP User-Agent with audio and video support

github.com

Post reply on HN
Print view View original

11–20 of 57 posts

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#11

Post by cyberax »

Interesting. I'm trying to (in background mode) build an open source SIP video doorbell, and so far finding a good client that can work with raw video capture devices proved tricky. All the clients with video support need full X-Windows or Wayland stacks, which I most definitely don't want.

This seems to be exactly what I need!

Now, why did you have to write it in pure C?!? It's not a big deal for me, my VoIP devices are already in a separate VLAN without external access, but still.

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#12

Post by cyberax »

alophawen wrote: post #9
doubleg72 wrote: post #8

Earlier quoted context omitted.

So where does that leave H.323?

Last I worked with telephony (around 2010), IIRC we recieved calls over 3G network as SS7/H323 using Dialogic hardware and converted them on the fly to SIP as they entered our systems. The whole PBX was running on SIP using Asterisk.

I'm really intrigued. Is it possible to get video calling working with mobile networks' own video calling support over LTE? I could never find how it's done.

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#14

Post by ninjin »

After having gone through about a handful of SIP clients, I have to say that baresip is by far the most reliable one I have found. No random breakages. Accounts just work once you have the configuration done. It has some idiosyncrasies in terms of its configuration layout due to how tries to be possibly too modular and wide in scope, but it is still wonderful to use.

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#15

Post by posguy »

cyberax wrote: post #12
alophawen wrote: post #9

Earlier quoted context omitted.

Last I worked with telephony (around 2010), IIRC we recieved calls over 3G network as SS7/H323 using Dialogic hardware and converted them on the fly to SIP as they entered our systems. The whole PBX was running on SIP using Asterisk.

I'm really intrigued. Is it possible to get video calling working with mobile networks' own video calling support over LTE? I could never find how it's done.

Yes, T-Mobile and a few other carriers support videocalling right in the Android dialer.

https://www.t-mobile.com/support/plans-features/t-mobile-vid...

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#16

Post by cyberax »

posguy wrote: post #15
cyberax wrote: post #12

Earlier quoted context omitted.

I'm really intrigued. Is it possible to get video calling working with mobile networks' own video calling support over LTE? I could never find how it's done.

Yes, T-Mobile and a few other carriers support videocalling right in the Android dialer. https://www.t-mobile.com/support/plans-features/t-mobile-vid...

I've seen it work _once_, around 8 years ago on a T-Mobile branded Galaxy S phone.

I don't think it still works, and/or it requires some strange confluence of events to work.

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#17

Post by yed »

doubleg72 wrote: post #8
toast0 wrote: post #4

Earlier quoted context omitted.

SIP is more or less the signaling protocol for telephone service as VoIP. SIP doesn't include the actual audio, which is usually RTP on a different socket, but this client seems to do audio too. If you've got VoIP service for a landline, it's probably SIP. I think VoLTE might be SIP too? There's extensions for text messaging over SIP as well.

So where does that leave H.323?

It’s mostly a legacy protocol at this point.

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#18

Post by trzy »

cyberax wrote: post #11

Interesting. I'm trying to (in background mode) build an open source SIP video doorbell, and so far finding a good client that can work with raw video capture devices proved tricky. All the clients with video support need full X-Windows or Wayland stacks, which I most definitely don't want. This seems to be exactly what I need! Now, why did you have to write it in pure C?!? It's not a big deal for me, my VoIP devices…

Why would you not want it in a simple, portable language that's easy to build and deploy anywhere?

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#19

Post by NavinF »

cyberax wrote: post #11

Interesting. I'm trying to (in background mode) build an open source SIP video doorbell, and so far finding a good client that can work with raw video capture devices proved tricky. All the clients with video support need full X-Windows or Wayland stacks, which I most definitely don't want. This seems to be exactly what I need! Now, why did you have to write it in pure C?!? It's not a big deal for me, my VoIP devices…

What are your resource limits and threat model?

I hate X11 and C as much as any other human, but let's be real:

- If your hardware can decode video, it can probably deal with X11

- As you noted, security is easy if you never have to communicate with malicious devices. Don't "but still" me.

Re: Baresip – An Open Source modular SIP User-Agent with audio and video support

#20

Post by kelnos »

cyberax wrote: post #11

Interesting. I'm trying to (in background mode) build an open source SIP video doorbell, and so far finding a good client that can work with raw video capture devices proved tricky. All the clients with video support need full X-Windows or Wayland stacks, which I most definitely don't want. This seems to be exactly what I need! Now, why did you have to write it in pure C?!? It's not a big deal for me, my VoIP devices…

Looks like the project started in 2010; there weren't many great options then if you wanted to build something portable, not to mention easily bindable in other languages. (And there are plenty of good rationales for not wanting to use C++.)
Post reply on HN