VoIP

1 readers

1 users here now

Rules

Be civil. Disagreements of varying intensities will happen, but particularly vitriolic attacks will be pruned from the discussion.
Do not promote or advertise for any business, service or product unless responding to a specific request for recommendations. This includes recommending a user change providers when they have not indicated they are interested in doing so.
Do not send private messages to users, or invite users to send you a private message, for the purpose of promoting or advertising a business, service or product.
Do not invite, encourage, or seek help with engaging in unethical or fraudulent activity relating to VoIP, such as call spoofing, robocalling and autodialers, or fraudulent STIR/SHAKEN attestation.

founded 1 year ago

MODERATORS

communick@netheads.online

VOIP command line client / Raspberry PI solution (alien.top)

submitted 11 months ago by siga241@alien.top to c/voip@netheads.online

1 comments fedilink hide all child comments

Hey!
I want to create a "Phone" using a raspberry pi and some buttons. I was looking for a way to get the button input into some sort of client but had no luck finding a good solution. I was looking for command line tools that I could use in a python script but all I found were deprecated or undocumented :(

Since I'm not a VOIP Pro, I wanted to ask here. Maybe someone has a nice tip or solution?! As I said the goal is not necessarily to find a command line tool, it is to get the button input from the PI's GPIOs into a Software that can process audio only calls. I am fairly experienced in scripting, but I don't know how much effort it would be to write a tool from scratch

Thanks already if someone has some kind of Information for me <3

top 1 comments

sorted by: hot top controversial new old

[–] dwargo@alien.top 1 points 11 months ago

Probably your best bet would be to find a binding for the pjsip library. It has a command line here but I’m not sure how that would work with incoming calls. It’s the library Asterisk is switching to so it’s pretty battle-tested.

On the GPIO side, if you’re using ioctls I would use the new GPIO2 interface - it’s not entirely obvious the older one is deprecated. It’s event driven so you don’t have to spin-poll, and can do de-bouncing kernel-side. Of course Linus’s “don’t break userspace” mantra means the old interface will work for the foreseeable future.