Caller ID processing

From Wildsong
Revision as of 03:23, 17 June 2017 by Brian Wilson (talk | contribs) (Created page with "I am inspired by Signal 2017 to try out more of Twilio features and services. So let's explore what I can do with caller id on messages coming via Twilio. Note from here on w...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

I am inspired by Signal 2017 to try out more of Twilio features and services. So let's explore what I can do with caller id on messages coming via Twilio.

Note from here on when I say "messages" here, I mean both SMS text and voice calls.

Flow:

  1. A message comes in to Twilio on my number; could be either SMS or voice.
  2. Send it to one of the many Twilio Caller ID plugins.
  3. Find out where it's coming from (as much detail as is available in results of the plugin lookup.)
  4. Use a webhook to send the lookup results to my server Bellman.
  5. Geocode the location.
  6. Put it onto a map on a laptop that hangs on my kitchen wall.
  7. Voice and SMS messages will be forwarded to Bellman and to phone(s).
  8. Text of an SMS will be displayed on walltop.

When a voice call needs to be sent to Bellman, it's done with Twilio Elastic SIP Trunk and processed by Bellman's Asterisk server. Asterisk takes on the task of ringing handsets and perhaps recording voicemail.

I wanted to switch from Asterisk to OpenVBX but that turned out to be pretty much a non-starter. Asterisk was already running here and OpenVBX seems like a weak alternative.

I could add in Twilio FAX support too, but I've never actually needed fax support for anything. What else? Maybe conferencing? I don't need a call center here so Task Router is not interesting to me.

Grandstream phones do a nice job at video but I have no idea how that fits in here today. Maybe after Signal 2018.

I am thinking I should try to use Twilio Functions for some of this to reduce dependencies on Bellman.

That's about 5 or 8 projects right there. Let's start.

Receiving messages

This is what happens right now today. I need to write this down since I don't think I've ever done it.

SMS - Under Phone Numbers, click on the main number, and see Messaging "When A Message Comes In" is directed to some TwiML.

These days (June 2017) look in Developer section under Runtime then click on "TwiML Bins".

Sometimes I add code in Asterisk when I want calls to forward to my cellphone, so a call comes in on Twilio and then rings both my home phones and cellphone. Currently it just rings my home phones.

In Geo-CEG's account the active bin is called "Forward calls to all Geo-CEG staff" but it currently just rings my phone. It's just this:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
 <Dial>

<Number>

     +1707827xxxx

</Number>

 </Dial>
</Response>

where xxxx is the last 4 digits of my Twilio SIP Trunk number.

After creating a TwiML bin you can select it under "Numbers"; set "A Call Comes In" to "TwiML" and then pick the named bin.

There is another bin under Messaging "A New Message Comes In" called "SMS Forwarding". That bin contains

<?xml version="1.0" encoding="UTF-8"?>
<Response>
 <Message to="+1707827xxxx">Template:From: Template:Body</Message>
</Response>

where xxxx is the last four of my cellphone. I have the same thing in my personal account.