Find a file
2026-03-20 17:02:38 -07:00
pjsua fixes 2026-03-20 17:02:38 -07:00
sipcord-bridge ye 2026-03-20 16:40:47 -07:00
wav big one 2026-03-20 16:08:41 -07:00
.env.example big one 2026-03-20 16:08:41 -07:00
.gitignore big one 2026-03-20 16:08:41 -07:00
Cargo.lock big one 2026-03-20 16:08:41 -07:00
Cargo.toml more formatting 2026-03-20 16:14:57 -07:00
config.toml big one 2026-03-20 16:08:41 -07:00
Dockerfile big one 2026-03-20 16:08:41 -07:00
LICENSE.md more formatting 2026-03-20 16:14:57 -07:00
README.md w 2026-03-20 16:52:46 -07:00

SIPcord Bridge

This is a slice of the code that powers SIPcord that you can use to self host something similar. It's not the full SIPcord package but rather the core functionality used in SIPcord with ways to build your own backend adapter. SIPcord itself uses this as a component of the full build so the code is the same that runs on the public bridges.

This means you have to build the call routing backend yourself. I am including a static-router backend which you can use to map extensions in a TOML file like this

[extensions]
1000 = { guild = 123456789012345620, channel = 987654321012345620 }
2000 = { guild = 123456789012345620, channel = 111222333444555620 }

but if you want more fancy routing you have to build it. You can easily use sipcord-bridge as a library and provide your own routers by implementing the Backend trait.

This was written a mix between myself and claude, sure, some of it's big slop but the parts I care about are not.

Can you help me set this up?

No. I am not providing support for this as my goal is to run sipcord.net, not support self hosting. If you want to run this self hosted, feel free to use this code but you are on your own here.

I have a feature request!

PR's welcome. No really, feel free to implement it and contribute.

Acknowledgements

License

Code is AGPLv3 Dusthillguy track is whatever dusthillguy wishe