Selfhosted

39435 readers

7 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Self-hosted VoIP? (mander.xyz)

submitted 8 months ago by [email protected] to c/[email protected]

20 comments fedilink hide all child comments

I would like to use a SIM7600X 4G Expansion Board (like this one) to connect my raspberry pi to the mobile network.

In this raspberry pi I am also running an XMPP server.

I want to then create an account that will bridge SMS messages between the SIM7600 and my XMPP account (should be easy), and ideally it should also be able to bridge phone calls (might be difficult?).

I know about the XMPP-VoIP JMP.chat, and since they are open source I can get some inspiration from them.

I will try to implement something myself, but I am not an amazing programmer. So I am wondering whether there is already some open source project that is more tailored for this application.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 8 months ago

The board finally arrived and it is indeed the SIM7600G-H, which is the global version.

I tried it on my raspberry pi 5 and struggled a bit because there was a change to the UART interface between the PI 4 and PI 5 and the documentation on this board describes the PI 4. But, after some fiddling around I figured out the correct setting and got it to work. The main difference is that the "UART0" needs to be explicitly turned on because the default debugging UART now uses the UART10 interface that is somewhere else on the board.