(no title)
jdillaaa | 6 years ago
I have the Twilio SIM (T-Mobile coverage) in my primary SIM (iPhone dual sim), and then Verizon/ATT/Sprint/TMobile on my e-sim. The e-sim is for data only, because data is expensive (and slow) on Twilio. If you don't have Dual Sim then the data element may be a bit of a roadblock for you to totally switch over to the Twilio SIM depending on your data needs. Tthe goal of my setup is to be completely cell phone agnostic. I wanted to be able to send a single signal into the PSTN over an IP connection OR over a cell-only connection (no data). The native support on this is great when you use the Twilio SIM, but with call forwarding and some other hacks you can get support without the Twilio SIM. Also, the great thing about the SIM is that I can pop it into a phone from 2002, and have it talk to the internet through a series of signals sent via SMS (e.g. server maintenance, open up a firewall for a few moments, etc). I wrote a server that I point the SIM endpoint to, and this server handles all of the forwarding/reception of voice and SMS.
I also built out a CLI for messaging (pulls in SMS history, deletes from Twilio, stores locally encrypted, lets you send out messages on a "convo" view, etc)... using the python API, and then built out a Web UI for making phone calls using client.js (receiving phone calls TBD). This has integrated support with my CardDav contacts (and depending on if someone is in my contacts, they get a different number on the caller ID), which makes for a more powerful (IMO) app than an iOS VOIP app, of which the options are fairly clunky and limited.
It is all pretty hacky but if you want to talk more about it I am curious to see what you have built out. I am not totally dependent on it for a few reasons, a big one being that I don't want to send all of my communications through the unencrypted telephone network.. The long-term goal here is to package it and open-source it so that people can easily "free" their communications, but it is pretty scattered right now.
Eagerly awaiting the PinePhone to give me more flexibility with all of this.
rsync|6 years ago
Interesting how you are sending SMS with different caller-ID based on contacts, but I am curious - without a VOIP dialer, can you place voice calls from your native dialer with different caller ID ?
Please, please email (or trouble ticket) twilio and ask them to add an "email" verb to twiml ...
That is one of the big missing links in all of this - you should be able to fire off email alerts/messages in your twiml workflow without any third-party[1] integration or other accounts/logins, etc.
[1] I would still consider sendgrid third party since I need a different login, account, etc.
jdillaaa|6 years ago
Yes it is not very pleasant, and it is how you basically described it where you call a Twilio number, and then type in the destination. You could set up some sort of signaling where you activate the outbound number with an SMS which may be less cumbersome than dialing on a phone call, but for native support that is the only way I can think of -- just dialing the target number would of course route from your main Telco
A decent SIP app might be an alternative here, I haven't explored them thoroughly because of Twilio Wireless (last I checked they weren't spectacular, but SIP is good)