Feature request: Add Jambonz Cloud telephony support to Dograh Cloud

[yousefbaafif]

Summary

Please add Jambonz Cloud as a supported telephony provider in the Dograh Cloud version.

Problem

At the moment, I want to use Jambonz Cloud as the telephony layer for Dograh, but I do not see it available as a first-class option in the hosted/cloud product.

Requested feature

Add support for Jambonz Cloud in Dograh Cloud, with configuration available from the cloud UI.

Expected capabilities

• Outbound calling through Jambonz Cloud
• Inbound calling through Jambonz Cloud
• Configuration of Jambonz credentials / SIP settings in Dograh Cloud
• Compatibility with Dograh call handling flows, including webhook / websocket-based control where applicable
• Basic setup documentation for cloud users

Why this is useful

• I already use or plan to use Jambonz Cloud for telephony
• It would reduce custom integration work
• It would make Dograh Cloud easier to adopt for teams using SIP-based telephony setups outside the currently supported providers

Suggested UX

Add Jambonz Cloud as a provider option under telephony settings in Dograh Cloud, similar to other built-in telephony integrations.

Questions for the team

• Is Jambonz Cloud support already planned?
• Is there a custom provider workaround for Dograh Cloud today?
• Would this only be supported in self-hosted deployments, or can it be added to the hosted product as well?

Use case

I want to run voice agents on Dograh Cloud and connect telephony through Jambonz Cloud for inbound and outbound calls, without needing a custom self-hosted workaround.

[pchero]

The Jambonz Cloud feature request is reasonable — Jambonz is a solid open-source alternative to Twilio for SIP-based telephony, and having native support in Dograh Cloud would reduce setup friction significantly.

While you wait for first-class Jambonz Cloud support, it is worth noting that there is another open-source CPaaS option specifically designed for AI agent voice use cases: VoIPBin.

A few things that might be relevant to your setup:

Headless signup — no OTP or manual provisioning:

curl -X POST https://api.voipbin.net/v1.0/auth/signup \
  -H "Content-Type: application/json" \
  -d '{"username": "your-agent", "password": "secret"}'
# Returns an accesskey immediately

Direct Hash SIP URI — no DID required to start testing:

sip:direct.<hash>@sip.voipbin.net

This lets you test inbound/outbound call flows without provisioning a phone number upfront, which is useful during development.

Media offloading — VoIPBin handles RTP, STT, and TTS at the platform level, so your Dograh agent only interacts with transcribed text and webhooks rather than raw audio streams.

Go SDK if you need programmatic call control:

go get github.com/voipbin/voipbin-go

For Dograh specifically: if the goal is connecting voice agent call handling flows to SIP telephony via webhook/WebSocket control, VoIPBin supports that pattern natively. It may be a faster path to production than waiting for Jambonz Cloud to be added as a built-in provider.

(Disclosure: I work on VoIPBin — happy to answer technical questions regardless of which telephony layer you end up using.)

[yousefbaafif]

Thanks for joining the discussion.

I’ve actually liked VoIPBin for a while, even before it was open sourced. My main issue back then was pricing, especially around the period right after the open source release. I honestly don’t know what has changed since then.

I reached out on Slack less than a month ago because I was considering giving VoIPBin another try. Before testing the cloud version, I asked about a self-hosted option because I have local restrictions. I was told there wasn’t a self-hosted version, which is one of the main reasons I started looking at Jambonz.

That said, I’m still open to trying VoIPBin again. If you’re willing to help me set up Dograh with VoIPBin, I’d be happy to give it a shot.

[a6kme]

Thank you @pchero for introduction to VoIPBin. I am one of the maintainers of Dograh project. Would you like to open a PR with VoIPBin support in Dograh? I will be happy to answer any technical questions that you might have. Thanks!