singpolyma

If we ever move to supporting SIP directly, it will include TLS support. Right now JMP does not really support SIP at all except that we leave a "back door" open where you can log in to (one of) our carriers directly on their SIP server.

We're more likely to provide an easier to set up SIP->puppet XMPP style gateway or something like that, which would have the same benefits and you can setup today with a bit of asterisk tinkering. Or something with https://sip.cheogram.com/ or maybe software for non-SIP hardphones.

In general we know that some % of the customer base prefers hardphones and we do like to support this use case, but I wouldn't want to commit to a specific version of the future for this. Will we have a way for you to use a hard phone with more encryption in the next 5 years? Probably. But there's nothing in motion today that I can point to.

Oh sure, if you wanted to puppet a Jabber ID from Matrix then I guess that would work to be able to still have a Jabber ID to log into.

I'm not aware of any bridges that operate that way though.

No, as many devices as you like of course.

The Cheogram app? That is a Jabber app, speaking the XMPP protocol. So if you switch the account to go via a bridge to Matrix instead you wouldn't even have an account for the app to log in to.

https://github.com/matrix-org/matrix-bifrost but it doesn't support calling and of course the user experience can never be as good with a client that isn't aware of the use case.

Worst case if you can't see the accept button on that page for any reason, you can backup, uninstall, and reinstall the app. Make sure you know your password.

If it must be a desktop app then probably Dino. Or you can use any client even without calls support alongside https://git.sr.ht/~singpolyma/ccd

If web is ok then mov.im or https://app.cheogram.com/ (in alpha testing) may work for you

Depending on your use case you can set all calls that aren't from known contacts to go straight to voicemail

If your current provider gives you a SIP URI for inbound, we can forward calls there as well at no extra charge. And yeah, outbound won't work that way.

So the main thing you're looking for is an option to block level C attestation calls. That's something I think we have all the information for, but haven't made an option for yet.

Monocles is a fork of Cheogram so has everything Cheogram has usually and will work fine. That said, Cheogram ceratinly has replies and reactions (that is, in fact, the reason Monocles has them, we had them before basically any other app).

You SIP phone will work with the default account, but not TLS or SRTP it's a direct connect to the carrier over standard UDP SIP.

Generally users use their party spam filtering stuff, but I'd be curious to hear more about what your other providers have been doing that you might like to see here.

Thanks for the bug report. Sounds like the app is forgetting you are a JMP user. This used to be a problem but we solved it with some caching in most cases. There may be a regression there we need to look at.

No. The Cheogram App is specifically designed to be Snikket compatible and have every feature Snikket app does

Maintenance is complete

We don't block anything, but there is a small chance it's an issue at an upstream carrier. If you contact JMP support with the details (what short code, etc) they can escalate with the carrier about this.

Yes it's basically a protocol translator to let you plug the twilio APIs into cheogram.com see https://wiki.soprani.ca/TwilioSetup

Not sure what you mean here. This post is in the atom feed for the blog already.

If you happen know someone working at the right department of a major RCS provider or user (Google, AT&T, etc) then let me know.